Scan Details - Linux-first Docs for Azure

6554

Pages Scanned

2220

Pages Flagged

6365

Changed Pages

33.9%

% Pages Flagged

Live Progress

🔴 Connecting...

91%

Phase: queuing

Processing: https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-batch-process-send-receive-messages.md

Activity Feed

04:23:15 Scan started

Scan Information

Started At: 2025-07-08 04:23:15

Finished At: In Progress

Status: cancelled

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

Current Phase: queuing

Pages Found: 6554

Pages Processed: 5953

Estimated Completion: 2025-07-09 07:20:09

Problematic Pages

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides code and tooling examples exclusively for Windows environments, specifically using PowerShell for key and certificate generation. There are no equivalent instructions or examples for Linux or cross-platform environments, and Windows tools are mentioned first and exclusively.

Recommendations:

Provide equivalent Linux and cross-platform examples for generating symmetric keys (e.g., using OpenSSL, /dev/urandom, or Python scripts).
Include instructions for generating self-signed certificates on Linux/macOS (e.g., using OpenSSL) alongside the PowerShell example.
Explicitly mention that the provided PowerShell commands are for Windows, and offer alternatives for other operating systems.
Reference cross-platform tools (such as OpenSSL) before or alongside Windows-specific tools to avoid the impression of Windows being the default or only supported environment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-AzAutomationAccount, Set-AzAutomationAccount) for checking and modifying the local authentication setting. There are no CLI, Bash, or Linux-native examples provided, nor are cross-platform tools like Azure CLI mentioned. The documentation assumes familiarity with Windows tooling and does not offer Linux-equivalent commands or workflows.

Recommendations:

Add Azure CLI examples (e.g., using 'az automation account show/update') alongside PowerShell cmdlets for all operations.
Include REST API curl examples for Linux users, especially since the note mentions REST API usage.
Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux administrators.
Reorder examples or present them in parallel (PowerShell and CLI) to avoid Windows-first bias.
Reference Linux-native tools or scripting environments where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides both Linux and Windows sections for most tasks, but there are several areas where Windows tools, patterns, or instructions are mentioned first or exclusively. Windows-specific tools such as Kudu and FTPS are referenced without always providing Linux-native alternatives. Some instructions (e.g., process explorer in Kudu, Debug Console) are Windows-centric, and there is a tendency to mention Windows or its configuration options before Linux equivalents. In a few places, Linux-specific details are marked as 'Linux only' rather than providing parity for both platforms.

Recommendations:

Ensure that for every Windows-specific tool or workflow (such as Kudu, FTPS, Debug Console), an equivalent Linux-native approach is described, or explicitly state if not available.
When listing instructions or configuration options, alternate the order or present Linux and Windows in parallel, rather than always listing Windows first.
Provide Linux-native file transfer and diagnostic tools (e.g., SCP, SFTP, rsync) as alternatives to FTPS for downloading files like JFR recordings.
Where possible, avoid language that implies Windows is the default or primary platform (e.g., 'On Windows, you can...'), and instead use neutral phrasing or present both platforms equally.
Expand on Linux troubleshooting and management tools, such as using SSH, Linux package managers, and command-line utilities, to match the depth of Windows/Kudu coverage.
Review all examples and ensure that both Linux and Windows users have clear, actionable instructions for all major workflows.

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 alongside Azure CLI, and in some cases, before Linux-native alternatives. There are no explicit Linux shell (bash) or cross-platform scripting examples, and the PowerShell module is referenced directly. The documentation assumes familiarity with Windows tools and does not provide parity for Linux users beyond the Azure CLI.

Recommendations:

Ensure that Azure CLI (which is cross-platform) examples are always listed first, before PowerShell.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash shell usage examples where appropriate.
Avoid referencing PowerShell-specific modules (like New-AzDeployment) without also providing equivalent bash or shell script examples.
Add a note or section for Linux/macOS users, clarifying that all steps can be performed using Azure CLI in their native shell environments.
Where screenshots or UI instructions are given, ensure they are not Windows-specific, or clarify that the Azure portal is OS-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI (which is cross-platform) and Azure PowerShell examples for managing access keys, but the PowerShell examples are given equal prominence and detail, despite PowerShell being primarily associated with Windows. There are no explicit Linux/Bash-native script examples, and the CLI example notes that it must be modified to run in a Windows terminal, but does not provide a corresponding Linux/Bash example. There is also no mention of Linux-specific tools or workflows, and the PowerShell examples are more verbose and detailed than the CLI ones.

Recommendations:

Provide explicit Bash/Linux shell script examples alongside Azure CLI and PowerShell, especially for key management tasks.
Clarify that Azure CLI commands are cross-platform and provide any necessary modifications for both Windows and Linux shells.
Avoid giving PowerShell examples equal or greater prominence than CLI/Bash unless there is a Windows-specific feature being demonstrated.
Where PowerShell is used, consider providing a Bash equivalent for parity.
Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide sample commands for each where syntax or environment differs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively providing examples for creating a Windows virtual machine, omitting any Linux VM creation examples. Additionally, the PowerShell example is presented alongside Azure CLI, but there is no mention of Linux-specific tools or shell environments. The Azure CLI installation link defaults to the Windows tab, and the VM creation command uses a Windows image without showing how to use a Linux image.

Recommendations:

Add a Linux virtual machine creation example using both Azure CLI and PowerShell, specifying a common Linux image (e.g., Ubuntu).
Ensure the Azure CLI installation link is platform-neutral or includes Linux installation instructions prominently.
Where PowerShell is mentioned, also reference Bash or other common Linux shells for parity.
Explicitly state that the tutorial works for both Windows and Linux VMs, and provide guidance or examples for both.
Include screenshots or portal instructions that show both Windows and Linux VM Automanage blades if there are differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific features (such as modifying audit modes for security baselines in Guest Configuration for Windows machines only) and enabling WindowsAdminCenter in the ARM template, without mentioning Linux equivalents or providing Linux-specific guidance. There are no Linux-specific examples or clarifications about Linux support, and Windows-related options are mentioned explicitly while Linux is omitted.

Recommendations:

Explicitly state which features are supported for Linux VMs and which are Windows-only, especially in sections referencing features like Guest Configuration or WindowsAdminCenter.
Provide Linux-specific examples or clarify how to configure Automanage profiles for Linux VMs, including any differences in supported services or settings.
If certain services (e.g., Microsoft Antimalware, WindowsAdminCenter) are not available for Linux, mention equivalent Linux tools or note their absence.
Include ARM template snippets or configuration examples tailored for Linux VMs, highlighting any required changes or limitations.
Review the documentation for opportunities to mention Linux support alongside Windows, rather than only referencing Windows features.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. It assumes the use of Visual Studio Code and the Azurite storage emulator, both of which are cross-platform but have stronger adoption and easier setup on Windows. The instructions for starting Azurite and running the function app rely on VS Code's command palette and do not provide explicit CLI alternatives for Linux/macOS users. There are no explicit Linux/macOS shell commands or terminal instructions, and no mention of platform-specific differences or troubleshooting for non-Windows environments. The documentation also does not mention or link to Linux-native tools or workflows, such as using the Azure CLI directly in bash/zsh, or running Azurite from the command line outside VS Code.

Recommendations:

Add explicit instructions for starting Azurite from the command line (e.g., `npx azurite` or `azurite` if installed globally), and clarify that it works on Linux/macOS as well as Windows.
Provide alternative instructions for running and debugging the function app using the Azure Functions Core Tools CLI (`func start`) for users who may not use VS Code or prefer terminal workflows.
Include notes or links about installing prerequisites (such as .NET Core, Node.js, Python, Java) on Linux/macOS, not just Windows.
Explicitly mention that all tools and steps are cross-platform, and call out any platform-specific caveats or troubleshooting steps.
Where possible, provide bash/zsh shell command equivalents alongside any PowerShell or Windows-centric instructions.
Consider adding a 'Platform differences' or 'Linux/macOS notes' section to address any subtle differences in setup or usage.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a strong Windows/PowerShell bias. All code samples, explanations, and tool references are exclusively for Windows PowerShell and related cmdlets. There is no mention of Linux, Bash, or cross-platform scripting, nor are there examples or guidance for users running Azure Automation from non-Windows environments. The documentation assumes the reader is using PowerShell and Windows-centric tools, and Linux or cross-platform users are not addressed.

Recommendations:

Add equivalent examples for Python runbooks, which are supported in Azure Automation, especially in sections discussing output and message streams.
Include information and examples for retrieving runbook output and messages using Azure CLI (az command), which is cross-platform and widely used on Linux.
Clarify which features and cmdlets are available or behave differently in Linux Hybrid Runbook Workers or in cross-platform environments.
Where PowerShell preference variables or cmdlets are discussed, note their applicability (or lack thereof) in Python or other supported runbook types.
Provide links to documentation or guides for managing Azure Automation from Linux environments, and mention any limitations or differences.
Rephrase sections that refer to 'Windows PowerShell' to 'PowerShell', and clarify when instructions apply to Windows-only versus cross-platform PowerShell Core.
Explicitly state if certain features (such as graphical runbooks or specific cmdlets) are only available on Windows, and suggest alternatives for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exhibits a Windows bias, primarily through a heavy emphasis on PowerShell-based automation, repeated references to Windows-centric tools and scenarios (e.g., Active Directory, SQL Server, registry changes), and by mentioning Windows/PowerShell approaches before Linux or cross-platform alternatives. While Linux is mentioned in passing (e.g., 'Linux and Windows support' in Automanage), there is a lack of Linux-specific examples, tools, or guidance, and the documentation assumes familiarity with Windows administration patterns.

Recommendations:

Provide Linux-specific examples and scenarios alongside Windows/PowerShell ones, such as using Bash scripts, Linux configuration management (e.g., Ansible, Chef, or native Azure DSC for Linux), and Linux-based monitoring.
Explicitly mention and demonstrate how Azure Automation and related services can be used with Linux VMs, including common Linux administrative tasks (e.g., package management, log rotation, cron jobs).
Balance references to PowerShell with equivalent Python or Bash scripting examples, and clarify cross-platform capabilities where applicable.
Include Linux-native tools and patterns (e.g., systemd, journald, apt/yum/zypper) in automation scenarios.
Highlight any differences or additional steps required for Linux environments, especially in areas like update management, configuration drift, and hybrid automation.
Ensure that tables and scenario descriptions do not assume Windows as the default, and use neutral or inclusive language (e.g., 'servers' instead of 'Windows servers').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation generally aims for cross-platform coverage, but there are subtle Windows biases. In several places, Windows-specific tools, settings, or patterns are mentioned before Linux equivalents, or are given more detailed explanations. Some settings and examples (such as environment variable delimiters, file paths, and PowerShell-specific settings) are Windows-centric or prioritize Windows terminology. PowerShell and Windows-specific configuration options are described in more detail than their Linux or cross-platform counterparts. In a few cases, Windows-only settings are called out, but Linux-only settings are less emphasized.

Recommendations:

Ensure that all examples and explanations are provided for both Windows and Linux, with equal detail and prominence.
When describing environment variable delimiters or file paths, always show both Windows and Linux syntax side by side.
For settings that are platform-specific (e.g., WEBSITE_NODE_DEFAULT_VERSION for Windows), provide a corresponding note or section for Linux, even if just to state the equivalent or that it is not applicable.
Avoid prioritizing Windows terminology or tools (such as Azure PowerShell) over cross-platform alternatives (like Azure CLI); mention both together or prefer cross-platform tools.
Where PowerShell-specific settings are described in detail, ensure similar coverage for Bash or other Linux-relevant scripting environments if applicable.
Review the order in which OS-specific information is presented, and alternate or balance Windows and Linux references to avoid implicit prioritization.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates Windows bias by prioritizing .NET Framework (a Windows-only technology) and WCF (Windows Communication Foundation) in both the API table and the detailed explanations. There are no explicit Linux or cross-platform command-line examples, nor is there mention of Linux-specific tools or patterns. The .NET Standard library is described as cross-platform, but examples and references (such as ASP.NET Core) are still Microsoft-centric. No Linux-native frameworks or usage patterns are discussed.

Recommendations:

Add explicit Linux usage examples, such as running .NET Standard clients on Linux distributions.
Include command-line examples for both Windows (PowerShell) and Linux (bash) environments.
Mention and demonstrate integration with Linux-native frameworks (e.g., Kestrel, systemd) where applicable.
Clarify cross-platform compatibility in the API table, highlighting which libraries work natively on Linux.
Provide parity in documentation for Linux and macOS users, not just Windows.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page focuses on .NET and Microsoft-specific tooling (such as WCF and .NET SDKs) for Azure Relay authentication and authorization, with sample code and references primarily targeting Windows-centric technologies. There are no explicit Linux or cross-platform command-line examples (e.g., Bash, curl, or Azure CLI usage), and the sample links are all for .NET, Java, and JavaScript, but not for scripting or tooling commonly used on Linux. There is also a lack of guidance for generating SAS tokens or managing keys using Linux-native tools.

Recommendations:

Add explicit Linux and cross-platform examples for generating SAS tokens (e.g., using Bash, curl, or OpenSSL).
Include Azure CLI commands for managing authorization rules and keys, demonstrating usage on both Windows and Linux shells.
Provide sample scripts or code snippets in Python or Bash for authenticating and connecting to Azure Relay from Linux environments.
Mention and link to relevant Linux tools or SDKs (such as Azure CLI, Python SDK, or REST API usage) alongside .NET and Windows-specific tools.
Ensure that any screenshots or UI instructions clarify that the steps are platform-agnostic or provide alternatives for Linux users where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), omitting any mention of Linux-compatible development tools or workflows. All instructions assume the use of Visual Studio, with no guidance for Linux users (e.g., using VS Code, .NET CLI, or Mono). There are no Linux-specific examples or notes on cross-platform compatibility.

Recommendations:

Include instructions for setting up and running the .NET applications using the .NET CLI (dotnet new, dotnet run), which works on Linux, macOS, and Windows.
Mention and provide examples for using cross-platform editors like Visual Studio Code.
Add a note clarifying that the sample code is compatible with .NET Core/.NET 5+ and can be run on Linux and macOS, not just Windows.
Provide terminal/command-line instructions for Linux and macOS users alongside Visual Studio steps.
Explicitly state any Windows-only requirements, or confirm that there are none, to reassure non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively covers mounting SMB volumes on Windows virtual machines, providing only Windows-specific instructions and screenshots. There are no examples or instructions for mounting SMB volumes on Linux clients, and Windows tools and workflows are mentioned without Linux equivalents.

Recommendations:

Add a section detailing how to mount SMB volumes on Linux clients, including command-line examples (e.g., using the 'mount' command or 'cifs-utils').
Provide Linux-specific screenshots or terminal output where appropriate.
Ensure that both Windows and Linux instructions are presented with equal prominence, or provide a platform selection tab.
Mention relevant Linux tools and packages (such as cifs-utils) alongside Windows tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias. While the main focus is on Azure CLI (which is cross-platform), the only alternative method mentioned is Azure PowerShell, with a direct link to a PowerShell-specific guide. There are no references to Linux- or macOS-specific shell environments, nor are there any examples or notes about running the commands in Bash or other non-Windows shells. Output redirection (e.g., '>restoreconfig.json') is shown in a way that works in both Bash and PowerShell, but there is no explicit mention of Linux or macOS compatibility, nor are there troubleshooting tips or environment notes for those platforms. The documentation does not mention Linux tools or patterns, and the only alternative to CLI is a Windows-centric tool (PowerShell).

Recommendations:

Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide any platform-specific notes if necessary.
When mentioning PowerShell as an alternative, also mention Bash or shell scripting as a valid approach for Linux/macOS users, or clarify that the CLI commands are cross-platform.
Include a section or note about running the commands in Bash or other Linux shells, especially if there are differences in variable syntax or output redirection.
If possible, provide example commands or troubleshooting tips for Linux/macOS users (e.g., handling environment variables, file permissions, or CLI installation).
Avoid implying that PowerShell is the only or primary alternative to Azure CLI by either omitting the PowerShell reference or balancing it with Linux/macOS alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows environments. All supported platforms are Windows Server versions, and all setup, configuration, and troubleshooting steps assume a Windows OS. Only Windows tools (e.g., PSExec, regedit, Windows certificate manager) and Windows-specific commands (cmd, PowerShell modules) are referenced. There are no Linux examples, nor is Linux support mentioned or considered.

Recommendations:

Clearly state if Linux is unsupported, or add a section on Linux support if available.
If Linux support is possible, provide equivalent instructions for Linux environments (e.g., mounting NFS shares, managing certificates, using Azure CLI instead of PowerShell).
Mention Linux tools and patterns where relevant, and provide parallel examples for both Windows and Linux.
Avoid assuming the use of Windows-only utilities (like PSExec, regedit) without alternatives or explanations for non-Windows users.
If the feature is truly Windows-only, make this explicit early in the documentation to set user expectations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation for Microsoft Azure Backup Server v3 is heavily oriented towards Windows environments. All examples, tools, and instructions reference Windows-only components such as SQL Server Management Studio (SSMS), SQL Server Reporting Services (SSRS), and Windows file paths. There are no examples or mentions of Linux support, tools, or equivalent procedures, and all troubleshooting steps assume a Windows environment.

Recommendations:

Clearly state at the beginning of the documentation whether MABS is Windows-only or if Linux workloads/agents are supported.
If Linux workloads are supported, provide parallel troubleshooting steps and examples for Linux environments, including command-line instructions and relevant tools.
Mention Linux equivalents (if any) for backup/restore operations, database management, and reporting, or clarify their absence.
Avoid using only Windows file paths and tools in examples; include Linux paths and commands where applicable.
If MABS is not supported on Linux, explicitly state this to set user expectations and avoid 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 supported platforms are Windows-only, and there is no mention of Linux support or examples. All instructions, prerequisites, and troubleshooting steps are written exclusively for Windows, using Windows-specific tools (PowerShell, MARS Agent, Windows command prompt, registry editor, Control Panel, etc.). There are no Linux equivalents or alternative workflows provided, nor is it clarified whether Linux is unsupported or simply omitted.

Recommendations:

Explicitly state whether Linux is supported or unsupported for this workflow. If unsupported, clarify this early in the documentation.
If Linux support is possible, provide equivalent instructions and examples for Linux environments, including installation, configuration, and troubleshooting steps.
Include Linux command-line examples (e.g., Bash, az CLI) alongside PowerShell commands where applicable.
Reference Linux tools and patterns (e.g., mounting NFS shares on Linux, using Linux backup agents) if available.
Ensure screenshots and UI references are not exclusively Windows-centric if cross-platform support is intended.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows environments, with all examples, supported operating systems, and deployment scenarios centered on Windows Server and related Microsoft technologies. There is no mention of Linux support, examples, or parity, and all tools and workflows assume a Windows-based infrastructure.

Recommendations:

Explicitly state if Linux is unsupported, or clarify any Linux limitations, to avoid ambiguity.
If partial Linux support exists (e.g., for agent-based backup or file-level backup), document the scenarios, requirements, and limitations.
Provide equivalent Linux examples or workflows where possible, such as agent installation, backup, and restore procedures for Linux VMs.
Include a section or matrix row for Linux-based workloads, even if only to state 'not supported', to make the documentation more inclusive and clear.
Mention any future plans or alternatives for Linux users, such as integration with other Azure Backup solutions that support Linux.

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 (Fiddler, IIS) for troubleshooting and configuration, without mentioning Linux equivalents or providing cross-platform guidance. All server-side configuration examples are for Microsoft IIS, and there are no instructions for common Linux web servers (e.g., Apache, Nginx).

Recommendations:

Include Linux-friendly tools for inspecting HTTP headers, such as curl, wget, or command-line examples using these tools.
Provide troubleshooting steps and configuration guidance for popular Linux web servers (e.g., Apache, Nginx), including how to handle compression and proxy headers.
Mention cross-platform or browser-based tools (such as browser developer tools) more prominently and provide example workflows.
When referencing server configuration, present both Windows (IIS) and Linux (Apache/Nginx) instructions in parallel, or link to relevant documentation for each platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias, particularly in the 'Install Vertica ODBC driver for the version 2.0' section, where only Windows installation steps and screenshots are provided. There are no instructions or examples for installing the ODBC driver on Linux or macOS, despite Vertica and self-hosted integration runtimes being commonly deployed on Linux servers. The documentation also references Windows-specific tools (e.g., ODBC Data Source Administrator, Start menu) without mentioning Linux equivalents.

Recommendations:

Add parallel instructions and screenshots for installing the Vertica ODBC driver on Linux (and optionally macOS), including command-line steps (e.g., using rpm, deb, or tar.gz packages).
Mention and provide examples for configuring ODBC on Linux, such as editing odbc.ini and odbcinst.ini files.
Reference Linux tools and locations (e.g., using isql for testing, typical driver install paths) alongside Windows tools.
Clearly indicate in each section whether the instructions apply to Windows, Linux, or both, and provide tabs or callouts for OS-specific steps.
Ensure all critical setup and troubleshooting steps are covered for both Windows and Linux environments to support cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exhibits a Windows bias by exclusively referencing Windows-specific tools (SQL Server Management Studio) for database access and omitting any mention of Linux-compatible alternatives. There are no examples or instructions for Linux users to connect to Azure SQL Database (e.g., via Azure Data Studio, sqlcmd, or other cross-platform tools). The only client tool mentioned is SQL Server Management Studio, which is Windows-only, and it is introduced without alternatives or parity for Linux/macOS users.

Recommendations:

Add instructions and examples for connecting to Azure SQL Database using cross-platform tools such as Azure Data Studio or the sqlcmd command-line utility.
Explicitly mention that SQL Server Management Studio is a Windows-only tool and provide Linux/macOS alternatives in the same section.
Wherever database queries are to be run, provide command-line examples (e.g., using sqlcmd) in addition to GUI-based instructions.
Review screenshots and UI steps to ensure they are not exclusively based on Windows-only tools, or supplement them with cross-platform tool screenshots where possible.
Consider a 'Platform note' at the start of the tutorial to guide Linux/macOS users to appropriate tools and steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page exclusively references Windows Server OS families, provides only Azure PowerShell scripts for discovery, and recommends Windows-centric tools (Visual Studio, .NET Framework). There are no examples, guidance, or references for Linux-based guest OSes or management tools, and the migration recommendations are entirely Windows-focused.

Recommendations:

If Linux-based guest OSes are supported in Azure Cloud Services (classic or extended), include equivalent guidance and examples for identifying and migrating Linux workloads.
Provide CLI (az cli) or cross-platform scripting examples (e.g., Bash) in addition to PowerShell, or clarify if only PowerShell is supported.
Mention Linux guest OS families, if applicable, and provide parity in recommendations for migration and support.
If the service is Windows-only, explicitly state this at the beginning of the documentation to set expectations for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides examples for ARM templates, PowerShell, and the .NET SDK (C#), but does not include any Linux-native CLI examples (such as Azure CLI/bash), nor does it mention Linux-specific tools or workflows. The PowerShell example is prominent, and there is no parity for Linux users who may prefer Bash or cross-platform scripting tools.

Recommendations:

Add an Azure CLI example (az cloud-service ...) demonstrating how to set allowModelOverride, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that the PowerShell example can be run on PowerShell Core on Linux, if applicable.
Consider including Bash scripting examples or references for Linux users.
Ensure that SDK examples include at least one language commonly used on Linux (e.g., Python or Java), not just C#.
Review the documentation for any terminology or tool references that assume a Windows environment and provide Linux equivalents where possible.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a bias towards Windows by exclusively recommending Microsoft Excel (2016/2013) and Power BI—both Windows-centric tools—for extracting the table index from an HTML page. There are no Linux or cross-platform alternatives mentioned, nor are command-line or open-source tools suggested. The only workflow for a key step (getting the table index) is described using Windows GUI applications, leaving Linux users without guidance.

Recommendations:

Provide alternative instructions for extracting the table index using cross-platform or Linux tools, such as Python scripts (e.g., using BeautifulSoup or pandas), curl, or command-line utilities.
Include example commands or scripts that work on Linux/macOS as well as Windows.
Mention open-source tools (e.g., LibreOffice Calc, web scraping libraries) that can perform similar tasks to Excel/Power Query.
Reorder or parallelize the instructions so that Windows and Linux/macOS approaches are presented with equal prominence.
Explicitly state that the process can be completed on non-Windows platforms, and provide links or references to relevant resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits Windows bias by referencing Windows versions as prerequisites for the self-hosted integration runtime, without mentioning Linux support or providing Linux-specific guidance. There are no Linux or cross-platform examples for key steps such as generating private keys, and the documentation does not clarify whether the integration runtime or connector can be run on Linux. All example commands and operational notes are either Windows-centric or omit Linux entirely.

Recommendations:

Explicitly state whether the self-hosted integration runtime and Xero connector are supported on Linux, and if so, provide Linux prerequisites alongside Windows.
For steps involving key generation (e.g., generating privatekey.pem with openssl), provide example commands for both Windows (using Git Bash or WSL) and Linux environments.
If certain features are Windows-only, clearly label them as such and, where possible, provide Linux alternatives or workarounds.
Include screenshots or instructions for Linux-based Azure Data Factory/Synapse deployments if supported.
Review all operational notes and ensure parity by adding Linux-specific instructions or clarifications where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell-specific commands (e.g., Get-AzKeyVault), linking to PowerShell-based recovery instructions, and omitting Linux or cross-platform CLI alternatives in troubleshooting and recovery steps. The only command-line tool mentioned is PowerShell, and there are no Bash, Azure CLI, or Linux-native instructions or examples. This may hinder Linux or cross-platform users from following the documentation effectively.

Recommendations:

For every PowerShell example or reference, provide an equivalent Azure CLI (az) command, which is cross-platform and works on Linux, macOS, and Windows.
In troubleshooting sections, link to both PowerShell and Azure CLI documentation for tasks like key vault recovery and URI retrieval.
Avoid referencing only Windows tools (e.g., Get-AzKeyVault) in command-line contexts; always include or prefer cross-platform alternatives.
Explicitly state that the Azure portal and Azure CLI are supported on all major operating systems, and provide links to installation guides for Linux/macOS users.
Where screenshots or UI steps are shown, clarify that the Azure portal experience is the same across platforms, and mention any OS-specific caveats if they exist.

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 use PowerShell, and the installation and configuration steps for the self-hosted integration runtime explicitly require a Windows machine. There are no instructions or examples for Linux or macOS users, and Windows-specific tools (such as SQL Server Management Studio and Notepad) are referenced without alternatives. The documentation assumes the user is operating on Windows from start to finish.

Recommendations:

Provide equivalent instructions and examples for Linux and macOS users, including using Azure CLI or Bash scripts instead of only PowerShell.
Mention and demonstrate cross-platform tools (e.g., Azure Data Studio for SQL Server management, VS Code, or nano/vim for editing JSON files) alongside Windows-only tools.
Clarify platform requirements early in the prerequisites, and if the self-hosted integration runtime is Windows-only, explicitly state this and suggest alternatives (such as using Azure-hosted integration runtime or Docker-based solutions) for Linux users.
Where possible, include links or references to Linux/macOS installation guides for required tools (e.g., Azure CLI, Data Factory integration runtime if available, SQL Server clients).
Structure the documentation so that platform-agnostic steps come first, and platform-specific instructions are clearly separated, with Linux/macOS sections given equal prominence.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references Windows tools and workflows, such as the use of 'dmgcmd.exe' and the Configuration Manager UI, with no mention of Linux equivalents or support. There are no Linux command-line examples or references to Linux-based installation or troubleshooting, implying the tool is Windows-only or that Linux users are not considered.

Recommendations:

Explicitly state whether the diagnostic tool is Windows-only or if Linux is supported.
If Linux is supported, provide equivalent Linux command-line instructions and examples (e.g., using a .sh script or Linux binary).
Mention Linux-specific troubleshooting steps or UI, if available.
If Linux is not supported, clarify this early in the documentation to set user expectations.
Consider adding a section on cross-platform support and any differences in usage or output between Windows and Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only Azure PowerShell examples for resource cleanup, with no mention of equivalent commands for Linux users (such as Azure CLI or Bash). The use of PowerShell-specific syntax and the lack of cross-platform command options indicate a Windows bias. There is also no reference to Linux or macOS tooling or workflows.

Recommendations:

Include Azure CLI (az) command examples for all resource management steps, especially for cleanup, alongside PowerShell.
Explicitly mention that the steps can be performed on any OS, and provide Bash or shell script equivalents where relevant.
Add a note or section for Linux/macOS users, highlighting any differences or confirming parity.
Where PowerShell is used, clarify that Azure CLI is also supported and link to relevant CLI documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation presents a clear Windows-first bias: the SMB/Windows workflow is described first and in greater detail, with explicit step-by-step instructions, screenshots, and use of Windows-specific tools (e.g., 'net use', File Explorer, Windows + R). The Linux/NFS section is shorter, less detailed, and lacks parity in terms of troubleshooting, verification, and user experience guidance. There is also a reliance on Windows command-line tools and GUI patterns, with Linux equivalents either missing or less emphasized.

Recommendations:

Alternate the order of Windows and Linux instructions, or present them in parallel tabs to avoid always putting Windows first.
Provide equally detailed, step-by-step instructions for Linux/NFS workflows, including screenshots of typical Linux file managers (e.g., Nautilus, Dolphin) and terminal outputs.
Include Linux command-line equivalents for all Windows commands (e.g., show how to use 'mount', 'df', 'ls', etc., to verify connection and file transfer).
Add troubleshooting and verification steps specific to Linux, such as checking mount status, permissions, and log files.
Avoid referencing Windows GUI patterns (e.g., 'Windows + R', File Explorer) without Linux equivalents; instead, show how to access shares via Linux file managers or command line.
Ensure that all error scenarios and their resolutions are covered for both platforms, not just Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits Windows bias by referencing Windows-specific tools and patterns, such as 'Microsoft RSA/Schannel Cryptographic Provider' and explicitly mentioning Windows PowerShell as the management interface for certain operations. There are no examples or references to Linux tools, commands, or equivalent workflows, and Linux is not mentioned as a supported or alternative environment for certificate troubleshooting.

Recommendations:

Include Linux-based examples and troubleshooting steps, such as using OpenSSL for certificate inspection and management.
Mention Linux-compatible cryptographic providers or clarify if only Windows providers are supported, and explain any platform limitations.
Provide equivalent command-line instructions for Linux (e.g., bash, OpenSSL) alongside PowerShell examples.
Explicitly state platform support and any differences in workflow between Windows and Linux environments.
Avoid assuming PowerShell is the only management interface; reference cross-platform tools where possible.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows SMB paths, Windows-style username formats, and Windows file management patterns (e.g., right-clicking folders, using the Security tab). There is no mention of Linux or Unix equivalents, nor are there examples or instructions for Linux users. The note about non-Windows NAS devices not being officially supported further deprioritizes Linux environments.

Recommendations:

Include explicit instructions and examples for Linux environments, such as how to specify SMB paths and credentials from Linux systems.
Provide guidance for managing file permissions and access on Linux (e.g., using chmod, setfacl, or other Linux tools) alongside Windows instructions.
Clarify the level of support for Linux/Unix NAS devices and, if possible, offer troubleshooting steps or workarounds for Linux users.
Avoid Windows-centric language (e.g., 'Right-click the folder, select Properties, then Security tab') or provide parallel Linux instructions (e.g., 'Use ls -l or getfacl to check permissions').
If the service is truly Windows-only, state this clearly at the beginning to set expectations for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by exclusively referencing Windows-centric update mechanisms (such as Windows Server Update Services and Microsoft Update Catalog), using .exe update packages, and omitting any mention of Linux-based update tools or workflows. There are no examples or instructions for Linux environments, and all tooling and file formats are Windows-specific.

Recommendations:

Include instructions or notes for Linux-based environments, such as how to download and apply updates using Linux tools (e.g., wget/curl, tar, shell scripts).
If the device supports Linux-based management, provide examples for Linux command-line interfaces or update workflows.
Mention whether the .exe update packages can be applied from non-Windows systems, or provide alternative package formats (e.g., .tar.gz) if possible.
Clarify if the update process is only supported from Windows hosts, and if so, explicitly state this limitation.
Reference cross-platform update mechanisms or APIs (such as REST endpoints) if available, and provide example usage from both Windows and Linux clients.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by referencing PowerShell interfaces and Windows-centric troubleshooting steps without providing equivalent Linux examples or mentioning Linux tools. The 'Next steps' section specifically points to a PowerShell-based interface for debugging Kubernetes issues, and there is no mention of Linux command-line or troubleshooting approaches.

Recommendations:

Include Linux-based troubleshooting steps and examples alongside or before Windows/PowerShell instructions.
Reference Linux tools (such as bash, journalctl, systemctl, docker, kubectl) where appropriate.
Provide parity in documentation by ensuring that Linux users can follow the same troubleshooting workflows.
Explicitly state platform applicability for each troubleshooting step or tool.
Add links or sections for Linux-specific troubleshooting guides if the device supports Linux-based management.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows/Powershell bias by explicitly referencing Azure PowerShell for enabling DDoS IP Protection, while not mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI, Bash, or ARM templates). There are no Linux/Unix-specific examples or parity in tooling guidance, and the only command-line example referenced is PowerShell.

Recommendations:

Provide parallel instructions and quickstarts for enabling DDoS IP Protection using Azure CLI (az), which is cross-platform and commonly used on Linux.
When referencing PowerShell, always mention or link to equivalent Azure CLI or REST API documentation.
Avoid implying that PowerShell is the primary or only supported method for configuration; instead, present both Windows and Linux-friendly options side by side.
Include explicit examples or links for Linux/macOS users, especially in sections that currently reference only PowerShell.
Consider a 'Choose your platform' approach in quickstart and configuration sections, allowing users to select their preferred environment (Azure Portal, PowerShell, Azure CLI, ARM/Bicep, etc.).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows instructions and tools are often presented first, with detailed PowerShell/Command Prompt examples and screenshots. The Windows toolset is referenced repeatedly and sometimes more prominently than Linux equivalents. While Linux instructions are present and fairly detailed, some sections (e.g., initial tool download, troubleshooting, and validation) default to Windows-first language or lack parity in example depth. There are also more references to Windows-specific requirements and tools, and some Linux steps require third-party utilities not managed by Microsoft, which may create a perception of less official support.

Recommendations:

Alternate the order of Windows and Linux instructions or use parallel tabbed layouts to present both platforms equally.
Ensure that all examples, screenshots, and troubleshooting steps are provided for both Windows and Linux clients with equal detail.
Where possible, provide official Microsoft-supported tools/utilities for Linux, or at least clarify support levels and provide direct links to trusted third-party resources.
Avoid language that implies Windows is the default or primary platform (e.g., 'To unlock the disks, open Command Prompt...' before mentioning Linux).
Add Linux-specific troubleshooting and validation sections to match the depth of Windows coverage.
Where third-party Linux tools are required, provide clear installation and usage instructions, and consider contributing to or supporting these tools to improve user confidence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively mentioning the Windows App as the method for connecting to a dev box, without providing equivalent instructions or references for Linux (or macOS) users. There are no examples or guidance for connecting from Linux devices, and Windows tooling is presented as the default and only option.

Recommendations:

Add explicit instructions for connecting to a dev box from Linux (and macOS) devices, such as using open-source RDP clients (e.g., Remmina, FreeRDP, rdesktop) or web-based access if available.
Mention and provide download links for cross-platform clients alongside the Windows App, making it clear that non-Windows users are supported.
Include example connection steps or screenshots for Linux users to ensure parity and inclusivity.
Avoid language that implies Windows is the only or primary supported platform; instead, clarify support for multiple operating systems where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation exhibits a strong Windows bias. All virtual machine examples use Windows Server 2019 Datacenter, and the only automation example for configuring IIS uses Azure PowerShell with Windows-specific commands. There are no Linux VM deployment or configuration examples, nor any mention of Linux tools or shell commands. The test and usage scenarios (RDP, PowerShell, IIS) are all Windows-centric, with no Linux alternatives provided.

Recommendations:

Provide parallel Linux examples for VM creation, such as deploying Ubuntu or other Linux distributions.
Include automation examples using Bash/Cloud Shell for Linux VMs (e.g., using Azure CLI and cloud-init for installing Apache or Nginx).
Demonstrate connectivity tests using SSH and curl/wget from a Linux VM, in addition to RDP and browser tests.
Mention both Windows and Linux options when describing VM creation steps and testing scenarios.
When showing PowerShell scripts, also provide equivalent Azure CLI/Bash scripts for Linux users.

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 Bash, Azure CLI, or Linux-native equivalents. Additionally, network validation and failover testing examples use Windows tools (tracert) and Windows-style command prompts, with no mention of Linux alternatives (e.g., traceroute). This prioritizes Windows environments and omits guidance for users on Linux or cross-platform systems.

Recommendations:

Provide Azure CLI (az) command equivalents for all PowerShell examples, especially for route validation and ExpressRoute circuit management.
Include Linux-native command examples (e.g., traceroute instead of tracert) alongside Windows examples when demonstrating network validation from on-premises servers.
Explicitly mention that the procedures can be performed from both Windows and Linux environments, and provide guidance or links for Linux users.
Where screenshots or sample outputs are shown from Windows terminals, consider adding corresponding Linux/Bash terminal examples.
Review the documentation for any other Windows-centric terminology or assumptions, and ensure Linux parity throughout.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides certificate generation instructions and examples exclusively using Windows PowerShell, with explicit mention of Windows and no equivalent Linux/macOS commands or guidance. The only installation note for the step CLI is 'Consider installing manually for Windows,' with no mention of Linux or macOS. This creates a Windows-first impression and omits Linux parity for a common cross-platform task.

Recommendations:

Add Linux and macOS examples for generating certificates using the step CLI, including equivalent bash/zsh commands.
Provide installation instructions or a link for step CLI on Linux and macOS, not just Windows.
Avoid specifying 'in Windows PowerShell' unless also providing a Linux/macOS shell alternative.
Where possible, use cross-platform command syntax or clearly separate instructions for each OS.
Review screenshots and UI references to ensure they are not Windows-specific unless necessary.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides both Linux and Windows (specifically IoT Edge for Linux on Windows/EFLOW) instructions, but Windows/PowerShell-specific tooling and workflows are heavily emphasized in the EFLOW sections. PowerShell cmdlets (e.g., Copy-EflowVMFile, Connect-EflowVm, Invoke-EflowVmCommand) are used exclusively for file transfer and port management on EFLOW, with no mention of alternative Linux-native or cross-platform methods. The EFLOW (Windows) instructions are more detailed in terms of Windows-specific tooling, and PowerShell is presented as the primary interface for EFLOW management, which may disadvantage users more familiar with Linux-native workflows. The Linux instructions are present and functional, but the Windows/PowerShell approach is more prominent and sometimes appears first or with more detailed steps.

Recommendations:

For EFLOW, provide alternative instructions using standard SSH/SCP/SFTP for file transfer and remote command execution, not just PowerShell cmdlets, to support users on non-Windows platforms or those preferring Linux-native tools.
Where PowerShell is used for port management (e.g., opening ports with Invoke-EflowVmCommand), offer equivalent instructions for users who may access EFLOW via SSH or other means.
Clarify that PowerShell cmdlets are one option and that standard Linux tools can also be used within the EFLOW VM, making the documentation more inclusive for Linux users.
Consider presenting Linux-native instructions first or in parallel, rather than defaulting to Windows/PowerShell-centric workflows for EFLOW.
Explicitly mention cross-platform alternatives and note any limitations or prerequisites for each approach.

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 examples and automation scripts exclusively in PowerShell syntax. There are no Bash or Linux shell equivalents, and the scripting patterns (e.g., function definitions, parameter handling) are tailored for Windows/PowerShell users. This may hinder accessibility for Linux or macOS administrators, who are more likely to use Bash or other Unix shells.

Recommendations:

Provide equivalent Bash shell scripts for all PowerShell examples, especially for the main cluster creation workflow.
When showing command-line examples (such as az CLI usage), present both PowerShell and Bash syntax side-by-side or clearly indicate differences.
Avoid using PowerShell-specific constructs (like function definitions and parameter blocks) as the only automation example; instead, offer cross-platform alternatives.
Explicitly mention that the Azure CLI is cross-platform and can be used from Bash, PowerShell, or CMD, and link to relevant installation or usage guides for Linux/macOS.
Add a note or section for Linux/macOS users, clarifying any differences or additional steps required.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. Windows and PowerShell are mentioned before Linux/Bash in several places, and Windows-specific tools and paths are referenced. Although Bash examples are provided throughout, the prerequisites and instructions often prioritize Windows environments (e.g., 'Bash on Ubuntu on Windows 10', PowerShell, Windows paths for jq). There are also notes about how to adapt Bash examples for Windows Command Prompt or PowerShell, but not vice versa. The use of Windows PowerShell and references to Windows Subsystem for Linux (WSL) further reinforce the Windows-centric approach.

Recommendations:

List Linux/Bash as the primary or first example in prerequisites and code blocks, especially since HDInsight clusters are Linux-based.
Provide clear, standalone instructions for native Linux and macOS users, not just WSL or Bash on Windows.
Avoid referencing Windows-specific paths (e.g., C:\HD\jq\jq-win64) in Bash/jq examples; instead, use generic or Linux-style paths.
When mentioning PowerShell or Windows tools, ensure equivalent Linux-native alternatives are described with equal prominence.
Clarify that all Bash examples work natively on Linux/macOS, not just in WSL.
If referencing Azure PowerShell cmdlets, also mention equivalent Azure CLI commands for Linux users where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation consistently presents Windows instructions and examples before Linux ones, uses PowerShell-specific scripts and commands heavily, and references Windows-specific tools (such as vcpkg and PowerShell cmdlets) without always providing equivalent Linux context or alternatives. While Linux instructions are present and generally complete, the overall structure and emphasis favor Windows users.

Recommendations:

Alternate the order of Windows and Linux sections throughout the documentation, or present both platforms side-by-side where feasible.
Where Windows-specific tools (like vcpkg or PowerShell cmdlets) are mentioned, provide equivalent Linux package manager commands (e.g., apt, yum) and bash alternatives.
Ensure that all prerequisite steps (such as installing OpenSSL) are equally detailed for Linux, including common installation commands for major distributions.
Where possible, use cross-platform language and avoid assuming PowerShell as the default shell. Highlight bash and POSIX-compliant alternatives.
Consider providing a summary table of commands for both platforms at the end of each major section for quick reference.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by focusing on RDP access to Windows Server VMs, referencing PowerShell for resource cleanup, and omitting Linux VM or SSH examples. The only command-line example uses Azure PowerShell, and the workflow assumes Windows-centric tools and patterns.

Recommendations:

Include examples for deploying and accessing Linux VMs (e.g., SSH access) alongside Windows examples.
Provide equivalent Azure CLI commands for resource management (such as deleting the resource group), not just Azure PowerShell.
Mention both RDP (for Windows) and SSH (for Linux) as possible ways to connect to backend servers.
Balance references to Windows and Linux tools and workflows throughout the documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits some Windows bias, primarily through the explicit mention of Azure PowerShell and Windows PowerShell cmdlets as setup and customization methods, and by referencing 'HDInsight Windows PowerShell cmdlets' before or instead of Linux equivalents. There is also a reference to working from a Windows PC in the related content, but no equivalent for Linux or macOS. While the main focus is on the Azure portal (which is cross-platform), command-line examples and tooling references tend to favor Windows or do not provide parity for Linux users.

Recommendations:

Ensure that all command-line examples and tooling references include both Windows (PowerShell) and Linux (Bash/Azure CLI) equivalents, presented side by side or with equal prominence.
In sections mentioning 'HDInsight Windows PowerShell cmdlets', also mention and link to Azure CLI or Bash scripting options for Linux users.
Add a 'Work in Apache Hadoop on HDInsight from a Linux PC' or 'macOS' equivalent to the related content, similar to the Windows PC link.
Review all references to tools and setup methods to ensure Linux-first or at least equal treatment, especially in tables and lists.
Where script actions or automation are discussed, provide examples for both PowerShell and Bash.
Audit for any screenshots or instructions that are Windows-specific and provide Linux alternatives where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows, providing only Windows-specific instructions and PowerShell commands for creating a virtual switch, NAT, and DHCP server. There are no Linux equivalents or cross-platform guidance, despite the topic being related to 'IoT Edge for Linux on Windows'. All tooling and examples are Windows/PowerShell-centric, and Linux networking tools or commands are not mentioned at all.

Recommendations:

Add a section or parallel instructions for performing similar networking setup (virtual switch, NAT, DHCP) on Linux hosts using common Linux tools (e.g., ip, brctl, dnsmasq, systemd-networkd).
Clarify in the introduction that the instructions are Windows-only, and provide links or references for Linux users if applicable.
Where possible, provide conceptual parity by describing what each step accomplishes in platform-agnostic terms before showing Windows-specific commands.
If the product is only supported on Windows hosts, explicitly state this limitation and explain why Linux host instructions are not included.
Include a comparison table or FAQ addressing differences between Windows and Linux networking setup for IoT Edge scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows a mild Windows bias by mentioning Azure PowerShell and the Azure portal as primary tools for cluster configuration and scaling, with no explicit mention of Linux-native command-line tools or examples (such as Bash, SSH, or Azure CLI on Linux). The workflow examples and screenshots focus on the Azure portal and PowerShell, and there are no Linux shell or script examples provided for common tasks. While the article does mention that Tez is enabled by default on Linux-based clusters, it does not provide Linux-specific operational guidance or parity in tooling examples.

Recommendations:

Include explicit examples using Azure CLI commands in Bash or Linux shell for cluster creation and scaling, alongside or before PowerShell examples.
Add references or examples for managing HDInsight clusters from Linux environments, such as using SSH or Linux-native tools.
Balance the order of tool mentions (e.g., mention Azure CLI before or alongside PowerShell and the Azure portal).
Provide screenshots or walkthroughs for Linux-based workflows where applicable.
Clarify when instructions or features are specific to Windows or Linux, and ensure Linux users are not left out of operational guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows-first bias: Windows instructions and tools (such as Control Panel, Task Manager, and NVIDIA Control Panel) are described in detail with screenshots, while Linux instructions are referenced via links without in-page examples or screenshots. Windows validation steps are explicit, but Linux validation is only linked. There is also a lack of parity in tool mention and step-by-step guidance for Linux users.

Recommendations:

Provide in-page, step-by-step Linux instructions for driver installation and validation, not just external links.
Include screenshots of Linux tools (e.g., nvidia-smi output, relevant desktop environment GPU settings) analogous to the Windows screenshots.
Mention Linux tools (such as nvidia-smi, lshw, or system monitoring utilities) for GPU validation, similar to Task Manager and NVIDIA Control Panel for Windows.
Present Windows and Linux instructions in parallel sections, or at least alternate which OS is presented first in each section.
Explicitly state when steps are identical or different between Windows and Linux, to help users understand OS-specific nuances.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by presenting Windows instructions and references before Linux equivalents, omitting Linux-specific examples in several sections, and focusing on Windows tools (such as Control Panel and Task Manager) for validation steps. Linux instructions are often relegated to notes or links, rather than being presented as first-class, step-by-step guidance.

Recommendations:

Provide parallel, step-by-step Linux instructions alongside Windows instructions in all relevant sections, not just as notes or external links.
Include Linux-specific validation steps, such as using nvidia-smi or lshw, with screenshots where appropriate, similar to the Windows Task Manager and Control Panel examples.
Explicitly mention Linux support in all tables and descriptions, clarifying which VM sizes and drivers are supported on Linux.
Where Windows-only features or limitations exist (e.g., certain visualization GPU sizes), clearly state this early and provide Linux alternatives or workarounds if available.
Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or alternate which OS is presented first in each section.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing command-line examples specifically for PowerShell, referencing the use of PowerShell as the default shell, and omitting equivalent instructions for Linux or macOS environments. The instructions for installing and using the Azure CLI are explicitly tied to PowerShell, and there are no examples or notes for users on Linux or macOS platforms. Additionally, the documentation does not mention or show screenshots from non-Windows environments, reinforcing a Windows-centric approach.

Recommendations:

Provide parallel command-line examples for Linux/macOS shells (e.g., Bash) alongside PowerShell instructions.
Clarify that the Azure CLI can be used on Windows, Linux, and macOS, and provide installation and usage instructions for each platform.
Include notes or callouts for cross-platform compatibility, highlighting any differences in steps or commands between Windows and Linux/macOS.
Add screenshots or terminal snippets from non-Windows environments to demonstrate parity.
Avoid assuming PowerShell as the default shell; instead, refer to 'your terminal' or 'command prompt' and specify platform-specific instructions where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing command-line examples specifically for PowerShell, referencing PowerShell explicitly, and omitting equivalent instructions for Linux/macOS environments. The Az CLI installation and usage steps are described as being performed in PowerShell, with no mention of Bash or other shells. There are no Linux-specific screenshots, instructions, or clarifications, and the workflow assumes a Windows-centric user environment.

Recommendations:

Provide parallel command-line examples for both PowerShell (Windows) and Bash (Linux/macOS) when demonstrating Az CLI usage.
Clarify that Az CLI can be used on Windows, Linux, and macOS, and provide installation links or instructions for each platform.
Avoid referencing PowerShell exclusively; instead, use neutral language such as 'open your terminal' and specify both PowerShell and Bash where appropriate.
Include notes or sections for Linux/macOS users, especially where file paths, environment variables, or command syntax may differ.
Add screenshots or step-by-step instructions from Linux/macOS environments where relevant to ensure parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses Azure PowerShell cmdlets and PowerShell scripting syntax for all examples and instructions. There are no references to Azure CLI, Bash, or Linux-native tools, nor are there any examples or guidance for users on Linux or macOS platforms. The prerequisites and workflow assume the use of PowerShell, which is more familiar to Windows users, and do not mention alternative cross-platform tools or approaches.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside PowerShell examples throughout the documentation.
Explicitly mention that Azure CLI and Bash can be used in Azure Cloud Shell, and provide instructions for both environments.
Include a section or callouts for Linux/macOS users, highlighting any differences or additional steps required.
Where possible, use cross-platform language and tools first, or present them alongside Windows/PowerShell instructions.
Update the prerequisites to mention both Azure PowerShell and Azure CLI, with links to installation and usage guides for each.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. It references Microsoft PowerShell as the primary method for generating GUIDs and provides a PowerShell script as the first scripting example for obtaining an access token. While a cURL example is also provided, the ordering and explicit mention of PowerShell tools and commands suggest a Windows-first approach. There is no explicit Linux shell or cross-platform alternative for GUID generation, and the PowerShell script is presented before the cURL example.

Recommendations:

When suggesting GUID generation, provide both PowerShell (Windows) and Linux/macOS (e.g., `uuidgen` or `cat /proc/sys/kernel/random/uuid`) command examples, or mention cross-platform tools first.
Present scripting examples in parallel (PowerShell and cURL/bash) or lead with a cross-platform tool like cURL, to avoid the impression of Windows-first bias.
Explicitly mention that all steps and scripts are cross-platform where possible, and provide Linux/macOS equivalents for any Windows-specific instructions.
Where referencing online tools, clarify that they are platform-agnostic.
Consider including bash or Python script examples alongside PowerShell for parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows development, specifically targeting WPF (Windows Presentation Foundation) desktop applications and requiring Visual Studio 2019. There are no examples or guidance for Linux or cross-platform desktop development, nor are alternative tools or frameworks mentioned. All code and instructions assume a Windows environment, and there is no mention of Linux equivalents or how to adapt the process for non-Windows platforms.

Recommendations:

Provide parallel instructions and examples for cross-platform desktop frameworks such as .NET MAUI, Avalonia, or Electron, which can run on Linux.
Include guidance for setting up the development environment on Linux (e.g., using VS Code, JetBrains Rider, or the .NET CLI).
Offer Linux-specific steps for cloning the repository, building, and running the sample application using the .NET CLI.
Mention any platform-specific limitations or considerations for Azure AD B2C authentication in non-Windows environments.
If WPF is inherently Windows-only, clarify this early and provide links or references to cross-platform alternatives for developers targeting Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows by exclusively providing PowerShell scripts and referencing Microsoft PowerShell as the HTTP client for testing the Node.js app, without offering equivalent Linux/macOS command-line examples (such as curl or HTTPie). The only terminal-based example is PowerShell, and no mention is made of common cross-platform or Linux-native tools. This may hinder Linux/macOS users from following the testing steps directly.

Recommendations:

Provide equivalent Linux/macOS command-line examples using curl or HTTPie for making HTTP POST requests to the Node.js app, alongside the PowerShell example.
Mention cross-platform tools (curl, HTTPie, Postman) as alternatives to PowerShell for testing HTTP endpoints.
When referencing tools, avoid listing Microsoft/Windows tools first or exclusively; instead, present options for both Windows and Linux/macOS users.
Explicitly state that the instructions are platform-agnostic where possible, and clarify any steps that are specific to Windows or require adaptation for other operating systems.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exclusively uses PowerShell scripts and tasks for deploying Azure AD B2C custom policies, with no mention of Bash, shell, or cross-platform scripting alternatives. All code examples, instructions, and pipeline tasks are centered around PowerShell, which is traditionally associated with Windows environments. There is no guidance for Linux or macOS users, nor are there examples using platform-agnostic tools or scripts.

Recommendations:

Provide equivalent Bash or shell script examples for deploying policies, suitable for Linux/macOS agents.
Include instructions for running the deployment on non-Windows agents in Azure Pipelines.
Mention and demonstrate the use of cross-platform tools (e.g., Azure CLI, curl, or REST API calls via Bash) as alternatives to PowerShell.
Clarify any platform requirements or limitations for the provided scripts, and suggest how users on Linux/macOS can adapt the process.
When listing steps or tools, avoid assuming PowerShell as the default and present cross-platform options side-by-side.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows-first bias by referencing Windows file paths (e.g., D:\home\site\wwwroot) before Linux equivalents, focusing on Windows directory structures, and omitting explicit Linux/Bash command examples or Linux-specific instructions. The use of backslashes in paths and references to Windows-style directories are prevalent, while Linux paths are mentioned only in passing. There are no Linux-specific troubleshooting notes or parity in deployment instructions.

Recommendations:

Provide Linux-specific examples alongside Windows ones, including explicit Linux file paths (e.g., /home/site/wwwroot) and directory structures.
Include Bash or Linux shell command examples where appropriate, especially for manual deployment steps.
Ensure all path references are given in both Windows and Linux formats, not just as a parenthetical note.
Add troubleshooting notes relevant to Linux environments, such as file permission issues or differences in mounting behavior.
Review all instructions and ensure that Linux users are given equal clarity and guidance as Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows, specifically WPF desktop applications, with all code samples and guidance tailored to the Windows ecosystem. There are no Linux or cross-platform examples, and Windows-specific patterns (such as WindowInteropHelper and WPF APIs) are used exclusively. The documentation does not mention or provide alternatives for Linux or other platforms.

Recommendations:

Include equivalent examples for cross-platform desktop frameworks (such as .NET MAUI, Avalonia, or GTK#) that run on Linux.
Provide guidance or links for configuring Azure AD B2C authentication in Linux desktop applications.
Clarify in the introduction that the guidance is specific to WPF/Windows, and link to cross-platform or Linux-specific documentation if available.
When discussing redirect URIs and MSAL usage, note any platform-specific considerations for Linux or macOS.
If possible, provide PowerShell and Bash/terminal command equivalents for any setup or configuration steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias, primarily in the 'Run your SPA application' section, where only PowerShell commands are shown for running the app. There is no mention of Linux or macOS command-line equivalents, nor any guidance for non-Windows users. Earlier steps use generic 'command shell' language, but the explicit use of PowerShell syntax and lack of cross-platform notes may confuse or exclude Linux/macOS developers.

Recommendations:

Provide both Windows (PowerShell/cmd) and Linux/macOS (bash/sh) command examples, especially in the 'Run your SPA application' section.
Use cross-platform command syntax where possible (e.g., 'node index.js' instead of 'npm ./index.js', which is not standard).
Add notes clarifying that all steps can be performed on Linux/macOS, and specify any OS-specific considerations.
Avoid using PowerShell-specific syntax unless necessary, or always pair it with bash equivalents.
Explicitly mention that the instructions are cross-platform and tested on Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation generally provides parity between Linux and Windows for most APM configuration steps, but there are subtle signs of Windows bias. In several places, Windows-specific tools (like the Kudu console) are mentioned for Windows, while SSH is used for Linux. In the Application Insights section, the Windows example includes an extra app setting (XDT_MicrosoftApplicationInsights_Java=1) not explained for Linux. The order of presentation sometimes places Windows before Linux, and references to Windows tools and patterns are more explicit. There are no missing Linux examples, but the documentation assumes familiarity with Windows-specific tooling and sometimes provides more detailed steps for Windows.

Recommendations:

Ensure that all platform-specific steps are equally detailed for both Linux and Windows, including explanations for any extra app settings or environment variables.
When referencing platform-specific tools (like Kudu for Windows), provide equivalent Linux alternatives or clarify if not applicable.
Present Linux and Windows instructions in a consistent order (e.g., Linux first if targeting OSS audiences, or alternate order in sections).
Explain any differences in environment variables or app settings between platforms, so Linux users are not left wondering about missing options.
Where possible, use cross-platform tools or commands (e.g., Azure CLI, FTP, or zip deployment) instead of platform-specific consoles.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides PowerShell-based examples (specifically using the Microsoft Graph PowerShell module) for configuring password expiry, but does not offer equivalent CLI or scripting examples for Linux/macOS users. There is an implicit assumption that administrators will use PowerShell, which is more common on Windows. No mention is made of cross-platform alternatives such as Azure CLI, Bash, or REST API usage via curl, and there are no Linux/macOS-specific instructions or examples.

Recommendations:

Provide equivalent examples using Azure CLI and/or Bash scripts (e.g., using curl to call Microsoft Graph API), which are natively available on Linux/macOS.
Explicitly mention that PowerShell Core is cross-platform and provide installation instructions for non-Windows systems, if PowerShell must be used.
Where possible, present REST API calls with both PowerShell and curl/Bash examples, so users on any OS can follow along.
Reorder or parallelize examples so that Windows and Linux/macOS approaches are given equal prominence.
Add a note clarifying that all operations can be performed from any OS, and link to relevant cross-platform tool documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias throughout. All AD FS configuration steps are described using Windows-specific tools such as Server Manager, AD FS Management snap-in, and PowerShell cmdlets. There are no Linux or cross-platform alternatives provided for any step, and all troubleshooting instructions reference Windows event logs and tools. The documentation assumes the administrator is operating in a Windows environment and does not mention or provide guidance for Linux-based AD FS alternatives or SAML identity providers.

Recommendations:

Provide equivalent instructions for configuring SAML identity providers using non-Windows AD FS alternatives (e.g., Shibboleth, SimpleSAMLphp) commonly used on Linux.
Include examples of how to generate and manage certificates using Linux tools (e.g., OpenSSL) alongside any Windows-specific instructions.
Offer guidance on how to view and troubleshoot SAML logs and events using Linux-based tools or generic SAML debugging tools.
Clearly state at the beginning of the document that the instructions are Windows/AD FS-specific, and link to separate guides for Linux-based SAML providers if available.
Where PowerShell or Windows GUI steps are given, provide equivalent CLI or configuration file examples for Linux-based SAML providers.

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 documentation (such as Schannel and enabling TLS 1.2 in Windows environments) and omitting Linux-specific guidance or examples. No Linux or cross-platform configuration instructions are provided, and the linked resources are primarily Windows-focused.

Recommendations:

Include examples or references for configuring TLS 1.2 and cipher suites on common Linux web servers (e.g., Apache, Nginx) and platforms.
Add links to official Linux/OpenSSL documentation for managing cipher suites and TLS versions.
Balance the 'Next steps' section with resources relevant to both Windows and Linux environments.
Mention cross-platform tools (such as OpenSSL's s_client) for endpoint testing, in addition to SSL Labs.
Explicitly state that the requirements apply to all platforms and provide parity in troubleshooting guidance for non-Windows systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented towards Windows and Visual Studio users. All instructions and UI references are for Visual Studio, a Windows-first IDE, with no mention of cross-platform alternatives (such as VS Code or CLI). The use of Solution Explorer, Publish dialogs, and NuGet Package Manager Console (which is PowerShell-based) are all Windows-centric. There are no Linux/macOS-specific instructions or CLI-based alternatives provided, despite Azure Storage Explorer being cross-platform.

Recommendations:

Provide equivalent instructions for developing and running Azure Functions using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
Include examples of how to install dependencies and manage app settings using command-line tools (e.g., dotnet CLI, func CLI) that work on Linux and macOS.
Reference cross-platform editors and workflows alongside Visual Studio, or link to relevant guides for non-Windows users.
Avoid assuming the use of Solution Explorer, Publish dialogs, or NuGet Package Manager Console; instead, offer alternative steps for users on other platforms.
Clearly indicate which steps are Windows-specific and provide parity for Linux/macOS users wherever possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows tools (Git Bash from Git for Windows, Visual Studio Immediate Window) as the primary or only examples for cloning and URL encoding passwords. There are no Linux or macOS-specific instructions or examples, and the only tool-specific guidance is for Windows environments. This may hinder Linux or cross-platform users who are unfamiliar with these Windows-centric tools.

Recommendations:

Provide explicit Linux and macOS instructions for cloning the repository, such as using the default terminal or common Linux tools.
Replace or supplement the Visual Studio Immediate Window example for URL encoding with a cross-platform method, such as using Python, Node.js, or command-line utilities available on Linux/macOS.
When referencing tools, mention cross-platform options first (e.g., 'any Git client or terminal'), and only mention Windows-specific tools as one possible option.
Add a note or section clarifying that all Git operations can be performed from any OS, and provide example commands for Linux/macOS shells.
Ensure parity in troubleshooting steps and credential handling for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates Windows bias by exclusively referencing Windows-specific tools (such as Server Manager and AD FS Management), providing only GUI-based instructions for AD FS setup, and omitting any Linux or cross-platform alternatives. There are no command-line or Linux-based examples for configuring AD FS or equivalent identity providers, and all instructions assume a Windows Server environment.

Recommendations:

Provide equivalent command-line instructions using PowerShell and, if possible, cross-platform tools or APIs.
Acknowledge that AD FS is a Windows-only technology, but suggest or link to Linux-compatible alternatives (such as Shibboleth, Keycloak, or other OpenID Connect providers) for non-Windows environments.
Include a section or appendix outlining how to integrate Azure AD B2C with OpenID Connect providers running on Linux, with example configurations.
Clarify early in the documentation that the steps are specific to Windows Server and AD FS, and offer guidance for users on other platforms.
Where possible, reference REST APIs or scripting approaches that could be used from non-Windows systems to automate or replicate the configuration.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily in the 'Revoke a consumer user's session' section, where only Microsoft Graph PowerShell commands are provided and explicitly reference 'Windows PowerShell.' There are no equivalent examples for Linux or macOS users, nor is there mention of using cross-platform tools like the Microsoft Graph CLI or direct API calls via curl. The rest of the documentation focuses on portal-based actions, which are platform-agnostic, but the only programmatic example is Windows-centric.

Recommendations:

Provide equivalent instructions for Linux and macOS users, such as using Microsoft Graph PowerShell on those platforms (since it is cross-platform), or using the Microsoft Graph CLI or REST API via curl.
Avoid phrases like 'In your Windows PowerShell' and instead use 'In your terminal' or specify that the commands work on all supported platforms.
Include explicit Linux/macOS command-line examples where programmatic actions are shown, or at least mention that the tools are cross-platform.
Where possible, link to documentation for installing and using Microsoft Graph PowerShell on Linux/macOS, and/or provide REST API examples for users who prefer not to use PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation assumes a Windows development environment throughout. It references Visual Studio (a Windows-centric IDE), .sln solution files, and Web.config XML configuration, all of which are typical of Windows/.NET workflows. There are no instructions or examples for Linux or cross-platform development environments, nor are alternative tools or editors mentioned. The guide does not address how to perform equivalent steps on Linux (e.g., using VS Code, JetBrains Rider, or command-line tools), nor does it mention .NET Core cross-platform capabilities.

Recommendations:

Include instructions for opening and editing the project using cross-platform tools such as VS Code or JetBrains Rider.
Mention how to run and test the sample application on Linux or macOS, including any prerequisites (e.g., .NET SDK installation, command-line build/run instructions).
Provide examples of editing configuration files using common Linux tools (nano, vim) or via the command line.
Clarify that the instructions are applicable to .NET Core/.NET 5+ projects, which are cross-platform, and note any differences for non-Windows environments.
Add a section or notes on how to deploy and test the application on Linux-based servers or containers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by referencing Windows-specific tools and workflows (such as ASP.NET MVC and OWIN middleware), providing links and instructions that default to Windows (e.g., certificate management), and omitting equivalent Linux-based examples or guidance. There are no Linux or cross-platform code samples for application integration, and the only application example for OIDC is a .NET/Windows stack. Certificate management and other operational steps reference Windows tabs or tools without Linux alternatives.

Recommendations:

Provide Linux-based examples for application integration, such as using a Python Flask or Node.js app for OIDC instead of only ASP.NET MVC.
Include instructions for obtaining and uploading certificates using Linux tools (e.g., OpenSSL) alongside or instead of Windows-centric instructions.
Ensure that all referenced documentation (such as certificate management) includes Linux tabs or sections, not just Windows.
When describing application configuration, offer both Windows and Linux deployment scenarios, especially for sample/demo apps.
Use cross-platform terminology and avoid assuming the reader is using Windows by default.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides both Linux and Windows instructions for configuring data sources in Tomcat and JBoss on Azure App Service. However, the Windows section is notably more detailed, with extensive PowerShell scripting and Windows-specific file paths and tools (e.g., PowerShell, %HOME%, %LOCAL_EXPANDED%). The Linux instructions are present and generally sufficient, but the Windows configuration is described with more step-by-step detail and custom scripting. Additionally, Windows-specific tools and patterns (PowerShell, .cmd files) are emphasized, and in some sections, the Windows approach is described before the Linux equivalent.

Recommendations:

Ensure Linux and Windows instructions are equally detailed, especially for advanced scenarios (e.g., custom Tomcat configuration).
Provide Linux shell script examples with the same level of detail as the Windows PowerShell scripts, including error handling and step-by-step explanations.
Where possible, present Linux and Windows instructions in parallel or side-by-side, rather than Windows-first.
Avoid assuming PowerShell as the default scripting language; offer Bash or sh alternatives for Linux users.
Clarify when a tool or pattern is Windows-only and suggest the closest Linux equivalent.
Review for any missing Linux-specific troubleshooting or automation tips that are present for Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing only PowerShell scripts for critical steps such as generating self-signed certificates and random signing keys, with no equivalent Linux or cross-platform commands. The use of PowerShell and references to Visual Studio for deployment further reinforce a Windows-centric approach, while omitting guidance for Linux or macOS users.

Recommendations:

Provide equivalent Bash/OpenSSL commands for generating self-signed certificates and random strings for Linux/macOS users.
Include deployment instructions using cross-platform tools such as Azure CLI, GitHub Actions, or VS Code instead of only referencing Visual Studio.
Explicitly mention that the PowerShell examples are for Windows and offer alternatives for other operating systems.
Review all steps to ensure that Linux and macOS users can follow the tutorial without needing to switch to a Windows environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing IIS as the example application for testing, linking to Microsoft IIS setup guides, and omitting any mention of Linux-based web servers (such as Apache or Nginx) or their configuration. All application testing and setup guidance is Windows-centric, with no Linux alternatives or parity in examples or instructions.

Recommendations:

Add parallel instructions and examples for deploying and testing with a Linux-based web application (e.g., Apache, Nginx, or a generic Python/Node.js app).
Include links to official documentation for setting up a test web application on Linux.
When referencing IIS, also mention Linux alternatives and provide equivalent configuration steps.
Ensure troubleshooting and SSL certificate management sections include Linux-relevant guidance (e.g., using OpenSSL, configuring certificates on Apache/Nginx).
Use neutral language when referring to test applications, e.g., 'a web application (such as IIS on Windows or Apache on Linux)' instead of only mentioning IIS.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing Visual Studio and linking to Windows-centric deployment instructions, without mentioning or providing equivalent guidance for Linux-based development environments or deployment tools. There are no examples or instructions for deploying the API from Linux or using cross-platform tools, and the only deployment path described is via Visual Studio, which is primarily a Windows tool.

Recommendations:

Add instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or GitHub Actions, which can be used from Linux, macOS, or Windows.
Provide examples for deploying the API using the dotnet CLI (dotnet publish) and Azure CLI (az webapp up), which are available on Linux.
Include a note or section highlighting that Visual Studio is not required and that developers can use VS Code or other editors on Linux.
Where deployment instructions are given, offer both Windows (Visual Studio) and Linux (CLI-based) alternatives, and avoid assuming the user is on Windows.
Review all linked documentation to ensure Linux users are not excluded or left without guidance.

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 examples use PowerShell syntax and cmdlets (such as Start-AzAutomationRunbook, Disable-AzContextAutosave, Connect-AzAccount), and there is no mention or example of using Python or other runbook types supported by Azure Automation (such as Python runbooks, which are commonly used on Linux). The terminology and instructions assume a Windows/PowerShell environment, and there are no Linux/bash equivalents or guidance for non-Windows users.

Recommendations:

Add equivalent examples for Python runbooks, which are supported in Azure Automation and commonly used in Linux environments.
Include bash/CLI examples where possible, or at least mention how Linux users can achieve similar functionality.
Explicitly state the platform support and limitations for each approach (e.g., which features are PowerShell-only, which are cross-platform).
Reorganize sections to avoid always presenting Windows/PowerShell approaches first; consider parallel presentation of PowerShell and Python/bash examples.
Reference Azure CLI or REST API alternatives for starting and managing runbooks, which are platform-agnostic.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a mild Windows bias. It references Windows-specific tools (Visual Studio, Azure Storage Explorer) without mentioning cross-platform or Linux alternatives, and omits command-line or deployment examples for Linux users. There are no explicit Linux or macOS instructions, and the only tool mentioned for code publishing is Visual Studio, which is primarily a Windows application.

Recommendations:

Provide alternative instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or GitHub Actions, including Linux/macOS command-line examples.
Mention and link to cross-platform editors (e.g., VS Code) and deployment methods (e.g., dotnet CLI, az webapp deploy) alongside Visual Studio.
For managing Azure Storage, suggest cross-platform tools such as the Azure CLI (az storage blob upload), AzCopy, or the Azure Portal, not just Azure Storage Explorer.
Explicitly state that all steps can be performed from Linux/macOS as well as Windows, and provide any necessary shell or command-line examples.
Review all tool and workflow mentions to ensure parity for Linux and macOS users, not just Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively providing PowerShell-based instructions for enabling Saviynt to delete users in Azure AD B2C. It explicitly instructs users to install the Microsoft Graph PowerShell module on a Windows workstation or server, with no mention of Linux or cross-platform alternatives. No CLI, Bash, or platform-agnostic examples are provided, and the use of PowerShell is assumed throughout the configuration steps.

Recommendations:

Provide equivalent instructions using the Microsoft Graph CLI or REST API with curl, which are cross-platform and work on Linux, macOS, and Windows.
Explicitly mention that the Microsoft Graph PowerShell module is available for Linux and macOS via PowerShell Core, and provide installation steps for those platforms.
Include Bash or shell script examples alongside PowerShell commands, or at least reference how to perform the same operations on Linux.
Avoid language that assumes a Windows environment (e.g., 'on a Windows workstation or server') unless absolutely necessary, and clarify when steps are platform-specific.
Add a section or note about platform compatibility and alternative tooling for non-Windows users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows environments by referencing .NET and web.config (Windows-centric technologies), omitting Linux-specific deployment or configuration guidance, and providing hosting instructions only for Azure App Service (commonly used with Windows). There are no examples or instructions for Linux-based hosting, configuration (such as environment variables or appsettings.json), or cross-platform .NET Core usage.

Recommendations:

Provide Linux-specific deployment instructions, such as hosting the .NET app on Linux-based services (e.g., Azure App Service for Linux, Docker, or on-premises Linux servers).
Include configuration examples using appsettings.json and environment variables, which are cross-platform and preferred for .NET Core/5+/6+ applications.
Offer guidance for running the sample app using the dotnet CLI, including Linux/macOS terminal commands.
Mention cross-platform certificate creation and management tools (e.g., OpenSSL) alongside or instead of Windows certificate tools.
Clarify that the sample app and instructions are compatible with both Windows and Linux, and highlight any platform-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows, specifically using a WPF (Windows Presentation Foundation) desktop application and Visual Studio as the development environment. There are no examples or instructions for running the sample on Linux or macOS, nor are any cross-platform frameworks or tools mentioned. All screenshots and workflow steps are tailored to Windows users, and the use of Visual Studio (Windows-only for WPF) further excludes Linux users.

Recommendations:

Provide equivalent instructions and sample applications for Linux (and macOS), such as using .NET MAUI or Avalonia for cross-platform desktop apps.
Include steps for running the sample using Visual Studio Code or JetBrains Rider, which are available on Linux.
Offer command-line instructions for building and running the application using the .NET CLI, which is cross-platform.
Add Linux-specific prerequisites and troubleshooting sections.
Include screenshots and workflow descriptions for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a primarily Windows IDE) for running the sample application, and all instructions assume the use of Windows tooling and workflows. There are no examples or guidance for running the sample on Linux or using cross-platform tools such as VS Code, .NET CLI, or alternative editors. Linux users are left without instructions on how to set up, run, or debug the sample application.

Recommendations:

Add a section with instructions for running the sample on Linux using the .NET CLI (e.g., dotnet build, dotnet run) and editors like VS Code.
Mention cross-platform prerequisites, such as installing the .NET SDK, and provide download links for Linux and macOS.
Include Linux/macOS-specific steps for cloning the repository, restoring dependencies, and running both the web app and API.
Provide screenshots or terminal output examples for Linux environments where appropriate.
Clarify that Visual Studio is optional and that the sample can be run on any platform supporting .NET Core/ASP.NET Core.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias primarily in the certificate creation section, where only PowerShell is mentioned as a method for creating self-signed certificates. There are no equivalent Linux or cross-platform command-line examples (such as OpenSSL) provided for certificate generation. The rest of the documentation is largely platform-agnostic, focusing on Azure portal UI and XML configuration, but the lack of Linux guidance in key operational steps may hinder non-Windows users.

Recommendations:

Provide Linux and cross-platform examples for creating self-signed certificates, such as using OpenSSL, alongside the existing PowerShell instructions.
When referencing command-line tools or scripts, ensure both Windows (PowerShell) and Linux (Bash/OpenSSL) options are presented, or link to platform-agnostic Azure CLI documentation where possible.
Explicitly state that certificate creation can be performed on any OS, and provide step-by-step instructions for at least the two major platforms (Windows and Linux).
Review any included scripts or downloadable resources to ensure they are not Windows-only, or provide equivalents for Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only a PowerShell script for monitoring directory quota, with no equivalent example for Linux or cross-platform environments. It assumes the use of Windows tools and patterns (PowerShell, Invoke-RestMethod, New-Object), and does not mention or prioritize Linux-compatible alternatives. This may hinder users on Linux or macOS from following the guide easily.

Recommendations:

Provide a cross-platform example using curl and jq (or similar tools) for Linux/macOS users.
Include a note that the PowerShell script can be run on PowerShell Core, which is available on Linux and macOS, if applicable.
List both Windows (PowerShell) and Linux/macOS (bash/curl) examples side by side, or at least mention Linux alternatives.
Avoid assuming the user is on Windows; use more neutral language and tool recommendations.
Add a section or callout for Linux users, explaining how to achieve the same result with native tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates Windows bias by providing a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, without mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI, Bash, or REST API). The use of PowerShell and the lack of Linux-native tooling or examples suggest a preference for Windows environments.

Recommendations:

Add Azure CLI examples for uploading and managing CA certificates, as Azure CLI is cross-platform and widely used on Linux.
Include REST API examples for certificate management to provide a platform-agnostic approach.
Present PowerShell and CLI/REST examples side-by-side, or at least mention Linux-compatible alternatives before or alongside Windows-specific tools.
Clarify that the PowerShell command is optional and provide guidance for users on non-Windows platforms.
Review and update screenshots or UI instructions to ensure terminology and steps are not Windows-centric.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only a PowerShell script example for programmatically accessing audit logs via the Microsoft Entra reporting API. There are no equivalent examples using Linux-native tools (such as curl, wget, or Python), nor are there references to Bash or shell scripting. The script assumes familiarity with PowerShell, which is primarily a Windows tool, and suggests using Azure Cloud Shell (which does support PowerShell, but Bash is also available). This creates a bias toward Windows users and may hinder Linux users or those preferring cross-platform scripting.

Recommendations:

Provide equivalent examples using Bash shell scripting with curl or wget to demonstrate how to access the API and process results on Linux or macOS.
Include a Python example for querying the Microsoft Graph API, as Python is cross-platform and widely used.
Explicitly mention that the API can be accessed from any platform and that PowerShell is just one option.
Add a note or section on using Azure CLI or other cross-platform tools where applicable.
Reorder or parallelize examples so that Windows and Linux approaches are presented together, or alternate which comes first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows/Azure portal bias by exclusively referencing the Azure portal UI and Microsoft Entra ID (formerly Azure Active Directory) for identity management, with no mention of Linux command-line tools, cross-platform CLI alternatives, or non-Microsoft identity providers in practical examples. There are no PowerShell-specific commands, but all workflows are described in the context of the Azure portal, which is most familiar to Windows users. There are no Linux shell/CLI examples, and no mention of using Azure CLI, REST APIs, or automation scripts that are platform-agnostic.

Recommendations:

Provide equivalent Azure CLI (az) commands for all portal-based steps, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
Include REST API examples for automation and platform neutrality.
Mention and, where possible, provide examples for using non-Microsoft identity providers (e.g., Auth0, Okta) for OAuth 2.0, not just Microsoft Entra ID.
Explicitly state that all steps can be performed from any OS using the Azure CLI or REST API, and provide links to relevant documentation.
Add a section or callout for Linux/macOS users, highlighting any differences or confirming parity.
If screenshots are used, consider including at least one from a non-Windows environment (e.g., browser on Linux/macOS) to reinforce cross-platform support.

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 and patterns (such as IISNode, web.config, and PowerShell) are mentioned prominently, sometimes before or in more detail than their Linux equivalents. Windows examples or explanations often precede Linux ones, and some advanced configuration or troubleshooting steps are only detailed for Windows (e.g., web.config troubleshooting), with Linux sections being more generic or referring to includes. PowerShell is referenced for Application Insights instrumentation, with no equivalent Bash/Azure CLI example for Linux. Some sections (like custom deployment scripts) are more detailed for Linux, but overall, Windows concepts and tools are more deeply integrated and explained.

Recommendations:

Ensure Linux and Windows instructions/examples are presented with equal prominence and detail, ideally side-by-side or in parallel sections.
For every PowerShell or Windows tool reference (e.g., web.config, IISNode), provide the Linux/container equivalent (e.g., startup scripts, PM2, nginx/apache config, etc.), or explicitly state when there is no equivalent.
Add Bash/Azure CLI examples for Application Insights instrumentation on Linux, not just PowerShell.
Expand troubleshooting and advanced configuration sections for Linux to match the depth provided for Windows (e.g., what to do if the app does not start, common misconfigurations, etc.).
When referencing tools like IISNode or web.config, clarify their scope (Windows-only) and provide links or guidance for Linux users.
Review the order of presentation so that Linux and Windows are treated equally, or alternate which platform is presented first in each section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides command-line examples for Azure CLI and Azure PowerShell, but does not include any Linux-specific or bash-native examples beyond Azure CLI. The PowerShell example is given its own section, and there is a FAQ entry specifically about PowerShell. There are no references to Linux tools, OpenSSL, or Linux-native certificate management patterns. The documentation assumes use of the Azure Portal or Azure CLI/PowerShell, which are cross-platform, but does not address Linux-specific workflows or mention Linux certificate stores.

Recommendations:

Add explicit bash/Linux shell examples for certificate export and handling, such as using OpenSSL to inspect or convert the .pfx file.
Include notes or examples for importing certificates into common Linux web servers (e.g., Apache, Nginx) after export.
Balance the PowerShell examples with equivalent bash or Linux-native commands where possible.
Mention Linux certificate stores and how to use the exported .pfx file with them.
In FAQs and troubleshooting, include Linux-specific scenarios and not just PowerShell-centric issues.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing AWS credential management via a link to the AWS PowerShell documentation, without mentioning or linking to equivalent Linux/CLI or SDK methods. There are no Linux-specific examples or references to cross-platform tools for credential management or automation, and the only external guidance provided is for PowerShell users.

Recommendations:

Include references and links to AWS CLI documentation for credential management, not just PowerShell.
Provide examples for storing and using AWS credentials in Automation runbooks using both PowerShell and Python (or other cross-platform languages).
Mention and link to Linux/macOS compatible tools and workflows for AWS credential management.
Ensure that all example commands and workflows are presented in both Windows (PowerShell) and Linux (Bash/CLI) formats where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by featuring PowerShell automation prominently, mentioning it before (and more visibly than) Azure CLI, and not providing Linux-specific or cross-platform command-line examples. The automation section gives a direct PowerShell script embed, while the Azure CLI is only linked. There are no Linux shell or bash examples, and no mention of Linux tools or workflows for certificate management or upload.

Recommendations:

Provide explicit Linux/bash command-line examples alongside or before PowerShell, especially in automation sections.
Embed Azure CLI examples directly in the documentation, not just as links, and ensure parity with PowerShell scripts.
Include references to Linux-native tools (such as OpenSSL for certificate management) where relevant.
Ensure that language in the documentation is platform-neutral unless a step is truly OS-specific.
Add a section or callouts for Linux/macOS users, clarifying any differences in workflow or tooling.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is heavily biased toward Windows and PowerShell usage. All command-line examples are provided exclusively in Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform scripting. File paths use Windows-style conventions (e.g., C:\Users\Contoso\), and there is no guidance for Linux or macOS users regarding certificate storage or command adaptation. The documentation assumes the use of Windows tools and patterns throughout, making it less accessible for users on Linux or macOS.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside PowerShell for all resource creation and configuration steps.
Include Bash shell script examples and use cross-platform file path conventions (e.g., $HOME/certs/ or ~/certs/) in variable definitions.
Add notes or sections specifically addressing Linux/macOS users, especially for certificate handling, file paths, and environment setup.
Reference cross-platform tools (such as OpenSSL for certificate generation) and avoid assuming the use of Windows-only utilities.
Where PowerShell is required, clarify that Azure PowerShell is available on Linux/macOS and provide installation instructions for those platforms.
Reorder or parallelize instructions so that Linux/macOS approaches are presented equally, not as an afterthought.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias toward Windows by providing only PowerShell examples for command-line operations (such as disabling certificate chain validation), without offering equivalent instructions for Linux or cross-platform tools like Azure CLI. The use of PowerShell cmdlets and the absence of bash or Azure CLI examples may disadvantage Linux users or those working in non-Windows environments.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell cmdlets, especially for tasks like disabling certificate chain validation.
Include bash shell examples where appropriate, particularly for uploading certificates or managing API Management resources.
Explicitly mention that PowerShell examples can be run on Linux/macOS using PowerShell Core, or provide alternative commands for native Linux environments.
Review the documentation for other areas where Windows-centric tools or workflows are assumed, and ensure Linux parity throughout.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments by providing only Azure PowerShell examples for command-line logger creation, without offering equivalent Azure CLI or Bash examples. The use of PowerShell is highlighted as the sole scripting interface, and there is no mention of Linux-native tools or cross-platform command-line alternatives. This may hinder Linux or macOS users who prefer or require non-PowerShell workflows.

Recommendations:

Add Azure CLI examples alongside PowerShell for logger creation and management, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that all configuration steps can be performed from any OS using the Azure portal or REST API, not just via PowerShell.
Where PowerShell is used, provide equivalent Bash or shell script snippets where possible, or link to documentation showing how to perform the same steps using Azure CLI.
Clarify that Bicep and ARM templates are OS-agnostic, and provide guidance on deploying them from Linux/macOS environments.
Review all sections for references to Windows-specific tools or workflows and ensure Linux parity is maintained throughout.

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 Azure PowerShell examples for command-line operations, referencing installation of Azure PowerShell (a Windows-centric tool), and omitting equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell approach is presented before ARM templates, and there is no mention of Linux or macOS workflows. This may disadvantage users on Linux or macOS who prefer Azure CLI or Bash scripting.

Recommendations:

Add Azure CLI examples for all operations currently demonstrated with Azure PowerShell, including creating and updating API Management instances with managed identities.
Include Bash script examples where appropriate, especially for ARM template deployments.
Explicitly mention that Azure CLI is cross-platform and provide installation links for Linux/macOS users.
Present Azure CLI and PowerShell examples side-by-side or in parallel tabs, rather than PowerShell-first.
Review references to 'install Azure PowerShell' and add corresponding instructions for Azure CLI.
Ensure screenshots and UI instructions are not Windows-specific, or clarify if they are universal.

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., New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) as the only CLI automation examples, without mentioning or providing equivalent Azure CLI or REST API commands that are cross-platform. There are no Linux/macOS-specific instructions or examples, and the use of PowerShell is presented as the default scripting/automation method.

Recommendations:

Provide equivalent Azure CLI commands for all PowerShell cmdlet examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
Include REST API examples for automation tasks, which are platform-agnostic.
When mentioning PowerShell, also mention Azure CLI and REST API options, and present them in parallel or in a neutral order (not Windows/PowerShell first).
Add explicit notes or sections for Linux/macOS users to ensure parity and inclusivity.
Review the documentation for other areas where Windows-specific tools or patterns are assumed, and update to include cross-platform alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only PowerShell-based examples for interacting with the Azure REST API, with no equivalent examples for Linux or cross-platform tools such as Azure CLI or curl. The workflow assumes the use of Windows tools and patterns (e.g., PowerShell cmdlets, Windows file paths), and does not mention or prioritize Linux or cross-platform alternatives.

Recommendations:

Add equivalent examples using Azure CLI and/or curl for sending the PATCH request, suitable for Linux/macOS users.
Include bash shell scripting examples alongside PowerShell to ensure parity.
Use platform-neutral file path examples or clarify paths for both Windows and Linux.
Mention both PowerShell and CLI/curl options in the introduction to REST API usage, rather than focusing solely on PowerShell.
Ensure that authentication steps are described for both PowerShell and Azure CLI (e.g., az login).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides a detailed PowerShell example for creating and assigning custom roles but does not offer equivalent examples using cross-platform tools such as Azure CLI. PowerShell is a Windows-centric tool (though available on Linux, it is less commonly used there), and the lack of Azure CLI or bash examples may hinder Linux users. Additionally, the page references Azure PowerShell before Azure CLI in the list of tools, and the only code sample is in PowerShell.

Recommendations:

Add equivalent Azure CLI (az role definition/az role assignment) examples alongside PowerShell code samples for custom role creation and assignment.
When listing tools for role assignment, mention Azure CLI before or alongside Azure PowerShell to avoid implying a Windows-first workflow.
Include bash or shell script examples where appropriate to demonstrate cross-platform compatibility.
Explicitly state that all operations can be performed using Azure CLI and provide links to relevant CLI documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation generally provides parity between Windows and Linux by using platform pivots, but there are several sections where Windows-specific tools, patterns, and instructions are emphasized or provided exclusively. Notably, the 'Run Composer' and 'Run Bower, Gulp, or Grunt' sections are only present for Windows, relying on KuduScript and deployment script customization, with no Linux equivalents or guidance. Some instructions (e.g., changing the site root) use Windows paths and tools first, and Windows-specific details (like .dll extensions, directory structures, and KuduScript) are described in more detail or earlier than their Linux counterparts. In some cases, Linux instructions are less detailed or missing for common tasks.

Recommendations:

Add Linux equivalents for 'Run Composer', 'Run Bower, Gulp, or Grunt', and custom deployment script automation, including examples of how to achieve similar automation using Oryx hooks or custom scripts.
Ensure that for every Windows-specific tool or pattern (e.g., KuduScript, .dll, Windows directory paths), a Linux equivalent (.so, Linux paths, SSH/Bash instructions) is provided with equal detail and prominence.
Where possible, present Windows and Linux instructions side-by-side or in parallel pivots, and avoid placing Windows instructions or tools first unless there is a clear reason.
Expand the Linux sections to include more detailed, step-by-step guidance for tasks that are described in detail for Windows (e.g., custom deployment automation, enabling extensions, changing site root).
Review for any missing Linux examples or references, especially for automation and deployment customization, and add them to ensure parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references Azure PowerShell and Azure SDKs as tools for automating subscription key management, but does not mention Linux-native tools, CLI examples, or provide cross-platform command-line instructions. There are no Linux-specific or cross-platform automation examples, and the only tooling mentioned is PowerShell, which is traditionally Windows-centric (despite now being cross-platform).

Recommendations:

Include Azure CLI examples alongside or instead of Azure PowerShell for automation tasks, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that Azure PowerShell is available on Linux and macOS, or provide Bash shell script examples where appropriate.
When referencing SDKs, clarify which languages and platforms are supported, and provide at least one example using a Linux-friendly language (e.g., Python).
Avoid implying that PowerShell is the primary or only automation tool; present CLI and SDK options in a platform-neutral order.
Add a section or callout for Linux/macOS users, highlighting equivalent tools and workflows.

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 examples, prerequisites, and instructions are specific to Windows (e.g., requiring Windows Management Framework, .NET Framework, and Windows PowerShell). There is no mention of Linux, macOS, or cross-platform PowerShell Core support. Installation and usage steps assume a Windows OS, and no Bash, CLI, or cross-platform alternatives are provided.

Recommendations:

Add equivalent instructions and examples for Linux and macOS environments, including how to use PowerShell Core (pwsh) and the Azure CLI.
Clarify which steps are Windows-specific and provide alternative steps for non-Windows users (e.g., installing modules on Linux/macOS, using dotnet instead of .NET Framework).
Include Bash/Azure CLI examples for authentication and automation tasks, not just PowerShell.
Mention cross-platform compatibility of the Az module and how to use it in non-Windows environments.
Explicitly state OS requirements and provide links to relevant installation guides for Linux/macOS.
Where Windows tools (e.g., Sign-in Assistant, WMF) are required, note their absence or alternatives on other platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page references Azure PowerShell before Azure CLI and does not provide Linux-specific examples or mention Linux tooling. The order of tools (Azure CLI, Azure PowerShell, Resource Manager templates, API) places PowerShell prominently, and there are no bash or Linux command-line examples. The documentation assumes familiarity with Windows-centric tools and patterns, which may disadvantage Linux users.

Recommendations:

Provide explicit Linux/bash examples alongside or before PowerShell examples.
When listing management tools, mention Azure CLI before Azure PowerShell, as CLI is cross-platform and more familiar to Linux users.
Include sample commands for both Azure CLI and Azure PowerShell where relevant.
Reference Linux-native tools or workflows where possible, and clarify that all management operations can be performed from Linux environments.
Avoid assuming the user is using Windows or PowerShell; use neutral language and tool ordering.

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 for generating tokens and calling APIs are provided exclusively in PowerShell, a Windows-centric shell. There are no equivalent examples using cross-platform or Linux-native tools (such as curl or bash scripts). The only CLI scripting guidance is for Azure PowerShell, and there is no mention of Linux or macOS workflows. The documentation assumes use of the Azure Portal (web UI), which is cross-platform, but all automation and scripting is presented in a Windows-first manner.

Recommendations:

Provide equivalent examples using curl and bash for Linux/macOS users, especially for OAuth token generation and API calls.
Explicitly mention that the API calls and token generation can be performed from any OS, not just Windows.
Where Azure PowerShell is referenced, also provide Azure CLI (az) equivalents, which are cross-platform.
Add a note or section highlighting Linux/macOS compatibility and any OS-specific considerations.
Ensure screenshots and UI instructions do not assume a Windows environment unless absolutely necessary.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references Windows PowerShell cmdlets and provides only PowerShell-based examples for managing Azure API Management via Azure Automation. There is no mention of Linux-compatible tools (such as Azure CLI, Bash scripts, or Python), nor are any cross-platform or Linux-specific examples provided. The focus on PowerShell and Windows tools creates a Windows-centric bias.

Recommendations:

Include equivalent examples using Azure CLI, which is cross-platform and widely used on Linux.
Provide Bash or Python script samples for managing Azure API Management in Azure Automation.
Explicitly mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.) and provide links or examples for each.
Reorder content or add parallel sections so that Linux-compatible tools and workflows are presented alongside Windows/PowerShell options.
Clarify in the introduction that the guide currently focuses on PowerShell, and point to resources for other 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 Azure PowerShell (and specifically the AzureAD module) instructions for provisioning the service principal, with no equivalent Bash/CLI or Linux-native example. The prerequisite section includes a PowerShell requirements include, and all command-line steps are shown using PowerShell syntax. There is no mention of cross-platform Azure CLI alternatives, and the documentation assumes use of the Azure Portal (web UI), which is platform-neutral but does not compensate for the lack of Linux/CLI parity in scripting steps.

Recommendations:

Provide equivalent Azure CLI (az) commands for all PowerShell steps, especially for provisioning the service principal. Azure CLI is cross-platform and works natively on Linux and macOS.
Add a section or callout indicating that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant Azure CLI documentation.
Where PowerShell modules are referenced (e.g., AzureAD), mention their platform limitations and suggest alternatives for non-Windows users.
Ensure that all code snippets and automation steps are available in both PowerShell and Bash/Azure CLI formats, ideally side-by-side.
Review the 'azure-powershell-requirements-no-header' include to ensure it does not exclude or discourage Linux users.

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 tools and workflows (IIS, Certreq.exe, PowerShell) are mentioned explicitly, sometimes without Linux equivalents or with Windows methods listed first. PowerShell is given as a primary automation example alongside Azure CLI, but Linux-native certificate management tools (beyond OpenSSL) and Linux-specific workflows are not covered. The documentation assumes familiarity with Windows concepts and tools, and Linux users may find gaps in guidance for common certificate management tasks.

Recommendations:

Provide Linux-native examples for certificate request and export, such as using OpenSSL for both certificate generation and export, and detail how to perform these tasks on Linux systems.
When mentioning Windows tools (IIS, Certreq.exe), also mention Linux equivalents (e.g., OpenSSL, certbot) and provide links or brief instructions.
In automation sections, include Bash scripting or Linux CLI examples alongside PowerShell, and clarify any OS-specific differences.
Avoid listing Windows tools or workflows before Linux equivalents; instead, present both options in parallel or in OS-specific tabs.
Clarify any App Service features or limitations that differ between Windows and Linux hosting plans, especially in the FAQ and outbound certificate usage sections.
Expand the FAQ to address common Linux scenarios, such as managing certificates on Linux-based App Service plans or containers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias towards Windows/Azure tools and workflows. All examples and instructions use Azure CLI, Azure Functions, and related Microsoft tooling, with no mention of Linux-specific workflows or alternatives. There are no explicit Linux or cross-platform deployment examples, and the recommended tools and services are all Microsoft-centric.

Recommendations:

Include explicit Linux/macOS command-line examples where applicable (e.g., bash, zsh).
Mention and provide examples for deploying to non-Azure static hosts (e.g., AWS S3, Google Cloud Storage, Apache/Nginx on Linux).
Reference cross-platform tools (such as Docker) for local development and deployment.
Clarify that Azure CLI and Azure Functions Core Tools are cross-platform, and provide installation instructions for Linux/macOS.
List alternative CDN and hosting providers, not just Azure CDN.
Add a section or callout noting that all steps can be performed on Linux/macOS, and highlight any differences if they exist.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and Azure PowerShell instructions for enabling virtual network integration, but the PowerShell section is significantly more detailed, with step-by-step parameter preparation, validation, and configuration commands. There are no Linux-specific shell (e.g., Bash) or cross-platform scripting examples, and PowerShell (traditionally associated with Windows) is given a prominent, detailed section. The CLI example is brief and lacks the depth of the PowerShell instructions, which may disadvantage Linux users or those preferring Bash scripting.

Recommendations:

Expand the Azure CLI section to include step-by-step instructions equivalent to the PowerShell section, covering parameter validation, subnet delegation, and integration.
Provide Bash shell script examples for common tasks, especially for subnet delegation and resource manipulation, to improve parity for Linux users.
Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, to encourage non-Windows users.
If possible, add guidance or links for using ARM templates or Bicep for infrastructure-as-code scenarios, which are platform-agnostic.
Avoid assuming PowerShell as the default scripting environment; present CLI or Bash examples first or in parallel with PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates bias towards Windows by referencing the Azure PowerShell cmdlet (New-AzApiManagementUser) as the only CLI-based method for adding users, without mentioning or providing examples for equivalent operations using cross-platform tools like Azure CLI, REST API, or scripting on Linux/macOS. No Linux or cross-platform command-line examples are given.

Recommendations:

Add equivalent Azure CLI commands for user management (e.g., az apim user create) alongside PowerShell examples.
Mention and link to REST API documentation for user management, which is platform-agnostic.
Explicitly state that Azure PowerShell is available cross-platform, but also provide bash/Linux/macOS-friendly examples.
Ensure that any scripting or automation guidance is provided for both Windows (PowerShell) and Linux/macOS (bash, Azure CLI).
Consider reordering examples so that cross-platform or Linux-friendly tools are mentioned first or alongside Windows-specific tools.

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. All command-line examples for creating and managing connections use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tools. The 'Create a new connection' section provides only a Windows PowerShell example, and the PowerShell tab appears before the Python tab in code samples. There is no guidance for users working from Linux or macOS environments, nor are cross-platform command-line alternatives (such as Azure CLI) presented.

Recommendations:

Add equivalent Azure CLI examples for creating and managing Automation connections, as Azure CLI is cross-platform and widely used on Linux/macOS.
Include explicit instructions or notes for users on Linux/macOS, clarifying how they can perform the same tasks without PowerShell.
Reorder or parallelize example sections so that PowerShell and Python (or CLI) examples are presented side-by-side, or at least do not always lead with Windows/PowerShell.
Mention and link to any relevant Linux tools or scripts that can interact with Azure Automation, if available.
Clarify in the introduction that the documented PowerShell cmdlets are available cross-platform (if true), or specify platform limitations.
Where GUI steps are described, note any differences or limitations for users accessing the Azure portal from non-Windows systems.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias, particularly in the permissions section, where only PowerShell scripts and Windows batch (.bat) scripts are provided for role creation and cleanup tasks. There are no equivalent examples or guidance for Linux or cross-platform environments (e.g., Bash, Azure CLI). Windows tools and patterns (PowerShell, .bat scripts) are mentioned exclusively and before any Linux alternatives, which are absent.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell scripts, especially for role creation and assignment.
Include Bash shell script examples alongside .bat scripts for cleanup and automation tasks.
Explicitly mention cross-platform compatibility and provide instructions for both Windows and Linux/macOS users.
Where possible, use platform-agnostic tools (e.g., Azure CLI, REST API) in examples and documentation.
Add notes or links to official documentation for performing the same tasks on Linux/macOS.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page focuses exclusively on using the Azure portal and Power Platform web interfaces, which are typically accessed via Windows environments. There are no command-line examples (such as Azure CLI, Bash, or PowerShell), but the workflow and screenshots implicitly assume a Windows-centric user base. There is no mention of Linux or cross-platform tooling, nor are there instructions for performing these tasks via non-Windows environments or automation scripts.

Recommendations:

Include Azure CLI or REST API examples for configuring CORS policies, which can be run on any platform (Windows, Linux, macOS).
Explicitly mention that the Azure portal and Power Platform interfaces are web-based and accessible from any OS, not just Windows.
Add notes or examples for users who may wish to automate these tasks from Linux or macOS environments.
If screenshots are used, consider including ones taken from browsers on Linux or macOS to reinforce cross-platform compatibility.
Reference cross-platform developer tools (e.g., VS Code, Azure CLI) where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on PowerShell DSC, with all examples and terminology centered around Windows-centric tools and patterns. There are no Linux-specific examples or mentions of Linux equivalents, and the only reference to Linux is an announcement about retirement, not usage or configuration.

Recommendations:

Provide examples or references for composing configurations with Linux nodes, if still supported.
Include Linux-native configuration management tools or patterns where applicable, or clarify the lack of support.
Balance references to PowerShell and Windows tools with equivalent Linux tools or workflows, or clearly state platform limitations.
If Linux support is deprecated, make this explicit at the beginning and suggest alternative solutions for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for importing a GraphQL API, but it gives equal prominence to PowerShell (a Windows-centric tool) and does not mention or provide native Linux shell (bash) or scripting examples. The prerequisites list Azure PowerShell as a required tool, which is primarily associated with Windows environments, and the PowerShell example is given its own dedicated section. There is no explicit Linux or bash example, nor is there mention of Linux-specific tooling or considerations.

Recommendations:

Add explicit bash or shell script examples for Linux users alongside PowerShell examples.
Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
In the prerequisites, note that Azure PowerShell is optional and primarily for users who prefer PowerShell, and highlight that Azure CLI is fully supported on Linux.
Ensure that any references to tools or commands are balanced between Windows and Linux environments, and avoid implying that PowerShell is required.
Consider adding a section or note for Linux/macOS users to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows-specific paths (e.g., D:\home\site\wwwroot) are mentioned before Linux equivalents, and the Kudu UI ZIP deploy method is explicitly unavailable for Linux. The use of PowerShell is presented as a primary method alongside Azure CLI, but PowerShell support is missing for several scenarios (with only CLI and API alternatives given). There is also a reliance on Azure portal navigation (Advanced Tools/Kudu), which is more familiar to Windows users. Linux-specific deployment nuances and parity in tooling are not fully addressed.

Recommendations:

Present Linux and Windows paths and behaviors in parallel, not with Windows first.
Clearly indicate when features are Windows-only and provide equivalent Linux workflows or alternatives, with step-by-step instructions.
Where PowerShell is not supported, provide Bash or shell script equivalents, especially for Linux users.
Include more Linux-centric examples and troubleshooting tips, such as using SCP, SFTP, or Linux-native tools for file transfer.
Clarify differences in Kudu UI and API availability between Windows and Linux, and link to Linux-specific documentation where appropriate.
Avoid defaulting to Windows terminology (e.g., drive letters, backslashes) in general explanations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by providing detailed, language-specific examples (C#, Java) for accessing certificates in Windows environments and referencing Windows certificate stores and tools. Linux guidance is less prominent, with Linux-specific code examples appearing later and only for C#. Other languages (Node.js, PHP, Python, Java) are not covered for Linux, and users are directed to external documentation. Windows tools and patterns (certificate store, environment variables, user profile settings) are discussed in depth, while Linux equivalents are less thoroughly explained.

Recommendations:

Provide Linux examples for all major supported languages (Node.js, Python, Java, PHP), not just C#.
Present Linux and Windows guidance in parallel or with equal prominence, rather than leading with Windows.
Include Linux-specific tools and patterns (e.g., OpenSSL, Linux file permissions, environment variable usage) where appropriate.
Where Windows-specific settings or tools are discussed (e.g., certificate store, user profile), provide Linux equivalents or clearly state when they are not applicable.
Avoid referencing only Windows certificate stores; explain Linux certificate handling (e.g., file-based, OpenSSL integration) in similar detail.
Ensure that all code samples and instructions are available for both platforms, or explicitly state any platform limitations.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-centric tools and workflows (such as Visual Studio Code and ASP.NET Core tutorials, which are traditionally associated with Windows development), and by omitting explicit Linux or cross-platform examples for creating and deploying web apps. There are no command-line examples (such as Bash, Azure CLI, or PowerShell), but the only development and deployment guidance references Windows-preferred technologies and patterns, with no mention of Linux alternatives or parity.

Recommendations:

Add explicit Linux-based examples for creating and deploying web APIs, such as using the Azure CLI and Bash.
Include references to Linux-friendly frameworks and editors (e.g., Python Flask, Node.js, or Java Spring Boot) alongside ASP.NET Core.
Provide deployment instructions using cross-platform tools (e.g., Azure CLI, GitHub Actions) rather than only referencing Visual Studio Code.
Clarify that the steps are platform-agnostic where possible, and call out any platform-specific differences.
Ensure that screenshots and UI references do not assume a Windows environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is traditionally associated with Windows environments) and its parity with CLI in the documentation can be seen as a Windows bias. There are no explicit Linux-specific examples, nor is there mention of Linux-native tools or shell environments. The order of presentation (Portal, CLI, then PowerShell) is neutral, but the presence of PowerShell-specific instructions and requirements, without any Linux shell or scripting examples, may disadvantage Linux users.

Recommendations:

Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell commands (e.g., bash) where appropriate.
Include a note or section for Linux users, clarifying that PowerShell is optional and not required on Linux.
Provide sample scripts using bash or other common Linux shells for tasks such as environment variable setup and command execution.
If referencing PowerShell, consider also referencing bash or zsh for parity, or clarify that PowerShell Core is cross-platform.
Add troubleshooting or environment setup notes specific to Linux (e.g., file path differences, installation steps for CLI tools on Linux).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides examples for both Azure CLI and Azure PowerShell, but there is a notable emphasis on PowerShell, which is traditionally associated with Windows environments. PowerShell is given equal prominence to Azure CLI, despite CLI being more cross-platform. There are no explicit Linux shell (bash) examples, and PowerShell is presented as a primary automation tool, which may not be as familiar or available to Linux users. Additionally, the prerequisites and instructions do not mention Linux-specific considerations or tools.

Recommendations:

Add explicit bash (Linux shell) examples alongside PowerShell, or clarify that Azure CLI commands are cross-platform and show them in a Linux context (e.g., using bash variables and syntax).
In the prerequisites, mention that Azure CLI works natively on Linux/macOS and provide installation links or notes for those platforms.
De-emphasize PowerShell as a primary automation tool for cross-platform scenarios, or at least note that it is available on Linux/macOS but may require separate installation.
Ensure that screenshots and UI instructions do not assume a Windows environment (e.g., file paths, dialogs).
Consider including a section or callout for Linux/macOS users with tips or troubleshooting relevant to those platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prominently featuring Windows-centric tools (such as Visual Studio, Azure PowerShell, and the App Service migration assistant for PowerShell scripts) and referencing them before or more frequently than cross-platform or Linux-native equivalents. There is a lack of explicit Linux or bash examples, and Linux-friendly tools or workflows (such as deploying from a Linux shell, using SCP/SFTP, or Linux-native editors) are not mentioned. The documentation assumes familiarity with Windows tools and does not provide parity for Linux users.

Recommendations:

Include explicit Linux/bash command examples alongside PowerShell and Windows tool references.
Mention and link to Linux-native deployment workflows (e.g., using SCP/SFTP, rsync, or bash scripts for deployment).
Provide parity in documentation for Linux-based editors and IDEs (e.g., JetBrains Rider, Eclipse, or command-line git workflows) alongside Visual Studio.
Clarify which tools and methods are cross-platform and which are Windows-only, and suggest alternatives for Linux users where appropriate.
Add references to Linux-specific documentation or quickstarts for deploying to Azure App Service.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by primarily referencing the Azure portal (a web UI, but often associated with Windows workflows), mentioning Azure PowerShell before Azure CLI, and not providing explicit Linux/Unix shell examples. While Azure CLI is mentioned, there are no concrete CLI or shell command examples, and no Linux-specific guidance or screenshots are provided. The documentation implicitly assumes a Windows-centric workflow.

Recommendations:

Provide explicit Azure CLI command-line examples for deploying and managing resources, with syntax suitable for Bash/Linux shells.
List Azure CLI before Azure PowerShell when mentioning alternative deployment methods, or present both equally.
Include screenshots or instructions that are platform-agnostic or show both Windows and Linux terminals where relevant.
Add a section or callout for Linux/macOS users, clarifying that all steps can be performed from any OS using Azure CLI.
Where possible, avoid language that implies the Azure portal is a Windows-only tool, and clarify its cross-platform nature.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page is heavily focused on Azure PowerShell cmdlets and Windows-centric tooling, with all examples and recommendations provided exclusively in PowerShell. There is no mention of Linux-native tools, Bash, or cross-platform scripting approaches. The guidance assumes the use of PowerShell and does not address how context switching or runbook management would be handled in Linux environments or with other automation languages supported by Azure Automation.

Recommendations:

Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used in Linux environments.
Include Bash or Python runbook examples to demonstrate context management outside of PowerShell.
Explicitly mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.) and clarify if context switching issues are unique to PowerShell or apply to other languages.
Reorganize sections to present cross-platform solutions first or in parallel, rather than focusing solely on Windows/PowerShell.
Reference Linux tools or patterns where appropriate, and ensure troubleshooting steps and error messages are relevant to both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page shows a moderate Windows bias. Kudu is described first as a Windows tool, with Linux support mentioned secondarily. FTP and WebDeploy (Windows-centric tools) are listed as primary deployment mechanisms, with no mention of Linux equivalents like SFTP or rsync. There are no explicit Linux shell or command-line examples, and the language-specific sections do not address Linux-specific deployment caveats or tools. While there is a GitHub Actions example that runs on Ubuntu, the overall framing and tool references favor Windows environments.

Recommendations:

Present Kudu's Linux and Windows behaviors equally, or mention Linux support first where relevant.
Include Linux-native deployment mechanisms (e.g., SFTP, rsync) alongside FTP and WebDeploy.
Add Linux shell (bash) examples for common deployment tasks, not just Azure CLI or YAML.
In language-specific sections, note any differences or best practices for Linux App Service plans.
Where possible, avoid listing Windows tools or patterns before their Linux equivalents, or present both together.
Clarify when instructions or tools are cross-platform, and provide links to Linux-specific documentation where available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page exhibits a strong Windows bias: all migration tools and examples focus exclusively on migrating from Windows environments, specifically from IIS servers, and make extensive use of Windows-specific tools such as PowerShell scripts and MSI installers. There is no mention of Linux-based .NET hosting environments (e.g., Apache, Nginx, Kestrel on Linux), nor are there migration paths or tools described for Linux-origin .NET apps. The documentation also references Windows containers but omits Linux container scenarios.

Recommendations:

Add guidance and examples for migrating .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel) to Azure App Service.
Include Linux-based migration tools or scripts, or clarify if such tools are not available.
Provide parity in documentation by listing Linux migration scenarios and tools alongside Windows ones, not just Windows-first.
If PowerShell scripts are provided, also offer Bash or cross-platform CLI equivalents where possible.
Mention and document migration to Linux-based App Service plans, not just Windows-based ones.
Clarify any limitations or differences in migration support between Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively discusses discovery of .NET web apps hosted on IIS web servers within VMware environments, which are Windows-centric technologies. There are no references to Linux-based hosting (e.g., Kestrel, Apache, Nginx) or examples for discovering .NET apps running on Linux. All discovery capabilities and dashboards are described in the context of Windows (IIS), and no Linux equivalents or instructions are provided.

Recommendations:

Include information about discovering .NET web apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx).
Provide parallel examples or instructions for Linux-based environments, including any differences in discovery steps or tooling.
Mention whether Azure Migrate supports Linux-hosted .NET apps, and if not, clarify this limitation explicitly.
Add references or links to resources for migrating or discovering .NET apps on Linux, if available.
Ensure future documentation covers both Windows and Linux scenarios equally, or clearly states platform limitations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page is generally platform-neutral but contains several instances of Windows bias. It references Windows-specific infrastructure and tools (such as KMS activation, Windows Update, and Windows Defender) without mentioning Linux equivalents or clarifying their relevance for non-Windows environments. Additionally, the only explicit example of a deployment model connection uses PowerShell (a Windows-centric tool) in the related content, and there are no Linux or cross-platform command examples provided.

Recommendations:

Where Windows-specific infrastructure (e.g., KMS, Windows Update, Windows Defender) is mentioned, clarify that these steps are only required for Windows VMs and provide equivalent guidance or a statement for Linux VMs (e.g., how to handle OS updates or security for Linux).
In related content and examples, provide parity by including links or instructions for Linux-based management (e.g., using Azure CLI, Bash scripts, or Linux tools) alongside PowerShell/Windows examples.
Explicitly state when a configuration step is only relevant for Windows workloads to avoid confusion for Linux users.
Add a section or note summarizing any differences or additional considerations for Linux-based deployments, especially regarding network access for updates, diagnostics, and security.
Review all tool and endpoint references to ensure Linux users are not left without guidance for their platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias. While both Azure CLI and Azure PowerShell examples are provided, PowerShell (a Windows-centric tool) is given equal prominence to the cross-platform Azure CLI, and no Linux-native scripting or shell examples (e.g., Bash) are shown. In the section on SKU availability, the 'Windows' example is listed before the 'Linux' example. The instructions and screenshots focus on the Azure Portal UI, which is platform-agnostic, but scripting automation leans toward Windows tools.

Recommendations:

Provide explicit Bash shell script examples for Linux users, especially in the automation section.
When listing platform-specific commands (such as SKU availability), alternate the order or present Linux and Windows examples side by side.
Clarify that Azure CLI commands are cross-platform and can be run on Windows, macOS, and Linux.
If referencing PowerShell, mention that PowerShell Core is available cross-platform, or provide Bash equivalents.
Consider including a table summarizing commands for both Windows (PowerShell) and Linux (Bash/CLI) environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows a Windows bias by presenting Windows-specific information and tools first, such as mentioning Windows SKU availability before Linux, and including Azure PowerShell examples (which are primarily used on Windows) without equivalent Bash or Linux shell script examples. The automation section provides both Azure CLI and PowerShell, but the PowerShell example is not accompanied by a Linux-native scripting example. The portal instructions and screenshots are Windows-centric, and there is no mention of Linux-specific considerations or UI differences. Additionally, the documentation does not provide parity in examples or guidance for Linux users, especially for scripting and automation.

Recommendations:

Present Linux and Windows options in parallel, or alternate which comes first to avoid 'windows_first' bias.
Provide Bash or shell script examples alongside PowerShell for automation tasks.
Include screenshots or notes for both Windows and Linux portal experiences if they differ.
Explicitly mention any Linux-specific considerations, such as differences in deployment, configuration, or tool usage.
Ensure that all command-line examples (especially for automation) are cross-platform or have equivalents for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates several forms of Windows bias. Windows installation and GUI instructions are consistently presented before Linux equivalents, and some troubleshooting steps (such as using PowerShell's Test-NetConnection) are only shown for Windows. Windows-specific tools and patterns (e.g., GUI, MSI installer, PowerShell commands) are described in detail, while Linux alternatives are sometimes less detailed or omitted (e.g., no Linux equivalent for Test-NetConnection, no Linux GUI). Some instructions and troubleshooting steps lack Linux-specific guidance or examples.

Recommendations:

Present Linux and Windows instructions in parallel or alternate which comes first to avoid 'windows_first' bias.
For every PowerShell or Windows-specific command (e.g., Test-NetConnection), provide an equivalent Linux command (e.g., nc, curl, or telnet) and example.
Where a GUI is not available on Linux, offer equivalent CLI workflows and highlight any feature gaps.
Ensure troubleshooting sections include Linux-specific tools and commands for connectivity and DNS checks (e.g., use 'nc', 'dig', or 'host').
Expand Linux installation and usage instructions to match the detail level of Windows instructions.
Explicitly note any feature parity gaps (such as lack of GUI on Linux) and, where possible, provide workarounds or roadmap information.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias in several ways: Windows-based deployment methods (such as Web Deploy) are featured with explicit instructions and troubleshooting, while Linux equivalents are not discussed or are only mentioned in passing. Examples and templates often default to ASP.NET (a Windows-centric technology), and when deployment agent OS is specified, 'windows-latest' is highlighted for Web Deploy scenarios. There is little to no coverage of Linux-native deployment tools or troubleshooting for Linux agents, and the documentation assumes familiarity with Windows deployment patterns.

Recommendations:

Provide parallel Linux-based deployment examples, especially for scenarios where Windows-specific tools (like Web Deploy) are discussed.
When introducing deployment templates or tasks, include examples for both Windows and Linux app types, and clarify any differences in configuration or prerequisites.
Highlight Linux agent compatibility and limitations for each deployment method, and offer troubleshooting steps for Linux agents where relevant.
Balance the focus on ASP.NET with examples for other stacks (Node.js, Python, Java) and clarify when instructions are Windows-specific.
Reference Linux-native deployment tools or patterns (such as rsync, SCP, or container-based deployments) where appropriate.
In FAQ and troubleshooting sections, address common issues for both Windows and Linux agents equally.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides command-line examples for Azure CLI (cross-platform) and Azure PowerShell (Windows-centric), but does not include any Linux- or macOS-specific shell examples (e.g., Bash scripting, environment variable handling, or FTP/Git usage from Linux). In the section discussing shell-specific issues (escaping $ in Bash), only a note is provided, without a concrete Bash example. The PowerShell tab is always present, even when it is not supported, and is listed before the portal tab, reinforcing a Windows-first pattern.

Recommendations:

Add explicit Bash/Linux shell examples for relevant commands, especially where shell escaping or environment differences matter (e.g., using git remote add with $ in the username).
Include examples of using standard Linux tools (e.g., curl, lftp, git) for FTP/S and Git deployments.
Where PowerShell is not supported, consider omitting the tab or clearly indicating its absence, and provide parity by including a Bash/Linux tab.
In tabbed command sections, alternate the order or default to CLI (cross-platform) or Bash before PowerShell to avoid Windows-first perception.
Add troubleshooting notes or examples for common Linux/macOS issues (e.g., file permissions, SSH key usage, credential storage).

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 PowerShell-based examples and instructions for restoring deleted Azure App Service apps. All command-line operations are shown using the Az PowerShell module, with no mention of cross-platform alternatives such as Azure CLI, Bash, or REST API. This approach assumes users are on Windows or have PowerShell installed, and does not address Linux-native workflows or tools. The documentation also introduces PowerShell before any other automation or scripting options, and omits Linux-specific guidance or examples.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash shell examples where applicable, especially for scripting or automation scenarios.
Mention REST API options for restoring deleted apps, providing sample requests and responses.
Clearly state that the PowerShell module can be used cross-platform (if true), or provide installation instructions for non-Windows environments.
Reorganize sections to present cross-platform or platform-neutral options (such as Azure CLI or REST API) before or alongside PowerShell.
Explicitly acknowledge Linux/macOS users and provide parity in instructions and troubleshooting steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows environments, specifically Azure App Service on Windows with iisnode. All configuration, troubleshooting, and examples are tailored for Windows, referencing Windows-specific tools (e.g., iisnode, web.config, named pipes, Win32 error codes, Kudu CMD/PowerShell, d:\ paths). There are no Linux equivalents or cross-platform instructions/examples, and Linux troubleshooting or deployment patterns are not mentioned.

Recommendations:

Add a parallel section or a separate guide for Node.js on Azure App Service for Linux, covering best practices and troubleshooting steps relevant to Linux environments.
Provide Linux-specific examples for common tasks (e.g., configuration, debugging, log file locations, process management), using Linux tools and conventions (e.g., bash, systemd, Linux file paths).
Reference Linux equivalents for Windows-specific tools and patterns (e.g., use of pm2 or systemd instead of iisnode, nginx/apache instead of IIS, environment variables instead of web.config).
When mentioning troubleshooting steps (e.g., checking logs, profiling, debugging), include instructions for both Windows and Linux platforms, or clearly indicate which steps are platform-specific.
Avoid assuming the use of Windows paths, tools, or error codes; provide cross-platform alternatives or clarify when something is Windows-only.
Link to official Azure documentation for Node.js on Linux App Service where appropriate.

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 or cross-platform development environments (e.g., Visual Studio Code, CLI, or deployment to App Service (Linux)). PowerShell and Windows-specific tools are used exclusively, with no mention of Bash, Azure CLI, or Linux-compatible workflows.

Recommendations:

Add parallel instructions and screenshots for Linux/macOS users, including using Visual Studio Code or JetBrains Rider.
Include examples using Azure CLI and Bash for all steps currently shown with PowerShell or Visual Studio GUI.
Provide guidance for deploying to Azure App Service (Linux) in addition to App Service (Windows).
Document how to run and debug the sample app using .NET CLI commands (dotnet run, dotnet publish) instead of only Visual Studio.
Show how to configure and connect to Azure SQL Database using cross-platform tools (e.g., Azure Data Studio, sqlcmd in Bash, or Azure CLI).
Explicitly state which steps are Windows-only and offer alternatives for other platforms where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias by providing only PowerShell-based CLI examples for all command-line operations, including REST API calls, ARM template deployment, and role assignments. There are no examples using Bash, Azure CLI (az), or Linux-native tools. File paths use Windows-style backslashes, and all scripting assumes a PowerShell environment. The only non-PowerShell code sample is a Python runbook, but even this relies on environment variables typically set in Azure Automation, not on Linux shell usage. There are no explicit instructions or examples for Linux users or those using Bash or Azure CLI.

Recommendations:

Add equivalent examples using Azure CLI (az) commands for all PowerShell examples, especially for adding managed identities, assigning roles, and deploying ARM templates.
Provide Bash shell script examples for REST API calls using curl or httpie, including authentication steps for Linux environments.
Use platform-neutral file path syntax (forward slashes or mention both styles) when referring to file locations.
Explicitly mention that all PowerShell examples can be run on PowerShell Core on Linux, or provide alternative commands for Bash users.
Include a section or callouts for Linux/macOS users, highlighting any differences or additional steps required.
When listing options (e.g., portal, PowerShell, REST API, ARM template), present Azure CLI and Bash examples alongside or before PowerShell to avoid 'windows_first' ordering.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias in the 'Server level (Windows apps only)' section, where only Windows/IIS (web.config) authorization is described, with no equivalent Linux example or mention of how to achieve similar functionality on Linux-based App Service plans. The use of Kudu and web.config is specific to Windows, and Linux alternatives are not discussed. Additionally, the section order presents the Windows-specific method before more general or cross-platform approaches.

Recommendations:

Add a section describing how to implement server-level authorization for Linux-based App Service apps, such as using .htaccess for Apache, nginx configuration, or middleware in common Linux web frameworks.
Explicitly state the lack of server-level authorization support on Linux and suggest application-level or identity provider-level alternatives.
Reorder the authorization section to present cross-platform or provider-level solutions before platform-specific (Windows) solutions.
Where platform-specific tools (like Kudu or web.config) are mentioned, provide Linux equivalents or clear guidance for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. PowerShell is given equal prominence to Azure CLI, but no Bash or Linux shell scripting examples are provided. The list of recommended FTP/S clients includes two Windows-focused tools (Visual Studio, WinSCP) and only one cross-platform option (Cyberduck), with no mention of Linux-native clients (e.g., lftp, FileZilla). There are no explicit Linux command-line or desktop environment instructions, and troubleshooting and connection examples reference Windows tooling and patterns.

Recommendations:

Add Linux/Bash shell scripting examples alongside PowerShell for all CLI operations.
Include Linux-native FTP/S clients (e.g., lftp, FileZilla, GNOME Files) in the list of recommended clients.
When listing tools or commands, alternate the order or provide parallel examples for both Windows and Linux users.
Add troubleshooting steps and screenshots relevant to Linux environments.
Clarify that Azure CLI commands work cross-platform and provide sample terminal output from Linux shells.
Avoid assuming the use of Windows-specific tools (such as Visual Studio) as the default workflow.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. It references Windows-specific deployment tools (such as Web Deploy/MSDeploy) and patterns (like Visual Studio deployment) without providing equivalent Linux-native alternatives or examples. The documentation mentions 'Web Deploy' and 'MSBuild'—both Windows-centric tools—without clarifying Linux support or alternatives. In the Azure Pipelines section, there is detailed discussion of Windows agent behavior, but no comparable detail for Linux agents. There are no explicit Linux command-line or scripting examples, and the documentation does not mention Linux-native FTP or deployment tools, nor does it provide parity in troubleshooting or agent configuration for Linux users.

Recommendations:

Include Linux-native deployment tool examples (e.g., lftp, curl, git CLI) for verifying FTP or Git access.
When referencing Visual Studio or MSDeploy, also mention cross-platform alternatives (such as VS Code, Azure CLI, or Git) and clarify their support on Linux.
In sections discussing Azure Pipelines, provide explicit guidance for both Windows and Linux agents, including troubleshooting steps and behavioral notes for Linux.
Add Linux-specific troubleshooting steps and examples for confirming authentication failures (e.g., using Linux FTP clients or Git from a Linux shell).
Ensure that any mention of Windows tools or patterns is accompanied by Linux equivalents, or at least clarify if a feature is Windows-only.

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 deployment and configuration patterns for ASP.NET apps in Azure App Service. All runtime version examples reference Windows file paths and tools (Kudu, CMD, PowerShell), with no mention of Linux equivalents or how to perform these tasks on Linux App Service plans. There are no Linux-specific examples or guidance, and Windows tools and patterns are presented as the default.

Recommendations:

Add equivalent instructions and examples for Linux App Service plans, including how to check .NET runtime versions and access diagnostic tools on Linux.
When referencing tools like Kudu, CMD, or PowerShell, clarify their availability (Windows-only) and provide alternatives for Linux (e.g., SSH, Bash).
Include Linux file paths and commands where appropriate, or explicitly state when a feature is Windows-only.
Structure sections to address both Windows and Linux scenarios, or clearly indicate which instructions apply to which OS.
Add a table or section summarizing feature parity and differences between Windows and Linux App Service for ASP.NET apps.

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 Azure CLI (cross-platform) and Azure PowerShell (Windows-centric), several features and examples are either Windows-only or presented with a Windows-first perspective. Some advanced configuration options (like default documents, virtual directories, and handler mappings) are explicitly stated as Windows-only, with no Linux equivalents or workarounds mentioned. PowerShell examples are detailed and extensive, while Linux-specific nuances are only briefly mentioned or omitted. There is also a lack of parity in bulk editing capabilities between PowerShell and CLI, and some CLI examples use Windows-style paths or escape sequences without clear Linux guidance.

Recommendations:

Clearly indicate feature parity or lack thereof for both Windows and Linux throughout the documentation, especially for features that are Windows-only.
Where features are Windows-only, suggest Linux alternatives or workarounds, or explicitly state that no equivalent exists.
Provide Linux-specific examples and guidance, especially for CLI commands (e.g., path formats, escape characters, file handling).
Balance the depth of PowerShell and CLI examples, ensuring that Linux users have equally detailed instructions.
For sections where PowerShell cannot perform an action (e.g., bulk editing via JSON), suggest CLI as a cross-platform alternative.
Add a summary table or section at the top that lists which features are available on Windows, Linux, or both.
When referencing configuration files or paths, provide both Windows and Linux path examples where applicable.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by referencing Azure Storage Explorer (a GUI tool with a primary focus on Windows) for uploading files and generating SAS tokens, and by linking to instructions that default to Windows tabs. There are no explicit Linux or cross-platform CLI alternatives provided for these steps, even though the rest of the guide uses Azure CLI (which is cross-platform). This may leave Linux users unclear on how to perform these actions without a Windows environment.

Recommendations:

Provide explicit Azure CLI (or azcopy) commands for uploading files to Azure Storage and generating SAS tokens, as these tools are cross-platform and suitable for Linux users.
When referencing Azure Storage Explorer, clarify its availability on Linux and macOS, or provide alternative instructions for users who prefer CLI tools.
Avoid linking to documentation pages with Windows-specific tabs as the default, or ensure that Linux/macOS instructions are equally prominent.
Add a section or note summarizing cross-platform options for all major steps, especially for file upload and SAS generation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows. Gateway-required virtual network integration is explicitly stated as unsupported for Linux apps, and all operational and troubleshooting examples (such as using PowerShell's Test-NetConnection and Windows tools like netstat) are Windows-centric. There are no Linux equivalents or guidance for Linux users, and Linux scenarios are not addressed.

Recommendations:

Clearly indicate at the beginning that gateway-required virtual network integration is not supported for Linux apps, and provide alternative guidance or links for Linux users.
Where troubleshooting steps are provided using Windows tools (e.g., Test-NetConnection, netstat), include equivalent Linux commands (e.g., nc, curl, ss, netstat) for users managing resources from Linux VMs.
If possible, provide a comparison table or section summarizing feature support and operational differences between Windows and Linux App Service plans.
In sections that mention using the Azure portal or Kudu, clarify any differences in experience or availability for Linux-based apps.
For all code or command-line examples, provide both Windows and Linux variants where applicable, or explicitly state when a feature 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 are often presented first or in greater detail. PowerShell commands are provided alongside Bash, but Windows-specific tools (e.g., Kudu, IIS, .NET Framework) and patterns are described in more depth. Some advanced configuration and diagnostic sections (e.g., customizing memory, CPU, health ping, machine key injection) are detailed only for Windows containers, with no Linux equivalents. Linux instructions are present but sometimes less prominent or detailed.

Recommendations:

Ensure all advanced configuration sections (memory, CPU, health ping, machine key injection) have Linux equivalents or explicitly state if not supported.
When presenting cross-platform commands, alternate the order (sometimes Linux/Bash first) or present them side-by-side.
Expand Linux-specific diagnostic and troubleshooting guidance to match the depth of Windows sections (e.g., Kudu, SSH, logs).
Clarify feature parity: if a feature is Windows-only, explicitly state so; if available on Linux, provide matching instructions.
Balance the use of PowerShell and Bash examples, and ensure Linux-native tools and patterns (e.g., systemd, OpenSSH, Linux file paths) are described as thoroughly as Windows ones.
Where Windows tools (e.g., IIS, .NET Framework) are mentioned, provide Linux analogs or note their absence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation exhibits a mild Windows bias by presenting Windows-specific instructions and tools (such as Kudu, CMD, and PowerShell) before their Linux equivalents, and by referencing Visual Studio and Windows deployment patterns as defaults. Linux instructions are present and generally comprehensive, but Windows tools and workflows are often mentioned first or exclusively, which may give the impression that Windows is the primary or preferred platform.

Recommendations:

Ensure parity in example order: Present Linux and Windows instructions side-by-side or alternate which platform is presented first to avoid the perception of a primary platform.
Balance tool references: When referencing tools like Kudu (which is Windows-centric), also mention or link to the equivalent Linux troubleshooting or management tools (e.g., SSH, Oryx logs).
Reduce Visual Studio/Windows defaults: When describing deployment workflows, clarify that Visual Studio is one option and highlight cross-platform alternatives (e.g., VS Code, CLI-based deployment) equally.
Expand Linux-specific guidance: Where Windows-specific tools (like PowerShell or Kudu) are mentioned, ensure Linux alternatives are described with equal detail and visibility.
Review terminology: Avoid phrases like 'already have all the supported .NET Core versions installed' for Windows without clarifying the Linux equivalent, to prevent assumptions about platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on deploying Windows containers, with all examples, variables, and instructions referencing Windows-specific settings (e.g., 'windows-latest' build agents, Web App for Containers (Windows), .NET/Windows app). There are no Linux container examples or references, and the documentation does not mention how to adapt the process for Linux-based containers or App Service for Linux.

Recommendations:

Provide parallel examples and instructions for deploying Linux containers, including YAML snippets using 'ubuntu-latest' or other Linux build agents.
Mention both Windows and Linux App Service types, and clarify which steps or settings differ between them.
Include notes or sections on how to adapt the pipeline for Linux-based applications, such as .NET Core or Node.js apps.
Add Linux container deployment variables and sample values alongside the Windows ones.
Explicitly state in the introduction that the guide is Windows-specific, or broaden the scope to cover both platforms equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell instructions, but there is a noticeable Windows bias. PowerShell is presented as a primary method alongside CLI, and several instructions (such as using a 'local PowerShell terminal') assume a Windows environment. There are no explicit Linux shell or macOS terminal examples for PowerShell steps, and troubleshooting references Windows-specific errors (e.g., native modules lacking Windows binaries). The documentation does not clarify cross-platform differences or provide parity for Linux users in PowerShell sections.

Recommendations:

Explicitly state that Azure CLI and Git commands work identically on Linux, macOS, and Windows, and provide example terminal commands for Linux/macOS where PowerShell is used for Windows.
For PowerShell sections, clarify that PowerShell Core is cross-platform, or provide Bash equivalents for Linux/macOS users.
In troubleshooting, avoid highlighting Windows-specific errors (such as native module Windows binary issues) without also mentioning common Linux/macOS issues.
Wherever a 'local PowerShell terminal' is referenced, also mention 'Bash or other shell' for Linux/macOS users.
Ensure that all code snippets and instructions are tested and presented for both Windows and Linux/macOS environments, or clearly indicate any platform-specific steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits some Windows bias, particularly in the .NET and Python sections. Windows-specific tools (Visual Studio, Azure PowerShell) are listed before cross-platform or Linux-native options. In the .NET section, Windows tools are prioritized, and Azure PowerShell is mentioned without an equivalent Azure CLI example. In the Python section, the quickstart links default to 'windows' tabs, even when Linux is supported. Linux-specific instructions are less prominent or missing in some cases. Other stacks (Java, Node.js, PHP) are more Linux-friendly, but overall, Windows tools and patterns are often presented first or exclusively.

Recommendations:

Ensure that for every Windows-specific tool or example (e.g., Visual Studio, Azure PowerShell), there is an equivalent Linux-friendly or cross-platform alternative (e.g., Azure CLI, VS Code) presented with equal prominence.
In quickstart tables, avoid defaulting to 'windows' tabs or pivots; instead, provide both Windows and Linux options side by side, or default to the most cross-platform approach.
For .NET, add explicit Azure CLI examples and ensure Linux development environments are covered as thoroughly as Windows.
Review all quickstart and tutorial links to ensure Linux instructions are not hidden behind secondary tabs or pivots.
Where possible, use neutral language and tool ordering (e.g., list VS Code and CLI before Visual Studio and PowerShell) to avoid implying Windows is the default or preferred environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by focusing on Microsoft-centric authentication libraries (MSAL, Microsoft.Identity.Web) and ASP.NET Core, which are most commonly associated with Windows development. Visual Studio and IDE integration are mentioned as benefits, but there is no mention of Linux development environments, cross-platform IDEs, or equivalent authentication solutions for non-Windows stacks. No Linux-specific examples, tools, or patterns are provided, and the documentation assumes familiarity with Windows-first technologies.

Recommendations:

Include examples and guidance for Linux-based development environments, such as using VS Code or JetBrains Rider on Linux.
Mention and provide parity for authentication libraries and patterns commonly used in Linux or cross-platform stacks (e.g., Node.js, Python, Java, PHP).
Highlight how App Service authentication works for apps deployed from Linux containers or running on App Service for Linux.
Add references or links to documentation for configuring authentication in non-Windows environments.
Clarify that the authentication solutions are cross-platform where applicable, and provide explicit instructions or examples for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell examples exclusively, referencing PowerShell runbooks and cmdlets as the primary automation method, and omitting equivalent CLI or Linux-native instructions. The 'Next steps' section prioritizes PowerShell tutorials and references, with only a single Python runbook tutorial mentioned. There are no examples or instructions for using Azure CLI, Bash, or Linux-native tools to perform the same tasks, nor is there guidance for users on non-Windows platforms.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell cmdlet instructions, especially for key management and account creation.
Include Bash shell examples where appropriate, particularly for Linux/macOS users.
Balance the 'Next steps' section by providing links to both PowerShell and Azure CLI tutorials, as well as Python and other cross-platform runbook types.
Explicitly state that all steps can be performed from any OS via the Azure portal, and clarify any OS-specific requirements.
Reference cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell, and avoid assuming PowerShell as the default automation tool.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a bias toward Windows-centric workflows and tools. It focuses exclusively on Azure App Service (which is often associated with Windows hosting, though it supports Linux), .NET Blazor applications, and Azure CLI tooling without providing any Linux-specific or cross-platform deployment/management examples. There are no references to Linux-native tools, shell environments, or alternative deployment methods (such as using Bash scripts, Docker, or Linux-based CI/CD pipelines). The troubleshooting and log viewing sections also only mention the Azure Portal, not command-line or Linux-native monitoring options.

Recommendations:

Add explicit notes or examples for deploying and running the sample app on Linux-based App Service plans, including any differences in configuration or troubleshooting.
Provide Linux/Bash shell command examples alongside Azure CLI commands, and clarify that azd and az CLI are cross-platform.
Include references to Linux-native tools for log viewing and troubleshooting, such as using SSH, Kudu, or Azure CLI log streaming from Bash.
Mention Docker-based deployment or containerization as an alternative, which is common in Linux environments.
Clarify that App Service supports both Windows and Linux, and provide guidance for choosing the appropriate runtime stack.
Expand the sample to include or reference non-.NET stacks (e.g., Node.js, Python) to ensure parity for Linux-first developers.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a strong bias towards Windows and PowerShell. All migration scripts and runbook examples are provided exclusively in PowerShell, with no mention of Bash, Python, or other Linux-native scripting options. The instructions for Hybrid Runbook Worker installation and migration consistently link to Windows-first tabs or examples, and there is no step-by-step guidance or code samples tailored for Linux users. The documentation assumes PowerShell as the default automation tool, which may not be familiar or preferred by Linux administrators.

Recommendations:

Provide equivalent migration scripts and runbook examples in Bash and/or Python, and document how to execute them on Linux-based Automation accounts.
Include explicit Linux/Unix instructions and screenshots alongside Windows/PowerShell examples, ensuring parity in all step-by-step guides.
When referencing installation or configuration steps for Hybrid Runbook Workers, ensure both Windows and Linux tabs are present and that Linux is not secondary or omitted.
Mention and, where possible, demonstrate the use of cross-platform tools (such as Azure CLI or REST API) for asset migration and automation tasks.
Clarify any limitations or differences for Linux users, and provide workarounds or alternatives where PowerShell is not available or preferred.

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 provided alongside Azure CLI and portal instructions, with equal prominence, but there is no mention of Linux-native scripting or shell environments (e.g., Bash). The use of Windows-specific tools and configuration files, such as Web.config and applicationInitialization, is presented without Linux or cross-platform alternatives. Troubleshooting and advanced configuration sections reference Windows file paths (D:\home\LogFiles\eventlog.xml) and IIS-specific features, which may not apply to Linux-based App Service environments. Additionally, the auto swap feature is noted as unsupported on Linux, but no Linux-specific guidance or alternatives are offered.

Recommendations:

Add explicit Bash or Linux shell examples where scripting is demonstrated, especially alongside Azure CLI commands.
Clearly indicate when features (such as auto swap) are not supported on Linux, and provide alternative workflows or mitigations for Linux users.
When referencing configuration files like Web.config or IIS features, include parallel instructions for Linux-based apps (e.g., using app settings, startup scripts, or other Linux-appropriate mechanisms).
In troubleshooting sections, mention log file locations and diagnostic steps for both Windows and Linux App Service environments.
Review all examples and ensure that Linux users are not left without actionable guidance, especially where Windows/IIS-specific features are discussed.

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 PowerShell examples for per-app scaling, referencing only Windows-centric tools (Az PowerShell cmdlets), and omitting equivalent Linux-native or cross-platform CLI examples. The PowerShell section appears first and is the only command-line example provided, with no mention of Azure CLI (az), Bash, or other Linux-friendly approaches. This may hinder accessibility for Linux users or those working in non-Windows environments.

Recommendations:

Add equivalent Azure CLI (az) examples for all PowerShell commands, showing how to enable per-app scaling and configure worker counts using cross-platform tools.
Include Bash shell script examples where appropriate, especially for configuring app settings via REST or CLI.
Explicitly mention that PowerShell commands can be run cross-platform (if true), or clarify any platform limitations.
Reorder sections or provide parallel examples so that Linux/cross-platform tools are not secondary to Windows/PowerShell.
Reference Linux tools and workflows in the narrative, not just in code samples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. Windows paths, environment variables (e.g., %HOME%), and drive letters (e.g., D:\home\...) are used as primary examples, with Linux equivalents only mentioned secondarily or not at all. The instructions for file exclusion and directory navigation use Windows-style paths and terminology. The use of Kudu DebugConsole and FTP is described in a Windows-centric way. There are references to Azure PowerShell and Windows-specific features, while Linux command-line or scripting examples are missing. Although Linux is mentioned in some tables, practical Linux-specific instructions or examples are not provided.

Recommendations:

Provide Linux-specific examples alongside Windows examples, especially for file paths (e.g., /home/site/wwwroot instead of D:\home\site\wwwroot).
When referencing environment variables, include both Windows (%HOME%) and Linux ($HOME) syntax.
Show how to upload or edit the _backup.filter file using Linux tools (e.g., SCP, SFTP, or Linux shell commands) in addition to FTP/Kudu.
Include sample commands or scripts for Linux users where PowerShell or Windows tools are mentioned.
Ensure that all instructions referencing directories, file paths, or environment variables are presented in both Windows and Linux formats.
Clarify any platform-specific limitations or differences in backup/restore behavior for Linux-based App Service apps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All code examples, instructions, and prerequisites are written for PowerShell, with no mention of Linux, Bash, or cross-platform alternatives. The only VM creation link points to a Windows VM via PowerShell, and there are no references to Linux VMs or Bash/Azure CLI usage. This creates a strong Windows bias and may alienate users working in Linux or cross-platform environments.

Recommendations:

Provide equivalent examples using Azure CLI (az) and Bash scripts, especially for steps like assigning permissions, creating runbooks, and managing VMs.
Include links to both Windows and Linux VM quickstart guides, not just Windows/PowerShell.
When listing prerequisites, mention both PowerShell and Azure CLI as supported options.
Show how to create and trigger runbooks using Bash or Azure CLI, not just PowerShell.
Add a section or callouts for Linux users, clarifying any differences or additional steps.
Ensure that runbook examples are language-agnostic where possible, or provide both PowerShell and Python (or Bash) samples.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias. It references PowerShell as a method to query Azure activity logs, and highlights integration with Visual Studio (a Windows-centric tool) for Application Insights. There are no explicit Linux or cross-platform command-line examples, nor are Linux-specific tools or workflows mentioned. The order of tool mentions (PowerShell before CLI) and the absence of Linux/Unix shell examples further reinforce the bias.

Recommendations:

When listing command-line options (e.g., for querying activity logs), mention Azure CLI and Bash examples before or alongside PowerShell.
Include examples or references for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform editors like VS Code.
Balance tool mentions: if Visual Studio is referenced, also mention cross-platform IDEs/editors (VS Code, JetBrains Rider, etc.) where possible.
Explicitly state that all monitoring features are available and supported on both Windows and Linux App Service plans.
Add troubleshooting/log streaming examples for both Windows and Linux App Service environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows-based App Service environments. It consistently uses Windows environment variables (e.g., %SystemDrive%, %ResourceDrive%, %HOME%), Windows file path conventions (e.g., d:\, c:\), and references to Windows-specific features such as IIS, ASP.NET, COM components, and the Windows registry. There are no Linux-specific examples, environment variables, or file system conventions. The only mention of Linux is a brief note at the beginning, with no further detail or parity in the rest of the document.

Recommendations:

Provide equivalent Linux examples and explanations for file paths, environment variables, and storage locations (e.g., use $HOME, /home/site/wwwroot, etc.).
Include Linux-specific details for file access, temporary storage, and network configuration.
Add sections or callouts that describe how the described functionality (e.g., diagnostic logs, process execution, registry access) maps to Linux containers in App Service.
Mention Linux tools and patterns (e.g., Bash, shell scripts, Linux permissions) alongside Windows tools (e.g., PowerShell, IIS).
Structure the documentation so that Linux and Windows information are presented in parallel, or clearly indicate when information is Windows-only.
Clarify which features (such as registry access, IIS, COM components) are not applicable or have Linux equivalents, and provide guidance for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing features and tooling (such as Process Explorer and diagnostic memory dumps) that are only available for Windows applications, without mentioning Linux equivalents or alternatives. Windows-specific capabilities are described in detail, while Linux users are left without guidance for similar tasks. Additionally, some notes and features are explicitly marked as Windows-only, and there are no Linux-specific examples or parity notes.

Recommendations:

For every Windows-specific feature (e.g., Process Explorer, diagnostic memory dumps), explicitly state whether a Linux equivalent exists. If not, provide alternative Linux troubleshooting or monitoring steps.
Add Linux-specific examples or instructions where features or workflows differ, especially for diagnostics and process monitoring.
When describing features, avoid presenting Windows capabilities first or exclusively; instead, structure sections to address both Windows and Linux users equally.
Where a feature is Windows-only (e.g., x-ms-auth-internal-token header), clarify what Linux users should do instead, or provide a workaround if possible.
Include screenshots or walkthroughs for Linux App Service where the portal experience or available options differ.

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 Windows PowerShell, and Windows-centric tools and paths (e.g., C:\, WindowsFeature) are referenced exclusively. There are no examples or instructions for compiling DSC configurations from Linux or using cross-platform tools. The documentation also refers to Windows PowerShell as the primary or only scripting environment, and does not mention Linux equivalents or alternatives.

Recommendations:

Add examples and instructions for compiling DSC configurations from Linux environments, using cross-platform PowerShell (pwsh) where possible.
Clarify which steps and cmdlets are supported on Linux and which are Windows-only.
Provide Linux file path examples (e.g., /home/user/configs) alongside Windows paths.
Mention any limitations or differences for Linux users up front, especially in sections where only Windows is supported.
If Linux support is deprecated or limited (as suggested by the Linux retirement announcement), make this explicit and provide guidance or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page exhibits a Windows bias by focusing on Windows-specific tools, commands, and examples. It references Windows registry paths, uses Windows-centric terminology (e.g., Patch Tuesday), and provides instructions and examples that are only applicable to Windows-based App Service instances. There is a lack of equivalent Linux-based examples or guidance, and the documentation does not clarify differences or provide parity for Linux App Service environments.

Recommendations:

Add explicit sections or notes for Linux-based App Service instances, including how OS and runtime patching works for Linux.
Provide Linux-specific examples for querying OS and runtime versions (e.g., using /etc/os-release, lsb_release, or other Linux commands in Kudu Bash).
Clarify which instructions or commands apply only to Windows and which to Linux, or provide side-by-side examples for both platforms.
Avoid referencing Windows registry or tools (such as reg query) without Linux equivalents, or provide alternative Linux commands.
Mention Linux patching cadence and mechanisms if they differ from Windows, and link to relevant Linux documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows-first bias by frequently specifying features as 'Windows apps only' (e.g., Application Insights integration, Proactive CPU monitoring, Proactive auto-healing, Navigator) without providing Linux equivalents or alternatives. Some advanced diagnostic tools and workflows are described as available only for Windows, and there are no Linux-specific troubleshooting examples or command-line instructions. Linux support is mentioned but not detailed, and Linux-specific features are less emphasized or lack parity in explanation.

Recommendations:

Provide equivalent Linux examples and workflows where possible, or clearly state limitations and suggest alternative approaches for Linux users.
Include Linux-specific troubleshooting steps, screenshots, and command-line (e.g., Bash) instructions alongside or before Windows/Powershell examples.
Highlight Linux diagnostic tools and features with the same level of detail as Windows features, including proactive monitoring and auto-healing capabilities.
Where features are Windows-only, offer guidance or workarounds for Linux users, and maintain parity in documentation structure and depth.
Add a comparison table summarizing feature availability and differences between Windows and Linux App Service environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-style paths (e.g., D:\home), describing behaviors and folder structures in Windows terms, and omitting equivalent Linux paths or behaviors. There are no Linux-specific examples or instructions, and tools/extensions mentioned (such as Azure Web Apps Disk Usage) are not clarified for Linux. The feature is described as unsupported for Linux containers, but there is little guidance for Linux App Service users overall.

Recommendations:

Include Linux-specific examples and path references (e.g., /home/site/wwwroot) alongside Windows examples.
Clarify which features and tools (such as Azure Web Apps Disk Usage) are available or have equivalents on Linux App Service.
Provide explicit instructions or notes for Linux App Service users, even if only to state limitations or alternatives.
Where features are unsupported on Linux, offer links or guidance to Linux-compatible alternatives (such as App Cache or KuduLite).
Ensure that all code snippets, environment variable checks, and troubleshooting steps are presented for both Windows and Linux environments where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several areas: IP restriction features and configuration examples are described specifically for 'App Service on Windows', with references to Windows-specific tools (web.config and IIS dynamicIpSecurity). There are no equivalent Linux examples or mentions of how to achieve similar security configurations on App Service for Linux. This may leave Linux users without guidance for important security features.

Recommendations:

Provide parallel instructions and examples for App Service on Linux wherever Windows-specific features (such as IP restrictions via web.config) are mentioned.
Explicitly state which features are Windows-only and offer alternative approaches or workarounds for Linux users.
Include Linux-relevant configuration files (such as nginx.conf or .htaccess) and command-line examples where appropriate.
Review the documentation for other sections where Windows tools or patterns are referenced and ensure Linux parity in guidance and examples.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides extensive examples using Azure PowerShell and references to PowerShell modules, which are most commonly used on Windows. In several sections, PowerShell is given equal or greater prominence than cross-platform tools, and there is no explicit mention of Linux-specific shell usage or guidance for Linux users. The documentation assumes familiarity with Windows-centric tools and patterns, potentially disadvantaging Linux users.

Recommendations:

Explicitly state that Azure CLI and ARM templates are fully cross-platform and provide shell-agnostic examples (e.g., Bash, zsh) where possible.
For PowerShell examples, clarify that PowerShell Core is available on Linux and macOS, and provide equivalent Bash or shell script examples for common tasks.
Avoid using PowerShell as the only scripting example; always pair with Bash/Azure CLI where possible.
Add notes or sections highlighting any differences or prerequisites for Linux users, such as installation steps for Azure CLI or PowerShell Core on Linux.
Review and adjust the order of examples so that cross-platform tools (Azure CLI, ARM templates) are presented before or alongside PowerShell, rather than after.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. Windows platforms and tools are consistently mentioned first in lists (e.g., 'Windows code' before 'Linux code'), and deployment via Visual Studio (a Windows-centric tool) is highlighted as a primary method. While Linux and Bash are acknowledged, there are no Linux-specific deployment examples or references to Linux-native tools (e.g., VS Code, SCP, or Linux CLI patterns). The documentation also lacks explicit Linux-focused guidance or parity in example scenarios.

Recommendations:

Alternate the order of Windows and Linux mentions, or list them alphabetically to avoid implicit prioritization.
Add Linux-specific deployment examples, such as using Azure CLI, SCP, or VS Code on Linux.
Include references to Linux-native tools and workflows (e.g., deploying from a Linux terminal, using Bash scripts for automation).
Provide links to tutorials or quickstarts that demonstrate Linux-based development and deployment.
Clarify that Visual Studio is not required and highlight cross-platform alternatives (e.g., Visual Studio Code, GitHub Actions, Azure CLI).

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, tooling, and workflows are specific to Windows, PowerShell, and Windows-centric package management (Chocolatey, DSC). Linux is only mentioned in passing, and no Linux equivalents or examples are provided. The documentation assumes the user is deploying to Windows VMs and using Windows-specific tools, with no guidance 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 a section or parallel workflow for setting up continuous deployment for Linux VMs, including scripts and configuration files.
Mention and demonstrate cross-platform tools and approaches where possible, or explicitly state the Windows-only scope at the beginning.
If Azure Automation State Configuration for Linux is deprecated or unavailable, provide clear alternatives or migration guidance for Linux users.
Balance the mention of package managers by giving Linux tools equal prominence and not relegating them to a single sentence.
Where PowerShell is used, provide Bash or shell script equivalents for Linux scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias. While the content is generally platform-agnostic, there are specific sections that focus on Windows Containers (with detailed subnet/IP calculations) without providing equivalent Linux container guidance. The mention of Kudu console UI (primarily associated with Windows-based App Service) and the lack of Linux-specific examples or troubleshooting steps further reinforce this bias. Linux-specific deployment/networking considerations are only briefly mentioned (e.g., a single note about Linux continuous deployment network dependencies), and there are no Linux container subnet/IP sizing examples, nor references to Linux-native tools or troubleshooting methods.

Recommendations:

Add a parallel section for Linux Containers, including subnet/IP address calculation examples and any platform-specific limits or considerations.
Include Linux-native tools (such as SSH, Bash, or Azure CLI examples run from Linux) in relevant sections, especially for troubleshooting or environment variable inspection.
Balance references to Kudu console UI with equivalent Linux troubleshooting tools or interfaces (e.g., SSH into Linux App Service, using the Azure CLI).
Where Windows-specific features or limitations are discussed, provide a corresponding Linux section or explicitly state if the limitation does not apply to Linux.
Expand the Linux continuous deployment section to include more comprehensive guidance and examples, similar to the detail provided for Windows Containers.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows and PowerShell, referencing only Windows PowerShell 5.1, PowerShell DSC, and the PowerSTIG project (which is Windows-centric). There are no examples or guidance for Linux systems, and Linux onboarding is only mentioned in a link reference, not in the main content. All tools and patterns discussed are Windows-specific, and Linux equivalents or cross-platform approaches are missing.

Recommendations:

Add explicit Linux examples for configuring STIG compliance with Azure Automation State Configuration.
Discuss or reference Linux-native tools or DSC resources (such as nx or xDSC resources) where applicable.
Clarify whether PowerSTIG or similar community projects exist for Linux, or provide guidance for Linux users.
Balance the 'Next steps' section with links and explanations relevant to Linux DSC usage.
State up front whether the guidance is Windows-only, or provide parity for Linux users where possible.

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 referencing Windows PowerShell DSC and related tooling. Linux is only mentioned in passing (e.g., onboarding Linux machines), with no Linux-specific examples, tools, or guidance provided. The documentation assumes familiarity with Windows-centric tools and workflows, and does not address Linux-native equivalents or cross-platform usage.

Recommendations:

Provide explicit Linux examples for configuring data at scale, including how to use Datum or similar tools on Linux systems.
Include instructions for using cross-platform PowerShell (PowerShell Core) and clarify any differences in behavior or support compared to Windows PowerShell 5.1.
Mention and link to Linux-native configuration management tools (such as Ansible, Chef, or native DSC for Linux) where appropriate, or clarify the scope if only Windows is supported.
Reorder or balance references so that Linux and Windows are treated equally, rather than Windows-first.
Add a section or callout for Linux users, detailing any prerequisites, limitations, or alternative workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation shows some Windows bias in the prerequisites section, where Windows and PowerShell options are listed before Linux equivalents, and Windows-specific tooling (PowerShell, Visual Studio Code) is emphasized. However, the main Terraform examples are provided for both Linux and Windows App Service plans, and the implementation steps use Bash commands, which are cross-platform.

Recommendations:

List Linux/Bash options before Windows/PowerShell in the prerequisites to avoid 'windows_first' ordering.
Ensure that all command-line examples are clearly marked as cross-platform or provide explicit Linux/macOS and Windows (PowerShell/CMD) alternatives where relevant.
Mention Linux-native editors (such as Vim, Nano, or VS Code on Linux) alongside Visual Studio Code to avoid the impression of Windows tooling preference.
In the prerequisites, clarify that Azure Cloud Shell is available in both Bash and PowerShell, and that both are accessible from any OS.
If referencing PowerShell, also reference Bash or other shells for parity, especially in step-by-step instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation generally provides parity between Linux and Windows deployment options, especially in CLI and VS Code workflows. However, there are subtle biases: (1) In the Visual Studio Code deployment section, the Windows workflow is described in more detail and with more steps, including troubleshooting for missing web.config, which is a Windows-specific concern. (2) The use of Visual Studio Code and FileZilla as recommended tools may be more familiar to Windows users, with no mention of Linux-native alternatives. (3) Some troubleshooting and configuration notes (such as web.config generation) are only present for Windows, with no equivalent Linux-specific guidance. (4) In some cases, Windows deployment steps are listed before Linux, or have more elaborate instructions, which can reinforce a Windows-centric perspective.

Recommendations:

Ensure that Linux and Windows deployment instructions are equally detailed, including troubleshooting tips specific to Linux (e.g., permissions, common deployment issues).
When referencing tools like FileZilla or Visual Studio Code, also mention popular Linux-native alternatives (e.g., gFTP, GNOME Terminal, or other editors like Vim/Emacs) and clarify cross-platform compatibility.
Where Windows-specific configuration (such as web.config) is discussed, provide parallel Linux-specific notes (such as startup script configuration, permissions, or environment variable handling).
In tabbed or pivoted instructions, present Linux and Windows options in a consistent order or randomize the order to avoid reinforcing a default preference.
Review all screenshots and UI references to ensure they are not exclusively from Windows environments; include Linux UI examples where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits several forms of Windows bias. Visual Studio (Windows-only) is presented as the primary IDE, with detailed, screenshot-rich steps for both .NET 8.0 and .NET Framework 4.8. PowerShell is given its own section, and PowerShell-based deployment steps are provided in detail, but Linux shell equivalents are not always present or are less detailed. In the PowerShell section, Linux deployment is explicitly discouraged, and the only provided publish steps use Windows-style paths and tools (e.g., Compress-Archive). Some CLI steps use Windows-centric commands and directory structures. Visual Studio for Mac is only mentioned in a table, with no corresponding walkthrough. There are also places where Windows is the default or first-mentioned OS, and Linux options are secondary or omitted.

Recommendations:

Provide parity for Linux users by including detailed, step-by-step instructions for Linux shell (bash) alongside PowerShell, especially for tasks like zipping and deploying files.
Include screenshots and walkthroughs for Visual Studio Code and command-line workflows on Linux, not just Windows.
Where PowerShell is used, offer equivalent bash/zsh commands and note any platform-specific differences.
Avoid language that discourages Linux use (e.g., 'We recommend Azure PowerShell for creating apps on the Windows hosting platform. To create apps on Linux, use a different tool...'). Instead, provide clear, supported Linux workflows.
Add explicit Visual Studio for Mac instructions or clarify its limitations.
Ensure all file paths and command examples are shown in both Windows and Linux formats where relevant.
When listing OS options (e.g., in Azure portal or CLI), present Linux and Windows equally, not always with Windows first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

While the documentation is titled and themed around Linux, there are several instances where Windows-specific tools and patterns are presented first or exclusively. For example, in the 'Set up your initial environment' and 'Run the sample' sections, PowerShell and Cmd examples are given alongside or before Bash, and in some cases, Bash/Linux-specific guidance is minimal or missing. The documentation sometimes assumes familiarity with Windows command-line tools (e.g., 'py -3'), and does not always provide parity for Linux users, especially in the Django section where Bash, PowerShell, and Cmd are all shown, but the Bash example is not always presented first or emphasized.

Recommendations:

Present Bash/Linux examples first in all code blocks and tabs, especially since the quickstart is Linux-focused.
Ensure all command-line instructions use Linux-native commands and patterns as the default, with Windows variants as secondary.
Where 'py -3' is used (a Windows launcher), clarify or provide the equivalent Linux command (usually 'python3') and explain any differences.
Review all sections for any missing Linux-specific instructions or troubleshooting tips, and add them where necessary.
Consider removing or de-emphasizing PowerShell and Cmd tabs unless the documentation is explicitly cross-platform, or clearly mark them as alternatives.
Audit for any references to Windows-only tools or patterns, and provide Linux equivalents or alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several ways: Windows-specific paths and tools are often mentioned first or exclusively (e.g., 'D:\home', references to 'w3wp.exe', 'applicationHost.config', and use of Windows time zone documentation). Many environment variable descriptions and examples are tailored to Windows (such as default paths, process names, and configuration files), with Linux equivalents either mentioned later, less prominently, or omitted. Some features are described only in the context of Windows tools or patterns (e.g., MSDeploy, Web Deploy, IIS), and PowerShell/Windows-centric terminology is prevalent. Linux-specific details are sometimes present but are less thorough or appear as afterthoughts.

Recommendations:

For every environment variable or feature that behaves differently on Windows and Linux, provide both Windows and Linux examples side by side, including file paths, process names, and configuration file locations.
Avoid referencing Windows tools (e.g., MSDeploy, Web Deploy, IIS, applicationHost.config) without also providing Linux alternatives or clarifying their applicability.
When listing default values or behaviors, present Linux and Windows defaults together, not with Windows first or exclusively.
Where possible, link to both Windows and Linux documentation for referenced concepts (e.g., time zones, logging, process management).
Review all examples and ensure that Linux users are not required to mentally translate Windows-centric instructions.
Add Linux-specific troubleshooting and configuration notes where only Windows-specific ones are currently present.
Ensure parity in depth and clarity for both platforms, especially in sections like build automation, logging, and deployment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows environments, specifically PowerShell and Windows DSC tooling. All examples and references are for Windows PowerShell 5.1, with no mention of Linux equivalents or cross-platform DSC solutions. The tools and resources discussed (ReverseDSC, SharePointDSC) are Windows/PowerShell-centric, and there are no Linux-specific instructions or examples provided.

Recommendations:

Add equivalent instructions and examples for Linux systems, including how to extract configurations from Linux servers using cross-platform DSC tools.
Mention and link to cross-platform DSC resources, such as PowerShell 7+ and the Linux DSC agent.
Clarify in the introduction that the current solution is Windows-specific, and provide guidance or alternatives for Linux users.
Include examples or references for managing configurations on Linux servers, not just Windows/SharePoint.
Balance the documentation structure so that Linux and Windows scenarios are presented with equal prominence where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides installation instructions for the required NuGet packages using both the .NET Core CLI and Visual Studio's Package Manager Console (PowerShell-based), but it lists the Visual Studio/PowerShell method second. However, the Visual Studio/PowerShell example is included, which is Windows-specific, while no explicit Linux or cross-platform GUI alternative is mentioned. The focus on Visual Studio and its tools, without mentioning Linux IDEs or editors, and the lack of explicit Linux shell examples (e.g., bash), indicates a mild Windows bias.

Recommendations:

Add explicit Linux/macOS shell instructions (e.g., bash/zsh) for installing NuGet packages, clarifying that the .NET CLI works cross-platform.
Mention and provide examples for using popular Linux editors/IDEs (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
Clarify that the .NET CLI commands are platform-agnostic and can be run on Windows, Linux, or macOS.
If referencing GUI tools, include cross-platform options or note their availability.
Avoid referencing PowerShell/Visual Studio-specific tools without offering Linux/macOS equivalents or alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias, particularly in the 'Application Initialization (AppInit)' section, where detailed instructions and references are provided for Windows (IIS Application Initialization Module), while Linux is only briefly mentioned with a single environment variable and no further explanation or example. Several features and troubleshooting steps are described in depth for Windows, with Linux alternatives either missing or only linked without detail. Windows tools and patterns (such as IIS modules and .NET Core stdout logging) are highlighted, while Linux equivalents are not discussed.

Recommendations:

Provide equally detailed Linux examples and explanations, especially for application initialization and warm-up mechanisms. For example, include a step-by-step guide for configuring WEBSITE_WARMUP_PATH on Linux, with sample configuration and expected behavior.
When referencing Windows-specific tools (like IIS Application Initialization Module or .NET Core stdout logging), also mention and explain Linux-native equivalents or approaches (such as using startup scripts, health probes, or Linux logging best practices).
Ensure that for every Windows feature or troubleshooting step described, a Linux equivalent is either described or explicitly noted as unavailable, with suggested workarounds if possible.
Structure sections so that Linux and Windows approaches are presented with parity, rather than Windows-first with Linux as an afterthought.
Add practical Linux command-line or configuration examples where appropriate, not just links.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides both Linux and Windows examples for basic App Service deployments, but Windows scenarios are often listed before Linux equivalents, and there are more Windows-specific templates (e.g., Windows container, Windows with MySQL/PostgreSQL) than Linux ones. Some advanced scenarios (e.g., App with connected resources) are only shown for Windows, with Linux equivalents missing. There is also a lack of parity in the depth and variety of Linux-focused examples compared to Windows.

Recommendations:

Ensure that for every Windows-specific template (e.g., App with MySQL/PostgreSQL, App with SQL Database), there is a Linux equivalent provided and linked.
Present Linux and Windows examples in parallel or alternate their order to avoid implicit prioritization of Windows.
Add more advanced Linux scenarios, such as Linux app with Azure SQL Database, Linux app with Blob storage, and Linux app with Redis cache.
Where possible, use neutral language and avoid grouping Linux examples separately from the main list to reinforce parity.
Review and update the documentation regularly to ensure Linux and Windows feature parity as Azure evolves.

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 and workflows. Package installation instructions are given first for the .NET Core CLI (cross-platform), but then for the Visual Studio Package Manager Console, which is Windows-only and uses PowerShell syntax. There are no explicit Linux or macOS-specific instructions or mentions of alternative editors or package managers. Visual Studio (Windows) is referenced without mention of VS Code or other cross-platform IDEs. The documentation assumes familiarity with Windows tooling and omits Linux-specific guidance.

Recommendations:

Add explicit instructions for Linux/macOS users, such as using the .NET CLI in Bash or Zsh terminals.
Mention and provide examples for using Visual Studio Code (cross-platform) alongside or instead of Visual Studio.
Clarify that the .NET CLI commands work on all platforms, and provide terminal commands for Bash (Linux/macOS) where appropriate.
Avoid referencing Windows-only tools (like the Visual Studio Package Manager Console) without offering cross-platform alternatives.
Where UI navigation is described (e.g., opening the console), include steps for cross-platform editors or command lines.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias towards Windows environments by prioritizing Windows-specific tools and workflows. The Package Manager Console (a Visual Studio/Windows feature) is highlighted alongside the .NET CLI, and only PowerShell commands are shown for package installation. There are no explicit Linux or cross-platform shell examples, and Visual Studio (primarily a Windows IDE) is referenced without mention of alternatives like VS Code or command-line workflows common on Linux.

Recommendations:

Add explicit Linux/macOS instructions for installing the required NuGet packages, such as using the .NET CLI in Bash or Zsh.
Mention and provide examples for using cross-platform editors like Visual Studio Code, or clarify that Visual Studio is Windows-only.
Present the .NET CLI (dotnet add package) instructions before or at least equally with the Package Manager Console, emphasizing its cross-platform nature.
Avoid referencing Windows-specific tools (like the Package Manager Console) without offering Linux/macOS equivalents.
Include notes or examples for running the sample code on Linux and macOS, ensuring parity in developer experience.

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 assuming the use of Windows PowerShell 5.1. There is no mention of Linux equivalents, cross-platform PowerShell (PowerShell Core), or how to perform similar tasks on Linux systems. Windows tools and patterns (such as MOF files, PowerShellGet, and Windows-specific DSC resources) are referenced exclusively, and Linux scenarios are not addressed.

Recommendations:

Add explicit guidance for using PowerShell DSC and composite resources on Linux, including any differences in configuration or supported features.
Include examples using PowerShell Core (pwsh), which is cross-platform, and clarify when instructions are Windows-specific.
Reference and link to Linux onboarding and configuration documentation more prominently, not just as a secondary link.
Provide sample configurations and workflows for common Linux scenarios (e.g., managing Apache/Nginx, SSH, Linux firewall, etc.).
Clarify which features or modules are Windows-only and which are supported on Linux, and update the 'Applies to' section accordingly.
Mention and link to Linux DSC resources and community modules where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows by referencing PowerShell and DOS commands as the primary means of interacting with the Kudu debug console, and by mentioning the use of Windows-specific tools like ProcDump. There are no examples or mentions of Linux shell commands or Linux-native troubleshooting tools, despite Azure App Service supporting Linux-based apps.

Recommendations:

Include examples of using Bash or Linux shell commands in the Kudu debug console, alongside PowerShell and DOS commands.
Mention Linux-compatible alternatives to ProcDump for memory dumps, or clarify if ProcDump is available in Linux containers.
Provide parity in troubleshooting steps and tool recommendations for both Windows and Linux-based App Service environments.
Explicitly state when a tool or command is Windows-only, and provide equivalent instructions for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows-first bias by providing more detailed instructions and features for Windows App Service apps, such as web server logging, detailed error messages, and failed request tracing, which are not available or documented for Linux. Several sections (e.g., enabling web server logging, detailed errors, failed request tracing) only mention Windows, with no Linux equivalents or alternatives. Additionally, Windows-specific tools and log formats (e.g., W3C log format, Log Parser, references to D:\ paths) are highlighted, while Linux-specific tools or patterns are not discussed.

Recommendations:

Clearly indicate feature parity or lack thereof for Linux vs. Windows in each section, and provide Linux alternatives or workarounds where possible.
Add explicit Linux examples and instructions for all logging types, or state if a feature is not supported on Linux.
Include Linux-relevant tools and log file paths (e.g., /home/LogFiles) alongside Windows examples.
For sections that are Windows-only (e.g., web server logging, failed request tracing), provide guidance on equivalent troubleshooting/logging approaches for Linux (such as using OpenTelemetry, custom logging, or third-party tools).
Balance the order of presentation so that Linux and Windows are given equal prominence, or group instructions by platform.
Reference Linux-friendly log analysis tools in addition to Windows tools like Log Parser.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation exhibits a mild Windows bias. In troubleshooting steps and FAQs, Windows-specific tools and commands (such as 'ipconfig /flushdns') are mentioned without Linux/macOS equivalents. PowerShell is referenced explicitly for resource movement, but no CLI or Bash alternatives are provided. There are no Linux-specific troubleshooting commands or examples, and Windows tools are mentioned before or instead of cross-platform or Linux-native tools.

Recommendations:

When providing command-line troubleshooting steps (e.g., flushing DNS cache), include equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS ('sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
When referencing PowerShell cmdlets (e.g., 'Move-AzResource'), also mention the equivalent Azure CLI command (e.g., 'az resource move') and provide Bash syntax where appropriate.
Where Windows tools or patterns are mentioned, ensure Linux and macOS alternatives are also described, or link to relevant documentation.
Add troubleshooting examples or notes that are relevant to Linux-based environments, especially for common tasks like certificate conversion, DNS troubleshooting, and file uploads.
Review the order of tool/command presentation to avoid always listing Windows/PowerShell first; consider grouping by platform or explicitly stating cross-platform options.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

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 references to Linux-based development environments, cross-platform tools, or command-line alternatives (such as Azure CLI or VS Code). All screenshots, file paths, and tool references are Windows-specific, and there is no guidance for users developing or troubleshooting from Linux or macOS systems.

Recommendations:

Add parallel instructions and examples for Linux and macOS users, including how to perform similar troubleshooting tasks using cross-platform tools like Azure CLI, VS Code, or Kudu.
Include command-line examples for enabling diagnostics, downloading logs, and remote debugging that work on Linux/macOS (e.g., using Azure CLI, SSH, or REST APIs).
Reference and provide guidance for using VS Code's Azure extensions, which are cross-platform, for tasks like remote debugging and log streaming.
Clarify which steps are Windows/Visual Studio-specific and provide alternative steps for non-Windows environments.
Mention and link to documentation for App Service troubleshooting using the Azure portal and Kudu/SCM site, which are accessible from any OS.
Avoid assuming the presence of Windows-only features (like Server Explorer, Solution Explorer, or File Explorer) and provide alternatives where possible.

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 (such as PowerShell, IIS logs, and SysInternals Procdump), mentioning Windows-centric features (like .NET Profiler for Windows), and providing examples and instructions that assume a Windows environment. There is a lack of Linux-specific guidance, tools, or examples, and Linux workflows are not mentioned or are omitted entirely.

Recommendations:

Provide equivalent Linux examples and instructions alongside Windows ones, such as using Bash/SSH instead of only PowerShell.
Mention and link to Linux-specific diagnostic tools (e.g., using strace, lsof, or Linux-native logging) where Windows tools like Procdump or IIS logs are referenced.
Clarify when a feature or tool is Windows-only, and offer Linux alternatives or note limitations for Linux-based App Service plans.
Include references to Linux App Service documentation, such as how to access logs, use the Kudu console on Linux, or collect memory dumps on Linux.
Balance the order of presentation so that Linux and Windows approaches are given equal prominence, rather than listing Windows first or exclusively.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page exclusively covers Windows operating systems, PowerShell, and Windows Management Framework (WMF) in all version histories, features, and instructions. There is no mention of Linux support, examples, or parity, despite Azure DSC historically having some Linux support. All examples, troubleshooting, and references are Windows-centric, and the only tools and patterns discussed are Windows/PowerShell-specific.

Recommendations:

Explicitly state the current and historical support status for Linux in the introduction, including any retirement or deprecation notices.
If Linux support is retired, provide a clear summary and links to migration or alternative solutions for Linux users.
If any versions supported Linux, include those versions and their features in the version history table.
Add Linux-specific examples, troubleshooting steps, and references where applicable, or clarify their absence.
Where PowerShell or WMF is mentioned, note the equivalent (or lack thereof) for Linux, such as Open Management Infrastructure (OMI) or cross-platform DSC implementations.
Ensure that any future documentation updates maintain parity in describing both Windows and Linux support, or clearly state when features are Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation provides both Windows and Linux instructions using Azure CLI, but Windows is consistently presented first in all platform-specific pivots. Additionally, references to Azure portal UI and 'Advanced Tools' (Kudu), which are more familiar to Windows users, are used without mentioning Linux-native equivalents. There is also a lack of Linux-specific troubleshooting or command-line (bash) examples outside of the Azure CLI context, and no mention of Linux shell or scripting patterns. The documentation does not provide PowerShell-specific commands, but the overall structure and tool references show a subtle Windows bias.

Recommendations:

Alternate the order of platform pivots so that Linux instructions are sometimes presented first, or use a neutral introduction before splitting into platform-specific instructions.
Where possible, provide Linux-native troubleshooting steps or mention Linux shell commands/scripts for common tasks (e.g., using bash, tailing logs, or using SSH).
When referencing Azure portal features like 'Advanced Tools', clarify their availability and behavior on both Windows and Linux App Service plans, or provide Linux-specific alternatives if differences exist.
Ensure that all screenshots and UI walkthroughs are equally applicable to both platforms, or provide separate images where necessary.
Explicitly state when a command or feature is identical across platforms to reinforce parity.
Consider including a section or callout highlighting any platform-specific caveats or differences, especially for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows environments. All configuration examples use Windows PowerShell DSC syntax and resources (e.g., WindowsFeature IIS), and the only VM creation instructions link to Windows VM guides. There are no Linux-specific examples, resources, or walkthroughs, and Linux support is only mentioned in passing or in deprecation notices. References and links are almost exclusively for Windows/PowerShell DSC, and no Linux equivalents or cross-platform DSC resources are provided.

Recommendations:

Add Linux-specific examples, such as a DSC configuration that manages a Linux package or service using the nx or cross-platform DSC resources.
Include instructions and links for creating and managing Linux VMs in Azure, alongside the Windows VM instructions.
Provide parity in walkthroughs for onboarding both Windows and Linux nodes to Azure Automation State Configuration.
Reference cross-platform DSC documentation and resources, not just Windows PowerShell DSC.
Clarify the current and future support status for Linux DSC in Azure Automation, and if deprecated, provide migration guidance or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as Visual Studio, Solution Explorer, and PowerShell/Package Manager Console, while omitting equivalent Linux or cross-platform alternatives. There are no explicit Linux or CLI-based development/publishing examples, and the local development and debugging guidance is focused on Windows environments. The documentation assumes the use of Windows-based development tools and does not provide parity for Linux users.

Recommendations:

Provide equivalent Linux and cross-platform examples for development, publishing, and debugging (e.g., using VS Code, dotnet CLI, Azure CLI, and GitHub Actions).
Include instructions for updating packages and managing dependencies using the dotnet CLI (e.g., 'dotnet add package') instead of only referencing Visual Studio and PowerShell.
Offer guidance for local debugging and authentication flows on Linux/macOS, including how to obtain tokens and connect to Azure SQL Database from non-Windows environments.
Mention and demonstrate cross-platform editors (e.g., VS Code) and workflows alongside Windows-specific tools.
Clarify which steps are platform-agnostic and which are Windows-specific, and provide alternatives where possible.

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. Visual Studio for Windows is presented first and in more detail, while macOS and cross-platform scenarios are treated as exceptions or afterthoughts. Windows-specific tools (Visual Studio, Azure PowerShell) are mentioned before their Linux/macOS equivalents, and PowerShell is given its own tab, whereas Linux-specific shells or tools are not. There are no explicit Linux command-line or shell examples, and the guidance for Linux users is less direct, often referring to Azure CLI as a workaround.

Recommendations:

Present cross-platform or Linux-native tools (such as Azure CLI) before or alongside Windows-specific tools.
Add explicit Linux/macOS shell examples and instructions, not just references to Azure CLI.
Include development environment setup instructions for common Linux IDEs (e.g., JetBrains Rider, VS Code on Linux) and shell environments.
Avoid treating macOS/Linux as exceptions; instead, structure sections so that Windows, macOS, and Linux are presented with parity.
Where PowerShell is mentioned, also provide Bash/zsh equivalents for Linux/macOS users.
Clarify that Azure CLI and VS Code are fully cross-platform and highlight their use on Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a clear Windows bias in several ways. The Windows section appears first and is more detailed in certain areas, with exclusive use of Windows tools (Visual Studio, Windows Explorer, PowerShell scripts) and workflows. The Windows example is tightly coupled to Visual Studio and Windows-specific features (such as installing fonts via Windows Explorer and using PowerShell scripts in Dockerfiles), with no equivalent Linux example for similar scenarios (e.g., custom OS integration, font installation). The Linux section, while comprehensive for a generic Python/Flask app, does not mirror the Windows scenario or provide parity for .NET or custom OS integration use cases.

Recommendations:

Provide Linux-first or at least parallel Linux and Windows sections, ensuring neither is prioritized in order or detail.
For every Windows-specific tool or workflow (e.g., Visual Studio, Windows Explorer, PowerShell), provide equivalent Linux instructions (e.g., VS Code, terminal commands, Bash scripts).
Include a Linux example that demonstrates how to migrate a .NET app with custom OS dependencies (such as custom fonts or libraries) to a Linux container, mirroring the Windows scenario.
Avoid assuming the user is on Windows by default; ensure all prerequisites and setup steps have Linux equivalents.
Where PowerShell scripts are used in Dockerfiles for Windows, provide Bash script equivalents for Linux.
Ensure that screenshots and step-by-step instructions are available for both platforms, not just Windows.
Explicitly mention any platform-specific limitations or differences, and guide users on how to address them on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-centric bias by prioritizing Windows/Visual Studio workflows, using PowerShell and Windows-specific tools for critical steps (such as granting SQL permissions), and omitting explicit Linux/macOS command-line or tooling alternatives for key operations. Linux and cross-platform development environments are only briefly referenced, and there are no concrete examples or guidance for performing database permission steps from non-Windows systems.

Recommendations:

Provide explicit Linux/macOS alternatives for all steps, especially for granting SQL permissions (e.g., using sqlcmd on Linux, Azure Data Studio, or cross-platform tools).
Include examples using bash and cross-platform shells for all CLI operations, not just Azure CLI.
Add a section or tab for Linux/macOS development environments, detailing how to configure and debug apps using VS Code or JetBrains Rider on those platforms.
When mentioning Visual Studio, clarify that Visual Studio Code is cross-platform and provide parity in instructions.
Avoid assuming PowerShell or Windows-only tools are available; always offer a cross-platform equivalent.
For SQL permission steps, show how to use sqlcmd or Azure Data Studio on Linux/macOS, or provide T-SQL scripts that can be run from any platform.

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, referencing Windows-centric tools (such as the Az PowerShell module and xDscDiagnostics), and omitting any Linux or cross-platform CLI alternatives. There are no Bash, Azure CLI, or Linux-native instructions, and the workflow assumes a PowerShell environment throughout. Additionally, the documentation references the retirement of Linux DSC support, but does not offer guidance for Linux users or alternatives.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell instructions, as Azure CLI is cross-platform and works natively on Linux and macOS.
Explicitly state the platform requirements for the PowerShell examples, and provide guidance for Linux/macOS users (e.g., using PowerShell Core or Azure CLI).
Where possible, provide Bash script examples or note how Linux users can achieve the same results.
Clarify the impact of Linux DSC retirement and suggest supported alternatives or migration paths for Linux users.
Ensure that references to tools and modules (such as xDscDiagnostics) include notes on platform compatibility and alternatives for non-Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by focusing heavily on PowerShell DSC, referencing Windows tools and patterns first, and providing detailed Windows OS/version support lists before Linux. Examples and references (such as Chocolatey and PowerShell cmdlets) are Windows-centric, and there are no Linux-specific usage examples or equivalent Linux tooling highlighted.

Recommendations:

Provide Linux-specific examples for onboarding, configuration, and troubleshooting, including sample commands and scripts.
List supported Linux distributions and versions explicitly, similar to the Windows OS list.
Highlight Linux-native configuration management tools or patterns where relevant, or clarify how PowerShell DSC for Linux integrates with typical Linux workflows.
Include Linux-focused continuous deployment pipeline examples (e.g., using apt, yum, or native package managers instead of Chocolatey).
Balance the order of presentation so that Linux and Windows are given equal prominence in prerequisites, examples, and feature descriptions.
Reference Linux command-line tools and scripting (e.g., Bash) where appropriate, alongside 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 detailed PowerShell examples and cmdlet references for Windows VMs, while Linux remediation is described only in general terms without concrete script examples. Windows tools and workflows (PowerShell, Update-DscConfiguration) are highlighted first and in more detail, whereas Linux instructions are less actionable and defer to external documentation.

Recommendations:

Provide explicit Linux command-line examples (e.g., shell or Python scripts) for remediating drift, similar to the PowerShell example for Windows.
List Linux remediation steps before or alongside Windows steps to avoid a 'Windows-first' impression.
Reference and explain Linux-native tools or scripts directly in the documentation, not just via external links.
Include parity in detail and clarity for both platforms, ensuring Linux users have actionable, in-page guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows development environments, specifically Visual Studio on Windows. All examples and instructions assume the use of Visual Studio, with no mention of Linux or cross-platform alternatives. There are no command-line or non-Windows deployment examples, and all tooling references (e.g., Solution Explorer, dialog boxes, right-click menus) are specific to Windows/Visual Studio. Linux users or those using other IDEs are not provided with equivalent guidance.

Recommendations:

Add instructions for developing and deploying WebJobs using cross-platform tools such as the Azure CLI, .NET CLI, or Visual Studio Code.
Include Linux-specific examples for creating, configuring, and deploying WebJobs.
Mention and document alternative workflows for non-Windows environments, such as using GitHub Actions, Azure DevOps, or command-line deployment.
Clarify which steps are Windows/Visual Studio-specific and provide parity guidance for macOS and Linux users.
Reference and link to documentation on deploying WebJobs without Visual Studio, including from Linux/macOS terminals.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell for deployment tutorials and omitting equivalent Linux-friendly tools or examples (such as Azure CLI or ARM templates). The 'Next steps' section specifically links only to a PowerShell-based tutorial, and there are no mentions or examples for Linux users, which may hinder accessibility for non-Windows administrators.

Recommendations:

Include Azure CLI examples and tutorials alongside PowerShell instructions to ensure Linux and macOS users have clear guidance.
Add references to ARM/Bicep templates for platform-neutral, declarative deployments.
In the 'Next steps' section, provide parallel links for both PowerShell and Azure CLI tutorials.
Review and update all example commands and scripts to offer both Windows (PowerShell) and cross-platform (CLI/ARM) alternatives.
Explicitly mention that all features are accessible via multiple tools, not just PowerShell, to avoid implying Windows-only support.

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 and instructions are provided exclusively for Windows PowerShell, with explicit notes that PowerShell Core (cross-platform) is not supported. There are no examples or guidance for Linux or macOS users, and all tooling and workflow references assume a Windows environment.

Recommendations:

Provide equivalent instructions and examples for Linux/macOS environments, including how to use Azure Automation with PowerShell Core where possible.
Clarify which features are Windows-only and suggest alternatives or workarounds for non-Windows users.
Include notes or links to documentation for managing Office 365/Azure Automation from Linux/macOS, such as using Azure CLI, REST APIs, or cross-platform PowerShell modules.
If certain modules (like Microsoft Graph PowerShell) are not supported on PowerShell Core, explicitly state this and provide alternative approaches for Linux users.
Reorder sections or provide parallel instructions so that Windows and Linux users are equally supported and neither is prioritized over the other.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows and Visual Studio users. All command-line examples use PowerShell syntax and the Visual Studio Package Manager Console, which are Windows-specific. There are no instructions or examples for Linux or cross-platform development environments (such as VS Code, .NET CLI, or terminal-based workflows). Visual Studio is assumed as the only development environment, and Windows UI navigation is described throughout. No mention is made of Linux equivalents or how to perform these steps on non-Windows systems.

Recommendations:

Provide .NET CLI equivalents for all NuGet package installation commands (e.g., 'dotnet add package ...'), and show these alongside or before PowerShell examples.
Include instructions for creating and running the project using cross-platform tools such as VS Code or JetBrains Rider, not just Visual Studio.
Add guidance for Linux and macOS users, including how to configure and run the app from the terminal.
Replace or supplement Visual Studio UI navigation steps with command-line alternatives where possible.
Explicitly state that the tutorial can be followed on Windows, Linux, or macOS, and clarify any platform-specific requirements.
Show how to set environment variables and configuration files on Linux/macOS (e.g., using export or editing files in the terminal).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses Azure PowerShell cmdlets for all instructions and examples, with no mention or examples of equivalent Azure CLI (cross-platform) or Bash commands. It references 'Windows PowerShell' and links to PowerShell-specific resources, implicitly prioritizing Windows tooling and workflows. There are no Linux or macOS-specific instructions or parity examples, and no mention of using the Azure Cloud Shell or Bash, which are common for Linux users.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside or in place of PowerShell cmdlets for each step.
Include a section or callout for Linux/macOS users, clarifying that all operations can be performed from Bash or Azure Cloud Shell.
Avoid referring to 'Windows PowerShell' unless the instructions are truly Windows-specific; use 'PowerShell' or 'Azure CLI' as appropriate.
Link to both PowerShell and Azure CLI installation guides.
When referencing external documentation, include links to both PowerShell and CLI management guides.
Consider reordering examples or providing tabs for PowerShell and CLI to avoid Windows-first bias.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell commands as the primary or only CLI examples, referencing Windows-specific tools (e.g., certlm.msc, netstat via cmd), and giving step-by-step instructions for Windows environments before or instead of Linux equivalents. Linux commands and workflows are mentioned less frequently, often as secondary notes or not at all, leading to an imbalance in cross-platform guidance.

Recommendations:

For every PowerShell example, provide an equivalent Azure CLI and, where relevant, Bash/Linux shell command.
When referencing Windows tools (e.g., certlm.msc, netstat in cmd), include parallel instructions for Linux (e.g., using openssl, ss, or netstat in a Linux shell).
In troubleshooting steps, avoid phrases like 'by using a browser or PowerShell' and instead say 'by using a browser, PowerShell, Azure CLI, or Bash', with examples for each.
When listing methods to check certificates or network connectivity, present Linux and Windows options together, or alternate which comes first.
Add explicit Linux/Bash command examples for tasks like checking open ports, viewing certificates, and resolving DNS (e.g., 'ss -tlnp', 'openssl', 'dig' or 'nslookup').
Ensure that all step-by-step instructions have Linux equivalents, not just Windows.
Consider a dedicated section or callouts for Linux users where workflows differ significantly.

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 enabling diagnostic logging, with no equivalent Azure CLI, Bash, or Linux-native instructions. The 'Enable logging' section exclusively features a PowerShell cmdlet, and there is no mention of cross-platform tools or Linux command-line alternatives. Additionally, the workflow and screenshots are oriented toward tools and patterns more familiar to Windows users, such as PowerShell and Excel, and the page references Visual Studio and C# for log conversion, further reinforcing a Windows-centric approach.

Recommendations:

Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash or shell script examples where appropriate, especially for log retrieval and processing.
Mention and provide examples for viewing and analyzing logs using Linux-native tools (e.g., jq, grep, awk) in addition to Excel and Power BI.
Reference cross-platform editors and tools (such as VS Code) instead of, or alongside, Visual Studio.
Ensure that all step-by-step instructions and screenshots are applicable to users on both Windows and Linux platforms.
Explicitly state that all operations can be performed from Linux, macOS, or Windows, and provide links to relevant cross-platform documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exclusively provides PowerShell-based examples and instructions for implementing scheduled autoscaling with Azure Automation, with no mention of Bash, Azure CLI, or Python runbooks. This creates a Windows-centric bias, as PowerShell is primarily associated with Windows environments, and Linux-native approaches are not addressed.

Recommendations:

Add equivalent examples using Azure CLI (bash) scripts for Linux users, demonstrating how to adjust Application Gateway autoscale settings.
Include guidance or sample runbooks written in Python, which is supported by Azure Automation and widely used in cross-platform and Linux environments.
Explicitly mention that both PowerShell and Python runbooks are supported in Azure Automation, and provide links or references to relevant documentation.
Present examples for both Windows (PowerShell) and Linux (CLI/Python) side by side, or at least mention Linux-friendly alternatives before or alongside Windows-centric tools.
Clarify that Azure Automation is cross-platform and not limited to PowerShell or Windows tooling.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell-only command-line examples for certificate management, referencing Azure PowerShell and ARM templates, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The troubleshooting steps and resolutions focus on Azure Portal and PowerShell, which are more familiar to Windows users, with no explicit guidance for Linux or non-Windows environments.

Recommendations:

Add Azure CLI (az) command examples alongside PowerShell for certificate upload and management, as Azure CLI is cross-platform and widely used on Linux and macOS.
Where PowerShell scripts are shown, provide equivalent Bash/CLI scripts or commands.
When mentioning tools or automation (e.g., ARM templates, PowerShell), also reference cross-platform alternatives (e.g., Azure CLI, Terraform).
Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and link to relevant documentation.
Balance the order of presentation so that cross-platform tools (CLI) are mentioned before or alongside Windows-specific tools (PowerShell).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is given its own tab and is referenced multiple times, with explicit PowerShell cmdlets shown for preview registration and status checks. The CLI tab is present, but some instructions (such as viewing registration status) reference PowerShell cmdlets even in the CLI section. There are no explicit Linux/Bash shell examples or screenshots, and the workflow assumes familiarity with PowerShell and the Azure Portal (which is platform-agnostic but often associated with Windows environments). No Linux-specific tools, shell commands, or screenshots are provided.

Recommendations:

Ensure that all CLI sections use only Azure CLI commands and do not reference PowerShell cmdlets for status checks or outputs.
Add explicit Bash/Linux shell examples where applicable, especially for scripting or automation scenarios.
Include screenshots or terminal outputs from Linux environments where possible, or clarify that the CLI commands are cross-platform.
Consider adding a section or note clarifying that Azure CLI is fully supported on Linux/macOS and that all CLI examples are platform-agnostic.
If referencing PowerShell, also mention cross-platform PowerShell Core, or provide equivalent Bash scripts for parity.

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 PowerShell cmdlet examples (e.g., New-AzApplicationGatewayProbeHealthResponseMatch) for configuring custom health probes, and by referencing Azure PowerShell as the primary automation tool. There are no equivalent examples or instructions for Linux users (e.g., Azure CLI, Bash, or ARM templates), and the 'devx-track-azurepowershell' custom tag further signals a Windows/PowerShell-centric approach. The 'Next steps' section also lists PowerShell before the Azure Portal, with no mention of Linux-friendly tooling.

Recommendations:

Add equivalent Azure CLI (az network application-gateway probe ...) examples alongside PowerShell cmdlets for all configuration tasks.
Include Bash or shell scripting examples where relevant, especially for automation scenarios.
Reference ARM/Bicep templates for declarative configuration, which are platform-agnostic.
Update 'Next steps' to mention Azure CLI and ARM/Bicep options, not just PowerShell.
Consider removing or balancing the 'devx-track-azurepowershell' tag with 'devx-track-azurecli' or similar.
Wherever PowerShell is mentioned, provide a parallel Linux/CLI example or a link to equivalent documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell multiple times as the primary or sole method for configuration and details retrieval. There are no explicit Linux or Bash examples, and the only command-line tool mentioned by name is PowerShell. When mentioning CLI, it is not clarified whether this refers to Azure CLI (which is cross-platform) or something else, and PowerShell is always listed first. The 'Next steps' section links only to a PowerShell-based configuration guide, omitting Linux/Bash or Azure CLI examples.

Recommendations:

Provide explicit Azure CLI (az) examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
Clarify in all references to 'CLI' that this means Azure CLI, and provide Bash syntax examples where appropriate.
Include links in the 'Next steps' section to both PowerShell and Azure CLI/Bash configuration guides.
Wherever PowerShell is mentioned, ensure parity by also mentioning and providing examples for Linux/Bash environments.
Avoid listing PowerShell before CLI in lists or instructions; alternate or use neutral ordering.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes certificate export using Windows tools (Certificate Manager, PowerShell), with detailed step-by-step instructions and screenshots for the Windows GUI. There are no Linux or cross-platform command-line examples, nor are alternative tools (like OpenSSL) mentioned. The only referenced automation is via PowerShell, and the 'Next steps' section links to a PowerShell-specific guide. This creates a strong Windows bias and leaves Linux users without guidance.

Recommendations:

Add equivalent instructions for exporting certificates using OpenSSL or other standard Linux tools.
Provide command-line examples for both Windows (certutil, PowerShell) and Linux/macOS (OpenSSL).
Include screenshots or terminal output for Linux workflows where appropriate.
Mention cross-platform tools early in the documentation, not just Windows-specific ones.
In the 'Next steps' section, link to Linux and cross-platform guides in addition to PowerShell.

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 and workflows are described using PowerShell scripts and cmdlets, with Linux instructions often being secondary, less detailed, or requiring use of Windows tools (e.g., generating metaconfigurations on Windows). Windows-specific tools and terminology (WMF 5, PowerShell DSC, Set-DscLocalConfigurationManager) are used throughout, and Linux workflows are often described as adaptations of the Windows process. Linux-specific examples are minimal, and Linux users are frequently directed to use Windows-based tooling for key steps.

Recommendations:

Provide Linux-first and Linux-native examples for all major workflows, including onboarding, metaconfiguration generation, and status checking.
Document how to generate DSC metaconfigurations entirely on Linux, without requiring Windows or PowerShell.
Where possible, use cross-platform tools or clearly indicate platform-specific steps, offering parity in detail and clarity.
Include bash or Python scripts for Linux alongside PowerShell scripts for Windows.
Clarify when a feature or cmdlet is Windows-only, and offer Linux alternatives or workarounds.
Reorganize sections so that Linux and Windows instructions are presented with equal prominence and detail.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing detailed PowerShell-based instructions and commands for managing and migrating classic Application Gateway resources, with no equivalent Bash, Azure CLI, or Linux-native examples for key operations. PowerShell is referenced as the primary tool for both legacy and migration tasks, and the step-by-step cleanup process is exclusively shown using PowerShell cmdlets. While Azure CLI is mentioned as an option for deployment, no CLI or Linux shell examples are provided for migration or cleanup steps.

Recommendations:

Provide equivalent Azure CLI (bash) commands for all PowerShell examples, especially for migration and cleanup tasks.
Include Linux/macOS-specific instructions or notes where relevant, such as authentication and environment setup.
When listing deployment options, alternate the order or explicitly state parity between PowerShell and CLI to avoid 'windows_first' perception.
Reference cross-platform tools (e.g., Azure CLI) in all sections where PowerShell is mentioned, and link to their documentation.
Add a section or examples for managing classic resources using Azure CLI or REST API, if supported, or clarify if such options are unavailable.

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 mention of Azure PowerShell for operational tasks (such as restarting the Application Gateway) and the absence of Linux/CLI examples or references. Where tooling is mentioned, PowerShell is referenced first or exclusively, and there are no explicit Linux command-line (Bash/Azure CLI) equivalents provided. This could make the documentation less approachable for Linux users or those who prefer cross-platform tools.

Recommendations:

Whenever PowerShell is referenced for operational tasks (e.g., restarting the Application Gateway), provide equivalent Azure CLI (az) commands, ideally in Bash syntax.
If referencing a tool or command, mention both PowerShell and CLI options, or present CLI first for neutrality.
Add explicit Linux/Bash examples where relevant, especially for common administrative tasks.
Review all procedural instructions to ensure they are not Windows-centric and are accessible to users on all platforms.

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 (Windows-centric) commands for all troubleshooting steps, referencing Windows tools and patterns (such as IIS and PowerShell cmdlets), and omitting equivalent Azure CLI, Bash, or Linux-native instructions. There are no Linux-specific troubleshooting examples or mentions of Linux-based backend servers, and Windows/PowerShell approaches are always presented first and often exclusively.

Recommendations:

Provide Azure CLI (az) command examples alongside or before PowerShell cmdlets for all troubleshooting steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash shell command examples for network diagnostics (e.g., using curl, dig, nslookup, traceroute) to check DNS, connectivity, and health probe responses from Linux VMs.
Mention and give examples for common Linux web servers (such as Apache, Nginx) in addition to IIS when discussing backend configuration and health checks.
Clarify that Application Gateway supports both Windows and Linux backend servers, and provide troubleshooting guidance relevant to both.
Where referencing Windows-specific tools or patterns (such as PowerShell or IIS), always provide Linux equivalents or alternatives.
Add troubleshooting steps for checking firewall rules and service status on Linux (e.g., using systemctl, ufw, firewalld).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on PowerShell and Windows workflows. All command-line examples use Windows PowerShell, with explicit references to Windows paths (e.g., c:\runbooks) and no mention of Linux or cross-platform PowerShell Core usage. There are no examples or instructions for editing runbooks from Linux or macOS environments, nor is there guidance for using PowerShell Core or Azure CLI as alternatives.

Recommendations:

Add equivalent examples using PowerShell Core (pwsh) on Linux/macOS, including Unix-style file paths (e.g., /home/user/runbooks).
Clarify that the Az PowerShell module and cmdlets can be used cross-platform, and provide instructions for installing and using them on Linux/macOS.
Include Azure CLI examples for exporting/importing runbooks, if supported, to provide a non-PowerShell alternative.
Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' or specify when instructions apply to Windows-only environments.
Explicitly state platform compatibility for each method, and provide troubleshooting or caveats for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation 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 and references are presented before any mention of cross-platform tools, and there are no Linux-specific instructions or screenshots. The documentation assumes familiarity with Windows-centric tools and patterns, such as PowerShell cmdlets, and omits guidance for users on Linux or macOS platforms.

Recommendations:

Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash shell command examples where appropriate, especially for unlinking or deleting resources.
Ensure that references to command-line tools do not assume a Windows environment; clarify that steps can be performed from any OS.
Where screenshots are used, consider including examples from both Windows and Linux environments if UI differences exist.
Reorder sections so that Azure CLI and PowerShell examples are presented together or in a neutral order, rather than PowerShell first.
Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and provide any OS-specific caveats if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by referencing Azure PowerShell and linking to a PowerShell-based quickstart as the next step, without mentioning or providing equivalent Azure CLI (cross-platform) or Linux-native instructions. There are no Linux-specific or cross-platform command examples, and the only tooling mentioned for creating the gateway is Azure PowerShell, which is more commonly used on Windows.

Recommendations:

Include Azure CLI examples alongside or before Azure PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux and macOS.
Update the 'Next steps' section to link to both PowerShell and Azure CLI quickstart guides, or to a neutral landing page where users can choose their preferred platform.
Explicitly mention that configuration can be performed using Azure CLI, ARM templates, or the Azure Portal, not just PowerShell.
If referencing sample template files, clarify that these can be deployed using both Azure CLI and PowerShell, and provide example commands for both.
Consider adding a short section or note for Linux/macOS users to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation exhibits a strong Windows bias. It exclusively uses Windows Server as the VM OS in all examples, provides only PowerShell-based instructions for backend configuration (IIS installation), and does not mention or provide alternatives for Linux-based VMs or command-line tools (such as Bash or Azure CLI). The use of Windows-specific tooling and the absence of Linux guidance may hinder users who prefer or require Linux environments.

Recommendations:

Include parallel Linux-based examples for VM creation (e.g., using Ubuntu or CentOS images) alongside Windows Server.
Provide Bash/Azure CLI commands for installing a web server (such as Apache or Nginx) on Linux VMs, in addition to the PowerShell/IIS example.
Explicitly mention that both Windows and Linux VMs are supported as backend pool members, and link to relevant documentation for both.
Where scripts or commands are shown, offer both PowerShell (for Windows) and Bash (for Linux) alternatives.
Consider reordering or balancing the presentation so that Linux and Windows options are given equal prominence, rather than Windows-first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a clear Windows bias: it exclusively uses Windows Server for backend VMs, provides only PowerShell commands for configuration (specifically for installing IIS), and gives instructions for editing the Windows hosts file and using Windows-specific networking commands (ipconfig). There are no Linux-based examples, nor are there instructions for performing equivalent steps on Linux systems.

Recommendations:

Include parallel Linux examples for backend VMs, such as using Ubuntu or another popular Linux distribution.
Provide Bash/Azure CLI commands for installing a web server (e.g., Apache or Nginx) on Linux VMs, alongside the PowerShell/IIS example.
Add instructions for editing the /etc/hosts file on Linux/macOS systems, and mention the use of 'sudo systemctl restart systemd-resolved' or 'sudo systemd-resolve --flush-caches' for DNS cache flushing.
When referencing command-line tools, offer both Windows (ipconfig) and Linux/macOS (ifconfig, ip, or systemd-resolve) equivalents.
Where possible, use cross-platform Azure CLI commands instead of (or in addition to) PowerShell.
Explicitly state that the Application Gateway supports both Windows and Linux backend servers, 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 examples for certificate creation and backend server setup use Windows PowerShell and Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate, Add-WindowsFeature). The tutorial instructs users to create Windows Server VMs and install IIS using PowerShell, with no mention of Linux alternatives or how to perform equivalent steps on Linux systems. There are no Linux shell, OpenSSL, or Apache/Nginx examples, and Linux VMs are not discussed as backend options.

Recommendations:

Provide equivalent Linux instructions for creating a self-signed certificate using OpenSSL, including export to PFX format.
Include examples for deploying Linux VMs (e.g., Ubuntu) as backend servers, and show how to install a web server (e.g., Apache or Nginx) for testing.
Show how to upload certificates generated on Linux to the Azure portal.
Where PowerShell is used, offer Bash or CLI alternatives for Linux/macOS users.
Explicitly state that both Windows and Linux VMs are supported as backends, and provide parity in setup instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only Azure PowerShell examples for configuring custom error pages, with no mention of Azure CLI, Bash, or other cross-platform tools. This creates a Windows-centric bias, as PowerShell is most commonly associated with Windows environments, and Linux users are not given equivalent guidance.

Recommendations:

Add Azure CLI examples for all configuration steps, especially for creating and updating custom error pages at both global and listener levels.
Explicitly mention that Azure CLI and Bash can be used on Linux and MacOS, and provide equivalent commands.
Where PowerShell is referenced, clarify that it is available cross-platform, but still provide CLI/Bash alternatives for parity.
Consider including a table or section comparing PowerShell and CLI commands for common tasks.
Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., file paths, UI elements).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias. All virtual machine creation steps use Windows Server as the OS, and IIS (a Windows-only web server) is installed for backend testing. The only shell/command-line example provided is in PowerShell, with no mention of Linux VMs, Linux web servers (such as Apache or Nginx), or Bash/CLI equivalents. No Linux setup or validation steps are included, and the documentation assumes a Windows-centric workflow throughout.

Recommendations:

Provide parallel instructions for creating Linux-based backend VMs (e.g., Ubuntu or CentOS) alongside Windows VMs.
Include examples for installing a Linux web server (such as Apache or Nginx) on the Linux VMs, with corresponding validation steps.
Offer Bash/Azure CLI command examples for installing web servers and configuring VMs, not just PowerShell.
When referencing OS choices, present Windows and Linux options equally (e.g., 'Select Windows Server or Ubuntu from the list').
Add screenshots and validation steps for Linux-based backend servers to ensure parity.
Avoid assuming IIS or Windows-specific tools as the default for backend validation.

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 instructions use Azure PowerShell, with no mention of Azure CLI or Bash. The example virtual machines are Windows Server only, and the web server setup uses IIS via PowerShell scripts. There are no Linux VM examples, nor instructions for installing a Linux-based web server (e.g., Apache or Nginx). Windows tools and patterns are presented exclusively, with no Linux alternatives or parity.

Recommendations:

Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for preview registration and VM extension management.
Include an example for deploying a Linux VM (e.g., Ubuntu) as a backend, alongside or instead of the Windows VM example.
Demonstrate how to install a web server (e.g., Apache or Nginx) on a Linux VM for backend testing, including the relevant shell commands.
When referencing VM creation, mention both Windows and Linux options, and clarify that Application Gateway supports both.
Balance screenshots and walkthroughs to show both Windows and Linux scenarios where possible.
Add a note or section highlighting cross-platform support and linking to Linux-specific documentation if available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates Windows bias by providing only a PowerShell command (Remove-AzResourceGroup) for resource cleanup, referencing IIS (a Windows web server) as the default backend and validation method, and omitting any Linux/CLI/bash alternatives for deployment, validation, or cleanup. There are no examples or instructions for users on Linux or macOS platforms.

Recommendations:

Provide equivalent Azure CLI (az group delete) and/or Bash commands for resource cleanup alongside the PowerShell example.
Include instructions or examples for deploying and validating the application gateway using Linux-based VMs (e.g., using Nginx or Apache instead of IIS).
Add notes or links for users on Linux/macOS platforms, clarifying how to perform each step without relying on Windows-specific tools.
Ensure that all code snippets and validation steps have both Windows and Linux/macOS equivalents, presented with parity or with Linux/CLI examples first where appropriate.

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 automation and CLI examples using Azure PowerShell cmdlets, with no equivalent Azure CLI (cross-platform) or Bash examples. All scripting and command-line instructions are written in PowerShell, which is most familiar to Windows users. There is no mention of Linux-native tools or workflows, and no guidance for users who prefer or require Bash or Azure CLI. The structure and examples assume a Windows-centric environment and toolset.

Recommendations:

Add equivalent Azure CLI (az) command examples for every PowerShell script block, using Bash syntax where appropriate.
Explicitly mention that both Azure PowerShell and Azure CLI are supported, and provide guidance for users on both Windows and Linux.
Where scripting is shown (e.g., for DNS, certificate management, backend pool configuration), provide Bash/Azure CLI alternatives alongside PowerShell.
Avoid assuming PowerShell as the default automation tool; present both PowerShell and CLI/Bash options in parallel tabs.
Include a note in the prerequisites or introduction clarifying that all steps can be performed on both Windows and Linux, and link to cross-platform tool installation guides.

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 tooling centered around PowerShell cmdlets and syntax. There is no mention of Linux-native scripting, Bash, or cross-platform considerations. The documentation assumes familiarity with Windows-based tools and patterns, and does not provide Linux or cross-platform alternatives or examples.

Recommendations:

Clarify early in the documentation that graphical runbooks in Azure Automation are currently limited to PowerShell and PowerShell Workflow, and explicitly state the lack of Bash or Linux-native scripting support.
If future support for Linux scripting or Bash is planned, add a roadmap or note to inform users.
Where possible, provide guidance for Linux users, such as how to author and manage runbooks that interact with Linux VMs or resources, even if the runbook language is PowerShell.
Include examples of managing Linux resources (e.g., using PowerShell cmdlets to interact with Linux VMs, run commands on Linux, or manage Linux-specific assets).
Reference cross-platform PowerShell (PowerShell Core) where applicable, and clarify any limitations or differences compared to Windows PowerShell.
Consider adding a section or FAQ addressing common Linux user questions, such as interoperability, prerequisites for managing Linux resources, and any platform-specific caveats.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows by referencing PowerShell and Windows-centric tooling for configuration tasks (e.g., configuring WAF custom rules, TLS policy), without providing equivalent CLI or Linux-native examples. There are no Linux shell (Bash/Azure CLI) commands or guidance, and PowerShell is mentioned as the method for advanced configuration. This may hinder Linux users or those preferring cross-platform tools.

Recommendations:

For every PowerShell-based configuration example or reference, provide an equivalent Azure CLI (az) example, which is cross-platform and works natively on Linux, macOS, and Windows.
When referencing documentation for configuration (e.g., WAF custom rules, TLS policy), link to both PowerShell and Azure CLI guides, or provide a unified guide with both sets of instructions.
Explicitly mention that all configuration steps can be performed using Azure CLI or ARM templates, and provide sample commands/scripts.
Avoid implying PowerShell is the only or primary way to perform advanced configuration; instead, present PowerShell and Azure CLI as equal options.
Add a section or callout for Linux/macOS users, highlighting cross-platform tools and any OS-specific considerations.

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 settings, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and referencing Windows-specific patterns such as 'Run as administrator'. There are no Linux or cross-platform alternatives offered for these tasks, and Windows tools are mentioned first and exclusively.

Recommendations:

Provide equivalent Azure CLI or Bash examples for checking Application Gateway settings, not just PowerShell.
Mention and give examples using cross-platform or Linux-native network debugging tools such as tcpdump, Wireshark, or mitmproxy alongside Fiddler.
Include instructions for Linux/macOS users, such as how to install and use these tools on their platforms.
Avoid Windows-specific instructions like 'Right click the setup executable, and run as administrator' without offering Linux/macOS installation guidance.
When referencing tools or commands, present cross-platform options first or in parallel, rather than defaulting to Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is the only scripting example provided for querying Hybrid Runbook Workers, with no equivalent Bash or Linux CLI example. When describing agent-based user Hybrid Runbook Worker deployment, Windows is mentioned before Linux, and the PowerShell-centric workflow is emphasized. References to system accounts and permissions also list Windows first, and the use of Windows-specific tools (PowerShell) is assumed for management tasks. Linux support is acknowledged, but practical examples and tool parity are lacking.

Recommendations:

Provide equivalent Bash or Azure CLI examples for Linux users wherever PowerShell scripts are shown.
When listing instructions or links for both Windows and Linux, alternate the order or present them together to avoid a 'Windows first' impression.
Include Linux-specific management guidance, such as using shell scripts or Linux-native tools, for querying and managing Hybrid Runbook Workers.
Clarify that both Windows and Linux are fully supported, and ensure all operational examples (scripts, permissions, troubleshooting) have Linux counterparts.
Highlight any differences or similarities in user accounts (e.g., System vs nxautomation) more equally, and provide explicit Linux instructions where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias, particularly in the 504 Gateway time-out section, where IIS (a Windows web server) is mentioned first and in more detail than Nginx (a common Linux web server). The IIS section provides a direct link and specific configuration attribute, while the Nginx section is less detailed and lacks a direct link to official documentation. There are no PowerShell-specific examples, but Windows-centric tools and patterns are prioritized. No Linux command-line or troubleshooting examples are provided elsewhere.

Recommendations:

Present Nginx (Linux) and IIS (Windows) backend configuration guidance with equal detail, including direct links to official Nginx documentation (e.g., https://nginx.org/en/docs/) and explicit configuration examples.
When mentioning backend server types, alternate the order (e.g., Nginx first in some cases) or mention both together to avoid implicit prioritization.
Add troubleshooting examples or references for common Linux-based backend servers (such as Apache, Nginx, or Tomcat), not just IIS.
Where possible, provide cross-platform command-line examples (e.g., curl, tcpdump, or Linux log file locations) alongside any Windows-specific guidance.
Explicitly state that Application Gateway supports both Windows and Linux backend servers, and ensure parity in troubleshooting steps and documentation coverage.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing several PowerShell-based command examples (marked as 'powershell-interactive'), using Windows-style variable assignment and scripting patterns, and referencing tools and workflows (such as Azure portal automation exports) that are more familiar to Windows users. Equivalent Linux/bash-native examples are missing or less prominent, and PowerShell is used even where bash would be more cross-platform appropriate. The documentation does not explicitly address Linux users or provide parity in scripting examples.

Recommendations:

For every PowerShell example, provide an equivalent bash shell example, especially for variable assignment and scripting blocks.
When referencing automation exports from the Azure portal, clarify which scripts are bash and which are PowerShell, and ensure both are available and referenced equally.
Avoid using PowerShell-specific syntax (e.g., $var=...) in generic command examples; prefer bash syntax or provide both.
Explicitly state that all commands work in both Windows and Linux environments, or note any differences.
Where possible, use Azure CLI commands in bash syntax as the primary example, as Azure CLI is cross-platform.
Add a section or callouts for Linux/macOS users to clarify any differences in procedure or tooling.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively using Windows Server as the backend VM example and providing only Azure PowerShell commands (with Windows-specific IIS installation) for backend setup and testing. There are no Linux-based backend examples, nor are there Bash/CLI or Linux-native instructions for deploying or testing the backend. This may hinder users who prefer or require Linux environments.

Recommendations:

Include parallel instructions for creating a Linux VM (e.g., Ubuntu) as a backend target, alongside the Windows Server example.
Provide Azure CLI (Bash) commands for installing a simple web server (such as nginx or Apache) on a Linux VM for testing, in addition to the PowerShell/IIS example.
Explicitly mention that both Windows and Linux VMs are supported as backend targets, and link to relevant documentation for both.
Where scripting is required, offer both PowerShell and Bash/CLI examples, or reference cross-platform scripts.
Ensure that screenshots and walkthroughs do not assume a Windows-only environment, and clarify any OS-specific steps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, referencing PowerShell steps before mentioning the Azure CLI, and omitting explicit Linux/bash examples. The 'Next steps' section also directs users to a PowerShell-specific guide, reinforcing the Windows-centric approach. While Azure CLI is mentioned as a supported method, no CLI or bash examples are provided, and the only detailed command-line walkthrough uses PowerShell.

Recommendations:

Add equivalent Azure CLI (az) command examples alongside PowerShell for all command-line instructions, especially in sections where PowerShell is currently the only example.
When referencing command-line tools, mention Azure CLI and PowerShell together, or list Azure CLI first to balance platform representation.
Include bash shell snippets for ARM template deployments and secret referencing, demonstrating cross-platform usage.
In the 'Next steps' section, provide links to both PowerShell and Azure CLI/Linux guides for configuring TLS termination with Key Vault certificates.
Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and provide relevant instructions or links.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias. All certificate export steps are described using Windows GUI tools (Certificate Manager and Certificate Export Wizard), with screenshots and instructions specific to Windows. There are no equivalent instructions or screenshots for performing these tasks on Linux (e.g., using OpenSSL or command-line tools). The only Linux-specific content is a single 'cat' command for concatenating certificates, which is presented after the Windows 'type' command. The prerequisites, export, and certificate management sections omit Linux approaches entirely.

Recommendations:

Add parallel Linux instructions for exporting certificates, using OpenSSL or similar command-line tools, including example commands and expected outputs.
Provide Linux-specific screenshots or terminal outputs where appropriate.
Present Windows and Linux instructions side-by-side or clearly label them, rather than defaulting to Windows-first.
Include a section or note on how to locate and manage certificates on Linux systems.
Avoid referencing Windows-only tools (like Certificate Export Wizard) without Linux alternatives.
Ensure parity in detail and clarity between Windows and Linux instructions throughout the documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on PowerShell-based migration, with all instructions, code snippets, and tooling references centered around PowerShell and the PowerShell Gallery. There are no examples or guidance for Linux or cross-platform users (e.g., Bash, Azure CLI), and the use of Windows-centric tools and patterns (such as .ps1 scripts, PowerShell modules, and Windows file paths) is pervasive. This creates a significant Windows bias and may hinder users on Linux or macOS from following the migration process.

Recommendations:

Provide equivalent Azure CLI (az) commands and scripts for all major steps, including authentication, resource discovery, and migration.
Offer Bash shell script examples or instructions for Linux/macOS users, especially for certificate handling and script execution.
Clearly state platform compatibility of the migration script and, if it is PowerShell Core compatible, provide explicit instructions for installing and running it on Linux/macOS.
Include download and execution instructions for the migration script that do not assume Windows or PowerShell Gallery (e.g., using wget/curl and pwsh).
Mention cross-platform Azure Cloud Shell as a primary option, and provide parity in examples for both PowerShell and Bash environments.
Add a section or callouts for Linux/macOS users, highlighting any prerequisites, differences, or limitations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows/Powershell bias. While the overall content is platform-neutral in its description of Azure Automation and Azure Monitor, it references PowerShell specifically when discussing error streams and job debugging. There are no explicit Linux or cross-platform CLI (e.g., Azure CLI, Bash) examples or mentions. The documentation does not provide Linux-specific guidance or alternative command-line workflows, and it assumes familiarity with PowerShell concepts and terminology.

Recommendations:

Add explicit references and examples for Linux users, such as using Azure CLI or Bash scripts to interact with Azure Automation and Azure Monitor logs.
When discussing job streams and error handling, mention how non-Windows runbooks (e.g., Python, Bash) handle errors and how their output appears in logs.
Where PowerShell is referenced, provide equivalent Azure CLI or REST API examples to ensure parity for Linux and macOS users.
Clarify that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.) and provide examples or links for each.
Include a section or note on how to access and query logs from Linux environments, possibly with sample Bash/Azure CLI commands.

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 references before Azure CLI, omitting Linux-native command-line or OpenSSL examples for certificate handling, and directing users to a PowerShell-based configuration guide as the next step. There is no mention of Linux tools or workflows for extracting or managing certificates, and the CLI section is less detailed than the PowerShell section.

Recommendations:

Provide equal depth and detail for Azure CLI examples as for PowerShell, including multi-step workflows if needed.
Include Linux-native commands (e.g., OpenSSL) for extracting and managing certificate chains, especially in sections discussing certificate preparation.
When referencing further configuration guides, offer both PowerShell and CLI/Linux-based guides as next steps.
Avoid positioning PowerShell or Windows tools as the default or primary method; present CLI and cross-platform approaches first or in parallel.
Explicitly mention that all configuration steps can be performed on Linux/macOS using Azure CLI, and provide any necessary command-line differences or caveats.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and commands for migration and preview registration, with no explicit mention or examples of equivalent Bash or Linux shell commands. The 'Next steps' section also prioritizes PowerShell and does not provide Linux/CLI-focused tutorials. Azure CLI commands are shown, but the usage is wrapped in PowerShell cmdlets (e.g., Set-AzContext), which are not cross-platform, and there is no guidance for Linux users.

Recommendations:

Provide explicit Bash/Linux shell examples for all Azure CLI operations, avoiding reliance on PowerShell-specific cmdlets like Set-AzContext.
When referencing scripts for migration or management, mention both PowerShell and Bash/CLI alternatives, or clarify if only PowerShell is supported.
In 'Next steps' and tutorial links, include Linux/CLI-focused guides alongside or before PowerShell-based tutorials.
Where Azure CLI is used, ensure the examples are platform-agnostic and do not assume a PowerShell environment.
Add a section or note clarifying cross-platform support and linking to relevant Linux documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific DSC resources (such as WaitFor resources in the /powershell/dsc/reference/resources/windows/waitForAllResource link) without mentioning Linux equivalents or cross-platform alternatives. There are no Linux-specific examples or references, and the documentation assumes familiarity with Windows-centric tools and patterns.

Recommendations:

Include references to Linux DSC resources and provide equivalent Linux documentation links where Windows resources are mentioned.
Add explicit examples or notes for configuring network requirements on Linux-based Hybrid Runbook Workers and State Configuration nodes.
Clarify that the guidance applies to both Windows and Linux, and highlight any platform-specific differences in network configuration or tooling.
Where PowerShell or Windows-specific resources are referenced, provide parallel instructions or links for Linux environments (e.g., using OMSAgent or Linux DSC).

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 tooling instructions centered around Windows environments. PowerShell is presented as the default and only scripting language, and all file paths and command examples use Windows conventions. There is no mention of Linux or cross-platform alternatives, nor are there any examples or guidance for users working in Linux environments.

Recommendations:

Provide equivalent examples using Azure Automation Python runbooks or Bash scripts, where applicable.
Include instructions and examples for Linux users, such as using Azure CLI or Bash for automation tasks.
Clarify whether the migration tools and modules are supported or can be run on Linux/macOS, and provide installation steps for those platforms if possible.
Use neutral file path examples (e.g., /home/user/runbooks or $HOME/runbooks) alongside Windows paths.
Mention cross-platform PowerShell (PowerShell Core) and provide guidance for users running PowerShell on Linux or macOS.
Explicitly state any platform limitations or requirements for the migration toolkit and related modules.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows and PowerShell bias. Windows operating systems and PowerShell (especially Windows PowerShell 5.1) are mentioned first and most frequently. Directory path examples use Windows-style paths (e.g., C:\abc), and there are no Linux/macOS path examples. The documentation focuses on PowerShell runbooks and local debugging, with limited mention of Python and no Linux-specific instructions or examples. Linux and macOS are only briefly referenced in the supported OS list, with no parity in examples or troubleshooting.

Recommendations:

Provide Linux/macOS-specific examples for directory paths (e.g., /home/user/abc) alongside Windows examples.
Include instructions and screenshots for configuring the extension and running/debugging runbooks on Linux/macOS.
List supported operating systems in a neutral or rotating order, not always starting with Windows.
Expand Python runbook documentation, including debugging guidance for Linux/macOS users.
Clarify any OS-specific limitations or differences in feature support.
Ensure all command palette and settings navigation instructions are valid for Linux/macOS (e.g., keyboard shortcuts).

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 code examples are in PowerShell, and references to modules, environment variables, and system paths are Windows-specific (e.g., $env:TEMP, C:\temp). Windows tools like WinSCP.exe and IIS are mentioned as module dependencies, with no Linux equivalents or examples provided. There is minimal mention of Linux or Bash scripting, and Linux-specific scenarios are not addressed, leading to a lack of parity for Linux users.

Recommendations:

Provide equivalent Bash or Python examples for common runbook tasks, especially for error handling and file operations.
Include Linux-specific guidance for Hybrid Runbook Workers, such as recommended temp directories (e.g., /tmp) and handling of permissions/elevation.
Mention Linux-compatible tools and modules (e.g., sftp, curl, Apache/Nginx) alongside Windows tools like WinSCP and IIS.
Clarify which features, modules, and cmdlets are supported on Linux Hybrid Runbook Workers, and document any differences.
Add a section or examples for authoring and running Python runbooks, which are supported in Azure Automation and are cross-platform.
Balance references to environment variables and file paths by including both Windows and Linux formats (e.g., $env:TEMP and /tmp).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides detailed configuration steps for Azure Application Gateway Private Link using the Azure portal, Azure PowerShell, and Azure CLI. However, the PowerShell section is more extensive and appears before the CLI section, which may suggest a Windows-first approach. There are no explicit Linux/Bash-specific examples or references to Linux tools, and the CLI section, while present, lacks parity in depth and troubleshooting guidance compared to PowerShell. No Linux-specific considerations or screenshots are provided.

Recommendations:

Ensure that Azure CLI (cross-platform) examples are as detailed and comprehensive as the PowerShell examples, including troubleshooting tips and references.
Consider placing Azure CLI instructions before or alongside PowerShell to avoid a Windows-first impression.
Add explicit notes or examples for Linux/macOS users, such as shell syntax, environment setup, and common issues.
Include screenshots or walkthroughs from a Linux environment where relevant.
Reference cross-platform tools (e.g., Bash, Cloud Shell) and clarify that Azure CLI works natively on Linux/macOS/Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides detailed PowerShell examples for configuring request and response buffers, which are specific to Windows environments. While Azure CLI examples are included (which are cross-platform), the PowerShell section is more comprehensive, covering both creation and update scenarios. There are no explicit Linux shell (bash) or scripting examples, and the documentation references .NET SDK, which is more common in Windows-centric development. No Linux-specific tools or workflows are mentioned.

Recommendations:

Add bash (Linux shell) scripting examples for creating and updating Application Gateway buffer settings, similar to the PowerShell section.
Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample usage in a Linux terminal context.
Include references to cross-platform SDKs (such as Python, Java, or Node.js) in addition to .NET, to ensure parity for non-Windows developers.
Avoid presenting PowerShell as the only scripting option for automation; offer alternatives or note cross-platform options.
Consider reordering examples to present Azure CLI (cross-platform) before PowerShell, or group them together to avoid a 'Windows-first' impression.

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-specific tools (PowerShell cmdlets) are referenced more frequently and prominently than Linux equivalents, and examples for backup/export tasks are provided only for Windows/PowerShell. In several sections, Windows instructions or tools are mentioned before Linux, and some Linux guidance is either less detailed or missing entirely.

Recommendations:

Provide Linux command-line examples (e.g., using Azure CLI or Bash scripts) alongside or before Windows/PowerShell examples for tasks like exporting runbooks, DSC configurations, and managing assets.
Include Linux-specific instructions for tasks such as enabling/disabling TLS protocols, not just a Python script but also relevant shell commands or configuration file edits.
Reference cross-platform tools (e.g., Azure CLI, REST API) wherever possible, rather than focusing on Windows PowerShell cmdlets.
Ensure that tables and lists do not always list Windows platforms first; alternate or group by platform type.
Add explicit Linux examples for asset management, backup, and recovery, not just for TLS configuration.

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 virtual machines as backend examples, providing only PowerShell commands for configuration (specifically for installing IIS), and omitting any Linux-based VM or CLI/Bash examples. The installation and testing instructions are tailored to Windows (IIS, PowerShell), with no mention of Linux alternatives (such as NGINX/Apache or Bash scripting). This may hinder Linux users from following the quickstart without additional research.

Recommendations:

Include parallel instructions for creating and configuring Linux VMs (e.g., Ubuntu) as backend servers.
Provide Linux-based examples for installing a web server (e.g., using Bash to install NGINX or Apache).
Offer Azure CLI and/or Bash script equivalents for all PowerShell commands, especially for installing and configuring backend servers.
When referencing VM images, mention both Windows and popular Linux distributions, and clarify that Application Gateway supports both.
Ensure screenshots and walkthroughs are not exclusively tied to Windows workflows or tools.

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 a PowerShell example for resource cleanup, referencing IIS (a Windows web server) for validation, and omitting Linux/CLI alternatives for these steps. While the page mentions that the quickstart can be completed using the Azure portal, PowerShell, or CLI, the actual walkthrough and examples focus on Windows-centric tools and patterns, with no Linux or cross-platform command-line examples provided inline.

Recommendations:

Provide equivalent Azure CLI commands for resource cleanup (e.g., az group delete) alongside the PowerShell example.
Include validation steps using a Linux-based web server (such as Apache or Nginx) in addition to IIS, or clarify how the template could be modified for a Linux VM.
When referencing tools or commands, present cross-platform (CLI) options first or in parallel with Windows-specific (PowerShell) options.
Add explicit Linux/CLI walkthroughs or links to them in the main flow, not just in the 'Next steps' section.
Clarify in the prerequisites or template review that the example VMs are Windows-based, and provide guidance for users who prefer Linux.

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 examples for configuring Azure RBAC are provided exclusively using Azure PowerShell cmdlets, with no mention or examples of equivalent Azure CLI (cross-platform) commands. The only scripting language shown is PowerShell, which is primarily associated with Windows environments. There is no guidance or examples for Linux/macOS users, nor is there mention of using Azure CLI or REST API for role assignments. The structure and ordering of the documentation also present PowerShell before any other tooling, reinforcing a Windows-first approach.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell cmdlets shown, especially for role assignment, listing, and removal.
Explicitly mention that Azure CLI and REST API can be used for these operations, and provide links or examples.
Where scripts are provided, offer both PowerShell and Bash (Azure CLI) versions side-by-side.
Clarify that PowerShell is available cross-platform, but also highlight the native experience for Linux/macOS users via Azure CLI.
Review all sections for implicit assumptions of a Windows environment and update language to be inclusive of Linux/macOS 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 command-line examples use PowerShell, including certificate creation and IIS installation. The VM scale set is explicitly created with Windows Server 2016 Datacenter, and IIS (a Windows web server) is installed via PowerShell scripts. There are no Linux or cross-platform alternatives provided for certificate creation, backend server OS, or web server setup.

Recommendations:

Provide equivalent Linux examples for all command-line steps, such as using OpenSSL for certificate creation and Bash/Azure CLI for automation.
Include instructions for deploying a Linux-based VM scale set (e.g., Ubuntu) and installing a Linux web server (e.g., Nginx or Apache) as the backend pool.
Offer both PowerShell and Bash/Azure CLI scripts for all automation steps, and clarify which OS each applies to.
Mention Linux tools and patterns alongside Windows ones, and avoid assuming Windows as the default environment.
Add a section or callouts for cross-platform considerations, helping users choose the right instructions for their environment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page is heavily focused on PowerShell and Windows-centric tools, with almost exclusive reference to the PowerShell Gallery, PowerShell modules, and Windows Azure VMs. There are no Linux-specific examples, tools, or workflows provided, and the only mention of Linux is in a tag suggestion. All example runbooks and scenarios are Windows/PowerShell oriented, and there is no parity in guidance for Linux automation or modules.

Recommendations:

Add equivalent examples and workflows for Linux automation, such as using Python runbooks or Bash scripts.
Include references to Linux Azure VMs and provide sample runbooks for managing Linux VMs (e.g., copying files to/from Linux VMs, managing Linux services).
Highlight cross-platform capabilities of Azure Automation, and clarify which features are Windows-only and which are available for Linux.
Provide parity in documentation structure: if PowerShell Gallery and modules are discussed, also discuss Python package sources or Bash script repositories where applicable.
Include at least one end-to-end example for Linux users, such as importing and running a Python runbook on a Linux VM.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides step-by-step instructions for renewing certificates on Azure Application Gateway, with detailed examples for Azure PowerShell and Azure CLI. However, the PowerShell example is presented before the Azure CLI example, and there is no explicit mention or example of Linux-native tools or workflows (such as Bash scripting or OpenSSL usage). The CLI example is generic but does not clarify Linux compatibility, and the PowerShell example is Windows-centric. There are no references to Linux file paths, shell environments, or common Linux certificate management patterns.

Recommendations:

Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more familiar to Linux users.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Linux-specific notes where relevant (e.g., file path formats, certificate file permissions).
Include a Bash shell example for uploading or renewing certificates, especially for scenarios where scripting is involved.
Reference common Linux tools (such as OpenSSL) for certificate preparation or validation.
Add a section or note on how to perform these tasks from a Linux environment, including any prerequisites or differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively references Azure PowerShell scripts for migration tasks, with no mention of Azure CLI, Bash, or Linux-native tooling. All migration automation examples and caveats are centered on PowerShell, which is traditionally associated with Windows environments. There are no examples or guidance for Linux users or those preferring cross-platform tools.

Recommendations:

Provide equivalent Azure CLI (az) commands and scripts for migration tasks alongside PowerShell examples.
Explicitly mention that migration can be performed from Linux/macOS using Azure CLI or PowerShell Core, and provide relevant instructions.
Include Bash or shell script examples where automation is discussed, or clarify cross-platform compatibility of provided scripts.
Add a section comparing PowerShell and CLI approaches, helping users choose the best tool for their environment.
Ensure that all references to tooling (scripts, automation, troubleshooting) include both Windows and Linux-friendly options.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While the main certificate generation workflow uses OpenSSL (cross-platform), Windows tools and patterns are frequently mentioned first or exclusively. The IIS section is more detailed than Linux alternatives, and the only automation example for uploading certificates to Application Gateway is in Azure PowerShell, with no Azure CLI (cross-platform) or ARM/Bicep alternatives. The hosts file editing link is Windows-specific, and some instructions assume a Windows file path structure.

Recommendations:

Provide Azure CLI examples alongside or before Azure PowerShell for certificate upload and configuration, as CLI is cross-platform.
Include Linux/macOS-specific instructions for editing the hosts file (e.g., /etc/hosts), not just a Windows link.
Balance the web server configuration sections: give equal detail for Apache and NGINX as for IIS, including links to official documentation for Linux.
Use neutral file path examples (e.g., ~/Downloads/contoso.cer or /home/user/contoso.cer) instead of Windows paths (C:\Users\...).
Mention that OpenSSL is available on macOS as well as Linux and Windows.
If referencing GUI tools or wizards, ensure Linux alternatives are mentioned or clarify if they are Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively using Windows Server as the backend VM example, providing only PowerShell commands for configuration (specifically for installing IIS), and omitting any Linux-based examples or equivalent Bash/CLI instructions. The tutorial assumes the use of Windows tools and environments, with no mention of Linux alternatives or parity.

Recommendations:

Provide parallel instructions for deploying Linux-based backend VMs (e.g., Ubuntu) alongside the Windows Server example.
Include Bash/Azure CLI commands for installing a web server (such as Apache or Nginx) on Linux VMs, in addition to the PowerShell/IIS example.
Explicitly mention that Application Gateway supports both Windows and Linux backend servers, and offer guidance for both.
When showing code or command-line examples, present both PowerShell (for Windows) and Bash/CLI (for Linux) versions.
Balance the order of presentation so that Linux and Windows options are given equal prominence, or clarify that the steps are similar for both platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by referencing Windows-specific tools and APIs (such as the PFXImportCertStore function), providing configuration guidance and next steps only for PowerShell (a Windows-centric tool), and omitting Linux or cross-platform command-line examples. The documentation also references ARM templates, but PowerShell is emphasized as the primary method. There are no Linux-native instructions or examples, nor are cross-platform tools (like Azure CLI or Bash) mentioned.

Recommendations:

Provide equivalent Azure CLI (az) examples for all PowerShell-based instructions, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Linux/Bash shell command examples for certificate management tasks (such as converting certificates to PFX using OpenSSL), not just references to Windows APIs.
Reference cross-platform certificate tools (e.g., OpenSSL) alongside or before Windows-specific tools and APIs.
In 'Next steps', offer links to both PowerShell and Azure CLI (and/or ARM template) guides for configuring end-to-end TLS.
Where possible, use neutral language (e.g., 'use your preferred tool' or 'using PowerShell, Azure CLI, or the Azure Portal') rather than defaulting to Windows/PowerShell.
Add troubleshooting and configuration notes relevant to Linux environments (such as file permissions, certificate storage locations, etc.).

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 error handling concepts and examples are presented exclusively in terms of PowerShell cmdlets and Windows-centric tools (e.g., Write-Warning, Start-AzVM, Get-AutomationVariable). There is no mention of Linux runbooks, Bash, or cross-platform scripting. The terminology and examples assume the user is working in a Windows/PowerShell environment, with no Linux or cross-platform parity.

Recommendations:

Include examples and explanations for error handling in Linux-based runbooks, such as using Bash or Python activities.
Mention and demonstrate how error handling works in graphical runbooks that target Linux hybrid workers or use cross-platform scripting languages.
Provide equivalent Linux tool or command examples (e.g., using shell scripts or Python for error handling and notifications).
Clarify in the introduction that the guidance is PowerShell-specific, or restructure the documentation to present both Windows/PowerShell and Linux/Bash/Python approaches side by side.
Reference Azure Automation support for Linux hybrid workers and how error handling differs or is implemented in those scenarios.

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 examples and instructions use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Linux or cross-platform alternatives. There are no CLI, Bash, or Linux-native certificate generation examples, and the tutorial assumes a Windows environment throughout.

Recommendations:

Provide equivalent Azure CLI (az) commands for all resource creation and configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Linux-native instructions for generating self-signed certificates (e.g., using OpenSSL) alongside the PowerShell examples.
Clearly indicate which steps are platform-specific and offer alternatives for non-Windows users.
Reorganize the documentation so that cross-platform (CLI) examples are presented first or in parallel with PowerShell/Windows-specific instructions.
Add notes or links to relevant documentation for Linux/macOS users, such as installing Azure CLI or using Bash scripts.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references Windows Server 2022 Datacenter: Azure Edition and only describes enabling SMB over QUIC and Automanage best practices for Windows VMs. There are no examples, instructions, or mentions of Linux support, tools, or equivalents. All links and references point to Windows Server documentation, and the workflow assumes a Windows-centric environment.

Recommendations:

Clearly state whether SMB over QUIC and Automanage best practices are supported or unsupported on Linux VMs.
If Linux support exists, provide equivalent instructions and examples for Linux-based VMs, including any required packages, configuration steps, and management tools.
If Linux is not supported, explicitly mention this limitation early in the documentation to set user expectations.
Include references or links to Linux SMB (Samba) documentation and clarify differences in feature support between Windows and Linux.
Consider providing a comparison table of supported features and management workflows for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod, PowerShell syntax) for all examples and instructions. There are no equivalent examples for Linux users (e.g., using Bash, curl, or az CLI), and the workflow assumes familiarity with Windows scripting and tools. This creates a significant bias toward Windows environments and leaves Linux users without clear guidance.

Recommendations:

Provide equivalent examples using Bash and curl for REST API calls.
Include az CLI commands for all operations where possible, as az CLI is cross-platform.
Explicitly mention that the steps can be performed from any OS, and clarify tool requirements.
Structure the documentation to present both Windows/PowerShell and Linux/Bash examples side by side.
Avoid assuming PowerShell as the default scripting environment; offer alternatives for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation lists Windows Server versions first in the supported OS section and includes a Windows-only service (Microsoft Antimalware) in the participating services table. There are no Linux-specific examples, tools, or guidance, and the only security/antimalware solution mentioned is exclusive to Windows. No Linux security or monitoring tools are referenced, and no Linux-specific configuration or troubleshooting examples are provided.

Recommendations:

List Linux distributions before or alongside Windows Server in the supported operating systems section to avoid the impression of Windows primacy.
Include Linux-specific security/antimalware solutions (such as Microsoft Defender for Endpoint on Linux or third-party supported solutions) in the participating services table, or clarify the Linux equivalents.
Add Linux-specific configuration, troubleshooting, or onboarding examples, especially for common tasks like monitoring, update management, and compliance.
Reference Linux-native tools and patterns (e.g., systemd, auditd, Linux package managers) where relevant, or provide links to Linux documentation for these services.
Clearly indicate which services or features are Windows-only and provide Linux alternatives or workarounds where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing PowerShell (a Windows-centric technology) in both order and depth of coverage, providing only PowerShell code examples (with Windows file paths), and referencing Windows-specific tools and environment variables. Linux support is mentioned but not illustrated with examples, and Linux-specific considerations are minimal or absent.

Recommendations:

Provide Linux-specific examples for PowerShell runbooks, including file paths and environment variables relevant to Linux (e.g., /home/user/modules instead of C:\modules).
Include explicit guidance and troubleshooting steps for running PowerShell and Python runbooks on Linux Hybrid Runbook Workers, not just Windows.
Balance the order of presentation so that Python and Linux scenarios are not always after PowerShell/Windows; consider parallel sections or tables.
Where Windows-specific tools or patterns are discussed (e.g., environment variables, file paths), provide Linux equivalents or note differences.
Add sample Python runbooks that demonstrate both Windows and Linux compatibility, and clarify any OS-specific limitations.
Highlight any differences in module/package management between Windows and Linux Hybrid Runbook Workers.
Explicitly state when a feature or limitation applies only to Windows, Linux, or both, to avoid ambiguity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exclusively uses PowerShell-based examples and workflows, referencing the AWS PowerShell module, PowerShell Gallery, and PowerShell ISE. There are no examples or instructions for using Linux-native tools (such as AWS CLI with Bash or Python scripts), nor is there mention of cross-platform scripting options. The documentation assumes a Windows-centric workflow and does not address Linux users or provide parity in tooling or examples.

Recommendations:

Provide equivalent instructions and examples using the AWS CLI in Bash or Python scripts for Linux users.
Include steps for importing and using AWS CLI modules in Azure Automation, highlighting cross-platform compatibility.
Mention and demonstrate how to author runbooks using Python or Bash, not just PowerShell.
Avoid referencing Windows-specific tools (e.g., PowerShell ISE) as the only option; suggest alternatives like VS Code or cloud-based editors.
Reorder sections or provide parallel instructions so that Linux and cross-platform options are presented alongside or before Windows-specific ones.
Explicitly state that Azure Automation supports multiple scripting languages and link to relevant documentation for non-PowerShell options.

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 are provided exclusively using Azure PowerShell cmdlets, with no equivalent examples for Azure CLI, Bash, or other cross-platform tools. The PowerShell sections are always presented first and in detail, while Linux-native or cross-platform approaches are either omitted or only briefly mentioned (e.g., Azure CLI is only referenced in passing for revocation). The documentation assumes the user is familiar with PowerShell and Windows tooling, and there is no guidance for users working on Linux or macOS environments.

Recommendations:

Provide Azure CLI examples for all PowerShell command sequences, including creating and assigning managed identities, configuring Key Vault access policies, and updating Automation account encryption settings.
Include Bash shell script examples where appropriate, especially for REST API calls using curl.
Explicitly mention cross-platform compatibility and note any differences in behavior or prerequisites between Windows and Linux/macOS environments.
Reorganize sections to present PowerShell and CLI examples side-by-side, or clearly label them as 'Windows/PowerShell' and 'Linux/macOS/CLI' to improve discoverability for non-Windows users.
Expand the 'Revocation of access' section to include full Azure CLI command examples, not just a reference link.
Add a note early in the document clarifying that all operations can be performed from any OS using Azure CLI or REST, not just PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented towards Windows environments, with exclusive use of PowerShell scripts, Windows-style file paths (e.g., D:\examplefiles), and instructions that assume the use of Windows tools and conventions. There are no examples or guidance for Linux-based Hybrid Runbook Workers, nor are Bash or Linux shell equivalents provided. The only method shown for creating test files is via PowerShell, and all directory references use Windows syntax.

Recommendations:

Include parallel Linux/Bash examples for all PowerShell commands, such as using 'touch' to create files.
Mention and show Linux file path formats (e.g., /home/user/examplefiles) alongside Windows paths.
Clarify that Hybrid Runbook Workers can run on Linux, and provide setup and usage instructions for Linux environments.
Ensure that documentation steps and screenshots are not exclusively Windows-centric; add Linux equivalents where applicable.
Reference both PowerShell and Bash (or other relevant shells) in runbook authoring and testing sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows-first bias in its guidance for installing and managing Hybrid Runbook Workers. All referenced installation and management links explicitly use the 'windows' tab, and there is no mention of Linux equivalents or examples. The documentation refers to VM Contributor roles and domain controllers, which are more relevant to Windows environments, and does not provide parity for Linux-based automation scenarios.

Recommendations:

Include explicit instructions and examples for installing and managing Hybrid Runbook Workers on Linux machines, using the appropriate tabs and links.
Ensure that all referenced links (such as installation guides) provide both Windows and Linux options, and do not default to the Windows tab.
Mention Linux-specific security considerations (e.g., avoiding installation on critical Linux servers, using sudoers for least privilege) alongside Windows-specific advice.
Provide examples of runbook execution and authentication for both Windows and Linux Hybrid Workers.
Review all sections for references to Windows-only tools or concepts and add Linux equivalents where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows and PowerShell, with all examples and terminology referencing PowerShell commands, workflows, and concepts. There is no mention of Linux, Bash, or cross-platform scripting, and the SDK and its usage are described exclusively in the context of PowerShell and Windows-centric workflows.

Recommendations:

Explicitly state whether the SDK and graphical runbooks support Linux Hybrid Runbook Workers or cross-platform execution.
Provide examples or guidance for authoring graphical runbooks that invoke Bash scripts or Linux commands, if supported.
Clarify whether the .dll and SDK can be used on non-Windows platforms (e.g., via .NET Core/5/6+ on Linux/macOS), and provide instructions for those environments if possible.
If Linux is not supported, clearly state this limitation at the top of the documentation.
Include a table or section comparing Windows/PowerShell and Linux/Bash support for graphical runbooks, so users understand platform compatibility.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a Windows bias by referencing PowerShell cmdlets as the primary method for automation, mentioning Azure Resource Manager and PowerShell together, and omitting equivalent Linux/CLI examples or tools. There is no mention of Bash, Azure CLI, or Linux-specific automation patterns. The language and examples assume a Windows-centric environment, with no guidance for users operating from Linux or cross-platform environments.

Recommendations:

Include equivalent examples using Azure CLI (az) commands alongside PowerShell cmdlets.
Explicitly mention that runbooks can be authored in Python or Bash, and provide examples for these languages.
Reference cross-platform tools and patterns, such as Bash scripting or Linux cron integration, where applicable.
Ensure that instructions for authentication and permissions are not tied exclusively to Windows tools or terminology.
Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
Review and update terminology to be platform-neutral (e.g., refer to 'command-line tools' instead of only 'PowerShell').

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 code examples, setup instructions, and tool references are exclusively for PowerShell, with no mention of Bash, Azure CLI, or Linux-based approaches. Windows/PowerShell tools and patterns are presented as the default and only option, with no Linux or cross-platform alternatives provided.

Recommendations:

Provide equivalent examples using Azure CLI and Bash scripts for Linux users.
Mention that Azure Automation runbooks can also be authored in Python and provide a Python example for sending email via SendGrid.
Include instructions for installing and using the Azure CLI on Linux/macOS, and show how to perform prerequisite steps (e.g., Key Vault creation, secret management, role assignment) using CLI commands.
Clarify that the PowerShell examples work cross-platform (if true), or specify any platform limitations.
Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
Balance the order of presentation so that Windows/PowerShell and Linux/CLI approaches 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 and PowerShell bias. All code examples for creating, invoking, and managing webhooks use PowerShell cmdlets or scripts, with no equivalent examples for Linux-native tools (such as Bash, curl, or Azure CLI). Even REST API examples are shown using PowerShell's Invoke-RestMethod. There are no Bash, curl, or Azure CLI examples, and the only scripting language shown for interacting with Azure Automation is PowerShell. This makes the documentation less accessible for Linux or cross-platform users.

Recommendations:

Add equivalent examples using Azure CLI for all PowerShell-based operations (creating, updating, deleting webhooks, invoking webhooks, retrieving job output, etc.).
Provide REST API examples using curl or HTTPie in Bash, not just PowerShell's Invoke-RestMethod.
Include sample scripts in Bash for preparing JSON payloads and invoking webhooks.
When showing code tabs, present Azure CLI or Bash/curl examples before or alongside PowerShell, not only after.
Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users.
Where possible, use neutral language (e.g., 'command line' instead of 'PowerShell prompt') and avoid assuming a Windows environment.

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 code examples for enabling and using managed identities (including REST API, ARM templates, authentication, and resource access) are provided exclusively in PowerShell, with only a single Python example (and no Bash/CLI/Linux shell examples). Windows tools and paths are referenced first or exclusively in several places, and Linux equivalents are either missing, less detailed, or mentioned after Windows. There are no Azure CLI, Bash, or Linux-native scripting examples for the main workflows, and the documentation assumes PowerShell as the default automation and scripting environment.

Recommendations:

Provide Azure CLI examples for all major workflows (enabling managed identity, assigning roles, authenticating, accessing resources) alongside PowerShell.
Include Bash/shell script examples for REST API calls and token retrieval, especially for Linux-based Automation accounts.
When referencing file paths or commands for both Windows and Linux Hybrid Runbook Workers, present them in parallel and with equal detail.
Add Python and/or Bash examples for accessing Azure Key Vault, SQL Database, and other resources using managed identity, not just PowerShell.
Avoid assuming PowerShell as the default; explicitly state when an example is PowerShell and offer alternatives for Linux users.
Where possible, use cross-platform tools (e.g., Azure CLI, REST via curl) in examples to ensure parity.
Review and update all sections to ensure Linux and cross-platform users can follow the documentation without needing to translate PowerShell to their environment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a notable Windows bias. PowerShell is used as the primary scripting example throughout, including for Linux scenarios, rather than native Linux tools or shell scripts. Windows-specific tools, paths, and patterns (such as C:\ paths, Windows PowerShell, .NET Framework, and registry keys) are referenced frequently and often before or instead of Linux equivalents. The Bicep and ARM template examples are exclusively for Windows VMs, with no Linux VM deployment examples. Linux-specific guidance is minimal or absent in several sections, especially for automation and extension management.

Recommendations:

Provide native Linux shell (bash) examples for all automation and extension installation steps, especially where PowerShell is currently used for Linux.
Include Bicep and ARM template examples for deploying Hybrid Runbook Worker extensions to Linux VMs, not just Windows.
When listing requirements, tools, or commands, present Linux and Windows options side-by-side, or alternate which platform is shown first.
Reference Linux file paths, permissions, and troubleshooting steps wherever Windows equivalents are given (e.g., folder permissions, uninstall instructions, proxy settings).
Clarify when PowerShell Core is required on Linux, and provide installation and usage guidance for bash or Python where possible.
Expand troubleshooting and management sections to include Linux-specific issues, logs, and commands.
Ensure all code samples, especially in REST, CLI, and scripting, show both Windows and Linux extension types and relevant settings.

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 code examples are provided exclusively in PowerShell, with no Bash, Python, or cross-platform CLI equivalents. File paths and script references use Windows conventions (e.g., C:\Runbooks\), and there is no mention of Linux shell environments or tools. The documentation assumes the use of Windows tooling and patterns throughout, omitting guidance for Linux users or those preferring cross-platform automation approaches.

Recommendations:

Provide equivalent examples using Azure CLI (az), Bash, or Python where possible, especially for common tasks such as creating, importing, publishing, and retrieving runbooks.
Include Linux-friendly file path examples and clarify that runbooks can be authored and managed from Linux/macOS environments.
Mention and demonstrate cross-platform tools and workflows (e.g., using az CLI, REST API, or SDKs) alongside PowerShell.
Explicitly state platform requirements or limitations, and offer guidance for users working from Linux or macOS.
Balance the order of presentation so that Windows/PowerShell and Linux/CLI approaches are given equal prominence.
Add notes or links to resources for Linux users, such as how to install and use Azure CLI or Python SDK for automation tasks.

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 automation and scripting examples use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native tools. Instructions for module installation and hybrid worker setup are PowerShell-specific, and there are no Linux or cross-platform alternatives provided. The documentation assumes a Windows-centric workflow throughout.

Recommendations:

Provide equivalent examples using Azure CLI (az) and Bash scripts for connecting and managing Azure SQL databases.
Include instructions for installing required modules or packages on Linux-based Hybrid Runbook Workers, not just via PowerShell.
Mention and demonstrate how to use Azure Automation with Python runbooks, which are supported and cross-platform.
Explicitly state cross-platform compatibility where applicable, and clarify any Windows-specific requirements.
Reorder or balance the presentation so that Linux and cross-platform methods are given equal prominence to PowerShell/Windows approaches.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a clear bias towards Windows and PowerShell environments. Most examples, especially for creating and managing runbooks and runtime environments, focus on PowerShell, with detailed steps and REST API payloads referencing PowerShell modules (e.g., Az PowerShell, Get-Module). Windows/PowerShell-specific packaging (.zip, PowerShell Gallery) is emphasized, while Linux/Python equivalents are only briefly mentioned or relegated to notes. There are no concrete Linux shell or Python-centric examples, and Windows tools and conventions are referenced before or instead of Linux alternatives.

Recommendations:

Provide equivalent, detailed examples for Python runbooks, including REST API payloads and portal workflows.
Include explicit Linux/Python packaging instructions and examples (e.g., using .whl files, pip, or Linux shell commands) alongside PowerShell/Windows instructions.
Balance the documentation by presenting Python/Linux options before or alongside PowerShell/Windows options, rather than as afterthoughts or notes.
Add screenshots and walkthroughs for Python runbooks and Linux-based runtime environments, not just PowerShell.
Reference Linux/Python package repositories (e.g., PyPI) and tools (e.g., pip) where appropriate, not just PowerShell Gallery.
Clarify when instructions or features are platform-specific, and provide parity where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a strong bias toward Windows and PowerShell environments. All code samples, migration steps, and runbook examples exclusively use PowerShell cmdlets and scripts, with no mention of Linux shell (Bash), Python, or cross-platform automation approaches. The documentation assumes the use of Windows-centric tools and workflows, such as PowerShell modules (Az, AzureRM), and does not provide equivalent guidance or examples for Linux-based Automation accounts or hybrid workers running on Linux. The order and language also assume PowerShell as the default, reinforcing a Windows-first perspective.

Recommendations:

Add equivalent examples using Azure CLI (az) and/or Python SDK for runbook authentication and resource management, demonstrating how to migrate from Run As accounts to managed identities in Linux-based runbooks.
Include sample scripts for Bash and Python runbooks, showing how to authenticate with managed identities and perform common automation tasks.
Explicitly mention support for Linux hybrid runbook workers, and provide migration guidance and troubleshooting steps specific to Linux environments.
Clarify in prerequisites and migration steps that both Windows and Linux runbook environments are supported, and link to platform-specific documentation where appropriate.
Balance the order of presentation so that cross-platform or Linux-native tools (e.g., Azure CLI, Python) are mentioned alongside or before PowerShell, to avoid reinforcing a Windows-first mindset.

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-centric tools (such as DSC) are mentioned more frequently and in greater detail than their Linux equivalents. PowerShell is referenced as the primary automation language, with only secondary mention of Python. The configuration management section focuses exclusively on PowerShell DSC, with no mention of Linux-native configuration management tools or approaches. Examples and scenarios often reference Windows-specific technologies (e.g., Active Directory, SQL Server, SharePoint) before or instead of Linux alternatives. There is a lack of explicit Linux-focused examples, tools, or guidance, despite claims of heterogeneous support.

Recommendations:

Provide equal prominence to Linux automation tools and scripting languages (e.g., Bash, Python) alongside PowerShell.
Include Linux-native configuration management options or clarify how DSC applies to Linux systems.
Add Linux-specific examples and scenarios, such as automating package management, service management, or configuration on Linux VMs.
Mention Linux equivalents to Windows technologies referenced (e.g., reference LDAP or Samba alongside Active Directory, PostgreSQL/MySQL alongside SQL Server).
Ensure that documentation for modules, galleries, and shared resources includes Linux-relevant content and examples.
Clarify any limitations or differences in feature support between Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows/Powershell bias. All command-line examples use Powershell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. Even REST API usage is shown via Powershell's Invoke-RestMethod, and variable paths use Windows-style backslashes. There are no Linux or cross-platform command-line examples, and Powershell is assumed as the default scripting environment throughout.

Recommendations:

Add equivalent Azure CLI examples for all operations, including authentication, resource modification, and verification.
Provide Bash shell examples for REST API calls using curl, including how to obtain an access token with Azure CLI.
Use platform-neutral variable naming and file path conventions, or show both Windows and Linux path styles.
Explicitly mention that Powershell examples are for Windows (and optionally for cross-platform Powershell Core), and provide Linux/macOS alternatives.
In sections where Powershell is used to verify results, also show how to do this with Azure CLI (e.g., az automation account show).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows-first bias, particularly in the sections on preparing wheel files for Python 3.8, where only Windows instructions are provided initially and in more detail. PowerShell cmdlets are heavily featured for package management, with no equivalent CLI or bash examples for Linux users. Windows-specific terminology and tools are referenced before Linux equivalents, and Linux guidance is only provided for the Python 3.10 (preview) scenario. There are no Linux/CLI examples for managing packages, and the PowerShell-centric approach may alienate Linux users.

Recommendations:

Provide equivalent Linux (bash/CLI) instructions for preparing wheel files for Python 3.8, not just for Python 3.10.
Include Azure CLI examples for all package management tasks currently shown only with PowerShell cmdlets.
When describing architecture or platform requirements, mention both Windows and Linux environments together, rather than prioritizing Windows.
Add explicit Linux-based examples for Hybrid Runbook Worker scenarios, including how to prepare and upload packages from Linux.
Where possible, use cross-platform tools (e.g., Azure CLI, REST API) in examples, or provide both PowerShell and bash/CLI alternatives.
Review and balance screenshots and terminology to ensure Linux users are equally represented.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates Windows bias by providing explicit instructions and command-line examples only for Windows environments (e.g., using Windows 64-bit machine and Windows-style pip invocation), while omitting equivalent Linux or cross-platform instructions. There are no Linux or macOS examples or notes, and Windows tools and paths are mentioned exclusively.

Recommendations:

Include Linux/macOS equivalents for all command-line instructions, such as pip usage and file paths.
Provide cross-platform guidance or clarify when steps are Windows-specific.
Add a note or section addressing how to perform the same tasks on Linux (e.g., using 'pip download' on Linux/Mac, and where to find the downloaded files).
Avoid using only Windows-style paths (e.g., C:\Python27\Scripts\pip2.7.exe); instead, show both Windows and Unix-style commands.
Mention any platform-specific requirements or differences explicitly to help non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several ways: Windows examples and tools (such as PowerShell and Windows-specific registry paths) are presented first or exclusively in key sections, especially in the Bicep and ARM template examples, which only show Windows VM creation and extension installation. PowerShell is heavily featured, while Linux command-line or scripting examples are minimal or absent for core tasks. Some operational steps (like folder permissions and extension installation) reference only Windows paths or tools, and Linux equivalents are either missing or less detailed.

Recommendations:

Provide parallel Linux examples for all automation, scripting, and deployment scenarios (e.g., show how to deploy the Hybrid Worker extension to a Linux VM using Bicep/ARM templates, Azure CLI, REST API, and PowerShell).
In code samples and step-by-step instructions, present both Windows and Linux paths, commands, and configuration details side-by-side or in clearly separated tabs.
Include Linux-specific operational guidance, such as required folder permissions, service management, and troubleshooting steps, matching the detail provided for Windows.
When listing tools or onboarding channels (e.g., PowerShell, Azure CLI), ensure Linux-friendly tools and workflows are given equal prominence and detail.
Avoid presenting Windows instructions or tools before Linux equivalents unless there is a technical reason; strive for parity in ordering and depth.
Expand the 'Remove agent-based Hybrid Worker' and other operational sections to provide more comprehensive Linux removal and cleanup steps, including agent uninstallation and configuration file cleanup.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows and PowerShell by consistently prioritizing PowerShell runbooks, mentioning PowerShell versions and features before Python or Linux equivalents, and providing examples and feature announcements that focus on PowerShell and Windows-centric tools. Linux and Python support are mentioned, but often as secondary or afterthoughts, and there are few, if any, Linux-specific examples or guidance.

Recommendations:

Ensure that all feature announcements and examples include both PowerShell and Python (or Bash) runbook scenarios, with equal prominence.
When discussing runbook support, mention Python and Linux support alongside PowerShell and Windows, not after.
Provide Linux-specific guidance, examples, and migration paths where appropriate (e.g., for Hybrid Runbook Workers, show both Windows and Linux installation/migration steps).
Highlight cross-platform capabilities and tools (such as Azure CLI in Bash) equally with PowerShell.
Where scripts or GitHub resources are referenced, include both PowerShell and Python/Bash versions, or clarify cross-platform compatibility.
Audit the documentation for sections that implicitly assume a Windows/PowerShell environment and revise to be OS-agnostic or to provide Linux parity.

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. PowerShell is consistently mentioned first and in greater detail than Python, with specific focus on PowerShell versions and features. The Azure CLI is only discussed in the context of PowerShell 7.4, with no mention of Bash or Linux-native scripting environments. There are no examples or references for Linux shell scripting, and the only default packages highlighted are Az PowerShell and Azure CLI (as used from PowerShell). The documentation does not provide parity for Linux users or those using Bash or other Unix shells.

Recommendations:

Include examples and explanations for using Azure CLI in Bash or Linux-native environments, not just PowerShell.
List Bash or shell scripting as a supported language if applicable, or clarify its support status.
Provide Linux-centric package examples (e.g., pip for Python, apt/yum for system packages) alongside PowerShell examples.
Mention and document any Linux-specific runtime environments or limitations, if they exist.
Ensure that references and links are balanced between PowerShell and Python, and add links to Bash or Linux scripting documentation where relevant.
Explicitly state if certain features are Windows/PowerShell-only, and suggest Linux alternatives if available.

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 examples are provided exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native workflows. The prerequisites and configuration steps assume the use of PowerShell consoles, and references to file encoding issues point to PowerShell/VSCode documentation. There are no Linux or cross-platform command-line examples, and the documentation does not address how users on Linux or macOS systems might perform equivalent tasks.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell commands, especially for assigning roles and configuring source control.
Include explicit instructions and examples for Linux/macOS users, such as using Bash or cross-platform shells.
Reference cross-platform tools and workflows (e.g., Azure CLI, REST API via curl) alongside PowerShell.
When discussing file encoding issues, link to general encoding best practices or Linux/macOS-specific guidance, not just PowerShell/VSCode.
Ensure that screenshots and UI walkthroughs do not assume a Windows environment where not necessary.
Clearly state platform compatibility and any limitations for Linux/macOS users at the start of the documentation.

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 code examples use PowerShell cmdlets and Windows-specific DSC resources (e.g., WindowsFeature IIS). The prerequisites and instructions focus exclusively on Windows VMs, with no Linux-specific examples or guidance. References and links are also Windows/PowerShell-centric, and there is no demonstration of managing Linux nodes or using Linux-compatible DSC resources.

Recommendations:

Add parallel examples for onboarding and configuring Linux VMs, including sample configurations using Linux DSC resources (e.g., nxFile, nxPackage).
Include prerequisites and instructions for Linux VMs, such as supported distributions and required packages.
Provide Bash/CLI examples where possible, or at least reference how Linux users can interact with Azure Automation State Configuration.
Clarify in the introduction and throughout the document whether Linux is still supported, especially in light of the included retirement announcement.
Link to documentation specifically about managing Linux nodes with Azure Automation State Configuration, if still supported.

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. Nearly all code examples, parameter definitions, and workflows are presented using PowerShell or PowerShell Workflow, which are Windows-centric technologies. The only mention of Python runbooks is brief and lacks concrete examples, and there are no examples or guidance for Linux shell scripting or CLI-based automation. The documentation assumes the use of Windows tools and patterns (e.g., PowerShell cmdlets, .NET types), and Linux/Unix equivalents are not discussed or demonstrated. Even SDK and REST API examples are shown in C# (another Windows-centric language), and all automation scenarios are illustrated using Windows tools and conventions.

Recommendations:

Provide equivalent examples for Linux/Unix environments, such as using Bash scripts or Azure CLI to start and manage runbooks.
Expand the Python runbook section with concrete parameter handling examples, including how to pass parameters from Linux environments.
Include examples of starting runbooks using Azure CLI (az automation runbook start) and show how to pass parameters from the command line.
Discuss differences and considerations for users running automation from Linux/macOS, such as authentication and file path handling.
Balance SDK examples by including Python or JavaScript code snippets, not just C#.
Clarify which features or patterns are Windows/PowerShell-specific and provide Linux-friendly alternatives where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a clear Windows bias. All command-line examples use Windows PowerShell, and there are no examples for Linux users (e.g., Azure CLI, Bash, or cross-platform PowerShell Core). The term 'Windows PowerShell' is used explicitly, and the documentation does not mention or provide parity for Linux tools or workflows. The order of presentation also places Windows/PowerShell methods before more cross-platform or API-based approaches.

Recommendations:

Add equivalent Azure CLI examples for starting and managing runbooks, as Azure CLI is cross-platform and widely used on Linux.
Clarify when 'PowerShell' refers to Windows PowerShell versus cross-platform PowerShell Core, and provide examples that work on both.
Include Bash/cURL examples for API-based methods to demonstrate Linux-friendly workflows.
Reorder the methods table or present cross-platform options (like Azure CLI and REST API) before or alongside Windows-specific tools.
Explicitly mention Linux/macOS compatibility and provide guidance for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and the .NET Framework, which are primarily Windows-based. Windows-specific tools and workflows (e.g., Visual Studio, Windows Command Prompt, PowerShell) are mentioned first and in detail. While Linux/macOS environment variable commands are included, they are always listed last and lack parity in development environment guidance (e.g., no mention of cross-platform .NET Core, VS Code, or Mono). The tutorial assumes the use of Windows throughout, with no Linux-specific or cross-platform development instructions.

Recommendations:

Provide equivalent instructions for developing and running the sample on Linux and macOS, such as using Visual Studio Code or JetBrains Rider, and .NET Core/Mono where possible.
List Linux/macOS commands before or alongside Windows commands to avoid 'windows_first' ordering.
Include guidance for setting up and running ASP.NET applications on Linux (e.g., using Mono or .NET Core if applicable), or explicitly state Windows-only limitations.
Mention and provide examples for cross-platform CLI tools (e.g., dotnet CLI) instead of or in addition to Visual Studio GUI steps.
Clarify any Windows-only requirements up front, and suggest alternatives or workarounds for non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias, particularly in the 'Build and run the app locally' section, where Windows command prompt and PowerShell instructions are consistently presented before Linux/macOS equivalents. Visual Studio, a Windows-centric IDE, is the only development environment mentioned. The overall workflow and examples assume a Windows environment, with only brief, secondary mention of Linux/macOS commands. There are no Linux-specific development tools or editors referenced, and the guidance to restart Visual Studio further centers the Windows experience.

Recommendations:

Present Linux/macOS instructions alongside or before Windows instructions, or group them equally to avoid the perception of Windows primacy.
Include alternative development environment options, such as Visual Studio Code or JetBrains Rider, which are cross-platform, and provide relevant instructions for those editors.
Explicitly mention that the .NET Framework is Windows-only, but highlight that .NET (Core/5+) is cross-platform and link to equivalent tutorials for those platforms.
Provide guidance for building and running the app using the .NET CLI (dotnet), where possible, to support Linux/macOS users.
When referencing environment variable setup, ensure parity in detail and order for all platforms.
Consider adding a section or callout for Linux/macOS users, outlining any platform-specific caveats or alternative workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. Windows command prompt and PowerShell instructions are presented before macOS and Linux equivalents. The example project is based on ASP.NET Core, and the build script uses MSBuild, which is more common on Windows (though cross-platform). Visual Studio Code is mentioned as cross-platform, but the workflow and examples are more familiar to Windows users. There is no explicit omission of Linux/macOS steps, but the ordering and tool choices favor Windows.

Recommendations:

Present Linux/macOS and Windows instructions in parallel or in a neutral order (alphabetically or grouped by shell type).
Include explicit notes about cross-platform compatibility of MSBuild and .NET CLI, and provide alternative scripts if needed for non-Windows environments.
Add more context or examples for Linux/macOS users, such as using bash scripts or alternative editors.
Highlight that the Azure CLI and .NET CLI are fully cross-platform, and provide troubleshooting tips for common Linux/macOS issues.
Consider using generic environment variable setting instructions first, then provide OS-specific tabs if needed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page generally uses cross-platform tools (Azure CLI, Helm), but in the section on passing literal key-values to Helm, only a PowerShell script is provided, with no Bash/Linux shell equivalent. The PowerShell example is presented as the only method for dynamic key-value injection, which may disadvantage Linux/macOS users. There is no mention or example of how to achieve the same result using Bash or other Unix shells, and the PowerShell example appears before any alternative is discussed.

Recommendations:

Provide equivalent Bash (or POSIX shell) examples alongside PowerShell scripts for dynamic key-value injection with Helm.
Explicitly mention that the PowerShell script is for Windows users and offer a parallel solution for Linux/macOS users.
Consider presenting cross-platform (Bash first or both together) examples when scripting is required, to avoid the perception of Windows-first bias.
Audit other sections for subtle Windows-centric language or tool recommendations and ensure parity in instructions for Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows. In the Azure CLI section, Windows PowerShell is mentioned as the default example for opening a command console, and in the PowerShell section, only Windows PowerShell is referenced. There are no explicit Linux shell (e.g., Bash) or macOS terminal instructions, nor are there screenshots or examples tailored for non-Windows environments. The documentation assumes familiarity with Windows-centric tools and does not provide parity for Linux users.

Recommendations:

In the Azure CLI section, mention opening a terminal or shell on Linux/macOS, not just Windows PowerShell.
Provide explicit Bash/zsh examples or notes for Linux/macOS users alongside PowerShell instructions.
Avoid defaulting to Windows PowerShell as the primary example; instead, present cross-platform instructions or alternate between platforms.
Include screenshots or references that are not Windows-specific (e.g., avoid showing only Windows UI or PowerShell windows).
Clarify that Azure CLI and portal steps are cross-platform and can be performed on any OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas. The prerequisite section links only to Windows-specific Python setup documentation, omitting Linux or macOS equivalents. When describing how to activate a Python virtual environment, only the Windows command ('.\venv\Scripts\Activate') is shown, with no mention of the Linux/macOS alternative ('source venv/bin/activate'). In the section on setting environment variables, Windows Command Prompt and PowerShell instructions are provided before the Linux/macOS example, and the Linux/macOS export command is missing a closing quote, which could cause confusion.

Recommendations:

Provide links to Python installation/setup documentation for Linux and macOS alongside the Windows link in the prerequisites.
When showing how to activate a Python virtual environment, include both Windows ('.\venv\Scripts\Activate') and Linux/macOS ('source venv/bin/activate') commands, clearly labeled.
In the environment variable section, present all platform instructions together, or rotate the order (e.g., Linux/macOS first sometimes) to avoid always privileging Windows.
Carefully check Linux/macOS command syntax for accuracy (e.g., ensure quotes are closed in export commands).
Wherever possible, use cross-platform commands or note platform differences explicitly to ensure parity and clarity for all users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias by recommending Visual Studio as the primary development environment and providing Windows command prompt and PowerShell instructions before Linux/macOS equivalents. The instructions for setting environment variables are detailed for Windows tools (cmd, PowerShell) and only then for bash. The use of Visual Studio and references to its features (such as F5 to run, and screenshots of the Visual Studio UI) further reinforce the Windows-centric approach. There are no explicit Linux development environment recommendations or parity in tooling guidance.

Recommendations:

Provide equal prominence to cross-platform development tools such as Visual Studio Code and the Azure Functions Core Tools CLI, including setup and usage instructions for Linux/macOS.
Present environment variable instructions for Linux/macOS alongside Windows, not after, or use tabbed sections to avoid implicit prioritization.
Include screenshots and workflow steps for non-Windows environments (e.g., VS Code on Linux/macOS) where Visual Studio is referenced.
Mention and link to cross-platform alternatives for all required tools, not just Visual Studio.
Clarify that all steps are supported on Linux/macOS and provide troubleshooting or notes for any platform-specific differences.

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, tools, and workflows are described exclusively for Windows Server, Windows clients, DPM, and MABS, with no mention of Linux support or equivalent Linux tools. All command-line instructions use Windows executables, and registry edits and certificate management are described using Windows-specific utilities and paths. PowerShell is referenced for user identification, and all screenshots and UI flows are from Windows-based products. There is no guidance for Linux-based backup servers or cross-platform scenarios.

Recommendations:

Explicitly state if Linux is unsupported for DPM/MABS offline backup workflows; if supported, provide equivalent Linux instructions and tools.
If possible, develop and document cross-platform utilities (e.g., for disk preparation and certificate management) that work on Linux.
Include Linux command-line examples (bash, shell scripts) and file paths where applicable.
Mention Linux backup server options and clarify their compatibility with Azure Import/Export.
Provide parity in screenshots and UI walkthroughs for any supported Linux-based management consoles.
Avoid assuming the user is on Windows by default; structure prerequisites and workflows to address both Windows and Linux environments where possible.

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 presented before the Linux/macOS equivalent. The use of setx and PowerShell-specific syntax is highlighted, while the Linux/macOS export command is listed last. Additionally, the documentation references Visual Studio Code as a cross-platform editor but does not provide any Linux-specific tooling or terminal instructions elsewhere. All Azure CLI commands are cross-platform, but the explicit ordering and detail for Windows tools and patterns indicate a preference for Windows environments.

Recommendations:

Present environment variable setup instructions for Linux/macOS before or alongside Windows instructions, rather than after.
Use neutral, cross-platform shell commands (e.g., export) as the primary example, with OS-specific alternatives in expandable sections or side notes.
Include explicit instructions or screenshots for Linux/macOS terminal usage where relevant, not just Windows.
Mention and provide examples for popular Linux editors or terminal environments, not just Visual Studio Code.
Ensure all code snippets and setup steps are tested and clearly documented for both Windows and Linux/macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias by prioritizing Windows tools (Visual Studio, Command Prompt, PowerShell) in both prerequisites and step-by-step instructions. Environment variable setting instructions list Windows methods (cmd, PowerShell) before Linux/macOS (bash), and the overall workflow assumes Visual Studio as the development environment, which is primarily Windows-based. There are no Linux-specific development environment suggestions or parity in tooling guidance.

Recommendations:

Present environment variable setting instructions in a neutral or rotating order (e.g., Linux/macOS, then Windows, or all at once in a table).
Include alternative development environment instructions for Linux (e.g., using VS Code, JetBrains Rider, or MonoDevelop).
Clarify that .NET Framework is Windows-only, but suggest .NET (Core/5+) for cross-platform scenarios, and link to equivalent cross-platform guides.
Where possible, provide CLI-based project creation steps (e.g., using dotnet CLI) for users on non-Windows platforms.
Explicitly state any Windows-only requirements at the top, and offer links to cross-platform alternatives for similar functionality.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. Visual Studio (a Windows-centric IDE) is the only development environment mentioned, and all instructions for creating and running the Azure Functions app are centered around it. In environment variable setup, Windows command prompt and PowerShell instructions are listed before Linux/macOS equivalents. The use of Visual Studio tooling and references to Windows-specific patterns (like setx and F5 debugging) further reinforce this bias. There are no Linux-specific development environment suggestions or CLI-based workflows for cross-platform parity.

Recommendations:

Include instructions for creating and running Azure Functions apps using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
Present Linux/macOS and Windows instructions in parallel or in a neutral order, rather than always listing Windows first.
Provide examples for setting environment variables and running/debugging the function using Bash and cross-platform tools, not just Windows command prompt, PowerShell, and Visual Studio.
Mention and link to cross-platform development environments and workflows, such as using VS Code or JetBrains Rider.
Clarify that Visual Studio is not required and that the process can be completed on Linux/macOS with appropriate tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by exclusively referencing Windows tools (Visual Studio, Windows command prompt, PowerShell) for setup and environment configuration. There are no instructions or examples for Linux or macOS users, such as using Bash or cross-platform editors. The order and presence of Windows-specific instructions, without Linux equivalents, may hinder non-Windows developers.

Recommendations:

Add equivalent instructions for setting environment variables on Linux (e.g., export ConnectionString=...) and macOS.
Include examples using cross-platform editors or .NET CLI (e.g., dotnet new console) instead of only Visual Studio.
Present setup instructions for both Windows and Linux/macOS, or use tabbed sections to separate platform-specific steps.
Reference cross-platform terminal commands (e.g., Bash) alongside Windows Command Prompt and PowerShell.
Clarify that the .NET SDK and Azure App Configuration are cross-platform, and provide links or notes 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 deployment instructions and examples exclusively using PowerShell cmdlets, which are native to Windows environments. There are no equivalent examples using cross-platform tools such as Azure CLI or Bash scripts, and no explicit mention of Linux or macOS workflows. The only command-line example for enabling public network access uses Azure CLI, but the main deployment workflow is Windows/PowerShell-centric. The order of presentation and tooling assumes a Windows-first audience.

Recommendations:

Add equivalent deployment instructions using Azure CLI, which is cross-platform and widely used on Linux and macOS.
Provide Bash script examples for deploying ARM templates to Azure, alongside PowerShell.
Explicitly mention that the instructions apply to all platforms and provide guidance for Linux/macOS users.
Where PowerShell is used, offer a side-by-side or alternative example using Azure CLI.
Review the documentation for other places where Windows tools or patterns are assumed, and ensure Linux parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. In the prerequisites, Windows-specific Python setup is mentioned first, and the environment variable setup instructions prioritize Windows command prompt and PowerShell before macOS and Linux. Windows tools (setx, PowerShell) are described in more detail, and validation steps are more explicit for Windows. While Linux/macOS instructions are present, they appear after Windows and are less detailed.

Recommendations:

Present environment variable setup instructions in a more platform-neutral order, or group them together with clear tabs for each OS.
Give equal detail and validation steps for Linux/macOS as for Windows (e.g., show how to check environment variables on Unix systems).
In prerequisites, mention Python setup for all platforms equally, or link to cross-platform instructions before platform-specific ones.
Avoid describing Windows tools (like setx) in more detail than their Unix equivalents; ensure parity in command explanations.
Consider using a table or tabbed interface for OS-specific commands to avoid implicit prioritization.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by presenting Windows command-line instructions (setx, PowerShell) before Linux/macOS equivalents, using Windows-specific tools and syntax, and labeling the Linux/macOS example as an afterthought. The primary build/run instructions use generic commands, but environment variable setup is Windows-centric.

Recommendations:

Present Linux/macOS and Windows instructions side-by-side or in parallel sections, rather than listing Windows first and Linux/macOS last.
Use neutral or cross-platform shell syntax (e.g., POSIX-compliant export) where possible, or clearly separate platform-specific instructions.
Avoid using Windows-specific tools (like setx) as the default; instead, provide equivalent instructions for all platforms.
Explicitly mention that all major platforms are supported and tested.
Consider using tabs or collapsible sections for platform-specific instructions to improve clarity and parity.

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, and .NET Framework (not .NET Core or .NET 5/6+). All instructions, screenshots, and project templates are for Windows/Visual Studio. There are no references to Linux, cross-platform .NET, or alternative development environments. The use of Windows-specific project types (Console App (.NET Framework), ASP.NET Web Application (.NET Framework)), and instructions such as 'Run as administrator' and reliance on the Web Platform Installer, further reinforce the Windows-centric approach. No Linux or cross-platform alternatives are mentioned or demonstrated.

Recommendations:

Add instructions for setting up the development environment on Linux (and macOS), including using Visual Studio Code or JetBrains Rider, and .NET Core/.NET 6+.
Provide equivalent examples using .NET Core or .NET 6+ project templates (which are cross-platform), rather than .NET Framework-only templates.
Include command-line instructions for dotnet CLI (dotnet new, dotnet add package, dotnet run, etc.) alongside Visual Studio GUI steps.
Clarify which parts of the tutorial are Windows-only (e.g., WCF on .NET Framework), and suggest alternatives or workarounds for Linux users (such as using CoreWCF or gRPC).
Mention and demonstrate how to run and debug the sample applications on Linux, including any required configuration changes.
If certain features are not available on Linux, explicitly state this and provide links to relevant tracking issues or alternative approaches.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias primarily in the Java example, where the ffmpeg path uses a Windows-style executable (ffmpeg.exe) and the instructions reference a Windows directory structure. There is no explicit Linux/Unix example for Java, and the use of .exe implies Windows as the default. In contrast, the Python examples and the file share mounting section are Linux-focused, but there is no parity in providing both Windows and Linux examples for all languages. Additionally, PowerShell is mentioned as an upload option, but not demonstrated, and Windows tools are referenced before Linux equivalents in some places.

Recommendations:

For Java, provide both Windows and Linux examples for accessing and executing dependencies, including paths and executable formats (e.g., ffmpeg.exe vs. ffmpeg).
Avoid using Windows-specific file extensions (like .exe) in cross-platform documentation unless both alternatives are shown.
Explicitly mention and demonstrate how to set up and use dependencies on both Windows and Linux environments for all supported languages.
When referencing upload tools (Azure CLI, PowerShell, Portal), provide example commands for both Windows (PowerShell/CMD) and Linux (Bash) environments.
Ensure that instructions and code snippets do not assume a default platform; clarify when steps or paths differ between Windows and Linux.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. It references Azure Storage Explorer (a GUI tool with a primary focus on Windows) for uploading files and generating SAS tokens, and the link for generating SAS tokens is specifically tagged with '?tabs=windows'. There are no Linux-specific instructions or CLI alternatives for these steps, and no mention of Linux-native tools or workflows. The documentation assumes the use of Storage Explorer and does not provide parity for Linux users who may prefer CLI or cross-platform solutions.

Recommendations:

Provide explicit Azure CLI commands for uploading files to Azure Storage and generating SAS tokens, as these are cross-platform and suitable for Linux users.
Avoid linking to documentation with Windows-specific tabs or, if necessary, ensure Linux/macOS tabs are equally visible and referenced.
Mention and provide instructions for using Linux-native tools (e.g., azcopy, Azure CLI) for all storage operations.
Clarify that Azure Storage Explorer is available on Linux and macOS, or suggest alternatives if certain features are Windows-only.
Review all steps to ensure that Linux users can follow the workflow without needing to use Windows-specific tools or interfaces.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates some Windows bias by only mentioning or providing examples with Windows-centric tools (such as AzCopy and Azure Storage Explorer), and by omitting any explicit Linux command-line or cross-platform alternatives for storage migration. There are no CLI or scripting examples (e.g., Bash, Azure CLI, PowerShell) for Linux users, and the tools referenced are more familiar or accessible to Windows users. The documentation also refers to UI navigation steps in the Azure portal, which are platform-agnostic, but the lack of command-line parity is notable.

Recommendations:

Add explicit Linux and cross-platform examples for copying storage data, such as using Azure CLI commands (az storage blob/file copy) or AzCopy examples with Bash.
Mention that AzCopy is available cross-platform and provide sample commands for both Windows (cmd/PowerShell) and Linux (Bash).
Include references to open-source or cross-platform tools for storage management, not just Azure Storage Explorer.
Where possible, provide both portal (UI) and CLI (Azure CLI, Bicep, ARM templates) instructions side-by-side, so users on any OS can follow along.
Clarify that all steps can be performed from any OS, and highlight any OS-specific prerequisites or differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation generally provides cross-platform instructions, but there are several areas where Windows and Windows-specific tools or patterns are prioritized or presented first. PowerShell is given its own programming language pivot, and in several command sections, Windows command-line (Cmd) and PowerShell examples are provided before or alongside bash/Linux equivalents. Some sections, such as virtual environment activation for Python, include multiple Windows-specific tabs (bash, Cmd), and PowerShell is treated as a first-class language option. There is also a tendency to refer to 'terminal or command prompt' generically, which can be ambiguous for Linux users.

Recommendations:

When presenting command examples, alternate the order of Windows and Linux/macOS instructions, or present Linux/macOS first where appropriate.
Ensure that all command-line instructions are clearly labeled for each platform, and avoid ambiguous terms like 'command prompt' or 'terminal' without specifying the OS.
For PowerShell, clarify cross-platform support and, where possible, provide bash/zsh equivalents for scripting tasks.
In sections where Windows-specific tools or patterns are mentioned (such as PowerShell or Cmd), ensure that Linux/macOS alternatives are equally visible and easy to follow.
Consider adding explicit Linux/macOS troubleshooting notes or common issues, especially for steps that may differ (e.g., file paths, environment variable syntax).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page is generally cross-platform in intent, focusing on Visual Studio Code and Azure Functions, which are available on Windows, macOS, and Linux. However, there are subtle signs of Windows bias: troubleshooting advice specifically mentions Windows (e.g., WSL Bash), and there are no explicit Linux/macOS-specific instructions or examples. Windows-specific issues are called out, but Linux/macOS equivalents are not discussed, and no terminal or shell commands are shown for non-Windows users.

Recommendations:

Add troubleshooting steps relevant to Linux/macOS environments, such as common shell or permission issues.
Where Windows-specific advice is given (e.g., about WSL Bash), provide equivalent guidance for Linux/macOS users (e.g., default terminal shell issues, permissions, or path differences).
Include explicit notes or examples for Linux/macOS users, such as how to open the command palette or run commands in their environments.
Ensure that any references to tools or extensions clarify their cross-platform compatibility.
If possible, add screenshots or terminal snippets from both Windows and Linux/macOS to illustrate parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ windows_file_extensions

Summary:

The documentation generally provides cross-platform instructions, but there are subtle signs of Windows bias. Windows-specific file extensions (e.g., 'handler.exe') are mentioned before or alongside Linux equivalents. Windows environment variable setting commands are shown after Unix-style commands, but the Windows instructions are sometimes more explicit. The documentation refers to Windows-specific behaviors (such as changing 'defaultExecutablePath' to 'handler.exe' on Windows) and includes Windows command syntax (e.g., 'set GOOS=linux') in separate tabs, but does not provide PowerShell examples or prioritize Windows tools. Linux and macOS instructions are present and generally complete.

Recommendations:

When referring to executable names, mention the Linux version ('handler') first, or present both at the same time (e.g., 'handler (or handler.exe on Windows)').
Instruct users to set the 'defaultExecutablePath' to 'handler' by default, with a note for Windows users to use 'handler.exe' if needed.
Ensure that Linux/macOS instructions are always presented before Windows, or group them together to avoid the perception of Windows-first bias.
If possible, provide PowerShell equivalents for Windows commands, or clarify when to use Command Prompt vs. PowerShell.
Explicitly state that all examples are cross-platform unless otherwise noted, and highlight any platform-specific differences in a dedicated section.
Consider adding a table summarizing key platform differences (e.g., file extensions, environment variable syntax) for quick reference.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias. Windows is presented as the default or primary runtime for Azure Functions (e.g., in pom.xml examples and deployment defaults), and Linux support is mentioned only as an alternative. The configuration and deployment instructions focus on Windows first, with Linux-specific instructions relegated to notes or tips. There is also a lack of explicit Linux shell examples for some steps, and the use of Windows tools and patterns (such as PowerShell and Cmd) is given equal or more prominence than Linux/Bash, despite the cross-platform context.

Recommendations:

Present Linux and Windows options equally, e.g., by showing both 'runtime.os: windows' and 'runtime.os: linux' in configuration examples, or by defaulting to a cross-platform neutral value.
When describing deployment and configuration, avoid language that assumes Windows as the default; instead, clarify that both Windows and Linux are supported and highlight any differences up front.
Ensure that all command-line examples are provided for Bash (Linux/macOS), PowerShell, and Cmd, and that Bash is not treated as an afterthought.
Where platform-specific instructions are necessary (e.g., setting JAVA_HOME), provide explicit examples for both Windows and Linux.
Consider including a section or callout on developing and deploying on Linux, including any caveats or best practices.
Review and update the documentation to ensure Linux users are not required to infer steps from Windows-centric instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Bash (Linux/macOS) and Windows (PowerShell, Cmd) examples for Python virtual environment setup, and both Azure CLI and Azure PowerShell examples for Azure resource creation. However, there is a slight Windows bias: PowerShell and Cmd are given equal prominence to Bash, and PowerShell is presented as a first-class alternative to Azure CLI throughout, despite Azure CLI being cross-platform. Windows-specific tools and patterns (PowerShell, Cmd, 'py' launcher) are mentioned alongside or before Linux equivalents, and some instructions (such as using 'py' instead of 'python') are more relevant to Windows users.

Recommendations:

Prioritize Bash (Linux/macOS) examples before PowerShell and Cmd, as Bash is the default shell on most non-Windows systems and is also available on Windows via WSL.
Clearly indicate which commands are for which platforms, and consider grouping Windows-specific instructions after cross-platform or Linux-first instructions.
Instruct users to use 'python' instead of 'py' for virtual environment creation, as 'py' is a Windows-specific launcher.
Emphasize Azure CLI as the primary, cross-platform tool for resource creation, and present PowerShell as an alternative for Windows users.
Add explicit notes or callouts for Linux/macOS users where necessary, especially for common issues (e.g., missing 'venv' package).
Consider providing a single, cross-platform command block for steps that are identical across platforms, reducing fragmentation and potential confusion.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation presents Azure PowerShell and Portal examples alongside Azure CLI, but does not provide any Linux- or bash-specific examples, nor does it mention Linux-native tools or workflows. PowerShell is given a dedicated section, and the CLI examples are generic but do not clarify Linux compatibility or provide bash-specific guidance. The Portal and PowerShell sections may imply a Windows-centric workflow, and the lack of explicit Linux shell examples or troubleshooting for Linux users (beyond a single note about hyphens in function names) suggests a Windows-first bias.

Recommendations:

Explicitly state that Azure CLI commands work cross-platform and, where relevant, provide bash/zsh shell examples (e.g., with export statements or Linux environment variable syntax).
Add a section or tab for bash/Linux shell users, especially for setting environment variables or editing local.settings.json using Linux tools.
Clarify that PowerShell examples are primarily for Windows users, and offer equivalent bash commands where possible.
Include troubleshooting or notes specific to Linux environments, such as file permissions or common shell differences.
Where PowerShell is mentioned, ensure parity by offering bash or sh alternatives, or at least referencing their use.

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-specific tools and configuration steps (such as Visual Studio, PowerShell, and Windows-specific Azure CLI commands) are mentioned before or more prominently than their Linux equivalents. Some deployment and configuration examples are provided only for Windows or with Windows as the primary example, with Linux alternatives appearing later or not at all. There are also references to Windows-specific concepts (e.g., .NET Framework, win-x86/win-x64) without always providing equivalent Linux guidance or parity in examples.

Recommendations:

Ensure all CLI and deployment examples are provided for both Windows and Linux, with Linux examples given equal prominence and order.
Where Visual Studio or PowerShell are mentioned, also mention and provide examples for cross-platform alternatives (e.g., Visual Studio Code, Bash, Azure CLI).
In tables and lists of options, avoid listing Windows tools or workflows first by default; alternate or group by platform.
When referencing runtime identifiers or build targets (e.g., win-x64), always include the Linux equivalents (e.g., linux-x64) in parallel.
For debugging and local development, provide explicit Linux instructions and troubleshooting steps, not just Windows/Visual Studio.
Add explicit notes or callouts where a feature or tool is Windows-only, and suggest Linux-compatible alternatives where possible.
Review all code snippets and ensure any shell commands (e.g., Azure CLI) are shown with both Windows (cmd/PowerShell) and Linux (bash) syntax where differences exist.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits subtle Windows bias. It references Windows-specific tools (e.g., func.exe), mentions PowerShell as a supported runtime with special features, and refers to Windows patterns (such as .pfx certificates and trusted certificate creation) without clarifying Linux/Mac equivalents. There are no explicit Linux or cross-platform shell examples, and some features (like log streaming) are noted as unsupported on Linux in certain plans, but without offering Linux alternatives or parity guidance.

Recommendations:

Provide explicit Linux/macOS shell examples (e.g., bash/zsh) alongside or instead of Windows/PowerShell commands.
Clarify cross-platform behavior for features like certificate creation, trusted certificates, and file paths (e.g., .pfx usage on Linux).
Avoid referencing Windows-specific tools (like func.exe) in the title/description; use cross-platform terms (e.g., Azure Functions Core Tools CLI).
For features not supported on Linux (e.g., log streaming in Consumption plan), offer alternative Linux-compatible workflows or clarify expected behavior.
Ensure all examples and instructions are validated on Linux/macOS and highlight any OS-specific differences or requirements.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Bash and Azure PowerShell examples for all CLI steps, but the PowerShell examples are always presented alongside Bash, and sometimes before or equally with Bash. However, there are no explicit Windows-only tools or patterns, and the CLI commands are cross-platform. The language SDK examples (C#, JavaScript, Python, Java) are all shown with Bash commands, and the prerequisites note that Bash is required for Python, JavaScript, and Java, which may disadvantage Windows users who do not have Bash. There is a slight bias in that PowerShell is given parity with Bash throughout, but there are no explicit Linux-only or Windows-only steps. There are no examples for native Windows CMD usage, nor explicit Linux-only tools.

Recommendations:

Clarify in the prerequisites that Bash can be used on Windows via WSL, Git Bash, or similar, and provide links or instructions for Windows users.
Consider providing Windows CMD examples or clarify that PowerShell is the recommended shell for Windows users.
In each step, explicitly state which shell is recommended for which OS, to avoid confusion.
If possible, provide parity in shell examples: for each Bash example, ensure the PowerShell equivalent is equally visible, and vice versa.
Add a note for Windows users who may not have Bash, explaining how to install or use Bash-compatible environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides deployment instructions using both Azure CLI and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is primarily a Windows-centric tool, and its inclusion as a first-class alternative (with full code samples for every language) indicates a Windows bias. There are no Linux-specific shell examples (e.g., Bash), and the PowerShell examples are given equal prominence to the CLI, which may confuse or disadvantage Linux users. Additionally, the documentation refers to saving files to your 'local computer' without clarifying cross-platform paths or shell conventions.

Recommendations:

Add explicit Bash shell examples for Linux/macOS users alongside Azure CLI commands, including file path conventions (e.g., ./main.bicep).
Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and recommend it as the primary cross-platform tool.
De-emphasize Azure PowerShell as a primary deployment method, or clearly label it as Windows-centric, with a note for Linux users about PowerShell Core availability.
Include notes or examples for common Linux/macOS shell environments where relevant (e.g., using export for environment variables, file permissions, etc.).
Ensure that any references to file paths or shell commands use cross-platform syntax or provide both Windows and Linux/macOS variants.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows a Windows bias in several ways: it references Windows-specific platforms first (e.g., 'Windows-Java 17'), omits explicit Linux/macOS instructions or screenshots, and does not provide any Linux-specific examples or terminal commands. The workflow assumes the user is on Windows or using Windows defaults, with no mention of Linux-specific steps or troubleshooting.

Recommendations:

Provide explicit instructions and screenshots for Linux/macOS users, especially for steps that may differ (e.g., setting JAVA_HOME, running Maven, or using Azure Functions Core Tools).
When listing platform options (such as during function app creation), mention Linux options alongside or before Windows, and clarify any differences (e.g., Java 21 support on Linux only).
Include terminal/command-line examples for Linux/macOS (e.g., using bash instead of only referencing GUI steps or Windows paths).
Add troubleshooting notes for common Linux/macOS issues (such as file permissions, environment variable setup, or dependency installation).
Ensure parity in all screenshots and instructions, so Linux/macOS users are not left to infer or adapt Windows-centric guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation exhibits a strong Windows bias. All instructions and examples assume the use of Windows-specific tools (Visual Studio, .NET Framework, WCF, App.config), and there is no mention of Linux or cross-platform alternatives. Steps such as 'Run as administrator', adding references via Visual Studio UI, and using Windows file paths are Windows-centric. No guidance is provided for Linux users, such as using .NET Core/.NET 6+, command-line tools, or cross-platform editors. There are no Linux or non-Windows development/testing instructions.

Recommendations:

Add a section or parallel instructions for Linux users, including how to set up the environment using .NET Core/.NET 6+ (which is cross-platform).
Provide command-line instructions (e.g., using dotnet CLI) for creating, building, and running the project, instead of relying solely on Visual Studio UI.
Mention and demonstrate how to use cross-platform editors like VS Code, and how to add NuGet packages and references via CLI.
Clarify which features (such as WCF) are Windows-only, and suggest alternatives or workarounds for Linux (e.g., using ASP.NET Core with Azure Relay, if possible).
Include Linux-specific testing and running instructions, such as terminal commands and file paths.
Avoid language like 'Run as administrator' or 'right-click', or provide equivalent instructions for Linux/macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation presents deployment options in the order: Portal, PowerShell, and then CLI. PowerShell is given equal prominence to CLI, and the CLI section references Git Bash (included in Git for Windows) as the example Bash shell, rather than a native Linux shell. There are no explicit Linux-specific instructions or examples, and the CLI instructions are written generically, but the only shell mentioned is Git Bash for Windows. This subtly prioritizes Windows tools and environments.

Recommendations:

Explicitly mention native Linux/macOS shells (e.g., bash, zsh) as supported environments for Azure CLI, not just Git Bash for Windows.
Add a note or section confirming that all CLI commands work natively on Linux/macOS terminals, and provide any Linux/macOS-specific prerequisites if needed.
When listing deployment options, consider rotating or randomizing the order, or explicitly stating that all platforms are supported equally.
Provide links or references to installing Azure CLI on Linux/macOS, not just a generic install link.
If referencing PowerShell, clarify that PowerShell Core is cross-platform, or provide Bash equivalents for any PowerShell-specific scripts where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows users by focusing exclusively on Visual Studio (the full IDE), which is only fully supported on Windows. All instructions, screenshots, and workflows assume the use of Visual Studio, with no equivalent steps or examples for Linux users. There are no CLI or cross-platform alternatives provided within the main content, and Linux users are only briefly redirected to a separate Visual Studio Code article. The use of Windows-specific tools and UI patterns (e.g., Visual Studio menus, File Explorer) further reinforces the Windows bias.

Recommendations:

Provide parallel instructions for Linux users using Visual Studio Code and the Azure Functions Core Tools CLI within this article, or clearly indicate cross-platform alternatives at each step.
Include CLI-based steps for creating, running, and deploying Azure Functions projects, which work on both Windows and Linux.
Add screenshots and examples from Linux environments (e.g., using terminal, file managers) where appropriate.
Clarify in the prerequisites and introduction that Visual Studio is only available on Windows, and offer a direct, prominent link to the cross-platform (VS Code/CLI) guide.
Where Azurite or other tools are mentioned, note their installation and usage on Linux.
Consider restructuring the article or providing tabs/sections for Windows (Visual Studio) and Linux/macOS (VS Code/CLI) users to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is strongly Windows-centric, explicitly stating support for C# class library functions on Windows only. There are no examples or instructions for Linux-based Azure Functions, nor for other operating systems. All code and deployment steps assume a Windows environment, and there is no mention of Linux-specific considerations or parity.

Recommendations:

Add explicit instructions and examples for deploying and running Azure Functions with identity-based connections on Linux-based hosting plans.
Clarify which steps are cross-platform and which are Windows-specific; provide alternative steps or notes for Linux users.
Include examples for other supported languages and platforms, or at least acknowledge their support and provide links to relevant documentation.
If certain features are not yet available on Linux, clearly state this and provide a roadmap or workaround if possible.
Ensure that CLI commands and file paths are presented in a cross-platform manner (e.g., use forward slashes or note both Windows and Linux path formats).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows-based deployment options (such as source control, Local Git, and FTPS) are called out as 'Windows-only' in the technology availability table, while Linux equivalents are either less emphasized or described as limited. Windows-specific tools and patterns (e.g., Visual Studio, Kudu/SCM site) are mentioned first or in more detail, and some deployment methods (like source control and FTPS) are not available or are restricted on Linux. Linux-specific instructions are present but often secondary, and there are few Linux command-line or native tool examples.

Recommendations:

Provide Linux-first or Linux-parity examples for each deployment method, especially where Windows is called out as the default or primary platform.
Where deployment technologies are Windows-only, offer clear Linux alternatives or workarounds, and link to relevant Linux documentation.
Include more explicit Linux command-line examples (e.g., Bash, native Linux tools) alongside or before Windows/PowerShell/Visual Studio instructions.
Clarify any limitations or differences for Linux users up front, and avoid presenting Windows tools as the default unless truly universal.
Expand documentation on remote build and deployment for Linux, including troubleshooting and best practices.
Where possible, avoid using 'Windows-only' as a default and instead structure tables and sections to give Linux and Windows equal prominence.

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 workflows assume the use of Visual Studio 2022, which is only fully supported on Windows. There are no examples or guidance for developing Azure Functions using Visual Studio Code, .NET CLI, or other cross-platform tools. PowerShell is used in package installation examples, and Windows-specific UI elements and dialogs are referenced throughout. There is no mention of Linux or macOS development environments, nor are alternative workflows (such as using VS Code or CLI tools) provided.

Recommendations:

Add explicit guidance and examples for developing Azure Functions on Linux and macOS using Visual Studio Code and the .NET CLI.
Include CLI-based instructions for project creation, dependency management, and publishing, alongside Visual Studio UI steps.
Provide screenshots and workflow descriptions for cross-platform tools (e.g., VS Code, terminal) in addition to Visual Studio.
Replace or supplement PowerShell commands with equivalent Bash commands for Linux/macOS users.
Clearly indicate which steps or features are Windows/Visual Studio-specific, and offer alternatives where possible.
Reference the Azure Functions Core Tools and Azure CLI for tasks like local development, configuration, and deployment, with examples for all supported platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several areas. File and executable naming conventions (e.g., 'handler.exe') are Windows-centric and appear before or instead of Linux equivalents. Example directory structures and configuration files consistently use Windows-style executable names, and there are no explicit Linux or macOS command-line or file examples. The documentation does not provide parity in showing how to configure or run custom handlers on Linux (e.g., using './handler' or without the '.exe' extension), nor does it mention Linux-specific tools or patterns.

Recommendations:

In all file and executable examples, show both Windows and Linux/macOS equivalents (e.g., 'handler.exe' for Windows, './handler' for Linux/macOS).
In directory structure diagrams, include both 'handler.exe' and 'handler' to illustrate cross-platform deployment.
In configuration file examples, clarify that 'defaultExecutablePath' should match the platform (e.g., 'handler.exe' on Windows, 'handler' on Linux/macOS).
Add explicit Linux/macOS command-line examples where relevant (e.g., how to build and run the handler on Linux).
Mention cross-platform considerations (such as file permissions on Linux, executable extensions, and case sensitivity) in relevant sections.
Where tools are referenced (such as Azure Functions Core Tools), clarify that they are available on all platforms and provide installation/use instructions for Linux/macOS as well as Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows environments. All paths, examples, and terminology (such as drive letters, backslashes in paths, and references to Windows-specific applications like Exchange and SharePoint) are Windows-centric. There are no examples or guidance for Linux systems, and no mention of Linux shell scripting or file system conventions.

Recommendations:

Add explicit guidance for configuring pre- and post-backup scripts on Linux systems, including example paths (e.g., /opt/scripts/myscript.sh) and file permissions.
Provide Linux shell script examples alongside Windows examples, and clarify any differences in script execution (e.g., bash vs. PowerShell/cmd).
Mention Linux data source naming conventions and provide examples relevant to Linux workloads (e.g., mount points, application data paths).
Clarify whether MABS supports Linux agents and, if so, document any differences in ScriptingConfig.xml location or usage.
Avoid assuming drive letters or Windows-only applications in examples; use more generic or cross-platform examples where possible.

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-specific tools and paths are mentioned before or instead of cross-platform or Linux equivalents (e.g., use of Windows MSI installer, %USERPROFILE% paths, win-x86 in ReadyToRun examples). Command-line installation and usage examples are provided for Windows (cmd, PowerShell) but not for Linux (bash, zsh). There is no mention of Linux-specific instructions or file paths, and the ReadyToRun publishing example only shows a Windows runtime identifier. The documentation does not provide parity for Linux or macOS users in terms of examples or tool usage.

Recommendations:

Add Linux/macOS equivalents for all Windows-specific instructions, such as file paths (e.g., use $HOME instead of %USERPROFILE%) and installation locations.
Include bash/zsh shell examples alongside cmd and PowerShell for package installation and CLI usage.
When discussing ReadyToRun or publishing, provide examples for Linux (e.g., linux-x64) and macOS runtime identifiers, not just win-x86.
When referencing installation of Azure Functions Core Tools, include Linux/macOS installation methods (e.g., apt, brew, manual download) and clarify any differences in behavior.
Ensure that all command-line and configuration examples are cross-platform or provide platform-specific tabs.
Review and update any references to Windows-only dependencies or tools to clarify cross-platform compatibility or alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a moderate Windows bias. Windows-based build agents (vmImage: 'windows-latest') are used by default or appear first in C# and PowerShell examples, while Linux (ubuntu-latest) is used for JavaScript and Python. PowerShell is included as a first-class language, but there is no mention of Bash or Linux shell scripting for administrative tasks. Windows is the default appType for deployment, and Windows-specific notes and terminology (such as 'windows-latest', 'functionApp' for Windows, and PowerShell language support) are presented before or more prominently than Linux equivalents. However, Linux deployment and build examples are present and reasonably complete, especially for Python and JavaScript.

Recommendations:

For C# examples, provide both 'windows-latest' and 'ubuntu-latest' YAML build pipeline samples, or explain when to use each.
For PowerShell, clarify that it is Windows-only and consider providing Bash equivalents for administrative or scripting tasks.
In deployment sections, present Linux and Windows options side-by-side or in parallel tabs, rather than defaulting to Windows.
Explicitly mention Linux support for C# and PowerShell if available, or clarify platform limitations.
Where Windows is the default (e.g., appType), explain how to select Linux and highlight Linux as an equal option.
Add a summary table or section comparing Windows and Linux support for each language and deployment scenario.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing PowerShell and Azure portal workflows before mentioning CLI alternatives, and by omitting explicit Linux/macOS examples for key steps (such as enabling managed identity or connecting to SQL). The SQL connection example uses sqlcmd, which is available cross-platform, but there is no mention of Linux-specific considerations or alternative tools. The documentation also refers to the Azure portal and PowerShell as primary methods, with Azure CLI as an alternative, which may not be as familiar or accessible to Linux users.

Recommendations:

Provide explicit Linux/macOS command-line examples for all steps, including enabling managed identity and connecting to SQL.
When listing methods (Azure portal, PowerShell, Azure CLI), avoid listing Windows-centric tools (PowerShell) before cross-platform options (CLI), or present all options equally.
Include notes or tips for Linux/macOS users, such as installation instructions for sqlcmd or alternative tools (e.g., mssql-cli).
Ensure that all screenshots and UI instructions are supplemented with CLI equivalents for users who do not use the Azure portal.
Review language to avoid implying that PowerShell or the Azure portal are the default or preferred options.

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 and PowerShell tools are consistently presented alongside or before Linux alternatives, and some features or instructions are only available or described for Windows environments. PowerShell examples are provided throughout, but Linux-specific shell or scripting examples are absent. Several advanced tools (like Kudu, App Service Editor, and in-portal console) are available only or primarily on Windows. Plan migration instructions are explicitly limited to Windows, with Linux migration described as unsupported or restricted. In some feature matrices, Linux support is marked as unavailable or not discussed, and Linux-specific workflows are not given equal coverage.

Recommendations:

Provide explicit Linux/bash shell examples alongside PowerShell for all CLI operations, especially for scripting and automation.
Clarify Linux support and limitations in all feature tables and sections, and offer workarounds or alternatives where features are Windows-only.
Where plan migration is not supported on Linux, explain the reasons and suggest alternative approaches or migration paths for Linux users.
Include Linux-specific instructions for using advanced tools (such as SSH-based console access) and clarify differences in tool availability.
Ensure that all screenshots and UI walkthroughs mention or show Linux options where relevant.
Add parity in documentation for local development and deployment workflows on Linux, including references to Linux-compatible tools and editors.
Where PowerShell is featured, provide equivalent bash or shell script snippets for Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation generally avoids overt Windows bias in code examples or commands, but there are subtle biases. There is a lack of Linux-specific examples or parity in feature descriptions. Some features (e.g., Performance Counters, built-in log streaming) are noted as unsupported or limited on Linux, but Linux alternatives or workarounds are not provided. The documentation references Windows-centric tools (App Service log streaming) without giving equal prominence to Linux workflows. In sections where feature limitations on Linux are mentioned, Linux is framed as the exception rather than being treated equally.

Recommendations:

Provide Linux-specific examples or explicit instructions for common monitoring and logging tasks, especially where features differ from Windows.
When describing features that are unavailable or limited on Linux (e.g., Performance Counters, built-in log streaming), offer alternative Linux-compatible solutions or workarounds.
Where possible, avoid framing Linux as a secondary or unsupported platform; instead, present both Windows and Linux capabilities side by side.
Include references to Linux-native tools or commands (such as using Azure CLI, Kudu, or SSH for log access on Linux) where appropriate.
Ensure that all feature tables and instructions clarify platform support and guide users to Linux-compatible workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Linux/macOS (bash) and Windows (PowerShell, Cmd) instructions for most steps, but Windows-specific tools and patterns are often mentioned first or in more detail. There are several places where Windows command patterns (such as 'py' launcher and registry edits) are emphasized, and troubleshooting advice is Windows-centric. The PowerShell and Cmd tabs are always present, sometimes before bash, and Windows-specific issues (like long path errors and registry changes) are discussed in depth, while Linux troubleshooting is minimal.

Recommendations:

Ensure that bash (Linux/macOS) instructions are presented first or at least equally with Windows instructions.
Provide Linux/macOS-specific troubleshooting advice where Windows-specific advice is given (e.g., discuss common Linux pip/venv issues, permissions, or path problems).
When mentioning tools like the 'py' launcher or registry edits, offer equivalent Linux/macOS context or explicitly state that these are Windows-only concerns.
Balance the depth of troubleshooting guidance for both platforms, including common Linux/macOS errors and their resolutions.
Where possible, use cross-platform commands or highlight differences clearly, rather than defaulting to Windows-first patterns.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation generally covers networking options for Azure Functions in a cross-platform manner, but there are notable areas of Windows bias. The 'Hybrid Connections' feature is only available for Windows, with Linux explicitly not supported. In the 'Virtual network triggers' section, CLI, PowerShell, and portal instructions are provided, but there is a heavier emphasis on PowerShell (a Windows-centric tool) and no Linux-specific scripting examples. Additionally, subnet sizing guidance is given for both Windows and Linux, but Windows is mentioned first and in more detail. There are no Linux shell (bash) command examples for automation or configuration, and Windows tools like PowerShell are referenced without Linux alternatives.

Recommendations:

Where PowerShell examples are given, provide equivalent bash/Azure CLI examples for Linux users.
In automation sections, ensure that Linux-friendly tools (e.g., bash scripts, Azure CLI) are presented alongside or before Windows tools.
In feature descriptions (such as Hybrid Connections), clearly state Linux limitations early and suggest alternative solutions for Linux users if available.
When giving subnet sizing or configuration guidance, present Linux and Windows information in parallel, not with Windows first.
Add explicit Linux testing and troubleshooting guidance, especially for scenarios where portal or Windows tools are referenced.
Review all screenshots and UI instructions to ensure they are not Windows-specific or clarify if the experience is the same on Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page for Azure Functions Premium plan demonstrates several forms of Windows bias. PowerShell is presented as a primary automation tool alongside Azure CLI, with detailed PowerShell examples provided throughout. Migration guidance is only available for Windows, with Linux explicitly unsupported. There are no Linux-specific command-line or scripting examples (e.g., Bash, shell scripts), and Windows terminology and tools (such as PowerShell and Windows migration) are mentioned before or instead of Linux equivalents. Some features are only available or described for Windows, with Linux limitations noted but not explained or worked around.

Recommendations:

Provide Linux-specific migration guidance or clearly state feature parity plans for Linux.
Include Bash/shell script examples alongside PowerShell for all CLI operations.
Ensure that Linux and Windows are given equal prominence in feature descriptions, tables, and examples.
Where features are Windows-only, offer alternative approaches or workarounds for Linux users, or link to relevant Linux documentation.
Explicitly mention any differences in portal experience for Linux users, if applicable.
Review and update region/scale-out tables and feature lists to clarify Linux support and limitations, and provide context or alternatives where Linux is not supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation generally provides both Bash and Windows CMD examples for command-line operations, but consistently lists Windows (CMD) examples after Bash. There is no exclusive use of Windows tools or PowerShell, but the documentation does not provide PowerShell-specific examples, which is a common Windows scripting environment. The documentation does not provide Linux-specific troubleshooting steps, nor does it highlight Linux-specific tools or patterns. In some tables (e.g., Java version support), Windows is listed before Linux, which may subtly reinforce a Windows-first perspective. However, overall, the documentation is relatively balanced, but could improve Linux parity by including more Linux-specific notes and examples.

Recommendations:

Add PowerShell examples alongside Bash and CMD, or clarify when PowerShell is supported.
Where relevant, provide Linux-specific troubleshooting steps or notes (e.g., file permissions, environment variable differences).
In tables and lists, alternate the order of Windows and Linux, or present them alphabetically to avoid implicit prioritization.
Include explicit mentions of Linux tools or patterns (e.g., using systemd for local development, or Linux-specific environment configuration).
Highlight any differences in behavior or setup between Windows and Linux environments, especially for local development and deployment.
Ensure all command-line examples are tested and work as expected on both Windows and Linux shells.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias by exclusively using Visual Studio (a Windows-centric IDE) for all steps, referencing Windows-specific UI and workflows, and omitting any Linux or cross-platform alternatives. There are no examples or instructions for using Linux or command-line tools (such as Azure CLI, VS Code, or cross-platform editors), and all tooling and screenshots are from the Windows ecosystem. The workflow assumes the user is on Windows and does not mention Linux or macOS at any point.

Recommendations:

Add parallel instructions for Linux and macOS users, including how to use VS Code or the Azure CLI to create and manage Azure Functions projects.
Provide examples for setting app settings and connection strings using Azure CLI or the Azure portal, not just through Visual Studio.
Include instructions for installing and managing NuGet packages using the dotnet CLI, which is cross-platform.
Mention and show how to run and debug Azure Functions locally using Azure Functions Core Tools on Linux/macOS.
Ensure screenshots and UI references are not exclusively Visual Studio/Windows-centric, or provide alternatives.
Explicitly state that the workflow is possible on non-Windows platforms and link to relevant cross-platform documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides command-line examples for Azure CLI and Azure PowerShell, but does not offer Linux-specific shell examples (e.g., Bash scripts or curl commands) where relevant. In sections where multiple tooling options are shown, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some cases, appears before or alongside CLI without clarifying cross-platform applicability. There are no explicit Linux-only or macOS-specific instructions, and no mention of platform differences in using tools like nslookup or Azure CLI. This may create a perception of Windows bias and insufficient Linux parity.

Recommendations:

Add explicit Bash/shell examples where appropriate, especially for common tasks (e.g., using curl/jq to parse JSON, or Bash scripting for automation).
Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows, while Azure PowerShell is primarily a Windows tool but also available cross-platform.
When listing multiple tooling options, present Azure CLI (the most cross-platform tool) before PowerShell, or clearly indicate which tools are recommended for which platforms.
Include notes or callouts for any platform-specific differences in command usage or output.
Where possible, provide examples of using native Linux tools (e.g., dig as an alternative to nslookup) and mention their installation if not present by default.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation generally aims for cross-platform parity, but there are subtle signs of Windows bias. Windows command-line tools (cmd, PowerShell) are mentioned alongside or before Linux equivalents, and some instructions or examples reference Windows-specific tools or patterns. The requirement for Azure PowerShell or Azure CLI is presented without noting Linux-specific package managers or shell environments. The cURL examples do include both Bash and Windows cmd, but Windows is often mentioned first or with extra detail. Some references (such as func.exe) use Windows-style naming. There is also a dedicated PowerShell programming language pivot, which may reinforce a Windows-centric view.

Recommendations:

Ensure all command-line examples are presented in both Bash (Linux/macOS) and Windows cmd/PowerShell, and alternate the order in which they are shown.
Avoid using Windows-specific executable names (like func.exe) in generic instructions; use 'func' unless specifically discussing Windows.
When referencing required tools (Azure CLI, PowerShell), clarify that both are cross-platform and provide Linux/macOS installation links or notes.
Explicitly mention Linux/macOS where appropriate, especially when discussing terminals, shells, or environment setup.
Consider adding a Linux/macOS-specific troubleshooting or tips section, similar to the PowerShell pivot.
Review for subtle language that assumes a Windows environment (e.g., 'command prompt'), and use more neutral terms like 'terminal'.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a subtle Windows bias by referencing Windows-centric tools (such as the .NET secret manager and environment variable conventions) without providing equivalent Linux or cross-platform examples. The only command-line examples for setting secrets use 'dotnet user-secrets', which is more commonly associated with Windows development environments, and environment variable naming conventions are described in a way that is most familiar to Windows users. There are no explicit Linux shell or configuration examples, and no mention of Linux-specific patterns or tools (such as exporting environment variables in Bash, or using Linux-based secret management solutions).

Recommendations:

Add Linux/Bash examples for setting environment variables, e.g., 'export Azure__SignalR__ConnectionString=...'.
Include notes or examples for using the .NET secret manager on Linux, or mention alternative secret storage mechanisms common in Linux environments.
When describing environment variable configuration, clarify that the double underscore convention works across platforms, and provide both Windows (set) and Linux (export) command examples.
Mention and provide examples for using Azure CLI and Key Vault in Linux environments, if applicable.
Ensure that all code/configuration examples are platform-neutral or provide both Windows and Linux variants where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily by providing only Azure PowerShell scripts for identifying function apps, with no equivalent Bash, Azure CLI, or Linux-native instructions. References to Visual Studio (a Windows-centric tool) are present, and there is no mention of cross-platform alternatives for publishing or managing Azure Functions. The documentation assumes the use of Windows tooling and does not address Linux/macOS users or provide parity in examples or instructions.

Recommendations:

Provide equivalent Azure CLI (az) commands and Bash scripts for identifying and managing function apps, alongside PowerShell examples.
Explicitly mention and provide instructions for using cross-platform tools such as Visual Studio Code and Azure CLI for publishing and managing Azure Functions.
Where Visual Studio is referenced, add guidance for Linux/macOS users, such as using VS Code or command-line deployment methods.
Audit the documentation for other Windows-specific assumptions (e.g., file paths, environment variables) and ensure cross-platform compatibility is addressed.
Add a section or callouts clarifying that all steps can be performed on Linux/macOS, and link to relevant cross-platform tooling documentation.

Create pull request

Bias Types:

⚠️ linux_first

⚠️ missing_windows_example

⚠️ linux_tools

Summary:

The documentation page demonstrates a bias toward Linux environments. All example commands are shown using bash syntax, and log file locations and commands (such as grep and /var/log/messages) are specific to Linux. While there are brief mentions of Windows (e.g., NTFS volumes and 'noflush' label), there are no example commands or log file paths for Windows users. Linux tools and patterns (e.g., sync, grep, /var/log/messages) are used exclusively in examples, and Windows equivalents are not provided.

Recommendations:

Add example commands for Windows environments, using PowerShell or Command Prompt syntax where appropriate.
Document the locations of log and result files on Windows systems, including typical paths and how to access them.
Provide Windows-specific instructions for tasks such as flushing I/O buffers, viewing logs, and checking backup results.
Where Linux tools (e.g., grep, cat, /var/log/messages) are referenced, include equivalent Windows commands (e.g., Get-Content, Select-String, Event Viewer) and file locations.
Ensure that both Linux and Windows workflows are described with parity in all sections, including configuration, execution, and troubleshooting.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides examples for Bash (Linux/macOS), PowerShell, and Cmd, but there are several indications of Windows bias. Windows-specific tools and patterns (like 'py' launcher, registry edits, and long path issues) are mentioned prominently, sometimes before or in more detail than their Linux equivalents. Troubleshooting tips focus on Windows-specific errors, and some commands (e.g., activating virtual environments) use Windows-first or Windows-specific syntax. Linux troubleshooting is minimal or absent.

Recommendations:

Ensure that Linux/macOS commands and troubleshooting steps are given equal prominence and detail as Windows examples.
When mentioning issues like long path errors, also include common Linux/macOS installation issues (e.g., permissions, missing packages, or path length limits on certain filesystems).
In prerequisite checks, mention both Linux/macOS and Windows commands together, or list Linux/macOS first in some sections to balance the order.
Provide Linux/macOS-specific troubleshooting tips, such as dealing with missing dependencies, permissions, or virtual environment activation issues.
Where Windows registry edits are mentioned, clarify that these are Windows-only and suggest analogous checks or solutions for Linux/macOS if applicable.
Review all code tabs to ensure that Bash (Linux/macOS) is always present and accurate, and that it is not treated as secondary to Windows shells.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily by providing only a PowerShell script to identify function apps to migrate, with no equivalent Bash, Azure CLI, or Linux-native example. The initial migration workflow references Azure PowerShell and Visual Studio (a Windows-centric tool) without mentioning cross-platform alternatives. There are no explicit Linux or Bash shell instructions for common tasks, and the only scripting example is PowerShell, which is less common on Linux. This can make the guide less accessible to users on Linux or macOS.

Recommendations:

Provide equivalent Bash and/or Azure CLI scripts alongside the PowerShell example for identifying function apps to migrate.
When referencing tools like Visual Studio, also mention cross-platform alternatives such as Visual Studio Code with Azure Functions extensions, or the Azure CLI for deployment.
Ensure that all scripting and command-line instructions are available in both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) formats.
Explicitly state that the migration process can be performed on Linux/macOS, and link to relevant cross-platform tooling documentation.
Review the documentation for other subtle Windows-first patterns (such as terminology or tool recommendations) and ensure Linux parity in all sections.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The tutorial demonstrates a mild Windows bias, particularly in the data preparation steps. It exclusively references Microsoft Excel and Notepad for converting and viewing data files, and describes UI actions (e.g., 'File > Save As...') in a way that is specific to Windows applications. There are no instructions or examples for performing these steps on Linux or macOS, nor are alternative tools mentioned. The recommended IDE is Visual Studio Code, which is cross-platform, but the workflow and screenshots assume a Windows environment.

Recommendations:

Provide alternative instructions for Linux and macOS users for converting Excel files to tab-delimited text, such as using LibreOffice Calc, csvkit, or command-line tools like 'ssconvert' or 'in2csv'.
Mention and show examples of opening and editing text files using cross-platform editors (e.g., VS Code, nano, vim, gedit) instead of only Notepad.
Avoid UI instructions that are specific to Windows applications (like Excel's 'Save As' dialog) or supplement them with equivalent steps for LibreOffice or command-line tools.
Include screenshots or notes that reflect cross-platform usage, or explicitly state that the steps apply regardless of OS, with links to relevant Linux/macOS resources.
Clarify that Visual Studio Code is available on all major platforms and that any suitable editor or IDE can be used.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased towards Windows and Visual Studio on Windows. All instructions and examples assume the use of Visual Studio 2022, a Windows-only IDE, and reference Windows-specific publishing targets (e.g., Azure Function App (Windows)). There are no instructions or examples for Linux users, such as using VS Code, the Azure CLI, or cross-platform .NET tools. The use of the Package Manager Console (PowerShell-based) and NuGet commands is also presented in a way that assumes a Windows environment. No Linux or cross-platform alternatives are mentioned or prioritized.

Recommendations:

Provide equivalent instructions for Linux users, such as using Visual Studio Code or JetBrains Rider with the Azure Functions extension.
Include examples using the Azure CLI and/or Azure Functions Core Tools for project creation, extension installation, and deployment, which work cross-platform.
Show how to install NuGet packages using the dotnet CLI (e.g., 'dotnet add package ...'), which is cross-platform, instead of only using the Package Manager Console.
When describing publishing, include steps for deploying from Linux/macOS using the Azure CLI or GitHub Actions.
Avoid specifying 'Azure Function App (Windows)' as the only deployment target; mention Linux-based hosting plans and how to select them.
Add a 'Prerequisites' section for Linux/macOS, listing required tools and setup steps.
Where possible, use neutral terminology (e.g., 'terminal' instead of 'console') and avoid assuming the reader is using Windows.

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 PowerShell scripts and instructions for generating a service principal, referencing Windows-specific tools (PowerShell, Set-ExecutionPolicy), and omitting any equivalent Bash, Azure CLI, or Linux/macOS guidance. The step-by-step process assumes the user is on Windows, with no mention of how to accomplish the same tasks on Linux or macOS platforms.

Recommendations:

Provide equivalent Azure CLI (az) commands and Bash scripts for service principal creation and related steps, suitable for Linux/macOS users.
Include instructions for running scripts on Linux/macOS, such as using chmod +x and ./script.sh, and note differences in execution policy handling.
When referencing tools, mention cross-platform options (e.g., Azure CLI, Bash) alongside PowerShell.
Structure examples so that cross-platform (CLI/Bash) solutions are presented before or alongside Windows/PowerShell solutions, not after.
Add a note clarifying that all steps can be performed on Linux/macOS, and link to relevant cross-platform documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias in several areas. In the instructions for setting up a Python virtual environment, Windows PowerShell is mentioned first, and the Windows-specific command (`py -m venv .venv`) is listed before the Linux equivalent. The activation command for the virtual environment also lists the Windows path and PowerShell command before the Linux shell alternative. Additionally, file paths in output examples use Windows-style backslashes (e.g., `<ProjectRoot>\HttpTriggerAsync\__init__.py`), and there is a general assumption of familiarity with Windows tools and conventions throughout the guide.

Recommendations:

Present Linux and Windows instructions side-by-side or in parallel, rather than listing Windows first.
Use neutral or platform-agnostic language where possible (e.g., 'Open a terminal' instead of 'Open a Windows PowerShell or any Linux shell as you prefer').
Show both Windows and Linux commands together, or use tabbed sections for each OS.
Include Linux-style file paths in output examples, or provide both Windows and Linux variants.
Explicitly mention macOS where relevant, as it often shares commands with Linux.
Avoid assuming the use of Windows-specific tools or shells unless the guide is explicitly for Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates some Windows bias. In several sections, Windows-specific plans and settings are mentioned before Linux equivalents, and PowerShell examples are provided alongside Azure CLI, but there is a lack of Linux shell (bash) or cross-platform scripting examples. Some features and limitations are described in terms of their Windows applicability first, and Linux-specific guidance is sometimes relegated to later sections or notes. There are also areas where Linux-specific instructions or parity are missing or less detailed.

Recommendations:

Provide Linux (bash) command-line examples alongside PowerShell, especially in sections about mounting file shares and configuring app settings.
When describing features or limitations, present both Windows and Linux information together, or clarify applicability in a parallel structure (e.g., 'On Windows... On Linux...').
Ensure that all settings and deployment options are explained for both Windows and Linux hosting plans, including any differences in behavior or support.
Add more explicit Linux-focused troubleshooting and configuration guidance, particularly for storage and deployment scenarios.
Where features are Windows-only or Linux-only, clearly label them and provide alternative recommendations for the other platform.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides only a PowerShell script to identify function apps for migration, with no equivalent Bash, Azure CLI, or Linux-native instructions. The use of PowerShell and references to Visual Studio (a primarily Windows tool) suggest a Windows-centric approach. There are no Linux or cross-platform command-line examples for key migration steps, which may hinder users on Linux or macOS.

Recommendations:

Provide equivalent Azure CLI or Bash scripts alongside PowerShell examples for identifying function apps and other automation steps.
Explicitly mention cross-platform tools (e.g., Azure CLI, VS Code) and provide instructions for their use where appropriate.
Ensure that all code and command-line examples are available for both Windows and Linux/macOS environments.
Where Visual Studio is referenced, also mention Visual Studio Code and/or CLI-based deployment options for non-Windows users.
Add a note clarifying that PowerShell Core is available cross-platform, but still provide native Bash/Azure CLI alternatives 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 command-line examples use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The prerequisites and provisioning steps exclusively reference PowerShell, and there are no Linux or cross-platform instructions. Quickstart links also default to Windows or Visual Studio tabs, further reinforcing a Windows-centric approach.

Recommendations:

Provide equivalent Azure CLI (az) commands alongside PowerShell examples for provisioning and managing resources.
Include Linux/macOS-specific setup instructions, such as installing Azure CLI and authenticating with Azure Government.
Ensure quickstart links and code samples include tabs or options for Bash, Azure CLI, and non-Windows environments.
Avoid language in prerequisites and instructions that assumes the user is on Windows; mention cross-platform tools first or equally.
Add screenshots or terminal outputs from Linux/macOS environments where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows-first bias in several areas: Windows paths and terminology are consistently mentioned before Linux equivalents, and some deployment instructions and troubleshooting notes reference Windows-specific tools or behaviors (e.g., MSDeploy, c:\ paths) without providing Linux-specific alternatives or examples. There are no explicit Linux command-line or shell examples, and the documentation assumes familiarity with Windows conventions. Linux deployment nuances are mentioned, but not with the same level of detail or parity as Windows.

Recommendations:

Alternate the order of Windows and Linux references throughout the documentation, or present Linux examples first in some sections.
Provide explicit Linux shell (bash) command examples alongside any Windows/Powershell commands or references.
Include Linux-specific troubleshooting steps and tool recommendations (e.g., alternatives to MSDeploy or Windows file paths).
Clarify any differences in deployment workflows or behaviors between Windows and Linux, and ensure both are covered equally.
Where file paths are mentioned, use a neutral format or present both Windows and Linux paths together, not always with Windows first.
Add examples of using Linux-native tools (such as az CLI, curl, or scp) for uploading and managing deployment packages.
Ensure that all features and settings are explained with Linux parity, including any limitations or best practices specific to Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a 'Windows-first' bias in several areas: Windows instructions and examples are consistently presented before Linux equivalents, especially in the stack configuration update sections. Some language/platform combinations (e.g., Python on Windows) are explicitly unsupported, but the documentation does not always provide Linux alternatives in those cases. Additionally, the use of Azure portal and Azure CLI is mostly platform-agnostic, but the CLI examples for updating stack versions are more detailed for Windows, and Linux-specific details are sometimes relegated to notes or require extra navigation. There is also an implicit bias in the structure, where Windows is the default or primary path, and Linux is secondary.

Recommendations:

Present Windows and Linux instructions/examples in parallel or with equal prominence, rather than always listing Windows first.
Where a language/platform combination is unsupported (e.g., Python on Windows), provide a direct Linux example or link, rather than just instructing the user to switch tabs.
Ensure that CLI examples for Linux are as detailed and explicit as those for Windows, including full command examples for all supported languages.
Where limitations exist (e.g., Linux Consumption plan restrictions), provide clear alternative steps or workarounds for Linux users.
Consider a structure where the user selects their OS first, then sees language-specific instructions, to avoid implicit prioritization of Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias in several areas: Windows commands and tools (such as PowerShell and 'py') are often mentioned before or in more detail than their Linux equivalents. Some instructions and examples are Windows-centric or lack parity in Linux-specific guidance. While Linux is acknowledged as the Azure Functions runtime environment, and some Unix-like examples are present, the documentation could better balance platform representation, especially in command-line instructions and troubleshooting steps.

Recommendations:

Ensure all command-line examples are provided for both Windows (PowerShell/CMD) and Linux/macOS (Bash), and present them in parallel or with equal prominence.
When referencing tools like 'py' (Windows Python launcher), also mention 'python3' for Linux/macOS, and clarify which platforms each applies to.
Avoid listing Windows commands or tools first by default; alternate the order or present both together.
Where platform-specific issues are discussed (e.g., pywin32), provide equivalent Linux/macOS troubleshooting steps or explicitly state if none exist.
Expand on Linux-native tools and workflows (e.g., using Bash, Linux file paths, package managers) where relevant.
Audit all sections for missing Linux/macOS examples, especially in deployment, troubleshooting, and environment setup instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a mild Windows bias. PowerShell examples and references to Visual Studio are present, and PowerShell is given as a first-class scripting option alongside Azure CLI. While the article uses platform pivots to separate Windows and Linux content, some sections (such as PowerShell commands and Visual Studio notes) are only present for Windows, with no Linux equivalents or alternatives. Additionally, the documentation sometimes presents Windows-specific tools and workflows (e.g., .csproj editing, Visual Studio dialogs) without Linux or cross-platform alternatives, and PowerShell is presented as a primary automation tool, which is less common on Linux.

Recommendations:

Where PowerShell examples are given, provide equivalent Bash or shell script examples for Linux users.
When referencing Visual Studio or .csproj file edits, mention cross-platform alternatives such as Visual Studio Code or editing project files manually.
Ensure that all automation and scripting examples are available in both PowerShell and Bash/shell script formats, or clearly indicate which platforms each example applies to.
Where possible, avoid presenting Windows tools or workflows before Linux equivalents; instead, present both options together or in parallel.
Add more explicit guidance for Linux users in sections where only Windows-specific instructions or tools are currently described.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias in several areas. Windows technologies, tools, and terminology are often mentioned first or exclusively, such as Hyper-V, BitLocker, Windows Firewall, and Windows-specific security features. Powershell and Windows portal are frequently referenced as primary management interfaces, with Linux alternatives mentioned later or not at all. Some technical explanations (e.g., Drawbridge, Hypervisor, security mitigations) are deeply rooted in Windows architecture, and Linux-specific details are sometimes missing or less detailed.

Recommendations:

Ensure that Linux examples and tools (e.g., Azure CLI, SSH, Linux firewall, DM-Crypt) are presented alongside or before Windows equivalents, especially in code snippets, configuration, and management instructions.
Provide balanced coverage of both Windows and Linux in technical explanations, including equal detail on Linux-based isolation, security, and encryption mechanisms.
Avoid using Windows-centric terminology as the default; use cross-platform or neutral terms where possible.
When referencing management interfaces (portal, PowerShell, CLI), always include Azure CLI and Linux-native tools in parallel with Windows/PowerShell.
Expand sections on Linux-specific technologies (e.g., DM-Crypt, iptables, SELinux/AppArmor, SSH) to match the depth given to Windows technologies.
Review all tables, figures, and callouts to ensure Linux is equally represented in security guidance and best practices.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a moderate Windows bias, particularly in the developer guidance section. PowerShell is highlighted with a dedicated note about the Az module, and PowerShell cmdlets are given equal prominence to Azure CLI, with explicit links and examples. References to Visual Studio and System Center Operations Manager further reinforce a Windows-centric perspective. While Azure CLI is mentioned and examples are provided, there is little to no mention of Linux-native tools, shells, or workflows, and Windows tools or patterns (e.g., Visual Studio, PowerShell) are often referenced first or exclusively.

Recommendations:

Ensure that all command-line examples are provided for both Azure CLI and PowerShell, and clarify that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
When referencing PowerShell, also mention Bash or other Linux-native shells where appropriate, especially for scripting and automation scenarios.
Include examples or guidance for Linux/macOS users, such as using Bash scripts, connecting from Linux environments, or integrating with Linux-based developer tools.
Avoid assuming Visual Studio as the default IDE; mention alternatives like VS Code or JetBrains Rider, and provide instructions for configuring Application Insights or other services from non-Windows environments.
Where Windows-specific tools or workflows are discussed (e.g., System Center Operations Manager), add notes or links to equivalent Linux-native solutions or clarify if no equivalent exists.
Review the ordering of tool mentions to avoid always listing Windows/PowerShell first; alternate or list cross-platform tools (like Azure CLI) before platform-specific ones.

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, and does not mention or provide instructions for Linux users or alternative cross-platform tools. There are no Linux or macOS examples, nor are cross-platform command-line tools (such as Azure CLI) referenced. The workflow assumes a Windows environment by default.

Recommendations:

Include instructions for connecting to Azure Government using cross-platform tools such as Azure CLI or Azure PowerShell, which are available on Linux and macOS.
Mention and provide examples for using Visual Studio Code, which is cross-platform, as an alternative to Visual Studio.
Clearly state the platform requirements for Visual Studio and provide links or references to equivalent workflows for non-Windows users.
Add a section or links for Linux/macOS users to ensure parity and inclusivity.

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 instructions for listing VM extensions in Azure Government, with no equivalent CLI or Linux-native example. The guidance assumes use of Windows tools and patterns, and the only code sample is in PowerShell. Linux users are not given direct instructions or parity in the main workflow.

Recommendations:

Add equivalent Azure CLI (az) instructions for listing VM extensions, which work cross-platform (Linux, macOS, Windows).
Present both PowerShell and CLI examples side-by-side, or clearly indicate that the CLI example is suitable for Linux users.
Avoid assuming PowerShell as the default tool; mention alternatives up front.
Ensure that Linux workflows are described with equal prominence and clarity as Windows/PowerShell workflows.

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 Linux CLI or Bash examples for obtaining images, and Linux guidance is less prominent.

Recommendations:

Add equivalent Azure CLI (cross-platform) and Bash examples for listing VM images.
Include instructions for connecting to Azure Government using the Azure CLI.
Ensure Linux VM creation steps are presented with equal prominence and ordering as Windows steps.
Where possible, use neutral, cross-platform tooling (e.g., Azure CLI) in examples.

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 tool, and provides no examples or guidance for Linux or cross-platform workflows (such as using the Azure CLI, GitHub Actions, or VS Code). All instructions and screenshots are based on the Windows/Visual Studio experience, with no mention of Linux, macOS, or command-line alternatives.

Recommendations:

Add a section describing how to deploy an Azure App Services app using the Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
Include examples for deploying using GitHub Actions or Azure DevOps pipelines, which are platform-agnostic.
Mention and provide instructions for using Visual Studio Code, which is available on all major operating systems, as an alternative to Visual Studio 2019.
Ensure that screenshots and step-by-step guides are provided for both GUI (portal) and CLI-based workflows.
Explicitly state that the described workflow is Windows-specific and provide links to Linux/macOS deployment documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows-first bias, with Windows servers and tools (such as System Center Operations Manager and Endpoint Protection) mentioned before Linux equivalents. Visuals and examples predominantly feature Windows environments, and there is a lack of Linux-specific command-line or onboarding examples. Linux is mentioned, but often as a secondary consideration, and Linux-specific tooling or instructions are minimal or absent.

Recommendations:

Provide Linux onboarding examples and screenshots alongside Windows ones, ensuring parity in visual representation.
Include Linux-specific tooling (e.g., auditd, syslog, Linux-native antimalware solutions) in antimalware and monitoring solution discussions.
Present instructions for both Windows and Linux in parallel, rather than referencing Windows first or exclusively.
Add PowerShell and Bash/CLI examples side by side for agent installation, configuration, and automation.
Highlight Linux security scenarios and solutions (e.g., SELinux, AppArmor, fail2ban) in the cybersecurity solution sections.
Ensure that all referenced documentation links for onboarding and configuration are equally available for Linux and Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias primarily by recommending Windows-specific tools (Visual Studio) and patterns (e.g., 'Download Visual Studio 2019') as prerequisites, and by omitting explicit Linux/macOS alternatives or instructions for key development steps. While Azure Storage Explorer is cross-platform, the setup and workflow examples focus on Windows-centric development environments, with no mention of Linux/macOS equivalents for Visual Studio or command-line usage. There are no PowerShell-specific examples, but the overall workflow assumes a Windows-first audience.

Recommendations:

In the prerequisites, provide alternative instructions for Linux/macOS users, such as recommending VS Code or JetBrains Rider instead of only Visual Studio.
Explicitly state that Azure Storage Explorer is cross-platform and provide installation links or instructions for Linux/macOS.
For code samples, clarify that environment variables and SDKs work across platforms, and provide any necessary shell commands for Linux/macOS (e.g., setting environment variables in bash/zsh).
Include a section or note on how to set up the development environment on Linux/macOS, including installation of required SDKs and tools.
Avoid language that assumes the user is on Windows (e.g., 'Open Visual Studio'), or provide parallel instructions for other operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-centric bias, particularly in sections discussing legacy authentication and infrastructure. It exclusively references Windows-based technologies such as Active Directory Domain Services, ADFS, and Kerberos/NTLM, and provides deployment guidance only for Windows Server environments. There are no examples or guidance for Linux-based identity solutions, nor are cross-platform alternatives mentioned. The documentation assumes the use of Windows tools and patterns, omitting Linux or open-source equivalents.

Recommendations:

Include examples and guidance for integrating Linux-based identity solutions (e.g., using Samba for Active Directory compatibility, or integrating with LDAP/Kerberos on Linux).
Mention and provide links to documentation for cross-platform identity management tools and patterns, such as Azure AD authentication libraries for Linux and open-source stacks.
When discussing domain controllers and federation services, acknowledge that Linux-based solutions (such as FreeIPA, Samba AD DC, or Shibboleth for federation) can be used in some scenarios, and provide high-level guidance or references.
Ensure that any PowerShell or Windows-specific instructions are accompanied by equivalent Bash/CLI or Linux-native examples where possible.
Explicitly state the platform assumptions in each section and clarify whether the guidance is Windows-only or applicable to other operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas. Windows and Windows Server are mentioned explicitly as examples for encryption in transit (SMB 3.0), with no mention of Linux equivalents. There are references to Windows-specific protocols and tools (e.g., SMB 3.0, PowerShell in blog post titles), and Linux is only mentioned in passing or as an afterthought in linked blog posts. There are no Linux-specific examples or guidance for common scenarios, such as encrypting data in transit or at rest, or for managing secrets. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users.

Recommendations:

Include Linux-specific examples alongside Windows examples for encryption in transit (e.g., mention NFSv4.1 with Kerberos, SSH/SCP/SFTP, or SMB 3.0 on Linux).
Provide explicit guidance for Linux VMs regarding disk encryption (e.g., using Azure Disk Encryption with dm-crypt).
When referencing PowerShell or Windows tools, also reference equivalent Linux command-line tools or scripts (e.g., Azure CLI, Bash, Python SDK).
Add Linux-focused best practices for managing secrets, such as using Key Vault with Linux applications and integration patterns.
Ensure that blog post references and documentation examples are balanced, highlighting both Windows and Linux attack detection and mitigation scenarios.
Review all sections for implicit Windows-first language and update to be platform-neutral or to provide equal coverage for Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively providing onboarding and configuration examples using Azure PowerShell cmdlets and Windows-style variable declarations. There are no equivalent CLI (az), Bash, or Linux-native examples for onboarding, managing ExpressRoute, or enabling features. The only mention of Linux is in the context of installing a Red Hat Satellite server, but no Linux command-line or automation examples are provided. The documentation assumes familiarity with PowerShell and Windows-centric tooling, which may disadvantage Linux users.

Recommendations:

Provide equivalent Azure CLI (az) and Bash examples for all PowerShell commands and workflows, especially for ExpressRoute and network configuration.
When introducing command-line examples, present both Windows/PowerShell and Linux/Bash/CLI options, or clearly indicate which platforms each example applies to.
Explicitly mention Linux-compatible tools and patterns (such as Bash scripting, cloud-init, or Ansible) where appropriate.
Ensure that references to enabling features (like Accelerated Networking) include links and steps for both Windows and Linux VMs.
Review the order of presentation so that Linux and Windows are treated equally, or alternate which platform is presented first in examples.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in the section on retrieving the Azure Maps Client ID programmatically. PowerShell is presented first, with a detailed example using the Get-AzMapsAccount cmdlet, which is specific to Windows environments. The Azure CLI example is provided second, but there are no Linux- or macOS-specific shell examples (e.g., Bash, curl, jq), nor is there mention of cross-platform scripting approaches. The documentation also references Windows-centric tools and patterns (PowerShell) without providing parity for Linux users.

Recommendations:

Provide Bash (Linux/macOS) shell examples alongside PowerShell, using curl and jq to retrieve the Client ID via the Azure REST API or Azure CLI.
Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform.
Explicitly state that both PowerShell and Azure CLI are available on all major platforms, and clarify any platform-specific requirements.
Avoid assuming the use of Windows tools (such as PowerShell) as the default or primary method.
Where possible, use cross-platform tools and patterns in code samples to ensure inclusivity for Linux and macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While it does mention using Ubuntu on WSL for rio-rgbify (acknowledging Windows limitations), the overall flow assumes a Windows environment (e.g., mounting drives with drvfs, referencing D: drives, and using Azure Storage Explorer, which is primarily a Windows GUI tool). There are no explicit Linux-native or macOS-native instructions for key steps like uploading to Azure Blob Storage or running the workflow outside WSL. The documentation also references Windows filesystem conventions and tools before or instead of cross-platform or Linux-native alternatives.

Recommendations:

Provide explicit Linux and macOS instructions for all steps, not just WSL/Ubuntu. For example, show how to run rio-rgbify natively on Linux and macOS.
Offer command-line alternatives for uploading to Azure Blob Storage, such as using the Azure CLI (az storage blob upload), which is cross-platform.
Avoid referencing Windows drive letters (e.g., D:) and drvfs mounting in the main instructions. Instead, provide platform-agnostic or platform-specific sections.
Mention and demonstrate open-source or cross-platform tools where possible, and clarify when a tool is Windows-only.
Ensure screenshots and UI walkthroughs are not exclusively from Windows environments, or provide equivalents for other OSes.
Add a section or callouts for macOS users, especially for steps involving QGIS, Python, and Azure tools.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias primarily through its recommendation of the Windows-only Guidgen.exe tool for generating GUIDs, without mentioning cross-platform alternatives. There are no Linux or macOS-specific instructions or examples, and the only tool explicitly mentioned for a technical task is a Windows tool. Additionally, the documentation does not provide command-line or scripting examples (e.g., PowerShell, Bash, Azure CLI), but when it does suggest a tool, it defaults to a Windows solution.

Recommendations:

When suggesting GUID generation, include cross-platform options such as 'uuidgen' (available on Linux/macOS/Windows), Python's uuid module, or online GUID generators.
Avoid referencing Windows-only tools (like Guidgen.exe) without providing alternatives for other platforms.
Where possible, provide Azure CLI or REST API command-line examples for common tasks (e.g., creating managed identities, uploading blobs), and show both Windows (PowerShell/CMD) and Linux/macOS (Bash) syntax.
Explicitly state that all steps can be performed from any OS using the Azure Portal or cross-platform tools.
If screenshots are used, consider including at least one from a non-Windows environment, or clarify that the portal UI is OS-agnostic.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a clear Windows bias by exclusively using PowerShell commands for all shell-based instructions, such as creating projects, installing packages, and setting environment variables. There are no equivalent examples for Linux or macOS shells (e.g., Bash), and the syntax for setting environment variables is only shown in PowerShell format. This may hinder Linux/macOS developers from following the guide smoothly.

Recommendations:

For every PowerShell command, provide an equivalent Bash (Linux/macOS) example, especially for dotnet CLI usage and setting environment variables.
When showing how to set environment variables, include both PowerShell and Bash syntax (e.g., $Env:VAR=... for PowerShell, export VAR=... for Bash).
Add a note at the start of the guide clarifying that examples are provided for both Windows (PowerShell) and Linux/macOS (Bash) users.
Consider using cross-platform neutral language and tools where possible, or explicitly mention platform differences.
Review screenshots and UI instructions to ensure they are not Windows-specific unless necessary.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation includes a prominent call-out for 'PowerShell & CLI', suggesting a focus on Windows-centric tooling (PowerShell) and potentially placing it before or above Linux-native alternatives. There are no explicit Linux command-line examples, nor is there mention of Linux-specific tools or workflows. The absence of Linux examples or parity in instructions may make the documentation less accessible for Linux administrators, who are common in SAP HANA environments.

Recommendations:

Provide explicit Linux CLI (bash, az CLI) examples alongside or before PowerShell examples.
Clarify in the 'PowerShell & CLI call-out' section that both Windows and Linux users are supported, and link to relevant Linux instructions.
Include screenshots or terminal snippets from Linux environments where applicable.
Ensure that any automation or scripting guidance is available in both PowerShell and bash/az CLI formats.
Review all referenced include files (such as application-volume-group-powershell.md) to ensure Linux parity.

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 for project creation, file creation, environment variable setup, and program execution use PowerShell syntax, with no equivalent Bash or Linux/macOS shell commands provided. Windows tools and patterns (e.g., PowerShell's New-Item, $Env:VAR) are used exclusively, and Linux alternatives are not mentioned or shown. This may hinder Linux/macOS users, who form a significant portion of the Java development community.

Recommendations:

For every PowerShell example, provide an equivalent Bash/Linux/macOS shell example side-by-side or in a tabbed interface.
When showing environment variable setup, include both PowerShell ($Env:VAR=) and Bash (export VAR=) syntax.
For file creation, show both New-Item (PowerShell) and touch (Bash) commands.
For running Java programs, show both Windows (java .\demo.java) and Linux/macOS (java ./demo.java) command syntax.
Explicitly state that the instructions apply to both Windows and Linux/macOS, and highlight any OS-specific differences.
Consider using cross-platform-neutral language and tools where possible, or at least avoid presenting Windows as the default or only option.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively using PowerShell commands for project setup and environment variable configuration. There are no Linux/macOS shell (bash) equivalents provided for creating directories, files, or setting environment variables. This may hinder Linux and macOS users, as the instructions are not directly applicable to their platforms.

Recommendations:

Provide equivalent bash (Linux/macOS) commands alongside PowerShell for all shell-based instructions, such as project directory creation and environment variable setting.
When showing how to set environment variables, include both PowerShell and bash/zsh syntax (e.g., export VAR=value).
Consider using platform-agnostic language or clearly labeling which commands are for Windows and which are for Linux/macOS.
Add a note or section addressing cross-platform usage, ensuring parity and clarity for users on non-Windows systems.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently uses PowerShell commands (e.g., mkdir, cd, npm init, npm install, node search.js) for all shell-based instructions, which are Windows-centric. No Linux or macOS shell equivalents (such as bash or sh) are provided, and there is no mention of cross-platform compatibility for these commands. This may create the impression that the guide is primarily intended for Windows users and could hinder Linux/macOS users who expect bash/zsh syntax.

Recommendations:

Provide both PowerShell (Windows) and bash (Linux/macOS) command examples for all shell instructions, or use bash as the default for broader cross-platform compatibility.
Explicitly mention that the commands are cross-platform where applicable, or note any platform-specific differences.
Where screenshots or UI instructions are given, clarify if the steps are identical across platforms or provide alternatives if not.
Consider using 'terminal' or 'shell' instead of 'PowerShell' in code block labels unless the syntax is truly PowerShell-specific.
Add a short section or note at the beginning clarifying that the SDK and instructions are cross-platform and that examples are provided for both Windows and Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias, primarily by referencing Windows-specific documentation first (e.g., linking to '/azure/virtual-machines/windows/proximity-placement-groups-portal' for PPG creation), and not providing Linux-specific examples or links. There are no explicit PowerShell commands or Windows-only tools, but the absence of Linux/CLI parity and the prioritization of Windows links suggest a Windows-centric approach.

Recommendations:

Provide equivalent Linux/CLI documentation links alongside or before Windows-specific links (e.g., link to '/azure/virtual-machines/linux/proximity-placement-groups-portal' if available).
Include examples or references for both Windows and Linux environments when discussing deployment steps, tools, or portal navigation.
Ensure that terminology and instructions are platform-neutral where possible, or explicitly call out differences for Linux users.
Review all 'Next steps' and in-text links to ensure Linux users are equally supported and not directed only to Windows-centric resources.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting all command-line examples in PowerShell syntax, explicitly stating that Azure CLI is run in a PowerShell instance, and using variable assignment and command substitution patterns specific to PowerShell (e.g., $var = $(...)). There are no examples or notes for running the same commands in Bash or other Linux shells, nor is there guidance for Linux or macOS users. The only scripting example is in PowerShell, and the documentation assumes a Windows environment throughout.

Recommendations:

Provide parallel Bash/Linux shell examples for all Azure CLI commands, including variable assignment and command substitution.
Add a note early in the document clarifying that Azure CLI commands can be run from any platform, and provide guidance for both Windows (PowerShell) and Linux/macOS (Bash).
Where PowerShell-specific syntax is used (e.g., $var = $(...)), show the equivalent Bash syntax (e.g., var=$(...) or use export).
In the 'Complete script example' section, include a Bash version of the script.
Avoid language such as 'runs in a PowerShell instance' unless also mentioning Bash or cross-platform alternatives.
Ensure that references to tools or commands (such as Get-AzADUser) are either cross-platform or alternatives are provided for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page references a CLI & PowerShell limitation via an include, but does not provide any Linux or cross-platform CLI examples. The mention of PowerShell before CLI in the included note, and the absence of Linux-specific guidance or examples, suggests a Windows-first and PowerShell-heavy bias. There are no explicit Linux commands, tools, or screenshots, and no mention of Linux mounting procedures or shell commands, which are highly relevant for SAP HANA deployments that are often Linux-based.

Recommendations:

Provide explicit Linux shell (bash) examples for common operations, such as mounting NFS volumes or interacting with the Azure CLI.
Ensure that any limitations or notes referencing PowerShell also mention Linux CLI equivalents, or clarify if there are none.
Include screenshots or instructions that are relevant to Linux environments, not just Windows or PowerShell.
Where possible, present CLI (cross-platform) instructions before or alongside PowerShell instructions to avoid a Windows-first impression.
Add a section or callout specifically addressing Linux administrators, especially since SAP HANA is typically deployed on Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by referencing PowerShell and CLI in a call-out at the top, but does not provide explicit Linux/Unix shell (bash) examples or mention Linux-native tools. The use of 'PowerShell & CLI' as a combined resource may imply a preference for Windows tooling, and there are no Linux-specific instructions or screenshots. The documentation does not address or acknowledge Linux environments, which are common for SAP HANA deployments.

Recommendations:

Provide explicit bash/Unix shell examples alongside PowerShell, especially for command-line operations relevant to Azure NetApp Files.
Clarify in the 'PowerShell & CLI call-out' section whether the CLI examples are cross-platform and, if so, provide Linux-specific usage notes or screenshots.
Include references to Linux-native tools or workflows where appropriate, such as using az CLI from a Linux terminal.
Add notes or sections addressing Linux administrators, acknowledging that SAP HANA is often deployed on Linux, and ensure parity in instructions and examples.
Where screenshots or UI references are shown, clarify that the steps are applicable regardless of the underlying OS, or provide Linux-specific context if there are differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page includes a call-out specifically for CLI & PowerShell, suggesting a focus on Windows and PowerShell tooling. There are no explicit Linux shell or bash examples, and the mention of PowerShell appears before any Linux-native tooling. While there is a note about Linux host reconfiguration, the operational guidance and examples are Windows-centric, lacking parity for Linux users.

Recommendations:

Add equivalent Linux/Bash CLI examples alongside or before PowerShell examples to ensure parity.
Provide explicit instructions or references for managing volumes using Linux-native tools (e.g., Azure CLI in Bash, shell scripts).
Balance the order of example presentation so that Linux and Windows users are equally supported.
Clarify in the call-out or steps that all operations can be performed from both Windows and Linux environments, and provide links to relevant Linux documentation where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation references a CLI & PowerShell limitation, indicating a focus on Windows and PowerShell tooling. There are no Linux-specific examples, nor are Linux-native tools or commands mentioned. The documentation does not provide parity for Linux users, and the mention of PowerShell appears before any mention of CLI, reinforcing a Windows-first perspective.

Recommendations:

Explicitly provide Linux CLI examples alongside or before PowerShell examples.
Clarify if the CLI refers to Azure CLI, and provide Linux shell command syntax where appropriate.
If there are limitations or differences for Linux users, document them clearly.
Include screenshots or walkthroughs using Linux environments or terminal windows.
Balance references to PowerShell with Bash or other common Linux shells to ensure cross-platform usability.

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 and .NET Framework. All setup and code examples assume the use of Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. There are no instructions or examples for running or developing the WCF Relay service or client on Linux or macOS, nor any mention of .NET Core/.NET 5+ (which are cross-platform). Windows-specific tools and workflows (e.g., Visual Studio, Solution Explorer, App.config) are referenced exclusively and repeatedly, and there are no PowerShell scripts, but the overall workflow is Windows-centric.

Recommendations:

Add instructions and examples for setting up and running the WCF Relay service and client using .NET Core or .NET 5+ (which are cross-platform) instead of only .NET Framework.
Include steps for using Visual Studio Code or command-line tools (dotnet CLI) for project creation, dependency management, and building/running the application, which work on Linux and macOS as well as Windows.
Provide sample code and configuration for Linux/macOS environments, including any necessary changes to configuration files (e.g., using appsettings.json instead of App.config where appropriate).
Mention and demonstrate how to install the required SDKs and dependencies on Linux (e.g., via apt, yum, or Homebrew) and how to run the applications from the terminal.
Clarify any platform-specific limitations of WCF (e.g., that full WCF server support is not available on .NET Core/.NET 5+ and thus not on Linux), and suggest alternatives (such as gRPC or ASP.NET Core for REST services) for cross-platform scenarios.
Where Visual Studio is referenced, also mention Visual Studio Code and/or JetBrains Rider as alternatives, and provide equivalent instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page references a '[CLI & PowerShell call-out]' include at the top, suggesting a focus on Windows and PowerShell tooling. There are no explicit Linux or bash examples, nor is there mention of Linux-native tooling or command-line patterns. The only protocol guidance is generic (NFS/dNFS), and there is no step-by-step example for Linux users or mention of Linux-specific considerations. This results in a Windows-first and PowerShell-heavy bias, with missing Linux parity.

Recommendations:

Add explicit Linux/Bash CLI examples alongside or before PowerShell examples, especially in the referenced call-out include.
Mention Linux-native tools (such as Azure CLI in Bash, or relevant shell commands) in the main workflow.
Include screenshots or walkthroughs from a Linux admin perspective, such as mounting NFS volumes from a Linux VM.
Clarify any OS-specific requirements or differences, especially regarding NFS/dNFS configuration on Linux.
Ensure that all steps referencing PowerShell or Windows tools are mirrored with Linux equivalents.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows by providing Azure PowerShell commands as the primary example for feature registration and status checking, mentioning Azure CLI only as an afterthought. There are no Linux/bash-specific examples or screenshots, and the workflow assumes familiarity with Windows-centric tooling. No Linux-native tools or command-line patterns are shown, and the ordering of examples prioritizes PowerShell over cross-platform alternatives.

Recommendations:

Provide both Azure PowerShell and Azure CLI (bash) command examples side-by-side for all feature registration and status-checking steps.
Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users, and provide equivalent bash syntax.
Include screenshots or terminal snippets that reflect Linux environments where appropriate.
Avoid assuming PowerShell as the default shell; clarify that both PowerShell and bash are supported.
Instruct users on how to perform tasks using both Windows and Linux-native tools where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides detailed, step-by-step Linux/Unix shell examples for SAP HANA, Oracle, and IBM Db2, but for Microsoft SQL Server, it only provides Windows-specific instructions and examples (e.g., using .\azacsnap.exe and Windows shell syntax). There are no examples or guidance for running AzAcSnap or SQL Server integration on Linux, despite SQL Server being supported on Linux. The documentation also references Windows tools and patterns (such as .exe invocation and backslash path separators) for SQL Server, and does not mention or prioritize Linux alternatives or parity for SQL Server scenarios.

Recommendations:

Add explicit instructions and examples for configuring and using AzAcSnap with Microsoft SQL Server on Linux, including Linux shell commands and paths.
Provide parity in example commands for both Windows and Linux environments for SQL Server, using appropriate syntax for each (e.g., .\azacsnap.exe for Windows, ./azacsnap for Linux).
Mention and document any differences or requirements for SQL Server on Linux (such as service names, user permissions, and environment variables).
Avoid assuming Windows as the default or only environment for SQL Server; present both platforms equally, or clarify when a feature is Windows-only.
Where possible, use cross-platform language and avoid Windows-centric terminology (such as backslash path separators or .exe extensions) unless specifically required.

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 instructions and tools, mentioning PowerShell module updates before Azure CLI, and providing PowerShell commands as the primary example for feature registration. Linux/Unix equivalents are only briefly referenced, and no explicit Linux shell or Bash examples are given.

Recommendations:

Provide Bash/Azure CLI examples alongside or before PowerShell examples for all command-line instructions.
When referencing module updates or prerequisites, ensure parity by including both PowerShell (Windows) and Bash (Linux/macOS) instructions.
Where PowerShell commands are shown, also show the equivalent Azure CLI or REST API commands in Bash syntax.
Avoid assuming the user is on Windows; use neutral language and cross-platform examples.
Explicitly mention that all steps can be performed from Linux/macOS environments using Azure CLI or REST API, and provide links or examples as appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and command tables, while omitting equivalent Linux or cross-platform shell (e.g., Bash) examples. The PowerShell section is comprehensive and appears after Azure CLI, but there is no mention of Linux-specific tools, shell environments, or guidance for users on non-Windows platforms. REST API and Azure CLI sections are present, but the CLI section does not clarify cross-platform usage or address Linux-specific considerations. The 'Next steps' also reference PowerShell-specific REST API usage.

Recommendations:

Add explicit Bash/Linux shell examples alongside PowerShell commands, especially for connecting to Azure Government.
Clarify that Azure CLI is cross-platform and provide example commands in both Windows (CMD/PowerShell) and Linux (Bash) syntax where differences exist.
Include notes or sections for Linux/macOS users, such as how to install and use Azure CLI or relevant tools on those platforms.
Balance the prominence of PowerShell and CLI sections, ensuring that Linux-friendly workflows are equally detailed and discoverable.
In 'Next steps', add links to Linux/Bash-focused guides or REST API usage from non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a Windows bias in several ways: it provides only Windows-based instructions and screenshots for managing SMB permissions, exclusively references Windows tools (MMC, Windows File Browser, net view), and omits any Linux or cross-platform examples for accessing or managing SMB volumes. Linux SMB clients and their management tools are not mentioned, and all permission management guidance is Windows-centric.

Recommendations:

Add equivalent instructions and screenshots for managing SMB share and file permissions from Linux clients, such as using smbclient, mount.cifs, or setfacl.
Include examples of mounting SMB volumes from Linux systems, referencing relevant commands and configuration steps.
Mention and link to Linux tools (e.g., smbclient, cifs-utils) alongside Windows tools when discussing SMB access and management.
Clarify that SMB volumes can be accessed from non-Windows clients and provide guidance or links for those scenarios.
Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or provide a dedicated section for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates subtle Windows bias by referencing Windows VM sizes before Linux equivalents, linking to Windows VM sizing documentation first, and mentioning Windows binary availability for FIO before Linux. There are no explicit Linux command-line examples or Linux-specific guidance, and no example commands for either platform. The documentation also references Azure Monitor and REST API access in a platform-neutral way, but omits any Linux-specific monitoring or scripting examples.

Recommendations:

Present Linux and Windows VM sizing links in parallel or mention Linux first, as Linux is often the default for performance benchmarking.
Provide explicit example commands for both Linux (e.g., bash shell) and Windows (e.g., PowerShell or CMD) when discussing tools like FIO, SSB, or API usage.
Include Linux-specific guidance for installing and running benchmarking tools, such as package manager commands (e.g., apt-get install fio).
Highlight any differences or considerations for running benchmarks on Linux vs. Windows, such as filesystem or mount options.
Ensure that tool descriptions and recommendations do not prioritize Windows availability or usage unless there is a technical reason.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands (e.g., Set-ADComputer) for configuring Active Directory computer accounts, referencing Windows-only tools such as RSAT, and describing AD DS/Entra as the only supported Kerberos infrastructure. Linux is mentioned as the NFS client, but no Linux-native alternatives or cross-platform methods for managing the required AD/Kerberos configuration are provided. The order of instructions also places Windows/AD configuration steps before Linux client steps, reinforcing a Windows-centric workflow.

Recommendations:

Provide equivalent Linux-native commands (e.g., using 'ldapmodify', 'kadmin', or 'adcli') for setting Kerberos encryption types on computer accounts in Active Directory.
Mention and link to cross-platform tools or APIs (such as Samba's 'net ads', or Python/LDAP scripts) that can be used from Linux systems to manage AD objects.
Clarify whether non-Windows Kerberos Key Distribution Centers (KDCs) are supported, and if so, provide guidance for those environments.
Reorder sections or provide parallel instructions so that Linux and Windows administrative tasks are presented with equal prominence.
Explicitly state any limitations or requirements that force the use of Windows tools, and suggest workarounds or alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

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 Linux-native tools or shell scripting examples. There are no Linux-specific instructions, nor is there any guidance for users on Linux or macOS platforms. The focus on PowerShell and lack of Linux examples or tools suggests a Windows bias.

Recommendations:

Add explicit examples or references for using Azure CLI on Linux and macOS, including installation and usage notes.
Include bash or shell script examples for common tasks, not just PowerShell.
Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
If possible, mention or link to Linux package managers (apt, yum, etc.) for installing Azure CLI.
Consider including a table or section highlighting platform compatibility for each tool.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. While it is mostly platform-agnostic in its main content (focused on Kusto queries and Azure portal usage), it lists PowerShell as the first automation client for ARG, and links to a PowerShell-specific tutorial before mentioning Azure CLI or SDKs. There are no explicit Linux shell or bash examples, and no mention of Linux-specific tools or workflows, which may make Linux users feel less prioritized.

Recommendations:

List Azure CLI before PowerShell when mentioning automation clients, or present both together to avoid implying a Windows-first workflow.
Include explicit bash/Azure CLI examples for running ARG queries, especially for automation scenarios.
Provide links to both PowerShell and Azure CLI tutorials/documentation equally, ensuring Linux users have clear guidance.
Mention that ARG queries can be run from any platform using the Azure CLI, not just from PowerShell or the portal.
Consider adding a short section or note on cross-platform usage, highlighting Linux compatibility and any platform-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias. All configuration and monitoring examples use Windows-specific tools (e.g., PowerShell cmdlets like Get-SmbClientNetworkInterface, set-SmbClientConfiguration, and Windows Performance Monitor). References and links are exclusively to Windows documentation. There are no examples or guidance for Linux SMB clients, nor are Linux tools or commands mentioned. The text assumes the reader is using Windows or Hyper-V environments.

Recommendations:

Add equivalent Linux SMB client configuration and monitoring examples (e.g., using smbclient, mount.cifs, or smbtorture).
Include Linux command-line examples for checking SMB Multichannel, RSS, and encryption support (e.g., using smbstatus, /proc/fs/cifs, or relevant sysfs entries).
Reference Linux documentation and tools (such as Samba, cifs-utils, or Linux performance monitoring tools like iostat, ifstat, or perf).
Provide performance tuning guidance for Linux SMB clients, including relevant sysctl or mount options.
Clarify which recommendations are Windows-specific and which are cross-platform, and structure sections to present both Windows and Linux guidance in parallel where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows/Active Directory-centric bias. It exclusively discusses integration with Active Directory Domain Services (AD DS) or Microsoft Entra Domain Services, with explicit statements that OpenLDAP or other third-party LDAP services are not supported. All attribute management examples and screenshots use Windows tools (Active Directory Users and Computers MMC snap-in, Multi-valued String Editor, Attribute Editor), and guidance for modifying LDAP server settings references Windows-specific tools (Ntdsutil.exe). There are no examples or instructions for managing POSIX attributes or LDAP integration from a Linux LDAP server perspective, and Linux tools for attribute management are not mentioned. Linux is only referenced in the context of NFS clients, not as a potential LDAP server or management environment.

Recommendations:

Clarify early in the documentation that only AD DS and Microsoft Entra Domain Services are supported, but also acknowledge the limitation and, if possible, provide a roadmap or alternatives for Linux/OpenLDAP users.
Where attribute management is discussed, provide equivalent command-line examples (e.g., using ldapmodify or ldapadd) for environments where AD DS is managed from Linux or via scripts.
Include a note or section explaining why OpenLDAP or other Linux-based LDAP servers are not supported, and what technical requirements or features are missing.
If feasible, provide troubleshooting steps or references for Linux administrators who may need to interact with AD DS from Linux hosts (e.g., using Samba tools, ldapsearch, or other cross-platform utilities).
Balance screenshots and examples by including at least one example of managing POSIX attributes using non-Windows tools, or clarify that all management must be done via Windows tools due to product limitations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily provides Azure PowerShell examples for feature registration and status checking, with Azure CLI commands only briefly mentioned in text and not shown as code examples. There are no explicit Linux shell or cross-platform CLI examples, and the step-by-step instructions and screenshots are focused on the Azure Portal UI, which is platform-agnostic but the scripting focus is Windows/Powershell-centric.

Recommendations:

Provide explicit Azure CLI (az) command examples alongside PowerShell for all feature registration and status steps, formatted as code blocks.
When referencing command-line operations, present CLI examples first or in parallel with PowerShell to avoid a Windows-first impression.
Include notes or sections clarifying that all CLI steps can be performed from Linux, macOS, or Windows, and provide any OS-specific considerations if relevant.
Where possible, add bash/zsh shell command snippets for tasks that can be performed outside the Azure Portal, ensuring Linux users have clear guidance.
Ensure parity in screenshots or UI walkthroughs by noting that the Azure Portal experience is the same across platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes root CA certificate generation and export using Windows Server tools (Certification Authority, MMC snap-in), with no mention of Linux-based alternatives or cross-platform methods. All certificate management steps assume a Windows environment, and there are no examples or instructions for performing these tasks on Linux systems.

Recommendations:

Add instructions for generating and exporting root CA certificates using common Linux tools such as OpenSSL.
Include Linux command-line examples for certificate management alongside or before Windows-specific instructions.
Mention that both Windows and Linux-based CAs are supported, and provide guidance for both environments.
Balance screenshots and tool references by including Linux terminal output or GUI alternatives where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell command examples (e.g., Get-AzProviderFeature) for feature registration checks, without offering equivalent Azure CLI (cross-platform) or Bash examples. There are no Linux/Unix command-line instructions or screenshots, and all command-line guidance assumes the use of PowerShell, which is most common on Windows. No mention is made of Linux-native tools or workflows.

Recommendations:

For every PowerShell command example, provide an equivalent Azure CLI (az) command, which is cross-platform and commonly used on Linux and macOS.
Include explicit instructions or code snippets for Bash or shell environments when referencing command-line operations.
Clarify that the Azure portal and Terraform steps are platform-agnostic, and avoid implying a Windows-only workflow.
Where screenshots show command-line tools, ensure at least some are from a Linux terminal or a cross-platform shell.
Add a note at the beginning stating that all operations can be performed from Windows, Linux, or macOS, and link to platform-specific setup guides if needed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. PowerShell and Windows-centric tools (such as Set-ADUser, Group Policy, and Windows registry keys) are used exclusively for configuration and management tasks, with no equivalent Linux or cross-platform examples. Windows terminology and patterns are presented first or exclusively, and there is a lack of guidance for administrators using Linux-based AD management tools or environments.

Recommendations:

Provide equivalent Linux/Unix command-line examples (e.g., using 'ldapmodify', 'kinit', or 'adcli') for configuring Kerberos encryption types and managing AD accounts.
Include instructions or references for managing Active Directory from Linux systems, such as using Samba tools or openldap utilities.
When discussing Group Policy or registry settings, mention if and how similar configurations can be managed from non-Windows environments.
Balance the order of presentation so that Linux/NFS and Windows/SMB use cases are given equal prominence, especially in sections relevant to both.
Add troubleshooting steps and best practices for Linux clients, particularly for NFS and Kerberos integration.
Explicitly state any limitations or requirements for Linux-based AD management, and provide links to relevant Microsoft or community documentation.

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 examples for feature registration and status checking, mentioning PowerShell commands first and in detail, and relegating Azure CLI (cross-platform) commands to a brief mention without examples. No Linux-specific or cross-platform shell examples are provided, which may disadvantage users on non-Windows platforms.

Recommendations:

Provide full Azure CLI command examples (e.g., 'az feature register' and 'az feature show') alongside PowerShell, not just as a mention.
Present CLI examples before or alongside PowerShell to avoid the impression of Windows-first bias.
Explicitly state that both PowerShell and CLI are supported and clarify which environments are required for each.
Consider including Bash shell usage examples for Linux/macOS users where relevant.
Review other sections for similar patterns and ensure parity in tooling and instructions for all major platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by focusing on Windows-based tools and workflows for managing LDAP POSIX attributes (e.g., exclusively referencing the Active Directory Users and Computers MMC snap-in and providing step-by-step instructions for accessing the Attribute Editor on Windows). There are no equivalent instructions or examples for managing POSIX attributes from Linux or cross-platform tools. Additionally, Windows terminology and tools are mentioned first or exclusively in several sections, while Linux or NFS client configuration is only referenced via a link, not with inline examples.

Recommendations:

Provide equivalent instructions for managing LDAP POSIX attributes using Linux tools (e.g., ldapmodify, ldapadd, or Apache Directory Studio) alongside the Windows MMC snap-in example.
Include examples or screenshots of editing POSIX attributes from a Linux environment or using cross-platform LDAP management tools.
When describing workflows or tools, present both Windows and Linux options in parallel, or alternate which platform is mentioned first to avoid a 'Windows-first' impression.
Expand the 'Configure the NFS client' section with at least a basic example of mounting the volume from a Linux client, rather than only linking to another page.
Where possible, use neutral terminology (e.g., 'LDAP management tool') and clarify when a step is platform-specific.

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 SMB/Windows-specific features (such as ACLs and permission inheritance). There are no explicit Linux command-line or configuration examples, and the integration with Active Directory (a Windows-centric directory service) is highlighted without mention of alternatives. Linux/UNIX tools, commands, or perspectives are underrepresented or missing.

Recommendations:

Alternate the order of SMB and NFS discussions to avoid always foregrounding Windows technologies.
Provide concrete Linux/UNIX command-line examples (e.g., using chmod, setfacl, or mount commands for NFS permissions and inheritance).
Include references or examples for integrating with non-Active Directory LDAP servers (such as OpenLDAP) if supported, or clarify if only Windows-based directory services are available.
Expand on NFS advanced permissions and inheritance with practical Linux examples, not just theoretical descriptions.
Where possible, add parity in detail and depth between SMB (Windows) and NFS (Linux/UNIX) sections, ensuring both audiences are equally served.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily uses Azure PowerShell commands to demonstrate how to disable showmount, with Azure CLI only mentioned secondarily and without examples. There are no Linux shell or cross-platform command examples, and the workflow assumes familiarity with PowerShell and the Azure Portal UI, both of which are more common in Windows environments.

Recommendations:

Provide explicit Azure CLI command examples (e.g., 'az feature register', 'az feature show', 'az feature unregister') alongside or before PowerShell examples.
Include bash/Linux shell command snippets for interacting with Azure CLI, making it clear that the process is cross-platform.
Clarify in the introduction that the feature can be managed equally from Windows, Linux, or macOS environments using Azure CLI.
Balance the order of examples so that CLI and PowerShell are presented together, or alternate which comes first.
Add notes or links for users who may not have PowerShell available, guiding them to install and use Azure CLI on Linux/macOS.

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 DNS concepts, providing Windows-centric instructions and screenshots, referencing Microsoft best practices and tools first, and offering more detailed Windows (nslookup) examples before Linux (dig). Linux/BIND is mentioned but not explored in depth, and Linux-specific configuration or troubleshooting steps are minimal or missing.

Recommendations:

Provide Linux/BIND DNS configuration and troubleshooting steps alongside or before Windows/Active Directory instructions.
Include Linux/BIND screenshots and examples for DNS management, not just Windows DNS Manager.
Expand the 'dig' section to match the detail and troubleshooting depth of the 'nslookup' (Windows) section.
Offer parity in packet capture and DNS update examples for Linux environments (e.g., using tcpdump, journalctl, or BIND logs).
Reference Linux/BIND best practices and documentation links in parallel to Microsoft/Windows links.
Clarify when features (like secure DDNS) are exclusive to Microsoft DNS and suggest alternatives or workarounds for Linux/BIND users.
Balance terminology by not assuming Active Directory or Windows DNS as the default; explicitly address both Windows and Linux DNS scenarios throughout.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by frequently referencing Windows/Active Directory tools and concepts first or exclusively, providing more detail on Windows/NTFS behaviors, and omitting concrete Linux/NFS client command examples for permission management. While both UNIX and NTFS security styles are described, practical guidance and examples for Linux/NFS environments are limited, and Windows terminology and tools (such as Windows RPC, SIDs, and NTFS ACLs) are often mentioned before or instead of their Linux equivalents.

Recommendations:

Include explicit Linux/NFS client command examples for managing permissions (e.g., show usage of nfs4_setfacl, chown, chmod) alongside or before Windows/NTFS examples.
Balance the order of presentation so that Linux/NFS concepts and tools are described with equal prominence as Windows/NTFS ones.
Provide practical Linux/NFS troubleshooting scenarios and solutions, similar to the detailed Windows/Active Directory authentication flows.
Reference Linux identity management solutions (such as sssd, nsswitch, or local passwd/group files) where relevant, not just Active Directory/LDAP.
Clarify limitations and best practices for Linux/NFS environments (e.g., how to manage NFSv4.x ACLs, what to expect with POSIX permissions) with concrete examples.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references Windows systems and PowerShell commands for verifying SMB Continuous Availability. There are no examples or instructions for Linux clients, nor are Linux tools or workflows mentioned. The reboot step explicitly refers to 'Windows systems', and the verification step uses a Windows-only PowerShell cmdlet.

Recommendations:

Add equivalent instructions for Linux clients, such as how to remount SMB shares or restart relevant services after enabling CA.
Provide Linux command-line examples (e.g., using smbstatus, smbclient, or mount options) to verify CA status from a Linux system.
Clarify whether CA is relevant or supported for non-Windows SMB clients, and if not, state this explicitly.
Avoid assuming all users are on Windows by using more neutral language (e.g., 'client systems' instead of 'Windows systems') where appropriate.
If certain features or verification steps are only available on Windows, note this clearly and provide any possible alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits some Windows bias, particularly in the SMB-focused sections. Windows workloads and tools are mentioned first or exclusively in several places, especially regarding SMB Transparent Failover and supported workloads. Linux equivalents for SMB-based scenarios are either omitted or explicitly marked as unsupported. In the Boomi section, Windows is prioritized for SMB, while Linux is mentioned for NFS, but there are no detailed Linux/SMB examples. The 'Next steps' section provides a link for mounting SMB volumes only for Windows VMs, with no equivalent for Linux, and the SMB application support list excludes Linux SQL Server.

Recommendations:

Provide explicit Linux examples or guidance for SMB-based scenarios, or clarify if/why they are unsupported.
When listing supported workloads or tools, avoid listing Windows-only options first; instead, present both Linux and Windows options together or clarify parity.
Add a 'Mount SMB volumes for Linux VMs' link or section in the 'Next steps' area, or state if this is unsupported and why.
For each application scenario (e.g., SQL Server, Boomi), include Linux guidance where possible, or clearly state support limitations.
Review and balance the order of protocol/tool mentions (e.g., NFS and SMB) to avoid implicit prioritization of Windows/SMB.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Linux (rsync) and Windows (robocopy) tool examples for file-based data migration, but consistently lists the Windows tool (robocopy) after the Linux tool (rsync). However, there is a subtle bias in the detailed linking and explanation for robocopy (linking to Windows Server docs), and the overall documentation structure and language is more familiar to Windows administrators (e.g., references to SMB, robocopy, and Azure-specific tools). There are no explicit Linux command examples or step-by-step instructions, and PowerShell/Windows terminology is more prevalent. There is also a lack of parity in providing detailed Linux/NFS migration examples or links to Linux documentation.

Recommendations:

Provide explicit Linux/NFS migration examples, including sample rsync commands and links to official rsync documentation or Linux man pages.
Balance the documentation by including both Windows (robocopy) and Linux (rsync) examples side by side, with equal detail and prominence.
Include references to Linux-native tools (such as scp, cp, or tar) where appropriate, and provide links to their documentation.
Avoid assuming Windows/PowerShell familiarity by explaining SMB and NFS concepts equally, and by not prioritizing Windows terminology.
Add a section or table comparing migration tools for both Linux and Windows environments, with pros, cons, and usage scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits Windows bias primarily in the section addressing NFS access from Windows clients. Only Windows-specific tools (PowerShell, Windows mount command) and examples are provided for troubleshooting performance issues, with no equivalent Linux guidance. Additionally, the Windows example appears before or instead of any Linux example, and there is an absence of Linux troubleshooting steps for similar scenarios.

Recommendations:

For each Windows-specific example (such as enabling CaseSensitiveLookup or mounting NFS volumes), provide equivalent Linux commands and troubleshooting steps (e.g., using mount options or sysctl settings on Linux).
When discussing client-side configuration or troubleshooting, present both Windows and Linux examples side by side, or alternate which platform is presented first to avoid implicit prioritization.
Include Linux-specific tools or commands (such as mount, nfs-utils, or relevant sysctl parameters) wherever Windows tools are mentioned.
Review the documentation for other sections where only Windows client behavior is discussed and add Linux client guidance where applicable.
Explicitly state when an issue or solution is platform-specific, and clarify if the guidance applies to both Windows and Linux clients.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a strong Windows bias. All examples, terminology, and troubleshooting steps are centered on Windows environments, tools, and protocols (e.g., MMC, Active Directory, Windows Server, UNC paths). There are no Linux or non-Windows client examples, nor is there mention of Linux tools or workflows for accessing or managing SMB shares. The documentation assumes the reader is operating in a Windows-centric environment.

Recommendations:

Add examples and guidance for accessing Azure NetApp Files SMB shares from Linux clients (e.g., using smbclient, mount.cifs, or gvfs).
Include troubleshooting steps and best practices for Linux SMB clients, such as handling authentication, mounting shares, and dealing with file locking or permissions.
Mention Linux-compatible tools (e.g., Samba utilities) alongside Windows tools like MMC.
Clarify any differences or limitations when using SMB with Linux clients, such as supported SMB versions, authentication methods, or feature parity.
Provide sample configuration snippets for Linux (e.g., /etc/fstab entries, smb.conf settings) where appropriate.

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 and workflows (such as Event Viewer, MMC, and PowerShell) for administration and troubleshooting, and providing detailed steps and examples for Windows environments before (or instead of) Linux equivalents. There is a lack of Linux-specific administrative guidance, troubleshooting steps, and examples, especially for common Kerberos and LDAP operations from Linux clients.

Recommendations:

Explicitly acknowledge the lack of support for non-Windows KDCs and provide guidance for integrating Linux clients with Windows AD in Kerberos scenarios.
Add Linux-focused administrative examples, such as using kinit, klist, ktutil, and editing krb5.conf, for Kerberos troubleshooting and configuration.
Include Linux command-line examples for viewing and managing SPNs (e.g., using ldapsearch, msktutil, or adcli), and for mounting NFS shares with Kerberos.
Provide troubleshooting steps and log file locations for Kerberos issues on Linux clients (e.g., /var/log/secure, journalctl, etc.), not just references to Windows Event Viewer.
When describing workflows or tools (e.g., managing SPNs, viewing tickets), present both Windows and Linux methods side by side, or at least mention Linux alternatives.
Clarify that while only Windows AD is supported as a KDC, Linux clients are fully supported for NFS Kerberos, and provide best practices for their configuration.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively describing the process of configuring asymmetric name mapping using the Windows-only 'Active Directory Users and Computers MMC' tool, with no equivalent instructions for modifying LDAP attributes on Linux or non-Windows platforms. The workflow and screenshots are Windows-centric, and Linux is only shown as a consumer (verifying the mapping), not as an administrative platform.

Recommendations:

Provide equivalent instructions for modifying LDAP user attributes using common Linux tools (e.g., ldapmodify, Apache Directory Studio, or command-line LDAP utilities).
Include Linux-based examples and screenshots for updating the UID attribute in LDAP.
Present both Windows and Linux workflows in parallel, or at least mention Linux alternatives before or alongside Windows tools.
Clarify that the process can be performed from non-Windows environments and link to relevant Linux LDAP administration documentation.

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 presented exclusively in the context of Microsoft Active Directory, using Windows-specific tools such as ADSI Edit. There are no examples or guidance for equivalent operations in common Linux LDAP servers (e.g., OpenLDAP), nor is there mention of Linux-native tools or configuration patterns. The attribute mapping table and performance discussion are also framed around Windows defaults and behaviors, with no Linux parity.

Recommendations:

Add equivalent examples and instructions for configuring LDAP schema attributes and indexing in popular Linux LDAP servers such as OpenLDAP.
Include Linux command-line examples (e.g., using ldapmodify, slapd.conf, or olcAttributeTypes) for schema and index management.
Present attribute mapping and schema explanations in a platform-neutral way, or provide parallel sections for both Windows/Active Directory and Linux/OpenLDAP environments.
Mention Linux tools (such as ldapsearch, ldapmodify, or phpldapadmin) alongside Windows tools like ADSI Edit.
Clarify any differences in default attribute indexing and schema handling between Active Directory and Linux LDAP servers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a strong Windows bias by exclusively referencing Microsoft Active Directory as the supported LDAP server, focusing on Windows-centric LDAP schema extensions, and providing command-line examples (e.g., nslookup) in Windows syntax before mentioning Linux alternatives. There is a lack of Linux-specific configuration guidance or parity in examples, and Linux/UNIX LDAP servers (such as OpenLDAP) are not discussed as supported or referenced for integration.

Recommendations:

Explicitly mention the lack of support for non-Active Directory LDAP servers (e.g., OpenLDAP) and, if possible, provide a roadmap or alternatives for Linux environments.
Provide Linux/UNIX command-line examples (e.g., using dig, ldapsearch) alongside or before Windows examples when demonstrating LDAP/DNS queries.
Include guidance or references for managing UNIX attributes in Active Directory from Linux clients or tools, not just Windows-based schema extensions.
Clarify any limitations or workarounds for Linux/UNIX administrators who may need to integrate with Azure NetApp Files in mixed environments.
Where possible, use neutral language and ordering (e.g., 'nslookup (Windows) or dig (Linux)') to avoid Windows-first presentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing Azure PowerShell commands as the primary example for feature registration, mentioning Azure CLI as an alternative only after the PowerShell examples. There are no explicit Linux or cross-platform shell examples, and the UI instructions reference right-click actions, which are more common in Windows interfaces. No Linux-specific tools or command-line workflows are highlighted.

Recommendations:

Provide Azure CLI examples alongside or before PowerShell examples, especially for registration steps, to ensure parity for Linux and macOS users.
Include explicit Linux/macOS shell command examples (e.g., bash) where applicable.
Clarify that Azure CLI commands work cross-platform and are often preferred for automation on Linux/macOS.
When describing UI actions, avoid Windows-centric terminology like 'right-click' or provide alternative instructions for users on different platforms or with accessibility needs.
Add a section or note highlighting cross-platform management options, including links to relevant CLI documentation for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing SMB (a Windows protocol) and its SID format before or more prominently than NFS (a Linux/UNIX protocol) in quota target instructions. There are detailed instructions and examples for SMB (Windows) SID formats, but no equivalent command-line or practical examples for Linux/NFS environments. The documentation also lacks any CLI or shell-based examples for Linux users, focusing exclusively on the Azure Portal UI, which may be more familiar to Windows administrators.

Recommendations:

Provide equivalent command-line examples for managing quotas using Linux/NFS tools (e.g., show how to retrieve user/group IDs on Linux).
When mentioning SMB SID formats, also provide explicit examples for NFS (UID/GID) and clarify the mapping between Windows and Linux identities.
Include screenshots or walkthroughs for Linux/NFS environments, not just the Azure Portal UI.
Ensure that Linux/NFS terminology and workflows are given equal prominence and are not always listed after Windows/SMB examples.
Consider adding a section or appendix specifically for Linux/NFS administrators, outlining best practices and common tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-based tools and workflows. PowerShell commands are given as the primary example for feature registration, and the detailed steps for setting SACLs are exclusively for Windows administration hosts using GUI tools. In contrast, Linux/NFSv4.1 instructions are minimal and redirect to another page, with no direct command-line or workflow examples provided in this document. There are no Linux shell or CLI-based examples for managing file access logs or ACLs directly.

Recommendations:

Provide Linux shell (bash) and Azure CLI examples alongside PowerShell for feature registration and status checking.
Include step-by-step instructions for setting Audit ACEs on NFSv4.1 exports directly in this document, using common Linux tools (e.g., nfs4_setfacl).
Ensure that Linux/NFS workflows are described with equal detail as Windows/SMB workflows, including both GUI and command-line options where applicable.
When listing protocols or tools, avoid always mentioning Windows/SMB first; alternate or present both equally.
Add screenshots or terminal output examples for Linux-based operations, similar to those provided for Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes Windows-based tools and workflows (Windows Explorer, Microsoft Management Console) for managing SMB share ACLs in Azure NetApp Files. There are no examples or instructions for performing these tasks from Linux or cross-platform tools, and Windows tools are mentioned first and exclusively throughout.

Recommendations:

Add equivalent instructions for viewing and managing SMB share ACLs from Linux systems, using tools such as smbclient, smbcacls, or other Samba utilities.
If certain operations are only possible from Windows, clearly state this limitation at the beginning of the documentation.
Consider including PowerShell and command-line examples for Windows, as well as CLI-based alternatives for Linux where possible.
Provide a summary table comparing available management options for both Windows and Linux clients.
Reference or link to any relevant cross-platform or REST API methods (if available) for managing SMB share ACLs.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on Active Directory (a Windows technology) and references Windows-centric tools, terminology, and patterns (e.g., Group Policy, 'Active Directory Sites and Services', 'NTFS permissions', 'SMB', 'Kerberos', 'LDAP', 'OU=Computers', 'SeSecurityPrivilege', SQL Server). There are no Linux command-line examples, nor are Linux/Unix tools or patterns (such as Samba, sssd, or Linux-specific LDAP/Kerberos configuration) mentioned. The documentation assumes a Windows administrative environment and does not address Linux-based integration or management scenarios.

Recommendations:

Add Linux/Unix-focused examples for integrating Azure NetApp Files with Active Directory, such as configuring sssd, winbind, or Samba for NFS and SMB access.
Include references to Linux tools and configuration files (e.g., /etc/krb5.conf, /etc/sssd/sssd.conf) where relevant.
Provide parity in instructions for both Windows and Linux administrators, including how to manage Kerberos, LDAP, and SMB integration from Linux systems.
Mention Linux equivalents for concepts like 'Group Policy' (e.g., using sssd or pam_ldap for policy enforcement) and 'NTFS permissions' (e.g., POSIX ACLs or NFSv4 ACLs).
Clarify when features or settings are relevant to both Windows and Linux clients, and provide guidance for mixed-environment deployments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page focuses exclusively on NTFS ACLs and references Microsoft/Windows-specific concepts and documentation. There are no examples or mentions of managing SMB permissions from Linux or cross-platform tools, nor is there guidance for Linux administrators. The only external link is to a Microsoft Windows security page, reinforcing a Windows-centric perspective.

Recommendations:

Include examples or references for managing SMB file permissions from Linux clients, such as using the 'smbcacls' or 'setfacl' tools.
Mention cross-platform SMB management tools and how Linux/Unix administrators can interact with NTFS ACLs on Azure NetApp Files.
Provide links to relevant Linux documentation or community resources for SMB/NTFS ACL management.
Clarify whether and how Linux clients can view or modify NTFS ACLs on Azure NetApp Files SMB volumes.
Balance the documentation by addressing both Windows and Linux administrator workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ 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 equivalents are described more abstractly and without visual aids or command examples. There are no Linux (e.g., chmod, setfacl) command-line examples or screenshots, and the explanation of NFS inheritance is less actionable.

Recommendations:

Provide equivalent Linux/NFS command-line examples (e.g., using chmod, setfacl, or nfs4_setfacl) for managing file permissions and inheritance.
Include screenshots or step-by-step instructions for configuring NFSv4.1 ACL inheritance, similar to the Windows example.
Present SMB and NFS instructions in parallel structure, ensuring neither platform is consistently prioritized.
Expand the explanation of NFS permission inheritance with practical examples and common Linux administration patterns.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in the SMB section by exclusively referencing Windows tools (e.g., MMC console, Windows Explorer, 'net view') for managing and viewing SMB share permissions. There are no examples or instructions for managing SMB shares or permissions from Linux or macOS clients. The documentation also describes SMB share enumeration and access scenarios solely from a Windows perspective, with screenshots and workflows based on Windows environments. NFS sections are platform-neutral, but SMB sections lack Linux parity.

Recommendations:

Include instructions or examples for managing SMB share permissions from Linux clients, such as using smbclient, mount.cifs, or setfacl.
Provide screenshots or command-line examples for accessing SMB shares and viewing permissions from Linux or macOS systems.
Mention Linux/macOS tools (e.g., Nautilus, Dolphin, Finder, smbclient) alongside Windows tools when describing how to browse or mount SMB shares.
Clarify that SMB shares can be accessed and managed from non-Windows clients and provide relevant guidance.
Balance the order of presentation so that Linux and Windows tools are introduced together, or alternate which platform is mentioned first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation generally presents Windows/SMB concepts and tools before or with more detail than Linux/NFS equivalents. Windows terminology (e.g., NTFS, SID, NTLM) is explained in depth, while Linux/UNIX-specific tools and configuration examples are minimal or absent. Official support is emphasized for Windows and macOS SMB clients, but Linux SMB (Samba) is mentioned as unsupported, with no guidance or examples. There are no Linux command-line examples for NFS or SMB usage, and Windows-centric patterns (Active Directory, NTFS ACLs) are foregrounded.

Recommendations:

Provide Linux command-line examples for both NFS and SMB (e.g., show how to mount NFS and SMB shares from Linux clients, including required packages and configuration).
Include parity in tool references: if referencing Windows tools (e.g., NTFS, SID, NTLM), also reference and explain Linux/UNIX equivalents (e.g., POSIX ACLs, UID/GID, Kerberos setup on Linux).
Offer troubleshooting tips and configuration steps for Linux clients (e.g., Samba configuration for SMB, idmapd.conf for NFSv4, LDAP integration).
Clarify the support status for Linux SMB clients and provide best-effort guidance or links to community resources.
Balance the order of presentation so that Linux/NFS and Windows/SMB are treated equally, or alternate which is presented first in each section.
Add explicit Linux-focused 'Next steps' or quickstart links, similar to those for Windows/SMB.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Microsoft Active Directory as the LDAP implementation, using Windows-centric terminology and tools (such as ldp.exe), and providing only Windows-based examples and screenshots. There are no examples or instructions for equivalent Linux/OpenLDAP environments, nor are Linux tools or patterns mentioned. The documentation assumes a Windows/AD context for LDAP group management, which may not be applicable to organizations using Linux-based LDAP servers.

Recommendations:

Include equivalent examples and screenshots for Linux/OpenLDAP environments, such as using ldapsearch or other standard Linux LDAP tools.
Mention and explain how supplemental groups and GID management work in non-Active Directory LDAP servers.
Provide instructions or references for modifying group membership and LDAP attributes in Linux/OpenLDAP, not just in Windows/AD.
Balance the order of presentation so that Linux/OpenLDAP approaches are described alongside or before Windows/AD approaches where possible.
Reference Linux documentation and tools (e.g., openldap, nslcd, sssd) in addition to Microsoft tools.
Clarify when a feature or limitation is specific to Active Directory versus generic to LDAP or NFS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. Windows tools and concepts (such as NTFS, volume shadow copies, and Windows Server striped volumes) are mentioned alongside or before Linux equivalents. In the 'Next steps' section, Windows-specific guidance ('Creating striped volumes in Windows Server') is listed before Linux-specific content, and there is no direct example or link for Linux disk striping (e.g., using LVM or mdadm). While Linux is referenced (e.g., Ubuntu VMs, XFS, LVM), explicit Linux command examples or links to Linux disk striping documentation are missing, and Windows terminology appears more frequently or is prioritized.

Recommendations:

Add explicit Linux disk striping examples and documentation links (e.g., guides for LVM or mdadm) in the 'Next steps' section, ideally placed before or alongside Windows equivalents.
When discussing file system freeze/snapshot operations, provide equal detail for Linux (e.g., xfs_freeze, LVM snapshots) as for Windows (NTFS, VSS).
Ensure that Linux tools and patterns are mentioned with equal prominence and detail as Windows tools throughout the document.
Include example commands or configuration snippets for both Linux and Windows where relevant (e.g., how to stripe disks, monitor performance, or perform snapshots).
Review the order of presenting Windows and Linux content to avoid consistently listing Windows first, which can reinforce perceived bias.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is largely platform-neutral in its narrative, but there are subtle biases favoring Windows/Azure-native paradigms. While the article focuses on Oracle on Azure NetApp Files (which is inherently cross-platform), it assumes familiarity with Azure-specific tooling and does not provide Linux-specific or cross-platform command-line examples except in the context of network interface validation. There is a lack of explicit Linux administration examples (e.g., for mounting, automation, or troubleshooting), and Azure/Windows-centric tools and patterns are mentioned without always offering Linux alternatives or parity.

Recommendations:

Provide explicit Linux and cross-platform examples for common administrative tasks (e.g., mounting NFS volumes, validating network performance, troubleshooting).
When referencing Azure-native tools or patterns, also mention or link to equivalent Linux-native tools or open-source alternatives where applicable.
Ensure that automation and scripting examples (e.g., for deployment, configuration, validation) are shown for both PowerShell and Bash/shell, or clarify when Bash/Ansible is used.
Highlight any differences or special considerations for Linux environments, especially in areas like network configuration, performance tuning, and monitoring.
Include troubleshooting steps and diagnostic commands for both Windows and Linux environments to ensure parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows environments in several ways. While the content is largely cross-platform in its conceptual explanations, practical configuration and deployment instructions (especially for enabling CORS and authentication) reference the Azure portal UI and features that are only available or fully functional on Windows or in the Windows Consumption plan. There are no explicit Linux or CLI-based examples for configuring CORS or authentication, and a note explicitly states that CORS configuration is not available in the Azure Functions Linux Consumption plan, without offering a Linux-native alternative. All code samples are in C# (a Microsoft-centric language), and there are no shell, Bash, or cross-platform CLI examples for local development or deployment. The documentation assumes use of the Azure portal (a GUI tool), which is more common in Windows workflows, and does not provide parity for Linux command-line users.

Recommendations:

Provide Azure CLI and/or Azure PowerShell examples for all configuration steps (such as enabling CORS, setting authentication, and deploying functions), ensuring that Linux users can follow along without needing the Azure portal.
Explicitly address Linux Consumption plan limitations by offering alternative solutions or workarounds, such as using Azure API Management or Azure CLI scripts, and link to relevant documentation.
Include examples in additional languages (such as JavaScript, Python, or Bash) where appropriate, especially for local development and deployment scenarios.
Add a section or callouts for Linux/macOS users, highlighting any differences in workflow or configuration, and ensure that all instructions are cross-platform where possible.
When referencing configuration files (like local.settings.json), clarify any OS-specific paths or environment variable differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_heavy_context

Summary:

The documentation page demonstrates a Windows-centric bias in its discussion of SMB support in Azure NetApp Files. The content and examples are almost exclusively focused on Windows environments, tools, and semantics (e.g., NTFS, Active Directory, Hyper-V, MS SQL Server, Windows client behaviors), with little to no mention of Linux or macOS SMB client usage, configuration, or differences. Linux-specific SMB client considerations, tools, or configuration steps are missing, and Windows terminology and tools are referenced first or exclusively throughout.

Recommendations:

Add examples and explanations for configuring and accessing Azure NetApp Files SMB shares from Linux and macOS clients, including common tools (e.g., smbclient, mount.cifs) and authentication considerations.
Include a section comparing Windows and Linux SMB client behaviors, especially for features like file permissions, symbolic links, and delete semantics.
Mention Linux/UNIX equivalents when referencing Windows tools or features (e.g., explain how 'share permissions' or 'offline files' map to Linux clients, or note differences).
Provide guidance on troubleshooting SMB access from non-Windows clients, including common error messages and solutions.
Reference Linux documentation or man pages where appropriate (e.g., for smb.conf, mount.cifs, or Kerberos configuration on Linux).
Clarify when features or limitations are specific to Windows clients versus cross-platform SMB clients.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. In sections describing how to create and manage snapshots, Windows tools (PowerShell) are mentioned explicitly and often listed before or alongside cross-platform tools, but there is no mention of Linux/Unix-specific tools or command-line examples (such as Bash scripts or Linux CLI usage). There are no Linux/Unix-specific usage patterns or examples, and the scripting example provided is linked to a SQL Server (a Windows-centric workload) scenario. The documentation does not provide parity in examples or tool references for Linux users.

Recommendations:

Include explicit Linux/Unix command-line examples (e.g., Bash scripts using Azure CLI) for creating, managing, and restoring snapshots.
When listing tools, alternate or randomize the order of Azure CLI and PowerShell, or list Azure CLI first as it is cross-platform.
Provide example scripts for both PowerShell and Bash to demonstrate parity.
Reference Linux/Unix workloads and use cases (e.g., restoring files from NFS volumes using Linux commands) alongside Windows/SMB examples.
Ensure that links to scripting examples include both Windows and Linux scenarios.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exclusively discusses SQL Server deployment scenarios, performance, and benchmarking in the context of Windows environments. There are no references to Linux-based SQL Server deployments, Linux tools, or cross-platform considerations. All examples, performance metrics, and tooling (such as SSB and perfmon) are implicitly or explicitly Windows-centric. The 'Next Steps' section also only references SMB (a Windows-native protocol), with no mention of NFS or Linux-based workflows.

Recommendations:

Include explicit mention of SQL Server on Linux as a supported scenario for Azure NetApp Files, if applicable.
Provide performance and cost analysis examples for SQL Server running on Linux VMs, including relevant VM series and storage configurations.
Reference Linux-native benchmarking and monitoring tools (e.g., iostat, sysstat, sar) alongside or instead of Windows tools like perfmon.
Add guidance or links for creating NFS volumes and connecting them to Linux-based SQL Server deployments.
Ensure that all diagrams, benchmarks, and configuration examples include both Windows and Linux perspectives where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation lists a variety of tools for Azure NetApp Files, but the only automation example provided is ANFHealthCheck, which is explicitly described as a PowerShell runbook. There are no equivalent Linux/bash examples or mentions of cross-platform automation tools. This suggests a bias toward Windows and PowerShell environments, with a lack of parity for Linux users.

Recommendations:

Provide equivalent Linux/bash or cross-platform automation examples for tools like ANFHealthCheck.
Mention or link to Linux-compatible alternatives or scripts where PowerShell is referenced.
Explicitly state platform compatibility for each tool, clarifying if they are Windows-only, Linux-only, or cross-platform.
Add examples or documentation for using these tools in Linux environments, especially for monitoring and automation tasks.
Encourage contributions or community solutions for Linux users if official tools are not yet available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-centric bias. It consistently references Windows tools (such as 'Active Directory Sites and Services'), provides step-by-step instructions and screenshots for Windows GUI utilities, and describes AD DS concepts and operations primarily from a Windows Server perspective. While Linux client authentication via Kerberos is mentioned, there are no Linux-specific configuration examples, tools, or screenshots. The documentation assumes familiarity with Windows administration and omits equivalent Linux-based approaches for managing AD DS integration or site topology.

Recommendations:

Provide Linux-based examples for AD DS integration, such as using Samba tools (e.g., samba-tool, net ads) for site discovery and domain controller management.
Include command-line examples for querying DNS SRV records and validating AD DS connectivity using Linux utilities (e.g., dig, host, kinit, ldapsearch).
Offer guidance or references for managing AD DS from Linux environments, such as using RSAT alternatives or open-source LDAP management tools.
Balance screenshots and step-by-step instructions by including both Windows and Linux workflows where applicable.
Clarify that while the Windows GUI tools are commonly used, equivalent operations can be performed from Linux systems, and provide links or instructions for those workflows.

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: troubleshooting steps and error messages are predominantly focused on SMB and Active Directory scenarios, which are Windows-centric. PowerShell commands are provided for AD configuration, but equivalent Linux/Unix commands or tools are not mentioned. In dual-protocol and NFS sections, while some Linux-specific instructions are present (such as using kinit and systemctl), Windows/AD/SMB issues are discussed first and in greater detail. There is a lack of parity in providing Linux/Unix troubleshooting examples, especially for NFS-only or LDAP-only environments.

Recommendations:

Provide Linux/Unix command-line examples (e.g., using ldapsearch, klist, systemctl, or nfsstat) alongside or before Windows/PowerShell examples.
Include troubleshooting steps for common Linux/Unix NFS and LDAP scenarios, such as checking mount options, verifying Kerberos tickets, or inspecting /etc/krb5.conf and /etc/hosts.
Balance the order of presentation: do not always list Windows/SMB/AD errors and solutions before Linux/NFS/LDAP ones; consider grouping by protocol or alternating order.
Where PowerShell or Windows AD tools are referenced, add equivalent Linux/Unix commands (e.g., samba-tool, kadmin, or openldap utilities) for managing Kerberos and LDAP.
Expand on Linux-specific troubleshooting for dual-protocol and NFSv4.1 Kerberos volumes, including more detailed steps for debugging on Linux clients.

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/SMB and Active Directory scenarios, referencing Windows-specific tools and features (such as Group Policy, registry settings, and Microsoft advisories), and omitting Linux or non-Windows client configuration examples. SMB encryption and UNC hardening are discussed in depth, with references to Windows documentation and tools, while NFS/Kerberos and LDAP sections lack equivalent Linux-focused guidance or examples. There are no Linux command-line or configuration examples, and Windows terminology and tools are mentioned first or exclusively in several sections.

Recommendations:

Add Linux/NFS client configuration examples for enabling and verifying Kerberos encryption, including relevant commands (e.g., mount options, krb5.conf settings).
Provide equivalent Linux LDAP client configuration steps for LDAP signing and StartTLS, including example commands and configuration file snippets.
Balance the order of presentation so that NFS/Linux and SMB/Windows scenarios are given equal prominence, or alternate which is presented first.
Reference Linux documentation and tools (e.g., sssd, nsswitch, OpenLDAP, MIT Kerberos) alongside Windows tools like Group Policy.
Include troubleshooting steps and best practices for both Windows and Linux environments.
Where screenshots or packet captures are shown, provide examples from both Windows and Linux clients 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 prioritizing Windows/SMB path length details, providing extensive instructions and screenshots for Windows-specific configurations (such as registry edits and Group Policy), and referencing Windows tools and error dialogs. Linux/NFS sections are present but less detailed, with fewer practical examples and no equivalent visual aids or troubleshooting steps. Linux tools are mentioned only in the context of character byte size calculation, not for path length management or troubleshooting.

Recommendations:

Add equivalent Linux/NFS troubleshooting steps and error examples, such as common error messages and how to resolve them.
Include screenshots or terminal output for Linux/NFS path length errors, similar to the Windows dialog screenshots.
Provide Linux-specific guidance for extending or querying path limits, such as relevant sysctl settings or mount options, if applicable.
Balance the order of presentation: introduce NFS/Linux and SMB/Windows path limits in parallel, rather than focusing on Windows first.
Reference Linux documentation or tools (e.g., getconf, limits.h) more prominently and provide practical usage scenarios.
Offer parity in practical examples, such as how to map NFS mounts deeper into the directory structure to work around path length issues, similar to the SMB mapping workaround.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. Windows tools (Explorer, PowerShell, Notepad, Notepad++, chcp, Windows Terminal, PowerShell ISE) are frequently mentioned, often before or in more detail than their Linux equivalents. PowerShell and Windows-specific commands are shown for encoding conversion and file operations, while Linux examples are sometimes present but less detailed or introduced after Windows. Some sections (e.g., file encoding viewing/conversion) provide more step-by-step guidance for Windows than for Linux. The page also refers to Windows-specific behaviors (e.g., 8.3 filenames, region settings) in greater depth.

Recommendations:

Ensure Linux and macOS examples are provided alongside Windows examples for all key operations (e.g., file encoding conversion, viewing file encodings, troubleshooting).
Present Linux and Windows examples in parallel, or alternate which OS is presented first, to avoid a 'Windows-first' impression.
Expand Linux tool coverage: for example, show how to use Linux text editors (vim, nano, gedit) to view and change file encodings, and provide more details on Linux locale and font configuration.
Include more screenshots or command outputs from Linux terminals, not just Windows tools.
When referencing Windows-specific tools or settings (e.g., PowerShell ISE, chcp, region settings), provide equivalent Linux/macOS guidance (e.g., locale, iconv, file, terminal font settings).
Explicitly mention macOS behaviors where relevant, especially since it is referenced briefly but not covered in detail.
Balance troubleshooting advice and error message explanations for both Windows and Linux clients.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily Windows-centric, focusing exclusively on Windows Server DFS Namespaces (DFS-N), Windows AD, and Windows DNS management. All examples, instructions, and tooling references are for Windows GUI or PowerShell, with no mention of Linux equivalents or cross-platform alternatives. There are no Linux-based examples, and the documentation assumes a Windows-based infrastructure throughout.

Recommendations:

Acknowledge that DFS Namespaces is a Windows Server feature and clarify if there are any cross-platform alternatives or limitations.
If possible, mention or link to any open-source or Linux-compatible DFS-like solutions (e.g., Samba DFS, autofs, or other namespace/virtualization tools) and explain interoperability or lack thereof.
Provide guidance for Linux clients accessing DFS-N namespaces (e.g., using smbclient, cifs-utils, or mount.cifs), including sample commands for mounting DFS-N shares from Linux.
Clarify that management and configuration of DFS-N is only supported on Windows, but accessing shares may be possible from non-Windows clients, and provide relevant instructions.
Where DNS changes are required, include generic instructions or note how to perform similar steps using BIND or other non-Windows DNS servers.
Consider adding a section on limitations or considerations for mixed Windows/Linux environments, especially for organizations with heterogeneous infrastructure.

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 deployment examples and instructions, with no equivalent Azure CLI or Bash examples for Linux/macOS users. The 'Next steps' section also lists PowerShell-based management tasks before mentioning Azure CLI or REST API alternatives, reinforcing a Windows-first approach.

Recommendations:

Add Azure CLI deployment instructions and examples alongside the PowerShell example, ensuring parity for Linux/macOS users.
Include Bash shell command examples for template deployment, or explicitly mention cross-platform options.
In the 'Next steps' section, alternate the order of PowerShell and CLI/REST API links, or group them together to avoid implying a preferred platform.
Explicitly state that all deployment methods (PowerShell, CLI, portal, REST API) are supported and provide links or code snippets for each.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides detailed instructions for moving an Azure SignalR resource using the Azure portal and Azure PowerShell, but does not include equivalent examples for Linux or cross-platform command-line tools such as Azure CLI. The PowerShell section assumes a Windows environment (e.g., use of 'notepad'), and no Bash, Azure CLI, or Linux-native editor alternatives are mentioned. This creates a bias towards Windows users and omits guidance for Linux or macOS users.

Recommendations:

Add equivalent instructions using Azure CLI (az) for exporting, editing, and deploying ARM templates, as Azure CLI is cross-platform and widely used on Linux and macOS.
When referencing file editing, suggest cross-platform editors (e.g., 'nano', 'vim', 'code', or 'your preferred editor') instead of only 'notepad'.
Include Bash or shell command examples alongside PowerShell, especially for steps like file manipulation and deployment.
Structure the documentation so that cross-platform or platform-neutral approaches (like Azure CLI or portal) are presented before or alongside Windows-specific (PowerShell) instructions.
Explicitly state that the steps can be performed on any OS, and provide notes or links for Linux/macOS users where workflows or commands may differ.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ dotnet_heavy

Summary:

The documentation page demonstrates a Windows/.NET-first bias. The only detailed sample provided is a .NET console application, with C# code highlighted and step-by-step instructions tailored to Visual Studio-style workflows. There are no explicit Linux or cross-platform instructions, nor are there terminal/CLI-based examples for Linux users. While Java and JavaScript samples are linked, the walkthrough and code focus exclusively on .NET, which is most commonly associated with Windows environments.

Recommendations:

Add explicit Linux instructions for running the sample applications, including any prerequisites or environment setup (e.g., .NET Core on Linux, Java, Node.js).
Provide equivalent code walkthroughs for the Java and JavaScript samples, not just .NET/C#.
Include command-line examples using Azure CLI for authentication and role assignment, with sample commands runnable on Linux/macOS terminals.
Clarify that the .NET samples can be run cross-platform (if true), and provide instructions for doing so on Linux/macOS.
Balance the highlighted code and instructions so that Linux and non-Windows users are equally supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for Windows environments, such as creating a Windows VM, using RDP for access, and referencing Windows-specific quickstarts. There are no equivalent instructions or examples for Linux VMs or tools, and Linux users are not guided on how to perform the same tasks.

Recommendations:

Add parallel instructions for creating and configuring a Linux VM, including enabling managed identity.
Provide examples of accessing the VM and running the sample app using SSH and Linux command-line tools.
Include notes or sections that highlight any differences or additional steps required for Linux environments.
Ensure that sample code and build instructions are platform-agnostic or provide Linux-specific guidance where necessary.
Reference both Windows and Linux quickstart articles where available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates Windows bias by referencing deployment instructions that link directly to PowerShell-based guidance, omitting equivalent Linux/CLI examples. There is no mention of Linux tools or cross-platform Azure CLI commands for deploying the Resource Manager template, and the only explicit deployment path is via PowerShell, which is Windows-centric. No Linux or Bash shell examples are provided.

Recommendations:

Add explicit instructions and examples for deploying the Resource Manager template using Azure CLI (az deployment group create) and Bash shell, ensuring parity with PowerShell instructions.
Include links to both PowerShell and Azure CLI documentation for template deployment, making it clear that both Windows and Linux users are supported.
Wherever deployment steps are referenced, provide both PowerShell and Bash/Azure CLI command snippets side by side.
Review the documentation for other places where only Windows tools or workflows are mentioned, and add Linux equivalents as needed.

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 diagnostics and logs, with no equivalent examples for Azure CLI (cross-platform) or bash scripting. All automation and scripting instructions are presented in PowerShell syntax, which is native to Windows and less common on Linux systems. There is no mention of Linux, macOS, or cross-platform tooling, and no guidance for users who may be working from non-Windows environments.

Recommendations:

Add Azure CLI (az) command examples alongside PowerShell for all diagnostic and logging configuration steps. Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that all steps can be performed from Linux, macOS, or Windows using Azure CLI or the Azure portal.
Where scripting is shown, provide both PowerShell and bash (or shell-agnostic) script snippets.
Include a section or note for Linux/macOS users, highlighting any differences or confirming parity.
Review terminology to avoid implying PowerShell is the default or only automation method.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias towards Windows environments, particularly in the legacy ASP.NET SignalR section. It provides installation instructions using the Package Manager Console (PowerShell), references configuration via web.config (a Windows/IIS-centric pattern), and omits equivalent Linux-friendly instructions (such as using dotnet CLI or editing appsettings.json). There are no explicit Linux or cross-platform examples for setup or configuration, and Windows tools and patterns are assumed as defaults.

Recommendations:

Provide Linux/cross-platform installation instructions, such as using the dotnet CLI (e.g., 'dotnet add package') alongside or instead of PowerShell/Package Manager Console.
Include configuration examples using appsettings.json or environment variables, which are more common in Linux and containerized deployments, in addition to web.config.
Explicitly mention that the SDK and service are cross-platform, and clarify any OS-specific steps.
When referencing environment variables, provide both Windows and Linux syntax (e.g., 'set' vs 'export').
Avoid assuming the use of Windows/IIS-specific tools and patterns as the default; present cross-platform approaches first or in parallel.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing only Azure PowerShell CLI examples for automation, referencing the creation of a Windows virtual machine for validation, and omitting equivalent Linux/Bash/CLI instructions. The validation steps assume the use of Windows tools and environments, and there are no examples or guidance for Linux users.

Recommendations:

Provide equivalent Azure CLI (az) and/or Bash shell examples for all PowerShell automation steps, ensuring Linux and cross-platform users are supported.
Include instructions for creating and validating with a Linux virtual machine, not just Windows, in the validation section.
When referencing command-line tools (e.g., nslookup), clarify that the command works on both Windows and Linux, or provide both Windows and Linux command syntax/examples.
Avoid assuming the user is on Windows in validation and management steps; offer parity for Linux/macOS environments.
Explicitly mention cross-platform support and tools in the prerequisites and throughout the documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a bias toward Windows environments. Troubleshooting steps and examples are almost exclusively focused on ASP.NET/ASP.NET Core (C#), with no mention of Linux-specific tools or patterns. Diagnostic instructions reference Windows-centric tools (e.g., Fiddler, Performance Monitor), and debugging steps assume Visual Studio or Windows workflows. There are no Linux command-line or open-source alternatives provided, nor are there any Bash or Linux-native code/configuration samples.

Recommendations:

Add Linux-specific troubleshooting instructions, such as using curl, tcpdump, or Wireshark for network diagnostics.
Include examples of viewing logs and debugging on Linux (e.g., using journalctl, systemd, or dotnet CLI tools).
Mention cross-platform tools (e.g., Wireshark, mitmproxy) alongside or instead of Windows-only tools like Fiddler.
Provide code/configuration samples for Linux environments, such as configuring .NET Core apps on Linux, or using environment variables instead of web.config.
When listing tools or steps, present cross-platform or Linux-first options before or alongside Windows-specific ones.
Reference Linux container diagnostics more thoroughly, including commands and links to relevant documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation shows a mild Windows bias. In several places, Windows tools and patterns are mentioned first or exclusively, such as Fiddler for network tracing and web.config for logging. Linux alternatives are sometimes mentioned, but often as secondary options or without equal detail. Some logging/tracing instructions are Windows-specific or reference Windows-only platforms (e.g., Windows Phone 8). There is a lack of parity in examples and guidance for Linux environments.

Recommendations:

When listing tools for network tracing, present cross-platform options (e.g., tcpdump, Wireshark) before or alongside Windows-specific tools like Fiddler.
Provide explicit Linux and macOS examples for enabling server-side and client-side logging, not just web.config (which is Windows/IIS-centric). Include instructions for configuring logging in Linux deployments (e.g., using environment variables, appsettings.json, or systemd).
Avoid referencing Windows-only platforms (e.g., Windows Phone 8) without mentioning their irrelevance to Linux users or providing Linux/mobile alternatives.
Ensure all code/configuration snippets are applicable to both Windows and Linux, or provide parallel examples for each.
Where possible, use neutral language and tool ordering (e.g., 'To collect a network trace, you can use tcpdump (Linux/macOS), Wireshark (cross-platform), or Fiddler (Windows)').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented towards Windows development environments. It exclusively lists Windows tools (Visual Studio 2019), assumes the use of .NET Framework (not .NET Core/.NET 5+), and provides instructions only for Visual Studio and PowerShell. There are no examples or instructions for Linux users, such as using VS Code, JetBrains Rider, or command-line .NET CLI workflows. The documentation does not mention or provide parity for Linux or cross-platform development scenarios.

Recommendations:

Add instructions for setting up and running the sample using .NET Core or .NET 5+ on Linux and macOS, including using the dotnet CLI.
Include alternative development environments such as VS Code or JetBrains Rider, with relevant steps for Linux/macOS.
Provide Linux/macOS equivalents for package installation (e.g., using dotnet add package instead of only PowerShell/NuGet Package Manager).
Clarify which steps are Windows-specific and offer parallel guidance for non-Windows users.
Add troubleshooting notes or links relevant to Linux/macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ aspnet_heavy

Summary:

The documentation page demonstrates a bias towards Windows and Microsoft-centric development environments. It emphasizes ASP.NET Core and ASP.NET as the primary (and only) server-side frameworks, with no mention of Linux-based hosting, non-Microsoft server frameworks, or cross-platform development patterns. There are no Linux-specific examples, tools, or deployment scenarios, and the language suggests a Windows-first approach by focusing on technologies historically associated with Windows.

Recommendations:

Include explicit references to Linux hosting and deployment scenarios for SignalR Service.
Provide examples or links for using SignalR Service with non-ASP.NET server frameworks (such as Node.js, Java, or Python) and demonstrate cross-platform compatibility.
Mention and document how to run SignalR client and server applications on Linux, including any relevant command-line tools or patterns.
Balance the focus on ASP.NET by highlighting SDKs and integrations for other languages and platforms, and provide parity in documentation structure and examples.
Add a section or callout clarifying that Azure SignalR Service is fully supported and commonly used in Linux and cross-platform environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by focusing almost exclusively on Visual Studio (a Windows-centric IDE) for project creation, deployment, and publishing workflows. All step-by-step instructions and screenshots assume the use of Visual Studio GUI, with no mention of cross-platform alternatives such as Visual Studio Code or command-line publishing. There are no Linux/macOS-specific instructions or examples for development, deployment, or troubleshooting, and the only non-GUI example is the 'dotnet new' CLI command for project creation.

Recommendations:

Add explicit instructions and examples for Linux/macOS users, such as using Visual Studio Code or JetBrains Rider, and clarify that the .NET CLI works cross-platform.
Provide alternative publishing steps using the 'dotnet publish' command and Azure CLI for deployment, including sample commands.
Include screenshots or terminal output from Linux/macOS environments where appropriate.
Mention cross-platform editors and tools in the prerequisites section, and avoid assuming Visual Studio as the default development environment.
Add troubleshooting notes or links relevant to Linux/macOS users, such as permissions, environment variables, or common issues on those platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing SQL Server Management Studio (SSMS) and the New Subscription Wizard—both Windows-only tools—when describing how to configure replication. There are no explicit examples or instructions for performing these tasks on Linux, nor is there mention of Linux-specific tools or command-line workflows. The documentation assumes the use of Windows-based SQL Server instances and management tools, with no parity for Linux environments.

Recommendations:

Include explicit instructions and examples for configuring replication using command-line tools (e.g., sqlcmd) or scripts that work cross-platform, especially on Linux.
Mention and provide examples using Azure Data Studio, which is cross-platform, for relevant tasks.
Clarify which steps or tools are Windows-only and suggest Linux alternatives where possible.
Add a section or callout for Linux users, outlining any differences or additional steps required.
Ensure that all example commands and workflows are either cross-platform or have Linux equivalents provided.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell deployment instructions and examples, with no equivalent Azure CLI or Bash examples for Linux/macOS users. The prerequisites specifically mention installing the Azure PowerShell module, and the deployment workflow is described exclusively in terms of PowerShell commands. Azure CLI and Bash are only mentioned in passing in the 'Next steps' section, not in the main deployment flow.

Recommendations:

Add Azure CLI and Bash examples for deploying the Bicep/ARM template, alongside the PowerShell example.
In the prerequisites, mention both Azure PowerShell and Azure CLI as options for users, with installation links for each.
Present deployment instructions for both Windows (PowerShell) and Linux/macOS (Bash/CLI), or use a tabbed interface to allow users to select their preferred environment.
Ensure that all steps, including tracking and restoring backups, have parity between PowerShell and CLI/Bash instructions.
Avoid assuming the use of PowerShell or Windows-specific workflows as the default; instead, provide cross-platform guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong bias towards Windows environments by exclusively providing PowerShell-based automation examples and instructions. It references Azure PowerShell modules and scripts, assumes the use of .ps1 files, and does not mention or provide equivalent Bash, CLI, or cross-platform scripting alternatives. There is no guidance for Linux or macOS users, nor are there examples using the Azure CLI or other non-Windows-native tools. The documentation also refers to downloading and running PowerShell scripts, further reinforcing a Windows-centric approach.

Recommendations:

Provide equivalent examples using Azure CLI (az) commands and Bash scripts for all PowerShell-based instructions, especially for stopping and starting triggers.
Explicitly mention that Azure Pipelines agents can run on Linux and macOS, and provide guidance for those environments.
Include notes or sections for cross-platform compatibility, highlighting any differences or requirements for Linux/macOS users.
Where PowerShell scripts are referenced, offer Bash or shell script alternatives, or at least link to resources for non-Windows users.
Avoid assuming the use of .ps1 files and PowerShell modules as the only automation method; present Azure CLI as a first-class option.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides a generally cross-platform approach for Azure SQL Edge, with most local operations using Bash and Docker commands suitable for Linux environments. However, when demonstrating how to generate a SAS token for Azure Blob Storage, the only example provided is a PowerShell script using Azure PowerShell modules, which are primarily Windows-centric. There are no equivalent Bash/Azure CLI examples for Linux or macOS users. Additionally, the documentation consistently refers to connecting via SQL Server Management Studio (SSMS) before mentioning Azure Data Studio, which is more cross-platform, indicating a subtle 'windows_first' bias.

Recommendations:

Provide equivalent Bash/Azure CLI scripts for generating SAS tokens and managing Azure Storage, ensuring Linux and macOS users can follow along without needing PowerShell.
When listing tools for connecting to Azure SQL Edge, mention Azure Data Studio before SSMS or highlight its cross-platform nature.
Where possible, ensure that all code examples and instructions are available in both Windows (PowerShell/SSMS) and Linux/macOS (Bash/Azure CLI/Azure Data Studio) formats.
Add explicit notes or sections for Linux/macOS users, especially in areas where the workflow differs from Windows.

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 and Windows-centric tooling (e.g., .ps1 scripts, Azure PowerShell, ARMClient with Windows file paths), with no equivalent CLI/bash/Linux examples. Instructions for scripting, automation, and role assignment are exclusively shown using PowerShell, and the use of Windows file path conventions (e.g., C:\<filepath>) further reinforces the bias. There is no mention of Azure CLI, Bash, or Linux-native workflows, and the examples and screenshots assume a Windows environment.

Recommendations:

Provide equivalent Azure CLI (az) commands for all PowerShell examples, including role assignments, private endpoint creation, and DNS management.
Include bash script examples alongside .ps1 scripts, and use cross-platform file path conventions (e.g., /home/user/file.json) where appropriate.
Show how to upload and run scripts in the Azure Cloud Shell using both Bash and PowerShell environments.
Add explicit Linux/Unix workflow guidance for tasks such as managing DNS, running nslookup, and editing host files.
Ensure that screenshots and instructions reference both Windows and Linux environments where relevant.
Mention that all steps can be performed from Linux/macOS as well as Windows, and provide links to platform-agnostic tooling documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation 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. No Linux or cross-platform alternatives (such as Azure Data Studio or sqlcmd) are mentioned. Additionally, the checklist and summary sections both highlight SSMS as the connection tool, reinforcing the Windows-first perspective. There are no examples or instructions for connecting from Linux or macOS environments.

Recommendations:

Mention and provide examples for cross-platform tools such as Azure Data Studio and sqlcmd for connecting to Azure SQL Edge.
Update the checklist and summary sections to reference both SSMS and cross-platform alternatives, e.g., 'Connect with SSMS or Azure Data Studio'.
Include connection instructions and screenshots for Linux/macOS users, demonstrating parity with the Windows experience.
If possible, provide a table or section listing available client tools for different operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Azure Data Studio (a GUI tool most commonly used on Windows), using Microsoft SQL Server connection terminology, and omitting any Linux-specific instructions or command-line alternatives. There are no examples or guidance for connecting from Linux environments, nor are cross-platform tools or CLI methods mentioned.

Recommendations:

Include instructions for connecting to Azure SQL Edge using cross-platform command-line tools such as sqlcmd or Azure CLI.
Explicitly mention that Azure Data Studio is available on Linux and macOS, or provide alternative Linux-native tools.
Provide example commands for connecting from Linux terminals, including authentication and file path conventions.
Balance the documentation by listing Linux-compatible steps alongside Windows GUI steps, ensuring parity for users on all platforms.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows tools (Visual Studio 2019, Azure Data Studio), omitting Linux equivalents or alternatives. There are no command-line or cross-platform instructions for building, pushing, or deploying modules, nor are there examples using Linux-native editors or tools. The workflow assumes a Windows development environment and does not address Linux users' needs.

Recommendations:

Include instructions for building and pushing IoT Edge modules using cross-platform command-line tools such as Docker CLI and Azure CLI, with example commands for Linux.
Mention and provide examples for using VS Code (which is cross-platform) instead of or in addition to Visual Studio 2019.
Provide guidance for connecting to Azure SQL Edge using sqlcmd or Azure Data Studio on Linux, including installation and usage notes.
Ensure all UI navigation steps in the Azure Portal are clearly marked as browser-based and not OS-specific.
Add explicit notes or sections for Linux/macOS users, highlighting any differences or additional requirements.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows environments by exclusively referencing Windows tools (ODBC Driver 17 for SQL Server, Azure Data Studio), using Windows-style connection strings, and omitting any Linux-specific instructions or troubleshooting. There are no examples or notes for Linux users regarding driver installation, connection string differences, or alternative tools. The documentation assumes the reader is using Windows, which may hinder Linux users attempting the same workflow.

Recommendations:

Add explicit instructions for installing ODBC Driver 17 for SQL Server on Linux (e.g., Ubuntu, CentOS), including relevant package manager commands.
Mention that Azure Data Studio is cross-platform and provide download/installation links for Linux and macOS.
Provide Linux-specific connection string examples, noting any differences in driver naming or path syntax.
Include troubleshooting tips for common Linux issues (e.g., driver not found, permissions).
Clarify that the workflow is supported on both Windows and Linux, and ensure parity in setup and execution steps.
If any steps are Windows-only, clearly label them and offer Linux alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates subtle Windows bias by referencing Windows-specific tools and patterns before or instead of Linux equivalents. For example, the 'Client Network Configuration' link points to a Windows-specific page, and there are no Linux-specific client configuration instructions. Additionally, while there are some Linux references (e.g., encrypted connections), there are no explicit Linux command-line or configuration examples, and Windows terminology is used by default.

Recommendations:

Provide Linux-specific client configuration guidance and examples, such as how to configure client network settings on Linux.
Include Linux command-line examples (e.g., using sqlcmd or mssql-tools on Linux) alongside or before Windows examples.
When referencing configuration utilities or files, clarify the Linux equivalents and provide sample commands or file snippets.
Ensure that links and references are balanced between Windows and Linux, or provide parallel links for both platforms.
Review terminology to avoid defaulting to Windows-centric language (e.g., 'host computer' instead of 'host system').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by focusing on Azure Portal workflows and referencing PowerShell/CLI scripts for permissions, but does not provide explicit Linux command-line examples or mention Linux-native tools. The instructions and screenshots are oriented around GUI steps, which are more familiar to Windows users, and there is no mention of Linux-specific mounting, file system, or SAP HANA restore commands, despite SAP HANA on Azure VMs typically running on Linux.

Recommendations:

Add explicit Linux command-line examples for mounting and restoring disks/snapshots, such as using 'lsblk', 'mount', or SAP HANA's native tools (e.g., hdbsql, hdbbackupdiag).
Provide sample Bash scripts or CLI commands for common restore tasks, not just PowerShell or generic 'CLI script' references.
Include Linux-specific guidance for disk attachment and permissions, such as using 'az' CLI commands and Linux file system operations.
Clarify when steps are OS-agnostic versus when they require Windows or Linux-specific actions.
Add screenshots or terminal output examples from Linux environments to balance the visual bias toward Windows GUIs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a Windows bias by requiring a Windows computer for the Data Sync Agent, referencing only Windows-based tools (such as the Data Sync Agent and PowerShell), and omitting any mention of Linux or cross-platform alternatives. There are no instructions or examples for Linux users, nor is there guidance for running the Data Sync Agent or related tooling on Linux systems.

Recommendations:

Provide explicit guidance on whether the Data Sync Agent can be run on Linux (natively or via compatibility layers such as Wine or containers), or clarify its platform limitations.
Include Linux-based examples or alternatives for all steps, such as using Azure CLI or REST APIs where possible, instead of only PowerShell.
Mention any cross-platform data sync tools or approaches if available, or suggest workarounds for Linux users.
Clearly state platform requirements and, if Windows is mandatory, explain why and provide links to feature requests or roadmap items for Linux support.

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 automation and management tools, without mentioning or providing examples for Linux-based tools (such as Azure CLI or Bash scripting). The language and examples assume a Windows-centric workflow, and there are no Linux-specific instructions or parity in tool recommendations.

Recommendations:

Include Azure CLI and Bash examples alongside or before PowerShell examples for managing API Management resources.
Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) as alternatives to PowerShell and the Azure portal.
Add guidance or links for Linux users on how to perform equivalent management and automation tasks.
Review diagrams and workflow descriptions to ensure they do not implicitly assume a Windows environment or toolset.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows by exclusively referencing and providing examples for Windows-specific tools (such as SqlPackage.exe and SQL Server Management Studio), omitting Linux equivalents or cross-platform alternatives. There are no examples or instructions for performing the same tasks on Linux, and Windows tools are mentioned first and exclusively.

Recommendations:

Include instructions and examples for using cross-platform or Linux-native tools (e.g., sqlcmd on Linux, Azure Data Studio on Linux, or Docker CLI commands for interacting with SQL Edge containers).
Mention and provide download links for Linux-compatible versions of tools like SqlPackage (which is available for Linux) and show example commands for Linux shells (bash) alongside Windows (cmd).
Avoid referencing only Windows-specific tools (like SQL Server Management Studio) or, if referenced, clearly indicate their cross-platform alternatives and usage.
When providing command-line examples, offer both Windows (cmd/PowerShell) and Linux (bash) syntax.
Explicitly state that Azure Data Studio and sqlcmd are available on Linux and macOS, and provide relevant installation and usage instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by focusing exclusively on Azure portal and VMware vSphere UI workflows, which are typically more familiar to Windows administrators. There are no Linux-specific examples, command-line workflows (other than Azure CLI), or mentions of Linux guest management tools or patterns. The prerequisites and instructions assume VMware Tools (commonly associated with Windows VMs) and do not mention open-vm-tools or Linux-specific considerations.

Recommendations:

Include explicit Linux guest management examples, such as using open-vm-tools for Linux VMs.
Add command-line workflows for enabling guest management on Linux VMs, possibly referencing shell scripts or Linux CLI tools.
Mention Linux-specific requirements or troubleshooting steps, such as ensuring open-vm-tools is installed and running on Linux guests.
Provide parity in examples and screenshots for both Windows and Linux guest operating systems.
Clarify that the instructions apply to both Windows and Linux VMs, and highlight any differences in the process.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily Windows-centric, assuming Azure Backup Server is running on Windows. All instructions, screenshots, and procedures reference Windows UI elements, Windows tools (such as the Certificate Import Wizard and registry editing via .reg files), and Windows-specific recovery options. There are no Linux equivalents or alternative instructions for non-Windows environments, and the only individual file restore option is for Windows Server VMs.

Recommendations:

Provide equivalent instructions for Linux-based environments, if supported (e.g., importing certificates using Linux tools like openssl or update-ca-certificates).
Include command-line examples for certificate management and TLS configuration on Linux, if Azure Backup Server supports Linux.
Clarify early in the documentation whether Azure Backup Server is only available on Windows, and if so, suggest alternative backup solutions for Linux users.
If individual file restore is only available for Windows VMs, explicitly state this limitation and suggest workarounds or alternative tools for Linux VMs.
Where possible, use cross-platform terminology and avoid assuming the user is on Windows (e.g., avoid exclusive use of Windows UI screenshots and registry edits).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. It exclusively provides PowerShell-based automation scripts for deploying Azure resources, with no equivalent Bash or Linux shell examples. The prerequisites recommend Visual Studio 2019 (a Windows-centric IDE) and Azure PowerShell, and the deployment workflow is described only in terms of PowerShell scripts. While some steps use Azure CLI (which is cross-platform), these are embedded within PowerShell scripts, and there are no standalone Linux/Bash instructions. Linux users are left to adapt the instructions themselves.

Recommendations:

Provide equivalent Bash/Linux shell scripts for all deployment steps, especially for resource provisioning and automation.
List cross-platform tools (e.g., VS Code, Azure CLI) before or alongside Windows-specific tools like Visual Studio.
Clearly indicate which steps are cross-platform and which are Windows-only, and offer alternatives where possible.
Include a dedicated section or callouts for Linux/macOS users, ensuring parity in setup and deployment instructions.
Where PowerShell is used for automation, provide Bash alternatives or reference Azure CLI commands that can be run directly in a Linux shell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a subtle Windows bias: it uses Windows-centric terminology (e.g., 'command prompt'), references Windows-style paths (e.g., 'azurite\debug.log'), and assumes familiarity with Windows tools and conventions. While most commands are cross-platform, the order and phrasing often prioritize Windows users, and there is a lack of explicit Linux/macOS instructions or clarifications.

Recommendations:

Replace 'command prompt' with 'terminal' or 'command line' to be OS-neutral.
When showing file paths, use forward slashes (/) or provide both Windows (\) and Linux/macOS (/) examples.
Explicitly mention that all CLI commands work on Linux/macOS, and provide any OS-specific notes if needed.
For Azurite, show both Windows and Linux/macOS invocation examples (e.g., 'azurite -l azurite -d azurite/debug.log' for Linux/macOS).
If referencing environment variables or configuration files, clarify any OS-specific differences.
Add a note or section confirming that all steps are supported on Linux/macOS, and link to platform-specific setup guides if available.

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 terminology, prerequisites, and screenshots are centered around Windows environments, with no mention of Linux tools, patterns, or alternative directory services.

Recommendations:

Add parallel instructions and examples for configuring NSX with a Linux-based LDAP server such as OpenLDAP, including any necessary differences in configuration, certificate management, and user/group mapping.
Update prerequisites to mention that any LDAP-compliant directory (including Linux-based solutions) can be used, and provide links or references to relevant Linux documentation.
Include screenshots or command-line examples for Linux environments where applicable, such as generating certificates with OpenSSL or configuring OpenLDAP.
Clarify in notes or callouts that while Windows Server Active Directory is common, other LDAP servers are fully supported, and provide troubleshooting tips for non-Windows environments.
Balance the language throughout the documentation to avoid implying that Windows Server Active Directory is the only or default option.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides detailed PowerCLI (PowerShell-based) instructions for verifying DNS resolution, with no equivalent Linux or cross-platform CLI examples. All command-line verification is shown using PowerShell cmdlets, and there are no references to Linux-native tools or workflows. This creates a bias toward Windows environments and users familiar with PowerShell.

Recommendations:

Add equivalent Linux/Unix command-line examples for DNS verification, such as using nslookup or dig directly from a Linux shell.
Include instructions or examples for using REST API calls (e.g., via curl) to interact with the NSX-T Policy API, which would be platform-agnostic.
Mention and demonstrate how to perform DNS resolution checks from Linux-based VMs within the workload segments, using standard Linux tools.
Reorder or supplement the verification section so that Linux and Windows methods are presented with equal prominence.
Clarify that PowerCLI is not required for DNS verification and provide alternatives for users on non-Windows platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows environments, specifically Windows Server Active Directory. All examples, procedures, and screenshots assume the use of Windows tools (MMC, Windows certificate store, Windows domain controllers), and there are no examples or guidance for integrating non-Windows LDAP servers (such as OpenLDAP) or for performing tasks from Linux-based systems. The documentation does not mention or provide parity for Linux LDAP servers, tools, or workflows.

Recommendations:

Add explicit guidance and examples for integrating non-Windows LDAP servers (e.g., OpenLDAP, FreeIPA) as external identity sources for vCenter Server.
Include Linux-based procedures for exporting and managing LDAPS certificates (e.g., using openssl or certutil on Linux) alongside the Windows MMC-based instructions.
Provide example configurations and screenshots for Linux LDAP environments where applicable.
Clarify in the introduction and prerequisites that non-Windows LDAP sources are supported, and link to relevant documentation for those scenarios.
Ensure that terminology and instructions are not exclusively tied to Windows (e.g., avoid only referencing NetBIOS names or Windows-specific credential formats).

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-based management tool primarily associated with Windows-centric workflows) for credential management and configuration steps. There are no examples or instructions for performing equivalent tasks using Linux tools, command-line interfaces, or automation scripts (such as Azure CLI, PowerShell Core on Linux, or REST APIs). The documentation assumes a GUI-based, portal-driven workflow, which is more common in Windows environments, and omits any mention of Linux-based management or automation options.

Recommendations:

Include equivalent instructions for managing credentials, deploying OVAs, and configuring NSX/vCenter using command-line tools such as Azure CLI, VMware CLI tools (govc, ovftool), or REST APIs that are cross-platform.
Provide examples for downloading and transferring OVA files using Linux commands (e.g., wget, scp) in addition to or instead of GUI-based steps.
Mention and document how to perform key steps (such as enabling SSH, configuring static IPs, or managing firewall rules) using Linux shell commands or scripts.
Clarify that all steps can be performed from Linux, macOS, or Windows environments, and provide any OS-specific prerequisites or considerations.
Where screenshots are used, consider including CLI output or terminal screenshots from Linux environments to balance the visual representation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively uses PowerShell-style cmdlets (e.g., Get-StoragePolicy, Set-VMStoragePolicy) and the Azure portal 'Run command' interface, both of which are Windows-centric. There are no examples or instructions for performing these operations via Linux command-line tools, REST APIs, or cross-platform automation frameworks. The documentation assumes the use of Windows tools and patterns throughout, with no mention of Linux or cross-platform alternatives.

Recommendations:

Provide equivalent examples using cross-platform tools such as Azure CLI, REST API, or PowerCLI on Linux/macOS.
Explicitly mention whether the 'Run command' interface is accessible from non-Windows environments, and provide instructions if so.
Include bash or shell script examples where possible, or clarify if only Windows/PowerShell is supported.
Add a section or note addressing Linux/macOS users and guiding them to appropriate tools or interfaces.
Where screenshots are shown, consider including examples from non-Windows environments if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits a subtle Windows bias. While it lists Azure portal, PowerShell, and CLI as supported clients, PowerShell (a Windows-centric tool) is mentioned before CLI (which is more cross-platform and commonly used on Linux). There are no explicit Linux-specific examples, nor is there mention of Linux tools or workflows. The documentation focuses on Azure Virtual Machines, SQL Server, and SAP HANA in Azure VMs, but does not clarify support or workflows for Linux VMs or Linux-native backup scenarios. Screenshots and instructions appear to assume a Windows-centric environment.

Recommendations:

Explicitly include Linux VM backup scenarios and clarify parity with Windows VM support.
Provide CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
Add Linux shell (bash) command examples where relevant, especially for common operations.
Clarify that the Azure CLI is cross-platform and provide guidance for Linux users.
Include screenshots or instructions that are relevant to Linux environments (e.g., terminal usage, Linux file paths).
If certain features are Windows-only, clearly state this and provide alternative guidance for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by emphasizing Windows-specific security features (such as BitLocker and credential protection), mentioning Windows operating systems and tools before Linux, and omitting Linux-specific examples or guidance for using vTPM. While Linux is listed as a supported guest OS, there are no Linux-focused instructions or references to Linux security tooling or workflows.

Recommendations:

Include Linux-specific examples for configuring and using vTPM, such as enabling disk encryption with LUKS or using Linux attestation tools.
Mention Linux security features (e.g., Secure Boot with shim/grub, TPM-backed disk encryption, measured boot) alongside Windows features like BitLocker.
Provide parity in documentation by showing how vTPM benefits both Windows and Linux VMs, including references to Linux documentation or community best practices.
Avoid language that implies Windows is the primary or only use case (e.g., 'prevents malware from running on windows system'), and instead use OS-neutral phrasing or explicitly mention both Windows and Linux.

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 (e.g., Set-vSANDataInTransitEncryption), using Windows-centric terminology (e.g., Run command, Packages), and mentioning Windows Server Failover Clusters as a supported feature. There are no Linux or cross-platform command-line examples, nor are Linux tools or workflows mentioned. The documentation assumes the user is operating from a Windows environment, with no guidance for Linux or macOS users.

Recommendations:

Provide equivalent command-line examples for Linux (e.g., using VMware's CLI tools such as govc, or REST API calls via curl).
Mention and document how to perform the same operations from non-Windows environments, including macOS and Linux.
Clarify if the 'Run command' feature is accessible via cross-platform tools or only through the Azure Portal/PowerShell.
Include references to Linux-supported features or guest OS requirements, not just Windows (e.g., mention Linux guest support for TRIM/UNMAP).
Balance the mention of Windows Server Failover Clusters with information about clustering support for Linux-based workloads.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively using PowerShell cmdlets for all configuration tasks, referencing Windows VM hardware requirements before Linux, and omitting any Linux-native command-line or tool examples. The workflow assumes use of the Azure portal and Windows-centric tools, with no mention of Linux shell equivalents or cross-platform automation options.

Recommendations:

Provide equivalent Linux shell (bash/CLI) commands or scripts for each configuration task, where possible.
Mention and document cross-platform tools (such as VMware's govc CLI or REST APIs) that can be used from Linux environments.
When listing VM prerequisites, alternate or parallelize the order of Windows and Linux requirements to avoid always listing Windows first.
Clarify whether the cmdlets and portal workflows are accessible from Linux or require Windows, and provide alternatives if needed.
Include examples or links for automating these tasks from Linux-based CI/CD pipelines or management hosts.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Windows (PowerShell) and Linux (bash) examples for running the installation scripts, but the Windows example is presented first and includes more detailed instructions (such as bypassing execution policy). Additionally, Windows-style paths (e.g., C:\Users\sampleUser.sslProxy.crt) are used in JSON examples for proxy configuration, and there is a general tendency to mention Windows Server and SQL Server as primary use cases. There are no missing Linux examples, but the documentation subtly prioritizes Windows patterns and tools.

Recommendations:

Alternate the order of Windows and Linux examples or present them side-by-side to avoid implicit prioritization.
Use platform-agnostic file path examples in JSON snippets (e.g., /home/sampleUser/sslProxy.crt for Linux, or use placeholders).
Explicitly state that both Windows and Linux management VMs are equally supported, and provide parity in troubleshooting and configuration details.
Where possible, avoid Windows-specific terminology or provide equivalent Linux instructions (e.g., mention chmod and bash for Linux alongside Set-ExecutionPolicy for Windows).
Highlight Linux-based use cases (e.g., Linux VMs, Linux management hosts) in the benefits and deployment considerations sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows/Azure-centric bias. All operational examples and automation steps are presented using Azure Run Command and PowerShell/cmdlet syntax, with no mention of Linux CLI, shell scripts, or cross-platform alternatives. The documentation assumes use of the Azure portal and Windows-style automation, omitting any Linux-native or cross-platform command-line instructions. There are no examples or guidance for users who may wish to automate or interact with JetStream DR from Linux environments.

Recommendations:

Provide equivalent Linux shell (bash) or cross-platform CLI examples for all installation, configuration, and management steps, especially for JetStream DR deployment and management.
Document how to perform JetStream DR operations using REST APIs, if available, or via the vSphere CLI, to support automation from Linux or non-Windows environments.
Clarify whether the Azure Run Command and cmdlets can be invoked from Linux systems (e.g., via Azure CLI or REST), and provide explicit instructions for doing so.
Include references or links to JetStream DR documentation that covers Linux-based deployment and management, if available.
Add a section addressing cross-platform automation and scripting, highlighting any differences or requirements for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Microsoft IIS Servers as backend VMs, omitting any mention of Linux-based alternatives (such as Apache or Nginx). All backend pool examples and screenshots focus on IIS and Windows-centric tools. There are no Linux-specific instructions, examples, or validation steps, and the only server OS referenced is Windows. This may give the impression that only Windows workloads are supported or recommended.

Recommendations:

Include examples using Linux-based web servers (e.g., Apache, Nginx) as backend pool members alongside IIS.
Explicitly state that both Windows and Linux VMs are supported as backend pool members in Azure VMware Solution.
Provide screenshots or command-line examples (e.g., using curl or wget) for verifying endpoints from Linux hosts, not just browser-based validation.
Mention Linux administration tools or validation steps (such as using SSH to connect to Linux VMs) where appropriate.
Balance references to Windows and Linux in both prerequisites and step-by-step instructions to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Bash and Windows CMD examples for setting environment variables, but Bash (Linux/macOS) is shown first. There is no exclusive use of Windows tools or PowerShell, and all code samples and instructions are cross-platform. However, the documentation assumes the use of Azure CLI, which is available on all platforms, and does not rely on Windows-specific tools. The only minor bias is the inclusion of both Bash and CMD snippets, but not PowerShell, and the use of 'export' (Bash) before 'SET' (CMD), which slightly favors Linux/macOS. There is no evidence of missing Linux examples or exclusive mention of Windows tools.

Recommendations:

Ensure that PowerShell examples are included alongside Bash and CMD where relevant, especially for setting environment variables.
Explicitly state that all instructions are cross-platform and can be run on Linux, macOS, or Windows.
Where CLI commands are shown, clarify that they work in all supported shells (Bash, CMD, PowerShell) and provide examples for each if possible.
Consider adding a short section or note about how to adapt the instructions for different operating systems and shells, especially for environment variable management.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows-centric workflows and tools, specifically the Azure portal and VMware vSphere client interfaces, with no mention of Linux command-line alternatives or parity. All operational steps (installation, upgrade, uninstall, password reset) are described using GUI-based or Windows-style 'Run command' workflows, and there are no CLI or automation examples for Linux users. The documentation assumes the use of Windows-based management tools and does not address Linux-based administration or scripting.

Recommendations:

Provide equivalent Linux CLI examples for installation, upgrade, and uninstallation (e.g., using Azure CLI, PowerShell Core on Linux, or REST API calls).
Document how to perform these operations via automation or scripting for Linux administrators.
Clarify whether the 'Run command' functionality is accessible via cross-platform tools (e.g., Azure CLI, REST API) and provide usage examples.
Include notes or sections for Linux users, outlining any prerequisites or differences in workflow.
Ensure parity in screenshots and instructions for both Windows and Linux environments where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows environments, specifically Windows Server and Microsoft SQL Server Always On Availability Groups, which are only supported on Windows. All examples, prerequisites, and operational steps assume Windows Server Failover Clustering, with no mention of Linux-based SQL Server deployments or cross-platform considerations. Only Windows tools (SQL Server Management Studio, Windows Server Failover Cluster) are referenced, and all guidance is Windows-centric.

Recommendations:

Explicitly state that SQL Server Always On Availability Groups are only supported on Windows, and clarify if Linux-based SQL Server deployments are out of scope for this guide.
If Linux-based SQL Server high availability scenarios (such as Pacemaker clusters) are supported for migration to Azure VMware Solution, provide a parallel section or a separate guide for those scenarios.
Where possible, mention the existence of SQL Server on Linux and its clustering options, even if only to clarify their support status.
Include references or links to documentation for Linux-based SQL Server deployments and migration strategies, if applicable.
If the migration process is fundamentally different for Linux, provide clear guidance or a pointer to relevant resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows Server Failover Clustering and SQL Server on Windows, with all examples, screenshots, and instructions referencing Windows Server tools (e.g., Failover Cluster Manager, SQL Server Management Studio). There is no mention of Linux-based SQL Server clusters, Linux failover clustering solutions (e.g., Pacemaker), or migration steps for non-Windows environments. The prerequisites, migration steps, and troubleshooting are all tailored exclusively to Windows Server environments.

Recommendations:

Add a section or parallel guide for migrating SQL Server clusters running on Linux (e.g., using Pacemaker/Corosync or Linux-based Always On Availability Groups).
Include Linux-specific prerequisites, such as reviewing and recording Linux network/storage configuration, and backing up using Linux-native tools.
Provide migration steps and screenshots for Linux-based clusters, including relevant commands and tools (e.g., systemctl, pcs, SQL Server on Linux management tools).
Reference Linux documentation for SQL Server clustering and failover, and link to official Microsoft and VMware resources for Linux environments.
Clarify in the introduction that the current guide is Windows-specific, and direct Linux users to appropriate resources if a Linux parity guide is not yet available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows environments, specifically Windows Server and Microsoft SQL Server, with no mention of Linux-based SQL Server deployments or migration scenarios. All examples, prerequisites, and validation steps assume a Windows Server environment, and only Windows tools (e.g., SQL Server Management Studio) are referenced. There is no guidance for users running SQL Server on Linux or for Linux-based VM migrations.

Recommendations:

Include explicit mention of SQL Server on Linux as a supported scenario, if applicable.
Provide parallel migration steps and prerequisites for SQL Server instances running on Linux (e.g., Ubuntu, Red Hat).
Add examples and screenshots using Linux-based management tools (such as sqlcmd or Azure Data Studio) alongside Windows tools like SQL Server Management Studio.
Reference Linux documentation and best practices for SQL Server deployments and migrations.
Clarify any limitations or differences in the migration process for Linux-based SQL Server VMs.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting Azure PowerShell instructions before Azure CLI, which is more cross-platform. There are no explicit Linux/macOS-specific instructions or clarifications, and the PowerShell example assumes a Windows environment. The CLI example is present but not emphasized or explained in a Linux context.

Recommendations:

Present Azure CLI instructions before PowerShell, as CLI is cross-platform and works natively on Linux/macOS.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts (e.g., $) to reinforce this.
If PowerShell is included, clarify that PowerShell Core is available cross-platform, or provide equivalent Bash/shell examples where possible.
Add a note or section for Linux/macOS users, including any prerequisites or differences in experience (e.g., installation of Azure CLI, authentication methods).
Ensure that all tooling references (e.g., 'copy the value from the ID column') are not Windows-centric and clarify how to perform these steps in different environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by repeatedly highlighting PowerShell as a primary automation method and in example scenarios, often mentioning it before cross-platform tools like CLI or SDKs. There are no explicit Linux-specific examples, nor is Bash or Linux shell scripting referenced. The automation scenarios and sample workflows focus on PowerShell and Azure Automation Runbooks, which are traditionally more Windows-centric, with no parity examples for Linux users.

Recommendations:

Include explicit Linux/Bash shell examples alongside PowerShell in automation scenarios.
When listing automation methods, alternate or randomize the order of PowerShell and CLI, or list CLI first to avoid implicit prioritization.
Provide sample scripts or workflows using Azure CLI and Bash for each scenario described (e.g., configuring backups, exporting data, automating responses).
Highlight cross-platform SDKs (Python, Go) with code snippets or links to Linux-focused guides.
Mention and link to Linux automation tools (e.g., cron jobs, systemd timers) where appropriate, especially in sections discussing scheduling and monitoring.
Ensure that all referenced videos and tutorials have Linux/CLI equivalents or supplementary materials.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively references PowerShell cmdlets and Windows-centric tooling (e.g., 'Run Command' panel, cmdlet naming conventions), with no mention of Linux/Unix equivalents or CLI alternatives. All examples and instructions are tailored to a Windows/PowerShell environment, and there is no guidance for users who may prefer or require Linux-based management or automation.

Recommendations:

Provide equivalent command-line examples using Bash or other Linux shells, if available.
Clarify whether the Run Commands can be invoked via Azure CLI, REST API, or other cross-platform tools, and provide usage examples.
Explicitly state if PowerShell is required, or if there are alternative methods for Linux users.
Include references to Linux-compatible tools or scripts for managing VMware HCX in Azure VMware Solution.
Ensure that documentation sections and examples are balanced, presenting both Windows and Linux approaches where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows bias. All backend VM configuration examples use Windows Server 2016 with IIS, and only PowerShell commands are provided for web server setup. There are no Linux-based examples or references to Linux tools (such as Apache or Nginx), and no Bash or shell commands are shown. The documentation implicitly assumes a Windows environment for web hosting, omitting Linux alternatives entirely.

Recommendations:

Add parallel Linux-based examples for backend web server setup, such as using Ubuntu VMs with Apache or Nginx.
Provide equivalent Bash/shell commands for installing and configuring web servers on Linux VMs.
Explicitly mention that both Windows and Linux VMs are supported as backend pools, and illustrate this with screenshots or configuration steps.
Where PowerShell is used, offer Linux command-line alternatives side-by-side.
Update diagrams and screenshots to include Linux VM icons or references where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by presenting Windows uninstall instructions before Linux, using Windows-specific tools (Control Panel, Programs and Features), and referencing Windows terminology and navigation patterns. While Linux instructions are present and reasonably detailed, the ordering and emphasis suggest a Windows-first approach.

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.
Where possible, provide command-line alternatives for Windows (e.g., using PowerShell or command prompt to uninstall the agent), similar to the Linux approach, to ensure parity for automation and headless environments.
Avoid Windows-centric navigation language (such as Control Panel) as the default; instead, clarify that these are Windows-specific steps and provide equivalent Linux navigation or command-line steps.
Add a summary table or section at the start of uninstall instructions that clearly distinguishes between Windows and Linux, helping users quickly find the relevant section.
Ensure that all examples and tool references are balanced between Windows and Linux, and that neither is given undue prominence unless justified by user base data.

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 only example for granting privileges to database users. There are no explicit Linux or cross-platform command-line examples (such as Bash, psql, or Azure CLI), and PowerShell is mentioned before other tools. While there is a brief mention of using PG admin or PSQL as alternatives, no concrete examples or guidance are provided for these tools, leaving Linux and cross-platform users underserved.

Recommendations:

Provide equivalent Linux/Bash/psql command examples alongside PowerShell scripts for tasks such as granting database privileges.
Explicitly mention and demonstrate how to use Azure CLI for relevant operations, as it is cross-platform.
When referencing scripts or tools, list cross-platform or Linux-native options first or in parallel with Windows/PowerShell.
Include screenshots or walkthroughs for PG admin and psql where PowerShell is referenced.
Add a section or callout for Linux/macOS users, summarizing the steps and tools they should use.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows environments. All examples, instructions, and credential requirements are specific to Windows guest OS, with explicit statements that Linux guest OS restores are not supported (except for a manual workaround). There are no Linux-specific instructions, examples, or parity in tooling or process. Windows tools, patterns, and account types are referenced exclusively.

Recommendations:

Clearly indicate in the introduction and prerequisites that Linux guest OS support is limited or unavailable, and provide a roadmap or ETA for Linux support if possible.
If manual restore from Linux VMs is possible (by attaching VMDKs), provide a dedicated section with step-by-step instructions for Linux users, including example commands for mounting VMDKs and copying files using Linux tools.
Where possible, generalize instructions and terminology to be OS-agnostic, or provide parallel sections for Windows and Linux.
Include examples of restoring files using Linux guest OS (even if only manually), with appropriate commands (e.g., using mount, guestmount, or similar tools).
List any limitations or differences in restore capabilities between Windows and Linux guests in a comparison table.
Avoid exclusive use of Windows-specific credential and account requirements in general documentation; instead, clearly scope such requirements to Windows-only sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias throughout. All VM creation, disk attachment, and installation instructions are provided exclusively for Windows environments. There are no Linux-based examples or guidance for deploying or managing Azure Backup Server on Linux. Windows-specific tools (such as PowerShell, Windows Update, and ReFS) are referenced without Linux alternatives, and the documentation assumes the use of Windows Server as the host OS for Azure Backup Server.

Recommendations:

If Azure Backup Server supports Linux as a host, provide equivalent Linux-based instructions for VM creation, disk attachment, and installation.
Include Linux command-line examples (e.g., using Azure CLI or Bash) alongside or before Windows/PowerShell examples.
Mention Linux-compatible file systems and storage configuration steps if supported.
Clarify early in the documentation if Azure Backup Server is Windows-only; if so, briefly explain why and suggest alternatives for Linux users.
Where PowerShell or Windows-specific tools are referenced, provide Azure CLI or cross-platform alternatives where possible.
Add a section or callout for Linux administrators, outlining any limitations or alternative approaches.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

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, migration paths, and next steps are centered on Microsoft SQL Server and Windows Server technologies, with no concrete examples or guidance for Linux subscriptions or workloads. Windows tools and patterns (e.g., Windows Server Failover Cluster, SQL Server) are highlighted, and Linux equivalents are not mentioned or linked.

Recommendations:

Include specific examples and migration guides for Linux workloads, such as migrating Linux VMs or databases (e.g., MySQL, PostgreSQL) to Azure VMware Solution.
Provide parity in 'Next steps' by adding links to Linux-focused documentation (e.g., configuring HA for Linux, enabling Azure Hybrid Benefit for Linux subscriptions).
Mention and explain Linux licensing/subscription options and how Azure Hybrid Benefit applies to them, with concrete scenarios.
Balance the coverage by describing both Windows and Linux use cases, tools, and patterns equally throughout the document.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows by exclusively referencing PowerShell cmdlets as the mechanism for Run Command operations, without mentioning or providing examples for Linux shells or tools. There are no Linux/Unix command-line examples, nor is there any discussion of how to perform similar tasks from a Linux environment. The terminology and workflow are centered around Windows-native tools and patterns.

Recommendations:

Include examples of running Run Command operations using Linux shells (e.g., Bash) or cross-platform tools (e.g., Azure CLI, REST API).
Clarify whether Run Command supports only PowerShell or if Linux/Unix scripting is also possible; if so, provide parity in examples.
Mention and document any Linux-compatible tools or workflows for managing Run Command, such as using the Azure CLI from a Linux terminal.
If PowerShell is required, note the availability of PowerShell Core on Linux and provide guidance for Linux users.
Ensure screenshots and UI references are not exclusively Windows-centric, or supplement them with Linux/CLI equivalents where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes creating and using a Windows VM as the jump box for accessing the Azure VMware Solution private cloud. All instructions, screenshots, and references are Windows-specific, with no mention of Linux alternatives or how to perform the same tasks on a Linux VM. The guidance for connecting to the VM and accessing vCenter/NSX Manager is tailored to Windows environments, and there are no Linux tools or patterns discussed.

Recommendations:

Provide parallel instructions for creating a Linux VM as a jump box, including recommended distributions (e.g., Ubuntu, CentOS) and any necessary configuration steps.
Include guidance and screenshots for connecting to the Linux VM (e.g., using SSH) and accessing vCenter Server and NSX Manager from a Linux environment (using Firefox/Chrome or CLI tools).
Mention Linux as an option in checklists and overviews, not just Windows.
Link to both Windows and Linux VM connection documentation in the 'connect to a virtual machine' step.
Discuss any differences or prerequisites for accessing vCenter/NSX Manager from Linux, such as browser compatibility or required packages.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits bias towards Windows environments. Restore instructions for encrypted VMs reference PowerShell and link exclusively to Windows-specific encryption documentation. There are no Linux-specific examples or references for restoring encrypted VMs or for item-level restore, and the documentation links for encryption are all Windows-focused. This may leave Linux users without clear guidance for equivalent operations.

Recommendations:

Add Linux-specific examples and instructions for restoring encrypted VMs, including references to relevant Linux disk encryption documentation.
Include CLI or Bash-based restore workflows alongside or instead of PowerShell-centric instructions.
Ensure that links and guidance for disk encryption and restore cover both Windows and Linux VM scenarios equally.
Explicitly mention any differences or additional steps required for Linux VMs in each restore scenario, especially for item-level restore and encrypted VM restore.
Where PowerShell is mentioned, provide Azure CLI or Bash alternatives for parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily Windows-centric, focusing exclusively on Windows environments and tools. All examples and instructions reference Windows-specific utilities (e.g., robocopy, Windows Server Backup, PowerShell), with no mention of Linux equivalents or support. There are no Linux examples or cross-platform guidance provided, and the documentation implicitly assumes the reader is using Windows.

Recommendations:

Explicitly state platform support at the beginning of the document. If MARS agent is Windows-only, clarify this to avoid confusion.
If Linux support is planned or available, provide equivalent Linux instructions, examples, and tool recommendations (e.g., using rsync instead of robocopy, bash scripts instead of PowerShell).
Where features are Windows-specific, clearly label them as such and provide alternative guidance or links for Linux users.
Include a comparison table or section outlining feature parity (or lack thereof) between Windows and Linux environments.
If MARS agent is not available for Linux, suggest alternative Azure backup solutions for Linux systems and link to relevant documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments, specifically Windows Server-based Active Directory. All examples, tools, and procedures are Windows-centric, with PowerShell scripts and references to Windows-specific utilities (e.g., ntdsutil.exe, DSRM). There are no Linux or cross-platform examples, nor is there mention of Samba or other non-Windows AD implementations. The documentation assumes the reader is operating in a Windows-only environment.

Recommendations:

Add a section or note clarifying that the procedures are specific to Windows Server Active Directory, and mention whether or not they apply to Samba-based (Linux) domain controllers.
If Azure Backup or related tools support Samba AD or Linux-based domain controllers, provide equivalent backup and restore instructions/examples for those platforms.
Where PowerShell scripts are given, provide equivalent commands for Linux environments (e.g., using samba-tool for Samba AD).
Discuss any limitations or differences in backup/restore procedures for non-Windows domain controllers, if applicable.
Explicitly mention the lack of Linux support if it is intentional, to set expectations for cross-platform administrators.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides detailed instructions for moving an Azure Web PubSub resource using the Azure Portal and Azure PowerShell, but does not include any examples or guidance for Linux users or alternative CLI tools (such as Azure CLI or Bash scripting). PowerShell is featured exclusively for command-line operations, and Windows-specific tools like 'notepad' are referenced for editing JSON files.

Recommendations:

Add equivalent instructions and examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
Replace or supplement the 'notepad' editor reference with cross-platform alternatives such as 'vi', 'nano', 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 provide sample commands.
Ensure that any PowerShell-specific instructions are accompanied by Azure CLI equivalents, especially for exporting, editing, and deploying ARM templates.
Review the documentation for other Windows-centric terminology or assumptions and revise to be OS-agnostic where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The Azure Backup glossary page demonstrates a Windows bias in several ways. Windows-specific technologies and tools (such as VSS, DPM, MABS, and MARS agent) are referenced without Linux equivalents or alternatives. In the 'Application consistent backup' entry, Windows VSS is mentioned first and in detail, while Linux is only referenced generically as 'pre or post scripts.' Several backup scenarios (bare metal, system state) are described in a way that is only applicable to Windows environments. Additionally, links and references to Windows tools (e.g., PowerShell, VSS documentation) are present, while Linux-native tools or workflows are not mentioned or are only briefly alluded to.

Recommendations:

For each Windows-specific tool or technology (e.g., VSS, DPM, MABS, MARS agent), add equivalent Linux-focused explanations or explicitly state if there is no Linux equivalent.
In entries like 'Application consistent backup,' provide concrete Linux examples (e.g., using fsfreeze, LVM snapshots, or specific pre/post script patterns) and link to relevant Linux documentation.
Where PowerShell is referenced, ensure Azure CLI (which is cross-platform) is also mentioned with equal prominence.
For backup types like 'bare metal backup' and 'system state backup,' clarify their applicability to Windows and describe analogous Linux backup strategies (e.g., full disk imaging with dd, tar, or third-party tools).
Add references to Linux backup best practices and tools where relevant, and ensure that Linux administrators can find parity in documentation and guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation references Azure PowerShell as an alternative method for restoring AKS clusters, but does not mention or provide examples for equivalent Linux-native or cross-platform CLI tools (such as Azure CLI or kubectl). The only explicit command-line method referenced is PowerShell, and there are no Linux-specific instructions or examples. This suggests a bias toward Windows/PowerShell environments and leaves out users who work primarily on Linux or macOS.

Recommendations:

Include Azure CLI examples for restoring AKS clusters, as Azure CLI is cross-platform and widely used on Linux and macOS.
Mention and provide instructions for using kubectl (where applicable) for restore operations, especially for item-level or namespace restores.
When referencing PowerShell, always provide a parallel example using Azure CLI or bash scripts.
Explicitly state that the restore process can be performed from any OS, and clarify any OS-specific requirements or limitations.
Review linked articles (such as the PowerShell restore guide) to ensure Linux parity and cross-platform guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a clear Windows bias by providing only PowerShell deployment instructions, referencing the Azure PowerShell module as a prerequisite, and omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux users. The 'Next steps' section also directs users to a PowerShell-based restore guide, further reinforcing the Windows-centric approach. There is no mention of Linux tools, shells, or cross-platform alternatives.

Recommendations:

Add Azure CLI and/or Bash examples for deploying the ARM template, as these are cross-platform and widely used on Linux and macOS.
List both Azure PowerShell and Azure CLI as prerequisites, with installation instructions for each.
In the deployment section, provide parallel instructions/scripts for PowerShell and Azure CLI, making it clear that either can be used.
Update the 'Next steps' section to include links to both PowerShell and Azure CLI restore guides.
Explicitly mention that the process is cross-platform and can be performed from Windows, Linux, or macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page, while focused on Azure CLI (which is cross-platform), demonstrates Windows bias in several ways. It references PowerShell objects and patterns before explaining CLI equivalents, uses Windows-style file paths (e.g., '.\OSSPolicy.json'), and does not provide Linux/macOS-specific examples or notes on differences (such as file path conventions or shell syntax). The guidance assumes a Windows environment for file manipulation and scripting, potentially confusing Linux users.

Recommendations:

Provide both Windows (PowerShell/CMD) and Linux/macOS (Bash) command examples, especially for file paths and redirection.
Replace or supplement Windows-style file paths (e.g., '.\OSSPolicy.json') with POSIX-style paths (e.g., './OSSPolicy.json') in CLI examples.
Add notes or callouts explaining differences in file handling and command syntax between Windows and Linux/macOS shells.
Avoid referencing PowerShell objects or behaviors unless specifically relevant, and clarify when instructions are Windows-specific.
Explicitly state that Azure CLI is cross-platform and provide parity in examples and troubleshooting for all supported OSes.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. While the main content is platform-neutral and focuses on Azure concepts, the 'Next steps' section lists Azure PowerShell (a Windows-centric tool) before or alongside Azure CLI (which is cross-platform) for backup and restore operations. There are no explicit Linux shell or bash examples, and PowerShell is mentioned as a primary automation tool, which may implicitly prioritize Windows users. No Linux-specific tools, commands, or examples are provided.

Recommendations:

Ensure that Azure CLI (which is cross-platform) is listed before or alongside Azure PowerShell in all 'Next steps' and example sections.
Provide explicit bash or shell command examples for common operations, especially for installation and management tasks.
Where PowerShell is mentioned, clarify that Azure CLI is available and supported on Linux/macOS/Windows, and provide links to CLI documentation.
Add a section or callout noting that all operations can be performed from Linux/macOS environments using Azure CLI.
If possible, include screenshots or walkthroughs from non-Windows environments (e.g., Azure Cloud Shell, Linux terminal) to reinforce cross-platform support.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the only command-line automation example, both in the introduction and in the 'Next steps' section, without mentioning or providing any Azure CLI (cross-platform) or Bash/Linux-native alternatives. All command-line automation is directed to PowerShell, and there are no Linux-specific or cross-platform shell examples. The documentation assumes use of the Azure Portal or PowerShell, omitting Linux-first workflows.

Recommendations:

Add Azure CLI examples alongside or before PowerShell examples for all automation steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
In 'Next steps', include links to Azure CLI-based backup and restore guides, or provide equivalent Bash scripts.
When referencing command-line options, mention both PowerShell and CLI, or provide a table with both sets of commands.
Explicitly state that all features are available via Azure CLI and provide links or inline examples.
If screenshots are shown, ensure they are not Windows-specific (e.g., avoid showing only Windows file paths or PowerShell terminals).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a mild Windows bias, primarily by listing Azure PowerShell as a first-class method for backup and restore operations alongside Azure CLI and the Azure portal. Azure PowerShell is a Windows-centric tool, and its inclusion (and placement before ARM/Bicep/Terraform) suggests a preference for Windows tooling. However, the documentation does not provide command-line examples, and the main technical requirements and supported scenarios focus on Linux-based node pools, which is positive for Linux parity. Still, the 'Next steps' section lists Azure PowerShell before ARM/Bicep/Terraform, and the page references Azure CLI and PowerShell as the main automation tools, which may reinforce a Windows-first perception.

Recommendations:

Ensure that all example commands and automation instructions are provided for both Azure CLI and Azure PowerShell, with CLI (cross-platform) examples listed first.
Explicitly state that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
Where possible, provide Bash shell examples for scripting and automation, not just PowerShell.
In the 'Next steps' section, list Azure CLI before Azure PowerShell, and consider grouping cross-platform tools (CLI, ARM, Bicep, Terraform) before Windows-centric tools.
Clarify that PowerShell is available cross-platform, but that Azure CLI is the primary tool for Linux users.
If referencing PowerShell, provide equivalent Bash/CLI examples or links for Linux users.

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 or Windows-specific tools (e.g., PowerShell cmdlets, .exe installers). The workflow assumes a Windows environment (e.g., references to Hyper-V, Windows Server, and NTLM authentication). Linux support is only briefly mentioned, with no concrete examples or detailed guidance for Linux VMs. There are no Linux shell commands, nor are Linux-specific backup or recovery scenarios illustrated.

Recommendations:

Provide parallel Linux command-line examples (e.g., bash commands for agent installation, configuration, and firewall management).
Include explicit instructions and screenshots for backing up and recovering Linux VMs, covering both host-level and guest-level scenarios.
Clarify any differences in backup and recovery workflows for Linux VMs, including limitations and best practices.
Mention Linux tools/utilities (e.g., systemctl, firewall-cmd/ufw) where relevant, alongside Windows tools.
Ensure that Linux prerequisites and supported scenarios are as detailed as those for Windows, and are not relegated to a single line or table row.
Consider reordering sections or examples so that Linux is not always mentioned last or as an afterthought.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented towards Windows environments. All instructions, terminology, and referenced features (such as Volume Shadow Copy Service, deduplication, and file/folder selection) are specific to Windows. There are no examples, notes, or guidance for Linux systems, nor is there any mention of Linux-specific backup considerations or tools. The documentation assumes the use of the MABS console, which is a Windows application, and references Windows-only features (e.g., VSS, Data Deduplication, file properties dialog).

Recommendations:

Add explicit notes clarifying whether MABS supports Linux clients, and if so, provide equivalent instructions or limitations for Linux systems.
Include Linux-specific examples or workflows, such as how to install the protection agent on Linux, how to select files/folders for backup, and how to perform recovery operations.
Mention Linux backup/recovery limitations (e.g., lack of VSS, differences in file system support, etc.) where relevant.
If Linux is not supported, state this clearly at the beginning of the documentation to set expectations.
Where Windows-specific features are referenced (e.g., Data Deduplication, VSS, file properties), provide Linux alternatives or note their absence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows environments, specifically Hyper-V on Windows Server, and Microsoft Azure Backup Server (MABS), which itself is a Windows-based product. Windows terminology, tools, and workflows are exclusively described, with Linux only briefly mentioned as a supported guest OS for file-consistent snapshots. There are no Linux command-line examples, no mention of Linux-based backup agents or recovery workflows, and all recovery and backup procedures are described using Windows GUI tools or Windows-specific features (e.g., VSS, SCSI controller requirements, registry edits).

Recommendations:

Provide explicit Linux guest backup and recovery examples, including command-line steps for Linux VMs.
Clarify the limitations and capabilities for Linux VMs (e.g., application-consistent vs. file-consistent backups, supported distributions, agent installation).
Include parity in recovery workflows for Linux VMs, such as how to restore files from a Linux guest, and whether item-level recovery is possible.
Mention or link to equivalent Linux backup tools or patterns where appropriate, or clarify if none exist.
If MABS does not support certain Linux scenarios, state this clearly and suggest alternative approaches or products for Linux environments.
Balance the documentation structure so that Linux prerequisites and workflows are not relegated to a single line or section, but are integrated throughout.

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 deployment instructions and code samples using Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The instructions reference Windows-specific behaviors (e.g., right-click to paste in the shell window), and there are no Linux/macOS-specific guidance or cross-platform notes. The 'Next steps' section also links only to PowerShell-based restore instructions.

Recommendations:

Provide equivalent Azure CLI (az) examples for deploying the Bicep template, as Azure CLI is cross-platform and widely used on Linux/macOS.
Include Bash shell instructions and note any differences in command usage or environment setup for Linux/macOS users.
Avoid Windows-specific instructions such as 'right-click to paste' or clarify how to paste in terminals on different operating systems.
In the prerequisites, mention both Azure PowerShell and Azure CLI as supported tools for deploying Bicep files, and link to installation guides for both.
In the 'Next steps' section, add links to restore instructions using Azure CLI or portal, not just PowerShell.
Consider a 'Platform differences' note or table summarizing how to perform each step on Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows environments, specifically focusing on Data Protection Manager (DPM), which is a Windows-only tool. All instructions, screenshots, and terminology assume the use of Windows Server, Windows-based SQL Server, and Windows authentication patterns (e.g., NTAuthority\System). There are no examples, guidance, or mentions of Linux-based SQL Server deployments or equivalent backup workflows for Linux environments.

Recommendations:

Add a section or parallel documentation for backing up SQL Server running on Linux VMs or containers, using Azure Backup or other supported tools.
Explicitly state that DPM is a Windows-only solution and provide alternative recommendations for Linux users (e.g., Azure Backup integration with Linux, or using native SQL Server backup/restore commands with Azure Blob Storage).
Include examples and screenshots for Linux-based SQL Server environments, if supported, or clearly direct Linux users to relevant documentation.
Mention and link to cross-platform or Linux-native backup tools and workflows where applicable.
Ensure that prerequisite and limitation sections clarify OS support and provide parity guidance for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation primarily focuses on Azure Portal UI steps and, where automation is mentioned, references PowerShell before CLI. There are no explicit Linux or cross-platform command-line examples, and scripting is described in terms of PowerShell or CLI, with PowerShell listed first. No Linux-specific tools, shell commands, or considerations are provided, and the overall flow assumes a Windows-centric audience.

Recommendations:

Provide Azure CLI examples alongside or before PowerShell examples, as CLI is cross-platform and works natively on Linux, macOS, and Windows.
Explicitly mention that all CLI commands can be run on Linux, macOS, or Windows, and provide sample shell commands for Linux users.
Where scripting is referenced, avoid listing PowerShell before CLI unless there is a technical reason; consider listing CLI first for cross-platform parity.
Add a section or callout for Linux/macOS users, clarifying that all operations can be performed from their platforms using Azure CLI.
If automation scripts are provided, include Bash shell script examples in addition to PowerShell.
Ensure that any downloadable scripts or templates are available in both PowerShell and Bash formats.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by focusing on Windows-specific backup agents (MARS, DPM, MABS), providing detailed architectural descriptions and workflows only for Windows/on-premises Windows Server scenarios, and omitting equivalent Linux backup workflows or agents. Linux is mentioned only to state that certain features are unsupported, and there are no Linux-specific examples, tools, or architectural diagrams. The documentation also lists Windows backup options before Azure VM or cross-platform options, and does not provide parity in guidance for Linux workloads.

Recommendations:

Add explicit coverage of Linux backup scenarios, including supported methods for backing up on-premises Linux machines (e.g., via Azure Backup Server, third-party tools, or native Azure VM backup).
Include architectural diagrams and step-by-step workflows for Linux backup scenarios, similar to those provided for Windows/MARS agent.
Clearly state the limitations and alternatives for Linux backup, and provide links to relevant Linux backup documentation.
Ensure that examples and feature tables include both Windows and Linux where applicable, or clarify when features are Windows-only.
Where possible, present Azure VM backup (which supports both Windows and Linux) before Windows-only solutions, to avoid a 'windows_first' impression.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation presents Windows requirements and tooling first, with detailed and finalized requirements, while Linux is explicitly marked as 'not yet supported' and only provides 'expected requirements.' Windows-specific tools and technologies (e.g., BitLocker, VBS, HVCI, Windows Defender, Schannel cipher suites) are referenced by name, while Linux equivalents are only generically described or listed as 'similar.' There is a lack of concrete Linux examples, resources, or references to common Linux security tools and practices, and the Linux section is less detailed and more tentative.

Recommendations:

Provide Linux support parity by finalizing Linux requirements and removing 'not yet supported' disclaimers when ready.
List Linux and Windows requirements side-by-side or in parallel, rather than presenting Windows first and in more detail.
Reference Linux-native tools and technologies by name (e.g., LUKS/dm-crypt for storage encryption, SELinux/AppArmor for code integrity, auditd/syslog for security logging, OpenSSL/GnuTLS for TLS cipher suites) in the same way as Windows tools.
Include links to Linux-specific documentation and best practices, similar to the Windows links provided.
Offer concrete Linux configuration examples and guidance, not just generic requirements.
Ensure that any Microsoft-specific dependencies (e.g., Azure Attestation, Defender for Endpoint) are clearly documented for Linux, with Linux-specific setup instructions or alternatives where appropriate.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation for the MARS Agent is heavily focused on Windows environments. All backup and recovery scenarios, process steps, and technical details are described exclusively for Windows systems, with explicit references to Windows-specific features (e.g., VSS, USN change journal, Windows volumes, system state). There are no examples, instructions, or mentions of Linux support or equivalent Linux tools. The documentation implicitly assumes the user is operating in a Windows environment.

Recommendations:

Clearly state the platform support for the MARS Agent at the beginning of the documentation. If Linux is not supported, explicitly mention this to set user expectations.
If Linux support is planned or available, add equivalent Linux examples, scenarios, and technical details (e.g., how to back up Linux files/folders, which snapshotting tools are used, etc.).
Where Windows-specific tools or patterns are mentioned (e.g., VSS, USN journal), provide Linux equivalents or clarify that these features are not available/applicable on Linux.
Add a comparison table or section outlining feature parity (or lack thereof) between Windows and Linux for the MARS Agent.
Ensure that any future updates to the documentation include Linux examples and instructions if/when support is added.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references Azure Backup Server and Data Protection Manager (DPM), both of which are Windows-only tools. All instructions, screenshots, and terminology are tailored to the Windows GUI and ecosystem, with no mention of Linux-based backup servers, command-line alternatives, or cross-platform recovery workflows. There are no Linux or PowerShell/Bash examples, but the bias is toward Windows GUI tools and patterns.

Recommendations:

Explicitly state that Azure Backup Server and DPM are Windows-only solutions at the beginning of the article.
If Linux-based backup and recovery is supported, provide parallel instructions or links for Linux environments (e.g., using Azure CLI, Recovery Services Vault with Linux VMs, or other supported Linux backup agents).
Include a comparison table or section outlining backup and recovery options for both Windows and Linux workloads.
Where possible, add command-line examples (PowerShell for Windows, Bash/Azure CLI for Linux) to supplement GUI instructions.
Reference Linux-specific documentation for users seeking to recover data from Linux-based systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows environments, referencing only Windows Server, Windows Client, and Microsoft-specific tools (such as DPM and Azure Backup Server) without any mention of Linux equivalents or cross-platform considerations. There are no troubleshooting steps or examples for Linux-based systems, nor is it clarified whether the guidance is applicable to non-Windows environments.

Recommendations:

Explicitly state whether Azure Backup Server supports Linux or is Windows-only. If Linux is supported, include troubleshooting steps and examples for Linux environments.
If the product is Windows-only, clarify this at the beginning of the documentation to set expectations for Linux users.
Where possible, provide parity in documentation by including Linux command-line examples (e.g., Bash) or references to Linux backup/recovery tools if supported.
Mention any cross-platform limitations or alternative solutions for Linux users, such as using Azure Backup for Linux VMs or other supported agents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias in several areas: Windows-specific examples and references (such as PowerShell and Windows tutorials) are given without equivalent Linux instructions; Windows terminology and tools are mentioned first or exclusively; and some advanced scenarios (e.g., restoring VMs with special network configurations or domain controllers) focus on Windows workflows. Linux-specific guidance is minimal or absent, and there are few, if any, CLI or Linux-native examples.

Recommendations:

Provide equivalent Linux examples and references wherever Windows/PowerShell examples are given (e.g., using Azure CLI or Bash scripts for restore operations).
Include links to Linux-specific documentation (e.g., restoring Linux VMs, handling cloud-init, or troubleshooting Linux agent issues).
Balance references to Windows and Linux in scenario tables and guidance, ensuring both platforms are equally represented.
When mentioning tools or workflows (such as PowerShell), also mention and provide examples for their Linux/CLI counterparts.
Add explicit notes or sections for Linux-specific post-restore steps, such as handling SSH keys, cloud-init, and agent installation.
Review scenario coverage (e.g., SQL VMs, domain controllers) to ensure Linux equivalents (e.g., restoring MySQL/PostgreSQL VMs, LDAP servers) are addressed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows and PowerShell by consistently providing PowerShell examples alongside Azure CLI, ARM, and portal instructions, even when PowerShell support is incomplete or missing for certain features (e.g., Key Vault references, secret volume mounts). There is no mention or example of Linux-specific tools, shell scripting, or cross-platform command-line usage (e.g., Bash), and PowerShell is presented as a primary automation method. The documentation does not address or acknowledge Linux shell environments, nor does it provide parity for Linux users in terms of scripting or automation guidance.

Recommendations:

Add explicit Bash/Linux shell examples for all CLI instructions, demonstrating usage in a typical Linux terminal environment.
Clarify that Azure CLI commands are cross-platform and can be run in Bash, PowerShell, or other shells, and provide sample commands for both Bash and PowerShell where relevant.
When PowerShell support is missing for a feature (e.g., Key Vault references, secret volume mounts), provide alternative Linux scripting or CLI-based workflows.
Avoid presenting PowerShell as the default or primary scripting language; instead, offer both PowerShell and Bash examples, or clearly indicate when an example is Windows-specific.
Include notes or sections addressing Linux/macOS users, such as environment variable syntax differences, file path conventions, and shell scripting best practices.
Where possible, provide downloadable sample scripts for both PowerShell and Bash to ensure parity and accessibility for users on all platforms.

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 cleanup examples use Azure PowerShell scripts, with no mention or example of Azure CLI or Bash equivalents. The Bicep template provisions only Windows VMs, and the allowed OS versions are exclusively Windows. The instructions and references (such as monitoring and starting backup jobs) link to PowerShell-specific guides. There is no guidance for Linux users or for deploying/protecting Linux VMs.

Recommendations:

Provide parallel Azure CLI/Bash examples for deploying the Bicep template, starting backup jobs, monitoring, and cleanup.
Include or reference a Bicep template that provisions a Linux VM, or show how to modify the template for Linux.
Mention both Windows and Linux options in the prerequisites and throughout the guide, including links to relevant Linux documentation.
When referencing tools or scripts, present cross-platform options (e.g., Azure CLI before or alongside PowerShell).
Ensure that links to further reading or next steps include Linux-focused guides as well as Windows ones.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes backup procedures using System Center Data Protection Manager (DPM), a Windows-only tool, and focuses on Microsoft Exchange Server, which is also a Windows-based application. All instructions, screenshots, and examples are based on Windows environments, with no mention of Linux equivalents, cross-platform tools, or alternative approaches for non-Windows systems.

Recommendations:

Clearly state at the beginning that the guide is specific to Windows environments and DPM, and provide links to cross-platform or Linux-based backup solutions if available.
If Azure Backup supports Linux-based workloads or Exchange alternatives on Linux, include parallel documentation or references for those scenarios.
Where possible, mention or link to Azure-native backup options or third-party tools that support Linux servers and applications.
Add a comparison table or section outlining backup options for both Windows and Linux environments, helping users identify the right tool for their platform.

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 tooling (such as the MARS agent, AzureOfflineBackupDiskPrep utility, and Azure PowerShell) are Windows-specific. There are no examples or guidance for Linux systems, and the workflow assumes the use of Windows-only tools and patterns (e.g., elevated command prompt, Windows file paths, Internet Explorer/Edge). Linux users are not addressed, and there is no mention of cross-platform alternatives.

Recommendations:

Explicitly state early in the documentation that the workflow is only supported on Windows, if that is the case. If Linux is not supported, clarify this to set user expectations.
If Linux support is possible, provide equivalent instructions, tooling, and examples for Linux environments (e.g., bash commands, Linux-compatible utilities, and browser requirements).
Mention any cross-platform or Linux-compatible Azure backup agents or workflows, if available.
Where PowerShell or Windows-specific tools are required, suggest or link to alternatives for Linux (such as Azure CLI or REST API usage).
Avoid assuming the presence of Windows-only browsers (Edge, Internet Explorer); mention cross-platform browser support if applicable.
Include a comparison table or section that outlines supported OSes and any limitations for non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes how to validate Edge Secured-core status using Windows GUI tools and navigation, with no mention of Linux or cross-platform methods. All instructions and screenshots are Windows-specific, and there are no command-line or Linux-based alternatives provided.

Recommendations:

Add equivalent instructions for Linux-based devices, if Edge Secured-core is relevant or supported on Linux.
If not supported on Linux, explicitly state that Edge Secured-core is a Windows-only feature to clarify the scope.
Provide command-line alternatives (e.g., PowerShell, Windows Command Prompt, or Linux shell commands) for users who may not use the Windows GUI.
Include a section or note on how to check similar security features on Linux (such as TPM version, memory integrity, or disk encryption status) for broader applicability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows environments, specifically referencing System Center Data Protection Manager (DPM), Microsoft Azure Backup Server (MABS), and the Microsoft Azure Recovery Services (MARS) agent—all Windows-only products. All examples, prerequisites, and workflows assume a Windows system, referencing Windows-specific tools (e.g., AzureOfflineBackupDiskPrep.exe), Windows PowerShell, and browsers like Microsoft Edge or Internet Explorer. There are no Linux equivalents, examples, or guidance for performing offline seeding from Linux systems, nor is it clarified whether the workflow is possible from non-Windows environments.

Recommendations:

Explicitly state in the prerequisites and introduction whether the workflow is supported or unsupported on Linux systems.
If possible, provide Linux-compatible tools or scripts for preparing disks and interacting with the Azure Import/Export service.
Include example workflows or guidance for performing offline seeding from Linux servers, or provide links to relevant Linux documentation if available.
Mention cross-platform alternatives (such as Azure CLI or REST APIs) where possible, and provide usage examples for Linux environments.
Clarify any limitations or required workarounds for Linux administrators who need to seed data to Azure.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments. All command-line examples use PowerShell, and all configuration steps reference Windows tools (such as Registry Editor and Certificate Import Wizard). There are no examples or instructions for performing equivalent tasks on Linux-based Azure Backup Server deployments, nor is there mention of Linux compatibility or alternatives. Windows-specific patterns (e.g., .reg files, Windows services, Windows-style file paths) are used exclusively and presented as the default or only approach.

Recommendations:

Add equivalent instructions and examples for Linux-based deployments, including how to import certificates, modify configuration files, and manage services.
Provide shell (bash) script examples alongside PowerShell for tasks like disk exclusion or service management.
Clarify whether Azure Backup Server is supported on Linux, and if not, explicitly state this early in the documentation.
When referencing tools (e.g., Registry Editor, Certificate Import Wizard), mention Linux alternatives or note their absence.
Use neutral language and ordering (e.g., 'On Windows, do X. On Linux, do Y.') when describing platform-specific steps.
If certain features or scripts (like ExcludeDisk.ps1) are Windows-only, clearly state this and suggest workarounds or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows environments. All instructions, tools, and examples assume a Windows Server context, with exclusive references to Windows-specific tools (e.g., Registry Editor, CMD, NT AUTHORITY\SYSTEM, %Program Files%, Windows registry paths, and Windows service accounts). There are no Linux equivalents or cross-platform guidance, and no mention of Linux-based SharePoint deployments or Azure Backup Server usage on Linux. All command-line examples use Windows CMD, and all administrative procedures reference Windows UI or Windows-specific concepts.

Recommendations:

Explicitly state that MABS and SharePoint backup are only supported on Windows, if that is the case. If Linux is not supported, clarify this early in the documentation.
If any part of the workflow is possible on Linux (e.g., Azure Backup Server components, agent installation, or monitoring), provide equivalent Linux instructions and examples.
For command-line operations, provide PowerShell and, if possible, Bash or cross-platform CLI alternatives.
Replace or supplement Windows-specific paths (e.g., %Program Files%, registry keys) with Linux equivalents or note their absence.
Mention any limitations or lack of support for Linux environments explicitly, so Linux administrators are not misled.
If the product is Windows-only, consider a brief section explaining why, and link to any roadmap or alternatives for Linux environments.

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 Windows environments without mentioning Linux alternatives or providing cross-platform guidance. There are no examples or guidance for Linux-based SharePoint deployments or backup tools, and the documentation assumes the use of Windows-native tools and interfaces throughout.

Recommendations:

Acknowledge that DPM is a Windows-only solution and clarify platform limitations early in the documentation.
Provide information or links to alternative backup solutions for SharePoint on Linux (if supported), or explicitly state if Linux-based SharePoint deployments are not supported.
If possible, include parity documentation for Linux-based backup tools (such as Azure CLI, AzCopy, or third-party solutions) for similar backup scenarios.
Add a comparison table or section outlining platform support and tool availability for both Windows and Linux environments.
Ensure that future documentation for Azure Backup scenarios includes both Windows and Linux examples where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias through heavy reliance on PowerShell scripts and commands, exclusive mention of Windows-centric tools (such as MARS, MABS, DPM, and ARMClient via Chocolatey), and a lack of Linux or cross-platform alternatives. Instructions for deleting backup items and vaults are primarily provided for Windows tools and interfaces, with no equivalent examples for Linux environments or Bash scripting. The CLI section is minimal and notes limited support, while the PowerShell and management console instructions are detailed and Windows-specific.

Recommendations:

Provide equivalent Bash or Azure CLI scripts for all major operations, including vault and backup item deletion, and ensure these are as detailed as the PowerShell examples.
Mention and demonstrate installation and usage of Azure CLI and ARMClient on Linux/macOS, not just via Chocolatey (Windows).
Include guidance for managing Recovery Services vaults from Linux-based environments, including any differences or limitations.
When referencing management consoles (MARS, MABS, DPM), clarify their platform support and, if Windows-only, suggest alternatives or note limitations for Linux users.
Ensure that examples and tool recommendations are presented in a platform-neutral order, or provide parallel instructions for both Windows and Linux 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 PowerShell examples for listing available VM sizes, referencing Windows-centric tools (PowerShell, Visual Studio), and omitting equivalent Linux/CLI examples. The deployment instructions and tooling references prioritize or exclusively mention Windows workflows, with no mention of Azure CLI, Bash, or cross-platform alternatives.

Recommendations:

Add equivalent Azure CLI (az) command examples for listing available VM sizes, suitable for Linux/macOS users.
Include Bash or shell script snippets alongside PowerShell to ensure parity.
Mention cross-platform tools (e.g., Azure CLI, ARM templates) before or alongside Windows-specific tools like PowerShell and Visual Studio.
Ensure deployment instructions and next steps reference both Windows and Linux-friendly workflows, such as deploying via Azure CLI or from a Linux environment.
Where possible, clarify that the service definition file and repackaging steps can be performed on any platform, not just Windows.

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 emphasized as the primary scripting method, with a dedicated section for running a PowerShell script to grant privileges. The instructions for setting up the environment variables for PSQL are explicitly Windows-centric, referencing Control Panel and System Properties, with screenshots and steps only for Windows. There are no equivalent instructions or examples for Linux or macOS users, and Linux command-line patterns are not mentioned. While the PSQL tool is referenced, its usage is only contextualized within a Windows environment.

Recommendations:

Provide parallel instructions and screenshots for Linux and macOS environments, especially for setting environment variables and running scripts.
Include bash or shell script examples alongside PowerShell, or at least mention how to adapt the PowerShell script for non-Windows platforms.
When referencing tools like PSQL, show how to install and configure them on Linux (e.g., using apt or yum) and macOS (e.g., using Homebrew).
Avoid assuming the user is on Windows; use cross-platform language and clarify when steps differ by OS.
Add notes or links to official PostgreSQL documentation for Linux/macOS users regarding environment setup and script execution.

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 code examples are provided exclusively in PowerShell, with explicit instructions for using PowerShell in the Azure Cloud Shell. The ARM template referenced is described as deploying a 'simple Windows VM', with no mention of Linux VM options or examples. Linux command-line tools or Bash/CLI examples are not provided, and the workflow assumes familiarity with Windows-centric tools and patterns.

Recommendations:

Add equivalent Azure CLI (Bash) examples for deploying the ARM template, including step-by-step instructions.
Reference and, if possible, provide an ARM template example for deploying and backing up a Linux VM, or clarify how to adapt the template for Linux.
Ensure that mentions of deployment methods (PowerShell, CLI, Portal, REST) give equal prominence to Azure CLI/Bash and not just PowerShell.
Include cleanup instructions using Azure CLI, not just PowerShell cmdlets.
Where possible, use neutral language (e.g., 'virtual machine' instead of 'Windows VM') unless the example is truly Windows-specific, and clarify applicability to Linux.
Provide links to Linux-specific backup/restore documentation if available.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page shows subtle Windows bias by referencing PowerShell and linking to PowerShell-based instructions (e.g., for creating a Backup vault and restoring blobs) before or in addition to CLI examples. There is no explicit mention of Linux or Bash environments, and the linked PowerShell instructions may not be directly usable on Linux or macOS systems. The documentation does not provide Linux-specific guidance or parity in example scripts.

Recommendations:

Ensure that all referenced instructions (such as creating a Backup vault and restoring blobs) include both Azure CLI and PowerShell options, with CLI (cross-platform) examples presented first.
Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and provide Bash shell examples where appropriate.
Avoid linking only to PowerShell-based guides; always provide a CLI alternative or make it clear when a step is Windows-specific.
Add a note in the prerequisites clarifying that the quickstart is cross-platform and does not require Windows or PowerShell.

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 and Windows-centric tools (such as .PFX certificates and Visual Studio) without providing equivalent Linux or cross-platform examples. The instructions and tooling are oriented towards Windows users, and there are no mentions of Linux command-line tools or certificate formats commonly used on Linux. Additionally, PowerShell is mentioned before any other scripting or CLI options, and deployment examples focus on Windows-first workflows.

Recommendations:

Include Azure CLI examples for certificate and Key Vault operations, as Azure CLI is cross-platform and widely used on Linux.
Provide instructions for preparing certificates in PEM format and converting between PEM and PFX, as PEM is common on Linux.
Add Linux shell (bash) examples for uploading certificates to Key Vault.
Mention and link to documentation for Linux-based deployment tools and editors (e.g., VS Code, ARM templates via CLI).
Ensure that all steps referencing PowerShell or Visual Studio are accompanied by Linux-friendly alternatives.
Clarify that the process is platform-agnostic where possible, and highlight any Windows-specific steps as such.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows environments, specifically referencing System Center DPM, Windows PowerShell, and .NET Framework as prerequisites. All instructions, tools, and screenshots assume a Windows GUI and Windows-based workflows. There are no examples, instructions, or considerations for Linux-based DPM servers or cross-platform scenarios. Linux equivalents for agent installation, prerequisites, or command-line operations are not mentioned.

Recommendations:

Explicitly state that DPM is a Windows-only product, if that is the case, or clarify Linux support status.
If Linux-based backup scenarios are supported (e.g., via MARS or Azure Backup agent), provide parallel instructions and examples for Linux environments.
List Linux prerequisites (such as required packages or dependencies) alongside Windows requirements.
Include Linux command-line examples (e.g., Bash, shell scripts) for agent installation, registration, and troubleshooting.
Mention and link to any Linux-native tools or agents that can be used for Azure Backup, if available.
If DPM is not available on Linux, suggest alternative Azure Backup solutions for Linux workloads and link to relevant documentation.

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 only CLI automation example and omitting explicit Linux or cross-platform CLI (e.g., Azure CLI, Bash) instructions. The mention of PowerShell for permission configuration is not balanced with equivalent Linux or cross-platform alternatives, and no Linux-specific tools or workflows are referenced.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside or before PowerShell instructions for all automation and scripting steps.
Explicitly mention that steps can be performed from Linux, macOS, or Windows, and clarify any OS-specific differences.
Include Bash shell examples where relevant, particularly for scripting or automation tasks.
Review linked pages (such as backup-azure-vms-automation.md) to ensure Linux parity in automation instructions.
Avoid referencing only Windows-specific tools (like PowerShell) without cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively demonstrates how to back up a Windows virtual machine in Azure using Terraform. All examples, resource creation steps, and references are specific to Windows VMs, with no mention of Linux VM equivalents or how to adapt the process for Linux. The 'Next steps' section also directs users to more Windows VM articles, reinforcing the Windows-centric focus. There are no examples or guidance for Linux users, nor any mention of Linux-specific considerations.

Recommendations:

Add parallel instructions and Terraform code samples for creating and backing up a Linux virtual machine, including any differences in resource definitions or backup procedures.
Update the checklist and step-by-step instructions to mention both Windows and Linux VM options, or provide a choice at the beginning for users to follow either path.
Include links to additional documentation or articles focused on Linux VM backup with Terraform.
Revise the 'Next steps' section to include resources for both Windows and Linux VMs.
Clarify in the introduction that the guide is Windows-specific, or broaden the scope to cover both operating systems.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes backup and recovery procedures for Microsoft Exchange Server using Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All examples, instructions, and screenshots are based on the Windows GUI and Windows file paths. There is no mention of Linux-based Exchange alternatives, Linux backup agents, or cross-platform considerations. The documentation assumes a Windows environment throughout.

Recommendations:

Clarify early in the documentation that MABS and Exchange Server are Windows-only, and explicitly state platform limitations.
If Azure Backup supports Linux workloads or other mail servers (e.g., Postfix, Dovecot), provide parallel documentation or links for Linux backup scenarios.
Where possible, mention or link to Azure Backup documentation for Linux servers, including agent installation and backup procedures.
Add a note or section addressing the lack of Linux support for this scenario, and suggest alternative solutions for Linux-based mail servers.
Ensure that future documentation for backup scenarios includes both Windows and Linux examples where supported.

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), using Windows-specific terminology (e.g., 'Server Explorer', 'New Query'), and omitting any mention of Linux-compatible alternatives or command-line approaches. There are no examples or instructions for performing the same tasks on Linux systems, such as using Azure Data Studio, sqlcmd, or other cross-platform tools. The instructions for installing the self-hosted integration runtime also assume a Windows environment, with no mention of Linux installation steps.

Recommendations:

Include instructions and examples for Linux users, such as using Azure Data Studio or sqlcmd for database operations.
Mention and provide steps for installing the self-hosted integration runtime on Linux, referencing the official cross-platform installation documentation.
Replace or supplement references to 'SQL Server Management Studio' and 'Server Explorer' with cross-platform alternatives.
Add notes or sections highlighting differences or additional steps required for Linux environments.
Ensure screenshots and UI instructions are not exclusively tailored to Windows-only tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation for Azure Backup Server troubleshooting is heavily biased toward Windows environments. All examples, file paths, commands, and troubleshooting steps reference Windows-specific tools (e.g., Registry Editor, Windows Services, Windows Server Backup, Control Panel, Internet Explorer, Windows registry keys, Windows file paths). There are no examples, instructions, or even mentions of Linux or cross-platform scenarios, and all operational guidance assumes a Windows OS context.

Recommendations:

Add explicit statements about platform support (e.g., clarify if Azure Backup Server is Windows-only or if Linux is supported).
If Linux is supported, provide equivalent troubleshooting steps, file paths, and commands for Linux environments.
Include Linux-specific examples for agent installation, service management, and backup/restore operations.
Reference Linux tools (e.g., systemctl, journalctl, Linux file paths) where appropriate.
If certain features or steps are Windows-only, clearly label them as such and provide alternatives or guidance for Linux users.
Ensure parity in documentation structure: for every Windows example or instruction, provide a Linux equivalent where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on the Microsoft Azure Recovery Services (MARS) Agent, which is a Windows-only backup solution. All instructions, screenshots, and tool references are specific to Windows environments (e.g., MARS management console, %ProgramFiles% paths, Windows-style UI navigation). There are no Linux equivalents, examples, or mentions, and the documentation implicitly assumes the user is operating on Windows systems.

Recommendations:

Clearly state at the beginning of the documentation that the MARS Agent is only supported on Windows, and provide links to equivalent Azure Backup solutions for Linux (such as Azure Backup for Linux VMs or Azure Backup Server).
Where possible, add a comparison table or section outlining backup options for both Windows and Linux, with links to relevant documentation for Linux users.
If any cross-platform features exist (e.g., Azure Backup Reports, Azure Monitor integration), provide Linux-specific instructions or examples alongside the Windows ones.
Avoid using only Windows-specific terminology and paths without clarification; if the product is Windows-only, make this explicit to avoid confusion for Linux users.
For antivirus configuration, mention that the guidance is for Windows and provide a note or link for Linux-based backup agent antivirus configuration if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-centric backup tools (DPM, MABS, MARS) and providing navigation examples that focus on Windows Server workloads. There are no explicit Linux or cross-platform examples, and the terminology and links (e.g., 'backup-azure-manage-windows-server.md') suggest a primary focus on Windows environments. Linux equivalents or guidance are missing.

Recommendations:

Include explicit examples and navigation instructions for monitoring Linux-based backup workloads.
Mention and link to documentation for Linux backup agents or solutions supported by Azure Backup.
Balance references to Windows tools (DPM, MABS, MARS) with Linux-native or cross-platform backup solutions.
Add notes or sections clarifying how Linux workloads are monitored and any differences in portal experience.
Ensure that all examples and screenshots, if any, represent both Windows and Linux scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation primarily describes installation steps using the Azure Portal UI, which is platform-agnostic. However, in the 'Next steps' section, Azure PowerShell is listed before Azure CLI, ARM, Bicep, and Terraform, which may suggest a Windows-first or PowerShell-heavy bias. There are no explicit Linux-specific instructions or CLI examples in the main quickstart, and no mention of Linux-native tools or shell commands. The documentation does not provide command-line examples (e.g., Bash, Azure CLI) inline, which are commonly used on Linux systems.

Recommendations:

Provide Azure CLI (bash) examples directly in the quickstart steps, not just as a link in 'Next steps'.
List Azure CLI before Azure PowerShell in the 'Next steps' to reflect cross-platform parity.
Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and clarify any platform-specific requirements.
Include at least one example of installing the extension using Azure CLI or Bash script within the main instructions.
If screenshots are shown, consider including CLI output or terminal screenshots in addition to portal UI.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation for troubleshooting the Azure Backup (MARS) agent is heavily biased towards Windows environments. All examples, instructions, and troubleshooting steps are specific to Windows OS, tools, and patterns (e.g., MMC console, Internet Explorer, Task Scheduler, Registry Editor, vssadmin, PowerShell, Windows file paths, and Windows-specific error codes). There are no references to Linux environments, tools, or equivalent procedures, nor is it clarified that the MARS agent is Windows-only, which may confuse cross-platform users.

Recommendations:

Explicitly state early in the documentation that the MARS agent is only supported on Windows, if that is the case. If Linux support is planned or exists, provide equivalent troubleshooting steps for Linux.
Where possible, mention alternatives for Linux users, such as Azure Backup for Linux VMs, and link to relevant documentation.
Avoid assuming the use of Windows-only tools (e.g., Internet Explorer, Task Scheduler, Registry Editor) without clarifying OS requirements.
If the documentation is intended for a cross-platform audience, provide parallel troubleshooting steps or notes for Linux (or clarify the scope).
Add a section or callout for users seeking Linux backup solutions, directing them to appropriate Azure documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily Windows-centric, with all installation, configuration, and operational instructions assuming a Windows Server environment. Only Windows operating systems are listed as supported platforms, and all examples, tools, and commands (such as PowerShell cmdlets and registry edits) are specific to Windows. There is no mention of Linux support, nor are there any examples or guidance for Linux environments.

Recommendations:

Clearly state at the beginning of the documentation whether Linux is supported or not. If not, explain the reasons and provide alternatives for Linux users.
If Linux support is possible or planned, add equivalent Linux installation and configuration instructions, including supported distributions and prerequisites.
Provide examples using Linux-native tools and commands (e.g., bash, systemd, Linux file paths) where applicable.
If the product is Windows-only, consider linking to Azure-native backup solutions that support Linux workloads, and provide guidance for mixed-environment scenarios.
Ensure that any references to PowerShell, Windows registry, or Windows-specific features are either accompanied by Linux equivalents or clearly marked as Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively references Windows tools and workflows (Task Manager, Control Panel, Windows file paths) when troubleshooting Azure Backup monitoring issues. There are no examples or instructions for Linux environments, nor is there any mention of Linux equivalents or cross-platform considerations.

Recommendations:

Include troubleshooting steps for Linux-based Azure Backup agents, if supported.
Provide Linux command-line equivalents for process and service management (e.g., using 'ps', 'systemctl', or 'service' commands).
Show Linux file path examples alongside Windows paths.
Clearly state if the instructions only apply to Windows, and link to Linux-specific documentation if available.
Ensure parity in examples and guidance for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references Windows-based operating systems (Windows Server 2008/2012/2012 R2) and provides only Azure PowerShell scripts for determining OS family usage. There are no examples or guidance for Linux-based cloud services, nor are cross-platform tools or CLI alternatives mentioned. The migration recommendations focus solely on Windows OS families and .NET frameworks, omitting any Linux or open-source stack considerations.

Recommendations:

Include equivalent Azure CLI or Azure Cloud Shell examples, which are cross-platform and can be used on Linux, macOS, and Windows.
Explicitly state if the retirement notice only applies to Windows-based cloud services, or clarify the status for Linux-based services if applicable.
Provide guidance for users running Linux-based workloads, if supported, or direct them to relevant documentation.
Mention cross-platform tools and patterns (such as Azure Resource Manager templates or Bicep) where possible, instead of focusing solely on Windows-centric tools and scripting.
If PowerShell is required, note that PowerShell Core is available cross-platform, and provide installation instructions for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references Windows tools, services, and patterns (e.g., 'net stop dpmra', NT AUTHORITY\SYSTEM, MARS agent, Data Protection Manager), with no mention of Linux equivalents or support. All troubleshooting steps and terminology are specific to the Windows ecosystem, and there are no examples or guidance for Linux environments.

Recommendations:

Clarify early in the documentation whether Data Protection Manager is Windows-only, or if there are Linux-supported scenarios.
If Linux is supported, provide equivalent troubleshooting steps and commands for Linux environments (e.g., service management commands, agent installation, and log locations).
Where Windows-specific tools or patterns are mentioned (e.g., 'net stop dpmra', NT AUTHORITY\SYSTEM), offer Linux alternatives or explicitly state if not applicable.
Include examples and error resolutions for Linux-based workloads or agents, if supported.
Ensure parity in documentation structure by presenting Linux and Windows solutions side-by-side where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing detailed PowerShell examples for moving Recovery Services vaults, mentioning Windows update procedures before Linux, and omitting Linux-specific command-line examples. While the Azure CLI is mentioned, the PowerShell workflow is more thoroughly documented, and there is no parity in Linux shell or scripting guidance.

Recommendations:

Provide equivalent Bash or Linux shell examples alongside PowerShell for all command-line operations, especially for moving resources.
Ensure that Azure CLI examples are as detailed and prominent as PowerShell examples, including explanations of parameters and expected output.
When discussing VM prerequisites (such as updating certificates), present Linux instructions before or alongside Windows instructions, with explicit commands or links to common Linux distributions.
Include references to cross-platform tools and avoid assuming the administrator is using a Windows environment.
Review all procedural steps and ensure that Linux users are not required to infer their own workflows from Windows-centric guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by mentioning Windows-centric tools (System Center DPM, Windows Server, Azure Backup Server) prominently and providing a 'Back up a Windows Server' next step, without equivalent Linux-specific examples or guidance. While Linux is mentioned as a supported workload, there are no explicit Linux backup scenarios, tools, or walkthroughs provided. The focus on Windows tools and the absence of Linux-specific examples or parity in next steps may make Linux users feel less supported.

Recommendations:

Add explicit Linux backup scenarios and walkthroughs, such as 'Back up a Linux Server' or 'Back up a Linux VM', in the 'Next steps' section.
Mention Linux-compatible backup tools or agents where Windows tools (like MARS agent, DPM, Azure Backup Server) are referenced, or clarify their applicability to Linux.
Provide links to Linux-specific documentation or guides alongside Windows examples.
Ensure that examples and references to operating systems are balanced, mentioning Linux and Windows together where both are supported.
Review the documentation for opportunities to add Linux command-line or scripting examples, not just Windows/PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily biased toward Windows and PowerShell usage. All examples use PowerShell cmdlets, Windows file paths (e.g., C:\), and Windows-centric tools and workflows. Linux is only mentioned in passing, with no Bash, Azure CLI, or Linux-native examples provided. The documentation assumes the user is operating in a Windows environment, even for Linux VM scenarios.

Recommendations:

Provide equivalent Azure CLI and Bash examples for all PowerShell commands, especially for Linux users.
Use platform-agnostic file paths or provide both Windows (C:\) and Linux (/home/user/) path examples.
Include explicit instructions for restoring keys and secrets from Linux or macOS environments, not just Windows.
Mention and demonstrate cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell.
Reorder sections or examples so that Linux and Windows are given equal prominence, or clarify when steps are identical across 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 examples for deploying the ARM template, with no equivalent Azure CLI or Bash/Linux shell instructions. The prerequisites and deployment instructions focus on PowerShell, which is primarily associated with Windows environments, and do not mention or demonstrate how to perform the same steps on Linux or macOS systems. This may hinder accessibility for users on non-Windows platforms.

Recommendations:

Add equivalent Azure CLI (az) examples for deploying the ARM template, suitable for Linux/macOS users.
Explicitly mention that the deployment can be performed from any platform (Windows, Linux, macOS) and provide cross-platform instructions.
Where PowerShell is referenced, also provide Bash or shell script alternatives.
In the prerequisites, include installation instructions for Azure CLI and note its cross-platform compatibility.
Ensure that all code snippets are available in both PowerShell and CLI formats, and consider presenting CLI examples first or side-by-side to avoid implicit Windows prioritization.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias in several areas: Windows terminology and tools (e.g., 'Download Executable', registry edits, Windows Explorer) are mentioned before their Linux equivalents, and Windows-specific troubleshooting steps are more detailed. PowerShell is referenced in the 'Next steps' section before the Azure CLI. Some sections (e.g., registry changes for large disks) are Windows-only, while Linux equivalents are less detailed or appear later. The documentation assumes familiarity with Windows patterns and tools, and Windows steps are often described first.

Recommendations:

Alternate the order of Windows and Linux instructions throughout the document, or present both in parallel where possible.
Provide equally detailed troubleshooting steps for Linux as are given for Windows (e.g., registry edits vs. Linux config changes).
In 'Next steps', list Azure CLI and Linux-native tools before or alongside PowerShell.
Use neutral terminology (e.g., 'Download recovery script' instead of 'Download Executable') and clarify both OS options at each step.
Where Windows tools (e.g., Windows Explorer, registry) are referenced, provide Linux equivalents (e.g., file managers, relevant config files) with equal prominence.
Ensure that screenshots and examples are balanced between Windows and Linux environments.

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, screenshots, and command-line examples are specific to Windows tools (e.g., Microsoft Azure Backup snap-in, Windows Server Backup utility, wbadmin, Windows Recovery Environment). There are no references to Linux systems, tools, or equivalent processes, nor any mention of cross-platform applicability or limitations.

Recommendations:

Clearly state at the beginning that the procedure is only applicable to Windows Server, and provide a link or note about Linux/UNIX backup and restore options if available.
If Azure Backup supports Linux system state or similar functionality, add equivalent sections and examples for Linux, including commands (e.g., using rsync, tar, or Azure CLI), and describe the restore process for Linux servers.
If Linux is not supported for system state restore, explicitly mention this limitation to set user expectations.
Where possible, use cross-platform Azure Backup tools (such as Azure CLI or portal-based workflows) in examples, or at least reference them.
Consider providing a comparison table or FAQ about differences in backup/restore capabilities between Windows and Linux servers in Azure Backup.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation references both Azure CLI and Azure PowerShell for retrieving metrics, but PowerShell is mentioned alongside CLI without providing any Linux-specific examples or guidance. There are no Linux shell (bash) or cross-platform command-line examples, and the only explicit command-line tooling mentioned is PowerShell, which is Windows-centric. This may make Linux users feel secondary or unsupported.

Recommendations:

Provide explicit bash/Linux shell examples for retrieving metrics using Azure CLI, demonstrating parity with PowerShell.
When referencing command-line tools, list Azure CLI (which is cross-platform) before PowerShell, and clarify that PowerShell is optional or for Windows users.
Include notes or sections highlighting that all Azure CLI commands work on Linux, macOS, and Windows.
Avoid implying PowerShell is the default or primary method unless there is a clear technical reason.
Add screenshots or terminal snippets from Linux environments where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits Windows bias primarily 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 there is no mention of Linux-native tools or CLI-based deployment options. No Linux or cross-platform examples are provided, and the ordering places Windows tools before more neutral options.

Recommendations:

Include Azure CLI deployment instructions and links alongside or before PowerShell to provide a cross-platform alternative.
Mention cross-platform editors (such as VS Code) in addition to Visual Studio.
Ensure that examples and instructions are provided for both Windows and Linux environments where applicable.
Reorder the deployment options to list cross-platform tools (Azure CLI, Templates) before Windows-specific tools (PowerShell, Visual Studio).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows-centric backup solutions (MABS, DPM, MARS), with no mention of Linux backup agents, Linux-specific workflows, or examples. All tools, error messages, and recovery procedures are described for Windows environments, and PowerShell commands are referenced without Linux CLI or scripting equivalents. The documentation assumes the user is operating in a Windows environment and does not address Linux hybrid backup scenarios.

Recommendations:

Include information about Azure Backup support for Linux workloads, if available, and how security features apply to them.
Provide parallel examples and procedures for Linux-based backup agents or scripts, including CLI commands and error handling.
Mention Linux-compatible tools and workflows alongside Windows tools, rather than focusing exclusively on Windows solutions.
If certain features are not available for Linux, explicitly state this and provide guidance or alternatives for Linux users.
Add troubleshooting steps and error messages relevant to Linux environments.
Ensure parity in documentation structure, so Linux users can follow similar steps and benefit from the same security features where supported.

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 deployment instructions, referencing PowerShell as a prerequisite, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The deployment workflow and prerequisites are tailored to Windows users, with no guidance for Linux or macOS environments.

Recommendations:

Add Azure CLI deployment instructions alongside the PowerShell example, as Azure CLI is cross-platform and widely used on Linux and macOS.
In the prerequisites section, mention both Azure PowerShell and Azure CLI as supported options, with installation links for each.
Wherever PowerShell-specific instructions are given (e.g., right-click to paste), provide equivalent instructions for Bash or other common Linux shells.
Ensure that all code snippets and deployment steps are presented in both PowerShell and CLI/Bash formats, or clearly indicate which environments are supported.
Review the 'Next steps' section to ensure that CLI and PowerShell links are given equal prominence.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing only PowerShell command-line examples for scripting and automation, with no equivalent examples for Linux shells (such as Bash or Azure CLI). The use of PowerShell as the sole scripting interface assumes a Windows environment or familiarity with Windows tooling. There is no mention of Linux-native tools or cross-platform command-line options, and the documentation does not provide guidance for Linux users who may prefer Bash or the Azure CLI.

Recommendations:

Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and commonly used on Linux.
Explicitly mention that PowerShell Core is available cross-platform, but also provide Bash/Azure CLI equivalents for Linux users.
Include a 'Choose a client' tab for Azure CLI, similar to the existing tabs for PowerShell, REST API, and Portal.
Review all command snippets and ensure Linux users are not required to use Windows-specific tools or patterns.
Add notes or sections addressing any differences or prerequisites for Linux environments, such as authentication or module installation.

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, instructions, and tooling references are specific to Windows environments. There is no mention of Linux-based SQL Server VMs, nor are there any examples or instructions for Linux users. All account names, file paths, permissions, and automation scripts (PowerShell, SMB shares, NT SERVICE accounts) are Windows-specific. The documentation assumes the use of Windows authentication, Windows file system paths, and Windows-only tools such as SSMS and PowerShell, with no Linux alternatives or parity.

Recommendations:

Add explicit guidance and examples for SQL Server running on Linux-based Azure VMs, including differences in backup extension installation, service accounts, and file system paths.
Provide Linux command-line equivalents (e.g., bash scripts, sqlcmd usage on Linux, chown/chmod for permissions) alongside PowerShell and SSMS instructions.
Clarify which features or steps are Windows-only and provide alternative steps or note limitations for Linux users.
Reference Linux authentication and account management patterns (e.g., systemd service accounts, sudoers) where appropriate.
Include screenshots or terminal output relevant to Linux environments, not just Windows GUIs.
Update links and quickstart guides to include both Windows and Linux SQL Server VM creation and management.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes using Microsoft Azure Backup Server (MABS) and Data Protection Manager (DPM), both of which are Windows-only tools. All examples, screenshots, and workflows assume a Windows environment, with references to Windows-specific accounts (NTAuthority\System) and no mention of Linux or cross-platform alternatives. There are no Linux-specific instructions, examples, or parity notes, and the documentation implicitly assumes SQL Server is running on Windows.

Recommendations:

Explicitly state that MABS and DPM are Windows-only tools at the beginning of the documentation.
Provide guidance or links for backing up SQL Server on Linux (if supported by Azure Backup or other Microsoft tools), or clarify that Linux-based SQL Server instances are not supported by this workflow.
Include a comparison table or section outlining backup options for SQL Server on Linux, such as using Azure Backup agent, native SQL Server backup/restore commands, or third-party tools.
If possible, add Linux-specific examples or alternative workflows for organizations running SQL Server on Linux.
Mention any limitations or differences in backup support for SQL Server on Linux versus Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on SQL Server (a Microsoft/Windows-centric database) running on Azure VMs, with all examples and terminology tailored to SQL Server instances (e.g., 'mssqlserver', 'master'). There are no examples or guidance for restoring other database types (such as MySQL, PostgreSQL, or even SQL Server on Linux VMs). The documentation assumes the use of SQL Server tools and patterns, and does not address Linux-specific considerations or provide parity for Linux-based SQL Server deployments.

Recommendations:

Include explicit examples and notes for restoring SQL Server databases running on Linux-based Azure VMs, highlighting any differences in process, file paths, or prerequisites.
Clarify whether the documented CLI commands and workflows are applicable to SQL Server on Linux VMs, and if not, provide Linux-specific instructions or call out limitations.
If Azure Backup supports other database engines (e.g., MySQL, PostgreSQL) on Linux VMs, add sections or links to equivalent documentation for those scenarios.
When referencing file paths (e.g., '/home/sql/restoreasfiles'), clarify OS-specific conventions and provide both Windows and Linux path examples where relevant.
Avoid assuming the use of Windows tools or patterns (such as 'master' database, 'mssqlserver' instance names) without noting Linux differences or alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows environments, specifically on-premises Windows servers, and provides only Windows-specific tools, commands (PowerShell, wbadmin), and troubleshooting steps. There are no Linux equivalents or cross-platform considerations, and all examples and screenshots are Windows-centric.

Recommendations:

Clearly state in the introduction that System State Backup is only supported on Windows, if that is the case, and provide links to equivalent Linux backup solutions if relevant.
If Azure Backup or MARS Agent supports Linux in other scenarios, add a section or links to Linux-specific documentation for parity.
Where possible, provide parallel troubleshooting steps or references for Linux environments, or explicitly mention that the described procedures are not applicable to Linux.
Avoid assuming the use of Windows-only tools (like PowerShell, Server Manager) without noting alternatives or the lack thereof for Linux.
If the product is Windows-only, clarify this early and suggest alternative backup strategies for Linux users.

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 tool references are specific to Windows (e.g., MARS Agent, .exe installers, Windows Server versions, Windows-specific commands like SFC). There are no Linux equivalents, examples, or even mentions of Linux support or alternatives. The workflow, tools, and terminology are all Windows-centric, and Linux users are not addressed at all.

Recommendations:

Clearly state in the introduction that this guide is Windows-only, and provide a link to equivalent Linux backup documentation if available.
Add a section or cross-reference for Linux system backup to Azure, if supported, including relevant tools (e.g., Azure CLI, azcopy, rsync, or third-party agents).
If Azure Backup supports Linux system state or file backup, provide parallel instructions and screenshots for Linux environments.
Avoid using only Windows-specific terminology and tools (such as MARS Agent, .exe installers, SFC) without mentioning if or how Linux users can achieve similar results.
If Linux is not supported for system state backup, explicitly mention this limitation to set user expectations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily Windows-centric, referencing only Windows tools (such as Performance Monitor), Windows file paths, and Windows-specific troubleshooting steps. There are no Linux examples, tools, or guidance provided, and the language assumes the user is operating in a Windows environment throughout.

Recommendations:

Add equivalent troubleshooting steps and examples for Linux systems, including references to common Linux backup agents or methods supported by Azure Backup.
Include Linux performance monitoring tools (such as iostat, vmstat, top, sar, or dstat) and provide example commands for diagnosing bottlenecks.
Mention Linux file paths and log locations where relevant, or clarify if the Azure Backup agent is not supported on Linux.
If the Azure Backup agent is Windows-only, explicitly state this at the start of the documentation and provide links or references to Linux backup solutions supported by Azure.
Ensure that troubleshooting advice and recommendations are presented for both Windows and Linux environments, or clarify platform limitations.

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 troubleshooting steps and tools (e.g., services.msc, Control Panel, Event Viewer, regsvr32.exe, Visual C++ Redistributable) are described in detail, often with screenshots, while Linux equivalents are less detailed or omitted. Windows is frequently mentioned first, and PowerShell is referenced for operations like setting static IPs or cancelling backup jobs, with no equivalent Linux CLI or shell commands provided. Some troubleshooting steps and error resolutions are Windows-specific, with Linux guidance being more generic or less actionable.

Recommendations:

Provide equivalent Linux commands and tools for all troubleshooting steps (e.g., systemctl/service for agent status, journalctl/log file locations for logs, dpkg/rpm for package management).
Include Linux CLI examples (e.g., az CLI, shell commands) wherever PowerShell or Windows GUI steps are given.
Add screenshots or terminal output examples for Linux where Windows screenshots are used.
Ensure Linux troubleshooting steps are as detailed and actionable as Windows steps, including specific commands for checking and restarting services, managing dependencies, and handling agent/extension issues.
When listing steps or options, alternate the order or present Windows and Linux guidance in parallel rather than always leading with Windows.
Reference Linux-specific documentation and best practices alongside Windows links.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by frequently presenting Windows troubleshooting steps and tools (such as File Explorer, Server Manager, Disk Management, ISCSI initiator Properties) before or in more detail than their Linux equivalents. Windows-specific error messages and GUI workflows are described with screenshots, while Linux sections often refer users to external links or provide minimal command-line guidance. Some scenarios (e.g., deduplication, disk management) are only covered for Windows, with no Linux equivalents or detailed steps.

Recommendations:

Provide Linux troubleshooting steps and examples with equal detail and prominence as Windows, including command-line workflows for common tasks (e.g., mounting/unmounting disks, checking disk status, handling deduplication).
Include Linux-specific error messages and their resolutions directly in the documentation, not just as links.
Add screenshots or terminal output examples for Linux steps, similar to the Windows GUI screenshots.
When listing steps for both OSes, alternate the order or present them in parallel sections to avoid always placing Windows first.
For every Windows tool or feature mentioned (e.g., Disk Management, deduplication), mention the Linux equivalent (e.g., lsblk, mount, lvm, mdadm, file system deduplication tools) and provide usage instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references Windows-specific tools (Volume Shadow Copy Service - VSS) before mentioning the Linux equivalent (fsfreeze), and does not provide detailed Linux examples or guidance. Windows terminology and links (such as to the VM Agent and snapshot extension for Windows) are provided, but there are no equivalent Linux-focused links or instructions. Linux is only mentioned in passing, and Linux-specific backup considerations (such as pre/post scripts) are not elaborated.

Recommendations:

Provide equal detail for both Windows and Linux backup mechanisms, including links to Linux VM Agent and snapshot extension documentation.
List Linux tools (e.g., fsfreeze) before or alongside Windows tools (VSS) to avoid Windows-first ordering.
Include Linux-specific examples or scenarios, such as how crash-consistent backups interact with common Linux filesystems and applications.
Expand on Linux pre/post script usage and provide guidance or references for Linux users.
Ensure all references to extensions or agents include both Windows and Linux documentation links.

Create pull request

Bias Types:

⚠️ windows_only

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

This documentation page exclusively lists updates for the Azure Guest OS, which is based on Windows operating systems. All update references, KB articles, and product categories are for Windows components (e.g., .NET Framework, Internet Explorer, Windows Security, Servicing Stack, etc.). There are no references to Linux distributions, Linux update mechanisms, or Linux-specific security advisories. The documentation is entirely Windows-centric, with no mention of Linux guest OSes, their update cadence, or equivalent security patching processes.

Recommendations:

Add a clear statement at the top clarifying that this page only covers Windows-based Azure Guest OS images, and provide a link to equivalent documentation for Linux-based Azure VM images.
Provide a parallel table or section for Linux guest OSes, listing update advisories, CVEs, and patch release dates for supported distributions (e.g., Ubuntu, CentOS, Red Hat, SUSE).
Reference Linux update mechanisms (such as apt, yum, zypper) and security advisories (USN, RHSA, etc.) where appropriate.
If Azure Guest OS for Linux is not supported in this context, explicitly state this to avoid confusion for Linux users.
Ensure future documentation on Azure VM guest OS updates covers both Windows and Linux platforms with parity in detail and update tracking.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased toward Windows environments. All instructions, screenshots, and terminology are specific to the Microsoft Azure Recovery Services (MARS) Agent, which is a Windows-only tool. There are no references to Linux systems, no Linux command-line or GUI examples, and no mention of restoring files on non-Windows platforms. The documentation assumes the use of Windows features (snap-ins, desktop apps, ACLs in NTFS format) and does not provide parity for Linux users.

Recommendations:

Clearly state at the beginning of the documentation that the MARS Agent is only supported on Windows, if that is the case.
If Linux support is available via other Azure backup solutions (such as Azure Backup for Linux VMs or Azure CLI), provide links or references to those alternatives.
If Linux support is planned, add equivalent Linux instructions, including command-line examples and screenshots for restoring files on Linux systems.
Avoid using Windows-specific terminology (such as 'snap-in', 'desktop app', 'NTFS ACLs') without clarifying platform limitations.
Add a comparison table or section outlining supported platforms and tools for both Windows and Linux, helping users quickly find the relevant guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation, while mentioning both Windows and Linux VMs, demonstrates a Windows bias by providing PowerShell commands as the only example for identifying a VM's associated Key Vault, referencing BitLocker (Windows) before dm-crypt (Linux) in the ADE section, and omitting equivalent Linux/CLI commands or examples. There are no explicit Linux command-line examples or references to Linux-native tools, and the only command-line example is Windows PowerShell.

Recommendations:

Provide equivalent Azure CLI or Bash examples alongside PowerShell commands, especially for tasks like identifying the Key Vault associated with a VM.
When describing ADE, mention Linux (dm-crypt) and Windows (BitLocker) in parallel, and provide links to both Windows and Linux disk encryption documentation equally.
Ensure that all procedural steps that reference command-line actions include both Windows (PowerShell) and Linux (CLI/Bash) variants.
Add Linux-specific troubleshooting links and examples where relevant.
Review the order of OS mentions to avoid always listing Windows first, and strive for parity in example depth and detail.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias, especially in the certificate import section, where Windows PowerShell and Windows Server UI instructions are presented first and in greater detail, including screenshots, before Linux instructions. The Linux section is less detailed and refers users to external documentation for specifics. Additionally, the use of Windows-specific tools and UI elements (e.g., Certificate Import Wizard) is emphasized, and Windows command-line options are highlighted alongside Linux, but Windows is often presented first.

Recommendations:

Present Linux and Windows instructions in parallel or alternate which comes first to avoid always prioritizing Windows.
Provide equally detailed, step-by-step Linux instructions, including screenshots where possible, for tasks such as certificate import.
Include examples for a wider range of Linux distributions (not just Ubuntu/Debian and RHEL/Fedora/CentOS), or at least link directly to official documentation for each.
Where Windows-specific tools or UI are mentioned (e.g., Certificate Import Wizard), mention Linux GUI alternatives if available (such as GNOME Certificates or KDE's certificate manager).
Ensure that all command-line examples (such as AzCopy) are equally detailed for both Linux and Windows, and clarify any differences in syntax or behavior.
Avoid language that implies Windows is the default or primary platform (e.g., 'On a Windows system, you can...'), and instead use neutral phrasing like 'On Windows...' and 'On Linux...'.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing detailed PowerShell examples before CLI examples, using Windows-specific tools and patterns (such as PowerShell cmdlets and Windows time zone handling), and offering more comprehensive step-by-step guidance for PowerShell users. Linux-specific considerations, shell examples, or parity in depth of CLI instructions are missing.

Recommendations:

Provide equivalent Bash (Linux shell) examples alongside PowerShell for all command-line operations, especially for scripting and automation scenarios.
Ensure CLI (az) examples are as detailed as PowerShell, including parameter explanations and sample JSON payloads for policy creation.
Include notes or sections addressing any OS-specific prerequisites or differences, such as file path formats, environment variables, or scheduling nuances.
If screenshots or UI steps are OS-agnostic, clarify this; otherwise, provide Linux desktop screenshots where appropriate.
Explicitly mention that both Windows and Linux VMs are supported, and highlight any differences in backup behavior or requirements.
Add troubleshooting tips or links specific to Linux VM backup scenarios.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by only providing individual file restore instructions for Windows Server VMs, omitting Linux VM scenarios. It references Windows-specific features (e.g., registry keys for configuration) and does not mention or provide parity for Linux-based VMs or tools. The workflow and terminology are tailored to Windows environments, with no guidance for Linux users.

Recommendations:

Add explicit instructions or notes for restoring individual files from Linux VMs, or clarify if this is unsupported.
If Linux file-level restore is not supported, state this limitation clearly and provide alternative guidance or workarounds.
Include examples or screenshots involving Linux VMs where possible, or at least acknowledge their usage and limitations.
When referencing configuration changes (such as registry keys), provide equivalent steps for Linux environments if applicable, or note their absence.
Ensure that recovery workflows and terminology are inclusive of both Windows and Linux VM scenarios.

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-specific tools (VSS) and workflows are described in greater detail and are mentioned before Linux equivalents. PowerShell is referenced for restore operations, but no CLI or Linux-native automation examples are provided. Linux backup consistency relies on custom scripting, but no example scripts or detailed guidance are included, unlike the explicit Windows VSS integration. Overall, Linux users receive less actionable guidance and fewer concrete examples.

Recommendations:

Provide parallel Linux CLI and automation examples wherever PowerShell is referenced (e.g., for restoring VMs with managed disks).
Include example pre/post scripts for common Linux workloads to help users achieve application-consistent backups.
Mention Linux tools (e.g., fsfreeze, LVM snapshots) explicitly and describe their role in the backup process, similar to how VSS is described for Windows.
Ensure that Linux guidance is as detailed and actionable as Windows guidance, including troubleshooting steps and best practices.
When listing options or processes, present Windows and Linux approaches side by side, rather than always listing Windows first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a noticeable Windows bias. Troubleshooting steps and error resolutions frequently reference Windows-specific tools (e.g., Services.msc, Event Viewer, regedit, command prompt, VSS, BitLocker, registry edits, icacls, MSIEXEC), and many examples or commands are provided only for Windows. PowerShell and Windows command-line instructions are given for several operations, while equivalent Linux commands or procedures are often missing or only briefly mentioned. In several sections, Windows solutions are described in detail before Linux alternatives, and some error resolutions lack Linux-specific guidance altogether.

Recommendations:

For every Windows-specific troubleshooting step (e.g., using Services.msc, Event Viewer, registry edits), provide equivalent Linux instructions (e.g., systemctl/service commands, journalctl/syslog, relevant config files).
Where PowerShell or Windows command prompt commands are given, include corresponding Bash or shell commands for Linux VMs.
When referencing Windows tools (e.g., VSS, BitLocker, MSIEXEC), clarify their Linux equivalents or note if the issue is Windows-only.
Ensure Linux examples are present and as detailed as Windows examples, especially in error troubleshooting sections.
When listing steps for both OSes, present them in parallel or clearly separated sections, rather than Windows-first.
Add more Linux-focused troubleshooting scenarios (e.g., SELinux/AppArmor, systemd service management, disk mounting issues) where relevant.
Review all error codes and ensure Linux-specific guidance is included where applicable, not just for a few select errors.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily Windows-centric, with all instructions, screenshots, and tooling (Server Manager, PowerShell cmdlets, ReFS, Windows Server versions) focused exclusively on Windows environments. There are no Linux examples, alternatives, or mentions of cross-platform support, and Windows-specific tools and patterns are presented as the default and only option.

Recommendations:

Clearly state early in the documentation whether Azure Backup Server and Modern Backup Storage are Windows-only, or if there is any Linux support or roadmap.
If Linux support exists or is planned, provide equivalent Linux instructions, examples, and screenshots (e.g., using Linux file systems, CLI tools, or relevant management consoles).
If the product is Windows-only, explicitly mention this limitation at the top of the page to set user expectations.
Where PowerShell is used, note if there are any cross-platform PowerShell Core options or REST APIs that could be used from Linux.
Consider adding a comparison table or FAQ about platform support to help users quickly understand OS compatibility.

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 Windows Server as the supported OS, uses Windows-specific paths (C:\, D:\), and only provides instructions and screenshots for Windows tools and interfaces. There are no Linux equivalents or examples, and PowerShell is the only command-line tool mentioned. The installation process, prerequisites, and troubleshooting are all described solely for Windows, with no mention of Linux support or alternatives.

Recommendations:

Clarify early in the documentation whether Azure Backup Server supports only Windows or if Linux is also supported. If Linux is not supported, state this explicitly.
If Linux support exists or is planned, provide parallel instructions, examples, and screenshots for Linux environments, including shell commands and Linux filesystem paths.
Include Linux-based prerequisites and installation steps, such as required packages, domain joining alternatives, and storage configuration.
Offer troubleshooting steps and command-line tools relevant to Linux (e.g., Bash scripts, systemd services) if applicable.
Balance the order of presentation so that, where both platforms are supported, Linux and Windows instructions are given equal prominence.

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 tools (PowerShell) for VM creation from restored disks, linking to Windows OS disk swap documentation, and providing more detailed guidance for Windows scenarios. Linux-specific instructions are minimal and appear after Windows content, with Linux restore steps condensed to a single section and lacking concrete examples or commands.

Recommendations:

Provide equivalent Linux CLI (az CLI, Bash) examples for restoring VMs from disks, alongside or before PowerShell examples.
Include links to Linux OS disk swap documentation, not just Windows.
Expand the 'Restore an encrypted Linux VM' section with step-by-step instructions and command-line examples (e.g., using az CLI or ARM templates).
Ensure that Linux and Windows procedures are presented in parallel, with equal detail and visibility.
Avoid referencing Windows tools (like PowerShell) as the only automation method; always mention cross-platform alternatives.

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. The 'Deploy a protected VM using a Resource Manager template' section links only to a Windows VM template, with no Linux equivalent provided. Additionally, automation guidance references PowerShell without mentioning CLI or Bash alternatives. While both Windows and Linux quick-create links are present, Windows is listed first, and Linux-specific automation or template examples are missing.

Recommendations:

Provide parallel examples and links for Linux VMs, such as a Resource Manager template for deploying and backing up a Linux VM.
Include automation instructions using Azure CLI or Bash scripts alongside PowerShell, ensuring Linux administrators have clear guidance.
When referencing quick-create guides, alternate the order or present Windows and Linux equally to avoid implicit prioritization.
Explicitly mention that all backup features and steps apply equally to Linux VMs, or note any differences.
Audit screenshots and UI walkthroughs to ensure they are not Windows-centric, or provide Linux-relevant visuals where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides a PowerShell example for configuring snapshot retention but does not include equivalent instructions or examples for Linux users (e.g., using Azure CLI or REST API). The only command-line automation shown is via PowerShell, which is primarily a Windows tool. There is no mention of Linux-specific tools or parity in scripting approaches, and the PowerShell section appears before any mention of cross-platform methods.

Recommendations:

Add equivalent Azure CLI examples for configuring snapshot retention, as Azure CLI is cross-platform and widely used on Linux.
Include REST API instructions or examples for users who may automate backup configuration outside of PowerShell or the Azure portal.
Explicitly mention that PowerShell is available on Linux and macOS, or clarify when examples are cross-platform.
Ensure that all automation and scripting instructions are presented in a platform-neutral way, or provide both Windows (PowerShell) and Linux (Azure CLI/bash) examples side by side.
Consider adding a section or note for Linux administrators highlighting supported tools and recommended workflows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation exclusively describes backup and recovery procedures using Microsoft Azure Backup Server, which is a Windows-based tool. All instructions, screenshots, and workflows are based on the Azure Backup Server console, with no mention of Linux-based alternatives, command-line options, or cross-platform tools. There are no examples or guidance for Linux VMs or file systems, nor any reference to Linux-native backup tools or scripting. The documentation assumes a Windows-centric environment throughout.

Recommendations:

Include explicit guidance for backing up and recovering files from Linux-based Azure Stack VMs, such as using Azure Backup agent for Linux or native Linux backup tools.
Provide command-line examples (e.g., Bash scripts, az CLI commands) for Linux environments alongside or in place of GUI-based, Windows-only workflows.
Mention any limitations or differences when protecting Linux workloads, and link to relevant Linux backup documentation.
Add screenshots or walkthroughs for Linux backup scenarios, if supported.
Clarify in the introduction that the described process is Windows-centric, and provide a section or links for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation exhibits a strong Windows bias. All detailed examples, supported workloads, and recovery scenarios are focused on Windows operating systems and applications (e.g., Windows Server, SQL Server, Exchange, SharePoint). Linux is only mentioned as a guest OS within Windows/Hyper-V/VMware environments, with no native Linux installation or agent support described. Recovery options for Linux are limited to entire VM restores, while Windows supports item-level recovery. Windows-specific tools and patterns (e.g., NTFS, VSS, Control Panel, Visual C++ redistributable) are referenced throughout, with no Linux equivalents or alternatives provided.

Recommendations:

Provide parity in documentation by including Linux-native backup and recovery scenarios, not just Linux as a VM guest.
Offer item-level recovery options or clearly state limitations for Linux workloads, and suggest workarounds if possible.
Include Linux-specific tools, filesystems (e.g., ext4, xfs), and backup agent installation instructions where applicable.
List Linux examples and scenarios alongside Windows in all relevant tables and sections, not as an afterthought.
Reference Linux management patterns (e.g., systemd, cron, shell commands) where Windows tools (e.g., Control Panel, VSS) are mentioned.
Clarify any limitations or roadmap for improved Linux support in MABS, so Linux users can plan accordingly.

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, tools, and examples assume a Windows Server context, with exclusive references to Windows-specific tools (e.g., CMD, Registry Editor, NT AUTHORITY\SYSTEM, Windows file paths, and Windows services). There are no Linux equivalents, nor is there any mention of Linux-based SharePoint deployments or Azure Backup Server support for Linux. The documentation does not address cross-platform scenarios or provide parity for Linux administrators.

Recommendations:

Explicitly state whether Microsoft Azure Backup Server (MABS) and SharePoint farm protection are supported or unsupported on Linux. If unsupported, clarify this early in the documentation.
If any Linux-based scenarios are possible (e.g., for other workloads or future support), provide parallel instructions, examples, and tool references for Linux environments.
Where possible, use platform-agnostic language and clarify when steps are Windows-specific.
Add a section or note addressing Linux users, either to direct them to alternative solutions or to explain current limitations.
If MABS is Windows-only, consider linking to Azure-native backup solutions or third-party tools that support Linux workloads.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation includes a dedicated PowerShell example for retrieving tokens from the managed identity endpoint, but does not provide equivalent Linux shell (bash/curl) examples. The PowerShell example uses Windows-specific tools (Invoke-RestMethod, PowerShell environment variable syntax), and there is no mention of Linux or cross-platform command-line alternatives. This may make it less accessible for Linux users or those working in non-Windows environments.

Recommendations:

For every PowerShell example, provide an equivalent bash/curl example for Linux/macOS users.
Explicitly mention that Azure CLI and HTTP GET examples are cross-platform, and clarify any OS-specific considerations.
Avoid using only Windows-specific tools (like PowerShell) in code samples; always provide parity with common Linux tools.
Where environment variables are referenced, show both Windows (e.g., $env:VAR) and Linux (e.g., $VAR) syntax.
Consider adding a section or tab for 'Bash' or 'Linux shell' alongside 'PowerShell' in code sample tabsets.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows environments. All examples, workflows, and tools referenced are specific to Windows Server (e.g., Windows Server Backup, WinRE, PowerShell cmdlets, Windows file paths). There is no mention of Linux or cross-platform support, nor are any Linux equivalents or examples provided. The documentation assumes the reader is operating in a Windows-only environment.

Recommendations:

Clearly state early in the documentation whether Azure Backup Server supports Linux system state or bare-metal recovery, and if not, provide links to relevant Linux backup documentation.
If Linux is supported, add equivalent Linux workflows, examples, and tool references (e.g., using rsync, tar, or Linux-native backup agents).
Provide parity in command-line examples, showing both PowerShell/Windows and Bash/Linux commands where applicable.
Reference Linux file paths and configuration files alongside Windows paths.
If certain features are Windows-only, explicitly call this out in the prerequisites and limitations section.
Consider including a comparison table of supported features for Windows and Linux to set clear expectations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several ways: variable assignment in CLI examples uses PowerShell syntax (e.g., $DiskId = ...), which is not portable to Linux/macOS shells; references to PowerShell and Windows tools appear in related content and permissions assignment sections; and there is a lack of explicit Linux/bash shell examples or guidance, which may confuse non-Windows users.

Recommendations:

Provide all CLI variable assignment examples in both PowerShell and bash syntax, or use bash syntax by default for cross-platform compatibility (e.g., DiskId="..." instead of $DiskId = ...).
Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and clarify any shell-specific syntax.
Include Linux/bash-specific instructions or notes wherever PowerShell syntax or Windows tools are mentioned.
In 'Next steps' and 'Related content', ensure parity by linking to Linux/bash-based guides (e.g., 'Restore Managed Disk using Azure CLI on Linux/macOS').
Avoid using Windows/PowerShell variable assignment as the only example; if both are shown, present bash first or side-by-side.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows environments, specifically referencing Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All instructions, screenshots, and terminology are based on Windows UI patterns and tools, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for Linux-based SQL Server deployments or backup workflows.

Recommendations:

Explicitly state that MABS is a Windows-only solution and clarify support limitations for Linux-based SQL Server instances.
Provide guidance or references for backing up SQL Server on Linux (if supported), including alternative tools or Azure-native backup options.
Include examples or links for command-line/scripted backup and recovery workflows that could be run on Linux (e.g., using az CLI, REST API, or other cross-platform tools).
If Linux is not supported, add a clear note at the top of the page to inform users and suggest alternative backup strategies for Linux SQL Server deployments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation for Microsoft Azure Backup Server (MABS) consistently prioritizes Windows environments, referencing Windows Server and Windows-specific features and tools throughout. There is a lack of Linux-specific examples, instructions, or parity in feature descriptions. Windows tools (e.g., registry keys, PowerShell cmdlets, ReFS, Hyper-V) are mentioned exclusively, and Linux workloads or backup scenarios are not addressed. The documentation assumes a Windows-centric deployment and omits guidance for Linux-based workloads or administrators.

Recommendations:

Add explicit sections or notes about Linux workload support, if available, including supported distributions and limitations.
Provide Linux-specific examples for backup, restore, and agent installation, including command-line instructions for common distributions.
Mention Linux equivalents when discussing Windows tools (e.g., registry keys vs. configuration files, PowerShell vs. shell scripts).
Clarify whether features such as item-level recovery, parallel backups, and immutable vaults are available for Linux workloads, and provide usage instructions if so.
Include a support matrix that clearly lists both Windows and Linux workloads, with feature parity and differences highlighted.
If Linux is not supported, explicitly state this early in the documentation to set expectations for cross-platform users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation primarily focuses on the Azure portal workflow and, where automation is mentioned, references PowerShell before CLI. There are no explicit Linux or cross-platform command-line examples within the main content, and scripting guidance is biased toward PowerShell with CLI as a secondary mention. No Linux-specific tools, shell scripts, or guidance are provided, and the 'Next steps' section lists PowerShell before CLI. This ordering and lack of Linux-first or parity examples indicate a subtle Windows bias.

Recommendations:

When referencing automation or scripting, present Azure CLI examples alongside or before PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
Explicitly mention that both PowerShell and CLI are supported, and provide equal visibility to both in the main workflow steps, not just as links.
Include example CLI commands inline for key operations (e.g., configuring backup, assigning roles) to improve accessibility for Linux users.
If scripts are referenced, ensure both PowerShell and Bash (or shell) script templates are available and linked.
In the 'Next steps' and similar lists, alternate or randomize the order of PowerShell and CLI to avoid reinforcing a Windows-first perception.
Consider a short section or callout for Linux users, clarifying that all operations can be performed from Linux using the Azure CLI.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page for Azure Backup demonstrates a Windows bias by primarily referencing Windows-centric tools (such as the Microsoft Azure Recovery Services (MARS) agent, DPM, and Azure Backup Server), mentioning Windows/Hyper-V before Linux/VMware, and not providing explicit Linux or cross-platform examples for on-premises backup scenarios. Linux-specific backup agents or instructions are not mentioned for on-premises workloads, and the examples and terminology are more familiar to Windows administrators.

Recommendations:

Include explicit references to Linux backup tools or agents (if supported), and provide guidance for backing up Linux-based on-premises servers.
Present examples for both Windows and Linux platforms when describing backup scenarios, especially for on-premises workloads.
Avoid listing Windows/Hyper-V before Linux/VMware unless there is a technical reason; strive for parity or alternate the order.
Clarify whether the MARS agent or other backup agents support Linux, and if not, suggest alternatives for Linux environments.
Add links or references to documentation that addresses Linux backup scenarios, including command-line or scripting examples relevant to Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation assumes SQL Server is running on Windows VMs and only describes the use of Windows-specific extensions (AzureBackupWindowsWorkload, NT Service accounts, SqlIaaSExtension). There are no instructions or examples for SQL Server running on Linux VMs, nor any mention of Linux-specific considerations or tools. The documentation is Windows-centric both in technical details and in the absence of Linux parity.

Recommendations:

Explicitly state whether the tutorial applies only to Windows-based SQL Server VMs or provide equivalent instructions for SQL Server on Linux VMs.
Include details about backup support, required extensions, and service accounts for SQL Server on Linux VMs (if supported).
Add Linux-specific examples, screenshots, and troubleshooting steps where applicable.
Clarify any differences in agent/extension installation, permissions, and backup/restore workflows for Linux-based SQL Server VMs.
If Linux is not supported, clearly state this at the top of the documentation to set expectations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a moderate Windows bias. PowerShell is consistently mentioned before Azure CLI and REST API as a non-portal client for monitoring and automation. The examples and references to custom dashboards and automation scripts prioritize PowerShell, which is traditionally associated with Windows environments. Additionally, several workload types and tools (such as DPM and Azure Backup Server) are Windows-centric, and there is no explicit mention or example of Linux-specific backup agents or Linux-oriented monitoring workflows.

Recommendations:

Ensure that CLI examples are presented alongside or before PowerShell examples, especially in sections discussing automation or custom dashboards.
Include explicit references to Linux-based backup scenarios, such as using the Azure CLI on Linux or monitoring Linux VMs.
Where possible, provide Linux shell (bash) script examples in addition to PowerShell.
Clarify that Azure CLI and REST API are fully cross-platform and provide links to Linux-specific guidance.
Mention Linux-compatible backup agents or tools if available, and ensure parity in documentation for both Windows and Linux workloads.

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: it references Windows-specific backup agents and tools (such as SCDPM and Azure Backup Server), mentions on-premises Windows Server registration explicitly, and highlights PowerShell as a primary automation interface. There is little to no mention of Linux equivalents, Linux-specific backup scenarios, or cross-platform parity in examples or tool references. Linux/Unix systems and their management tools are not addressed, and the documentation does not provide guidance or examples for Linux users.

Recommendations:

Include explicit references to Linux-based backup scenarios, such as registering on-premises Linux servers or using Linux backup agents if supported.
Provide examples and guidance for managing Azure Backup and RBAC using Bash/Azure CLI on Linux, not just PowerShell.
Mention Linux/Unix systems alongside Windows when discussing on-premises registration and supported platforms.
Clarify whether features and role requirements apply equally to Linux workloads, and add notes or tables for any differences.
Where PowerShell is referenced, also provide equivalent Azure CLI or Bash commands, and link to cross-platform tooling documentation.
Add a section or FAQ addressing common Linux backup management questions in Azure.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented towards Windows environments, specifically SQL Server on Windows VMs. All directory paths in examples use Windows-style paths (e.g., C:\SQLfiles\Default.ldf), and there is no mention of Linux-based SQL Server VMs or examples relevant to Linux. The documentation assumes the use of Windows containers and file systems, and does not provide parity or guidance for Linux users.

Recommendations:

Include explicit guidance and examples for restoring SQL Server databases on Linux-based Azure VMs, if supported.
When showing directory paths or file system operations, provide both Windows and Linux path examples (e.g., C:\SQLfiles\Default.ldf and /var/opt/mssql/data/Default.ldf).
Clarify in the prerequisites and introduction whether the procedure applies only to Windows-based SQL Server VMs or if Linux is supported.
If Linux is not supported, state this clearly at the beginning of the documentation.
If Linux is supported, add Linux-specific REST API request body examples, including appropriate file paths and container naming conventions.
Mention any differences in restore behavior or requirements between Windows and Linux SQL Server VMs.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias in several ways. Although the main focus is on Azure CLI (which is cross-platform), the explanations and object model discussions repeatedly reference PowerShell as the default or primary method for managing backup policies. File path examples (e.g., .\OSSPolicy.json) use Windows-style backslashes, and there are no explicit Linux or macOS command-line examples or file path conventions. The documentation describes PowerShell object manipulation in detail, but only briefly mentions that Azure CLI users must use files, without providing Linux-specific guidance or examples. There is also a tendency to mention PowerShell and Windows-centric approaches before or instead of Linux equivalents.

Recommendations:

Provide explicit Linux/macOS shell examples alongside or instead of Windows/PowerShell examples, especially for file paths (e.g., use ./OSSPolicy.json instead of .\OSSPolicy.json).
When discussing object manipulation, offer parity in explanation for both PowerShell (objects) and CLI (JSON/files), including sample jq or sed commands for Linux users.
Avoid referring to PowerShell as the 'default' or primary method; instead, present both PowerShell and CLI approaches neutrally.
Include notes or callouts for Linux/macOS users regarding file path conventions, shell differences, and any required environment setup.
Where possible, use cross-platform syntax in examples, or provide both Windows and Linux variants.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively covers Windows-based Guest OS families (Windows Server 2022, 2019, 2016, 2012 R2, 2012, 2008 R2 SP1) and related .NET Framework versions, with no mention of Linux-based Guest OS options, examples, or parity. All configuration strings, compatibility notes, and update processes are Windows-centric. There are references to Windows-specific tools (Visual Studio, RDP), and the terminology assumes Windows as the only platform. No Linux equivalents, distributions, or instructions are provided.

Recommendations:

Explicitly state in the introduction whether Linux-based Guest OS options are available for Azure Cloud Services (classic) and, if not, clarify this limitation.
If Linux Guest OS support exists or is planned, add equivalent sections for Linux Guest OS families, including release tables, update processes, and compatibility notes.
Provide parity in tooling recommendations (e.g., suggest cross-platform tools or Linux alternatives to Visual Studio and RDP where applicable).
Include examples or references for managing and updating Linux-based roles if supported, or link to relevant Linux documentation.
Review and update terminology to be inclusive of both Windows and Linux where possible, or clearly scope the document to Windows if Linux is not supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. When mentioning command-line options for moving Backup vaults, it lists PowerShell before CLI, and does not provide explicit Linux/bash examples or references. The only command-line tool mentioned by name is PowerShell, with no Linux-specific scripting or shell guidance. All procedural examples use the Azure portal UI, which is cross-platform, but the lack of parity in command-line references and examples may disadvantage Linux users.

Recommendations:

When referencing command-line tools, mention Azure CLI before or alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux.
Provide explicit bash/Azure CLI command examples for key operations (e.g., moving Backup vaults), not just PowerShell.
Where scripts or automation are referenced, clarify that both PowerShell and bash/CLI scripts may need updating after resource moves.
Consider adding a section or callout for Linux users, highlighting any differences or providing Linux-specific guidance.
Ensure that all command-line documentation is balanced, with equal prominence and detail for both Windows (PowerShell) and Linux (CLI/bash) users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page exhibits a Windows-centric bias. It assumes SQL Server VMs are Windows-based, references Windows-specific tools and extensions (e.g., AzureBackupWindowsWorkload, NT Service accounts), and provides connectivity troubleshooting scripts only for Windows. There are no examples or guidance for Linux-based SQL Server VMs, nor mention of Linux-specific requirements or differences.

Recommendations:

Explicitly state whether the instructions apply to both Windows and Linux SQL Server VMs, or clarify if only Windows is supported.
If Linux-based SQL Server on Azure VMs is supported, add parallel sections or notes for Linux, including prerequisites (e.g., Linux VM Agent, .NET requirements if any), service account equivalents, and extension installation.
Provide Linux-specific troubleshooting scripts or guidance, similar to the Windows connectivity test scripts.
Reference Linux documentation for VM extensions and agent installation where appropriate.
When mentioning tools or extensions (e.g., AzureBackupWindowsWorkload, NT Service\AzureWLBackupPluginSvc), clarify Linux equivalents or note if not applicable.
Include CLI or shell-based examples for Linux where PowerShell or Windows UI steps are described.
Review and update all screenshots and step-by-step instructions to indicate any OS-specific differences.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows-specific tools and extensions (such as AzureBackupWindowsWorkload and NT Service accounts), and by not mentioning or providing instructions for Linux-based SQL Server VMs. There are no examples or guidance for backing up SQL Server running on Linux VMs, nor is there any discussion of Linux-specific requirements or differences.

Recommendations:

Explicitly state whether the documented process supports both Windows and Linux SQL Server VMs, or clarify if it is Windows-only.
If Linux SQL Server VMs are supported, provide parallel instructions and screenshots for Linux, including any differences in agent/extension installation, service accounts, and permissions.
Mention Linux-specific tools, extensions, or service accounts if applicable, or provide links to Linux backup documentation.
Add a section comparing Windows and Linux support, highlighting any limitations or differences.
Ensure that terminology and screenshots do not assume a Windows environment unless it is a documented prerequisite.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation assumes a Windows-centric environment for SQL Server Always On Availability Groups, with no mention of Linux-based SQL Server deployments. All instructions, terminology, and backup tooling (such as the workload backup extension and Recovery Services vault registration) implicitly target Windows VMs. There are no examples, notes, or guidance for Linux-based SQL Server AGs, which are supported by SQL Server and Azure. The documentation also refers to concepts and error codes typical of Windows deployments, and does not address Linux-specific considerations or tools.

Recommendations:

Explicitly state whether the guidance applies to both Windows and Linux SQL Server AGs, or clarify any limitations.
Add sections or notes describing how to back up SQL Server AGs running on Linux VMs, including any differences in agent installation, registration, and supported features.
Provide Linux-specific examples, such as using shell commands for agent installation, or referencing Linux file paths and system services.
Mention any differences in error codes, troubleshooting steps, or backup/restore workflows for Linux-based AGs.
Ensure parity in terminology and instructions so that Linux administrators can follow the documentation without ambiguity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias. All examples, file paths, and troubleshooting steps reference Windows-specific tools, directories (e.g., C:\Program Files), and services (e.g., Control Panel, Local Security Policy). The extension required is named AzureBackupWindowsWorkload, and there is no mention of Linux-based SQL Server VMs or their backup processes. PowerShell is referenced as the automation tool for re-registration, with no mention of Bash or CLI alternatives. Antivirus exclusions, service accounts, and permissions are all described in a Windows context, with no Linux equivalents or guidance.

Recommendations:

Add explicit guidance and examples for SQL Server running on Linux VMs, including Linux file paths, service management, and extension installation.
Provide Linux-specific troubleshooting steps, such as how to check service status, configure permissions, and manage antivirus exclusions on Linux.
Include Bash/CLI commands alongside PowerShell for automation and scripting tasks.
Reference Linux equivalents for Windows tools (e.g., Control Panel, Local Security Policy) or note when a step is Windows-only.
Clarify in the introduction whether the documentation applies only to Windows VMs, or expand scope to cover Linux VMs if supported.
Where only Windows is supported, explicitly state this to avoid confusion for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows-first bias: Windows scenarios, tools, and examples are presented before Linux equivalents, and some features (such as file/folder-level backup with the MARS agent, DPM, or MABS) are only available for Windows. PowerShell is mentioned as the primary automation tool for restore operations, with no equivalent Linux/CLI examples. Windows-specific tools and backup agents (MARS, DPM, MABS) are referenced throughout, with Linux support often noted as 'not supported' or requiring workarounds. Linux-specific guidance is limited and less detailed, and some restore and backup scenarios lack Linux parity or examples.

Recommendations:

Provide Azure CLI and Bash examples alongside PowerShell for backup and restore operations, especially in sections where PowerShell is referenced for VM creation or disk attachment.
Present Linux and Windows scenarios in parallel tables or sections, rather than listing Windows first and Linux as an afterthought.
Expand Linux-specific documentation, including detailed steps for file-level backup/restore, and clarify any workarounds or alternatives for Linux users.
Where features are Windows-only (e.g., MARS agent, DPM, MABS), clearly state the lack of Linux support up front and suggest alternative approaches for Linux workloads.
Include more Linux-focused use cases and examples, such as restoring to Linux VMs, handling LVM/RAID, and using custom scripts for app-consistent backups.
Review all automation and scripting guidance to ensure Linux/CLI parity, not just PowerShell.
Where possible, prioritize cross-platform/OS-agnostic features (such as agentless backups) in the documentation structure and examples.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation consistently lists PowerShell as the first automation method in all tables, and provides PowerShell examples for every operation, regardless of whether the workload is cross-platform or Linux-specific (e.g., SAP HANA). This prioritization of PowerShell, a Windows-centric tool, and the lack of explicit mention of Linux-native scripting (such as Bash) or Linux-specific nuances, demonstrates a Windows-first and PowerShell-heavy bias. The documentation also refers to 'PowerShell' as a primary automation tool, which is more familiar to Windows users, even though Azure CLI is cross-platform and often preferred on Linux.

Recommendations:

Alternate the order of automation methods in tables, sometimes listing Azure CLI before PowerShell, especially for Linux-centric workloads (e.g., SAP HANA, PostgreSQL).
Explicitly mention that Azure CLI commands and examples are cross-platform and can be used on Linux, macOS, and Windows.
Where possible, provide Bash script examples or reference Bash usage for Linux administrators, not just PowerShell.
Add a note or section clarifying the cross-platform nature of Azure CLI and REST API, and highlight any Linux-specific considerations or best practices.
For workloads that are primarily Linux-based (e.g., SAP HANA), consider omitting PowerShell where not supported and emphasizing CLI or REST API.
Ensure that documentation for automation tasks does not assume familiarity with PowerShell, and provide parity in guidance for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a clear Windows bias. Windows-based backup methods (MARS agent, DPM, MABS) are described in detail and appear first in tables and explanations, while Linux support is often listed as 'not supported' or only as a secondary note. There are no Linux-specific examples or tools mentioned, and the documentation focuses heavily on Windows tools and backup agents. Linux support is generally limited to VM-level backup via extensions, with no direct on-premises Linux backup options provided.

Recommendations:

Provide Linux-specific backup examples and workflows where possible, especially for on-premises scenarios.
List Linux support and options alongside Windows in all tables, not as afterthoughts or exclusions.
Include parity in tool descriptions: if a Windows tool (like MARS agent) is mentioned, clarify Linux alternatives or explicitly state roadmap plans.
Add practical examples or references for configuring app-consistent backups on Linux (e.g., sample custom scripts).
Avoid always listing Windows options first; alternate or group by scenario rather than OS.
Clarify the limitations for Linux support and, where possible, provide guidance or workarounds for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation for the MARS agent is exclusively focused on Windows environments. All examples, supported operating systems, and instructions reference only Windows or Windows Server. There is no mention of Linux or other non-Windows platforms, and all tools and commands (e.g., PowerShell, MMC, DISM.exe, registry edits) are Windows-specific. The support matrix, installation instructions, and troubleshooting steps are all tailored to Windows, with no Linux equivalents or alternatives provided.

Recommendations:

Explicitly state in the introduction that the MARS agent is only available for Windows, and provide guidance or links for Linux backup alternatives (such as Azure Backup for Linux VMs or Azure Backup Server support for Linux).
If Linux support is planned, add a section outlining current limitations and a roadmap for Linux compatibility.
Where Windows-specific tools or commands are mentioned (e.g., PowerShell, registry edits), clarify that these are not applicable to Linux, and suggest equivalent Linux procedures if available.
Add a comparison table or FAQ highlighting the differences in backup support and tooling between Windows and Linux environments in Azure.
Provide links to documentation for Linux backup solutions (such as Azure VM backup for Linux or third-party agents) to help Linux users find relevant information.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows-centric bias. All operational examples, file paths, and tool references (e.g., PsExec, NT AUTHORITY\SYSTEM, C:\Program Files, SSMS) are specific to Windows environments. There are no instructions, examples, or even mentions of restoring SQL Server databases on Linux-based Azure VMs, nor are Linux file paths, permissions, or tools discussed. The only restore tooling referenced is SQL Server Management Studio (SSMS), which is Windows-only, and the use of Windows command-line utilities is assumed throughout.

Recommendations:

Add explicit instructions and examples for restoring SQL Server on Linux-based Azure VMs, including relevant file paths (e.g., /var/opt/mssql/), permissions, and service management commands.
Provide Linux equivalents for all Windows-specific tools and commands (e.g., use 'sudo' and Linux file permissions instead of NT AUTHORITY\SYSTEM and PsExec).
Mention and provide examples for cross-platform tools such as Azure CLI and SQLCMD, and clarify how to perform restores using these tools on Linux.
Avoid assuming the presence of SSMS; suggest alternatives like Azure Data Studio or SQLCMD for Linux users.
When referencing file locations or commands, present both Windows and Linux variants side by side.
Explicitly state any limitations or differences for SQL Server on Linux in Azure VMs, if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily biased toward Windows environments. All operational instructions, command-line examples, and tool references (such as PowerShell, mountvol.exe, diskshadow.exe, psexec.exe, Net Share, Windows Explorer, and VSS) are specific to Windows. There are no examples, instructions, or considerations for Linux environments, nor are cross-platform alternatives mentioned. The documentation assumes the use of Windows-only tools and patterns throughout.

Recommendations:

Clearly state early in the documentation that MABS is a Windows-only product, if that is the case. If not, provide equivalent instructions and examples for Linux environments.
Where possible, provide cross-platform alternatives or note the lack thereof. For example, if certain backup or restore operations can be performed using SQL tools available on Linux, include those examples.
Avoid assuming the use of Windows Explorer or Windows-specific GUI tools; suggest command-line or cross-platform alternatives where applicable.
If the use of Windows tools (e.g., mountvol.exe, diskshadow.exe, psexec.exe) is unavoidable, explain their purpose and suggest any open-source or Linux equivalents, or explicitly state that these steps are only possible on Windows.
For SQL Server backup/restore operations, include examples using sqlcmd or other tools available on Linux, if supported.
If Linux is not supported at all, make this explicit in the prerequisites or introduction to avoid confusion for cross-platform administrators.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (such as Visual Studio, CSPack.exe, and the Azure Compute Emulator), providing only Windows command-line examples, and mentioning Windows-specific paths and UI (e.g., Certificates tab in Visual Studio). There are no Linux or cross-platform alternatives or examples provided for packaging, deploying, or managing Azure Cloud Services (extended support).

Recommendations:

Include explicit instructions and examples for Linux and macOS users, such as how to install and use CSPack or equivalent tools on non-Windows platforms.
Clarify whether CSPack and the Azure Compute Emulator are available or supported on Linux/macOS, and if not, suggest alternative workflows (such as using Azure CLI, Azure DevOps, or Docker-based builds).
Provide cross-platform command-line examples (e.g., Bash, Azure CLI) alongside Windows CMD/PowerShell examples.
Avoid referencing Windows UI elements (like Visual Studio tabs) as the only method for configuration; instead, describe how to perform these actions using cross-platform tools or editors.
Add a section or note summarizing the platform support matrix for all tools and steps, and direct Linux/macOS users to relevant resources or workarounds.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias towards Windows environments by referencing PowerShell and Windows-centric tools (such as MARS agent, DPM/MABS) for automation and hybrid backup scenarios, without providing equivalent Linux examples or mentioning Linux-native tools. There are no explicit Linux CLI or shell script examples, and the hybrid backup section focuses solely on Windows-based agents. Automation is often described in the context of PowerShell, and video tutorials reference PowerShell procedures, with no mention of Bash, Linux CLI, or Linux backup agents.

Recommendations:

Include Linux-specific examples and guidance alongside PowerShell, such as Bash scripts or Azure CLI commands for common backup operations.
When discussing automation, provide parity by showing both PowerShell and Bash/CLI procedures for tasks like auto-retry of failed jobs.
In hybrid backup sections, mention and link to documentation for Linux backup agents (such as Azure Backup Server for Linux or third-party solutions) and clarify support for Linux workloads.
Ensure that references to tools like MARS, DPM, and MABS are balanced with Linux equivalents or alternatives, and clarify their platform support.
Add explicit Linux workload backup scenarios, including any prerequisites, limitations, and best practices for Linux systems.
When listing supported workloads and features, clearly indicate Linux support and provide links to relevant Linux documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is exclusively focused on Windows environments, both in its intent and technical instructions. All examples, prerequisites, and installation steps are for Windows machines only, with explicit references to Windows tools (e.g., .exe installers, Windows-specific wizards, and settings). There is no mention of Linux support, alternatives, or parity, and the MARS agent is presented as a Windows-only solution.

Recommendations:

Clearly state in the introduction and prerequisites whether the MARS agent is supported only on Windows, and if so, provide guidance or links for Linux backup solutions (such as Azure Backup for Linux VMs or other agents).
If Linux support is available or planned, add equivalent Linux installation and configuration instructions, including command-line examples and references to Linux tools.
Avoid using 'Windows machines' as the default or only example; instead, use more inclusive phrasing or provide parallel sections for Linux where applicable.
Mention any limitations or differences in backup capabilities between Windows and Linux environments, and direct users to appropriate documentation for Linux scenarios.
If the MARS agent is not available for Linux, explicitly state this and suggest alternative backup strategies for Linux workloads.

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-based tool, and provides only GUI-based instructions relevant to Windows environments. There are no Linux equivalents, command-line alternatives, or cross-platform considerations mentioned. The terminology and screenshots are specific to Windows, and there is no indication that Linux is supported or how to manage telemetry on non-Windows systems.

Recommendations:

Clarify whether MABS is Windows-only or if there are Linux-compatible components. If Linux is supported, provide equivalent instructions for managing telemetry settings on Linux systems.
Include command-line examples (e.g., PowerShell for Windows, Bash for Linux) for managing telemetry settings, if applicable.
If only Windows is supported, explicitly state this at the beginning of the documentation to set expectations for Linux users.
If telemetry can be managed via configuration files or scripts, document the file locations and syntax for both Windows and Linux environments.
Ensure that any future updates to the documentation consider parity between Windows and Linux instructions, where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias: Windows workloads and tools are described in detail and always appear first, with extensive coverage of Windows-specific features (NTFS, VSS, ReFS, deduplication, system state, bare metal, etc.). Linux is only mentioned as a VM guest, with no details on native Linux workload protection, agent installation, or file-level recovery. Windows tools and patterns (e.g., Volume Shadow Copy Service, NTFS, Windows Management Framework) are referenced exclusively, and there are no Linux command-line or configuration examples. Recovery options are consistently limited to Windows VMs/files, with Linux only supporting full-VM recovery.

Recommendations:

Provide parity by including Linux-native workload protection details, such as supported distributions, file systems, and backup/recovery scenarios beyond VM-level.
Add Linux-specific examples for agent installation, configuration, and recovery (e.g., command-line steps for popular distributions).
Clarify limitations and alternatives for Linux environments (e.g., file-level recovery, application-aware backup for Linux workloads).
Mention Linux tools and patterns where relevant (e.g., LVM snapshots, ext4/xfs support, Linux backup agents).
Reorganize documentation to present Windows and Linux support side-by-side where possible, rather than relegating Linux to a separate, minimal section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias: all workload examples, supported platforms, and backup/recovery scenarios are centered on Windows operating systems and Microsoft applications (e.g., Windows Server, SQL Server, Exchange, SharePoint, Hyper-V). Linux is only mentioned as a guest VM, with limited support (entire VM backup only, no file-level recovery), and there are no examples or details for Linux workloads, filesystems, or application backups. Windows-specific technologies (NTFS, VSS, ReFS, Windows Management Framework) are referenced exclusively, with no Linux equivalents or alternatives discussed.

Recommendations:

Add explicit support matrix rows for Linux distributions, including supported filesystems (e.g., ext4, xfs) and backup/recovery capabilities (file-level, application-aware, etc.).
Provide examples and details for Linux workloads, such as how to back up and recover Linux VMs, files, and applications.
Clarify any limitations or differences in Linux support (e.g., snapshot consistency, file-level recovery) and reference relevant Linux tools or technologies (e.g., LVM snapshots, rsync, etc.) where appropriate.
If Linux support is limited by design, state this clearly and provide links to alternative Azure backup solutions for Linux workloads.
Avoid referencing only Windows-specific tools and patterns (e.g., VSS, NTFS, Windows Management Framework) without mentioning Linux equivalents or noting their absence.

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 and workflows. PowerShell and Visual Studio are mentioned as primary deployment options, with no explicit mention of Linux CLI or cross-platform alternatives. Example links and tabs reference Windows environments, and there are no Linux-specific instructions or screenshots.

Recommendations:

Include Azure CLI examples for scaling and deployment, as Azure CLI is cross-platform and widely used on Linux.
Provide Linux-specific instructions or notes where workflows differ from Windows (e.g., environment variables, shell commands).
Add screenshots or terminal examples from Linux environments alongside Windows/portal images.
Mention cross-platform tools (e.g., Azure CLI, Bicep, ARM templates) before or alongside Windows-specific tools like PowerShell and Visual Studio.
Ensure that quickstart and reference links include Linux tabs or alternatives, not just Windows or PowerShell.

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 provided extensively and in detail, and Windows-specific tools and terminology (e.g., BitLocker, C: drive, PowerShell cmdlets) are used throughout. While Linux is mentioned, Linux-specific instructions, examples, or command-line usage are minimal or absent. The documentation assumes familiarity with Windows paradigms and tools, and Linux considerations are often relegated to notes or limitations rather than being integrated into the main workflow.

Recommendations:

Add explicit Linux command-line examples (e.g., bash scripts, Linux CLI usage) alongside PowerShell, especially for disk identification and management.
Provide Linux-specific troubleshooting steps and error messages, similar to those given for Windows/PowerShell.
When discussing OS-specific limitations or requirements (e.g., BitLocker for Windows, dm-crypt for Linux), present them in parallel and with equal detail.
Include Linux-first or Linux-equal examples in all sections, not just as notes or afterthoughts.
Clarify any differences in workflow or prerequisites for Linux VMs (e.g., how to install and use lsblk/lsscsi, how to identify LUNs on Linux, how to check backup status from the Linux VM).
Balance the order of presentation: do not always mention Windows/PowerShell first; alternate or present both together.
Where possible, provide sample outputs or screenshots from Linux VMs in the portal/UI sections.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows environments, specifically referencing the MARS agent, which is a Windows-only backup solution. All operational instructions and screenshots are based on the MARS console, a Windows GUI application. There are no Linux equivalents, examples, or mentions of cross-platform support. Automation references (such as Set-OBMachineSetting) are for Windows PowerShell only. The documentation does not acknowledge or provide alternatives for Linux users.

Recommendations:

Clearly state at the beginning that the MARS agent and this workflow are Windows-only, and provide links to equivalent Linux backup solutions (such as Azure Backup for Linux VMs or Azure CLI-based backup).
If possible, include parity documentation for Linux-based backup agents and how to securely store their credentials/passphrases in Azure Key Vault.
Where automation is discussed, mention whether similar automation is available for Linux (e.g., via shell scripts or Azure CLI) or clarify that it is not supported.
Add a comparison table or section outlining backup options for both Windows and Linux, with links to relevant documentation for each platform.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates bias towards Windows environments by referencing a PowerShell script for undeleting file shares and not providing equivalent CLI or Linux-native examples. The only script-based recovery method mentioned is a PowerShell script, and there is no mention of using Azure CLI, Bash, or cross-platform tools for these operations. This may disadvantage users on Linux or macOS systems who do not use PowerShell.

Recommendations:

Provide equivalent Azure CLI and Bash script examples for undeleting file shares and other operations, alongside the existing PowerShell script.
When referencing scripts or automation, mention both PowerShell and cross-platform (CLI/Bash) options, or clarify if a feature is only available via PowerShell.
Ensure that links to scripts or documentation include both Windows and Linux/macOS instructions where possible.
Explicitly state platform compatibility for any scripts or tools referenced, and avoid assuming the user is on Windows.

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 mention or provide examples for Linux-native tools, Azure CLI, or shell scripting. All command-line automation is shown using PowerShell, which is traditionally a Windows-centric tool, despite its cross-platform support. There are no bash or Linux CLI examples, and the documentation does not address Linux administrators' workflows.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell operations, as Azure CLI is widely used on Linux.
Include bash/shell scripting examples where appropriate, especially for automation scenarios.
Explicitly mention cross-platform compatibility for PowerShell, or clarify if the steps are supported on Linux.
Consider providing a 'Linux administrator' tab or section, outlining steps and tools familiar to Linux users.
Reference Linux-native tools or patterns where relevant, such as scripting with cron or using SSH for remote operations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides detailed instructions for managing soft delete of VM backups via the Azure Portal and Azure PowerShell, but does not mention or provide examples for Linux command-line tools (such as Azure CLI) or shell scripting. PowerShell is emphasized as the only scripting/automation interface, which is more familiar to Windows users. There are no Linux-specific examples or guidance, and the documentation does not mention parity with Linux tools.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell operations, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that all operations can be performed from Linux environments using Azure CLI or REST API, and provide links or examples.
Where scripting is shown, offer both PowerShell and Bash/Azure CLI snippets side by side.
Review screenshots and UI instructions to ensure they are not Windows-centric (e.g., avoid referencing right-click if not applicable on all platforms).
Include a section or note on automation from Linux/macOS environments, referencing relevant tools and documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily Windows-centric, explicitly stating that only Windows Server operating systems are supported and that Linux is not supported. All examples, requirements, and supported tools (e.g., PowerShell) are Windows-specific, with no mention of Linux alternatives or parity. The documentation does not provide any Linux commands, tools, or guidance, and the feature set is described solely in the context of Windows environments.

Recommendations:

Clearly state early in the document that Linux is not supported, and provide a link to any roadmap or alternatives for Linux users if available.
If partial Linux support is planned or available in preview, mention it and provide relevant instructions or limitations.
When referencing tools (e.g., PowerShell), note the absence of Linux/CLI support and suggest workarounds or alternatives where possible.
Include a comparison table or section outlining feature parity (or lack thereof) between Windows and Linux for Azure SQL Server Backup.
If Linux support is not planned, suggest alternative backup strategies for SQL Server on Linux in Azure VMs, or link to relevant documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows PowerShell commands (e.g., Get-AzRole) as the only CLI example for checking instance status, listing PowerShell and Visual Studio as deployment options without mentioning cross-platform or Linux-native tools, and omitting any Bash, Azure CLI, or Linux-specific instructions. The ordering of deployment options also places Windows-centric tools before cross-platform alternatives.

Recommendations:

Provide Azure CLI (az) command examples alongside or instead of PowerShell, especially for tasks like checking instance status (e.g., az vm list or az cloud-service role-instance list).
Explicitly mention that ARM templates and REST API methods are cross-platform and can be used from any OS.
Include Bash or shell script examples where relevant, particularly for Linux users.
In the 'Next steps' section, list cross-platform tools (Azure CLI, ARM template) before Windows-specific tools (PowerShell, Visual Studio), or group them by platform.
Where PowerShell is mentioned, 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 is heavily focused on Windows environments, providing only Windows-specific instructions (such as registry edits and KB articles) and omitting any guidance for Linux systems. All configuration steps, troubleshooting, and examples are tailored exclusively to Windows, with no mention of Linux equivalents or cross-platform considerations.

Recommendations:

Add a section describing how to ensure TLS 1.2 is enabled and enforced on Linux-based systems, including relevant configuration files (e.g., OpenSSL, GnuTLS, or system-wide crypto policies).
Provide Linux command-line examples (such as using openssl or update-alternatives) to verify and configure TLS support.
Include troubleshooting steps and error messages relevant to Linux environments.
Reference Linux-specific documentation or Microsoft Learn pages related to Azure Backup on Linux.
Clarify in the introduction or prerequisites if the guidance is only applicable to Windows, or explicitly state cross-platform support and differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows/Powershell bias by providing scripts and automation examples exclusively in Powershell, referencing scripts with 'powershell' in their filenames, and not offering equivalent CLI or Bash scripts for Linux/macOS users. There are no Linux-specific instructions or examples, and automation guidance is Windows-centric.

Recommendations:

Provide equivalent Azure CLI or Bash scripts for all Powershell script references, ensuring Linux/macOS users have parity.
When linking to scripts (e.g., for finding Recovery Services vaults or undeleting file shares), offer both Powershell and Azure CLI/Bash alternatives, or clearly indicate cross-platform options.
Avoid using only Windows-centric terminology (such as 'Powershell script') in main troubleshooting steps; instead, refer to 'automation script' and specify both Windows and Linux options.
Include explicit Linux/macOS troubleshooting steps or notes where relevant, especially for command-line or scripting tasks.
Review all automation and scripting guidance to ensure cross-platform compatibility and representation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned as a primary automation tool alongside the Azure portal, while Linux-native tools (such as Bash or Azure CLI) are less emphasized or mentioned after PowerShell. Visual Studio, a Windows-centric IDE, is referenced as a deployment tool, and there is no mention of cross-platform alternatives (e.g., VS Code, GitHub Actions). Some instructions and examples focus on Windows tools and patterns, with Linux equivalents either omitted or de-emphasized.

Recommendations:

Ensure Azure CLI is mentioned equally or before PowerShell in all tool lists and instructions, as it is cross-platform and widely used on Linux.
Add explicit Linux/Bash command examples where PowerShell is referenced, especially for key vault creation and virtual network setup.
Reference Visual Studio Code or other cross-platform editors in addition to Visual Studio, or clarify when Visual Studio is optional.
Where possible, provide ARM/Bicep template examples as the primary automation method, as these are platform-agnostic.
Include a note or section on deploying and managing Cloud Services (extended support) from Linux/macOS environments, with links to relevant documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows environments by primarily referencing PowerShell scripts for privilege assignment and not providing equivalent Linux/Unix command-line (e.g., Bash, psql) examples. The mention of PowerShell occurs first and most prominently, with alternatives like PG admin or PSQL tool only briefly mentioned and without concrete examples. No Linux-specific instructions or screenshots are provided, and the overall workflow assumes a Windows-centric administrative approach.

Recommendations:

Provide explicit Linux/Unix command-line examples (e.g., using Bash and psql) for all steps where PowerShell is referenced, especially for granting privileges to database users.
When mentioning PowerShell, always mention Linux/Unix alternatives in parallel, not as an afterthought.
Include screenshots or terminal output from Linux environments where applicable.
Clarify that all steps can be performed from both Windows and Linux environments, and provide parity in instructions.
Consider providing downloadable scripts for both PowerShell and Bash/psql.
Review all references to administrative tools to ensure Linux-native tools are given equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page is generally cross-platform and CLI-focused, but it exhibits subtle Windows bias. It references PowerShell as an alternative in the introduction and links to a PowerShell-specific guide before mentioning Linux alternatives. Some terminology and linked resources (such as zone-pinned VM documentation) default to Windows examples or documentation. There are no explicit Linux command examples, and the only mention of Linux is in the context of prerequisites, not in the main workflow or examples.

Recommendations:

Provide explicit Linux/Bash shell examples alongside or before PowerShell references, especially in introductory sections.
When referencing alternative tooling (such as PowerShell), also provide links to Linux-specific guides or clarify that the CLI commands are cross-platform.
Ensure that all linked documentation (e.g., for availability zones, VM creation) includes both Windows and Linux examples, or links to both.
Where possible, use neutral terminology (e.g., 'VM' instead of 'Windows VM') and avoid defaulting to Windows-centric documentation.
Add a brief section or callout confirming that all CLI commands work identically on Linux, macOS, and Windows, and provide troubleshooting tips for common Linux shell issues (such as line continuation differences).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes upgrading the Microsoft Azure Recovery Services (MARS) agent in a Windows environment. All instructions, screenshots, and tool references (e.g., Remote Desktop, DPM Console) are Windows-specific. There are no examples, instructions, or even mentions of Linux systems or command-line alternatives. The documentation assumes the use of Windows tools and patterns throughout.

Recommendations:

Clarify early in the documentation that the MARS agent is only supported on Windows, if that is the case. If Linux is supported, provide equivalent instructions and examples for Linux environments.
If the agent is Windows-only, explicitly state this in the introduction to avoid confusion for Linux administrators.
If cross-platform support is planned or available, include Linux installation and upgrade instructions, using Linux-native tools (e.g., SSH, shell commands) and screenshots.
Where possible, provide PowerShell and command-line alternatives to GUI steps, which can help both Windows Server Core and potential cross-platform scenarios.
Add a section addressing common questions about non-Windows environments, clarifying support boundaries.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page for Azure Backup service release notes exhibits some Windows bias. Several features and updates reference Windows-specific tools (such as MARS agent and Microsoft Azure Backup Server), and Windows platforms are mentioned explicitly (e.g., 'protect and run on Windows Server 2022'). There is a lack of explicit Linux or cross-platform examples, and Linux equivalents are not mentioned alongside Windows tools. In sections where command-line or scripting interfaces are referenced, PowerShell is sometimes mentioned without equal mention of Bash/CLI. Overall, the documentation assumes or highlights Windows environments and tooling, with limited attention to Linux or cross-platform scenarios.

Recommendations:

Where Windows-specific tools (e.g., MARS agent, Microsoft Azure Backup Server) are mentioned, clarify their platform limitations and provide equivalent Linux-native solutions or alternatives if available.
When referencing scripting or automation (e.g., PowerShell), always mention Azure CLI and/or Bash alternatives, and provide example commands for both Windows and Linux environments.
Include explicit references to Linux support in backup scenarios, especially for VM and database workloads that are commonly run on Linux (e.g., PostgreSQL, MySQL, SAP HANA).
Add notes or links to documentation that address Linux-specific backup agents, tools, or best practices.
Review the documentation for opportunities to use neutral, cross-platform language and to ensure Linux users are equally addressed in all relevant sections.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page is heavily focused on Windows and PowerShell. All deployment examples use Azure PowerShell, with no Azure CLI or Bash/Linux shell examples provided inline. The 'Create a VM' section links only to Windows VM creation guides, and the overall workflow assumes familiarity with Windows tools and patterns. Linux users are not given equivalent step-by-step guidance, and Linux command-line tools are not mentioned or demonstrated.

Recommendations:

Add parallel Azure CLI (az) examples for all deployment steps, with Bash syntax, to provide Linux parity.
In the 'Create a VM' section, link to both Windows and Linux VM creation quickstarts.
Where PowerShell is mentioned, clarify that Azure CLI is also supported and provide links or tabs for both.
Review terminology and instructions to ensure they are not Windows-specific (e.g., avoid assuming use of PowerShell or Windows-only tools).
Consider using tabbed content blocks to allow users to select their preferred platform (PowerShell, Azure CLI, Portal).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation consistently lists Azure PowerShell (a Windows-centric tool) before Azure CLI in configuration tables, and provides PowerShell-specific parameter names and links. There is a notable emphasis on PowerShell as a primary automation/configuration method, which is more familiar to Windows users. While Azure CLI is mentioned, it is always listed after PowerShell, and there are no Linux-specific tools or shell examples (e.g., Bash scripts). No explicit Linux commands, patterns, or troubleshooting are provided.

Recommendations:

Alternate the order of Azure CLI and PowerShell in tables and examples, sometimes listing CLI first to avoid Windows-first bias.
Provide explicit Bash shell or Linux-native command examples where relevant, especially for CLI usage.
Include links to both PowerShell and CLI documentation equally, and ensure parity in depth and clarity.
Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
Where possible, add Linux-specific notes or troubleshooting tips, especially for common configuration scenarios.
Consider including a 'Platform considerations' section outlining any differences or tips for Linux vs. Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several areas. Browser recommendations are Windows-centric, with Windows browsers mentioned first and Mac as a secondary consideration. Keyboard layout configuration instructions are provided only for Windows, with no equivalent guidance for Linux or Mac users. The documentation references Windows-specific tools and patterns (such as RDP and Windows keyboard shortcuts) without offering parallel Linux examples or alternatives. There are no explicit Linux command-line or SSH examples, nor instructions for setting up keyboard layouts or other OS-specific tasks on Linux.

Recommendations:

Provide browser recommendations and instructions for Linux users, including supported browsers and any known issues.
Include instructions for configuring keyboard layouts on Linux and Mac, not just Windows.
When referencing RDP, also mention SSH and provide examples for both Windows and Linux clients.
Add parity in native client connection instructions, ensuring both Windows and Linux workflows are described.
Where Windows-specific shortcuts or settings are mentioned, provide equivalent steps for Linux and Mac where possible.
Explicitly state support and any limitations for Linux VMs and Linux client environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing PowerShell-based tutorials (as indicated by the '-powershell.md' suffix in linked tutorials), and does not provide equivalent Linux/bash/CLI examples. The terminology and workflow examples focus on Windows-centric tools and patterns, with no mention of Linux shell, bash, or cross-platform command-line alternatives. This may limit accessibility for users on Linux or macOS platforms.

Recommendations:

Provide parallel step-by-step tutorials using Azure CLI, Bash, or cross-platform scripting tools alongside PowerShell examples.
Explicitly mention and link to Linux-compatible tools and workflows where possible.
Ensure that all code samples and automation scripts are available in both PowerShell and Bash/CLI formats.
Add a section or callout for Linux/macOS users, highlighting any platform-specific considerations or differences.
Review and update tutorial file names and links to reflect cross-platform parity (e.g., '-powershell.md' and '-bash.md' versions).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by prioritizing RDP (a Windows protocol) in both the UI and command-line examples, listing it before SSH. There are no explicit Linux-specific instructions or examples, such as using native SSH clients or Linux credential formats. The documentation assumes familiarity with RDP and Windows-style authentication, and does not provide Linux/Unix-specific guidance or screenshots.

Recommendations:

Provide Linux-specific examples, such as connecting from a Linux terminal using SSH, including sample commands and credential handling.
Balance the order of protocol presentation: alternate or start with SSH (commonly used for Linux VMs) before RDP.
Include screenshots or walkthroughs from both Windows and Linux environments, demonstrating the connection process from each.
Clarify credential requirements for both Windows (username/password) and Linux (username/SSH key) scenarios.
Mention and link to Linux-native tools (e.g., OpenSSH client) and how they interact with Azure Bastion.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows environments. All examples, templates, and verification steps assume Windows VMs, Windows Server as the domain controller, and Windows-specific tools (such as Local Group Policy Editor and PowerShell). There are no instructions or examples for configuring Kerberos with Linux VMs, Linux-based domain controllers (such as Samba/FreeIPA), or using Linux-native tools. The ARM template provisions only Windows VMs, and all automation scripts are PowerShell-based.

Recommendations:

Add parallel instructions and examples for Linux VMs, including how to configure Kerberos authentication for Linux-based systems accessed via Bastion.
Provide guidance for deploying and configuring a Linux-based domain controller (e.g., Samba/FreeIPA) and joining Linux VMs to the domain.
Include Linux command-line examples (e.g., using kinit, realm, or sssd) for verifying Kerberos authentication.
Offer an alternative ARM/Bicep template or scripts that provision Linux VMs and automate their domain join and Kerberos configuration.
Reference Linux documentation and tools alongside Windows ones, and avoid assuming Windows as the default platform.
Clarify any Azure Bastion limitations regarding Linux Kerberos support, if applicable, and document workarounds or roadmap.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows VMs and tools first, providing keyboard shortcut examples only for Windows VMs, and mentioning Windows-specific ports and behaviors before Linux equivalents. There are no detailed Linux-specific examples or instructions, and Linux user scenarios are not equally represented in the connection or troubleshooting guidance.

Recommendations:

Provide Linux-specific examples alongside Windows examples, such as keyboard shortcuts for Linux desktops when accessed via Bastion.
List Linux and Windows ports together or alternate their order to avoid always mentioning Windows first.
Include screenshots or descriptions of what users should expect when connecting to Linux VMs, not just Windows.
Add troubleshooting tips or notes relevant to Linux users, such as clipboard or keyboard behavior differences.
Ensure that references to creating VMs, connecting, and managing are balanced between Windows and Linux, with equal detail and prominence.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias, especially in the certificate/key vault steps, where only PowerShell commands are provided for key vault and certificate management. There are no equivalent examples for Linux users (e.g., using Azure CLI or Bash). The use of PowerShell is assumed, and Windows-centric tools and patterns (such as .cspkg packaging and RDP extensions) are referenced without Linux alternatives or guidance. The documentation does not provide parity for Linux users in critical steps.

Recommendations:

For every PowerShell example, provide an equivalent Azure CLI (az) or Bash example suitable for Linux/macOS users, especially for key vault and certificate operations.
Mention Azure CLI and Bash as supported options in the prerequisites and throughout the guide.
Clarify that .cspkg packaging and RDP extensions are Windows-centric, and provide guidance or alternatives for Linux-based deployments if available.
Reorder or parallelize instructions so that Windows and Linux approaches are presented together, rather than defaulting to Windows/PowerShell first.
Add a note or section addressing Linux/macOS users, highlighting any differences or additional steps they may need.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. In the prerequisites, the link to the Windows VM quickstart is listed before the Linux VM quickstart. In the required inbound ports section, the Windows port (3389) is listed before the Linux port (22). In the 'Connect to a VM' section, keyboard shortcut examples are provided only for connecting to Windows VMs, with no equivalent Linux examples or discussion of Linux-specific connection nuances. There are no explicit Linux command-line or SSH examples, and the only OS-specific details are for Windows.

Recommendations:

Alternate the order of Windows and Linux references throughout the documentation, or list Linux first in some sections to balance representation.
In the 'Connect to a VM' section, provide examples or notes for connecting to Linux VMs, such as SSH session behaviors, keyboard shortcuts, or clipboard usage.
Include Linux-specific tips or troubleshooting steps, especially for users connecting from Linux or Mac clients.
Ensure parity in all examples and explanations, such as providing both RDP (Windows) and SSH (Linux) connection walkthroughs.
Where keyboard shortcuts are discussed for Windows, add equivalent information for Linux VMs (e.g., how to send signals like Ctrl+Alt+Del to a Linux VM, if relevant).

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 configuration method before Azure CLI, which is more commonly used on Linux. There are no explicit Linux or SSH client examples, and the documentation does not mention Linux tools or workflows, focusing instead on Windows-centric tools and patterns.

Recommendations:

Include explicit Linux/SSH client examples for accessing Azure VMs via Bastion.
Present Azure CLI instructions before or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
Mention and provide examples for Linux-native tools (e.g., SSH from a Linux terminal) when discussing remote access.
Ensure parity in documentation by referencing both Windows and Linux workflows equally in all sections.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a significant Windows bias. Throughout the prerequisites and deployment steps, only Azure PowerShell and Windows-centric tools (such as Visual Studio and RDP) are mentioned or provided as examples. There are no CLI (az) or Bash/Linux shell examples for resource creation, file uploads, or template deployment. The extension profile example is focused on RDP (a Windows-only protocol), and the guidance for certificate/key vault management only references PowerShell and the Azure portal, omitting Linux-friendly alternatives. The deployment command at the end is shown only in PowerShell, with no az CLI or Bash equivalent.

Recommendations:

Add equivalent Azure CLI (az) commands for all resource creation, file upload, and deployment steps, alongside or before PowerShell examples.
Include Bash/Linux shell examples for uploading files to storage and managing key vaults.
Mention cross-platform tools (such as Azure CLI and VS Code) before or alongside Windows-specific tools like PowerShell and Visual Studio.
Provide extension profile examples that are not Windows-specific (e.g., SSH for Linux), or clarify that the RDP extension is only relevant for Windows workloads.
Explicitly state when a step or tool is Windows-only, and offer Linux/macOS alternatives where possible.
Update the deployment section to include az deployment group create or az deployment sub create commands as alternatives to New-AzResourceGroupDeployment.

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 examples, with no mention of Bash, Azure CLI, or Linux-native scripting alternatives. All instructions, sample scripts, and YAML pipeline tasks are PowerShell-centric, assuming the user will use PowerShell Core even in cross-platform scenarios. There are no Linux/Unix shell or Azure CLI equivalents provided, and the documentation does not address how to achieve the same tasks outside of the PowerShell ecosystem.

Recommendations:

Provide equivalent examples using Azure CLI and Bash scripts for Linux users.
Explicitly mention that PowerShell Core is cross-platform, but also offer native Bash/CLI alternatives for users who prefer not to use PowerShell.
Include YAML pipeline tasks that demonstrate running Bash scripts or AzureCLI@2 tasks to achieve the same pre- and post-deployment automation.
Add a section discussing cross-platform considerations and how to adapt the workflow for Linux-based build agents.
Reference official Azure CLI documentation and provide links to relevant CLI commands for managing Data Factory triggers and deployments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by presenting Windows/RDP instructions and tools (MSTSC, Copy/Paste) before Linux/SSH equivalents. The Windows native client workflow is described in detail, while Linux workflows are less emphasized and lack explicit, step-by-step Linux-native examples. The use of Windows-specific terminology and tools (e.g., MSTSC, right-click Copy/Paste) further centers the Windows experience.

Recommendations:

Provide Linux-native client instructions and examples with equal prominence and detail as Windows instructions.
Include explicit step-by-step examples for Linux users, such as using Remmina or rdesktop for RDP, and detailed SCP/SFTP workflows.
Avoid Windows-specific terminology (e.g., 'right-click', 'Copy and Paste') without offering Linux equivalents.
Structure the documentation so that Windows and Linux workflows are presented in parallel sections, or alternate which platform is described first.
Reference Linux-native tools (Remmina, KRDC, rdesktop, etc.) and provide links to their documentation.
Clarify that file transfer via RDP is possible from Linux clients (if supported), or explicitly state limitations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several ways: it explicitly states that the example deploys Windows software on Windows-based Batch nodes, uses a Windows-specific FFmpeg build, and the ARM template for the Batch pool is hardcoded to use Windows Server images. There are no parallel Linux examples, and the repository setup and pipeline instructions only reference Windows artifacts. Additionally, the agent specification in the pipeline is set to 'windows-latest', and PowerShell Core is used for scripting, with no mention of Bash or Linux agents.

Recommendations:

Provide parallel Linux-based examples throughout the documentation, including ARM templates for Linux Batch pools (e.g., using Ubuntu images) and instructions for deploying Linux software.
Include instructions for downloading and packaging a Linux build of FFmpeg, and update the repository structure to accommodate both Windows and Linux application packages.
Show how to set up the pipeline using a Linux agent (e.g., 'ubuntu-latest') and provide Bash script alternatives for Azure CLI tasks.
Clearly state at the beginning that both Windows and Linux are supported, and offer readers a choice of which path to follow.
Where possible, use OS-agnostic language and tools, or provide both Windows and Linux command examples side by side.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page primarily focuses on the Azure portal, which is cross-platform, but in the 'Next steps' section, Windows-centric tools (PowerShell, Visual Studio) are mentioned before any Linux-friendly or cross-platform alternatives. There is no mention of Azure CLI or Bash examples, and the deployment options prioritize Windows tools, indicating a subtle Windows-first and PowerShell-heavy bias.

Recommendations:

Include Azure CLI (az) as a deployment option alongside PowerShell and Visual Studio, and list it before or alongside PowerShell to avoid Windows-first ordering.
Provide explicit mention or examples for Linux/macOS users, such as using Bash or cross-platform tools.
Balance the order of tool recommendations so that Linux-friendly options are not always listed after Windows tools.
If possible, add screenshots or instructions that are not specific to Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias toward Windows by providing only PowerShell commands (Get-AzMarketplaceTerms, Set-AzMarketplaceTerms) for accepting legal terms, without offering equivalent Azure CLI or Bash examples. The 'Other Batch account management options' section lists PowerShell cmdlets before Azure CLI, and no Linux shell or cross-platform command-line examples are given for key configuration steps. This may hinder Linux users or those preferring cross-platform tools.

Recommendations:

Provide equivalent Azure CLI commands for all PowerShell examples, especially for accepting legal terms and managing Batch accounts.
When listing management tools, mention Azure CLI before or alongside PowerShell cmdlets to avoid implying a Windows-first approach.
Include Bash or shell script examples where appropriate, or clarify that steps can be performed from any OS using the Azure CLI.
Explicitly state that all portal-based steps are OS-agnostic, and provide links to cross-platform documentation where available.
Consider adding a table or section summarizing command-line options for both Windows (PowerShell) and Linux/macOS (Azure CLI/Bash).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias. PowerShell cmdlets are listed first among command-line tools, and the use of Remote Desktop (RDP) for node access is highlighted without mentioning SSH as a Linux equivalent. While the Azure CLI is described as cross-platform and Batch Explorer is available for all OSes, the overall pattern places Windows tools and workflows before Linux alternatives, and omits explicit Linux-native examples or instructions.

Recommendations:

List Azure CLI before PowerShell in the command-line tools section to emphasize cross-platform parity.
When mentioning RDP for node access, also mention SSH for Linux nodes, with a link to instructions for SSH access.
Include explicit examples or references for Linux users, such as Bash scripts or Linux shell commands, alongside or before Windows/PowerShell examples.
Ensure that any tool or workflow described (such as file downloads or node access) includes Linux-relevant instructions or notes.
Consider adding a table or section that summarizes OS-specific guidance for common developer tasks in Azure Batch.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific file types and installation methods (such as .exe and .msi files) without providing equivalent Linux examples or mentioning Linux package formats. There are no examples or guidance for Linux tools, commands, or installation patterns, and the only executable and installer formats mentioned are Windows-centric.

Recommendations:

Include Linux-specific examples alongside Windows ones, such as referencing .sh scripts, .tar.gz archives, or .deb/.rpm packages.
When discussing installation commands, provide both Windows (e.g., msiexec, .exe) and Linux (e.g., bash install.sh, dpkg -i, rpm -i) equivalents.
Mention Linux tools and patterns for copying and installing applications, such as using wget, curl, scp, or package managers (apt, yum).
Avoid assuming the use of Windows by default; explicitly state that the guidance applies to both Windows and Linux nodes, and clarify any differences.
Provide example start task command lines for both Windows (cmd, PowerShell) and Linux (bash, shell scripts).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page focuses exclusively on .NET and C# examples, which are most commonly associated with Windows development. It references the Azure portal and uses terminology such as 'Windows Azure Service Management API', and all code samples are in C#. There are no examples or guidance for Linux users, such as command-line registration with Azure CLI, nor are there any cross-platform code samples (e.g., Python, Java, or REST). The documentation implicitly assumes a Windows development environment and does not address Linux or macOS workflows.

Recommendations:

Include examples for registering applications using the Azure CLI and Azure PowerShell, making clear which commands work cross-platform.
Provide code samples in additional languages (such as Python or Java) that are commonly used on Linux.
Clarify that the .NET library and authentication flows are supported on Linux and macOS, and provide any necessary setup instructions.
Reference cross-platform tools and workflows (such as VS Code, Docker, or REST API usage) alongside or before Windows-specific tools.
Avoid using 'Windows Azure' terminology unless specifically referring to legacy services; use 'Azure' for modern, cross-platform services.
Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a clear Windows bias. All code examples are in C# and use Windows-centric command lines (e.g., 'cmd /c'), with no Linux shell equivalents provided. The only virtual machine image example is for Windows Server, and environment variable usage is explained for both platforms, but only Windows command syntax is shown in executable examples. There are no Linux-specific code samples, shell commands, or references to Linux tools or patterns.

Recommendations:

Provide parallel Linux examples for all code snippets, especially for task command lines (e.g., show both 'cmd /c ...' and '/bin/bash -c ...').
Include examples of creating pools with Linux VM images (e.g., Ubuntu) alongside the Windows example.
Demonstrate how to reference and execute installed applications on Linux nodes using appropriate shell syntax.
Mention Linux-specific considerations (such as file permissions, path separators, and case sensitivity) where relevant.
Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate or combine examples, rather than always presenting Windows first).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by presenting Windows terminology and tools first (e.g., RDP before SSH), providing code examples that default to Windows node agent SKUs, and omitting explicit Linux-specific examples or commands. References to Windows-specific tools and patterns (such as RDP and nodeAgentSkuId for Windows) are more prominent, while Linux equivalents are only mentioned in passing or as secondary options.

Recommendations:

Provide parallel Linux-focused examples alongside Windows ones, including explicit nodeAgentSkuId values for Linux pools.
When listing connection methods, mention SSH (Linux) before or alongside RDP (Windows), or present both equally.
Include sample code snippets and REST API request bodies for creating Linux-based pools, not just Windows.
Reference Linux tools and workflows (e.g., bash, Linux CLI commands) explicitly in relevant sections.
Ensure that all guidance (such as for Packer or image preparation) includes both Linux and Windows links and steps, not just Windows or generic instructions.
Avoid defaulting to Windows-specific values (like 'batch.node.windows amd64') in code samples; provide Linux alternatives or clarify how to select the appropriate value.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation generally presents Windows tools and patterns before Linux equivalents, such as listing 'cmd.exe' before '/bin/sh' and using Windows-style path examples and syntax. There is a tendency to describe Windows-specific details first, and some examples (e.g., directory postfixes) use Windows path separators without showing Linux equivalents. There are also references to Windows-specific environment variable naming conventions and tools, with less emphasis or detail for Linux.

Recommendations:

Present Linux and Windows examples side-by-side, or alternate which platform is shown first to avoid implicit prioritization.
For directory and path examples, always show both Windows (backslash) and Linux (slash) formats.
Where environment variable naming conventions differ (e.g., underscores vs. hash), clearly document both and provide explicit Linux examples.
Expand Linux-specific guidance, such as showing how to use shells other than /bin/sh (e.g., bash), and clarify any differences in behavior.
Avoid using only Windows tools (e.g., 'cmd.exe') in explanations; always provide the Linux equivalent with equal prominence.
Include Linux-specific notes where features are not available or behave differently, and ensure parity in example depth and clarity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by describing Windows-specific paths and behaviors first and in more detail, providing a detailed table of Windows host/container paths, and omitting equivalent Linux path mappings. There are no Linux-specific code or path examples, and the documentation references Windows drive letters and conventions exclusively in path tables.

Recommendations:

Add a parallel table showing Linux host and container paths for each Azure Batch data path, using Linux filesystem conventions (e.g., /mnt/batch/tasks/applications).
Provide Linux-specific examples for configuring container isolation, including sample paths and mount behaviors.
Ensure that explanations and examples are presented in a platform-neutral order or provide Linux and Windows information side by side.
Reference Linux tools and conventions where appropriate, not just Windows drive letters and paths.
Clarify any platform-specific differences in behavior, and provide guidance for both Windows and Linux users equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively discusses the Key Vault VM extension for Windows, with all examples and explanations tailored to Windows environments. There is no mention of Linux support, Linux certificate stores, or Linux-specific configuration steps. The documentation references Windows certificate stores and uses Windows-centric terminology and file paths, indicating a strong Windows bias.

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, provide equivalent instructions and examples for Linux, including details on certificate storage locations and configuration steps.
Include Linux-specific code snippets or configuration samples (e.g., for cloud-init or Linux VM extensions).
Mention Linux tools and patterns (such as OpenSSL, Linux certificate stores, etc.) alongside Windows tools.
Ensure parity in documentation structure and depth for both Windows and Linux platforms, or clearly indicate platform-specific limitations.

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: .NET (C#) and Windows-centric examples are consistently presented first and in greater detail, including code snippets that use Windows VM images (e.g., MicrosoftWindowsServer) and node agent SKUs for Windows. PowerShell and .NET SDKs are emphasized, with only a single Python example provided for Linux (Ubuntu) and no Bash/CLI or Linux shell examples. There are no explicit Linux command-line or scripting examples, and Windows terminology and tools are referenced more frequently and prominently than their Linux equivalents.

Recommendations:

Provide Linux-first or side-by-side examples for all SDKs, including Bash/CLI and Python, not just .NET/C#.
Include explicit Linux VM image references and node agent SKUs in .NET and other language examples, not just Windows.
Add examples using Azure CLI and Bash scripts for common operations (e.g., creating pools, enabling autoscale), to complement PowerShell and .NET code.
Ensure that Linux tools and workflows are mentioned with equal prominence and detail as Windows/PowerShell/.NET equivalents.
Review terminology and ordering to avoid always listing Windows/PowerShell/.NET first; alternate or parallelize with Linux/Python/CLI where possible.

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 instructions for managing the Remote Desktop extension use PowerShell and the Az.CloudService module, which are Windows-centric tools. There are no examples or guidance for performing equivalent tasks using cross-platform tools such as Azure CLI, Bash, or Linux-native RDP clients. The workflow assumes the use of .rdp files and the Windows Remote Desktop client, with no mention of Linux or macOS alternatives. The 'Next steps' section also lists PowerShell and Visual Studio (both Windows-focused) before mentioning templates, and does not reference Azure CLI or Linux tools.

Recommendations:

Add equivalent Azure CLI examples for managing the Remote Desktop extension, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include instructions or references for connecting to RDP-enabled instances from Linux and macOS, such as using 'xfreerdp', 'remmina', or 'rdesktop'.
When listing deployment options, mention cross-platform tools (e.g., Azure CLI, ARM templates) before or alongside Windows-specific tools like PowerShell and Visual Studio.
Clarify that .rdp files can be used with RDP clients on Linux and macOS, and provide links to relevant documentation.
Where possible, use neutral language and tool-agnostic instructions, or provide parallel examples for both Windows and Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively providing Windows command-line examples (using 'cmd /c' and Windows environment variable syntax), referencing Windows file paths (with backslashes), and omitting any Linux or cross-platform shell examples. There is no mention of Bash, sh, or Linux-specific command lines, nor are there notes about cross-platform compatibility or how to adapt the examples for Linux compute nodes.

Recommendations:

Provide parallel Linux/Bash shell examples for all command-line snippets (e.g., use 'bash -c' or 'sh -c' and appropriate environment variable and path syntax).
Explicitly mention that Batch compute nodes can run both Windows and Linux, and clarify any differences in job preparation/release task scripting.
Add a section or callout explaining how to write cross-platform scripts for job preparation and release tasks, including tips for detecting the OS and using portable commands.
Update sample output and file paths to include Linux-style paths (forward slashes) and environment variable syntax ($VAR).
Where Windows tools or patterns are mentioned, provide Linux equivalents (e.g., 'del' vs. 'rm', '%VAR%' vs. '$VAR').

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a strong bias towards Windows environments, particularly through its exclusive recommendation and usage of PowerShell scripts for pre- and post-deployment tasks. There are no examples or guidance for performing these tasks using Linux-native tools (such as Bash or shell scripts), nor is there mention of cross-platform alternatives. The documentation also assumes the use of PowerShell Core but does not clarify how to adapt the process for Linux users, and Windows-centric tools and patterns are referenced without Linux parity.

Recommendations:

Provide equivalent Bash or shell script examples for pre- and post-deployment tasks, alongside the PowerShell scripts.
Explicitly state that PowerShell Core is cross-platform and provide instructions for installing and running it on Linux/macOS.
Mention and, where possible, provide examples using Azure CLI (az) commands for deployment steps, as these are cross-platform.
Reorder or supplement recommendations so that Linux and cross-platform options are presented alongside or before Windows-specific tools.
Clarify any platform-specific limitations or considerations for Linux/macOS users in the relevant sections.
Link to documentation or guides for running Azure DevOps pipelines and scripts in Linux-based agents.

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-based examples and tools. The only detailed code samples are in C# using the Batch .NET library, which is most commonly used on Windows. The .NET example for pool creation uses a Windows Server image, and there are no equivalent Linux-focused .NET code samples. While the REST API example uses Ubuntu, there are no Linux shell, Bash, or cross-platform scripting examples. The GitHub sample project is a C# console application, further reinforcing the Windows/.NET focus. There is no mention of Linux-specific tools, shell commands, or cross-platform SDKs (e.g., Python, CLI).

Recommendations:

Add Linux-focused .NET code samples, e.g., using an Ubuntu image in the VirtualMachineConfiguration section.
Provide equivalent examples using the Azure Batch Python SDK, which is widely used on Linux.
Include Bash or shell command examples for common operations (e.g., using Azure CLI to create pools and tasks).
Mention and link to cross-platform tools (such as Azure CLI and Python SDK) alongside or before Windows/.NET tools.
Ensure that code snippets and sample projects are available in multiple languages and platforms, not just C#/.NET.
Explicitly state that Azure Batch supports both Windows and Linux nodes, and provide parity in documentation examples.

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 commands for applying the Azure diagnostics extension. All command-line examples use PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. The configuration file examples reference Windows-style performance counters and patterns. There are no Linux-specific instructions, examples, or troubleshooting notes, and the documentation does not address how to perform these tasks from a Linux or cross-platform environment.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux.
Include Bash shell script examples for downloading and managing configuration files.
Document any differences or considerations when applying the diagnostics extension to Linux-based cloud service roles, if supported.
Mention and link to Linux tools or documentation where relevant, such as using curl/wget for file downloads or jq for JSON manipulation.
Ensure that references to performance counters or monitoring patterns include Linux equivalents (e.g., CPU/memory metrics as reported by Linux).
Clearly state platform limitations or differences if the extension or process is Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. All code samples, configuration snippets, and walkthroughs use Windows-specific tools (MS-MPI, cmd.exe, .NET/C#), and reference Windows VM images. The installation and execution commands are exclusively for Windows (e.g., MSMpiSetup.exe, cmd /c, mpiexec.exe), and there are no Linux shell or Python examples. Linux and Intel MPI are only mentioned in passing, with no practical guidance or code samples. The code sample and step-by-step instructions require Visual Studio and Windows development tools, with no Linux equivalents or parity.

Recommendations:

Add parallel Linux-focused sections and code samples using Python SDK or Azure CLI, demonstrating how to configure and run multi-instance tasks on Linux pools.
Provide equivalent shell/bash commands for installing Intel MPI on Linux nodes using StartTask, and show how to run MPI applications with mpirun.
Include Linux VM pool configuration examples (e.g., Ubuntu images) and show how to set up pools for Linux-based MPI workloads.
Reference and link to Linux sample repositories more prominently, and provide walkthroughs for building and running MPI applications on Linux.
Ensure that both Windows and Linux examples are presented side-by-side or in separate clearly marked sections, so users of either platform can follow the documentation equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Linux and Windows guidance, but there is a notable Windows bias in several areas. Windows examples and tools (such as PowerShell and Remote Desktop) are mentioned explicitly and sometimes before their Linux equivalents. The detailed example for installing Microsoft MPI is only provided for Windows, and the process involves Windows-specific tools. In the pool configuration examples, Windows images and settings are often listed first or in more detail. There is also a reliance on Windows-specific tools (e.g., PowerShell, RDP) in the workflow descriptions.

Recommendations:

Provide Linux-first or parallel Linux and Windows examples in all sections, especially in step-by-step guides.
Include explicit Linux command-line examples (e.g., using SSH, Bash scripts) where Windows tools like PowerShell or RDP are referenced.
Add a detailed example for setting up MPI on Linux pools, mirroring the Windows MPI example.
Ensure that all configuration tables and sample settings are presented in a balanced order (alternating or side-by-side for Linux and Windows).
Where possible, use cross-platform tools or provide both Windows and Linux command lines/scripts for tasks like driver installation and VM configuration.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows-centric bias by focusing on Windows-specific tools (such as PowerShell and Windows Defender), mentioning Windows Server versions, and omitting Linux equivalents or examples. All extension descriptions and configuration instructions assume a Windows environment, with no guidance for Linux-based cloud service roles or alternative tools for Linux users.

Recommendations:

Provide equivalent instructions and examples for Linux-based roles, including how to configure and use extensions on Linux VMs.
Mention and link to Linux-compatible monitoring and security tools (e.g., Azure Monitor Agent, Linux antivirus solutions) where applicable.
Include Linux command-line examples (such as Azure CLI or bash scripts) alongside or before PowerShell examples.
Clarify which extensions and features are Windows-only and which are cross-platform, and provide guidance for Linux users where features are not available.
Avoid assuming the use of Visual Studio or Windows-specific deployment tools; mention cross-platform alternatives like VS Code or ARM/Bicep templates.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only a C# SDK example that uses a Windows VM image (MicrosoftWindowsServer) and node agent (batch.node.windows amd64), with no equivalent example for Linux VM images or Linux node agents. There are no Linux-specific examples, commands, or references to Linux tools or patterns. The documentation implicitly prioritizes Windows by example and omits Linux parity.

Recommendations:

Add parallel examples using Linux VM images (e.g., Ubuntu, CentOS) and the appropriate Linux node agent SKU in the C# SDK example.
Explicitly mention both Windows and Linux options when discussing VM image configuration, including sample publisher/offer/sku values for popular Linux distributions.
Provide at least one example that updates a pool to use a Linux image, including the correct nodeAgentSkuId for Linux.
Where relevant, mention any Linux-specific considerations or differences in pool property updates.
Ensure that REST/HTTP and SDK examples are balanced between Windows and Linux scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by presenting Windows-specific tools, commands, and patterns before or in greater detail than their Linux equivalents. Examples for file copying and mounting Azure Files are provided only for Windows (using cmdkey, net use, and Windows-style azcopy syntax), while Linux mounting and usage are referenced but not exemplified. The documentation also references Windows tools and workflows (e.g., PowerShell, cmdkey, net use) without providing parallel Linux command-line examples or explicit parity in instructions.

Recommendations:

Provide Linux command-line examples for all file copy and mounting operations, such as using azcopy with Linux syntax, and mounting Azure Files with mount.cifs or SMB utilities.
Ensure that for every Windows-specific tool or workflow mentioned (e.g., cmdkey, net use), a Linux equivalent (e.g., smbclient, mount -t cifs) is described and exemplified.
Present Linux and Windows examples side-by-side or in parallel sections, rather than Windows-first or Windows-only.
Include explicit instructions and code snippets for mounting Azure Files on Linux VMs, not just referencing blobfuse.
Review the order of presentation to avoid always listing Windows tools and workflows before Linux equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows tools and patterns (such as RDP, PowerShell, and Windows-specific instructions) are mentioned before or more prominently than their Linux equivalents. Some examples and instructions are Windows-centric or list Windows first, and there is a lack of parity in providing Linux-specific command-line or tool examples (e.g., no Bash or Linux shell script examples).

Recommendations:

When listing tools or connection methods (e.g., RDP for Windows, SSH for Linux), present both options equally and in parallel, not with Windows first.
For every PowerShell example or reference, provide an equivalent Bash or Linux shell example where possible.
When referencing Azure CLI or SDKs, include explicit Linux usage examples (e.g., Bash scripts, Linux shell commands) alongside or before Windows/PowerShell examples.
In sections describing how to connect to VMs, provide step-by-step instructions for both RDP (Windows) and SSH (Linux), not just a brief mention.
Ensure that all prerequisites and setup steps are described for both Windows and Linux environments, including any OS-specific considerations.
Review the order of presentation so that Linux and Windows are given equal prominence, or alternate which is listed first.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page exhibits a strong Windows bias. All code examples use Windows command-line syntax (cmd.exe /c echo ...), and there are no Linux or cross-platform shell examples. The documentation refers exclusively to Windows tools (cmd.exe), and does not mention Linux shells (bash/sh) or provide equivalent Linux command examples. The structure and examples assume a Windows environment by default, with no guidance for Linux users.

Recommendations:

For every code example using Windows command-line (cmd.exe), provide an equivalent Linux shell (bash/sh) example, e.g., 'bash -c "echo Flowers"'.
Explicitly mention that Azure Batch supports both Windows and Linux compute nodes, and clarify any differences in task command line syntax.
Add a section or note explaining how to adapt the examples for Linux pools, including differences in shell invocation and exit code handling if applicable.
Avoid using Windows tools exclusively in examples; use cross-platform commands where possible (e.g., 'echo' is available on both platforms, but the shell invocation differs).
Where possible, provide side-by-side or tabbed code samples for Windows and Linux to improve parity and accessibility for all users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates bias toward Windows environments by exclusively providing .NET (C#) code samples, referencing Visual Studio as the development environment, and mentioning Windows-specific tools and patterns (such as .exe executables and Visual Studio solutions). There are no examples or guidance for Linux users, alternative development environments, or cross-platform .NET usage. The documentation assumes a Windows-centric workflow and does not address Linux or macOS scenarios.

Recommendations:

Provide equivalent code samples and instructions for .NET development on Linux and macOS, including use of cross-platform editors like VS Code and command-line tools like dotnet CLI.
Mention and demonstrate how to run and build the sample projects using the dotnet CLI, which is available on all major platforms.
Clarify that the .NET File Conventions library can be used on Linux and macOS, and provide any necessary setup or troubleshooting tips for those environments.
Avoid references to Windows-specific file extensions (such as .exe) or provide Linux equivalents (such as .dll or cross-platform .NET Core executables).
Include guidance for uploading application packages and running tasks from Linux/macOS, not just via the Azure portal or Windows tools.
Explicitly state platform compatibility and provide links to cross-platform .NET documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation exhibits a strong Windows bias: all code samples use Windows-specific command syntax (cmd.exe), file paths use backslashes by default, and there are no Linux/bash equivalents provided. The only mention of Linux is a note telling users to change backslashes to forward slashes, without any actual Linux example. The code sample and workflow are centered around C#/.NET and Visual Studio, with no mention of cross-platform development tools or languages. The sample project is a Visual Studio solution, further reinforcing the Windows-centric approach.

Recommendations:

Provide equivalent Linux/bash command examples for task commands (e.g., use bash shell syntax in addition to cmd.exe).
Show file path examples using both Windows (\) and Linux (/) conventions, or use platform-agnostic path joining.
Include code samples in at least one cross-platform language (e.g., Python) in addition to C#.
Mention and demonstrate how to use cross-platform development tools (e.g., VS Code, CLI) rather than only Visual Studio.
Explicitly document any platform-specific considerations (e.g., line endings, shell differences) and provide guidance for both Windows and Linux users.
Reference and link to Linux-specific Azure Batch documentation or guides, if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively providing examples for Windows-based pools (e.g., using MicrosoftWindowsServer images and Windows-specific nodeAgentSKUId), referencing Windows-specific configuration properties (such as windowsConfiguration.enableAutomaticUpdates), and omitting any Linux-based pool configuration or examples. There are no Linux image references, node agent SKUs, or Linux-specific configuration guidance, which may mislead users into thinking Auto OS Upgrade is only for Windows pools or make it harder for Linux users to adopt the feature.

Recommendations:

Add parallel examples for Linux-based pools in both REST API and SDK sections, using a popular Linux image (e.g., Ubuntu) and the appropriate nodeAgentSKUId (e.g., batch.node.ubuntu 20.04).
Include Linux-specific configuration properties and clarify any differences in upgrade behavior or requirements for Linux pools.
In the requirements section, mention both Windows and Linux configuration properties (e.g., clarify that windowsConfiguration.enableAutomaticUpdates is not relevant for Linux, and note any Linux equivalents if applicable).
In all code and JSON samples, provide both Windows and Linux variants, or at least alternate between them to ensure parity.
Explicitly state that Auto OS Upgrade is supported for both Windows and Linux pools (if true), and link to documentation listing supported Linux images.

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 only example for programmatically checking VM support for ephemeral OS disks, without mentioning or providing equivalent Linux/CLI commands. Additionally, the only explicit tooling example for querying capabilities is PowerShell, and there is no mention of Bash, Azure CLI, or cross-platform alternatives. While the code samples for SDK usage are platform-neutral (Python and C#), the operational guidance prioritizes Windows tools.

Recommendations:

Add Azure CLI and/or Bash examples for checking VM series support for ephemeral OS disks, alongside or before the PowerShell example.
Explicitly mention cross-platform tools (e.g., Azure CLI) in the section about programmatically querying VM capabilities.
Ensure that all operational instructions and examples are provided for both Windows and Linux users, not just PowerShell.
Consider linking to documentation or guides that show how to perform the same tasks on Linux/macOS environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias in several ways: PowerShell is the only command-line example shown, and PowerShell is mentioned before CLI in the provider registration step. Visual Studio is listed as a deployment tool, but no Linux-native tools or workflows are highlighted. There are no explicit Linux/Unix shell (bash/az CLI) examples, and the documentation assumes familiarity with Windows-centric tools and patterns.

Recommendations:

Provide Azure CLI (az) command examples alongside or before PowerShell for all command-line operations, especially for resource provider registration and status checking.
Include deployment instructions and examples using cross-platform tools such as Azure CLI, ARM templates, and VS Code, not just Visual Studio.
Explicitly mention Linux/macOS compatibility and provide guidance for users on those platforms.
Balance the order of tool presentation (e.g., list CLI before or alongside PowerShell) to avoid implying Windows is the default or preferred platform.
Where possible, add bash shell script examples or references for common migration tasks.

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 tools and patterns (such as cmd.exe, Windows Data Protection API, and RDP) are mentioned before or instead of Linux equivalents. Code examples for running tasks often default to Windows command lines (e.g., 'cmd /c echo hello'), and Windows-specific features are described in more detail or earlier than Linux ones. Some Linux-specific details (such as SSH or Linux user configuration) are present but less emphasized, and there are missing Linux command-line examples in several code snippets.

Recommendations:

Provide Linux shell command examples (e.g., 'bash -c "echo hello"') alongside or before Windows 'cmd.exe' examples in all code snippets.
When referencing Windows tools (e.g., DPAPI, RDP), also mention Linux equivalents (e.g., GnuPG, SSH, or Linux file permissions) and provide links or explanations.
Ensure that all code samples that show Windows VM configuration or user account creation also include equally detailed Linux examples, not just in .NET but in all supported languages.
In sections discussing remote access, mention SSH for Linux before or alongside RDP for Windows, and provide parity in guidance and links.
Review the order of presentation so that Linux and Windows are treated equally, or alternate which OS is presented first in each section.
Explicitly call out any OS-specific limitations or differences to help users understand cross-platform implications.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits subtle Windows bias. While it covers general Azure Batch and networking concepts, it tends to mention Windows-specific tools, ports, and patterns before their Linux equivalents. For example, remote access ports are listed as '3389 (Windows), 22 (Linux)', with Windows (RDP) always preceding Linux (SSH). There is also a lack of explicit Linux CLI or scripting examples (e.g., Bash), and the prerequisites mention Azure PowerShell before Azure CLI. No Linux-specific tooling or command-line examples are provided, and there is no demonstration of Linux-native workflows.

Recommendations:

When listing ports or OS-specific details, alternate the order (e.g., mention Linux/SSH before Windows/RDP in some places) or present them together without preference.
Provide explicit Linux/Bash command-line examples alongside PowerShell, especially for common tasks like creating virtual networks or subnets.
Include references to Linux-native tools and workflows (e.g., Bash scripts, Linux CLI usage) in the prerequisites and examples.
Ensure that all instructions and screenshots are OS-agnostic or provide both Windows and Linux perspectives where relevant.
Where Azure CLI is mentioned, clarify that it is cross-platform and provide sample commands for both Windows (PowerShell/CMD) and Linux (Bash).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation generally covers both Windows and Linux nodes, but there are subtle biases: Windows-specific tools and patterns (e.g., .exe, .cmd, .bat, PowerShell, RDP, Windows Server containers) are mentioned before or more prominently than their Linux equivalents. Some sections (like container support) provide detailed Windows instructions but lack equivalent Linux guidance. There are no Linux-specific command or configuration examples, and Linux tools (e.g., SSH, shell scripts) are referenced less prominently.

Recommendations:

When listing supported script types, mention Linux formats (e.g., shell scripts, Python scripts) before or alongside Windows formats.
In sections discussing remote access, mention SSH for Linux before or equally with RDP for Windows.
For container support, provide explicit instructions and examples for both Windows and Linux nodes, including recommended Linux images and setup steps.
Include Linux-specific examples and references (e.g., mounting disks, using shell scripts in start tasks) wherever Windows examples are given.
Ensure parity in tool and terminology references (e.g., don't only mention PowerShell or .exe; include bash, sh, and ELF binaries).

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 cmdlets) are mentioned before or more prominently than their Linux equivalents. Some examples and troubleshooting steps are provided only for Windows (e.g., using PowerShell's Get-Disk), while Linux examples are less detailed or appear after Windows. In some cases, only Windows-specific issues (like directory junctions) are discussed, and Linux alternatives are not equally covered. There are also references to .NET SDKs and Windows configuration properties before mentioning cross-platform or Linux options.

Recommendations:

Ensure that all examples and tooling references are provided for both Windows and Linux, and that Linux examples are as detailed as Windows ones.
When listing tools or APIs (e.g., PowerShell, Azure CLI), mention cross-platform tools (like Azure CLI) first or alongside Windows-specific tools.
Provide Linux shell command examples (e.g., using lsblk, fdisk, mkfs) wherever PowerShell examples are given, and ensure parity in the level of detail.
Include troubleshooting tips and best practices for Linux nodes with the same prominence as for Windows nodes.
Avoid Windows-specific terminology or patterns (such as .NET classes or Windows Services) without also providing Linux equivalents (such as systemd).
Where Windows-specific issues are discussed (e.g., directory junctions), add corresponding Linux guidance (e.g., symlinks, mount points) for completeness.

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 or sole scripting interface for management tasks (e.g., retrieving deployments, retrying operations, abort/commit actions). There are no explicit Linux or cross-platform CLI examples, and PowerShell is mentioned before or instead of Azure CLI in most cases. This may make the documentation less accessible or immediately actionable for Linux or cross-platform users.

Recommendations:

Provide Azure CLI examples alongside or before PowerShell examples for all management tasks, especially for operations like retrieving deployments, aborting/committing migrations, and interacting with Key Vault.
Explicitly mention that Azure CLI is cross-platform and supported on Linux, macOS, and Windows.
Where PowerShell is referenced, add equivalent Bash/Azure CLI command snippets and links to relevant Azure CLI documentation.
Avoid language that implies PowerShell is the default or only supported tool; use neutral phrasing such as 'using Azure CLI or PowerShell'.
Add a section or callout for Linux/macOS users, highlighting any platform-specific considerations or tools.

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 a primary method for creating public IP addresses, and mentioning it before providing any Linux-specific or cross-platform alternatives. While the Azure CLI is mentioned (which is cross-platform), there are no explicit Linux shell or Bash examples, and PowerShell is called out by name. No Linux-specific tools or command-line examples are provided, and the documentation does not clarify parity or differences between Windows and Linux environments for these operations.

Recommendations:

Provide explicit Bash or Linux shell examples for creating public IP addresses using Azure CLI, including sample commands.
List Azure CLI (which is cross-platform) before Azure PowerShell in the list of methods, or clarify that both are supported equally.
Clarify that all steps can be performed from Linux, macOS, or Windows, and highlight any OS-specific considerations if they exist.
Where PowerShell is mentioned, also mention Bash or other Linux-native shells to ensure parity.
Consider adding a table or section comparing the steps for Windows and Linux users, or explicitly stating that the process is OS-agnostic when using Azure CLI.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page references 'PowerShell deployments' as a method for specifying reserved IP allocation, but does not mention or provide examples for Linux-based tools or workflows (such as Azure CLI or ARM templates used from Linux). There are no Linux-specific examples or parity in tooling references, and the only deployment tool mentioned is PowerShell, which is primarily associated with Windows environments.

Recommendations:

Include references and examples for Azure CLI commands, which are cross-platform and commonly used on Linux.
When mentioning PowerShell, also mention Azure CLI or Bash scripting as alternatives for Linux users.
Provide at least one example of configuring the NetworkConfiguration schema using Linux-friendly tools or workflows.
Avoid implying that PowerShell is the only or primary way to deploy or configure these settings; clarify that multiple tools are supported.
Add a section or note on how Linux users can achieve the same configuration, possibly linking to relevant Azure CLI or ARM template documentation.

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 are exclusively in PowerShell, with no Linux shell or cross-platform alternatives provided. Windows-specific tools and patterns (e.g., PowerShell cmdlets, .msi installers, Windows Management Framework) are referenced throughout, and instructions for certificate creation, service principal setup, and Key Vault access are all tailored to Windows environments. There is no mention of Linux equivalents or guidance for users on Linux-based Batch nodes.

Recommendations:

Provide equivalent Bash/CLI examples for certificate creation (e.g., using OpenSSL) and service principal setup (e.g., using Azure CLI).
Include instructions for installing necessary Azure libraries on Linux nodes (e.g., Azure CLI, Python SDK).
Demonstrate how to authenticate to Azure Key Vault from Linux Batch nodes using certificates and managed identities.
Avoid assuming PowerShell is the default scripting environment; offer cross-platform guidance.
Reference Linux tools and patterns alongside Windows ones, and ensure both are given equal prominence.
Add a section or callouts specifically for Linux users, linking to relevant documentation (e.g., 'using Linux compute nodes').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on the Azure portal for migration steps and, in the 'Next steps' section, lists PowerShell as the only command-line automation example. There are no references to Linux tools, Bash, Azure CLI, or cross-platform scripting options. This presents a Windows-first and PowerShell-heavy bias, with missing Linux or cross-platform examples.

Recommendations:

Include Azure CLI examples alongside or before PowerShell in the 'Next steps' section, as Azure CLI is cross-platform and widely used on Linux.
Add explicit instructions or links for performing the migration using Bash or shell scripting where possible.
Ensure that screenshots and UI references clarify that the Azure portal is platform-agnostic, and consider mentioning that all steps can be performed from any OS.
Where automation is discussed, provide parity between PowerShell and Azure CLI/Bash examples to support Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. Deployment methods are listed as PowerShell, Portal, and Visual Studio, all of which are primarily Windows-based, with no mention of Azure CLI, Bash, or Linux-native tooling. There are no Linux or cross-platform examples or instructions, and PowerShell is referenced as the primary scripting method. This may make it less accessible or intuitive for Linux users or those working in cross-platform environments.

Recommendations:

Include Azure CLI examples and instructions alongside or before PowerShell, as Azure CLI is cross-platform and widely used on Linux and macOS.
Mention and provide examples for deploying Cloud Services (extended support) using Bash scripts or shell environments common on Linux.
List deployment options in a neutral or cross-platform order (e.g., Azure CLI, PowerShell, Portal, Visual Studio) rather than Windows-first.
Reference cross-platform tools and editors (such as VS Code) in addition to Visual Studio.
Explicitly state Linux support where applicable and provide parity in documentation for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. While it mentions both Linux and Windows monitoring agents and extensions, Windows tools and .NET libraries are referenced more prominently and with more detailed examples. There are no Linux-specific code samples or references to Linux-native tools or SDKs, and the only application-level monitoring walkthrough is for a .NET (Windows-centric) solution. No PowerShell or CMD examples are present, but the lack of Linux CLI or SDK examples and the focus on Windows/.NET tools indicate a Windows-first approach.

Recommendations:

Add Linux-specific examples for accessing and analyzing Batch logs, such as using Azure CLI, Bash scripts, or Python SDK.
Provide walkthroughs or code samples for monitoring Batch from Linux environments, not just .NET/Windows.
Mention and link to cross-platform SDKs (e.g., Python, Java) and show how to use them for monitoring tasks.
Include references to Linux-native tools (e.g., jq for JSON parsing, Bash scripting) when discussing log file access and analysis.
Ensure parity in agent/extension documentation by providing equal detail and examples for both Linux and Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. It exclusively references Windows tools and patterns, such as Visual Studio, the Microsoft.ApplicationInsights.WindowsServer NuGet package, and Windows-specific VM images. All code and configuration examples assume a Windows environment, including PowerShell commands and Windows batch commands (cmd /c). There is no mention of Linux equivalents, nor are there any Linux-specific instructions or examples for integrating Application Insights with Azure Batch on Linux compute nodes.

Recommendations:

Provide parallel Linux instructions and examples, including how to install and configure Application Insights on Linux-based Batch nodes.
Include Linux-friendly package installation commands (e.g., dotnet CLI, apt, yum) and avoid assuming Visual Studio as the only development environment.
Show how to configure Application Insights for .NET Core/.NET 5+ applications running on Linux, including relevant config file locations and environment variables.
Demonstrate how to set up Batch pools using Linux VM images, and provide sample pool configuration for both Windows and Linux.
Replace or supplement PowerShell and cmd examples with Bash or shell script equivalents.
Clarify any platform-specific limitations or differences in Application Insights support between Windows and Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by prioritizing PowerShell and Visual Studio in its examples and instructions. PowerShell is mentioned as a primary tool for retrieving deployment files and managing updates, with no explicit mention or examples of equivalent Bash, Azure CLI, or Linux-native workflows. Visual Studio, a Windows-centric IDE, is referenced for update processes, and there is a lack of Linux-specific guidance or parity in automation/script examples. Azure CLI is mentioned once, but not as prominently as PowerShell.

Recommendations:

Provide explicit Azure CLI and Bash examples alongside PowerShell for all operations, especially for retrieving deployment files and managing updates.
Include instructions or references for using cross-platform tools (e.g., Azure CLI, REST API via curl) for Linux and macOS users.
Add a section or callouts for Linux users, highlighting any differences or additional steps required.
When mentioning Visual Studio, also reference cross-platform alternatives (e.g., VS Code, command-line deployment) and provide guidance for non-Windows environments.
Ensure that all automation and scripting recommendations are platform-agnostic or have clear Linux equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for creating and using Windows-based compute nodes (specifically Windows Server 2019) in Azure Batch. The task command line example uses Windows-specific commands (cmd, set, timeout), and there is no mention of Linux pools, Linux VM images, or equivalent Bash command lines. No Linux or cross-platform alternatives are provided at any step.

Recommendations:

Include parallel instructions and screenshots for creating a Linux-based pool (e.g., using Ubuntu or CentOS images) alongside the Windows example.
Provide Linux-equivalent command line examples for tasks (e.g., using Bash: `bash -c 'env | grep AZ_BATCH; sleep 90'`).
Explicitly mention that Azure Batch supports both Windows and Linux nodes, and help users choose the appropriate OS for their workloads.
Where possible, use cross-platform language or clarify when steps are OS-specific.
Add a section or callout guiding users to Linux-specific documentation or quickstarts if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a clear Windows bias. It exclusively uses Windows Server for compute nodes, configures the pool with a Windows image, and provides only Windows command-line examples (e.g., 'cmd /c type'). There are no Linux VM or command-line examples, and the workflow assumes Windows environments for both pool configuration and task execution. Linux equivalents are not mentioned or demonstrated.

Recommendations:

Add parallel Linux examples throughout the documentation, including pool creation with a Linux Marketplace image and corresponding VirtualMachineConfiguration/ImageReference code.
Show how to specify a Linux command line for tasks (e.g., using '/bin/bash -c cat ...' instead of 'cmd /c type ...').
Explicitly mention that Azure Batch supports both Windows and Linux pools, and provide guidance on choosing and configuring each.
Include sample code snippets and configuration for both Windows and Linux scenarios side by side.
Clarify in the prerequisites and instructions that the quickstart can be completed on both Windows and Linux development environments, and provide any OS-specific notes as needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias. It exclusively uses Windows Server VM images for compute pools, references Windows-specific ffmpeg builds and command-line syntax (cmd /c, .exe), and names pools and jobs with 'Win' prefixes. There are no examples or guidance for running the workload on Linux pools, nor are Linux-compatible ffmpeg packages or shell syntax shown. The workflow and code are tailored to Windows environments, with no parity for Linux users.

Recommendations:

Provide parallel Linux examples: Show how to configure a Batch pool with a Linux VM image (e.g., Ubuntu), including the necessary BatchImageReference and node agent SKU values.
Demonstrate Linux-compatible ffmpeg usage: Reference a Linux build of ffmpeg, and show how to package and use it as an application package.
Show Linux shell command lines: Include examples using bash/sh syntax (e.g., ./ffmpeg instead of ffmpeg.exe, and without cmd /c).
Use neutral naming: Avoid pool/job names like 'WinFFmpegPool' and use OS-neutral identifiers.
Add guidance for cross-platform support: Explain how to adapt the sample for both Windows and Linux, and highlight any differences in configuration or command lines.
Mention both OS options early: In the prerequisites and pool creation sections, explicitly mention that both Windows and Linux pools are supported and provide links or code for both.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation generally states that Azure Batch supports both Linux and Windows, but there are several subtle biases toward Windows. Windows-specific security configuration (TLS/cipher suites) is discussed in detail, with direct links to Windows Server documentation, while equivalent Linux guidance is missing. The only command-line tool explicitly referenced for querying supported images is PowerShell, with the Azure CLI mentioned only as an afterthought. There are no Linux-specific examples or references to Linux security practices (e.g., SSH hardening, Linux-specific patching guidance), and Windows terminology (RDP, registry settings) is more prominent and explained in greater detail.

Recommendations:

Add Linux-specific security guidance, such as links to official documentation on securing SSH, managing Linux TLS/cipher suites, and patching best practices.
When referencing command-line tools, provide Azure CLI examples before or alongside PowerShell, and ensure parity in instructions.
Include explicit Linux examples or notes wherever Windows-specific details are provided (e.g., mention SSH configuration and hardening alongside RDP).
Balance references to Windows and Linux tools/documentation, ensuring both are equally discoverable and detailed.
Where OS-specific configuration is discussed (such as TLS/SSL settings), provide equivalent Linux instructions or links to authoritative Linux resources.

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 without Linux equivalents, and omitting any Linux-specific instructions or examples. There are no references to Linux file paths, tools, or usage patterns, and no guidance for users working on non-Windows platforms.

Recommendations:

Include Linux file path examples for schema locations, such as '/usr/local/share/azure-sdks/schemas' or similar, alongside Windows paths.
Mention cross-platform tools (e.g., Azure CLI, VS Code) and provide instructions for both Windows and Linux environments.
Clarify whether the .cscfg schema and related SDKs are available and supported on Linux, and if so, provide installation and usage guidance for Linux users.
Avoid assuming Visual Studio or .NET SDK usage is exclusive to Windows; reference cross-platform alternatives where possible.
Add explicit Linux examples or notes in sections discussing file locations, tools, or configuration steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by exclusively providing instructions and examples that assume a Windows environment. It specifies the use of Windows-based Batch node images (Dsvm Win 2019), uses Windows command-line syntax (cmd /c), and does not mention or provide alternatives for Linux-based Batch pools or Linux command-line usage. All tooling (Batch Explorer, Storage Explorer) is cross-platform, but the workflow and commands are tailored to Windows, with no guidance for Linux users.

Recommendations:

Include instructions for creating a Batch pool with a Linux image (e.g., Ubuntu) and provide equivalent steps.
Provide Linux shell command equivalents (e.g., use bash syntax instead of cmd /c) for installing Python packages and running scripts.
Show how to specify a Linux start task (e.g., /bin/bash -c "pip install ...") and how to run the Python script in a Linux environment.
Clarify that Batch Explorer and Storage Explorer are cross-platform, and note any differences in usage or UI on Linux.
Add screenshots or notes for Linux users where UI or workflow may differ.
Explicitly mention Linux as a supported platform in the prerequisites and throughout the tutorial.

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. Windows tools and patterns (e.g., 'net use', 'cmdkey') are described in detail, and Windows-specific troubleshooting steps and references are often presented before or more prominently than their Linux equivalents. The documentation also references Windows tools and workflows in several places, sometimes before mentioning Linux alternatives.

Recommendations:

Provide native Linux shell (bash) examples alongside or instead of PowerShell for Linux scenarios, especially for manual mounting and troubleshooting.
Balance the order of presentation so that Linux and Windows instructions/examples are given equal prominence, or alternate which comes first.
Include Linux-native troubleshooting commands (e.g., 'mount', 'dmesg', 'journalctl') and log file locations, not just Windows RDP and log file paths.
Reference Linux-specific documentation and tools (such as mount.cifs, mount.nfs, systemd unit files) where appropriate.
Clarify when PowerShell is required on Linux, and offer alternatives for users who prefer bash or other shells.
Ensure that all code snippets and workflows are equally detailed for both platforms, avoiding extra detail or explanation for Windows-only tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation repeatedly references PowerShell scripts and command-line tools as the primary or only automation method, with no explicit mention or examples of Linux shell (bash) equivalents. When command-line options are offered, 'PowerShell/CLI' is the phrasing used, but all screenshots and script references are PowerShell-centric. There are no bash, Azure CLI (in bash), or Linux-specific instructions or screenshots, and no mention of Linux environments or considerations.

Recommendations:

Provide explicit Azure CLI (bash) script examples alongside PowerShell scripts, especially for automation tasks like triggering backups or changing security settings.
When offering 'Command tools (PowerShell/CLI)' as an option, clarify and show both PowerShell and bash/Azure CLI usage, including screenshots or code blocks for each.
Include notes or sections addressing Linux/macOS users, specifying any differences or prerequisites for running scripts.
Ensure screenshots and downloadable scripts are available in both PowerShell and bash/Azure CLI formats.
Adopt neutral phrasing such as 'Azure CLI or PowerShell' rather than 'PowerShell/CLI', and avoid assuming PowerShell as the default automation tool.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates Windows bias by referencing only the Windows file path for the Azure Diagnostics configuration schema file location (C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK\<version>\schemas) and does not mention Linux or cross-platform equivalents. There are no Linux or macOS-specific instructions or examples, and the documentation implicitly assumes a Windows development environment.

Recommendations:

Include the equivalent file path or installation instructions for Linux and macOS environments, if available.
Explicitly state whether the Azure SDK and related tools are supported on non-Windows platforms, and provide relevant guidance.
Add cross-platform notes or examples to ensure parity for developers using Linux or macOS.
Avoid referencing only Windows-specific tools or locations unless absolutely necessary; if so, provide alternatives or clarifications for other platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows development environments. It exclusively references Visual Studio (Windows-only version), uses Windows-specific UI instructions, and only provides instructions for using the NuGet Package Manager Console (a Visual Studio feature). There are no examples or guidance for Linux or cross-platform development (e.g., using VS Code, .NET CLI, or command-line tools available on Linux/macOS). The 'Next Steps' section also promotes PowerShell, a tool historically associated with Windows, without mentioning Bash or other cross-platform alternatives.

Recommendations:

Provide 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.
Mention and provide examples for using Visual Studio Code, a cross-platform editor, instead of or in addition to Visual Studio 2015.
Include screenshots and steps for Linux/macOS users, such as installing .NET SDK, creating projects, and managing NuGet packages from the command line.
In the 'Next Steps' section, add links or references to Bash/Azure CLI equivalents for managing CDN resources, not just PowerShell.
Avoid UI instructions that are exclusive to Windows (e.g., Visual Studio menus) or provide alternative steps for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation for Azure Cloud Services (extended support) WebRole schema demonstrates a Windows bias. It exclusively references Windows technologies (IIS 7, ASP.NET, .NET Framework), Windows file paths and environment variables (e.g., %ROLEROOT%), and Windows-centric configuration concepts (certificate stores, CMD scripts). There are no examples or mentions of Linux-based web roles, alternative web servers, or cross-platform scripting. All examples and descriptions assume a Windows environment.

Recommendations:

Add explicit statements about Linux support or lack thereof for Cloud Services (extended support) web roles. If Linux is unsupported, clarify this early in the documentation.
If Linux support exists, provide parallel examples and schema explanations for Linux-based web roles, including references to Linux web servers (e.g., Apache, Nginx), Linux file paths, and environment variables.
Include information about how startup tasks and scripts should be formatted and executed on Linux (e.g., using shell scripts instead of CMD files).
Mention Linux certificate storage and management equivalents if applicable.
Where possible, use neutral or dual-platform terminology and examples (e.g., 'web server' instead of 'IIS', or provide both IIS and Nginx/Apache scenarios).

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-line examples for enabling diagnostic logs, with no equivalent Azure CLI, Bash, or Linux-native instructions. The section on consuming logs recommends Microsoft Azure Storage Explorer, a GUI tool primarily available for Windows (though cross-platform, it is often associated with Windows environments), and does not mention Linux-native alternatives or command-line options. There are no Linux shell, Azure CLI, or cross-platform scripting examples, and no mention of how to perform these tasks on Linux systems.

Recommendations:

Add Azure CLI examples alongside PowerShell for all diagnostic log configuration tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash or shell script examples for downloading and processing logs from Azure Storage, such as using az storage blob commands or tools like curl, jq, or Python scripts.
Mention and provide instructions for Linux-native tools (e.g., azcopy, Azure CLI, or Python SDK) for accessing and exporting logs, in addition to Microsoft Azure Storage Explorer.
Ensure that any downloadable tools or sample code are described as cross-platform, and provide explicit instructions for Linux users where applicable.
Consider reordering sections so that cross-platform or Linux-friendly approaches are presented before or alongside Windows/PowerShell-specific instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides detailed instructions and code samples for performing tasks using Azure PowerShell, but does not include equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). The use of PowerShell as the only command-line automation example introduces a Windows-centric bias, potentially making it less accessible for users on non-Windows platforms.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux/macOS.
Where PowerShell is shown, provide a parallel tab or section for Bash/Azure CLI usage.
Clarify that PowerShell Core is cross-platform, but also mention and demonstrate Azure CLI as a first-class alternative.
Ensure that screenshots and portal instructions do not assume a Windows environment (e.g., avoid references to Windows-specific UI or terminology).
Review all automation and scripting sections to ensure Linux/macOS users have clear, tested guidance.

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 the only command-line management tool for Azure CDN endpoints, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI or Bash. The 'Manage your content delivery network endpoints' section links exclusively to PowerShell documentation, and there are no Linux or cross-platform command-line examples or references. This may make it less accessible for Linux or macOS users.

Recommendations:

Include Azure CLI examples and documentation links alongside PowerShell for managing CDN endpoints, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that management can be performed from Linux, macOS, and Windows, and provide parity in instructions and examples.
Where PowerShell is referenced, add equivalent Bash or shell command examples, or at least link to relevant Azure CLI documentation.
Review all 'Next steps' and 'Requirements' sections 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 demonstrates a Windows bias by referencing Windows-specific concepts and tools (such as certificate store locations like 'CurrentUser' and 'LocalMachine', store names like 'My', 'Root', etc., and the use of CMD/batch files for startup tasks) without mentioning Linux equivalents or alternatives. There are no examples or guidance for Linux-based deployments, and terminology assumes a Windows environment (e.g., .NET Framework, environment variables like %ROLEROOT%).

Recommendations:

Add explicit documentation or notes for Linux-based worker roles, including how certificates, environment variables, and startup tasks are handled on Linux.
Provide Linux-specific examples for startup tasks (e.g., using shell scripts instead of CMD files) and clarify file encoding requirements for Linux.
Document how certificate management works on Linux (e.g., using PEM files or Linux certificate stores), and provide equivalent instructions.
Clarify whether environment variables like %ROLEROOT% are available or mapped differently on Linux, and provide examples using $ROLEROOT or similar syntax.
Include guidance for cross-platform compatibility, highlighting any differences or limitations when deploying worker roles on Linux VMs.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation displays a moderate Windows bias. PowerShell and Windows-specific concepts (such as the Azure: drive and PowerShell provider) are explained in detail, with Windows copy/paste shortcuts listed first and PowerShell examples provided alongside Bash. Windows tools and browser instructions (Edge/Chrome) are prioritized, while Linux is mentioned but less emphasized. Some features, like the Azure: drive, are described only in the context of PowerShell, with no Linux/Unix shell equivalent discussed.

Recommendations:

Ensure Linux/Bash examples are always provided alongside PowerShell, and consider listing Bash examples first or equally.
When describing features like the Azure: drive, clarify their relevance (or lack thereof) for Bash/Linux users.
Provide Linux-specific troubleshooting steps or notes where applicable, not just Windows/PowerShell-centric guidance.
Balance browser instructions to include Firefox/Linux-specific steps, not just Edge/Chrome.
Where Windows tools or patterns are mentioned, ensure Linux equivalents are also explained (e.g., file system access, command-line tools).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a moderate Windows bias, primarily through a heavy emphasis on PowerShell features (such as the Azure drive and numerous PowerShell modules), listing Windows-centric tools (like Exchange Online PowerShell, Microsoft Graph PowerShell, and SqlServer PowerShell modules), and often mentioning PowerShell before Bash or Linux equivalents. While Linux tools and shells are acknowledged, the documentation gives more prominence to PowerShell and Windows-oriented workflows.

Recommendations:

Provide equivalent Bash/Linux examples for features highlighted with PowerShell (e.g., show how to navigate Azure resources using Azure CLI in Bash, not just Azure drive in PowerShell).
Balance the listing of tools by including more Linux-native or cross-platform tools alongside PowerShell modules (e.g., mention Azure CLI and Bash scripts before or alongside PowerShell cmdlets).
Clarify which features are exclusive to PowerShell and which are available in Bash, and provide guidance for Linux users where functionality differs.
Include more Linux/Bash-focused productivity and scripting examples, especially in sections where PowerShell is featured.
Reorder tool and feature lists to alternate or group by platform, rather than consistently leading with PowerShell/Windows tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

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 users. There are no examples or guidance for performing these tasks using Linux-native tools or cross-platform methods, and the only scripting environment referenced is PowerShell, which is traditionally associated with Windows environments.

Recommendations:

Provide equivalent instructions and examples for performing Microsoft Teams Direct Routing configuration using cross-platform PowerShell Core (pwsh), and clarify that it can be used on Linux and macOS as well.
If possible, include examples using Microsoft Graph API or other RESTful interfaces that can be accessed from any platform, not just PowerShell.
Explicitly mention that PowerShell Core is available on Linux and macOS, and provide installation instructions or links.
Where applicable, offer bash or shell script equivalents for common administrative tasks, or clarify when tasks are only possible via PowerShell.
Add a section or note addressing Linux and macOS administrators, outlining any platform-specific considerations or limitations.

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 provided exclusively in PowerShell syntax. There is no mention of Bash or Linux shell equivalents, nor are alternative tools or predictive features for non-PowerShell environments discussed. The guidance assumes the user is operating within a PowerShell-centric workflow, which, while available in Azure Cloud Shell, does not address users who prefer or require Bash or other Unix shells.

Recommendations:

Add equivalent examples and instructions for Bash users in Azure Cloud Shell, such as how to enable or configure command prediction features (e.g., bash-completion, fish shell suggestions, or other relevant tools).
Explicitly mention the availability (or lack) of predictive IntelliSense features in Bash or other shells within Cloud Shell, and provide links or references to documentation for those environments.
Balance the documentation structure so that both PowerShell and Bash/Linux users can easily find relevant information, possibly by splitting sections or providing parallel instructions.
If predictive features are not available in Bash, state this clearly and suggest any workarounds or alternative productivity tools for Linux shell users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides detailed PowerShell command examples (Get-CloudDrive, Dismount-CloudDrive) for managing Azure Cloud Shell storage, but does not include equivalent Bash or Linux shell commands. The only explicit command-line examples are in PowerShell, and the section 'Use PowerShell commands' is present without a corresponding 'Use Bash commands' section. This creates a Windows/Powershell bias and may disadvantage users of the Bash environment in Cloud Shell.

Recommendations:

Add equivalent Bash/Azure CLI command examples for all PowerShell commands shown (e.g., show how to get file share info and unmount clouddrive using Bash/Azure CLI).
Include a 'Use Bash commands' section parallel to the 'Use PowerShell commands' section.
When introducing command-line examples, present both PowerShell and Bash/Azure CLI commands side-by-side or indicate which environment each applies to.
Review the documentation for any other sections where only Windows/Powershell tools or patterns are mentioned, and add Linux/Bash equivalents where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell parameters and patterns without providing equivalent Linux or cross-platform CLI examples. The configuration table lists PowerShell parameters alongside Teams Admin Center settings, but does not mention or provide examples for Linux-based management tools, Bash, or cross-platform scripting. There are no Linux-specific instructions or references to non-Windows tooling for any of the administrative steps.

Recommendations:

Provide equivalent examples using cross-platform tools such as Azure CLI, Microsoft Graph API, or Bash scripts where possible.
Explicitly mention whether the PowerShell commands can be run on PowerShell Core (which is cross-platform) and provide installation instructions for Linux/macOS if so.
Include references or links to Linux-based management options for Teams Direct Routing and Azure Communications Gateway, if available.
Clarify in each step whether the instructions are Windows-only or cross-platform, and offer alternatives for Linux users.
Where administrative actions are performed in the Teams Admin Center, note that this is web-based and platform-independent.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is heavily biased toward Windows environments, specifically PowerShell. All command-line instructions are provided exclusively for PowerShell, with no mention of Linux or cross-platform alternatives such as Azure CLI, Bash, or Cloud Shell. The steps assume the user is running PowerShell on Windows, including instructions to 'open PowerShell as admin,' and do not provide equivalent guidance for Linux or macOS users. Windows tools and patterns are referenced throughout, and there are no Linux-specific notes or parity examples.

Recommendations:

Provide equivalent Azure CLI or Bash commands for all PowerShell instructions, especially for module installation and authentication steps.
Explicitly mention cross-platform options such as Azure Cloud Shell, which supports both PowerShell and Bash and works on any OS.
Add notes or sections for Linux/macOS users, clarifying any differences in command syntax, prerequisites, or permissions.
Avoid instructions that are Windows-specific (e.g., 'open PowerShell as admin') without offering alternatives for non-Windows systems.
Where PowerShell modules are required, clarify their cross-platform compatibility or provide alternatives if available.
Consider reordering examples or providing parallel instructions so that Linux/macOS users are not an afterthought.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively providing PowerShell commands for critical configuration steps (e.g., setting PSTN gateways for voice routes) without mentioning or providing equivalent instructions for Linux or cross-platform environments. There is no reference to Linux tools or alternative command-line interfaces, and the documentation assumes the use of Microsoft 365 Admin Center and PowerShell, both of which are traditionally Windows-centric. No Linux-specific guidance or parity is offered.

Recommendations:

Provide equivalent instructions for Linux users, such as using PowerShell Core (pwsh) on Linux or alternative cross-platform tools where possible.
Explicitly state whether the required PowerShell modules and commands are supported on PowerShell Core and how to install them on Linux/macOS.
Include examples or notes for running the necessary commands from non-Windows environments, including any prerequisites or differences.
Mention any REST APIs or CLI alternatives (e.g., Azure CLI, Microsoft Graph API) that can be used for configuration, and provide sample usage.
Clarify any steps that are only possible from Windows and suggest workarounds or remote management options for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several ways. The JSON web token example and claims focus heavily on Windows-specific fields (e.g., 'x-ms-azurevm-is-windows', 'x-ms-azurevm-ostype': 'Windows'), and there is no mention of Linux-specific claims or examples. The documentation does not provide Linux-specific instructions, examples, or parity in the attestation process, nor does it mention Linux tools or patterns. The focus on Windows is evident both in the example data and the absence of Linux guidance.

Recommendations:

Include Linux-specific examples and claims in the JSON web token section, such as 'x-ms-azurevm-ostype': 'Linux' and relevant Linux distribution fields.
Provide sample attestation workflows or diagrams for Linux confidential VMs, highlighting any differences or considerations.
Mention Linux guest attestation libraries, tools, or SDKs if available, and provide links or references.
Ensure that API usage examples and error codes cover both Windows and Linux scenarios, noting any platform-specific differences.
Balance the documentation by presenting Windows and Linux information side-by-side where applicable, rather than focusing on Windows first or exclusively.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by relying heavily on PowerShell syntax and variables throughout the CLI examples, mentioning PowerShell installation as a prerequisite, and using Windows tools (such as PowerShell cmdlets and variable syntax) even when the main focus is Azure CLI. Additionally, in several places, Windows examples or references are presented before Linux equivalents.

Recommendations:

Provide all CLI examples in both PowerShell (Windows) and Bash (Linux/macOS) syntax, especially for variable assignment and command chaining.
List Linux/Bash installation and usage instructions alongside or before Windows/PowerShell instructions in the prerequisites.
Avoid using PowerShell-specific constructs (e.g., `$variable` assignment, backticks for line continuation, `Out-String | ConvertFrom-Json`) in generic Azure CLI examples; instead, provide Bash equivalents (e.g., `variable=value`, `\` for line continuation, `jq` for JSON parsing).
When referencing example parameter files, alternate the order or present Linux examples first where appropriate.
Explicitly state that all steps can be performed on Linux/macOS and provide links to relevant Bash shell documentation.
Where PowerShell modules or tools are required (e.g., Microsoft Graph SDK), provide equivalent instructions for Linux environments if available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments in the sections related to customer-managed keys and Azure Key Vault integration. Several steps use PowerShell syntax and Windows-specific tools (e.g., Microsoft Graph SDK for PowerShell), and there are no equivalent Bash or Linux-native command examples provided for these steps. This may hinder Linux users who expect parity in CLI-based documentation.

Recommendations:

For every PowerShell example, provide an equivalent Bash/Azure CLI example that works natively on Linux/macOS.
Where Microsoft Graph SDK is required, document how to perform the same actions using REST APIs or CLI tools available on Linux.
Explicitly note when a step is Windows-only, and provide alternative instructions for Linux users where possible.
Ensure that all scripting and automation steps can be performed in cross-platform environments, not just in PowerShell.
Review the use of Windows-centric terminology and tools, and balance with Linux-native approaches throughout the documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits several signs of Windows bias. PowerShell is the only example given for service principal setup, with no Azure CLI or Bash equivalent. Windows tools (e.g., PuTTY) are mentioned prominently as SSH clients, and Windows port (RDP 3389) is listed before Linux (SSH 22) in inbound port selection. The documentation refers to Windows connection instructions first and provides more detailed steps for Windows tools, while Linux instructions are less detailed and lack native SSH/Bash command examples.

Recommendations:

Provide Azure CLI and/or Bash equivalents for all PowerShell commands, especially for service principal and key creation steps.
Mention native SSH clients (e.g., OpenSSH) before or alongside PuTTY, and provide command-line SSH examples for Linux/macOS users.
List Linux ports (SSH 22) before Windows ports (RDP 3389) or present both equally.
Ensure that connection instructions for Linux VMs include native SSH command-line examples, not just PuTTY.
Wherever Windows-specific tools or patterns are mentioned, ensure Linux equivalents are also referenced with equal prominence.
Add explicit Linux/Bash/CLI examples for all steps that currently only show PowerShell or Windows-centric instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is generally neutral but exhibits subtle Windows bias in a few areas. Windows terminology and options are often mentioned before or more prominently than Linux equivalents, and some Linux-specific steps (such as installing the Azure DCAP client) are referenced but not detailed. There is also a lack of parity in post-deployment instructions, with explicit links and steps for Windows but not for Linux.

Recommendations:

Ensure Linux and Windows instructions are presented with equal prominence, or alternate which comes first.
Provide direct links and step-by-step instructions for Linux post-deployment tasks (e.g., installing the OE SDK on Linux), similar to the Windows guidance.
Include Linux-specific screenshots and examples where appropriate, not just generic or Windows-centric visuals.
Expand the 'Install Azure DCAP Client' section to include explicit Linux installation steps and commands.
Where Windows tools or patterns are mentioned (e.g., RDP, PowerShell), ensure Linux equivalents (e.g., SSH, Bash) are given equal or greater detail.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific TPM documentation, Secure Boot, and PCR management links, without mentioning or linking to Linux equivalents. All conceptual explanations and links are Windows-centric, and there are no Linux-specific examples, tools, or references for working with vTPMs in Azure confidential VMs.

Recommendations:

Include references and links to Linux TPM documentation, such as tpm2-tools and Linux kernel TPM documentation.
Provide examples or guidance for managing and attesting vTPMs in Linux-based Azure confidential VMs, including command-line examples using tpm2-tools.
Mention Linux equivalents for Secure Boot and Measured Boot, such as shim, GRUB2, and Linux Integrity Measurement Architecture (IMA).
Balance references to Windows and Linux throughout the document, ensuring parity in conceptual explanations and practical guidance.

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 and operational guidance implicitly targets Windows environments. There are no Linux-specific instructions, examples, or troubleshooting steps. The only service mentioned by name is PBIEgwService, which is a Windows service. There is no mention of Linux installation, service management, or compatibility, and all links and references are Windows-centric.

Recommendations:

Explicitly state whether the on-premises data gateway and Oracle client are supported on Linux, and if so, provide installation and configuration steps for Linux environments.
Include Linux-specific troubleshooting steps, such as how to check if the gateway service is running (e.g., using systemd or service commands), and how to install the Oracle client on Linux.
Mention Linux equivalents for service management (e.g., 'sudo systemctl restart gateway-service') alongside Windows instructions.
Clarify any platform limitations or differences in supported features between Windows and Linux.
Add screenshots or command-line examples from Linux environments where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While it provides both Linux and Windows instructions for the guest attestation client, the primary scripting example for performing the key release operation is a PowerShell script, which is more natural for Windows users. The script includes some Linux handling, but it is written in PowerShell, which is not a default or common shell on most Linux distributions. Additionally, references to tools like PowerShell cmdlets (e.g., Get-AzSubscription, Get-AzADUser) and .NET classes for certificate handling are prominent, and there are no equivalent Bash or Python examples for Linux users. The documentation often mentions Windows tools or patterns first or exclusively, and Linux alternatives are sometimes only referenced in passing or as an afterthought.

Recommendations:

Provide a full Bash (or Python) script example for performing the key release operation on Linux, including obtaining the attestation token, fetching the managed identity token, and making the HTTP request to Key Vault.
When referencing how to obtain object IDs or tenant IDs, include both PowerShell and Azure CLI commands, and present them in parallel or with equal prominence.
For certificate validation and JWT decoding, provide Linux-native alternatives (e.g., using OpenSSL, jq, or Python scripts) alongside PowerShell/.NET examples.
Ensure that all code samples and instructions are available for both Windows and Linux, and avoid assuming PowerShell is available on Linux unless explicitly stated and installation instructions are provided.
Where possible, present Linux and Windows instructions in parallel tabs or sections, rather than listing Windows first or exclusively.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (such as certmgr.exe and PowerShell), focusing on Windows certificate stores, and omitting equivalent Linux instructions or examples. Certificate management and validation steps are described only for Windows environments, with no mention of Linux-based approaches or commands. The documentation also refers to App Service Environment v3 'with Windows-only' plans as a requirement for certain features, without discussing Linux alternatives or parity.

Recommendations:

Provide equivalent Linux instructions for certificate management, such as using openssl or Linux certificate stores (e.g., /etc/ssl/certs).
Include Linux command-line examples (e.g., bash, openssl, keytool) alongside PowerShell and Windows tool references.
Clarify whether Linux-based App Service Environments or hosts are supported, and if not, explicitly state the limitation.
If features are Windows-only, explain why and offer guidance or workarounds for Linux users.
Reference cross-platform tools or approaches where possible, and avoid assuming the use of Windows by default.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias. It references 'IBM DB2 for Windows running in Azure virtualization' as the primary example of a cloud DB2 database, and in several places, Windows-specific terminology or authentication (e.g., 'Windows (Kerberos)') is mentioned. Username length for DB2 for Windows is highlighted (30 bytes), while Linux/UNIX is only briefly mentioned (8 bytes) and never prioritized. There are no Linux-specific examples, screenshots, or instructions, and the documentation does not mention Linux tools or patterns for connecting to DB2, nor does it provide parity in examples or troubleshooting for Linux environments.

Recommendations:

Provide explicit examples and screenshots for connecting to DB2 on Linux (and UNIX) servers, not just Windows.
When listing supported platforms or username formats, avoid listing Windows first or giving it more detail than Linux/UNIX.
Include Linux authentication options and clarify any differences or requirements for Linux-based DB2 servers.
Mention Linux/UNIX as equally valid cloud or on-premises DB2 deployment targets, not just Windows.
If there are Linux-specific considerations (such as case sensitivity, authentication, or firewall rules), document them.
Ensure parity in troubleshooting steps and connection string examples for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific environments (e.g., App Service Environment v3 (Windows plans only)), authentication methods (Windows Authentication), and tools (on-premises data gateway, which is primarily a Windows service). There are no examples or explicit instructions for Linux-based environments, nor are Linux authentication or deployment scenarios discussed. The documentation assumes the use of the Azure portal and Visual Studio Code, but does not mention Linux-specific considerations or alternatives. Windows authentication is described in detail, but there is no mention of Kerberos or other Linux-compatible authentication methods. The 'on-premises data gateway' requirement for on-prem SQL is a Windows-only solution, with no Linux alternative or workaround provided.

Recommendations:

Add explicit notes and examples for connecting from Linux-based environments, including any differences in connector support or authentication flows.
Document alternatives to the on-premises data gateway for Linux (such as self-hosted integration runtimes or other cross-platform options, if available).
If Windows Authentication is only supported via the data gateway (which is Windows-only), clarify this limitation and suggest Linux-compatible authentication methods (e.g., SQL Server Authentication, Azure AD authentication).
Include sample connection strings and walkthroughs for Linux-based deployments (e.g., running Logic Apps Standard on Linux App Service plans, if supported).
Review all tool and environment references to ensure Linux parity is addressed, or clearly state when features are Windows-only.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by providing a PowerShell script as the only automation example for enabling CORS on Azure Blob Storage, and by referencing Windows-centric tools (Azure Portal, Azure Storage Explorer) without mentioning Linux CLI alternatives. There are no explicit Linux or cross-platform command-line examples (such as Azure CLI or Bash scripts) for key tasks, and the PowerShell script is not accompanied by a Linux equivalent.

Recommendations:

Provide Azure CLI (az storage cors add ...) and Bash script examples alongside the PowerShell script for enabling CORS, ensuring parity for Linux and macOS users.
Explicitly mention that Azure Storage Explorer is cross-platform, and provide download links for Linux and macOS versions.
Include instructions for performing all tasks (such as uploading Swagger files, setting CORS, retrieving blob URLs) using the Azure CLI and/or REST API, not just the Azure Portal or PowerShell.
Add a note clarifying that all steps can be performed on Windows, Linux, or macOS, and link to relevant cross-platform documentation where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily biased towards Windows environments. It explicitly states that the File System connector only supports Windows file systems and Windows operating systems, and all examples, prerequisites, and authentication methods are Windows-centric (e.g., Windows authentication, domain\username format, references to Windows domains, and App Service Environment v3 with Windows plans only). There are no examples, instructions, or even mentions of Linux file systems or how to connect to non-Windows file shares. Linux users are not addressed, and no alternatives or workarounds are suggested.

Recommendations:

Clearly state early in the documentation that Linux file systems are not supported, and provide a roadmap or link to feature requests if Linux support is planned.
If partial Linux support exists (e.g., via SMB/CIFS shares from Linux servers), document the requirements and limitations, and provide Linux-specific examples.
Offer alternative approaches for Linux environments, such as using SFTP, NFS, or other connectors that support Linux file systems, and link to relevant documentation.
Include a section comparing Windows and Linux support, so users can quickly determine applicability.
If Linux support is not planned, suggest community or third-party solutions for Linux file system integration.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides detailed instructions and code examples for Azure PowerShell, a Windows-centric tool, without offering equivalent examples for Linux-native tools (such as Azure CLI, Bash, or REST via curl). The PowerShell method is given a dedicated section, and troubleshooting steps are also PowerShell-based. No Linux shell or cross-platform command-line examples are provided, and there is no mention of Linux-specific considerations or parity.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell instructions, including configuration updates and troubleshooting.
Provide REST API examples using curl or HTTPie, which are cross-platform and commonly used on Linux.
Explicitly mention that all management operations can be performed from Linux/macOS using Azure CLI or REST, and provide links or examples.
Include troubleshooting steps using Azure CLI or REST, not just PowerShell.
Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., avoid referencing Windows-only tools or paths).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a bias toward Windows by exclusively referencing Windows-based tools (such as Microsoft Host Integration Server and HIS Designer, which require .NET Framework 4.8 and Visual Studio), and does not mention or provide any Linux-compatible alternatives or examples. The setup and screenshots are all based on Windows environments, and there is no guidance for users on Linux or macOS platforms.

Recommendations:

Provide information on whether the HIS Designer and related tooling are available or supported on Linux or macOS, or explicitly state if they are Windows-only.
If possible, suggest or develop cross-platform alternatives for generating HIDX files or parsing host files, or provide guidance for using the connector from non-Windows environments.
Include example workflows or instructions that can be followed from Linux or macOS, such as using Azure CLI, VS Code (cross-platform), or other non-Windows tools.
Clarify any prerequisites that are Windows-specific, and offer workarounds or alternatives for Linux users where feasible.
Add screenshots or walkthroughs using cross-platform tools or interfaces, not just Visual Studio or Windows-only applications.

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 (Host Integration Server Designer, which requires .NET Framework 4.8) for generating required metadata files. There are no Linux or cross-platform alternatives mentioned for these critical steps, and the prerequisites and setup instructions assume a Windows environment. No Linux-specific guidance or parity is provided.

Recommendations:

Provide information about whether the Host Integration Server Designer or equivalent tooling is available for Linux or via cross-platform means (e.g., .NET Core, containerized solutions).
If no Linux-native tooling exists, explicitly state this limitation and suggest possible workarounds (such as using a Windows VM or container).
Include Linux-specific instructions or examples where possible, especially for steps like file management, installation, and workflow integration.
Consider developing or recommending cross-platform tools for generating HIDX files to improve accessibility for non-Windows users.
Clarify in the prerequisites section that the current tooling is Windows-only, and provide links or guidance for Linux users to set up the necessary environment.

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) and the HIS Designer for Logic Apps, which are Windows-only tools. All setup and prerequisite instructions assume the use of these Windows-based tools, with no mention of Linux-compatible alternatives or workflows. There are no examples or guidance for Linux users, and the documentation does not clarify whether the required tools or processes are available or supported on non-Windows platforms.

Recommendations:

Explicitly state platform requirements and limitations, including whether HIS Designer and related tools are Windows-only.
If Linux-compatible tools or workflows exist (e.g., command-line utilities, cross-platform designer tools, or REST APIs), provide equivalent instructions and examples for Linux users.
If no Linux alternatives exist, acknowledge this limitation and suggest possible workarounds (such as using a Windows VM or container).
Consider collaborating with product teams to develop or document Linux-compatible tooling or processes for cross-platform parity.
Add a section addressing common questions for non-Windows users, including guidance on how to proceed if they are developing from Linux or macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by referencing Windows DNS and its default zone file location before mentioning BIND (the most common Linux DNS server), and by providing explicit Windows file paths (e.g., %systemroot%\system32\dns) without equivalent Linux examples. There are no Linux command-line or file path examples, and the process for obtaining zone files from Linux/BIND is less detailed than for Windows. No Linux-specific tools or workflows are mentioned, and screenshots and instructions are entirely platform-agnostic or Windows-oriented.

Recommendations:

Provide explicit Linux/BIND examples for obtaining zone files, including common file paths (e.g., /etc/bind/).
Include sample commands for exporting zone files from BIND (e.g., using 'cp', 'cat', or 'named-checkzone').
Mention Linux tools and workflows alongside Windows ones, not after.
Ensure parity in detail between Windows and Linux/BIND instructions.
Consider adding a table or section comparing default zone file locations and export methods for both Windows DNS and BIND/Linux.
Where Windows paths are given, provide Linux equivalents in parallel.

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, referencing PowerShell before Bash, and omitting explicit Linux or cross-platform examples. The focus on Visual Studio (a Windows-first IDE) and lack of Linux-specific guidance or screenshots further reinforce this bias. While Azure CLI and AZD are cross-platform, the documentation does not provide parity in Linux-specific instructions or highlight Linux-native development environments.

Recommendations:

Include explicit Linux examples and workflows, such as using VS Code on Linux, or developing/deploying from a Linux terminal.
Provide Bash-first or Bash-equal examples alongside PowerShell, especially in CLI automation contexts.
Mention Linux-native editors (e.g., Vim, Emacs, JetBrains IDEs) as alternatives to Visual Studio.
Add screenshots or walkthroughs from Linux environments where possible.
Clarify that Azure CLI and AZD are cross-platform, and provide installation or usage notes for Linux users.
Balance the order of tool presentation (e.g., mention Bash before or alongside PowerShell).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias by providing only PowerShell command examples for pipeline deployment and execution, referencing Windows file paths (e.g., C:\ADF), and omitting any equivalent instructions for Linux or cross-platform environments (such as Azure CLI or Bash). There is no mention of Linux tools or shell scripting, and the workflow assumes a Windows/PowerShell context throughout.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell commands, using Bash syntax and Linux file paths (e.g., /home/user/ADF).
Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
Where file paths are referenced, show both Windows and Linux path formats.
Consider providing a table or section comparing PowerShell and CLI/Bash approaches for common tasks.
Update the note and tutorial references to include Linux/macOS walkthroughs, not just PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented towards Windows users by focusing exclusively on Visual Studio, a Windows-centric IDE, for all steps including project creation, deployment, and resource management. There are no examples or instructions for performing these tasks using cross-platform tools or on Linux/macOS. The workflow assumes the use of Visual Studio GUI and does not mention alternatives such as the Azure CLI, Docker CLI, or VS Code, which are more commonly used on Linux. While the Docker container is set to Linux, the development and deployment process is entirely Windows/Visual Studio-centric.

Recommendations:

Add parallel instructions for deploying to Azure Container Apps using cross-platform tools such as the Azure CLI, Docker CLI, and VS Code.
Provide command-line examples for project creation, Docker image building, and deployment that work on Linux and macOS.
Include a section or links for Linux/macOS users who may not have access to Visual Studio, outlining equivalent workflows.
Mention and demonstrate how to use GitHub Actions or Azure DevOps pipelines for CI/CD from non-Windows environments.
Clarify in the prerequisites that the tutorial is Visual Studio-specific and provide references to cross-platform alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and PowerShell examples for managing environment variables in Azure Container Apps, but the PowerShell section is significantly more detailed and complex, reflecting a Windows-centric approach. PowerShell (a Windows-native tool) is given equal prominence to Azure CLI, and the PowerShell workflow is described in much greater depth, including object creation and manipulation, which may be unfamiliar or irrelevant to Linux/macOS users. There is no mention of Linux-specific tools, shell scripting, or considerations for non-Windows environments, and the documentation does not clarify that Azure CLI is cross-platform while PowerShell examples are primarily for Windows users.

Recommendations:

Clarify that Azure CLI is cross-platform and suitable for Linux/macOS/Windows, while PowerShell is primarily for Windows users (or for those who have installed PowerShell Core on other platforms).
Provide Bash shell scripting examples alongside PowerShell, especially for common automation scenarios, to ensure Linux users have parity.
Reduce the depth and complexity of the PowerShell section unless there is a specific Windows-only feature being demonstrated. Instead, focus on Azure CLI as the primary, platform-neutral interface.
Explicitly state in each section which platforms the instructions are intended for, and recommend Azure CLI for Linux/macOS users.
If PowerShell is included, also mention PowerShell Core and its cross-platform capabilities, but do not assume all users have it installed.
Consider adding a table or quick-start guide comparing Azure CLI and PowerShell usage for common tasks, with notes on platform compatibility.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several ways: When creating a VM for testing, the only OS option shown is Windows Server 2022, and the CLI example uses the Win2022Datacenter image. The instructions for verifying connectivity exclusively use PowerShell commands inside the Windows VM, with no mention of Linux alternatives (e.g., using nslookup or dig on a Linux VM). There are no examples or guidance for deploying or testing with a Linux VM, nor are Linux command-line tools or shell examples provided for the verification steps. The portal instructions also default to Windows images and workflows.

Recommendations:

Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) in both portal and CLI sections, including appropriate image references (e.g., UbuntuLTS).
Include Linux command-line examples for verifying DNS resolution and connectivity (e.g., using nslookup or dig in bash).
When presenting a list of OS options or tools, avoid defaulting to Windows first; present both Windows and Linux options, or alternate their order.
Instruct users on how to run equivalent commands in both PowerShell (Windows) and bash (Linux), especially for common tasks like DNS lookups.
Clarify that the private endpoint functionality is OS-agnostic and works with both Windows and Linux VMs.

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 there are several signs of Windows bias: PowerShell examples are always present and sometimes appear before Bash, the Bash examples use 'SET' (a Windows command) instead of 'export' for environment variables, and there is no mention of Linux-specific tools or patterns. Additionally, there are no explicit Linux/macOS instructions or troubleshooting tips, and the CLI sections do not clarify cross-platform differences.

Recommendations:

Replace 'SET' with 'export' in Bash examples to align with standard Linux/macOS shell usage.
Ensure Bash (Linux/macOS) examples are listed before PowerShell (Windows) examples to avoid Windows-first bias.
Add explicit notes or troubleshooting tips for Linux/macOS users where command syntax or behavior may differ.
Include references to Linux/macOS terminal environments and tools where appropriate.
Audit all CLI examples for platform-appropriate syntax and clarify any differences in environment variable usage or command output.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias by recommending Docker Desktop (which is primarily for Windows and macOS) as the default Docker installation method, and by not mentioning native Linux Docker installation or Linux-specific development workflows. Visual Studio Code is presented as the primary editor, with no mention of alternative editors or command-line workflows common on Linux. There are no Linux-specific troubleshooting or setup instructions, and the documentation omits guidance for users developing on native Linux environments.

Recommendations:

Include instructions for installing Docker Engine natively on Linux distributions (e.g., Ubuntu, Fedora), not just Docker Desktop.
Mention alternative editors and workflows commonly used on Linux, such as JetBrains IDEs, Eclipse, or command-line tools.
Provide Linux-specific troubleshooting tips (e.g., using systemd to manage Docker, checking permissions for the docker group).
When listing tools, avoid phrasing that implies Docker Desktop is required for all platforms; clarify that Linux users should install Docker Engine.
Add explicit Linux shell command examples where relevant (e.g., using apt or yum for installation, using systemctl to manage Docker).
Ensure parity in examples and instructions for both Windows and Linux environments, especially in setup and debugging sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Portal-based troubleshooting steps are described using generic UI instructions, but when command-line examples are given, PowerShell and Windows-specific tools are often mentioned or prioritized. For example, the section on verifying container image accessibility refers to running Docker in an 'elevated command prompt' and specifically calls out 'Docker on Windows', without mentioning Linux or macOS equivalents. When discussing Azure CLI and PowerShell, the PowerShell module is given its own tab and update instructions, but there is no equivalent for Linux shell environments beyond a single Bash example. There are no explicit Linux/macOS troubleshooting notes or examples, and Windows terminology (e.g., 'elevated command prompt') is used exclusively.

Recommendations:

Wherever 'elevated command prompt' or 'Docker on Windows' is mentioned, add equivalent instructions for Linux (e.g., 'open a terminal and run with sudo if needed') and macOS.
When referencing Docker, clarify that the command works on all platforms and provide links to Docker installation instructions for Linux and macOS, not just Windows.
For Azure CLI and PowerShell instructions, ensure parity by providing Bash/zsh examples and update instructions for Linux/macOS environments, not just PowerShell.
Avoid Windows-specific terminology (like 'elevated command prompt') or always pair it with cross-platform equivalents.
Explicitly state that all CLI commands are cross-platform unless otherwise noted, and provide troubleshooting notes for common Linux/macOS issues where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits 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 is no mention of Linux, Bash, or cross-platform alternatives for running the pipeline or managing files. The tutorial and walkthrough links also focus on Azure PowerShell, reinforcing the Windows-centric approach.

Recommendations:

Provide equivalent Bash/CLI examples for Linux and macOS users, using Azure CLI commands (az datafactory ...).
Use cross-platform file path examples (e.g., /home/user/ADF or <path-to-adf-folder>) or clarify that file paths should be adapted to the user's OS.
Include a note or section on how to perform the same steps on Linux/macOS, including installation and authentication steps for Azure CLI.
Reference tutorials or quickstarts that use Azure CLI or REST API, not just Azure PowerShell.
Avoid assuming the user is on Windows by default in instructions and examples.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily Windows-centric, focusing exclusively on Microsoft HPC Pack, which only supports Windows nodes. All configuration, prerequisites, and tooling (such as the azhpcpack.ps1 CLI) are Windows-specific, with no mention of Linux support, Linux-based alternatives, or cross-platform considerations. Windows tools, patterns, and terminology are used throughout, and Linux is only mentioned to state that Linux compute nodes are not supported.

Recommendations:

Clearly state at the beginning that the integration is Windows-only and that Linux support is not available, to set expectations.
If Linux support is planned, include a roadmap or reference to alternative solutions for Linux clusters (e.g., CycleCloud integration with Slurm or other Linux schedulers).
Where possible, provide parity in documentation by referencing Linux-based HPC solutions and how they can be integrated with CycleCloud.
If any cross-platform features exist (such as Azure Key Vault or Managed Identities), provide Linux command-line examples (e.g., using Azure CLI or bash scripts) alongside PowerShell/Windows examples.
Avoid using only Windows file paths and PowerShell scripts; if the CLI or tooling is Windows-only, explicitly state this and suggest alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific optimization and best practices in the 'Next steps' section, specifically linking to Windows Dockerfile optimization and Windows container management. There are no equivalent Linux or cross-platform examples or references, and Linux containerization or migration scenarios are not mentioned. The focus on Windows tools and the absence of Linux-specific guidance or parity in examples suggest a bias toward Windows environments.

Recommendations:

Include links and references to Linux Dockerfile optimization and best practices for Linux containers, especially for AKS and App Service scenarios.
Add examples or guidance for assessing and migrating Linux-based web apps, not just Windows-based ones.
Ensure that any optimization or best practices documentation referenced covers both Windows and Linux platforms, or provide parallel links for each.
Explicitly mention that Azure Migrate supports both Windows and Linux workloads, and provide steps or considerations unique to Linux migrations where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by listing Windows paths and behaviors before Linux equivalents, referencing Windows-specific features and limitations, and failing to provide Linux-specific command examples or details where relevant. Some features are described as unsupported on Windows, but Linux-specific usage is not elaborated. There is also a lack of Linux-specific troubleshooting or usage notes, and no Linux shell or scripting examples are provided.

Recommendations:

Alternate the order of Windows and Linux references, or list Linux first where it is the primary platform.
Provide Linux-specific command examples, especially for features not supported on Windows (e.g., 'jetpack run_on_shutdown').
Include Linux shell scripting examples where relevant (e.g., registering shutdown scripts, log file locations, service management).
Add troubleshooting notes or caveats for Linux environments, such as permissions, systemd integration, or SELinux/AppArmor considerations.
Clarify any differences in behavior or requirements between Windows and Linux, especially for environment variables, file paths, and service management.
Ensure that documentation for features that are Linux-only (or have different behavior on Linux) is as detailed as for Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references deploying global parameters via a PowerShell script as the only example of scripting automation for CI/CD, without mentioning Linux-compatible alternatives (such as Azure CLI, Bash, or cross-platform scripting). This suggests a bias toward Windows tooling and omits guidance for users on Linux or macOS platforms.

Recommendations:

Provide equivalent examples using Azure CLI or Bash scripts for deploying global parameters, ensuring Linux and macOS users have clear guidance.
Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, or clarify if only Windows PowerShell is supported.
Add a note or section describing how to perform CI/CD tasks related to global parameters on Linux environments.
Where possible, present cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools like PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias, particularly in the automated testing section, where .NET/NUnit with Visual Studio and PowerShell are highlighted as primary tools for automated testing and CI/CD scripting. There are no examples or explicit mentions of Linux-based tools, shell scripting, or cross-platform alternatives for these tasks. The documentation assumes familiarity with Windows-centric tooling and omits Linux/Unix equivalents or guidance.

Recommendations:

Include examples and references for Linux-based CI/CD and testing workflows, such as using bash scripts, Python, or cross-platform test runners.
Mention and provide examples for running Azure CLI commands in both Windows (PowerShell) and Linux (bash) environments.
Highlight cross-platform editors and tools (e.g., VS Code, Git CLI, GitHub Actions) alongside Visual Studio and PowerShell.
Add explicit notes or sections on how to perform key tasks (e.g., automated testing, deployment scripting) on Linux/macOS systems.
Where PowerShell is mentioned, provide equivalent bash or shell script snippets.
Reference cross-platform CI/CD pipelines (e.g., GitHub Actions, Azure Pipelines with Linux agents) and show parity in instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented towards Windows environments, with all examples and instructions assuming the use of Windows tools such as SSMS, dtutil, cmdkey, net use, and DOS batch scripting. There is no mention of Linux or cross-platform alternatives, and no guidance is provided for users operating from Linux or macOS systems.

Recommendations:

Provide equivalent instructions and examples for Linux environments, including how to connect to Azure Files (e.g., using SMB mounting on Linux) and how to run dtutil if available or alternatives for package deployment.
Mention whether SSMS and dtutil are available or supported on non-Windows platforms, and if not, suggest workarounds or alternative tools (such as Azure Data Studio or REST APIs).
Include PowerShell Core (cross-platform) or Bash script examples where possible, especially for batch operations.
Clarify any platform limitations explicitly at the start of the documentation, so Linux/macOS users know what is and isn't supported.
If certain features are Windows-only, provide links or references to cross-platform approaches for managing SSIS packages in Azure.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. While it does not explicitly present Windows or PowerShell commands as primary examples, it references PowerShell APIs and Windows-centric tools (such as PowerShell and Nunit) without providing equivalent Linux or cross-platform alternatives. There are no explicit Linux shell, Bash, or CLI examples, and the documentation assumes familiarity with Windows-based DevOps tooling. The mention of PowerShell APIs and Nunit for testing, without mentioning Linux-friendly alternatives (e.g., Bash, pytest, xUnit), further reinforces this bias. Additionally, there are no explicit instructions or examples for Linux users, and no mention of cross-platform command-line tools.

Recommendations:

Provide equivalent Linux/Bash/CLI examples alongside any PowerShell or Windows-specific instructions.
Mention and provide examples for cross-platform testing frameworks (e.g., pytest for Python, xUnit for .NET) in addition to Nunit.
When referencing PowerShell APIs, also mention Azure CLI or REST API alternatives that are platform-agnostic.
Explicitly state when a tool or method is cross-platform, and clarify any platform-specific limitations.
Include troubleshooting steps or automation examples that work on Linux agents (e.g., using Bash scripts in Azure Pipelines).
Review all references to Windows tools and ensure Linux equivalents are documented and easy to find.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias primarily through its reliance on PowerShell scripts for configuration (notably in the custom DNS setup), the absence of any Linux/bash/CLI examples for scripting or automation, and the exclusive mention of Windows-centric tools and file formats (e.g., .ps1 scripts). There are no references to Linux shell scripts or cross-platform alternatives, and the related content section only highlights a PowerShell-based approach for joining the virtual network, omitting Azure CLI or other Linux-friendly methods.

Recommendations:

Provide equivalent examples using Azure CLI and bash scripts for all configuration steps, especially for custom setup scripts and automation.
Include references and links to Linux-based or cross-platform tooling in the related content section (e.g., 'Join Azure-SSIS IR to a virtual network via Azure CLI').
Offer sample scripts in both PowerShell (.ps1) and bash (.sh) formats, or use platform-agnostic scripting where possible.
Explicitly state platform compatibility for provided scripts and instructions, and guide users on adapting steps for Linux environments.
Ensure that any downloadable resources (like setup scripts) have Linux-compatible versions or clear instructions for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. It explicitly states that Azure-SSIS IR runs on Windows Server 2019 and lists only Windows-based components, drivers, and tools (e.g., OLEDB, ODBC, WMI, MSMQ, SQL Server Native Client, Excel, Access Database Engine). There is no mention of Linux support, Linux-based tools, or cross-platform alternatives. All examples and terminology are Windows-centric, and there are no Linux equivalents or instructions provided.

Recommendations:

Clearly state in the introduction that Azure-SSIS IR is Windows-only, if that is the case, or clarify any Linux support or roadmap.
If Linux support is planned or available, provide a parallel table or section listing Linux-compatible components, drivers, and tasks.
Where possible, mention cross-platform alternatives to Windows-specific technologies (e.g., alternatives to WMI, MSMQ, or Excel/Access drivers).
Add a note or FAQ addressing the lack of Linux support and suggest workarounds or alternatives for Linux users.
Ensure that future documentation for similar services includes both Windows and Linux perspectives, or explicitly states platform limitations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows environments in its discussion of self-hosted integration runtimes. It references Windows-specific tools (such as the diagnostic tool and PowerShell-based setup), omits explicit Linux installation or management examples, and links to articles that imply or directly use Windows-centric approaches. There is no mention of Linux as a supported platform for self-hosted integration runtime, nor are there examples or guidance for Linux users, which may lead readers to assume Windows is the only or primary supported environment.

Recommendations:

Explicitly state platform support for self-hosted integration runtime, including whether Linux is supported.
Provide parallel Linux-based setup, configuration, and management instructions alongside any Windows/PowerShell examples.
Reference or link to Linux-specific diagnostic and monitoring tools if available, or clarify any limitations.
Ensure that examples and linked articles (such as those for shared integration runtime setup) include both Windows and Linux instructions, or clarify platform applicability.
Use neutral language (e.g., 'machine' instead of 'Windows machine') unless a feature is truly platform-specific, and always mention alternatives for Linux 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 command-line examples are provided exclusively in PowerShell, with explicit references to Windows file paths (e.g., C:\ADF). There are no examples or guidance for running the same tasks on Linux or macOS, nor are cross-platform tools (such as Azure CLI) mentioned. The instructions and walkthroughs assume a Windows environment, potentially excluding users on other platforms.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works on Windows, Linux, and macOS.
Use platform-agnostic file paths in examples, or provide both Windows and Linux/macOS path examples (e.g., C:\ADF and ~/ADF).
Explicitly mention that the JSON definitions and pipeline concepts are platform-independent, and show how to deploy/run them from Linux/macOS.
Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.
Where possible, use screenshots or instructions that are not specific to Windows UI conventions.
Review related tutorials and quickstarts to ensure they also offer Linux/macOS parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments, primarily through the exclusive use of PowerShell for scripting examples and references to Windows-specific tools and concepts (e.g., Windows firewall rules, RDP/port 3389, and Secure Access Workstation). There are no Linux CLI (Azure CLI, Bash) equivalents or examples provided, and no mention of Linux-based tooling or workflows. This may hinder users who manage Azure resources from Linux or cross-platform environments.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside PowerShell scripts for all automation and configuration tasks.
Include notes or sections on how to perform relevant firewall and NSG configurations from Linux environments, referencing tools like iptables, ufw, or Azure CLI.
Clarify that RDP/port 3389 and Windows firewall rules are only relevant for Windows-based nodes, and provide guidance for Linux-based scenarios if supported.
Ensure that all scripting and automation guidance is cross-platform, or clearly indicate when a step is Windows-specific.
Add a section or callout for Linux administrators, summarizing any differences or additional steps required when managing Azure-SSIS IR from Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias, particularly in the Self-hosted Integration Runtime (IR) section, where it explicitly states that the self-hosted IR is only supported on Windows operating systems. There is no mention of Linux support, installation steps, or parity. Additionally, tools and examples referenced for SSIS workloads (such as SQL Server Data Tools and SQL Server Management Studio) are Windows-centric, with no alternatives or guidance for Linux users. No PowerShell-specific examples are present, but the overall pattern is Windows-first and Windows-only for critical features.

Recommendations:

Add explicit information about Linux support status for Self-hosted IR. If not supported, clarify roadmap or alternatives.
If Linux support is available or planned, provide installation and configuration instructions for Linux environments.
Include references to cross-platform tools or alternatives for managing SSIS packages, or clarify if only Windows tools are supported.
Wherever possible, provide parity in examples and instructions for both Windows and Linux environments.
If certain features are Windows-only, clearly state this early in the documentation and suggest workarounds or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. While many examples and configurations are cross-platform (e.g., JSON for Linux-based clusters), there is a notable preference for Windows tools and patterns, such as referencing PowerShell cmdlets (New-AzBatchAccount, New-AzBatchPool) and Microsoft Azure Storage Explorer for storage management. PowerShell is mentioned before portal or CLI alternatives, and there is no mention of Linux-native tools or shell commands for equivalent operations. The documentation does specify Linux as the default for HDInsight clusters, but operational guidance and tooling references are Windows-centric.

Recommendations:

Provide equivalent Azure CLI and/or Bash shell commands alongside PowerShell cmdlets for resource creation and management (e.g., for Azure Batch accounts and pools).
Mention cross-platform or Linux-native tools for storage management (e.g., az storage blob delete, rclone, or s3cmd) in addition to Microsoft Azure Storage Explorer.
When referencing tools or patterns, avoid listing Windows/PowerShell options first; instead, present cross-platform solutions or alternate between Windows and Linux approaches.
Explicitly state when features or examples are cross-platform, and provide guidance for both Windows and Linux users where applicable.
Include troubleshooting and operational instructions (such as SSH access, file deletion, or script actions) with both Windows and Linux command-line examples.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by prominently featuring PowerShell as a primary automation tool, listing it before REST API and omitting Linux-native alternatives (such as Azure CLI or Bash scripting). There are no Linux-specific examples or references to cross-platform tooling, and the quickstart and creation sections prioritize Windows-centric tools and workflows.

Recommendations:

Add Azure CLI examples and quickstarts alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash scripting or shell-based automation examples for dataset creation and management.
When listing tools or SDKs, present cross-platform options (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
Explicitly mention that all features are available on Linux and macOS, and provide links to relevant Linux documentation.
Ensure screenshots and UI walkthroughs do not assume a Windows environment (e.g., avoid Windows-only UI elements or terminology).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by prominently featuring PowerShell as a primary automation/example tool, listing it before cross-platform alternatives, and omitting explicit Linux/CLI examples. The tooling and quickstart sections prioritize Windows-centric tools (PowerShell, .NET) and do not mention or provide parity for Linux-native approaches (such as Azure CLI or Bash scripting).

Recommendations:

Add explicit examples and quickstarts using Azure CLI and Bash scripts, which are cross-platform and commonly used on Linux.
List cross-platform tools (such as REST API, Azure CLI) before or alongside Windows-specific tools like PowerShell and .NET.
Include a section or callout for Linux/macOS users, highlighting supported tools and any differences in workflow.
Ensure that all automation and scripting guidance includes both PowerShell and Bash/Azure CLI equivalents.
Review and update related tutorials to provide Linux-friendly instructions and screenshots where appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page references 'All cumulative Windows and .NET framework updates' as a key update, without mentioning equivalent updates or considerations for Linux environments. There are no Linux-specific examples, updates, or tools referenced, and the update information is Windows-centric. This suggests a Windows-first perspective and a lack of Linux parity.

Recommendations:

Include information about Linux support or lack thereof for Azure Data Box Gateway, if applicable.
If Linux is supported, mention relevant Linux kernel or package updates alongside Windows/.NET updates.
Provide examples or notes for Linux users, such as update procedures or known issues specific to Linux environments.
Clarify in the documentation if the product is Windows-only to set expectations for cross-platform users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page provides sample PowerShell commands and references a PowerShell-based tutorial for running pipelines, with no equivalent examples or guidance for Linux or cross-platform CLI users (e.g., Azure CLI, Bash). This prioritizes Windows tooling and omits Linux-friendly alternatives.

Recommendations:

Add equivalent examples using Azure CLI commands, which are cross-platform and work on Linux, macOS, and Windows.
Include Bash shell script examples for running pipelines, or at least mention how to accomplish the same tasks outside of PowerShell.
Reference tutorials and quickstarts that use Azure CLI or REST API, not just PowerShell.
Explicitly state that the Wait activity and pipeline operations can be managed from any OS, and provide links to relevant cross-platform documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates Windows bias primarily in the authentication section, where only a PowerShell snippet is provided for base64-encoding a PFX certificate file. There are no equivalent Linux or cross-platform command examples (e.g., using OpenSSL or base64 utilities). The documentation assumes familiarity with Windows tooling and omits Linux alternatives, which may hinder users on non-Windows platforms.

Recommendations:

Provide equivalent Linux/macOS command-line examples for base64-encoding a PFX file (e.g., using 'base64' and 'openssl').
When referencing certificate conversion or encoding, mention both Windows and Linux tools and workflows.
Wherever possible, use cross-platform language (e.g., 'your favorite utility' could be expanded to list both Windows and Linux tools).
Review other sections for implicit Windows assumptions and add Linux/macOS guidance as needed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily through its exclusive use of PowerShell-based tutorials in the 'Related content' section. No Linux or cross-platform CLI (such as Azure CLI or Bash) examples are provided, and the referenced tutorials are PowerShell-specific, which is most commonly used on Windows. There are no explicit Linux or cross-platform instructions or examples, and the documentation does not mention alternative tools or approaches for non-Windows users.

Recommendations:

Include equivalent Azure CLI and/or Bash examples alongside PowerShell instructions in both the main documentation and the related tutorials.
Reference Linux/macOS-compatible tools and workflows where appropriate, not just PowerShell.
Ensure that links in the 'Related content' section point to both PowerShell and Azure CLI (or Bash) versions of the tutorials, or provide a clear choice for users of different platforms.
Explicitly state when instructions are platform-agnostic or provide notes for platform-specific steps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias in its examples and tooling references. In the 'Manual execution with other APIs/SDKs' section, Azure PowerShell is prominently featured with a full command-line example, while there are no equivalent CLI/bash/Linux-native examples. The PowerShell example uses Windows-style paths and conventions, and the documentation does not mention or provide examples for the Azure CLI (az), which is cross-platform and commonly used on Linux/macOS. The ordering of examples also places PowerShell before Python and REST, reinforcing a Windows-first perspective.

Recommendations:

Add Azure CLI (az) examples for running pipelines, using bash syntax and Linux-style paths where appropriate.
Include explicit bash or shell script examples for REST API usage (e.g., using curl), not just the HTTP request.
Reorder the 'Manual execution with other APIs/SDKs' section to present cross-platform or Linux-friendly tools (Azure CLI, Python SDK, REST API with curl) before or alongside PowerShell.
Clarify that Azure PowerShell is available cross-platform, but also provide Linux-native command-line alternatives.
Where file paths are referenced, use both Windows and Linux path formats, or avoid OS-specific paths.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows/Powershell bias by consistently referencing and linking to Powershell-based tutorials and quickstarts (e.g., 'quickstart-create-data-factory-powershell.md', 'tutorial-transform-data-spark-powershell.md') as the default or only walkthroughs for pipeline creation and data transformation. There are no equivalent examples or walkthroughs for Linux, Bash, or cross-platform CLI tools. The documentation does not mention or provide parity for Linux users or alternative command-line environments.

Recommendations:

Provide equivalent walkthroughs and quickstarts using Azure CLI (az), Bash scripts, or REST API examples that are cross-platform and work natively on Linux/macOS.
When referencing tutorials or quickstarts, include both Powershell and non-Windows (e.g., Bash, Azure CLI) links side-by-side, or clarify that alternatives exist.
Explicitly mention that Data Factory and Synapse pipelines can be managed from Linux/macOS using cross-platform tools, and provide links to relevant documentation.
Ensure that all code snippets and automation examples are available in both Powershell and Bash/Azure CLI formats.
Review related content and ensure Linux-friendly resources are equally discoverable and not only present as an afterthought.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell-based configuration scripts and referencing Windows-centric tools and patterns. There are no equivalent examples or guidance for Linux users, such as Bash/CLI scripts or cross-platform alternatives. The exclusive use of PowerShell and lack of mention of Linux environments or tooling may hinder accessibility for users operating from non-Windows systems.

Recommendations:

Provide equivalent Azure CLI (az) or Bash script examples alongside PowerShell scripts to support Linux and macOS users.
Explicitly mention cross-platform options for configuring and managing Azure-SSIS IR, clarifying which steps are platform-agnostic.
Reference documentation or tutorials for Linux users where relevant, ensuring parity in setup and management workflows.
Avoid language that assumes the user is on Windows or using PowerShell by default; instead, present both Windows and Linux approaches equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a mild Windows bias, particularly in the section describing how to configure TLS/SSL truststores for the self-hosted integration runtime. File paths are shown in Windows (C:\MyTrustStoreFile) format, and there is no mention of Linux file paths or examples. The documentation also omits explicit Linux command-line or environment variable examples, and does not clarify how to perform equivalent steps on Linux-based self-hosted IR machines.

Recommendations:

Provide parallel Linux examples for file paths (e.g., /home/user/MyTrustStoreFile) wherever Windows paths are shown.
Explicitly mention that the self-hosted integration runtime can run on both Windows and Linux, and clarify any OS-specific requirements.
Include Linux command-line examples for openssl commands (even if the commands are the same, show Linux-style paths and shell syntax).
Document environment variable configuration (e.g., TNS_ADMIN) for both Windows and Linux, showing how to set them in each OS.
Add a note or table summarizing any differences or additional steps for Linux users, especially for truststore placement and permissions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. It references PowerShell and SSMS (SQL Server Management Studio, a Windows-only tool) for management and scripting tasks, and the 'ms.devlang' metadata is set to PowerShell. All scripting and management examples use T-SQL and SSMS, with no mention of cross-platform tools like Azure CLI, Azure Data Studio, or Linux-based workflows. There are no explicit Linux examples or guidance for non-Windows environments, and the documentation assumes the use of Windows-centric tools for orchestration and job management.

Recommendations:

Provide equivalent examples using Azure CLI for all PowerShell-based or portal-based instructions, especially for creating and managing Azure-SSIS IR and failover groups.
Mention and provide examples using Azure Data Studio (which is cross-platform) as an alternative to SSMS for T-SQL scripting and job management.
Explicitly state which steps can be performed from Linux/macOS environments and provide guidance or links for those users.
Avoid assuming the use of Windows-only tools (like SSMS) as the default; instead, present cross-platform alternatives first or alongside.
Update metadata (e.g., ms.devlang) to reflect multi-platform support if examples are added.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing only Windows versions for supported environments, linking exclusively to the Windows ODBC driver installation guide, and omitting any mention of Linux or cross-platform support. There are no Linux-specific instructions, prerequisites, or examples, and the documentation does not clarify whether Linux is supported or provide guidance for Linux users.

Recommendations:

Add explicit information about Linux support for the Amazon Redshift connector, including supported distributions and prerequisites.
Include links to the Amazon Redshift ODBC driver installation guides for Linux and macOS, not just Windows.
Provide Linux-specific instructions for installing and configuring the self-hosted integration runtime, if supported.
Clarify in the prerequisites and supported capabilities sections whether Linux-based self-hosted integration runtimes are supported, and if so, provide setup examples.
Ensure all referenced tools and workflows are described in a cross-platform manner, or provide parallel instructions for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows authentication, Windows-style usernames (domain\username), and Windows-specific tools and configuration steps (such as SQL Server Management Studio, SQL Server Configuration Manager, and Windows Firewall). Troubleshooting and setup instructions are written only for Windows environments, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for Linux users, nor any references to Linux-compatible tools or authentication methods.

Recommendations:

Include instructions and examples for connecting from Linux environments, such as using sqlcmd, Azure Data Studio, or other cross-platform tools.
Provide Linux-compatible authentication guidance (e.g., Kerberos, SQL authentication) and clarify any limitations or differences.
Add troubleshooting steps for Linux, such as configuring firewalls with iptables/firewalld, and enabling TCP/IP via configuration files or command-line tools.
Avoid assuming the use of Windows-only tools (like SQL Server Management Studio or Configuration Manager); mention cross-platform or browser-based alternatives where possible.
When showing username formats, clarify that domain\username is a Windows convention and provide Linux/Unix equivalents if applicable.
Explicitly state OS requirements or limitations for features that are only available on Windows, and suggest workarounds or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias in its treatment of Azure Files, especially in the legacy model sections. It uses Windows-specific UNC path syntax (\\<storage name>.file.core.windows.net\<file service name>) and user ID formats (AZURE\<storage name>), and refers to SMB (Server Message Block) without clarifying cross-platform usage. There are no Linux or macOS-specific examples or guidance for mounting or accessing Azure Files, nor is there mention of Linux tools or commands for interacting with Azure Files. The documentation assumes a Windows environment for certain configuration patterns and omits Linux parity in both examples and conceptual explanations.

Recommendations:

Add explicit Linux and macOS examples for mounting and accessing Azure Files, using native tools (e.g., mount.cifs, smbclient) and syntax relevant to those platforms.
When describing the legacy model, clarify how Linux users should specify paths and credentials, including the correct syntax and any differences from Windows.
Include a section or note on cross-platform compatibility, highlighting any differences or additional steps required for Linux/macOS environments.
Provide sample commands or configuration snippets for Linux (e.g., how to mount Azure Files using CIFS in Linux, with example /etc/fstab entries or mount commands).
Avoid presenting Windows-specific patterns (such as UNC paths and AZURE\<storage name> user IDs) as the only or primary method; instead, present both Windows and Linux approaches side by side.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively providing PowerShell commands for generating shared access signatures (SAS) and referencing Windows-centric tools (e.g., New-AzStorageContext). No equivalent Linux, Bash, or cross-platform CLI examples are given. The only command-line example for SAS generation is in PowerShell, with no mention of Azure CLI or REST API alternatives, which are more platform-neutral. This may hinder Linux or macOS users who do not have access to PowerShell or prefer native tools.

Recommendations:

Provide equivalent Azure CLI examples for generating SAS tokens (e.g., using 'az storage account generate-sas' or 'az storage container generate-sas').
Mention REST API options for SAS generation for maximum platform neutrality.
When presenting command-line examples, either show both PowerShell and Bash/Azure CLI, or default to Azure CLI for cross-platform compatibility.
Avoid referencing only Windows tools or patterns; ensure Linux/macOS users are equally supported in all procedural steps.
Explicitly state that all steps can be performed on any platform, and provide links or guidance for Linux/macOS users where workflows differ.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias, particularly in the staged copy section where firewall configuration examples reference only the Windows firewall and port requirements. There are no Linux-specific examples or mentions of Linux firewall tools (such as iptables, firewalld, or ufw), and no Linux command-line or shell examples are provided. The documentation assumes a Windows-centric environment for on-premises scenarios, which may leave Linux users without clear guidance.

Recommendations:

When discussing firewall configuration, include Linux firewall tools (e.g., iptables, firewalld, ufw) alongside Windows Firewall, and provide equivalent Linux command examples.
Explicitly mention that the self-hosted integration runtime can be installed on both Windows and Linux, and provide links or notes for Linux installation and configuration.
Provide example commands or configuration snippets for both Windows and Linux environments where relevant (e.g., opening ports, managing services).
Review all examples and ensure parity by including Linux-oriented content where Windows is referenced.
Add a note or section clarifying cross-platform support and any platform-specific considerations for performance optimization.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows-first and Windows-heavy bias. Windows authentication and file share patterns are mentioned and exemplified throughout, with Windows path syntax (backslashes) and Windows-specific terminology (e.g., 'Windows authentication', 'local Powershell') appearing before or instead of Linux equivalents. Linux support is only briefly mentioned (via Samba), with no Linux-specific configuration or example paths provided. All sample paths, JSON, and UI screenshots use Windows conventions, and command-line references are to Powershell, with no Linux shell or mount examples.

Recommendations:

Provide Linux-specific examples for file share setup, including sample Linux paths (e.g., /mnt/share) and Linux user authentication.
Include step-by-step instructions for configuring a Linux file share (e.g., using Samba), with sample configuration files and mount commands.
Offer equivalent Linux shell commands (e.g., using smbclient or mount.cifs) alongside Powershell references.
Use both Windows and Linux path syntax in examples and tables, or clarify when each is appropriate.
Explicitly document authentication options for Linux environments (e.g., username/password, Kerberos, etc.) and note any differences from Windows.
Add screenshots or UI walkthroughs that show Linux shares being configured, if possible.
Review terminology to ensure Linux is presented as a first-class scenario, not just an afterthought.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing Windows support and tools (such as the supported Windows versions for the integration runtime) without mentioning Linux support or providing Linux-specific instructions or examples. There are no Linux or cross-platform examples for configuring the integration runtime or specifying file paths, and the documentation implies a Windows-centric environment for setup and operation.

Recommendations:

Explicitly state whether the Self-hosted Integration Runtime and connector support Linux, and provide a link to Linux prerequisites if available.
Include Linux-specific instructions or examples for file paths (e.g., using /home/user/key.json instead of C:\path\to\key.json).
If Linux is supported, add screenshots or terminal commands for Linux environments where relevant.
Mention any differences or limitations when running on Linux versus Windows, if applicable.
Ensure parity in troubleshooting and configuration guidance for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-centric bias in several areas: authentication options and configuration steps are primarily described in terms of Windows authentication and Windows domain integration; configuration commands and tools (e.g., Ksetup, netdom) are Windows-specific and provided before or instead of Linux equivalents; and there are no explicit Linux-based integration runtime setup examples, even though HDFS and Kerberos are commonly used in Linux environments. The documentation assumes or prioritizes Windows environments for self-hosted integration runtime and Kerberos configuration, with only minimal references to Linux-native approaches.

Recommendations:

Provide parallel Linux-based examples for self-hosted integration runtime setup, including Kerberos configuration using native Linux tools (e.g., kinit, krb5.conf, systemd services).
Include Linux shell command equivalents for all Windows command-line instructions (e.g., Ksetup, netdom), or clarify if certain steps are only required on Windows.
Explicitly document how to configure the integration runtime and HDFS connector on a Linux host, including any differences in authentication, file paths, or permissions.
Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or group them under clear OS-specific headings.
Clarify which authentication types are supported on Linux, and provide guidance for common Linux-based HDFS/Kerberos deployments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Azure PowerShell, instructing users to edit the Windows hosts file, and providing no Linux or cross-platform alternatives for key steps such as integration runtime installation, VM setup, or host file modification. There are no Bash, CLI, or Linux-specific instructions or screenshots, and the workflow implicitly assumes a Windows environment throughout.

Recommendations:

Add equivalent instructions for Linux-based VMs, including how to install and configure the self-hosted integration runtime on Linux.
Provide Azure CLI and/or Bash script alternatives alongside Azure PowerShell commands for all relevant steps.
When referencing host file modifications, include Linux paths (e.g., /etc/hosts) and editing commands (e.g., using nano or vi) as alternatives to the Windows path.
Clarify that the self-hosted integration runtime can be installed on both Windows and Linux, and link to platform-specific installation guides.
Ensure screenshots and UI references are not exclusively Windows-centric, or provide Linux/terminal equivalents where appropriate.
Explicitly state cross-platform compatibility and provide troubleshooting tips for both Windows and Linux environments.

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 being supported on Windows), mentioning Windows compatibility before any Linux equivalent (with no explicit mention of Linux support), and omitting Linux-specific instructions or examples for setting up the integration runtime or connector. There are no Linux command-line or configuration examples, and the prerequisites section only links to Windows requirements.

Recommendations:

Explicitly state whether the self-hosted integration runtime and Hive connector are supported on Linux, and provide a link to Linux prerequisites if available.
Add Linux-specific setup instructions or examples for the self-hosted integration runtime and Hive connector, including any differences in configuration or file paths.
Include example commands or scripts for Linux environments (e.g., shell scripts, Linux service management) alongside or before Windows/Powershell examples.
Clarify any limitations or differences in feature support between Windows and Linux environments.
Ensure that all references to operating system requirements or compatibility are balanced and not Windows-centric.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing only Windows versions as supported for the self-hosted integration runtime, without mentioning Linux support or providing Linux-specific instructions. There are no Linux or cross-platform examples, and the prerequisites link directs users to a Windows-centric page. No Linux tools or patterns are discussed.

Recommendations:

Explicitly state whether Linux is supported for the self-hosted integration runtime, and if so, provide a link to Linux installation instructions.
Include Linux-specific examples or notes where relevant, such as for setting up the integration runtime or troubleshooting.
If Linux is not supported, clearly mention this limitation early in the documentation.
Where possible, use cross-platform language and avoid assuming a Windows-only environment.
Add a section comparing Windows and Linux support, including any feature or performance differences.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation assumes the use of Windows environments by requiring the Microsoft Access ODBC driver (which is only available on Windows), referencing file paths in Windows format (e.g., C:\mydatabase.accdb), and omitting any mention of Linux or cross-platform alternatives. There are no Linux-specific instructions, examples, or caveats, and all tooling and configuration steps are implicitly or explicitly Windows-centric.

Recommendations:

Explicitly state that the Microsoft Access ODBC driver is only available on Windows and clarify that Linux is not supported for this connector.
If possible, mention any workarounds or third-party solutions for accessing Access databases from Linux (e.g., mdbtools, unixODBC with alternative drivers), even if not officially supported.
Provide a table or section comparing platform support, so Linux users are aware of the limitations up front.
Use neutral language in file path examples or provide both Windows and Linux path formats where relevant (even if Linux is not supported, this clarifies the scope).
Add a note in the prerequisites or introduction highlighting the Windows-only nature of the required drivers and runtime environment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. While most of the content is platform-neutral (focused on Azure UI, REST, .NET, and Python SDKs), there are several areas where Windows/PowerShell tools and patterns are mentioned first or exclusively. For example, certificate conversion is linked to a PowerShell-based guide, and Azure PowerShell is listed as a primary automation tool. There are no explicit Linux CLI or Bash examples, and Linux-native tooling is not referenced.

Recommendations:

Provide Linux/Bash equivalents for certificate conversion (e.g., using openssl and base64 commands) alongside the PowerShell example.
Include Azure CLI examples and tutorials (az commands) for pipeline and resource creation, not just Azure PowerShell.
When listing tools or SDKs, present cross-platform options (e.g., Azure CLI, REST, Python SDK) before or alongside Windows-specific tools like PowerShell.
Reference Linux-compatible automation and scripting methods where possible, and clarify that all features are available cross-platform.
Add a note or section confirming that all steps can be performed from Linux/macOS environments using supported tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias. Windows authentication is listed as a primary authentication method, and the only OS-specific authentication example provided is for Windows (with domain\user syntax). There is no mention of Linux-specific authentication scenarios or examples, nor is there guidance for Linux users on how to obtain or use credentials. Additionally, the use of Windows-centric patterns (such as domain\user) and the absence of Linux command-line or tool references (e.g., curl, wget, or Linux-based token retrieval) reinforce this bias.

Recommendations:

Add explicit Linux authentication examples, such as using Kerberos or NTLM from Linux environments, or clarify cross-platform support for authentication types.
Provide equivalent Linux command-line examples for obtaining access tokens (e.g., using curl or httpie instead of only referencing Postman).
Clarify whether Windows authentication is supported from non-Windows integration runtimes, and if so, provide Linux-specific configuration guidance.
When listing authentication types, avoid putting 'Windows' before more cross-platform options, or clarify their applicability to different OSes.
Include a note or section on best practices for Linux users, especially for common scenarios like service principal authentication or API key usage.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing SQL Server Management Studio (SSMS) for running SQL scripts, without mentioning cross-platform or Linux alternatives. There are no examples or instructions for Linux or macOS users, and the only tool mentioned for database interaction is a Windows-only application. No PowerShell-specific examples are present, but the workflow assumes a Windows environment for key steps.

Recommendations:

Mention and provide instructions for cross-platform SQL tools such as Azure Data Studio, sqlcmd, or DataGrip, which are available on Linux and macOS as well as Windows.
Include example commands for running the generated SQL scripts using sqlcmd or Azure Data Studio's integrated terminal, not just SSMS.
Rephrase step 8 to say 'Open your preferred SQL client (such as SSMS, Azure Data Studio, or sqlcmd) to connect to your control table server...' instead of only referencing SSMS.
Add a note or section for Linux/macOS users, outlining supported tools and any differences in workflow.
Ensure screenshots and UI walkthroughs do not assume only Windows-based tools where possible.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias in its guidance for configuring SSL verification with the ODBC driver. It exclusively references Windows file paths (e.g., C:\Windows\ServiceProfiles...) and does not provide equivalent instructions or examples for Linux-based Self-hosted Integration Runtime (SHIR) servers. There are no Linux-specific examples or mentions of Linux file locations, and the only operating system-specific guidance is for Windows.

Recommendations:

Add equivalent instructions and file paths for configuring SSL certificates on Linux-based SHIR servers (e.g., ~/.postgresql/root.crt or /etc/ssl/certs/).
Explicitly mention that the ODBC driver and SHIR can be run on both Windows and Linux, and provide OS-agnostic or dual-platform guidance where applicable.
Include Linux-based examples or notes wherever Windows-specific paths, tools, or procedures are mentioned.
Review all examples and configuration steps to ensure Linux users are not excluded or left to infer the correct steps for their environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing 'Command Prompt' as the context for running curl, omitting Linux/macOS terminal instructions, and recommending Fiddler (a Windows-only tool) for SSL troubleshooting. No Linux-specific tools or terminal environments are mentioned, and example commands are not adapted for cross-platform usage.

Recommendations:

When suggesting command-line tools like curl, refer to 'terminal' or 'command line' generically, and provide examples for both Windows (Command Prompt/PowerShell) and Linux/macOS (bash/zsh).
Include Linux/macOS equivalents for troubleshooting tools, such as recommending Wireshark or mitmproxy alongside Fiddler.
Explicitly state that curl is available on Linux/macOS by default, and provide any necessary installation instructions for Windows users.
Ensure that all example commands are cross-platform or provide platform-specific variants where syntax differs.
Avoid referencing only Windows environments (e.g., 'Command Prompt') unless the documentation is Windows-specific.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation displays a Windows bias in its guidance for configuring SSL verification with the ODBC driver on Self-hosted Integration Runtime (SHIR). It references only Windows file paths (e.g., C:\Windows\ServiceProfiles\DIAHostService\AppData\Roaming\postgresql\root.crt) and does not mention Linux equivalents or provide Linux-specific instructions. There are no Linux or cross-platform examples for setting up ODBC DSNs or certificate locations, and the only operating system-specific details are for Windows. This may hinder users running SHIR on Linux or other non-Windows environments.

Recommendations:

Add equivalent instructions and file paths for configuring SSL certificates and DSNs on Linux-based SHIR hosts (e.g., ~/.postgresql/root.crt or /etc/ssl/certs/).
Explicitly state whether SHIR is supported on Linux, and if so, provide parity in setup steps for both Windows and Linux environments.
Where file paths or OS-specific steps are mentioned, include both Windows and Linux variants side by side.
Provide examples or references for configuring ODBC DSNs and certificates on Linux, not just Windows.
Review the documentation for other implicit Windows assumptions and ensure cross-platform applicability is clear.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page provides only a Windows PowerShell example for creating an Azure Integration Runtime via command line, with no equivalent example for Linux users (e.g., Azure CLI or Bash). The use of the Set-AzDataFactoryV2IntegrationRuntime PowerShell cmdlet and lack of mention of cross-platform tools or scripts indicates a Windows-centric approach. No Linux or macOS command-line alternatives are provided.

Recommendations:

Add equivalent Azure CLI examples for creating and configuring Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that PowerShell examples are for Windows and provide Bash or shell script alternatives where possible.
Include a section or note on how to perform the same actions on Linux/macOS environments, referencing Azure CLI or REST API.
Ensure parity in documentation by presenting cross-platform command-line options before or alongside Windows-specific tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation requires Azure PowerShell for setup and references only PowerShell installation instructions, with no mention of Linux/Unix alternatives (such as Azure CLI or Bash). There are no examples or instructions for Linux/macOS users for uploading files or managing resources, and the only prerequisite for automation is Azure PowerShell. This creates a bias toward Windows users and omits parity for Linux environments.

Recommendations:

Provide equivalent instructions using Azure CLI (az) for all steps currently described with Azure PowerShell, including installation and usage.
Include Bash or cross-platform shell examples for uploading files to Azure Blob Storage (e.g., using az storage blob upload or Azure Storage Explorer).
Explicitly mention that all steps can be performed from Linux/macOS as well as Windows, and provide links to relevant cross-platform tools.
In the prerequisites, list both Azure PowerShell and Azure CLI as options, with links to their respective installation guides.
Where automation or scripting is referenced, offer both PowerShell and Bash/CLI script snippets.

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, with no mention of Linux-compatible alternatives or cross-platform tooling. There are no examples or guidance for Linux users, and the documentation assumes the use of Windows environments and tools throughout.

Recommendations:

Explicitly state the platform requirements and whether deployment and management of SSIS packages is supported from Linux or macOS environments.
If possible, provide guidance or alternatives for Linux users, such as using Azure Data Factory web UI, REST APIs, or cross-platform command-line tools.
Include examples or documentation links for deploying SSIS packages from non-Windows environments, or clarify if such scenarios are not supported.
Avoid assuming the use of Windows tools by default; mention cross-platform options first if available, or clearly indicate when only Windows tools are supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exhibits mild Windows bias, primarily in its recommendations and tooling references. In the 'TIP' section about testing REST APIs, only Windows-centric tools (Visual Studio, PowerShell's Invoke-RestMethod, web browser) are mentioned, with PowerShell called out explicitly. Additionally, when describing how to convert a certificate to base64, the only linked guide uses PowerShell, a Windows-first tool. There is no mention of Linux-native tools or cross-platform alternatives for these common tasks, and Windows tools are listed first and exclusively.

Recommendations:

When suggesting tools for testing REST APIs, include cross-platform and Linux-native options such as curl, httpie, or Postman, alongside PowerShell and Visual Studio.
When referencing certificate conversion, provide Linux/Unix command-line alternatives (e.g., openssl) and link to relevant documentation or examples.
Avoid listing Windows tools first or exclusively; present cross-platform or platform-neutral options where possible.
Explicitly state that all examples and tooling recommendations are applicable to both Windows and Linux, or provide platform-specific instructions as needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing 'SAP HANA CLIENT for Windows' as the ODBC driver to install, without mentioning Linux or cross-platform alternatives. No Linux installation instructions or examples are provided for the ODBC driver or integration runtime setup. The authentication examples and terminology (e.g., 'Windows authentication') are Windows-centric, and there is no guidance for Linux environments.

Recommendations:

Explicitly mention and provide instructions for installing the SAP HANA ODBC driver on Linux (and macOS, if supported), including links to relevant SAP documentation.
Clarify that the Self-hosted Integration Runtime can be installed on both Windows and Linux, and provide platform-specific setup instructions or references.
Include Linux-based examples for connection strings and authentication, noting any differences (e.g., Kerberos or other authentication mechanisms on Linux).
Avoid using 'Windows authentication' as the only named authentication method; instead, describe all supported authentication types and their applicability to different operating systems.
Where screenshots or UI steps are shown, note any differences for Linux users if applicable, or clarify if the experience is the same across platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only a PowerShell (Windows-specific) command (Test-NetConnection) for troubleshooting connectivity to the SAP server, without offering equivalent Linux/macOS commands or guidance. This prioritizes Windows tools and patterns, and omits Linux alternatives, making the instructions less accessible for users running integration runtime on Linux or macOS.

Recommendations:

Include equivalent Linux/macOS troubleshooting commands, such as using 'nc', 'telnet', or 'curl' to test port connectivity.
Present both Windows and Linux/macOS examples side by side, or at least mention alternatives for non-Windows users.
Avoid assuming the integration runtime is always installed on a Windows machine; clarify platform support and provide guidance accordingly.
Consider a table or section that lists commands for multiple operating systems to improve parity and inclusivity.

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 guidance assumes the user is on Windows, with no mention of alternatives for Linux or macOS users.

Recommendations:

Provide equivalent troubleshooting steps using cross-platform tools such as Azure CLI, Microsoft Graph API, or PowerShell Core (pwsh) where possible.
Explicitly state platform requirements for the SharePoint Online Management Shell and offer alternatives or workarounds for Linux/macOS users.
Include Linux/macOS command-line examples or scripts, or reference official Microsoft documentation for performing these tasks on non-Windows platforms.
Consider restructuring the troubleshooting steps to present cross-platform solutions first, or at least alongside Windows-specific instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a Windows bias by explicitly stating support for Windows versions of the self-hosted integration runtime and linking only to Windows prerequisites. There are no mentions of Linux support, nor are there any Linux-specific instructions or examples. The documentation does not clarify whether Linux is unsupported or simply omitted, and no Linux tools or command-line examples are provided.

Recommendations:

Clarify whether the self-hosted integration runtime supports Linux, and if so, provide explicit instructions and prerequisites for Linux environments.
If Linux is not supported, state this clearly to avoid ambiguity.
Include Linux-specific examples or references where relevant, such as installation steps, configuration, or troubleshooting.
Ensure parity in documentation structure and examples for both Windows and Linux users, including screenshots or command-line snippets as appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-centric tools (SSDT, SSMS, dtutil), providing PowerShell as the only command-line automation example, and omitting Linux-native tooling or instructions. There are no examples or guidance for Linux users, and the documentation assumes familiarity with Windows-based administrative patterns.

Recommendations:

Include equivalent instructions and examples for Linux users, such as using Azure CLI for provisioning and configuration tasks instead of only PowerShell.
Mention cross-platform tools (e.g., Azure Data Studio) alongside or before Windows-only tools like SSMS and SSDT.
Provide command-line examples using Bash or Azure CLI where PowerShell is referenced.
Clarify which tools are cross-platform and which are Windows-only, and suggest alternatives for non-Windows environments.
Add a section or notes specifically addressing Linux/macOS users, outlining supported workflows and toolchains.

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 for advanced configuration (e.g., backup storage redundancy), mentioning Windows-specific tools (e.g., SSMS, UNC paths), and omitting Linux-specific examples or guidance. There are no Linux command-line examples, and file system integration assumes Windows-style paths and authentication. The documentation does not address Linux users' needs or provide parity in instructions for non-Windows environments.

Recommendations:

Provide equivalent CLI examples using Azure CLI and Bash scripts for all PowerShell instructions, especially for tasks like configuring backup storage redundancy.
Clarify how Linux users can interact with Azure Files and file system package stores, including mounting instructions and authentication methods suitable for Linux.
Mention cross-platform tools (e.g., Azure Data Studio) alongside SSMS for managing SSIS packages.
Include examples of file paths and access patterns for both Windows (UNC paths) and Linux (NFS/Samba mounts or Azure Files via SMB/NFS).
Explicitly state any platform limitations or differences in experience between Windows and Linux users.
Ensure all referenced tools and workflows are accessible or have documented alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing 'Windows authentication' as a primary authentication method, omitting mention of Linux authentication patterns. It also assumes the installation of Sybase providers on the Integration Runtime without clarifying Linux support or providing Linux-specific instructions. There are no examples or guidance for Linux environments, and Windows terminology appears before or instead of cross-platform alternatives.

Recommendations:

Explicitly state whether the Sybase connector and required providers are supported on Linux-based Self-hosted Integration Runtime, and provide installation instructions for Linux if supported.
Include Linux authentication options or clarify the authentication mechanisms available on Linux hosts.
Provide examples and troubleshooting tips for both Windows and Linux environments, including any differences in setup or configuration.
Avoid listing 'Windows authentication' before or instead of cross-platform authentication methods unless it is the only supported option, and clarify platform-specific limitations.
If Linux is not supported, clearly state this in the prerequisites section to avoid confusion.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing PowerShell for configuring the self-hosted integration runtime (SHIR) and omitting any mention of Linux command-line tools or configuration methods. There are no Linux or cross-platform examples provided, and the only setup instructions link to a PowerShell-based workflow.

Recommendations:

Include equivalent Linux command-line instructions (e.g., Bash scripts or CLI commands) for configuring SHIR file system access.
Mention cross-platform tools or provide guidance for both Windows and Linux environments.
Explicitly state platform requirements or limitations if certain features are only available on Windows.
Add examples or links for Linux users to ensure parity and inclusivity in troubleshooting steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias in several areas: Windows authentication is consistently listed before other authentication types, and Windows-specific dependencies (such as Visual C++ Redistributable) are referenced without Linux equivalents or guidance. There are no examples or instructions for Linux environments, such as installing the Teradata .NET Data Provider or drivers on Linux-based self-hosted integration runtimes. All examples and troubleshooting steps implicitly assume a Windows environment.

Recommendations:

Add explicit guidance and examples for Linux-based self-hosted integration runtimes, including how to install required Teradata drivers and dependencies on Linux.
When listing authentication types or configuration options, avoid putting 'Windows' first unless it is the most common or only supported option; otherwise, use a neutral or alphabetical order.
For prerequisites, provide Linux equivalents or alternatives to Windows-only dependencies (e.g., Visual C++ Redistributable), or clarify if the connector is only supported on Windows-based runtimes.
Include troubleshooting tips and environment setup steps for both Windows and Linux platforms.
Clearly state platform support limitations (if any) early in the documentation, so Linux users can quickly determine applicability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows environments. All installation instructions, prerequisites, and examples assume or require Windows OS. Only Windows versions are listed as supported, and all command-line automation is shown using PowerShell or Windows batch tools. There are no instructions or examples for Linux or macOS, nor any mention of cross-platform support. Windows-specific tools (e.g., registry editing, Windows DPAPI, Notepad, Windows Firewall, NT SERVICE accounts) are referenced throughout, and Linux equivalents are not discussed.

Recommendations:

Clearly state early in the document whether Linux or macOS are supported or not. If not, make this explicit in the prerequisites.
If Linux is supported, add a dedicated section for Linux installation, including supported distributions, dependencies (e.g., .NET Core/Mono), and step-by-step instructions.
Provide Linux/macOS equivalents for all PowerShell and Windows command-line examples (e.g., Bash scripts, CLI commands).
Reference Linux-native tools and configuration files (e.g., systemd for services, iptables/firewalld for firewall, environment variables for JAVA_HOME).
If Windows-only features (such as DPAPI or registry edits) are required, explain the Linux/macOS alternatives or limitations.
For proxy and firewall configuration, include Linux-specific instructions (e.g., editing /etc/hosts, /etc/environment, or using ufw/firewalld).
Mention any differences in credential storage, service accounts, or permissions models between Windows and Linux.
If the product is Windows-only, consider renaming the article or adding a prominent note to clarify this, and avoid implying cross-platform support.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively provides PowerShell-based deployment and management commands for Azure-SSIS IR, with no mention of cross-platform tools or Linux/macOS-compatible alternatives. All automation and CLI examples are Windows-centric, and there is no guidance for users on Linux or macOS platforms.

Recommendations:

Add Azure CLI examples for deploying and managing Azure-SSIS IR, as Azure CLI is cross-platform and works on Windows, Linux, and macOS.
Mention and demonstrate how to use the Azure Portal for template deployment, which is platform-agnostic.
Explicitly state the platform requirements for PowerShell commands, and provide links or instructions for using PowerShell Core on non-Windows systems if PowerShell must be used.
Reorder or supplement examples so that cross-platform methods (e.g., Azure CLI, Portal) are presented before or alongside Windows-specific tools.
Include a note or section addressing Linux/macOS users, outlining their options for performing the same tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows authentication, tools, and patterns. Windows authentication is described in detail, with examples and explicit mention of domain\username formats. Troubleshooting steps and configuration instructions exclusively reference Windows tools such as SQL Server Management Studio, SQL Server Configuration Manager, and Windows Firewall, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for connecting to SQL Server from Linux environments or using Linux-based authentication methods.

Recommendations:

Add equivalent instructions and examples for Linux environments, such as using sqlcmd, Azure Data Studio, or ODBC/JDBC clients on Linux.
Include troubleshooting steps for configuring SQL Server connectivity on Linux, such as firewall configuration using iptables/firewalld and enabling TCP/IP in Linux-based SQL Server installations.
Provide authentication examples relevant to Linux, such as SQL authentication, Kerberos, or Azure Active Directory authentication, and clarify any limitations or differences.
Avoid assuming Windows as the default environment; present cross-platform guidance or clearly indicate when steps are Windows-specific.
Reference or link to official Microsoft documentation for SQL Server on Linux where appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates Windows bias by referencing Windows-specific tools (diawp.exe.config) and configuration steps (disabling FIPS mode on Windows VMs) without mentioning Linux equivalents or providing guidance for non-Windows environments. There are no troubleshooting steps or examples for Linux-based self-hosted integration runtimes, and the only OS-specific advice is for Windows.

Recommendations:

Include troubleshooting steps for Linux-based self-hosted integration runtimes, such as how to handle FIPS or MD5 issues on Linux.
When referencing configuration files or tools (e.g., diawp.exe.config), specify if these are Windows-only and provide Linux equivalents or note if not applicable.
Add examples or notes for both Windows and Linux environments where OS-specific troubleshooting may differ.
Avoid assuming the user is on Windows; use neutral language or provide parity in instructions for all supported platforms.

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. All command-line examples are provided exclusively using Azure PowerShell, with explicit instructions to use Windows PowerShell ISE and references to installing Azure PowerShell on Windows. There are no examples or guidance for performing these tasks using cross-platform tools such as Azure CLI, Bash, or on Linux/macOS environments. The installer instructions for the self-hosted integration runtime do not clarify Linux support or alternatives.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works on Windows, Linux, and macOS.
Avoid referencing Windows-specific tools such as 'Windows PowerShell ISE' unless absolutely necessary; instead, use generic terms like 'terminal' or 'command line interface'.
Clarify whether the self-hosted integration runtime installer is available for Linux/macOS, and if not, explicitly state the platform requirements.
Include instructions or notes for users on Linux/macOS, even if only to clarify limitations or alternative approaches.
Reorganize sections so that cross-platform solutions (e.g., Azure CLI) are presented before or alongside Windows/PowerShell-specific instructions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation shows a mild Windows bias. It references Windows-specific tools (WinSCP) for SFTP troubleshooting and recommends a third-party web tool for base64 encoding, but does not mention Linux-native alternatives. In the code examples for base64 encoding, both C# and Python are provided, but the Python example uses a Windows-style file path. The only explicit command-line example for checking SFTP host key fingerprints is given for Linux, but there are no corresponding Windows/PuTTY examples. There is a lack of parity in tool recommendations and examples for Linux users.

Recommendations:

When recommending tools for verifying SFTP connections, mention both Windows (e.g., WinSCP) and Linux (e.g., OpenSSH sftp, FileZilla) options.
For base64 encoding, provide Linux-native command-line examples (e.g., 'base64' command) alongside Python and C#.
In file path examples, use platform-neutral notation or provide both Windows and Linux path examples.
When referencing third-party tools, suggest both web-based and command-line alternatives for different platforms.
For SFTP host key fingerprint checking, include Windows/PuTTYgen instructions as well as the Linux ssh-keygen example.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exhibits a moderate Windows bias. Several troubleshooting steps and code examples reference Windows-specific tools (such as PowerShell and Fiddler) without providing Linux or cross-platform alternatives. For example, the Azure Batch troubleshooting section provides only PowerShell-based unzip commands, and the use of Fiddler is described in detail without mentioning Linux-compatible network tools. There are also references to Windows behaviors (e.g., Windows zip compression defaults) without equivalent Linux context. No Linux shell or tool examples are provided alongside the Windows ones.

Recommendations:

For every PowerShell example, provide an equivalent Bash or Linux shell command (e.g., using unzip or tar for extracting files).
When recommending tools like Fiddler for network troubleshooting, mention and provide instructions for Linux alternatives such as tcpdump, Wireshark, or curl.
Where Windows-specific behaviors are discussed (e.g., zip compression algorithms), clarify how the same scenario would appear or be handled on Linux systems.
Ensure that any references to file paths, command syntax, or troubleshooting steps are cross-platform or include both Windows and Linux variants.
Review all troubleshooting steps and add Linux/macOS guidance where currently only Windows is mentioned.

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-specific file paths (e.g., C:\Program Files\...) and configuration steps are provided. There are no equivalent instructions or examples for Linux-based environments, nor is there any mention of Linux-specific troubleshooting steps for self-hosted integration runtime scenarios. This may leave Linux users without clear guidance.

Recommendations:

Provide equivalent troubleshooting steps and file paths for Linux-based self-hosted integration runtime installations, if supported.
Explicitly mention whether the FIPS workaround and configuration applies only to Windows or also to Linux, and offer Linux-specific instructions if applicable.
Wherever file paths or commands are shown, include both Windows and Linux variants (e.g., C:\Program Files\... and /opt/... or /usr/local/...).
Audit other troubleshooting steps to ensure parity for Linux environments, including references to environment variables, service restarts, and configuration file locations.
Add a note clarifying platform support for self-hosted integration runtime and connector troubleshooting, and link to platform-specific documentation where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides troubleshooting steps that reference Windows-specific paths (e.g., C:\Program Files\MIT\Kerberos\bin) and environment variable configuration, without mentioning Linux equivalents. There are no Linux or cross-platform examples for Kerberos configuration or file locations, and the instructions assume a Windows environment.

Recommendations:

Include Linux-specific instructions for Kerberos configuration, such as referencing /etc/krb5.conf and relevant environment variables.
Provide parallel examples for both Windows and Linux file paths and system variable settings.
Explicitly state when steps are platform-specific, and offer alternatives for other operating systems.
Consider using cross-platform language and tools where possible, or link to platform-specific documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in its troubleshooting instructions. For network troubleshooting, only Windows Command Prompt and the nslookup command are mentioned, with screenshots and instructions tailored to Windows users. There are no examples or guidance for performing equivalent steps on Linux or macOS systems. Additionally, browser troubleshooting steps are presented for Edge and Chrome, which are available cross-platform, but the instructions and screenshots are Windows-centric.

Recommendations:

Include equivalent troubleshooting steps for Linux and macOS users, such as using the terminal and the dig or nslookup commands.
Provide example commands and expected outputs for Linux/macOS terminals alongside Windows Command Prompt instructions.
Add notes or screenshots for browser settings on Linux/macOS versions of Chrome and Edge, or clarify any differences.
Where referencing tools like Command Prompt, mention cross-platform alternatives (e.g., Terminal on macOS/Linux) and provide parallel instructions.
Explicitly state that the troubleshooting steps apply to all platforms, or call out any platform-specific differences.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. References to 'SQL Tools' and 'SQL Server Management Studio (SSMS)' are made without mentioning cross-platform or Linux alternatives. The only explicit firewall configuration link is for Windows Firewall. No Linux-specific tools, commands, or troubleshooting steps are provided, and there are no PowerShell examples, but the absence of Linux/Unix command-line or tool references is notable.

Recommendations:

When referencing 'SQL Tools' or 'SQL Server Management Studio (SSMS)', also mention cross-platform alternatives such as Azure Data Studio, sqlcmd, or other Linux-compatible tools.
For firewall configuration, provide links or instructions for both Windows Firewall and Linux-based firewalls (e.g., UFW, firewalld, iptables).
Include Linux command-line examples or troubleshooting steps where relevant, especially for connectivity and firewall issues.
Explicitly state that the troubleshooting steps apply to both Windows and Linux environments, or provide environment-specific notes where behavior may differ.
Where possible, use neutral terminology (e.g., 'database client tool') and provide examples for both major platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only a PowerShell script example for programmatically finding impacted objects, with no mention of Linux-compatible alternatives (such as Bash, Azure CLI, or Python). This assumes a Windows environment and omits guidance for users on Linux or macOS platforms.

Recommendations:

Provide equivalent examples using Azure CLI and/or Bash scripts for Linux/macOS users.
Mention cross-platform scripting options (e.g., Python SDK, REST API) and link to relevant documentation.
Clarify whether the provided PowerShell script can run on PowerShell Core (pwsh) on Linux/macOS, and provide installation guidance if so.
Ensure that future documentation includes both Windows and Linux/macOS approaches for programmatic tasks.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing detailed PowerShell examples for generating and retrieving managed identities, referencing the Azure portal (which is often more familiar to Windows users), and omitting equivalent CLI (az CLI), Bash, or Linux-native examples. PowerShell is presented as the primary or only scripting interface, and there are no Linux/Unix shell or cross-platform command-line examples. This may disadvantage users working on Linux or macOS environments.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
Explicitly mention that PowerShell commands can be run on any platform with PowerShell Core, or provide Bash alternatives where possible.
When listing methods (e.g., 'using PowerShell, REST API, SDK'), include Azure CLI as a first-class option.
For retrieving managed identities, provide az CLI commands (e.g., az datafactory show ...) alongside PowerShell.
Balance the order of presentation so that Windows-specific tools (PowerShell) are not always listed before cross-platform tools (CLI, REST, SDK).
Include notes or links for users on Linux/macOS about how to accomplish the same tasks in their environments.

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/SMB/Robocopy instructions and examples first and in greater detail, while Linux instructions are minimal and lack parity in depth and tooling. Windows-specific tools (Robocopy, net use, File Explorer) are emphasized, with only brief Linux mounting instructions and no Linux-native copy tool examples. There are no Linux equivalents for advanced copy scenarios, performance tuning, or error handling, and Robocopy is presented as the primary (and only detailed) copy tool.

Recommendations:

Provide Linux-native copy tool examples (e.g., rsync, cp, smbclient) for copying data after mounting the SMB share, including command-line syntax and sample output.
Include Linux-specific performance tuning guidance (e.g., parallel rsync, mount options for performance, etc.) similar to the Robocopy session/thread recommendations for Windows.
Offer parity in troubleshooting/error handling instructions for Linux users, such as how to interpret mount errors, log file locations, and common issues.
Present Windows and Linux instructions in parallel sections or tables, rather than always listing Windows first and in more detail.
Reference Linux documentation for SMB/CIFS (e.g., man mount.cifs, man smbclient) and provide links to relevant resources.
If Robocopy is recommended for Windows, suggest and document equivalent robust tools for Linux (e.g., rsync with appropriate flags for preserving metadata, parallelization, logging, etc.).

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 the primary or sole automation method for working with Data Flow Script outside the UI. There are no examples or mentions of Linux or cross-platform alternatives (such as Bash, CLI, or REST API usage from non-Windows environments). The documentation assumes the user is familiar with PowerShell and Windows tooling, and does not provide parity for Linux users.

Recommendations:

Include equivalent examples using Azure CLI and/or Bash scripts for generating and submitting Data Flow Scripts, alongside the PowerShell example.
Explicitly mention that the Data Flow Script can be used with REST APIs, and provide a sample using curl or similar Linux-native tools.
Rephrase sections that mention PowerShell as the default or only automation method to clarify that cross-platform options exist.
Add a 'Platform compatibility' note early in the document, highlighting that all features are available on both Windows and Linux, and link to relevant cross-platform tooling.
Where automation is discussed, present Windows and Linux options side-by-side or in parallel sections, rather than Windows-first or Windows-only.

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 command-line instructions are provided exclusively using Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform alternatives. The prerequisite section specifically requires Azure PowerShell, and all deployment and monitoring steps are shown only with PowerShell scripts. There are no examples or guidance for Linux or macOS users, nor is there mention of how to perform these tasks using non-Windows tools.

Recommendations:

Add equivalent instructions using Azure CLI, which is cross-platform and works natively on Linux, macOS, and Windows.
Provide Bash shell script examples for Linux/macOS users alongside PowerShell examples.
In the prerequisites, mention both Azure PowerShell and Azure CLI as supported options, with links to installation guides for each.
Clearly indicate in each step whether the instructions are for Windows/PowerShell or for Linux/Bash, and provide both where possible.
Consider including a table or section comparing the commands in PowerShell and Bash/Azure CLI to help users choose the best fit for their environment.
Review the use of terms like 'launch PowerShell' and replace with more inclusive language such as 'open your 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-centric development tools (Visual Studio, Visual Studio Code) and workflows, referencing Windows-specific patterns (such as NuGet package manager in Visual Studio), and omitting explicit Linux or cross-platform alternatives for key steps. While the Azure CLI is cross-platform, the instructions and examples assume familiarity with Windows tooling and do not provide parity for Linux users in terms of editor, package management, or shell-specific guidance.

Recommendations:

Explicitly mention and provide examples for Linux development environments, such as using VS Code on Linux, JetBrains Rider, or command-line editors (vim, nano).
Include instructions for installing .NET SDK and required packages using Linux package managers (apt, yum, etc.) and dotnet CLI.
When referencing Visual Studio or Visual Studio Code, clarify that both are available cross-platform and provide links to Linux installation guides.
For shell commands, provide notes or examples for escaping special characters in both Bash and PowerShell, and clarify any differences.
Highlight any platform-specific prerequisites or troubleshooting steps for Linux (e.g., permissions, environment variables).
Ensure that all steps (such as running the device simulator or publishing the function) are validated and documented for Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a Windows bias by repeatedly specifying or implying the use of Windows machines for installing the Data Factory self-hosted integration runtime, without mentioning Linux as an alternative. All architecture diagrams and implementation instructions refer to Windows VMs, and the pricing section explicitly excludes only 'Azure Windows VM' costs, reinforcing the perception that Windows is the default or only supported platform. There are no examples or guidance for Linux-based hosts, nor any mention of Linux-specific considerations or parity.

Recommendations:

Explicitly state that the Data Factory self-hosted integration runtime can be installed on both Windows and Linux, if supported.
Provide parallel instructions and architecture diagrams for deploying the integration runtime on Linux machines (both on-premises and in Azure).
Include Linux-specific best practices, such as recommended VM sizes, scaling guidance, and monitoring tools.
Update authentication and credential management sections to mention any Linux-specific configuration steps or Kerberos integration nuances.
In pricing and implementation examples, include Linux VM cost estimates and performance considerations.
Wherever a Windows VM is referenced, add 'or Linux VM' to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias by referencing Windows-specific tools (e.g., Windows Installer/MSI) for security integration and not mentioning Linux equivalents or alternatives. There are no command-line examples, but the only authentication mechanism mentioned is Windows-centric. Linux tools, patterns, or authentication methods are not discussed, and there is no guidance for Linux users regarding self-hosted integration runtime or credential management.

Recommendations:

Include Linux-friendly authentication and integration options, such as service principals, managed identities, or instructions for installing the self-hosted integration runtime on Linux.
Mention cross-platform alternatives to Windows Installer (MSI), such as tarball or shell script installation methods for self-hosted IR.
Provide parity in documentation by explicitly stating how Linux users can achieve secure service-to-service integration and credential management.
If examples or step-by-step guides are added, ensure both Windows and Linux command-line instructions are included.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation consistently refers to installing the Azure Data Factory self-hosted integration runtime (IR) on Windows machines or VMs, both on-premises and in Azure. There is no mention of Linux support or examples, nor are Linux tools or patterns discussed. Windows is presented as the default and only supported platform for the self-hosted IR, and all scaling and configuration guidance is Windows-specific.

Recommendations:

Explicitly state platform support for the self-hosted integration runtime, including whether Linux is supported or not. If not, clarify this early in the documentation.
If Linux is supported, provide equivalent instructions, examples, and best practices for installing and configuring the self-hosted IR on Linux systems.
Include Linux-specific considerations for scaling, monitoring, and troubleshooting the self-hosted IR.
If only Windows is supported, suggest possible workarounds for Linux environments (e.g., using Windows containers or VMs) and explain the rationale.
Ensure that any references to 'machines' or 'VMs' clarify the required operating system, and avoid assuming Windows by default.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows VMs for self-hosted Integration Runtime (IR) installation and configuration. There are no examples or guidance for deploying self-hosted IR on Linux, nor is there mention of Linux compatibility or alternatives. The only recommended pattern for private network scenarios is to use a Windows VM, and all scaling and monitoring advice is Windows-specific.

Recommendations:

Explicitly state whether self-hosted Integration Runtime is supported on Linux, and if so, provide equivalent instructions for deploying and managing IR on Linux VMs.
Include Linux-based examples and configuration guidance alongside Windows instructions, especially for scenarios involving self-hosted IR.
If Linux is not supported, clarify this limitation early in the documentation to set expectations for cross-platform users.
When recommending VM sizes or monitoring strategies, provide guidance for both Windows and Linux environments where applicable.
Review all references to 'Windows VM' and consider using neutral language such as 'VM' or 'host machine', specifying OS-specific steps only when necessary.

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: it provides only PowerShell cmdlet examples for credential management, references Windows-specific tools and APIs (such as DPAPI and Windows Firewall), and omits equivalent Linux tools or instructions. The documentation assumes a Windows environment for self-hosted integration runtime, credential encryption, and firewall configuration, without mentioning or providing guidance for Linux-based deployments.

Recommendations:

Provide equivalent Linux command-line examples (e.g., Bash scripts, az CLI) alongside PowerShell cmdlets for credential management and integration runtime setup.
Document how credential encryption and storage are handled on Linux hosts, including which APIs or mechanisms are used instead of Windows DPAPI.
Include instructions for configuring firewalls on Linux (e.g., iptables, firewalld, ufw) in addition to Windows Firewall.
Clarify whether the self-hosted integration runtime is supported on Linux, and if so, provide Linux-specific installation, configuration, and security guidance.
Ensure that all references to tools, ports, and configuration steps are cross-platform or have platform-specific sections, so Linux users are not left without guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses PowerShell cmdlets (New-AzDataFactoryV2LinkedServiceEncryptedCredential, Set-AzDataFactoryV2LinkedService), which are primarily Windows-centric and require PowerShell 7.0 or higher. There are no examples or instructions for performing the same tasks on Linux or macOS, nor are cross-platform alternatives (such as Azure CLI, REST API, or Bash scripts) mentioned. The use of DPAPI for encryption is also a Windows-specific technology.

Recommendations:

Provide equivalent examples using Azure CLI or REST API, which are cross-platform and can be run on Linux and macOS.
Clarify whether the encryption process and cmdlets are supported on non-Windows platforms, especially since PowerShell 7 is cross-platform but DPAPI is not.
If the process is inherently Windows-only (due to DPAPI or integration runtime limitations), explicitly state this limitation early in the documentation.
Offer guidance or workarounds for Linux users, such as running the commands in a Windows container or VM, or alternative credential management approaches.
Reorder or supplement examples so that Linux/macOS approaches are presented alongside or before Windows-specific instructions where possible.

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 command-line instructions are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux equivalents. Windows-specific tools and file paths (such as editing the hosts file at C:\Windows\System32\drivers\etc) are referenced without Linux alternatives. The workflow assumes the user is operating from a Windows environment, and there are no examples or guidance for users on Linux or macOS.

Recommendations:

Provide equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
Include instructions for editing the hosts file on Linux (typically /etc/hosts) alongside the Windows path.
Mention that the self-hosted integration runtime can be installed on Linux (if supported), or clarify platform limitations.
Add notes or examples for users working from Linux or macOS, especially for file operations, command-line usage, and environment setup.
Where screenshots or UI steps are shown, clarify if they are Windows-specific and provide Linux/macOS alternatives if available.
Consider reordering sections or providing parallel instructions so that Linux/macOS users do not feel like an afterthought.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exhibits a strong Windows bias. All command-line examples use PowerShell, and there are no CLI or Bash equivalents provided. The required tooling for several steps (Microsoft Entra PowerShell, Azure PowerShell, SQL Server Management Studio) are Windows-centric, with no mention of cross-platform alternatives. Instructions for connecting to Azure SQL resources are given exclusively with SSMS, which is only available on Windows. No Linux or macOS workflows are described or referenced.

Recommendations:

Provide Azure CLI and/or Bash script equivalents for all PowerShell commands, especially for group and identity management.
Mention and demonstrate the use of cross-platform tools such as Azure Data Studio for SQL tasks, or provide T-SQL scripts that can be run from any SQL client.
Explicitly state which steps require Windows-only tools and offer alternatives or workarounds for Linux/macOS users.
Reorder or parallelize examples so that cross-platform methods are presented alongside Windows-specific ones, rather than only after or not at all.
Add a section or notes on how to perform each step from Linux/macOS environments, including installation and authentication steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a clear Windows bias. Windows instructions and screenshots are presented first and in greater detail, including explicit command-line and GUI (File Explorer) steps. The Linux section is brief, provides only a single mount command (which appears to use NFS syntax rather than SMB), and lacks further guidance or troubleshooting. The only file copy tool mentioned is Robocopy, a Windows utility, with no Linux alternatives or examples provided.

Recommendations:

Present Windows and Linux instructions in parallel sections, or alternate which OS is presented first.
Provide accurate Linux SMB mount commands (e.g., using 'mount -t cifs' instead of NFS).
Include Linux file copy tool examples (e.g., cp, rsync, smbclient) alongside Robocopy.
Add Linux screenshots or terminal output where Windows screenshots are shown.
Reference Linux troubleshooting steps and permissions considerations for SMB mounts.
List both Windows and Linux tools/resources in the 'For more information' section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in the section on configuring Java for Self-hosted Integration Runtime. It describes the Java runtime discovery process as checking the Windows registry first, provides download links to Windows-specific JDK installers, and gives environment variable examples using Windows paths (e.g., C:\Program Files\Java\jdk-23). There are no explicit Linux or macOS instructions, examples, or path conventions, and no mention of Linux-specific installation or troubleshooting steps.

Recommendations:

Add explicit instructions for installing and configuring JRE/JDK/OpenJDK on Linux (and optionally macOS), including package manager commands (e.g., apt, yum) and typical installation paths (e.g., /usr/lib/jvm/java-23-openjdk).
Clarify how the Self-hosted IR locates Java on Linux (e.g., does it use JAVA_HOME, PATH, or other mechanisms?).
Provide Linux-specific examples for setting environment variables (e.g., export JAVA_HOME=/usr/lib/jvm/java-23-openjdk, export _JAVA_OPTIONS="-Xms256m -Xmx16g").
Include troubleshooting tips for common Linux issues (e.g., permissions, library paths, service restarts).
When mentioning download links, provide cross-platform options or clarify which links are for Windows and which are for Linux/macOS.
Use neutral language and path examples (or provide both Windows and Linux/macOS variants) when describing configuration steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows-based tools (such as SQL Server Management Studio and Azure PowerShell), providing step-by-step instructions for SSMS (a Windows-only application), and omitting any guidance or examples for Linux or cross-platform alternatives. There are no examples using Azure CLI, cross-platform SQL clients, or Linux-native automation tools. The documentation assumes the user is operating in a Windows environment.

Recommendations:

Include instructions for connecting to SSISDB and configuring properties using cross-platform tools such as Azure Data Studio, Azure CLI, or sqlcmd, which are available on Linux and macOS.
Provide examples of automating SSISDB log cleanup using bash scripts, Azure CLI, or Python, in addition to PowerShell.
Mention and demonstrate how to perform relevant tasks using Azure Portal UI, which is OS-agnostic.
Explicitly state that SSMS is Windows-only and suggest cross-platform alternatives for users on Linux or macOS.
Ensure that all automation and scripting examples are provided in both PowerShell and bash/Azure CLI where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments. All examples, tools, and scripts assume a Windows OS context (e.g., .cmd, .bat, .exe, .msi, PowerShell). Windows-specific commands (cmdkey, set, msiexec, odbcconf) and tools (Azure PowerShell, Azure Storage Explorer) are used exclusively. There are no Linux or cross-platform examples, and Linux equivalents are not mentioned. The documentation presumes the reader is operating in a Windows environment, with no guidance for Linux users.

Recommendations:

Clearly state early in the documentation that Azure-SSIS IR is Windows-based, if that is a technical limitation. If not, provide Linux support or clarify cross-platform capabilities.
If Linux customization is possible, add equivalent Linux/bash examples and instructions (e.g., shell scripts, Linux tools, az CLI usage).
Where Windows tools are referenced (e.g., msiexec, cmdkey, PowerShell), mention if there are Linux alternatives or explicitly state if only Windows is supported.
For scripting, provide bash or Python examples alongside .cmd/.ps1 where feasible.
If Azure Storage Explorer is required, mention az CLI or other cross-platform alternatives.
Explicitly document any OS limitations or requirements up front, so non-Windows users can quickly determine applicability.

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 provisioning the Azure-SSIS Integration Runtime. It references Windows authentication and Windows-specific tools without mentioning or providing alternatives for Linux or cross-platform environments. There are no Bash, CLI, or Linux-native instructions or examples, and all setup steps assume a Windows-centric workflow.

Recommendations:

Provide equivalent instructions using Azure CLI (az commands), which is cross-platform and works on Linux, macOS, and Windows.
Include Bash script examples for provisioning and configuring the Azure-SSIS IR.
Clarify whether the features and setup steps are supported or possible on Linux-based environments, and if not, explicitly state the platform limitations.
Reference cross-platform authentication methods or alternatives to Windows Authentication where possible.
Add a section or note addressing Linux/macOS users, guiding them to appropriate tools and commands.

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 and workflows (such as Event Viewer logs and Windows Performance Counters), providing links and instructions only for Windows-based Log Analytics agent installation, and omitting any mention of Linux equivalents or guidance for Linux-based SHIR hosts. There are no examples, instructions, or references for configuring log analytics collection on Linux systems.

Recommendations:

Add a section describing how to instrument Linux-based SHIR hosts for log analytics collection, including installation of the Log Analytics agent on Linux and relevant prerequisites.
Provide equivalent examples for configuring log collection and performance counters on Linux (e.g., syslog, Linux performance counters, or custom logs).
Include links to Azure documentation for installing and configuring the Log Analytics agent on Linux virtual machines.
Clearly indicate in each section whether the instructions apply to Windows, Linux, or both, and provide parity in guidance and screenshots.
Mention any limitations or differences in monitoring capabilities between Windows and Linux SHIR hosts.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias, particularly in the Azure PowerShell section. It provides explicit instructions for installing Azure PowerShell 'on Windows with PowerShellGet' and uses Windows file paths (e.g., C:\ADFv2QuickStartPSH\MyTrigger.json) in code samples. The PowerShell section appears before the Azure CLI section, and the prerequisites for PowerShell are Windows-specific, potentially excluding Linux/macOS users. However, the Azure CLI and SDK sections are cross-platform and do not show similar bias.

Recommendations:

In the Azure PowerShell section, clarify that Azure PowerShell is cross-platform and provide installation instructions for Linux and macOS, or link to the general installation guide.
Use platform-agnostic file paths in code samples (e.g., ./MyTrigger.json or $HOME/ADFv2QuickStartPSH/MyTrigger.json), or provide both Windows and Linux/macOS examples.
When listing command-line approaches, consider presenting Azure CLI before PowerShell, as CLI is more universally available across platforms.
Add explicit notes or callouts that all SDK and CLI examples work on Linux, macOS, and Windows.
Where possible, avoid language or screenshots that assume a Windows environment unless the tool is truly Windows-only.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows environments. All examples and instructions reference Windows-specific tools and concepts, such as the Windows Registry, Windows environment variables, and Windows file paths. There are no examples or guidance for Linux environments, and the documentation assumes the use of Windows throughout.

Recommendations:

Provide equivalent instructions and examples for Linux environments, if supported by Azure-SSIS IR or self-hosted IR.
Clarify early in the documentation whether Linux is supported or not for these scenarios. If not, state this explicitly.
If Linux support is planned or possible, include Linux-specific paths, environment variable handling, and installation steps alongside Windows instructions.
Where Windows Registry is referenced, suggest equivalent configuration mechanisms for Linux (such as configuration files or environment variables).
When showing file paths or commands, provide both Windows and Linux syntax where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias in several ways: the PowerShell sample is presented first and is specifically tied to Windows (with instructions to install Azure PowerShell on Windows and to create files in a Windows path, e.g., C:\ADFv2QuickStartPSH\). The CLI example is more cross-platform, but the overall structure and ordering prioritize Windows-centric tools and workflows. There are no explicit Linux shell or scripting examples, and the PowerShell instructions do not mention cross-platform compatibility.

Recommendations:

Add explicit Linux/macOS instructions for creating and managing the JSON file (e.g., use ~/ADFv2QuickStart/ or /tmp/ paths in addition to C:\).
Clarify that Azure PowerShell is cross-platform and provide installation links for Linux/macOS, or add a note about using PowerShell Core on non-Windows systems.
Consider presenting the Azure CLI example first, as it is natively cross-platform and more familiar to Linux users.
Add bash shell examples for common tasks (e.g., using jq or curl with the REST API for trigger management).
Review all file path examples and ensure both Windows and Linux/macOS formats are shown where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias by exclusively referencing Windows tools (SSMS, AzureDTExec.exe), providing only Windows command-line examples, and omitting any mention of Linux or cross-platform usage. The installation, configuration, and invocation instructions all assume a Windows environment, with no guidance for Linux users or alternatives for running SSIS packages outside of Windows.

Recommendations:

Explicitly state whether AzureDTExec and SSMS are available or supported on Linux or macOS. If not, clarify this early in the documentation.
If cross-platform support exists (e.g., via .NET Core, Docker, or Azure CLI), provide equivalent Linux/macOS installation and usage instructions.
Include Linux shell (bash) command-line examples alongside Windows examples, or clarify that only Windows is supported.
Mention any alternative tools or workflows for Linux users who need to run SSIS packages in Azure Data Factory.
Avoid assuming the presence of Windows-specific features (like 'Run as administrator', UAC, or UNC paths) without noting their absence or alternatives on other platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias by exclusively referencing Windows authentication, UNC paths, and Windows-centric tools (such as SQL Server Data Tools, SQL Server Management Studio, and the dtutil utility). All file path examples use Windows UNC syntax, and there are no Linux or cross-platform alternatives or examples. There is no mention of Linux-based authentication, file storage, or tooling, nor any guidance for users operating from non-Windows environments.

Recommendations:

Provide Linux-compatible examples for file paths (e.g., Azure Files mounted via SMB on Linux, or using Azure Blob Storage with SAS tokens).
Mention and, where possible, demonstrate authentication mechanisms that work on Linux (such as Azure AD authentication or SAS tokens) in addition to Windows authentication.
Reference cross-platform tools for package development and deployment, or clarify if certain steps require Windows-only tools (like SSDT or SSMS).
Explicitly state any platform limitations (e.g., if only Windows-based Azure-SSIS IR is supported, or if Linux is not supported for certain features).
Where possible, provide guidance or links for Linux users to set up and interact with Azure Data Factory and SSIS packages.
Include notes or examples for managing secrets and credentials using cross-platform methods (such as Azure CLI or REST APIs) instead of only GUI-based or Windows-centric approaches.

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, for all procedures. All examples and UI walkthroughs are based on SSMS, with no mention of cross-platform or Linux alternatives. File path examples use Windows UNC paths, and authentication options reference Windows authentication. There are no instructions or guidance for users on Linux or macOS platforms.

Recommendations:

Provide equivalent instructions using cross-platform tools such as Azure Data Studio or command-line utilities (e.g., sqlcmd, Azure CLI) where possible.
Explicitly state the platform requirements and, if SSMS is mandatory, clarify that it is Windows-only and suggest workarounds for non-Windows users (such as using a Windows VM or remote desktop).
Include examples of file paths and authentication methods relevant to Linux environments, or clarify limitations.
If no Linux-native options exist, acknowledge this in the documentation and provide guidance for Linux users on how to proceed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows environments, specifically Visual Studio and SQL Server Data Tools (SSDT), both of which are Windows-only tools. All instructions, UI references, and workflows assume the use of Windows, with no mention of Linux or cross-platform alternatives. There are no Linux-specific examples or guidance, and Windows authentication is discussed without reference to Linux-compatible authentication methods.

Recommendations:

Explicitly state that SSDT and Visual Studio are Windows-only and note the lack of Linux support up front.
If possible, provide alternative methods for developing, deploying, or executing SSIS packages from Linux environments (e.g., using Azure Data Factory UI, Azure CLI, or REST APIs).
Include references to cross-platform tools or document workarounds for Linux users, such as using remote Windows VMs or containers.
Clarify authentication options for non-Windows environments, or explicitly state if only Windows authentication is supported.
If no Linux support exists, add a section addressing this limitation and suggest feature requests or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references SQL Server Management Studio (SSMS) and SQL Server Agent, both of which are Windows-only tools. All instructions, screenshots, and workflow steps assume the use of SSMS on Windows, with no mention of Linux or cross-platform alternatives. There are no examples or guidance for users on Linux or macOS, nor are command-line or platform-agnostic methods provided.

Recommendations:

Acknowledge in the prerequisites or introduction that SSMS and SQL Server Agent are Windows-only tools, and clarify if there are any supported alternatives for Linux/macOS users.
If possible, provide guidance or references for performing similar migrations using cross-platform tools such as Azure Data Studio, Azure CLI, or PowerShell Core (which is cross-platform).
Include a note or section addressing Linux users, outlining any available options or workarounds, or explicitly state if the migration process is only supported from Windows environments.
Consider adding command-line examples (e.g., using Azure CLI or REST API) for steps such as ARM template deployment, to improve parity for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented towards Windows and PowerShell. All automation and scripting examples use PowerShell, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. The use of SQL Server Management Studio (a Windows-only tool) is recommended for verification. There are no Linux-specific instructions or examples, and the documentation assumes the use of Windows-centric tools and workflows throughout.

Recommendations:

Provide equivalent examples using Azure CLI and Bash scripts for starting, stopping, and monitoring Azure-SSIS IR, alongside PowerShell.
Include instructions for verifying SSIS package execution using cross-platform tools or Azure Portal, not just SQL Server Management Studio.
Mention and demonstrate how to use REST API calls via curl or other cross-platform tools for automation.
Clarify that PowerShell Core is available cross-platform, but also provide Bash/CLI alternatives for Linux users.
Review all screenshots and UI instructions to ensure they are not exclusive to Windows environments, or provide notes for Linux/macOS users where UI may differ.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias. PowerShell is mentioned as a primary method for monitoring pipelines, and the 'Related content' section lists PowerShell before other cross-platform options like .NET, Python, and REST. There is no mention of Linux-specific tools, shell commands, or CLI usage, and the documentation does not provide parity in examples or tool recommendations for Linux users. The focus on PowerShell and the ordering of tools suggest a Windows-first perspective.

Recommendations:

Include Azure CLI examples and references alongside or before PowerShell, as Azure CLI is cross-platform and widely used on Linux.
Mention and link to Bash or shell scripting guides for Linux users where automation or scripting is discussed.
Balance the order of tool references in 'Related content' by listing cross-platform options (Azure CLI, Python, REST) before or alongside PowerShell.
Explicitly state that Azure Data Factory can be managed from Linux, macOS, and Windows, and provide links to relevant Linux/macOS quickstarts.
Where monitoring or automation is discussed, provide examples or references for both PowerShell and Azure CLI.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only Azure PowerShell examples for creating managed virtual networks and private endpoints, with no equivalent examples for Linux/Unix users (e.g., Azure CLI, REST API, or ARM templates). The exclusive use of PowerShell and the absence of cross-platform tooling or scripting options indicate a Windows-centric bias.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell scripts to support Linux/macOS users.
Include REST API and/or ARM template examples for automation scenarios that are platform-agnostic.
Explicitly mention that the PowerShell examples can be run on PowerShell Core (cross-platform) if applicable, or clarify any Windows-only requirements.
Where screenshots or UI steps are shown, ensure they are not specific to Windows-only tools.
Review all sections for references to Windows-specific tools or terminology, and provide Linux/macOS alternatives where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias, particularly in its automation and scripting sections. All command-line examples are provided exclusively in PowerShell, with explicit references to Windows file paths (e.g., C:\ADF\RunSSISPackage) and no mention of Bash, Azure CLI, or cross-platform alternatives. The PowerShell approach is presented as the only automation method, and there are no Linux/macOS-specific instructions or parity notes. The UI walkthrough is platform-agnostic, but all scripting and file management assume a Windows environment.

Recommendations:

Provide equivalent examples using Azure CLI and Bash scripts for all PowerShell automation steps, including Data Factory creation, linked service setup, pipeline deployment, and monitoring.
Replace or supplement Windows file paths (e.g., C:\ADF\RunSSISPackage) with cross-platform or Linux/macOS-friendly paths (e.g., ~/ADF/RunSSISPackage), or clarify that the location is arbitrary.
Explicitly state that the PowerShell approach is cross-platform if using PowerShell Core, or clarify Windows-only requirements if not.
Add a section or callout for Linux/macOS users, outlining any prerequisites or differences in procedure.
Where possible, link to Azure CLI documentation and provide side-by-side code samples for both PowerShell and CLI.
Review metadata (e.g., ms.devlang: powershell) and custom tags to ensure they do not exclude or discourage non-Windows users.

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 command-line automation tool for provisioning and managing Azure-SSIS IR. There are no examples or mentions of Linux-native tools (such as Azure CLI or Bash scripting), nor are there instructions or links for performing equivalent tasks on Linux or macOS platforms. The related content and workflow examples focus on Azure PowerShell and ADF UI, both of which are more familiar to Windows users.

Recommendations:

Add parallel instructions and examples using Azure CLI (az commands), which is cross-platform and widely used on Linux and macOS.
Include explicit references to Bash or shell scripting where automation is discussed, not just PowerShell.
Where PowerShell is mentioned, provide equivalent Azure CLI documentation links or code snippets.
Review related articles to ensure Linux users can follow all workflows without needing to install or use PowerShell.
Clarify in the documentation that all major steps can be performed from Linux/macOS as well as Windows, and provide guidance for both.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools (Event Viewer, Performance Monitor) and linking only to Windows documentation for event logs and performance counters. While Linux is briefly mentioned in the context of performance counters, no Linux-specific instructions, tools, or examples are provided. The focus is on Windows patterns and tools, with Linux support implied but not detailed.

Recommendations:

Include explicit Linux examples for viewing event logs and performance counters, such as using journalctl, syslog, or sar/vmstat.
Provide links to Linux documentation for performance monitoring and log analysis.
Mention Linux tools and commands alongside Windows tools, ensuring parity in instructions.
Clarify any differences in log locations, formats, or monitoring approaches between Windows and Linux SHIR hosts.
Add a section or callout specifically addressing Linux monitoring scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell-based command-line examples for reconfiguring and deleting Azure-SSIS integration runtimes. There are no equivalent examples or instructions for Linux users (e.g., using Azure CLI, Bash, or cross-platform tools). PowerShell is a Windows-native tool (though available on Linux, it is less commonly used there), and no alternative command-line approaches are mentioned.

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 provide installation guidance if PowerShell usage is required.
Where possible, provide Bash script examples or references for Linux users.
Ensure that any references to tools or scripts are clearly marked as cross-platform or provide alternatives for non-Windows environments.
Consider reordering sections or providing tabs to show both PowerShell and Azure CLI (or Bash) approaches side by side.

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 use Azure PowerShell cmdlets, with no mention of equivalent Azure CLI or REST API methods that are cross-platform. The self-hosted integration runtime is described as being installed on 'on-premises Windows machines' only, with no mention of Linux support or alternatives. Windows-centric tools and patterns (PowerShell, SSMS, SSDT) are referenced exclusively or before any cross-platform options. There are no Linux-specific instructions or examples, and the documentation does not address monitoring or managing integration runtimes from Linux environments.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works natively on Linux and macOS.
Mention and document REST API options for monitoring integration runtimes, which can be used from any OS.
Clarify whether self-hosted integration runtime can be installed or monitored from Linux machines, and if not, state this limitation explicitly.
Include references to cross-platform tools (e.g., Azure Data Studio instead of or alongside SSMS, or mention of VS Code for pipeline authoring/monitoring).
Rephrase sections that imply Windows exclusivity (e.g., 'Node is an on-premises Windows machine') to either clarify support or provide Linux alternatives if available.
Add a section or note for Linux/macOS users, summarizing supported monitoring approaches and tools.

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-centric tools (SSMS, SSDT, SQL Server Agent) for monitoring and managing SSIS operations, without mentioning or providing equivalent Linux-based tools or CLI examples. There are no Linux or cross-platform command-line examples, and the workflow assumes the use of Windows environments and tooling.

Recommendations:

Include Azure CLI examples alongside or instead of Azure PowerShell for checking SSIS IR operational status, as Azure CLI is cross-platform.
Mention cross-platform alternatives to SSMS and SSDT, such as Azure Data Studio, and provide instructions or examples for their use.
Clarify whether monitoring and querying can be performed from Linux/macOS environments, and provide guidance for those platforms.
Ensure that all tool references (e.g., for querying logs, raising alerts) include both Windows and cross-platform options.
Add explicit Linux/macOS command-line examples for common monitoring tasks.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing REST API examples exclusively in PowerShell, referencing PowerShell cmdlets throughout, and omitting equivalent Linux/bash/cURL examples. Windows tools and scripting patterns (PowerShell, Write-Host, Get-Date) are used without mention of cross-platform alternatives, and Windows-centric approaches are presented before or instead of Linux-friendly options.

Recommendations:

For REST API sections, provide bash/cURL examples alongside or instead of PowerShell scripts to support Linux and macOS users.
Explicitly mention that PowerShell examples are for Windows and provide equivalent bash or Python scripts for Linux environments.
Where PowerShell cmdlets are referenced (e.g., Get-AzDataFactoryV2PipelineRun), note cross-platform alternatives or clarify their platform compatibility.
Avoid using Windows-specific scripting idioms (e.g., Write-Host, Start-Sleep) without Linux equivalents; provide corresponding bash commands (e.g., echo, sleep).
Consider reordering or parallelizing examples so that Linux-compatible approaches (bash, Python, cURL) are presented alongside Windows/PowerShell, not only after or instead of them.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for deployment and resource management, but consistently lists PowerShell after CLI. However, in the 'Create a file' step, it references Notepad (a Windows-specific editor) without mentioning Linux alternatives. There are no explicit Linux shell or scripting examples, and the use of PowerShell is prominent. The instructions assume familiarity with Windows tools and patterns, and do not provide parity for Linux users in terms of editor or command-line environment guidance.

Recommendations:

In the 'Create a file' section, suggest cross-platform editors (e.g., VS Code, nano, vim) alongside Notepad.
Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and provide any necessary shell syntax (e.g., bash) if needed.
Where PowerShell is shown, consider also showing Bash equivalents for common tasks, or clarify that Azure CLI is cross-platform.
Add notes or tips for Linux/macOS users where file paths, editors, or command syntax may differ.
Ensure that all steps are clearly cross-platform or provide platform-specific guidance as appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), providing only PowerShell-based NuGet installation commands, and omitting any Linux or cross-platform development guidance. There are no instructions or examples for using .NET SDK on Linux or macOS, nor are alternative editors or shell environments (such as VS Code, JetBrains Rider, or Bash) mentioned.

Recommendations:

Include instructions for creating and running the .NET console application using cross-platform tools such as Visual Studio Code and JetBrains Rider.
Provide alternative NuGet installation commands using the dotnet CLI (e.g., 'dotnet add package ...'), which works on Windows, Linux, and macOS.
Mention that the .NET SDK and Azure SDK libraries are cross-platform, and provide guidance for Linux/macOS users (e.g., using Bash or zsh).
Add a section or callout noting any platform-specific differences, such as file paths or environment setup.
Ensure screenshots, if any, are not Windows-only, or provide equivalent steps for other operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools and paths (e.g., Notepad, C:\ paths), providing only Azure PowerShell commands for resource cleanup, and omitting Linux/macOS equivalents for file creation, path conventions, and command-line operations. There are no CLI or Bash examples, and the instructions assume a Windows environment throughout.

Recommendations:

Provide parallel instructions for Linux/macOS users, including file creation using editors like nano, vim, or touch, and using POSIX-compliant paths (e.g., /home/user/ADFv2QuickStartPSH/emp.txt).
Include Azure CLI examples for resource cleanup (e.g., az group delete, az datafactory delete) alongside PowerShell commands.
Avoid referencing only Windows tools (e.g., Notepad); instead, suggest cross-platform editors or provide alternatives.
When specifying file paths, show both Windows and Linux/macOS formats.
Explicitly state that the instructions apply to all platforms, or call out any platform-specific steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation shows a mild Windows bias. It suggests launching Notepad to create a file, which is a Windows-specific tool, and refers to 'command prompt with administrator privileges' before 'terminal', which is a Windows-first phrasing. There are no explicit Linux/macOS examples or tool recommendations (e.g., nano, vi, or touch for file creation), and no mention of Linux-specific instructions for uploading files or running commands. The only optional tool mentioned is Azure Storage Explorer, which is cross-platform, but no Linux-native alternatives or CLI methods are discussed.

Recommendations:

When instructing users to create a text file, mention cross-platform editors (e.g., Notepad (Windows), nano/vi (Linux/macOS), or any text editor).
Instruct users to 'open a terminal or command prompt' without specifying administrator privileges unless required, and clarify if sudo is needed on Linux/macOS.
Provide examples for uploading files to Azure Blob Storage using Azure CLI or azcopy, which are cross-platform, in addition to Azure Storage Explorer.
Explicitly state that all Python code and commands work on Windows, Linux, and macOS, and mention any OS-specific considerations.
Where possible, include Linux/macOS shell commands (e.g., touch input.txt, nano input.txt) alongside Windows instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows bias. All setup instructions and examples assume a Windows environment: PowerShell is used for connectivity testing, the SAP .NET Connector (Windows-only) is required, and file paths reference Windows locations. There are no Linux equivalents or guidance for non-Windows platforms, and Windows tools and patterns are mentioned exclusively.

Recommendations:

Provide equivalent instructions and examples for Linux environments, such as using curl, nc, or telnet for connectivity testing instead of PowerShell.
Clarify whether the self-hosted integration runtime and SAP .NET Connector are supported on Linux, and if not, explicitly state this limitation.
If Linux is supported, include Linux file paths and commands for editing the hosts file (e.g., /etc/hosts).
Mention cross-platform alternatives or workarounds where possible, or direct users to relevant documentation for non-Windows setups.
Structure sections so that Windows and Linux instructions are presented in parallel, or clearly label platform-specific steps.

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 or providing Linux alternatives or examples. The migration steps and tooling assume a Windows environment, and there is no guidance for users operating from Linux or cross-platform environments.

Recommendations:

Explicitly state platform requirements for tools like SSMS, SSDT, dtutil, and DMA, and clarify if they are Windows-only.
If possible, provide Linux-compatible alternatives or document any cross-platform command-line utilities (e.g., Azure CLI, PowerShell Core, REST APIs) that can be used for package management and migration.
Include Linux-specific examples or workflows for common migration tasks, or acknowledge the lack of Linux support and suggest workarounds.
Mention Azure Data Studio as a partial cross-platform alternative to SSMS, and clarify its capabilities and limitations regarding SSIS.
Reorganize sections to avoid always listing Windows tools and approaches first; consider a neutral or platform-agnostic structure.

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, UNC paths, registry entries, and Windows-specific tools (e.g., cmdkey) without providing equivalent Linux or cross-platform guidance. There are no Linux/Unix-specific examples or mentions of how to handle these scenarios on non-Windows systems, which may leave Linux users without clear migration paths.

Recommendations:

For every mention of Windows authentication, environment variables, or registry, provide Linux/Unix equivalents or explicitly state if unsupported.
Include examples or notes for Linux-based SSIS deployments, such as handling environment variables, file paths, and authentication.
When referencing tools like cmdkey or UNC paths, add parallel instructions for Linux (e.g., using keyrings, mounting NFS/Samba shares, or using environment variables).
Clarify platform limitations (e.g., if Azure-SSIS IR only supports Windows-based packages) and provide migration tips for Linux users.
Ensure that documentation structure and examples do not assume a Windows-only environment; add cross-platform context where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several areas. Troubleshooting steps and examples reference Windows-specific tools (e.g., PsPing.exe), and instructions for editing the hosts file are given only for Windows (C:\Windows\System32\drivers\etc), with no mention of Linux equivalents. There are no Linux/Unix command examples or file paths, and Windows tools and patterns are presented exclusively or before any cross-platform alternatives.

Recommendations:

Provide equivalent Linux/Unix command examples (e.g., use 'ping' and 'nc' or 'curl' instead of only 'psping.exe').
Include instructions for editing the hosts file on Linux (e.g., /etc/hosts) alongside the Windows example.
Reference cross-platform tools or note when a tool is Windows-only, and suggest alternatives for other platforms.
Ensure that troubleshooting steps are platform-agnostic or clearly separated for Windows and Linux environments.
Add screenshots or command snippets for both Windows and Linux where 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 are provided exclusively in PowerShell, which is primarily a Windows tool. There is no mention of Linux or cross-platform alternatives, nor are there any bash or shell script examples. The documentation assumes the use of the 'self-hosted integration runtime client', which is a Windows application, and does not address Linux installation, management, or monitoring scenarios. This may leave Linux users without clear guidance.

Recommendations:

Provide equivalent bash or shell script examples for all PowerShell commands, especially for querying and managing integration runtimes using the Azure CLI.
Explicitly mention whether the self-hosted integration runtime is supported on Linux, and if so, provide Linux-specific installation and management instructions.
Include screenshots or instructions for Linux environments where applicable.
Clarify any platform limitations or differences in behavior between Windows and Linux hosts.
Ensure that references to tools (such as the 'client') are accompanied by notes about their platform compatibility.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a strong Windows bias. All installation and configuration instructions, including command-line actions and authentication setup, assume a Windows environment. PowerShell is the only scripting example provided, and references to Windows-specific tools (such as Local Security Policy, NT SERVICE accounts, and Visual Studio/SSDT) are prevalent. There are no Linux or cross-platform alternatives or examples, and no mention of support for running the self-hosted IR or related tools on Linux.

Recommendations:

Clarify early in the documentation whether self-hosted IR and SSIS proxy features are supported on Linux or only on Windows. If Windows-only, state this explicitly.
If Linux is supported, provide equivalent installation, configuration, and authentication instructions for Linux environments, including command-line examples (e.g., Bash, shell scripts) and references to Linux service accounts and security policies.
Offer cross-platform alternatives to PowerShell scripts, such as Azure CLI or REST API examples.
Document where logs and configuration files are located on Linux, if applicable.
Mention any required dependencies or drivers for Linux, and provide download/installation instructions.
If Visual Studio/SSDT is required and only available on Windows, suggest alternative cross-platform development tools if available, or clarify the limitation.
Review all references to Windows-specific tools (e.g., Local Security Policy, NT SERVICE accounts) and provide Linux equivalents or note their absence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias throughout. All troubleshooting steps, examples, and tool references are exclusively for Windows environments. Windows-specific tools (Event Viewer, MMC, Regedit, certutil, Process Monitor, Netmon), file paths, registry edits, and PowerShell commands are used without mention of Linux equivalents. There are no Linux-specific instructions, examples, or troubleshooting guidance, despite the potential for running self-hosted integration runtime on Linux (e.g., via Docker or Mono). Even generic troubleshooting (network, certificates, permissions) is always described using Windows paradigms.

Recommendations:

Add parallel Linux instructions and examples for all troubleshooting steps, including log collection, certificate management, service management, and environment variables.
Include Linux equivalents for all Windows tools mentioned (e.g., use 'journalctl' or 'systemd' logs instead of Event Viewer, 'openssl' for certificate checks, 'strace' or 'lsof' for process monitoring, 'tcpdump' or 'wireshark' for network tracing).
Provide Linux file paths and environment variable instructions alongside Windows paths.
When referencing commands (e.g., PowerShell, certutil, regedit), also provide bash/shell alternatives for Linux.
Explicitly state OS-specific limitations or requirements (e.g., if some features/tools are Windows-only, clarify this and suggest workarounds or alternatives for Linux).
Reorganize sections to present Windows and Linux instructions side-by-side or in clearly labeled tabs, rather than only Windows.
Where only Windows is supported, clearly state this at the top of the documentation.

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 command-line examples use Azure PowerShell cmdlets, and there are no examples or instructions for Linux/macOS users or for using cross-platform tools like Azure CLI or curl. The prerequisite section requires Azure PowerShell, and the workflow assumes a PowerShell environment throughout. Additionally, tools like Azure Storage Explorer (a GUI tool) are mentioned, but no Linux-native or CLI alternatives are provided. This approach excludes users on Linux or macOS who may prefer or require bash, Azure CLI, or REST calls via curl/httpie.

Recommendations:

Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and widely used on Linux/macOS.
Include REST API invocation examples using curl or httpie, demonstrating how to authenticate and make requests without PowerShell.
Explicitly mention that all PowerShell commands can be run on PowerShell Core, which is available on Linux/macOS, or clarify any Windows-only dependencies.
In the prerequisites, offer installation instructions for both Azure PowerShell and Azure CLI, and note their cross-platform availability.
When referencing Azure Storage Explorer, also mention az storage CLI commands or other open-source, cross-platform tools for managing Azure Storage.
Where possible, provide bash script equivalents for automation steps.
Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a bias toward Windows environments by exclusively referencing SQL Server and Azure SQL Database (both Microsoft-centric, often Windows-based), using T-SQL syntax, and describing stored procedures and control tables only in the context of SQL Server. There are no examples or guidance for using open-source or Linux-native databases (such as PostgreSQL or MySQL), nor are there instructions for creating control tables or stored procedures in those systems. No Linux command-line or shell examples are provided, and the workflow assumes a Windows-centric database stack.

Recommendations:

Provide equivalent examples for popular Linux/open-source databases (e.g., PostgreSQL, MySQL, MariaDB), including DDL and stored procedure syntax.
Include guidance for creating and managing control tables and high-watermark logic in non-SQL Server environments.
Offer sample shell (bash) commands or scripts for Linux users where relevant (e.g., for interacting with databases or automating tasks).
Clarify in the introduction that the template is compatible with multiple database systems, and link to platform-specific instructions.
Ensure screenshots and UI references are not specific to Windows-only tools or environments.

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 environment variables (e.g., %TEMP%), and Windows file path conventions (e.g., C:\abc.txt, UNC paths). There are no examples or instructions for Linux-based environments, and no mention of Linux authentication methods, file paths, or tools.

Recommendations:

Include equivalent instructions and examples for Linux-based SSIS IR nodes, if supported.
Mention and provide examples using Linux environment variables (e.g., $TMPDIR) and file paths (e.g., /tmp/abc.txt).
Describe how to connect to file shares using Linux authentication methods (such as SMB/CIFS with Kerberos or username/password).
Clarify whether Azure-SSIS IR supports Linux nodes, and if not, explicitly state this limitation.
If only Windows is supported, add a note to inform users that the documentation is Windows-specific.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias, primarily through the exclusive mention of PowerShell and the lack of Linux-specific or cross-platform command-line examples. References to updating the factory via 'PowerShell or an SDK' and the absence of any mention of Bash, CLI, or Linux tools suggest an assumption of a Windows environment. No explicit Linux or cross-platform workflows, troubleshooting, or configuration steps are provided.

Recommendations:

Add equivalent Bash/CLI examples alongside PowerShell references, especially in troubleshooting and automation sections.
Explicitly mention cross-platform compatibility for SDKs and command-line tools, and provide links to relevant documentation for Linux/macOS users.
Where PowerShell is referenced, add a note or example for Azure CLI or Bash to ensure Linux users are not excluded.
Review all troubleshooting and automation guidance to ensure parity for Linux and macOS environments.
Include a section or callout on cross-platform support, clarifying that all features and integrations are available on non-Windows systems where applicable.

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, paths, and authentication patterns (e.g., SSMS, C:\ paths, NT AUTHORITY accounts, Visual C++ runtime), and by omitting Linux equivalents or cross-platform alternatives. There are no examples or troubleshooting steps for Linux-based environments, and all file path and log references use Windows conventions. The documentation assumes the use of Windows authentication and components, with no mention of Linux-compatible tools or deployment scenarios.

Recommendations:

Add troubleshooting steps and examples for Linux-based environments, including file paths, log locations, and authentication patterns.
Reference cross-platform tools (e.g., Azure Data Studio) alongside or instead of Windows-only tools like SSMS.
Provide both Windows and Linux file path examples and clarify when a step is OS-specific.
Mention Linux-compatible prerequisites (e.g., Mono for SSIS, if supported) and clarify any platform limitations.
Include guidance for setting up and troubleshooting SSIS integration runtime on Linux hosts, if supported, or explicitly state Windows-only support where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing PowerShell cmdlets as a primary troubleshooting interface, mentioning Windows tools (e.g., SSMS) for diagnostics, and omitting Linux equivalents or cross-platform alternatives. All example troubleshooting steps and tool recommendations assume a Windows environment, with no mention of how to perform these tasks on Linux or macOS.

Recommendations:

Include Azure CLI examples alongside or instead of PowerShell cmdlets, as Azure CLI is cross-platform.
Mention and provide steps for using cross-platform SQL management tools (e.g., Azure Data Studio) in addition to SSMS.
When recommending testing scripts locally, clarify how to do so on both Windows (cmd, PowerShell) and Linux/macOS (bash, sh).
Explicitly state whether SSIS IR management and troubleshooting can be performed from non-Windows environments, and provide guidance if so.
Ensure that all tool and script references have Linux/macOS equivalents or note any limitations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation consistently references Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and managing SSIS packages, with no mention of Linux alternatives or cross-platform options. All command-line and GUI examples assume a Windows environment, and PowerShell is referenced for firewall configuration without Bash/Azure CLI equivalents. There are no Linux-specific instructions or parity in tool recommendations.

Recommendations:

Include Azure CLI and Bash examples alongside PowerShell for tasks like configuring firewall rules.
Explicitly state the platform requirements for tools like SSDT, SSMS, dtutil, and AzureDTExec, and mention if they are Windows-only.
If Linux or cross-platform alternatives exist (e.g., Azure Data Studio, cross-platform Azure CLI), provide instructions or links.
Clarify whether package deployment and management can be performed from non-Windows environments, and if not, note this limitation.
Add a section or note addressing Linux/macOS users, outlining what is and isn't supported, and suggesting workarounds or alternatives where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a clear Windows bias. All command-line and scripting examples use PowerShell and Windows command patterns (e.g., 'cmd /c', '.exe' applications). There are no Linux/bash equivalents provided for creating or managing Azure Batch accounts, running pipelines, or specifying commands for custom activities. The documentation references Windows-native tools and patterns (such as .exe files and cmd commands) without mentioning or demonstrating Linux alternatives, and Windows approaches are always presented first or exclusively.

Recommendations:

Provide equivalent bash/CLI examples alongside PowerShell commands for managing Azure Batch and running pipelines.
Include Linux-native command examples (e.g., using '/bin/bash -c' or shell scripts) in the 'command' property for custom activities.
Demonstrate usage of Linux executables (e.g., .sh scripts, ELF binaries) in addition to .exe files.
Clarify in the documentation that both Windows and Linux pool nodes are supported, and specify how to target each OS.
Reference Azure CLI and REST API methods for account and pool management, not just PowerShell.
Add a section or table comparing Windows and Linux usage patterns for custom activities.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a bias towards Windows by providing only .NET/C# SDK code samples, referencing Visual Studio as the default editor, and using Windows-centric instructions for downloading files. There are no Linux-specific examples, alternative SDKs (such as Python, Java, or JavaScript), or CLI-based workflows. The instructions for setting up and running code assume a Windows development environment, and there is no mention of Linux-compatible editors, shells, or package managers.

Recommendations:

Provide code samples in additional languages supported by the Azure Digital Twins SDK, such as Python, Java, or JavaScript, to ensure cross-platform accessibility.
Include instructions for setting up and running the sample project on Linux and macOS, including references to cross-platform editors like VS Code and command-line tools.
Offer alternative commands for package installation using Linux/macOS shells (e.g., bash) and package managers.
When describing file downloads, mention Linux/macOS methods (such as wget or curl) alongside browser-based instructions.
Explicitly state that the SDK and tools are cross-platform, and provide any necessary steps for Linux users (such as setting environment variables or handling authentication).
Add a section or callouts for Linux users, highlighting any differences or considerations in the development workflow.

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 Self-hosted integration runtime installation instructions that implicitly assume a Windows environment), mentioning SQL Server (a Microsoft/Windows-centric database) with detailed setup instructions, and omitting explicit Linux or cross-platform examples or guidance. There are no examples or notes about running the Script activity against Linux-hosted databases, nor are there references to Linux-based integration runtime installation or usage.

Recommendations:

Add explicit instructions or notes for installing and running the Self-hosted integration runtime on Linux, including supported distributions and any differences in setup.
Include examples or references for connecting to databases commonly hosted on Linux (e.g., PostgreSQL, MySQL) if supported, or clarify platform support.
Balance the mention of SQL Server and Windows-centric databases with equivalent guidance for Linux-based environments and databases.
When describing installation or configuration steps, provide both Windows and Linux command-line examples or links to relevant documentation.
Explicitly state platform compatibility and any limitations for Script activity and integration runtime components.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased towards Windows environments. All command-line examples use PowerShell, and certificate management instructions rely on Windows-specific tools (MMC snap-in, Windows certificate stores, and Windows service accounts). There are no examples or guidance for Linux systems, and all terminology and screenshots are Windows-centric.

Recommendations:

Provide equivalent Linux command-line examples (e.g., using openssl, hostname, or certbot for certificate generation and management).
Include instructions for installing and trusting certificates on Linux (e.g., using update-ca-certificates or placing certs in /etc/ssl/certs).
Mention Linux-compatible integration runtime options, if available, or clarify Windows-only support.
Add screenshots or terminal output from Linux environments where applicable.
Use cross-platform terminology where possible (e.g., 'machine' instead of 'Local Machine', 'certificate store' instead of 'Personal').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page is largely platform-neutral in its main content, but there are subtle signs of 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 Microsoft/Windows-centric technologies, without mentioning open-source or Linux-native alternatives. The custom activity section focuses on .NET, a technology historically associated with Windows, and does not provide examples for Linux-native languages or runtimes. The only tutorial linked is for Spark using PowerShell, a Windows-centric tool, with no Bash or Linux CLI equivalent provided.

Recommendations:

When describing HDInsight clusters, alternate the order of 'Windows/Linux-based' or simply state 'Linux or Windows-based' to avoid implicit prioritization.
In the 'Stored procedure activity' section, mention support for other database engines (such as PostgreSQL or MySQL) if available, and provide examples for those platforms.
For custom activities, include examples or references for running Python, Java, or other Linux-native workloads, not just .NET.
Provide equivalent tutorials and code samples for Linux environments (e.g., Bash scripts, Azure CLI) alongside PowerShell examples.
Where possible, clarify cross-platform support and highlight any differences or limitations for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias. All code samples and project setup instructions are based on Visual Studio (Windows-only or Windows-first), and the .NET SDK is used exclusively. The prerequisite tools listed (Visual Studio, Azure Storage Explorer) are Windows-centric, and there are no examples or guidance for Linux or cross-platform development environments. No alternative instructions are provided for Linux users, such as using VS Code, the Azure CLI, or .NET Core on Linux/macOS.

Recommendations:

Provide equivalent instructions for Linux and macOS users, such as using VS Code or JetBrains Rider instead of Visual Studio, and .NET Core SDK instead of .NET Framework.
Include command-line examples using Azure CLI or PowerShell Core (which is cross-platform), and show how to run the sample code on Linux/macOS.
Mention cross-platform alternatives for Azure Storage Explorer, or clarify its availability on Linux/macOS.
Add a section or callout at the start of the tutorial indicating that the steps can be performed on Linux/macOS, and provide links to relevant setup guides.
Where possible, use .NET 6+ (or .NET Core) for code samples to ensure cross-platform compatibility.
Explicitly state any Windows-only requirements, and suggest workarounds or alternatives for non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a subtle Windows bias by referencing Windows-specific tools and workflows (e.g., Notepad for file creation), omitting Linux/macOS equivalents, and not providing cross-platform command-line alternatives. There are no explicit Linux or macOS instructions or examples, and the only tool mentioned for file editing is Notepad, which is Windows-specific. The documentation also references browser support but does not mention OS-specific browser nuances or alternatives for Linux users.

Recommendations:

When instructing users to create a text file, mention cross-platform editors (e.g., 'Use Notepad (Windows), TextEdit (macOS), or nano/vi (Linux) to create the emp.txt file').
Provide command-line alternatives for file creation and upload, such as using 'echo' or 'cat' in a terminal, and include Azure CLI or azcopy commands for uploading files to Blob storage.
Avoid assuming the user's operating system; use neutral language and mention steps for both Windows and Linux/macOS where relevant.
If referencing tools like Azure Storage Explorer, clarify that it is cross-platform and provide download links for all supported OSes.
Explicitly state that the tutorial is OS-agnostic except where the Azure portal UI is used, and provide tips for Linux/macOS users where workflows may differ.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias by exclusively using Visual Studio (a Windows-centric IDE), .NET SDK, and NuGet Package Manager Console (PowerShell-based) for all code and setup instructions. There are no examples or guidance for Linux or cross-platform development environments (e.g., VS Code, CLI, or Python SDK). All tooling and workflow steps assume a Windows environment, omitting Linux equivalents for project creation, package management, and database access/validation.

Recommendations:

Provide equivalent instructions for Linux users, such as using VS Code or JetBrains Rider for C# development, and include CLI-based project creation (dotnet CLI) instead of only Visual Studio.
Show how to install required NuGet packages using the dotnet CLI (e.g., 'dotnet add package ...') rather than only the Package Manager Console.
Mention and provide examples for using the Azure Data Factory Python SDK or REST API, which are cross-platform.
Include instructions for connecting to Azure SQL Database using cross-platform tools like Azure Data Studio or sqlcmd, not just SQL Server Management Studio (SSMS) or Visual Studio.
Add a note or section on how to run and debug the sample code on Linux or macOS, including any prerequisites or differences.
Ensure all screenshots and UI references are either cross-platform or alternatives are provided for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows tools (SQL Server Management Studio, Notepad), omitting Linux alternatives or instructions, and implicitly assuming a Windows environment for the integration runtime installation. There are no examples or guidance for users on Linux or macOS platforms, and all setup steps and screenshots are tailored to Windows users.

Recommendations:

Include instructions for connecting to SQL Server from Linux/macOS using tools like Azure Data Studio or sqlcmd.
Mention and provide steps for editing files using cross-platform editors (e.g., VS Code, nano) instead of only Notepad.
Clarify whether the self-hosted integration runtime can be installed on Linux, and if so, provide installation steps for Linux (and macOS, if supported).
Add notes or sections for Linux users wherever the process differs or additional steps are required.
Ensure screenshots and UI references are not Windows-specific, or provide Linux/macOS equivalents where relevant.

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), using Windows-centric terminology (e.g., Notepad), and omitting any Linux-specific instructions or alternatives. There are no examples or guidance for users running SQL Server on Linux or for using Linux-based tools to accomplish the same tasks.

Recommendations:

Include instructions for connecting to SQL Server using cross-platform tools such as Azure Data Studio, which is available on Windows, macOS, and Linux.
Provide alternative command-line examples for creating databases and tables using sqlcmd, which is available on Linux.
Mention Linux-compatible text editors (e.g., nano, vim) alongside Notepad.
Clarify that SQL Server can run on Linux and provide links or notes for Linux installation and management.
Ensure that any screenshots or step-by-step instructions that are OS-specific are accompanied by Linux equivalents or notes.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows tools (SQL Server Management Studio) for database operations, omitting any mention of Linux-compatible alternatives. All instructions for interacting with the database assume the use of SSMS, and there are no examples or guidance for users on Linux or macOS platforms. No PowerShell-specific commands are present, but the overall workflow and tooling references are Windows-centric.

Recommendations:

Include instructions for connecting to Azure SQL Managed Instance using cross-platform tools such as Azure Data Studio, sqlcmd, or DataGrip, alongside or instead of SQL Server Management Studio.
Provide command-line examples (e.g., using sqlcmd) for creating tables, enabling CDC, and modifying data, so Linux and macOS users can follow along without SSMS.
Explicitly mention that the steps can be performed from any OS, and list the supported tools for each platform.
Where screenshots are shown for SSMS, consider adding equivalent screenshots or terminal outputs for cross-platform tools.
Add a section or note at the beginning of the tutorial clarifying that all database operations can be performed from Linux, macOS, or Windows, and provide tool recommendations for each.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides examples for Azure Portal, Azure CLI, and PowerShell, with significant emphasis on PowerShell and Windows-centric tooling. PowerShell examples are detailed and include references to Windows file paths (e.g., D:\testFiles), and the PowerShell section suggests running commands locally or in Azure Cloud Shell. There is no mention of Linux-specific shell usage, nor are there any Bash or Linux-native command examples. The documentation assumes familiarity with Windows conventions and tools, and does not provide parity for Linux users.

Recommendations:

Add explicit Bash examples alongside PowerShell, especially for common tasks like uploading files to Azure Storage.
Avoid using Windows-specific file paths (e.g., D:\testFiles) in examples; provide cross-platform alternatives or note Linux equivalents (e.g., /home/user/testFiles).
Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide sample commands in Bash syntax where appropriate.
Mention that Azure Cloud Shell supports both Bash and PowerShell, and provide guidance for both environments.
Where PowerShell is referenced, include a note or section for Linux users on how to install and use PowerShell Core if needed, or suggest equivalent Bash commands.
Ensure that documentation does not assume a Windows environment by default, and structure examples so that Linux and Windows users are equally supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides extensive PowerShell examples, including file paths and commands that are specific to Windows environments (e.g., D:\testFiles), and references to PowerShell as a primary automation tool. While Azure CLI examples are present (which are cross-platform), the PowerShell sections are more detailed, and there are no explicit Linux shell (bash) or native Linux file system examples. The documentation also references Windows-style file paths and omits Linux-specific guidance for file uploads or scripting, potentially making it less approachable for Linux users.

Recommendations:

Add explicit bash/Linux shell examples alongside PowerShell, especially for file operations (e.g., uploading files to Azure Storage using az CLI and Linux file paths like /home/user/testFiles/textfile.csv).
Avoid using Windows-specific file paths (e.g., D:\testFiles) in generic examples; provide both Windows and Linux path variants.
Clarify that PowerShell commands can be run cross-platform (e.g., in Azure Cloud Shell), but also provide equivalent bash/CLI workflows for Linux users.
Ensure that all automation and scripting examples are available in both PowerShell and bash/CLI formats, with equal detail and explanation.
Mention Linux tools (e.g., azcopy, curl, or bash scripting) where appropriate, not just Windows-centric tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by highlighting updates to the Windows VHD base image and cumulative Windows/.NET updates, without mentioning Linux equivalents or updates. There is no reference to Linux-based deployments, images, or tools, and all update notes are Windows-centric. No Linux-specific issues, improvements, or instructions are provided.

Recommendations:

Include information about Linux-based images or deployments if supported, or explicitly state if only Windows is supported.
Mention updates or changes relevant to Linux environments, such as kernel or package updates, if applicable.
Provide parity in release notes by listing both Windows and Linux changes, or clarify platform support.
If Linux is not supported, add a clear note to avoid confusion for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by referencing Windows-centric tools and defaults (such as time.windows.com for NTP and NTLM authentication for proxies), and by omitting any Linux-specific instructions or examples. There is no mention of Linux-based management, nor are Linux-friendly alternatives or considerations provided for key steps such as proxy authentication or NTP configuration.

Recommendations:

Include Linux-specific examples or notes, such as how to access the local web UI from common Linux browsers or how to handle certificate warnings on Linux.
Mention Linux-friendly NTP servers (e.g., pool.ntp.org) alongside time.windows.com, and clarify that any standards-compliant NTP server can be used.
Provide guidance for proxy authentication methods commonly used in Linux environments (e.g., Basic, Digest) or clarify NTLM limitations.
Add troubleshooting tips or references for Linux users, such as how to find the device's IP address from Linux-based hypervisors or network tools.
Ensure that any references to Windows-specific tools or defaults are balanced with Linux equivalents, or explicitly state cross-platform compatibility where appropriate.

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 command-line examples use PowerShell cmdlets, and the workflow assumes a Windows client environment. Instructions for installing and using kubectl are Windows-specific, and file path references are Windows-only. There are no Linux or macOS examples, nor any mention of equivalent Linux commands or file locations. Windows tools (e.g., Notepad, curl.exe) and patterns are referenced exclusively.

Recommendations:

Provide parallel instructions and examples for Linux (and optionally macOS) environments, including shell (bash) commands for managing namespaces, users, and kubectl configuration.
Include Linux-specific instructions for downloading and installing kubectl, referencing the appropriate binary and installation steps.
Document the location of the kube config file for Linux/macOS users (typically ~/.kube/config), and provide examples of copying the config file in those environments.
Replace or supplement Windows-specific tools (e.g., Notepad, hosts file path) with Linux equivalents (e.g., nano/vim, /etc/hosts).
Clearly state at the beginning that the instructions are applicable to both Windows and Linux clients, and structure the documentation to present both options equally.
Where PowerShell cmdlets are required (e.g., New-HcsKubernetesNamespace), clarify if and how these can be run from non-Windows clients, or provide REST API or CLI alternatives if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased towards Windows environments, specifically Windows Server with Hyper-V. All instructions, screenshots, and tooling references are Windows-specific (e.g., Hyper-V Manager, Server Manager, BitLocker, PowerShell cmdlets). There are no examples, instructions, or even mentions of Linux-based hypervisors (such as KVM, QEMU, or even VMware on Linux), nor are there cross-platform command-line alternatives. The use of PowerShell cmdlets for network configuration further excludes Linux users.

Recommendations:

Add a parallel tutorial for provisioning Data Box Gateway on Linux-based hypervisors (e.g., KVM, QEMU, or VMware Workstation/ESXi on Linux).
Include Linux command-line examples for network configuration and device management, using standard Linux tools (e.g., ip, nmcli).
Mention and provide guidance for cross-platform hypervisors (such as VMware, VirtualBox) where supported.
Clearly state in the prerequisites and overview whether Linux hosts are supported or not; if not, explain the limitation.
If the product is Windows-only, make this explicit early in the documentation to set user expectations.
Where PowerShell cmdlets are used, provide equivalent Linux shell commands if possible, or clarify that these steps are only for Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides only a PowerShell script for deploying Arc-enabled ContainerApps in an Extended Zone, with no equivalent Bash or Linux shell example. All automation and scripting guidance is presented in PowerShell syntax, which is native to Windows and less commonly used on Linux. There is no mention of Linux or cross-platform alternatives, and the script assumes a Windows environment (e.g., use of .ps1 files, PowerShell-specific constructs).

Recommendations:

Provide a Bash (or cross-platform shell) script example alongside the PowerShell script to ensure Linux users can follow the same workflow.
Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI and Bash, and provide any necessary adjustments (e.g., syntax differences, file paths).
If PowerShell is required, clarify that PowerShell Core is available cross-platform, and provide installation instructions for Linux/macOS.
Review all script snippets and ensure that any Windows-specific commands or patterns have Linux equivalents or are written in a cross-platform manner.
Consider restructuring the documentation to present both Windows and Linux approaches in parallel, or at least note the parity and differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows guest OS settings, using Windows-specific command-line tools (PowerShell cmdlets), and omitting any Linux-based examples or instructions. The tutorial instructs users to select Windows as the guest OS, provides only PowerShell cmdlets for network configuration, and does not mention or provide guidance for Linux-based management or alternative approaches.

Recommendations:

Include instructions for provisioning the Data Box Gateway with a Linux guest OS, if supported, or clarify if only Windows is supported.
Provide equivalent Linux shell commands (e.g., ip, ifconfig, nmcli) for network configuration, or explicitly state if only PowerShell is available within the VM.
Add notes or sections addressing Linux-based host environments, such as managing the VM from a Linux workstation or using open-source hypervisors if applicable.
Clarify OS compatibility and support in the prerequisites, and provide parity in examples for both Windows and Linux users where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows Server/Hyper-V as the primary host platform, mentioning it before VMware, and omitting any references to Linux-based hypervisors (such as KVM or VirtualBox). There are no Linux-native instructions or examples, and the only supported host environments are Windows Server (Hyper-V) and VMware ESXi, both of which are typically managed from Windows or proprietary interfaces. No Linux command-line or tooling is referenced.

Recommendations:

Add explicit support or documentation for Linux-based hypervisors (e.g., KVM, VirtualBox) if the product supports them.
If Linux is not supported as a host, clearly state this limitation early in the prerequisites.
Provide parity in examples and instructions for Linux environments where possible (e.g., how to download and deploy the VMDK on a Linux-managed VMware host).
Include Linux command-line examples for tasks such as downloading and unzipping the device image.
Mention Linux-compatible management tools or clarify if only Windows tools are supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides command-line examples exclusively in PowerShell, which is native to Windows environments. There are no equivalent examples or instructions for Linux users (e.g., using Azure CLI or Bash). The documentation assumes the use of Windows tools and does not mention Linux alternatives or provide parity in command-line instructions.

Recommendations:

Provide equivalent Azure CLI commands for listing and registering resource providers, as Azure CLI is cross-platform and commonly used on Linux.
Explicitly mention that the PowerShell examples are for Windows and offer Bash/Azure CLI alternatives for Linux/macOS users.
Include notes or sections that address Linux users, ensuring that all command-line operations can be performed on both Windows and Linux platforms.
Where screenshots or UI instructions are given, clarify if there are any platform-specific differences or confirm that the web UI is platform-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing SMB (the Windows protocol) as the default and providing more detailed instructions for SMB shares, including references to File Explorer and local user management, which are Windows-centric. There is no mention of Linux tools or workflows for managing NFS shares beyond specifying allowed client IPs. The documentation omits Linux-specific guidance or examples for accessing or managing shares, and does not mention Linux file managers or command-line tools. All examples and screenshots are based on the Azure portal UI, but the only workflow details provided for permissions and access are for Windows/SMB scenarios.

Recommendations:

Provide equivalent Linux/NFS examples, such as how to mount NFS shares from a Linux client and manage permissions using Linux tools.
Include references to Linux file managers (e.g., Nautilus, Dolphin) or command-line utilities (e.g., mount, chmod, chown) for managing NFS shares.
Balance the detail level between SMB and NFS sections, ensuring that Linux/NFS users have clear, actionable instructions.
Avoid assuming SMB is the default or primary use case; present SMB and NFS options with equal prominence.
Add troubleshooting tips and best practices for both Windows and Linux environments.

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 patterns (e.g., Hyper-V and a YouTube link for adding a hard drive to a Hyper-V VM) without mentioning or providing equivalent instructions for Linux-based hypervisors (such as KVM or VMware on Linux). There are no Linux-specific examples or guidance, and the only virtualization management example is for Windows.

Recommendations:

Provide equivalent instructions and references for adding data disks in popular Linux hypervisors (e.g., KVM/QEMU, VMware ESXi on Linux).
Include links to official documentation for managing disks in Linux environments.
Ensure that examples and guidance are platform-neutral or include both Windows and Linux scenarios where applicable.
Avoid referencing only Windows tools (such as Hyper-V) without mentioning Linux alternatives.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (such as Windows Defender, Device Guard, BitLocker, and Hyper-V Manager) and PowerShell for remote management, without mentioning Linux equivalents or providing Linux-based examples. The guidance and security recommendations are tailored to Windows environments, with no discussion of Linux hypervisors, Linux-compatible encryption, or remote management via Linux-native tools.

Recommendations:

Include equivalent Linux-based instructions and examples for all management and security tasks, such as using SSH for remote access, and Linux-native disk encryption tools (e.g., LUKS/dm-crypt) for protecting virtual disks.
Mention and provide guidance for deploying Data Box Gateway on popular Linux hypervisors (such as KVM or VMware on Linux) alongside Hyper-V.
Reference Linux-compatible malware protection solutions if available, or clarify the security posture when running the device on Linux hosts.
Provide parity in documentation structure by presenting Linux and Windows options side by side, rather than Windows-first or Windows-only.
Clarify any platform limitations (e.g., if certain features are Windows-only) and suggest best practices for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a strong Windows bias. All file copy examples use Windows 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 tools mentioned for copying or validating data. Linux users are only briefly referenced, with no guidance or command-line examples provided for Linux environments.

Recommendations:

Provide equivalent Linux command-line examples for copying data to the Data Box Disk, such as using cp, rsync, or smbclient.
List Linux-compatible tools for checksum validation (e.g., sha256sum, md5sum) and provide example commands for validating data integrity.
Explicitly mention any limitations or differences for Linux users at the start of relevant sections, and offer alternative workflows where Windows-only tools are referenced.
Include troubleshooting tips and best practices for Linux environments, such as handling long paths, file permissions, and mounting NTFS disks.
Where screenshots or walkthroughs are provided, include at least one example from a Linux desktop or terminal.

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 instructions for setting blob tiers, without mentioning or providing equivalent Linux/CLI examples. The use of PowerShell as the primary automation tool and the lack of explicit Linux/Unix command-line alternatives (such as Azure CLI or REST API) may disadvantage Linux users. Additionally, the documentation does not clarify cross-platform compatibility or provide Linux-specific guidance for common tasks.

Recommendations:

Include Azure CLI examples alongside or before PowerShell instructions for tasks such as setting blob tiers, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that Data Box Gateway supports both SMB and NFS, and provide example commands for both Windows and Linux clients (e.g., using mount, smbclient, or NFS utilities on Linux).
Where PowerShell scripts are referenced, add equivalent Bash or shell script examples for Linux users.
Clarify any platform-specific requirements or differences in the setup and usage of Data Box Gateway.
Review all step-by-step procedures to ensure Linux users are not required to infer or translate Windows-specific instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses PowerShell commands and references connecting to the PowerShell interface, with no mention of Linux shells, CLI alternatives, or cross-platform tools. All examples, command syntax, and output are Windows/PowerShell-specific, and there are no instructions or guidance for users on Linux or macOS systems.

Recommendations:

Provide equivalent command-line instructions using Azure CLI (az) where possible, which is cross-platform.
Include Linux shell (bash) examples for connecting to the device and managing VM sizes, if supported.
Clarify whether the operations can only be performed via PowerShell or if there are REST API/CLI alternatives, and document those for non-Windows users.
Add a section or note explicitly addressing Linux/macOS users, including any prerequisites or limitations.
If PowerShell Core (pwsh) is required and supported on Linux/macOS, mention this and provide installation guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a notable Windows bias. PowerShell and Windows-specific instructions are given prominence, with command prompts and output examples consistently referencing Windows environments (e.g., 'PS C:\Windows>'). Installation steps and prerequisites focus on Windows PowerShell, and there is little to no mention of Linux or macOS equivalents for local CLI or PowerShell usage. Even when discussing Azure CLI, the examples and screenshots are Windows-centric, and there are no explicit Linux terminal examples or guidance for non-Windows users.

Recommendations:

Provide explicit Linux (and optionally macOS) examples for Azure CLI usage, including sample commands and expected output in a bash shell (e.g., '$ az login').
When referencing installation steps for CLI or PowerShell, include links and instructions for Linux and macOS, not just Windows (e.g., 'Install Azure CLI on Linux').
Avoid using Windows PowerShell as the default or only terminal in CLI examples; alternate or parallel examples in bash should be included.
Where output paths or prompts are shown (e.g., 'PS C:\Windows>'), provide equivalent bash prompt examples (e.g., '$'), or use generic prompts.
Clarify that Azure PowerShell can be used cross-platform (with PowerShell Core), and provide installation and usage instructions for Linux/macOS.
Add a section or note explicitly addressing Linux/macOS users, outlining any differences or considerations for those platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific technologies (such as BitLocker) as the primary or default encryption method, mentioning Windows client requirements before Linux, and not providing Linux-specific instructions or examples for ordering or managing Data Box Disk. There are no CLI or portal instructions that address Linux-specific workflows or tools, and the only encryption technology explicitly named is BitLocker, which is a Windows technology.

Recommendations:

Provide explicit Linux client instructions and examples, especially for disk encryption and mounting, in parity with Windows.
Mention Linux compatibility and workflows alongside Windows in all relevant sections, not just as an afterthought.
Include references to Linux-native tools and commands (e.g., cryptsetup for disk encryption, mount commands) where appropriate.
Clarify the process for using hardware-encrypted disks on Linux, including any required drivers or utilities.
Ensure that any software prerequisites or required software sections include both Windows and Linux tools, with equal detail.
Where BitLocker is mentioned, also describe the Linux alternatives or how Linux users can access BitLocker-encrypted disks.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by focusing on PowerShell-based management and commands, referencing Windows clients and tools, and omitting equivalent Linux/Unix instructions or examples. All command-line examples use PowerShell syntax, and device access is described via a PowerShell interface, with no mention of Linux shells or cross-platform alternatives. The documentation assumes or prioritizes Windows environments, leaving Linux users without clear guidance.

Recommendations:

Provide equivalent Linux/bash command-line examples alongside PowerShell commands, using standard Azure CLI or shell syntax.
Explicitly mention and document how to connect to the device and perform management tasks from Linux or macOS clients.
Clarify whether the PowerShell interface is accessible from non-Windows systems (e.g., via SSH or cross-platform PowerShell Core), and provide instructions if so.
Include screenshots or UI walkthroughs from non-Windows environments where applicable.
Review all prerequisite and step sections to ensure Linux users are not excluded or left without actionable instructions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several areas. Windows tools and patterns (e.g., robocopy, Explorer, PowerShell) are mentioned exclusively or before Linux equivalents. Some command examples are given only in Windows syntax (e.g., mounting NFS shares with Windows paths), and workarounds reference Windows utilities without providing Linux alternatives. There is a lack of parity in providing Linux-specific instructions or examples, especially for common cross-platform tasks.

Recommendations:

For each tool or workaround mentioned (e.g., robocopy, Explorer, PowerShell), provide equivalent Linux commands or tools (e.g., rsync, cp, bash/ssh).
When giving command-line examples (such as mounting NFS shares), include both Windows and Linux syntax side by side.
Avoid referencing only Windows utilities in general recommendations; always mention cross-platform or Linux-native options.
If a PowerShell interface is referenced, clarify if a Linux-compatible shell or CLI is available, and provide instructions for both environments.
Review all examples and ensure Linux users can follow the documentation without needing to translate Windows-specific instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias through the frequent use of PowerShell interfaces and commands, references to Windows-specific tools (e.g., robocopy, Explorer), and examples that use Windows paths or commands before (or instead of) Linux equivalents. There are missing Linux command examples in several workarounds, and in some cases, only Windows-centric instructions are provided.

Recommendations:

For every PowerShell command or interface reference, provide equivalent Bash/shell commands for Linux clients.
When suggesting tools like 'robocopy' or 'Explorer', also mention and provide examples for Linux tools such as 'rsync', 'cp', or file managers.
In NFS mount examples, include both Windows (e.g., 'mount -o anon ...') and Linux (e.g., 'mount -t nfs -o nolock ...') command lines.
For SQL connectivity, show both Windows (cmd/PowerShell) and Linux (bash) usage of 'sqlcmd'.
Ensure that all device management and troubleshooting steps are documented for both Windows and Linux environments, or explicitly state if a feature is Windows-only.
Review all code snippets and paths to ensure parity (e.g., avoid only showing 'C:\Users\...' and include '/home/user/...').

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 (robocopy) instructions and scenarios first and in much greater detail, including command breakdowns and multiple usage examples. Linux instructions are minimal, lacking detailed steps for preserving metadata (especially ACLs), and do not provide equivalent command breakdowns or advanced scenarios. The Linux section omits examples for copying ACLs and attributes, and does not mention or explain tools such as smbcacls or cifsacl beyond a brief mention.

Recommendations:

Provide Linux examples with the same level of detail as Windows, including command breakdowns and explanations for each parameter.
Include step-by-step instructions for copying both data and metadata (ACLs, timestamps, attributes) on Linux, using tools like smbcacls or cifsacl.
Present Linux and Windows sections in parallel or side-by-side, or clearly indicate both options at the start, to avoid the impression of Windows being the default.
Add troubleshooting notes and advanced scenarios for Linux users, similar to the Windows/robocopy section.
Reference Linux documentation for the mentioned tools, and provide links to official guides for rsync, smbcacls, and cifsacl.

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 tool usage 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 examples or guidance for running the tool on Linux or macOS, nor any mention of cross-platform compatibility or alternatives. The documentation assumes the user is on Windows from the outset and does not address Linux users at all.

Recommendations:

Clarify whether the Azure Stack Network Readiness Checker can be run on Linux or macOS (e.g., via PowerShell Core/7.x). If not, state this limitation explicitly at the top of the documentation.
If the tool supports PowerShell Core (which is cross-platform), provide installation and usage instructions for Linux and macOS, including how to install PowerShell and the module on those platforms.
Include Linux/macOS-specific examples for installing PowerShell, installing the module, and running the tool, including sample command lines and expected output.
If the tool is Windows-only, suggest alternative network readiness checks for Linux users, or provide a roadmap for cross-platform support.
Avoid using Windows-specific file paths in examples and outputs, or provide equivalent paths for other operating systems where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. Several examples and instructions reference Windows tools (e.g., PowerShell, robocopy, Explorer), and PowerShell is the primary interface mentioned for device management and troubleshooting. Some command examples use Windows paths or syntax, and Linux equivalents are often missing or not mentioned first. There are also cases where only Windows-specific tools or workflows are described, with no parallel Linux guidance.

Recommendations:

Provide Linux/bash command examples alongside PowerShell and Windows command line instructions for all device management and troubleshooting steps.
When referencing tools like robocopy or Explorer, include Linux alternatives such as rsync, cp, or file manager equivalents.
For connection instructions (e.g., sqlcmd, mounting NFS shares), show both Windows and Linux command syntax.
Avoid assuming the use of Windows as the default environment; present cross-platform instructions or clearly indicate when a step is OS-specific.
Where PowerShell is referenced, mention if SSH/bash access is also supported and provide equivalent commands.
Review all examples and ensure Linux users can follow the documentation without needing to translate Windows-specific steps themselves.

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 primary (and often only) command-line interface referenced for device management, troubleshooting, and automation. Windows-specific tools and patterns (such as RDP, Windows services, and Windows Guest Agent processes) are detailed, while Linux equivalents are not mentioned or are missing entirely. In example commands and workarounds, Windows approaches are described first or exclusively, with little to no Linux parity or alternative instructions.

Recommendations:

Provide equivalent Linux/bash command-line instructions and examples wherever PowerShell is referenced (e.g., connecting to the device, managing VMs, troubleshooting).
Include Linux tools and patterns (such as SSH, systemd, Linux guest agent processes) alongside Windows tools like RDP and Windows services.
When describing issues or workarounds that are Windows-specific, explicitly state if/how they apply to Linux VMs, and provide Linux-specific guidance if relevant.
For all code snippets and command examples, offer both Windows (PowerShell/CMD) and Linux (bash/CLI) versions.
Review documentation for assumptions that users are on Windows, and ensure Linux users are equally supported in all workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits Windows bias by referencing Windows-specific tools (DataBoxDiskSplitCopy.exe, DataBoxDiskValidation.cmd), providing troubleshooting steps only for Windows clients (enabling long paths), and omitting any mention of Linux equivalents or guidance for Linux users. There are no Linux or cross-platform examples or instructions, and the only client configuration advice is for Windows.

Recommendations:

Include equivalent instructions for Linux clients, such as how to handle long file paths and any relevant filesystem limitations.
Mention or provide Linux-compatible tools or scripts for validating and splitting data, or clarify if the provided tools are Windows-only.
Add examples or troubleshooting steps for common Linux scenarios, such as mounting disks, copying data, and handling file naming or path length issues.
Use neutral, cross-platform language where possible, and avoid assuming the user is on Windows.
If certain features or tools are only available on Windows, explicitly state this and suggest alternatives 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 and PowerShell bias. Most configuration and management instructions reference the PowerShell interface, Az cmdlets, or Windows-specific tools and workflows. Several examples and workarounds are presented only for Windows environments (e.g., using robocopy, Explorer, or Windows command line for file operations), and Linux equivalents are missing or not mentioned. Windows tools and patterns (such as RDP, waappagent.exe, Windows VM Guest Agent) are discussed in detail, while Linux/Unix approaches are not provided or are secondary. There is little to no guidance for users managing Azure Stack Edge from Linux systems.

Recommendations:

Provide equivalent Linux/bash command-line examples alongside PowerShell commands for all device management and configuration tasks.
Mention and document Linux-native tools (e.g., rsync, cp, scp) wherever Windows tools like robocopy or Explorer are referenced.
Include instructions for connecting to and managing the device from Linux systems, such as using SSH instead of RDP or PowerShell remoting.
Document how to use Az CLI (cross-platform) in addition to Az PowerShell cmdlets.
Ensure that all troubleshooting and workaround steps have Linux alternatives where applicable.
Avoid assuming the user is on Windows; structure examples so that Linux and Windows approaches are presented with equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows updates and tools, providing PowerShell/cmdlet instructions for key operations, and referencing Windows-specific utilities (e.g., robocopy, Explorer, RDP). Linux equivalents, where relevant, are missing or not mentioned, and Linux command-line examples are rare or absent. In several cases, only Windows-centric workarounds or instructions are provided, with no parity for Linux users.

Recommendations:

Provide Linux/Unix command-line examples alongside Windows/PowerShell instructions for device management, troubleshooting, and configuration tasks.
Reference Linux-native tools (e.g., rsync, cp, scp) in addition to Windows tools like robocopy and Explorer for file operations.
Include instructions for connecting to the device using SSH or Linux shells, not just PowerShell or RDP.
When describing certificate management, VM management, or network configuration, ensure that both Windows and Linux workflows are documented.
Explicitly call out any differences in behavior or requirements between Windows and Linux clients, and provide guidance for both.
Add Linux-specific troubleshooting steps and examples where only Windows steps are currently given (e.g., for custom script extensions, VM management, or network troubleshooting).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. Several workarounds and examples reference Windows-specific tools (e.g., robocopy, Explorer, PowerShell, RDP), and some instructions are provided only for Windows environments or with Windows commands first. In some cases, Linux equivalents are missing or not given equal prominence. For example, file copy workarounds mention robocopy and Explorer, and PowerShell is referenced for device management and VM operations, but Linux shell or command-line alternatives are not provided.

Recommendations:

For every Windows-specific tool or command mentioned (e.g., robocopy, Explorer, PowerShell), provide equivalent Linux commands (e.g., rsync, cp, bash shell commands) alongside.
When giving examples or workarounds, include both Windows and Linux command-line instructions, and avoid listing Windows first by default.
Where PowerShell is referenced for device management, provide corresponding bash or shell command examples for Linux users.
Explicitly mention cross-platform alternatives for remote access (e.g., SSH for Linux, RDP for Windows) when discussing VM connectivity.
Audit all examples and workarounds to ensure Linux users are not required to infer steps or tools on their own.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias through frequent references to Windows-specific tools (e.g., PowerShell cmdlets, robocopy, Windows VM Guest Agent), and provides examples and workarounds primarily for Windows environments. PowerShell is often mentioned as the interface for device management, and Windows tools or patterns are described without equivalent Linux alternatives. In several cases, Linux or cross-platform alternatives are missing or only implied, not explicitly documented.

Recommendations:

For every PowerShell or Windows-specific command or tool mentioned (e.g., Get-VMInguestLogs, robocopy, Windows VM Guest Agent), provide equivalent Linux/bash commands or instructions where applicable.
When referencing file copy operations (e.g., using robocopy or Windows Explorer), also mention Linux tools such as rsync, cp, or scp.
If a workaround involves connecting via PowerShell, add instructions for connecting via SSH or using Linux-native management tools, where supported.
For SQL database access, include Linux installation and usage instructions for sqlcmd, and clarify any OS-specific differences.
When discussing VM or device management, clarify whether Linux-based management is supported and provide examples.
Audit all examples and workarounds to ensure Linux users are not left without clear guidance.
Where Windows-specific issues are described, note if similar issues exist or do not exist on Linux, and provide Linux-specific troubleshooting steps if relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation shows a moderate Windows bias. Several examples and workarounds reference Windows tools (e.g., robocopy, Explorer), PowerShell commands, and Windows-specific procedures (e.g., RDP, Windows services). In some cases, only Windows command-line or UI paths are given, with no equivalent Linux instructions. Linux is mentioned in a few examples (e.g., NFS client on Ubuntu), but parity is lacking, and Windows approaches are often presented first or exclusively.

Recommendations:

For every Windows-specific tool or command (e.g., robocopy, Explorer, PowerShell), provide equivalent Linux/macOS alternatives (e.g., rsync, cp, bash commands).
When giving example commands (such as mounting NFS shares), include both Windows and Linux syntax, and clarify which OS each applies to.
If referencing Windows services or processes (e.g., waappagent.exe, rdagent), note the equivalent Linux service management steps if applicable, or clarify if not relevant.
Avoid using Windows UI navigation (e.g., Explorer) as the only example; add CLI and Linux desktop equivalents.
Ensure that troubleshooting steps and workarounds are provided for both Windows and Linux environments where possible.
Where PowerShell is referenced, also provide bash or shell command equivalents for Linux.
Audit for any implicit assumptions that the user is on Windows, and update language to be OS-neutral or inclusive.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas: Windows-specific tools and commands (e.g., robocopy, Explorer, PowerShell, RDP) are referenced without Linux equivalents, and Windows workflows are described in detail while Linux alternatives are missing or underexplained. In several examples, Windows commands are given first or exclusively, and Linux command-line or tool alternatives are not provided. This may hinder Linux users' ability to follow the documentation effectively.

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, etc.).
When giving command-line examples (such as mounting NFS shares), provide both Windows and Linux syntax, and present them in parallel or in a neutral order.
Where PowerShell commands are referenced, include Bash or shell script equivalents for Linux environments.
Explicitly mention and document Linux client workflows for tasks like connecting to SQL databases, managing VMs, and interacting with the device.
Review all workaround steps and ensure Linux users are not left without clear, actionable instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a moderate Windows bias. Several examples and workarounds reference Windows tools (e.g., robocopy, Explorer, RDP), PowerShell commands, and Windows-specific procedures before or instead of Linux equivalents. In some cases, Linux alternatives are missing or less detailed, and Windows-centric terminology is used in mixed environments.

Recommendations:

Provide Linux equivalents for all Windows-specific tools and commands (e.g., suggest rsync/cp instead of only robocopy/Explorer, include Linux command-line examples for mounting NFS shares).
When giving command-line examples (such as for sqlcmd or mounting NFS), show both Windows and Linux syntax side by side.
Avoid referencing only Windows-specific management tools (e.g., RDP, PowerShell) without mentioning SSH or Linux-native alternatives.
Ensure that troubleshooting steps and workarounds are equally detailed for both Windows and Linux environments.
Review all examples and ensure Linux-first or at least parallel presentation where appropriate, especially in cross-platform scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a moderate Windows bias. Several examples and workarounds reference Windows tools and workflows (e.g., robocopy, Explorer, PowerShell, RDP), and some examples use Windows-style paths or commands without providing Linux equivalents. In some cases, only Windows-specific troubleshooting steps are detailed, and Linux alternatives are omitted or less prominent.

Recommendations:

For every Windows-specific tool or command mentioned (e.g., robocopy, Explorer, PowerShell), provide equivalent Linux commands (e.g., rsync, cp, bash shell, SSH).
When showing mount examples, include both Windows (e.g., net use, Explorer) and Linux (e.g., mount command in bash) syntax.
If troubleshooting steps involve Windows-only tools (e.g., RDP, PowerShell), add parallel instructions for Linux users (e.g., SSH, bash commands).
Avoid using only Windows paths (e.g., C:\Users\...) in examples; show Linux paths (/home/user/...) as well.
Explicitly call out when a workaround or feature is platform-specific, and provide alternatives or note limitations for the other platform.
Review all examples and ensure Linux parity in documentation, especially for common administrative and troubleshooting tasks.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Several workarounds and instructions reference Windows-specific tools (PowerShell, RDP, Windows services, robocopy, Explorer), and some examples are shown only for Windows (e.g., mounting NFS shares from Windows paths, using PowerShell to restart nodepool VMs, and troubleshooting Windows VM Guest Agent). Linux equivalents are rarely mentioned or are only referenced indirectly. In some cases, Linux is mentioned as an afterthought or only in the context of running a Linux VM, not as a first-class management or troubleshooting environment.

Recommendations:

For every Windows-specific workaround or example (e.g., PowerShell commands, robocopy, Explorer, RDP), provide equivalent Linux commands and workflows (e.g., SSH, systemctl, cp/rsync, Linux mount commands).
When referencing mounting NFS shares, include both Windows and Linux mount examples side by side.
If troubleshooting steps are given for Windows VMs (e.g., using RDP, Windows services), provide parallel steps for Linux VMs (e.g., SSH, systemctl, journalctl).
When suggesting tools like robocopy or Explorer, also mention Linux tools such as rsync, cp, or Midnight Commander.
Instruct users on how to connect to the device via SSH or Linux shell, not just via PowerShell.
Review the order of examples and ensure Linux is not always secondary to Windows; alternate or present both equally.
Explicitly mention Linux support and provide links to Linux-specific documentation where available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several areas: Windows tools and interfaces (such as PowerShell, RDP, and Windows-specific commands) are mentioned or used in examples, sometimes without Linux equivalents. In some cases, only Windows command-line examples are given (e.g., mounting NFS shares), and workarounds reference Windows tools (e.g., robocopy, Explorer) or PowerShell interfaces. Linux alternatives are either missing or not given equal prominence.

Recommendations:

For every Windows-specific tool or command (e.g., robocopy, Explorer, PowerShell), provide Linux equivalents (e.g., rsync, cp, bash shell, SSH).
When giving command-line examples (such as mounting NFS shares), include both Windows and Linux syntax, and present them with equal prominence.
If referencing connecting to the device via PowerShell, also describe how to connect via SSH or other Linux-native methods.
Where workarounds or procedures involve Windows-only utilities, add parallel instructions for Linux users.
Review all troubleshooting and workaround steps to ensure Linux users are not left without guidance.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits several signs of Windows bias. Windows-specific tools and workflows (e.g., robocopy, Explorer, PowerShell, RDP, Windows VM Guest Agent) are referenced without Linux equivalents or alternatives. Example commands and workarounds are often given for Windows environments (e.g., mounting NFS shares with Windows paths, using robocopy), while Linux commands or tools are either missing or mentioned only after Windows. PowerShell and Windows-centric troubleshooting steps are detailed, but Linux-based approaches are not provided, even when relevant (e.g., custom script VM extension, NFS mounting).

Recommendations:

For every Windows-specific tool or command mentioned (e.g., robocopy, Explorer, PowerShell), provide equivalent Linux alternatives (e.g., rsync, cp, bash commands).
When giving example commands (such as mounting NFS shares), include both Windows and Linux syntax, and present them in parallel or alternate order.
If troubleshooting steps are provided for Windows VMs (e.g., using RDP, PowerShell), also include steps for Linux VMs (e.g., SSH, systemctl, relevant Linux services).
Avoid assuming the user is on a Windows client; clarify when instructions are OS-specific and provide cross-platform guidance.
Review all workarounds and ensure Linux users are not left without actionable steps, especially for common scenarios like file copying, mounting, and command-line utilities.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas: Windows tools and workflows (e.g., robocopy, Explorer, command line with Windows paths, RDP, PowerShell commands) are mentioned or exemplified, often without Linux equivalents. In some cases, only Windows-specific instructions or examples are provided, and Linux alternatives are omitted or not given equal prominence.

Recommendations:

For every Windows-specific tool or command mentioned (e.g., robocopy, Explorer, PowerShell, RDP), provide equivalent Linux commands or workflows (e.g., rsync, cp/mv, SSH, Linux shell commands).
When giving example commands (such as mounting NFS shares), include both Windows and Linux syntax side by side.
If referencing Windows utilities (like sqlcmd), clarify cross-platform availability or provide installation instructions for Linux/macOS.
Avoid using Windows paths (e.g., C:\Users\...) exclusively; show Linux paths (e.g., /home/user/...) as well.
When troubleshooting or giving workarounds, ensure both Windows and Linux environments are addressed where applicable.
Review all sections for implicit assumptions of a Windows environment and add Linux parity where missing.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several areas: Windows tools and interfaces (such as PowerShell, robocopy, Windows Explorer, and RDP) are referenced or used in examples, sometimes without Linux equivalents. In some cases, only Windows command examples are provided, or Windows-specific workarounds are described before (or instead of) Linux alternatives. Linux tools and workflows are sometimes omitted or mentioned only as an afterthought.

Recommendations:

For every example or workaround involving Windows tools (e.g., robocopy, Windows Explorer, PowerShell), provide equivalent Linux commands (e.g., rsync, cp, bash commands, SSH).
When referencing connecting to the device interface (e.g., PowerShell), also describe how to connect from Linux (e.g., SSH, Bash).
In tables or lists where Windows and Linux clients are both relevant, present both options side by side, or alternate which is presented first.
For SQL command-line tools, mention Linux installation and usage of sqlcmd, not just Windows.
Avoid using only Windows path formats (e.g., C:\Users\...) in mount examples; provide Linux mount command equivalents.
Where Windows-specific issues are described, clarify if similar issues exist or do not exist for Linux VMs.
Audit all examples and instructions to ensure Linux users are equally supported and not left to infer the correct approach.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by listing Windows operating systems and tools before Linux equivalents, providing detailed requirements for Windows (including PowerShell, .NET, BitLocker), and referencing Windows-specific tools without equivalent Linux usage examples or guidance. Linux requirements are mentioned, but with less detail and no example commands or workflows. There are no Linux command-line examples or step-by-step parity with Windows instructions.

Recommendations:

Present Linux and Windows operating systems and requirements in parallel, rather than listing Windows first.
Provide example commands and workflows for both Windows (e.g., PowerShell) and Linux (e.g., bash, shell scripts) for common tasks such as disk unlocking and data copy.
List required Linux tools with the same level of detail as Windows tools, and explain their installation and usage.
Include troubleshooting and validation steps for Linux environments, not just Windows.
Where Windows-specific tools (e.g., PowerShell, BitLocker) are mentioned, provide Linux equivalents (e.g., dislocker, cryptsetup) and usage notes.
Ensure that all tables and sections have Linux and Windows content side-by-side to reinforce parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias through the frequent use of PowerShell cmdlets and interfaces for management tasks, explicit references to Windows tools (e.g., robocopy, Explorer), and examples that assume a Windows environment (such as mounting NFS shares from Windows paths and using Windows command syntax). There is a lack of equivalent Linux command examples or guidance, and Linux tools or workflows are rarely mentioned, if at all. In some cases, Linux is only referenced as a workaround or alternative, not as a first-class platform.

Recommendations:

Provide Linux CLI/bash equivalents for all PowerShell and Windows command examples (e.g., show how to check VM status or restart VMs using SSH and virsh or similar tools).
When referencing tools like robocopy or Explorer, also mention Linux alternatives such as rsync, cp, or scp.
For NFS mount instructions, include Linux mount command examples alongside Windows ones.
Where PowerShell is mentioned as an interface, clarify if SSH or other Linux-native management options are available and provide links or instructions.
Review all troubleshooting and workaround steps to ensure Linux users are equally supported with relevant commands and procedures.
Adopt a platform-neutral or parallel documentation style, presenting Windows and Linux options side by side.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides detailed troubleshooting steps for Linux users in the first section, but in the Split Copy tool errors section, it references Windows-specific tools (e.g., 'diskmgmt.msc') without mentioning Linux equivalents or providing Linux-specific guidance. The error table assumes a Windows environment and does not offer parallel Linux instructions, which may leave Linux users without clear solutions for those scenarios.

Recommendations:

For each tool or command mentioned (such as 'diskmgmt.msc'), provide Linux equivalents (e.g., 'lsblk', 'fdisk', 'gnome-disks', or 'udisksctl') and instructions for bringing disks online in Linux.
Ensure that error messages and troubleshooting steps are accompanied by both Windows and Linux solutions, or clearly indicate when a tool is Windows-only and suggest alternatives for Linux.
Add Linux-specific examples and commands for all common operations, especially in sections currently focused on Windows tools or workflows.
Review the error table to include Linux-relevant error messages and their resolutions, or clarify which errors are platform-specific.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. Several examples and workarounds reference Windows-specific tools (e.g., robocopy, Explorer, PowerShell, Windows VM Guest Agent), and provide command-line examples or instructions only for Windows environments. In some cases, Linux alternatives are missing or only mentioned secondarily. There are also multiple references to connecting via PowerShell and using Windows cmdlets, with no equivalent Linux/bash instructions provided.

Recommendations:

For every Windows-specific tool or command (e.g., robocopy, Explorer, PowerShell cmdlets), provide equivalent Linux alternatives (e.g., rsync, cp, bash commands).
When giving command-line examples, include both Windows and Linux syntax side by side.
Mention Linux tools and patterns before or alongside Windows ones to avoid 'Windows-first' ordering.
For troubleshooting steps involving Windows VMs or PowerShell, add parallel instructions for Linux VMs or SSH-based management where applicable.
Review all examples and ensure Linux users have clear, actionable guidance for all scenarios.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. Several workarounds and instructions reference Windows-specific tools (e.g., robocopy, Explorer, PowerShell, RDP), and Windows command-line examples are provided without equivalent Linux commands. In some cases, Windows tools or patterns are mentioned first or exclusively, and Linux alternatives are missing or only referenced indirectly. While there are some Linux mentions (e.g., ssh, NFS, Linux VM for IoT Edge), parity in examples and instructions is lacking.

Recommendations:

Provide Linux command-line equivalents for all Windows examples (e.g., show both robocopy and rsync/cp for file copy operations).
When referencing PowerShell or Windows-specific tools, also include Linux/Unix alternatives (e.g., bash, systemctl, journalctl).
Avoid mentioning Windows tools or patterns first unless they are more common for the audience; instead, present both Windows and Linux options together.
For troubleshooting steps that use Windows tools (e.g., RDP, PowerShell cmdlets), provide SSH and Linux-native command alternatives.
Where possible, add explicit Linux examples for VM management, certificate handling, and network troubleshooting.
Review all workaround and example sections to ensure Linux users are equally supported and not required to infer steps from Windows instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows terminology and tools, providing detailed instructions and validation scripts only for Windows, and lacking equivalent Linux-specific examples or guidance. The unlock and validation steps reference Windows tools (e.g., .cmd scripts, BitLocker dialogs) without offering Linux alternatives or parity.

Recommendations:

Provide explicit Linux command-line examples for unlocking disks, copying data, and validating files, alongside the Windows instructions.
Document the availability and usage of the Data Box Disk unlock tool for Linux, including installation and execution steps.
Offer Linux-compatible validation scripts or instructions, or clarify if the provided .cmd script is cross-platform or provide a shell script alternative.
Mention Linux-specific considerations (e.g., mount commands, file system compatibility, safe removal procedures) where relevant.
Ensure that any references to Windows tools (such as BitLocker dialogs) are matched with Linux equivalents or clear guidance for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a moderate Windows bias. Several examples and workarounds reference Windows tools (e.g., robocopy, Explorer, PowerShell cmdlets), provide Windows command syntax before or instead of Linux equivalents, and sometimes omit Linux-specific instructions. In some cases, only Windows remediation steps are detailed, and Linux alternatives are not mentioned or are less prominent.

Recommendations:

For every Windows-specific tool or command (e.g., robocopy, Explorer, PowerShell cmdlets), provide equivalent Linux commands (e.g., rsync, cp, bash commands) alongside.
When showing mount commands or file copy examples, include both Windows and Linux syntax, and do not default to Windows paths or commands.
If a workaround or remediation is described for Windows (e.g., using PowerShell to manage VMs), provide parallel steps for Linux environments (e.g., SSH and relevant Linux commands).
Ensure that troubleshooting steps and examples are balanced, with Linux and Windows instructions given equal prominence and detail.
Where third-party tools are referenced (e.g., SQL command utility), clarify cross-platform availability and usage, and provide installation/use instructions for both Windows and Linux.
Review all examples and tables for implicit prioritization of Windows workflows, and adjust ordering or content to reflect cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several areas: Windows tools and commands (such as PowerShell cmdlets, robocopy, and Windows-specific troubleshooting steps) are referenced without equivalent Linux examples or alternatives. In some cases, Windows paths and commands are shown first or exclusively, and Linux alternatives are missing or only briefly mentioned. This may hinder Linux users from effectively following the documentation.

Recommendations:

For every Windows-specific tool or command (e.g., robocopy, PowerShell cmdlets), provide equivalent Linux commands (e.g., rsync, cp, systemctl, ps).
When giving examples of mounting NFS shares, include both Windows and Linux syntax side by side.
For troubleshooting steps involving Windows VMs or services, add parallel instructions for Linux VMs where applicable.
Avoid referencing Windows tools or patterns (such as Explorer, RDP, robocopy) exclusively; always mention or link to Linux alternatives.
Where PowerShell is used to interact with the device, include Bash or SSH-based alternatives for Linux users.
Review all examples and ensure Linux users are not left without clear, actionable 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 Windows tools and patterns (such as exporting PFX from Windows 10/Server 2016), recommending the Microsoft RSA/Schannel Cryptographic Provider (Windows-specific), and providing next steps only for Azure PowerShell and the Azure Stack Hub Readiness Checker tool (both Windows-centric). There are no Linux or cross-platform certificate management examples or guidance, and Linux-compatible tools or methods are not mentioned.

Recommendations:

Include equivalent Linux/OpenSSL commands and workflows for exporting and managing PFX certificates.
Mention cross-platform cryptographic providers or clarify if non-Windows providers are supported.
Provide next steps or links for certificate creation and export using Linux tools (e.g., OpenSSL) alongside PowerShell.
Clarify whether the Azure Stack Hub Readiness Checker tool is available or has alternatives for Linux/macOS.
Ensure that references to Windows-specific defaults (like 3DES encryption) are accompanied by Linux/OpenSSL equivalents or instructions.

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 workflows, error messages, and resolutions are written exclusively for Windows environments. Only Windows-specific tools (e.g., BitLocker, Windows PowerShell) are mentioned, and there are no examples, instructions, or troubleshooting steps for Linux or other operating systems. The unlock tool usage, error messages, and resolutions assume a Windows client, with no parity for Linux users.

Recommendations:

Add troubleshooting sections specifically for Linux clients, including common errors and their resolutions.
Provide unlock tool usage examples for Linux, including command-line syntax and expected outputs.
Mention Linux equivalents for tools (e.g., how to unlock encrypted drives using Linux utilities such as cryptsetup or dislocker if supported).
Clarify OS compatibility for the Data Box Disk Unlock tool and provide download/installation instructions for Linux if available.
Ensure that error messages and logs are explained for both Windows and Linux environments.
If Linux is not supported, explicitly state this early in the documentation to set user expectations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell and Windows-centric tools for certificate creation and management. Instructions and links for certificate generation use PowerShell or Windows-based tools, with no mention of Linux or cross-platform alternatives. Some verification steps (e.g., right-clicking a certificate and using the Details tab) assume a Windows GUI environment. There are no Linux command-line examples or references to Linux-native certificate management tools.

Recommendations:

Provide equivalent Linux-based instructions for certificate creation, such as using OpenSSL commands for generating and exporting certificates.
Include examples and links for certificate management on Linux clients, not just Windows/PowerShell.
When referencing tools (e.g., Readiness Checker, PowerShell), clarify if they are cross-platform or provide Linux alternatives.
For certificate verification steps, include Linux methods (e.g., using openssl x509 -text -in cert.pem) alongside Windows GUI instructions.
Review all linked articles to ensure Linux parity in step-by-step guides and tool recommendations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows Server Failover Clustering concepts and terminology, with no mention of Linux-based clustering solutions or examples. All technical explanations, requirements, and setup instructions assume a Windows environment (e.g., SMB file shares, Windows Server clustering), and there are no Linux equivalents or cross-platform considerations provided.

Recommendations:

Include references to Linux-based clustering solutions (e.g., Pacemaker, Corosync) and how quorum/witness concepts apply in those environments.
Provide Linux-specific examples for setting up a cluster witness, such as using NFS shares or other Linux-supported mechanisms.
Clarify whether Azure Stack Edge supports only Windows-based clustering or if Linux-based clusters are also supported, and document accordingly.
If the product is Windows-only, explicitly state this limitation early in the documentation to set expectations.
If cross-platform support exists, provide parity in setup and configuration instructions for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. It exclusively references Windows Server Failover Clustering as the clustering technology, repeatedly links to Windows Server documentation, and describes clustering concepts in Windows-centric terms. There are no Linux-based clustering options, tools, or examples mentioned, nor are any Linux command-line or management approaches referenced. Cluster management is described via PowerShell and the local UI, with no mention of Linux CLI or tools.

Recommendations:

Acknowledge in the introduction that clustering on Azure Stack Edge is based on Windows Server Failover Clustering, and clarify if Linux-based clustering is supported or not.
If Linux-based clustering is not supported, explicitly state this to set expectations for Linux users.
If Linux-based clustering or management is possible, provide equivalent Linux examples, tools, and references (e.g., Pacemaker, Corosync, Linux CLI commands).
When describing management interfaces, mention whether Linux-based management (e.g., SSH, Linux CLI) is available or not.
In sections referencing PowerShell or Windows tools, provide Linux alternatives or clarify their absence.
Consider including a comparison table or FAQ addressing platform support and management options for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. All certificate import instructions and screenshots are exclusively for Windows, with no mention of Linux or macOS workflows. PowerShell and Windows-specific tools (e.g., Chocolatey) are referenced for installing and using openssl, and all command-line examples are shown in PowerShell with Windows file paths. There are no Linux or cross-platform instructions for certificate management, despite openssl being a cross-platform tool.

Recommendations:

Add parallel instructions and screenshots for Linux (and optionally macOS) users, especially for importing certificates into system stores.
Provide openssl installation steps for Linux (e.g., using apt, yum, or other package managers) alongside the Chocolatey/Windows instructions.
Show command-line examples using bash or generic shell syntax, not just PowerShell, and use platform-neutral file paths where possible.
Clarify in each section whether the steps apply to Windows only or if there are alternative steps for other operating systems.
Reference Linux certificate stores (such as /etc/ssl/certs or update-ca-certificates) and provide guidance for importing certificates on Linux clients.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based instructions and commands for collecting VM guest logs, without offering equivalent Linux shell or cross-platform alternatives. The log collection process relies on PowerShell cmdlets, and there are no examples or guidance for users who may be managing the device from a Linux or macOS environment. While log file locations for both Linux and Windows VMs are mentioned, the actual collection workflow is Windows-centric.

Recommendations:

Provide equivalent Linux shell (bash) commands or scripts for collecting VM guest logs, or clarify if the process is only supported via PowerShell.
Mention and document any cross-platform tools (such as Azure CLI or REST API) that can be used for log collection, if available.
If PowerShell is required, specify whether PowerShell Core (which is cross-platform) can be used on Linux/macOS, and provide installation or usage instructions.
Ensure that examples and instructions are presented for both Windows and Linux environments, or explicitly state platform limitations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses Windows PowerShell cmdlets and tools for configuring MetalLB via BGP on Azure Stack Edge, with no mention or examples of Linux-based workflows or CLI equivalents. All configuration steps and example outputs are Windows/PowerShell-centric, and there is no guidance for users operating from a Linux environment.

Recommendations:

Provide equivalent Linux command-line instructions (e.g., using SSH, kubectl, or Linux networking tools) for configuring MetalLB and BGP.
Include examples of how to connect to the device and perform necessary configuration steps from a Linux or cross-platform shell.
Mention any platform-specific limitations or requirements up front, and clarify if configuration is only possible via Windows tools.
If PowerShell is required, note the availability of cross-platform PowerShell Core and provide examples for both Windows and Linux environments.
Add troubleshooting and verification steps that can be performed from Linux systems.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by centering the workflow around PowerShell (even for Linux/macOS clients), presenting Windows Remote Desktop instructions before Linux alternatives, and using Windows-centric tools and patterns throughout. Linux instructions are present but less detailed and positioned after Windows examples.

Recommendations:

Provide equal prominence and detail for Linux workflows, including step-by-step instructions for using FreeRDP and other Linux-compatible RDP clients.
Include example commands and outputs for Linux/macOS terminals, not just PowerShell.
Clarify any differences or prerequisites for Linux/macOS users (e.g., how to install and use PowerShell 7 on Linux, or alternative ways to connect if PowerShell is not preferred).
Present Windows and Linux/macOS instructions in parallel sections or side-by-side, rather than always listing Windows first.
Mention and link to alternative Linux-native tools where applicable, and provide troubleshooting tips specific to non-Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows, providing only Windows PowerShell examples and instructions for certificate creation. There are no Linux or cross-platform alternatives mentioned, and all tooling and workflows assume a Windows environment. The use of Windows-specific tools (PowerShell, Cert:\ store) is exclusive, and Linux users are not given guidance or parity in the documentation.

Recommendations:

Add equivalent Linux examples using OpenSSL for certificate creation, including step-by-step commands.
Mention cross-platform tools (e.g., Azure CLI, OpenSSL) and provide guidance for both Windows and Linux users.
Clearly indicate which steps are Windows-specific and offer alternative instructions for Linux/macOS environments.
Include a section or note at the start highlighting cross-platform options and linking to relevant Linux/macOS documentation.
Avoid assuming the user is on Windows; use neutral language and provide parallel workflows where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows environments. All instructions, examples, and screenshots assume the use of Windows clients, Windows PowerShell (specifically version 5.1), and Windows-specific tools (e.g., Notepad, hosts file at C:\Windows\System32\Drivers\etc). There are no examples or guidance for Linux or macOS users, despite PowerShell Core being cross-platform. Steps for certificate management, environment setup, and connectivity verification are all Windows-centric, and there is no mention of equivalent Linux commands, file paths, or tools.

Recommendations:

Add parallel instructions and examples for Linux (and optionally macOS) clients, including PowerShell Core usage.
Provide Linux-specific commands for editing the hosts file (e.g., using nano or vi to edit /etc/hosts) and verifying DNS resolution (e.g., using ping, dig, or host).
Include guidance on importing certificates into Linux certificate stores (e.g., update-ca-certificates, certutil, or relevant distro-specific tools).
Clarify which steps are Windows-only and which are cross-platform, and provide clear alternatives where possible.
Update screenshots and file paths to include Linux equivalents.
Explicitly state PowerShell Core support and provide installation/usage instructions for non-Windows platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation exhibits a Windows-first bias: Windows terminology, tools, and privileges (e.g., SeBackupPrivilege, Administrator/Backup Operators groups) are referenced in detail, while Linux equivalents are either omitted or only briefly mentioned. Linux-specific behaviors are described as exceptions or limitations (e.g., only Windows NT ACLs transferred, default ACLs not transferred on Linux), and there are no Linux command examples or tool recommendations. The documentation assumes familiarity with Windows security concepts and does not provide parity for Linux users.

Recommendations:

Provide explicit Linux tool examples (e.g., using smbclient, rsync, or cp with appropriate flags) for copying data and preserving metadata.
Include Linux privilege requirements and equivalents to Windows concepts like SeBackupPrivilege (e.g., root or specific capabilities needed).
Clarify what 'Windows NT ACLs' means in the context of Linux clients and how Linux users can verify or manage these ACLs.
Add a section or table comparing Windows and Linux behaviors and limitations side-by-side for clarity.
Ensure that Linux workflows are described with the same level of detail as Windows, including troubleshooting tips and error messages relevant to Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows, requiring a Windows 10 or Windows Server client and providing only PowerShell-based instructions and examples. There are no Linux or cross-platform alternatives mentioned for any step, and all file paths and tooling references are Windows-specific. The Azure Stack Hub Readiness Checker tool is distributed via the PowerShell Gallery, further reinforcing the Windows-centric approach.

Recommendations:

Provide equivalent instructions for Linux users, including supported distributions and prerequisites.
If the Azure Stack Hub Readiness Checker tool is not available for Linux, clearly state this limitation and suggest alternative methods for Linux users (e.g., using OpenSSL for CSR generation).
Include Bash or cross-platform CLI examples alongside PowerShell commands where possible.
Use platform-agnostic language and file paths in documentation, or provide both Windows and Linux/Mac examples.
Clarify whether the tool can be run via PowerShell Core on Linux/macOS, and provide installation steps if supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing PowerShell for device access and GPU monitoring (e.g., 'connect to the PowerShell interface', 'Get-HcsNvidiaSmi' command), without providing equivalent Linux shell or command-line examples. There is no mention of standard Linux tools or workflows for GPU management, and all operational instructions assume a Windows-centric environment.

Recommendations:

Provide equivalent Linux shell commands for GPU monitoring (e.g., using 'nvidia-smi' directly in bash).
Include instructions for accessing the device via SSH or Linux terminal, not just PowerShell.
Mention and demonstrate Linux-native tools and workflows for GPU management alongside Windows/PowerShell examples.
Ensure that examples and instructions are presented in a platform-neutral way, or provide both Windows and Linux variants side-by-side.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily through the exclusive mention of PowerShell cmdlets (e.g., Set-HcsMacAddressPool) for device configuration, without providing equivalent Linux/CLI commands or guidance. There are no Linux shell or cross-platform examples for device management, and the only explicit command-line example is Windows-specific. Additionally, the documentation refers to the PowerShell interface as the means to interact with the device, with no mention of Linux alternatives or parity.

Recommendations:

Provide equivalent Linux shell (bash) or cross-platform CLI commands for all PowerShell cmdlets mentioned, or clarify if such alternatives are unavailable.
Explicitly state whether device management and configuration can be performed from Linux hosts, and if so, document the supported tools and workflows.
Where only Windows tools or patterns are available, acknowledge the limitation and provide guidance or workarounds for Linux users.
Ensure that all command-line examples are presented in both PowerShell and bash (or other relevant shells) where possible.
Review all references to management interfaces to ensure Linux users are not excluded or left without clear instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows instructions and tools (such as PowerShell and Windows command prompt) are presented first and in more detail, while Linux instructions are present but less emphasized. The AzCopy usage section and sample output are shown only in a Windows/PowerShell context, with no explicit Linux shell examples. The download and upload steps reference Windows paths and tools, and the sample output is from a Windows PowerShell session. There is also a lack of parity in showing Linux command-line equivalents for AzCopy and related tasks.

Recommendations:

Provide Linux shell (bash) examples alongside PowerShell/Windows examples for all command-line operations, especially for AzCopy usage.
Include sample output from Linux environments (e.g., bash shell) to demonstrate parity.
Avoid presenting Windows instructions and tools first by default; alternate or present both OSes in parallel tabs or sections.
Explicitly mention Linux tools or methods where relevant (e.g., using AzCopy on Linux, or alternative upload/download methods).
Ensure that all steps referencing file paths or command prompts include Linux equivalents (e.g., ~/azcopy/ or /usr/local/bin/azcopy).
Where possible, use OS-agnostic language and screenshots, or provide both Windows and Linux visuals.

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, where only Windows-specific instructions and PowerShell commands are provided for using the step CLI. There are no equivalent Linux or macOS command-line examples, and the instructions reference opening a Command Prompt and using Windows environment variables. The .NET code sample also assumes usage in Visual Studio, a Windows-centric IDE, without mentioning cross-platform alternatives.

Recommendations:

Provide explicit Linux and macOS command-line examples for generating certificates with the step CLI, including terminal commands and file paths.
Avoid referencing Windows-specific actions (e.g., 'Win+R type %USERPROFILE%') without cross-platform equivalents; instead, mention generic terminal navigation or provide alternatives for different OSes.
Include instructions for running the .NET sample on Linux/macOS (e.g., using VS Code, JetBrains Rider, or the dotnet CLI) and clarify that the code is cross-platform.
Where file paths are referenced, use cross-platform path examples or note the differences.
If referencing IDEs or tools, mention cross-platform options and not just Visual Studio.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a significant Windows bias. While the initial steps use Azure CLI (which is cross-platform), all variable assignments and command examples are written in PowerShell syntax (e.g., $var = ...), and the output is shown from a PowerShell prompt (PS /home/user>). The VHD export process relies on Azure PowerShell cmdlets (New-AzureStorageContext, Start-AzureStorageBlobCopy, Get-AzureStorageBlobCopyState), which are not available or standard on Linux/macOS. There are no equivalent Bash or Linux-native examples provided, and the documentation assumes a Windows/PowerShell environment throughout, despite referencing Azure CLI.

Recommendations:

Provide equivalent Bash/Linux shell examples for all steps, especially for variable assignment and command execution.
For the VHD export step, include az storage blob copy or azcopy examples, which are cross-platform and work natively on Linux/macOS.
Avoid using PowerShell-specific cmdlets (e.g., New-AzureStorageContext) as the only option; if PowerShell is shown, always pair with a Bash/Linux alternative.
Show output from both PowerShell and Bash shells, or use a neutral prompt (e.g., $ or >) to avoid implying Windows-only usage.
Explicitly state that the workflow can be performed on Linux/macOS, and provide any prerequisites or differences for those platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by referencing Windows-specific tools (such as WSUS and the default use of the public Windows update server) and omitting Linux equivalents or cross-platform alternatives. There are no explicit Linux or macOS instructions or examples for tasks such as network configuration, proxy setup, or update server configuration. The documentation assumes familiarity with Windows environments and tools, and does not provide parity for Linux users.

Recommendations:

Include instructions for configuring update servers on Linux (e.g., using local Linux-based update mirrors or repositories) alongside WSUS/Windows Update references.
Mention and provide examples for network configuration on Linux and macOS (e.g., how to change IPv4 settings, set static IPs, configure NTP, etc.).
If referencing tools like the Azure Stack Network Readiness Checker or Network Readiness Tool, clarify their cross-platform compatibility or provide Linux/macOS alternatives if available.
When discussing proxy or firewall settings, include command-line examples for both Windows (e.g., PowerShell, netsh) and Linux (e.g., iptables, systemd-resolved, environment variables).
Avoid defaulting to Windows terminology (e.g., 'public Windows update server') and instead use neutral or cross-platform language, or explicitly call out options for different operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting Windows/SMB connection steps and tools (e.g., Notepad, Windows Explorer, File Explorer, 'net use' command) first and in greater detail, while Linux/NFS instructions are provided later and with less visual support. The host file modification example is exclusively for Windows, with no explicit Linux equivalent. Visuals and step-by-step instructions are Windows-centric, and Linux users are expected to infer or adapt steps.

Recommendations:

Provide parallel Linux examples for all steps, including host file modification (e.g., editing /etc/hosts with nano or vi).
Include screenshots or terminal output for Linux steps, similar to the Windows visuals.
Present SMB (Windows) and NFS (Linux) instructions in parallel sections, or alternate which platform is described first.
Mention Linux tools and commands explicitly (e.g., using 'mount', 'nano', 'vi', 'cat') wherever Windows tools are referenced.
Clarify any platform-specific caveats or differences in both directions, not just for Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell cmdlets and sample outputs from a Windows environment (e.g., 'PS C:\windows\system32>'). It references Windows-specific tools and file formats (e.g., Azure PowerShell, .cer files, Storage Explorer UI steps for Windows), and does not provide equivalent Linux/Unix command-line instructions or examples. There is no mention of Linux tools, shell commands, or how to perform these tasks on non-Windows platforms.

Recommendations:

Provide equivalent command-line examples using Azure CLI (az) for Linux/macOS users alongside PowerShell examples.
Include sample outputs and instructions for running commands in Bash or other Unix shells.
Document how to obtain storage account keys and connect to the device using cross-platform tools, not just PowerShell.
Clarify file format differences and import steps for certificates on Linux/macOS (e.g., PEM, .crt, .pfx handling).
Ensure Storage Explorer instructions are not Windows-specific and mention Linux/macOS installation and usage where applicable.
Where screenshots or UI steps are given, provide notes for cross-platform differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias by presenting Windows/SMB connection instructions and tools (e.g., 'net use', File Explorer) in greater detail and before Linux/NFS instructions. Windows-specific commands and UI steps are described with screenshots and explicit step-by-step guidance, while Linux/NFS instructions are more concise and lack comparable detail. There is also a reliance on Windows command-line tools and patterns (e.g., 'net use', File Explorer), with no mention of Linux equivalents for browsing shares or copying files.

Recommendations:

Provide Linux/NFS instructions with the same level of detail as Windows/SMB, including screenshots and step-by-step guidance for mounting and browsing shares.
Include Linux command-line examples for copying files (e.g., using 'cp', 'rsync', or 'scp') and for browsing mounted shares (e.g., using 'ls', 'nautilus', or other file managers).
Present Linux/NFS instructions before or alongside Windows/SMB instructions to avoid the appearance of prioritizing Windows.
Mention and demonstrate Linux tools for verifying share access and copying data, not just Windows tools.
Ensure parity in troubleshooting steps and error screenshots for both Windows and Linux scenarios.

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 Azure PowerShell and Windows Server Update Services), showing certificate download examples in Windows File Explorer, and omitting Linux or cross-platform command-line examples for certificate creation, conversion, or installation. There are no explicit instructions or screenshots for Linux or macOS users, nor are alternative tools or workflows mentioned.

Recommendations:

Provide equivalent Linux/macOS instructions and examples for creating, converting, and installing certificates (e.g., using OpenSSL, Linux certificate stores, or CLI tools).
Include screenshots or terminal commands showing certificate handling on Linux and macOS, not just Windows File Explorer.
Mention cross-platform tools (such as Azure CLI, OpenSSL, or platform-agnostic certificate import methods) alongside or before Windows-specific tools.
Clarify that the steps are applicable to all supported client OSes, and provide links or references to OS-specific certificate management documentation.
When referencing tools like Azure PowerShell or WSUS, also mention their Linux/macOS equivalents or alternatives, if available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page shows a Windows bias by referencing the use of the PowerShell cmdlet `Set-HcsMacAddressPool` for configuring MAC addresses, without mentioning equivalent Linux commands or workflows. There are no Linux CLI examples or references to Linux tools for device configuration, and the only command-line example is specific to PowerShell.

Recommendations:

Provide equivalent Linux command-line instructions (e.g., using SSH and Linux shell commands) for configuring MAC addresses or other device settings.
Mention whether the device can be managed from Linux or cross-platform terminals, and if so, provide guidance or examples.
Clarify if PowerShell is required or if there are REST API or other cross-platform alternatives.
Ensure that all command-line examples are given for both Windows (PowerShell) and Linux (bash/CLI) where possible.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates Windows bias by exclusively referencing Windows-centric tools and services, such as Windows Server Update Services (WSUS) and time.windows.com as the default NTP server. There are no examples or mentions of Linux equivalents (e.g., Linux update servers, chrony/ntpd, or pool.ntp.org), nor are there instructions or screenshots relevant to Linux environments. The documentation assumes a Windows-based infrastructure for updates and time synchronization, and does not provide parity for Linux-based workflows.

Recommendations:

Include examples and instructions for configuring updates using Linux-based update servers (e.g., apt, yum, or custom HTTP/S update mirrors).
Mention and provide examples of using public or Linux-friendly NTP servers (e.g., pool.ntp.org) alongside time.windows.com.
Clarify that WSUS is a Windows-specific solution and suggest alternatives for environments that use Linux or mixed OS infrastructure.
Add notes or sections that address common Linux administration patterns and tools where relevant.
Ensure screenshots and step-by-step instructions are not exclusively tailored to Windows-centric setups.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific account names and log formats (e.g., 'WIN-DATABOXADMIN', 'NT AUTHORITY'), and by providing log samples and audit details that are clearly modeled after Windows Event Log output. There are no explicit Linux or cross-platform command-line examples, nor are Linux-specific audit or log formats discussed. The documentation assumes familiarity with Windows authentication and logging paradigms, and does not mention or illustrate Linux access, tools, or audit patterns.

Recommendations:

Include examples of accessing and interpreting Data Box logs from Linux systems, such as using Linux command-line tools (e.g., grep, less, tail) to view logs.
Provide sample audit log entries or authentication events as they would appear when accessed from Linux clients (e.g., via NFS or SMB mounts from Linux).
Clarify whether the Data Box supports Linux authentication mechanisms (e.g., mapping Linux users to SMB shares) and how such events are logged.
Add instructions or screenshots for tracking and downloading logs using Linux tools or from a Linux environment.
Ensure that any references to account names, domains, or logon types are explained in a cross-platform context, or provide Linux equivalents where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily biased towards Windows environments and PowerShell usage. Windows clients and PowerShell are assumed as the default throughout, with explicit instructions and examples provided only for Windows and PowerShell interfaces. There are no equivalent Linux or bash examples, and Linux/macOS client workflows are not described, despite the mention that other OSes are supported. All command-line examples use PowerShell syntax, and Windows tooling is referenced exclusively.

Recommendations:

Provide parallel instructions and examples for Linux/macOS clients, including bash/zsh shell commands.
Include az CLI and kubectl command examples in bash syntax, not just PowerShell.
Explicitly document how to connect to the device and run required commands from Linux/macOS clients.
Mention and demonstrate any differences in prerequisites or setup for non-Windows environments.
Avoid assuming Windows as the default client; structure the documentation to present both Windows and Linux/macOS workflows equally, or provide a clear OS selection at the start.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows environments. All command-line examples use PowerShell, and Windows-specific tools and paths (e.g., C:\ paths, PowerShell cmdlets) are used exclusively. There are no Linux shell (bash) equivalents or instructions for Linux/Mac users, even though tools like kubectl are cross-platform. The documentation assumes a Windows client and does not mention or demonstrate Linux alternatives for connecting, configuring, or managing the device.

Recommendations:

Provide Linux (bash) equivalents for all PowerShell commands, including kubectl usage, file path conventions, and environment setup.
Include instructions for saving kubeconfig files in Linux home directories (e.g., ~/.kube/config) and using Linux file paths.
Mention supported Linux distributions explicitly in the prerequisites and provide any OS-specific requirements.
Demonstrate how to connect to the device and run commands from a Linux terminal, including using SSH and bash.
Ensure that all screenshots and code snippets are either OS-neutral or have both Windows and Linux versions.
Clarify that the workflow is cross-platform and highlight any differences or limitations for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively providing PowerShell scripts and command examples, with no equivalent Bash or Linux shell instructions. All automation and CLI usage is shown in PowerShell syntax, which is native to Windows, and there is no mention of how to perform these steps on Linux or macOS environments. This may hinder accessibility for users on non-Windows platforms.

Recommendations:

Provide equivalent Bash shell scripts and command-line examples for Linux/macOS users alongside the PowerShell examples.
Explicitly mention cross-platform compatibility for all CLI commands, clarifying that Azure CLI and kubectl are available on Linux/macOS.
Where possible, use platform-agnostic scripting (e.g., Bash or plain Azure CLI commands) in mainline documentation, or offer both PowerShell and Bash versions.
Add a note or section addressing any platform-specific differences or prerequisites for Linux/macOS users.
Ensure that tool installation and usage instructions are not Windows-centric and reference Linux/macOS installation guides where appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a moderate Windows bias. It references Windows-specific clustering concepts (e.g., cluster witness, file share witness, cloud witness) and links to Windows Server documentation for NIC teaming and failover clustering. PowerShell is mentioned as the CLI method for changing Kubernetes workload profiles, with no mention of Bash or Linux CLI alternatives. The file share witness example uses Windows SMB path syntax. There are no explicit Linux or cross-platform command-line examples, and Windows tools/patterns are referenced before any Linux equivalents (which are absent).

Recommendations:

Provide Linux/Bash command-line alternatives alongside PowerShell instructions for tasks such as changing Kubernetes workload profiles.
Reference cross-platform or Linux-native clustering concepts and tools where possible, or clarify if only Windows-based clustering is supported.
When mentioning file share witness, include NFS-based or Linux-compatible file share examples, not just Windows SMB paths.
Avoid linking exclusively to Windows Server documentation for networking concepts like NIC teaming; include Linux equivalents (e.g., bonding, teaming) or clarify platform support.
Explicitly state platform limitations or support (e.g., if only Windows-based clustering is supported, clarify this up front).
Add notes or examples for users managing the device from Linux or macOS environments, especially for CLI-based configuration.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell and Windows-specific tools (e.g., Remove-AzureRmVMExtension cmdlet) are referenced exclusively for extension removal, with no equivalent Linux/CLI instructions. Troubleshooting and extension installation steps highlight Windows scenarios (e.g., TLS 1.2 on Windows 2016 VHD) and link to Windows-specific guidance before Linux. Linux examples are either deferred, less detailed, or referenced only as an afterthought (e.g., Red Hat GPU extension installation). There are no explicit Linux CLI or Azure CLI examples for common management tasks.

Recommendations:

Provide equivalent Azure CLI or Bash examples for all PowerShell commands, especially for tasks like removing VM extensions.
Ensure troubleshooting and installation steps for Linux are as detailed and prominent as those for Windows.
When referencing OS-specific requirements (e.g., TLS 1.2 for Windows 2016), also mention any Linux-specific prerequisites or considerations.
Present Linux and Windows instructions in parallel or in clearly separated tabs, rather than listing Windows first or exclusively.
Include explicit Linux/CLI guidance for common management tasks, not just portal-based workflows.

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 explicit references to Windows paths (e.g., C:\gpu-sharing\...), and all screenshots and outputs are from PowerShell sessions. There are no Linux shell (bash) equivalents, nor are there any references to Linux tools or terminal environments. The documentation assumes the use of Windows clients and PowerShell for all management tasks, and device management commands (e.g., Get-HcsGpuNvidiaSmi, Start-HcsGpuMPS) are only shown in PowerShell, with no mention of Linux alternatives or how to perform these tasks from a Linux client.

Recommendations:

Provide equivalent Linux shell (bash) command examples alongside PowerShell commands for all kubectl and file operations.
Include Linux path examples (e.g., /home/user/gpu-sharing/k8-gpusharing.yaml) in addition to Windows paths.
Clarify whether device management commands (e.g., Get-HcsGpuNvidiaSmi, Start-HcsGpuMPS) are available from Linux clients, and if so, provide Linux usage instructions.
If device management is only possible from Windows, explicitly state this limitation and suggest workarounds for Linux users (such as using a Windows VM or container).
Add screenshots or terminal outputs from Linux environments to balance the visual representation.
Update the prerequisites to explicitly mention supported Linux shells and tools, and provide guidance for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. It assumes the user is on a Windows client, provides only Windows PowerShell command-line examples, and uses Windows file paths (e.g., C:\Users\user). There are no equivalent Linux/macOS instructions, shell commands, or file path examples. Windows-specific tools and commands (such as New-HcsKubernetesNamespace) are referenced without Linux alternatives, and the documentation repeatedly refers to using a Windows client as the primary scenario.

Recommendations:

Provide parallel Linux/macOS instructions and examples for all steps, including shell command syntax and file paths (e.g., ~/user/.kube).
Include Linux/macOS command-line output samples alongside PowerShell examples.
Clarify which steps or tools are Windows-only and offer Linux/macOS alternatives where possible.
Reference cross-platform tools and commands first, or at least equally, rather than prioritizing Windows-specific tools.
Explicitly state any limitations or differences for non-Windows clients early in the prerequisites section.
Where Windows PowerShell commands are used (e.g., New-HcsKubernetesNamespace), document if/how these can be run from Linux/macOS, or provide REST API/CLI alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows bias by exclusively using PowerShell cmdlets (e.g., Add-HcsNetRoute, Get-HcsNetRoute, Remove-HcsNetRoute) for all network configuration tasks, with no mention of Linux command-line equivalents or cross-platform alternatives. The instructions assume access to a PowerShell interface and reference Windows-specific networking concepts (such as Hyper-V virtual switches and Switch Embedded Teaming), without providing guidance for users familiar with Linux networking tools or environments. There are no Linux or kubectl-based examples for managing routes or networking, and the documentation does not address how to perform these tasks if the Kubernetes nodes were running on Linux or in a more standard Kubernetes environment.

Recommendations:

Provide equivalent Linux command-line instructions (e.g., using ip route, nmcli, or netplan) for adding, viewing, and removing routes on Kubernetes nodes.
Include examples using kubectl or standard Kubernetes networking resources for route management, if possible.
Clarify whether the PowerShell cmdlets are available only on Windows-based Azure Stack Edge devices, and provide alternative instructions for Linux-based environments or for users connecting via SSH.
When describing networking concepts (e.g., virtual switches, NIC teaming), mention Linux equivalents (e.g., Linux bridges, bonding) or clarify their applicability.
Consider reordering or supplementing examples so that Linux and cross-platform approaches are presented alongside or before Windows/PowerShell-specific methods.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing SMB (a Windows-native protocol) in examples and explanations, mentioning SMB before NFS (the Linux/UNIX equivalent) throughout. There are no explicit Linux command-line or shell examples, and the documentation does not provide parity in terms of Linux-specific tooling or workflows. The focus on Azure portal GUI and SMB shares, with NFS only mentioned as an alternative, further reinforces this bias.

Recommendations:

Provide Linux-specific examples, such as using NFS as the primary example or showing both SMB and NFS usage equally.
Include command-line examples for both Windows (PowerShell) and Linux (bash/shell) environments for provisioning and mounting storage.
Clarify that both SMB and NFS are supported equally, and provide guidance for Linux-first users, including troubleshooting tips for NFS.
Add references to Linux-native tools (e.g., mount, exportfs, etc.) and workflows for managing storage.
Balance the order of presentation so that NFS and Linux-native methods are not always secondary to SMB/Windows methods.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. All command-line examples are shown as being run from Windows (with PowerShell prompts and Windows file paths). The prerequisites specifically call out Windows clients and PowerShell, and the workflow is described as being performed on a Windows system. There are no Linux or macOS examples, and no mention of Linux-specific instructions, file paths, or shell environments. Windows tooling and conventions (such as C:\ paths and PowerShell) are used exclusively.

Recommendations:

Provide parallel Linux/macOS instructions and examples, including shell prompts (e.g., $) and POSIX file paths (e.g., /home/user/.kube).
Mention installation steps for kubectl and prerequisites for Linux/macOS clients, not just Windows.
Show example commands and outputs as they would appear in a bash or zsh shell, not only PowerShell.
Clarify that the procedure is cross-platform and works on any supported OS, not just Windows.
Link to or summarize supported OSes and any OS-specific caveats in the prerequisites section.
Avoid using Windows-specific commands (e.g., New-HcsKubernetesNamespace) unless they are truly unavailable on other platforms; if so, explain alternatives or limitations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing SMB paths in Windows UNC format (\\Server\Share), using Windows-style username formats, and describing file/folder permissions using Windows GUI actions (right-click, Properties, Security tab). There are no examples or instructions for Linux or Unix-based environments, such as how to specify SMB paths or credentials from a Linux NAS, nor are Linux command-line or permission management methods mentioned.

Recommendations:

Include examples for specifying SMB paths and credentials from Linux systems (e.g., using /mnt/server/share or smb:// syntax).
Describe how to set permissions on source folders using Linux/Unix commands (e.g., chmod, chown) in addition to Windows GUI instructions.
Clarify that the data copy service supports both Windows and Linux NAS sources, and provide guidance for both.
Add troubleshooting steps and log file access instructions relevant to Linux environments.
Ensure that regular expression and wildcard pattern examples are platform-agnostic or provide both Windows and Linux shell equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. It explicitly assumes a Windows client, requires Windows PowerShell, and all command-line examples are shown in PowerShell context. There are no Linux or macOS command-line examples or instructions, and the documentation does not provide parity for non-Windows users. Windows tools and paths are referenced exclusively, and the workflow is described from a Windows perspective.

Recommendations:

Add parallel instructions and examples for Linux and macOS clients, including shell commands and environment setup.
Show command-line examples in both PowerShell and Bash (or general shell) formats.
Avoid assuming the client is Windows by default; instead, present Windows, Linux, and macOS as equally supported options.
Reference generic tools and paths (e.g., ~/.kube for kubeconfig) alongside Windows-specific ones.
Explicitly mention any differences or additional steps required for Linux/macOS users.
Where screenshots or UI steps are shown, clarify that the process is the same regardless of client OS, or note any differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows environments. All command-line examples are shown in PowerShell, with Windows-style paths (e.g., C:\Users\<username>\.kube), and sample outputs are from PowerShell terminals. The prerequisites and instructions explicitly refer to Windows PowerShell and Windows client systems, with no Linux or macOS equivalents provided. There is no mention of Linux shell usage, Linux file paths, or cross-platform considerations, despite kubectl being cross-platform.

Recommendations:

Provide equivalent Linux (bash) and macOS command-line examples alongside PowerShell examples.
Include Linux/macOS file path examples (e.g., ~/.kube) and explain where configuration files are stored on non-Windows systems.
Update prerequisites to mention supported Linux/macOS environments and required shell versions.
Show sample outputs from bash or zsh terminals as well as PowerShell.
Avoid assuming the user is on Windows; use neutral language or clarify when instructions are OS-specific.
Link to official kubectl installation guides for all platforms, not just Windows PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a strong Windows bias. All deployment and management commands use PowerShell cmdlets, even for Linux VMs. Windows examples and file paths are presented first and in more detail. Linux-specific tools, shell commands, and file paths are either missing or only briefly mentioned. The Linux section reuses Windows-centric PowerShell deployment and tracking commands, and does not provide equivalent Bash/CLI examples or Linux-native workflows.

Recommendations:

Provide Azure CLI and Bash examples for deploying and managing the Custom Script Extension on Linux VMs, rather than only PowerShell.
Include Linux-native file paths and log locations alongside Windows paths, and explain their significance.
Show Linux shell commands (e.g., mkdir, touch, cat) in the 'commandToExecute' examples, rather than using Windows-style commands or referencing the /home/Administrator directory, which is not standard on Linux.
Present Linux and Windows instructions in parallel, giving equal prominence to both, rather than always listing Windows first.
Demonstrate how to track and remove extensions using Linux-native tools or Azure CLI, not just PowerShell.
Clarify any differences in publisher/type/typeHandlerVersion for Linux vs. Windows extensions, and provide context 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 throughout. All command-line examples, environment variable settings, and certificate management steps are shown exclusively using Windows PowerShell, Windows paths, and Windows-specific tools (e.g., certutil.exe, Notepad, Windows Explorer). There are no equivalent instructions or examples for Linux or macOS users, and references to running commands are always in a Windows context. Even the installation and usage of Azure CLI and Python are shown only for Windows environments.

Recommendations:

Provide parallel instructions and examples for Linux (and optionally macOS) users, including bash shell commands, Linux file paths, and use of common Linux tools (e.g., openssl for certificate conversion, nano/vim for editing /etc/hosts).
When referencing tools like certutil.exe or Notepad, include Linux alternatives such as openssl and nano/vim.
Show environment variable setting examples for bash/zsh (e.g., export VAR=value) alongside PowerShell examples.
Include sample output from Linux terminals (e.g., $ prompt, /home/user paths) in addition to Windows PowerShell output.
When linking to installation instructions, provide links for all supported platforms, not just Windows.
Explicitly state that the procedure is cross-platform and highlight any platform-specific differences or requirements.

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 references Windows-centric tools and patterns (such as PowerShell and Windows-specific NUMA documentation) and does not provide Linux alternatives or parity in workflow or troubleshooting. While there is a brief mention that both Windows and Linux VHDs can be used as VM images, all operational guidance assumes a Windows/PowerShell environment.

Recommendations:

Provide equivalent Linux shell (bash) or Azure CLI examples for all PowerShell cmdlets used (e.g., for querying and setting NUMA policies, managing VMs).
Reference Linux documentation for NUMA and CPU affinity management, not just Windows.
Clarify whether the device management interface supports SSH or Linux-native management tools, and provide instructions if so.
When mentioning prerequisites or workflows, explicitly state and demonstrate steps for both Windows and Linux admin environments.
Ensure troubleshooting and monitoring guidance includes Linux-compatible tools and commands.
If PowerShell is required regardless of admin OS, clarify this up front and provide installation guidance for non-Windows platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell cmdlets for role management, without providing equivalent CLI or Linux-native command examples. The only command-line tooling discussed is PowerShell, and there is no mention of Azure CLI or Bash scripting. While the API and SDK samples are platform-neutral, the lack of Linux-specific or cross-platform command-line instructions may hinder Linux users.

Recommendations:

Add Azure CLI examples alongside PowerShell cmdlets for all role management tasks.
Explicitly mention cross-platform support for the SDK and API, and provide Bash/cURL examples for API usage.
Include Linux/Bash scripting alternatives where PowerShell is referenced, or clarify if PowerShell Core is required and supported on Linux.
Ensure that documentation sections referencing command-line tools do not assume a Windows environment by default.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is heavily oriented around PowerShell and Windows tooling, even for Linux VM scenarios. All command-line examples (including those for Linux) use Azure PowerShell cmdlets and are shown in a Windows PowerShell prompt. There are no CLI/bash examples, and the instructions assume the use of a Windows client environment. The documentation also references Windows-specific file paths and screenshots, and Windows terminology is prevalent throughout.

Recommendations:

Provide Azure CLI (az) examples alongside or instead of PowerShell for Linux VM scenarios, using bash syntax and Linux file paths.
Show sample commands and outputs from a Linux shell (e.g., bash prompt), not just Windows PowerShell.
Clarify that PowerShell Core can be used cross-platform, or explicitly support native Linux workflows.
Include screenshots and instructions relevant to Linux client environments where appropriate.
Avoid assuming the user is operating from a Windows machine; balance references to both Windows and Linux client environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing and exclusively mentioning Windows PowerShell and Windows Server Update Services (WSUS) for management and updates. There are no examples or explicit instructions for Linux or cross-platform management tools (e.g., Bash, SSH, Linux CLI), and the local management interface is described as the 'Windows PowerShell interface' without mention of Linux alternatives. Update instructions reference WSUS and manual downloads via the web UI, but do not mention Linux-compatible update mechanisms or tools. VM management is described via Azure PowerShell, with no Linux or cross-platform CLI examples provided.

Recommendations:

Include Linux and cross-platform management instructions, such as using SSH, Bash, or Azure CLI on Linux/macOS.
When referencing the 'Windows PowerShell interface', also mention SSH or Bash access for Linux users, if supported.
Provide update instructions that are compatible with Linux environments, or clarify if updates can be applied via Linux tools.
For VM management, add examples using Azure CLI or REST API that can be run from Linux/macOS, not just Azure PowerShell.
Avoid referencing Windows-specific tools (like WSUS) without offering Linux equivalents or alternatives.
Ensure that all code snippets and management workflows are presented in both Windows and Linux contexts, or explicitly state platform limitations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a strong Windows bias. All command-line examples use PowerShell syntax, and all screenshots and sample outputs are from Windows environments (e.g., 'PS C:\WINDOWS\system32>'). Instructions for editing the hosts file, installing certificates, and using Docker are written specifically for Windows, with no equivalent Linux or macOS guidance. There is no mention of Linux shell commands, Linux file paths, or Linux-specific Docker installation steps. The use of Windows-specific tools and patterns (e.g., PowerShell cmdlets, Windows file paths) is pervasive, and Linux users are not provided with parallel instructions.

Recommendations:

Provide parallel Linux/macOS instructions and examples for all steps, including editing /etc/hosts, installing certificates, and using Docker.
Include Linux shell (bash) command examples alongside PowerShell, especially for Docker, kubectl, and HTTP API interactions.
Show sample outputs from Linux terminals (e.g., bash prompt) in addition to Windows PowerShell.
Document certificate installation steps for Linux (e.g., using update-ca-certificates or similar tools).
Reference Linux file paths (e.g., /etc/hosts) and explain any OS-specific differences.
Clarify that the process is cross-platform and explicitly support Linux/macOS users in the prerequisites and throughout the guide.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by focusing on PowerShell as the primary interface for Kubernetes RBAC operations on Azure Stack Edge Pro. It mentions using PowerShell to create namespaces and users, with no equivalent Linux shell or cross-platform CLI examples. The instructions and references are tailored to Windows environments, and Linux alternatives are not discussed or shown.

Recommendations:

Provide equivalent Linux shell (bash) examples for all PowerShell commands and operations.
Clarify whether operations can be performed using standard kubectl commands on Linux/macOS, and provide guidance if so.
Explicitly mention cross-platform compatibility of tools and interfaces, or note any Windows-specific limitations.
Include screenshots or command snippets from both Windows (PowerShell) and Linux (bash) environments.
Reorder examples or explanations to present cross-platform or Linux-native methods before or alongside Windows/PowerShell approaches.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing PowerShell as the primary method for initial access/user/namespace setup, without mentioning Linux or cross-platform alternatives. There are no Linux shell or cross-platform command examples for these steps, and the initial workflow assumes familiarity with Windows tooling.

Recommendations:

Provide equivalent Linux/bash command-line instructions for configuring access (user, namespace, RBAC) alongside PowerShell examples.
Explicitly state whether all steps can be performed from Linux/macOS systems, and if not, clarify any platform-specific requirements.
Include notes or links to cross-platform tools (e.g., Azure CLI, Bash scripts) where possible.
Reorder or parallelize instructions so that Windows and Linux users are equally supported, rather than presenting Windows/PowerShell first or exclusively.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation consistently presents SMB (a Windows-centric protocol) as the default and standard, with NFS (the Linux equivalent) mentioned secondarily. There are references to Windows tools (e.g., File Explorer) for managing permissions, but no equivalent Linux instructions or examples are provided. There are no command-line examples or guidance for Linux users on mounting or managing shares, and the documentation lacks parity in practical Linux usage instructions.

Recommendations:

Provide explicit Linux examples for mounting NFS shares, including sample mount commands and configuration steps.
When discussing SMB and NFS, present both protocols with equal prominence and provide usage examples for both Windows (SMB) and Linux (NFS) clients.
Include instructions for managing permissions on NFS shares from Linux systems, similar to the File Explorer guidance for Windows.
Avoid language that positions SMB as the default or standard; instead, clarify that SMB is typical for Windows clients and NFS for Linux, without prioritizing one over the other.
Add 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 clear Windows bias: Windows instructions and examples (using net use, File Explorer, and Robocopy) are presented first and in much greater detail than Linux equivalents. The Linux section is brief, lacks detailed copy tool examples, and even contains a likely error (mount -t nfs instead of -t cifs for SMB). Only Windows-specific tools (Robocopy) are discussed in depth, with no Linux alternatives (like rsync or smbclient) shown for SMB copy. The copy performance tuning section only references Robocopy sessions/threads, not Linux tools. This results in a lack of parity and guidance for Linux users.

Recommendations:

Provide equally detailed Linux instructions for connecting to SMB shares, using the correct mount command (mount -t cifs) and showing how to specify credentials.
Include Linux-native SMB copy tool examples (such as smbclient, rsync over SMB, or cp after mounting) with sample commands and output, similar to the Robocopy section.
Add performance tuning guidance for Linux copy tools (e.g., rsync options, parallelization strategies) analogous to the Robocopy tuning table.
Mention Linux tools and patterns alongside Windows tools, not only in separate sections but also in summary tables and recommendations.
Correct any technical inaccuracies (e.g., using -t nfs for SMB is likely incorrect; should be -t cifs or -t smb3).
Where Robocopy is referenced, also reference Linux equivalents and provide links to their documentation.

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 used as the primary (and sometimes only) CLI for both Windows and Linux instructions, with all command-line examples and outputs shown in PowerShell sessions on Windows hosts. Windows-specific tools and file paths are referenced first and more extensively. Linux instructions are present but often shown as being executed from a Windows PowerShell environment, and there are no native Linux shell (bash) command examples for deployment or management tasks. Additionally, removal instructions and some troubleshooting steps are only shown using PowerShell, with no Linux-native alternatives.

Recommendations:

Provide native Linux shell (bash) command examples for all deployment, tracking, and removal steps, using Azure CLI or Azure PowerShell Core on Linux where appropriate.
Show Linux command outputs from a Linux terminal, not from a Windows PowerShell session.
When presenting instructions for both OSes, avoid always listing Windows first; alternate or present both in parallel.
Include Linux-native file paths, tools, and troubleshooting steps where relevant.
Clarify that Azure CLI and Azure PowerShell Core are cross-platform, and provide installation/use instructions for Linux users.
Ensure that all steps (including removal and troubleshooting) have Linux-native equivalents, not just PowerShell commands.

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 device. There are no Linux shell (bash) or cross-platform CLI examples for the key configuration steps, and the connection instructions reference only the PowerShell interface. The sample output also uses PowerShell prompts, reinforcing the Windows-centric approach.

Recommendations:

Provide equivalent bash or cross-platform Azure CLI commands for all configuration steps, especially for connecting to the device and setting Azure Monitor configuration.
Document how to connect to the device using SSH or other Linux-friendly methods, if supported.
Include sample outputs and command prompts for both Windows (PowerShell) and Linux (bash) environments.
Clearly state if certain steps or cmdlets are only available on Windows, and suggest alternatives or workarounds for Linux users.
Review and update screenshots and instructions to reflect parity between Windows and Linux usage where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell in the 'Next steps' link, without mentioning or providing equivalent Linux/CLI examples. There are no Linux-specific instructions or examples, and the documentation implicitly assumes the use of Windows tools and patterns.

Recommendations:

Provide equivalent Linux/Bash/CLI examples alongside or before PowerShell instructions.
Include references or links to Linux-compatible tools (e.g., Azure CLI, curl, bash scripts) for interacting with the local Azure Resource Manager.
Ensure that 'Next steps' and related links offer parity for both Windows and Linux users.
Explicitly state that the APIs and templates can be used from any OS, and provide cross-platform guidance where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a clear Windows bias. All command-line examples use PowerShell exclusively, with no mention of Linux shells or tools. Device access is described only via remote PowerShell, and BitLocker (a Windows technology) is referenced for encryption without Linux alternatives. There are no Linux or cross-platform command-line instructions, and Windows-centric terminology and tools are presented first and exclusively.

Recommendations:

Provide equivalent Linux/Bash command-line instructions for device management tasks, such as registering resource providers or accessing the device remotely.
Mention and document cross-platform or Linux-compatible methods for remote device access (e.g., SSH, Azure CLI, or REST APIs), not just PowerShell.
If BitLocker is referenced for encryption, clarify whether Linux-compatible alternatives exist or how Linux users can interact with encrypted volumes.
Include notes or sections specifically addressing Linux/macOS users, outlining any differences or additional steps required.
Ensure that examples and screenshots are balanced between Windows and Linux environments, 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 Windows bias by providing instructions and examples that assume the user is on a Windows client. Specifically, it instructs users to edit the Windows hosts file (C:\Windows\System32\Drivers\etc\hosts), and the certificate installation steps are only described for Windows (using the Certificate Import Wizard and 'Local machine' store). There are no equivalent instructions or examples for Linux or macOS users, nor is there any mention of how to perform these steps on non-Windows platforms.

Recommendations:

Provide parallel instructions for Linux and macOS users, including the location and editing of the /etc/hosts file.
Describe how to install the downloaded certificate on Linux (e.g., using update-ca-certificates or similar tools) and macOS.
Avoid assuming the client is always Windows; use neutral language or present Windows and Linux/macOS steps side-by-side.
Include screenshots or command-line examples for Linux/macOS where appropriate.
Explicitly state platform requirements or limitations if certain features are only available on Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments, with all command-line examples using PowerShell, Windows-specific tools (e.g., Notepad, Windows hosts file path), and screenshots from Windows. There are no CLI, Bash, or Linux-native command examples for any step, and Windows tools are mentioned before or instead of cross-platform alternatives. Linux is only referenced as a possible VM guest OS, not as a management/deployment platform.

Recommendations:

Provide equivalent Azure CLI (az) and Bash command examples for all resource creation, deployment, and querying steps, alongside PowerShell.
Include instructions and screenshots for editing the hosts file on Linux/macOS (e.g., /etc/hosts with sudo nano or vi).
Mention and demonstrate how to use Storage Explorer and AzCopy on Linux/macOS, including installation and certificate import steps.
Show sample output from Linux/macOS terminals (e.g., bash prompt, not just PS C:\WINDOWS\system32>).
Clarify that all deployment steps can be performed from Linux/macOS, and explicitly call out any Windows-only requirements.
Add a section or tabs for Linux/macOS users in all code and tool usage blocks, ensuring parity in instructions and examples.

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 commands for Linux users (such as Azure CLI). The only command-line example is Windows-centric, and there is no guidance for Linux or cross-platform users.

Recommendations:

Include Azure CLI examples (e.g., using 'az resource list') alongside PowerShell to support Linux and macOS users.
Explicitly mention that both PowerShell and Azure CLI can be used, and provide links to relevant documentation for both.
When referencing command-line tools, avoid assuming the user is on Windows; clarify cross-platform options.
Add a note or section for Linux/macOS users on how to perform the same tasks using their preferred tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ visual_studio_heavy

⚠️ missing_linux_example

Summary:

The documentation consistently presents Visual Studio (a Windows-centric tool) before Visual Studio Code and the Azure CLI, both in project creation and publishing steps. There are no explicit Linux-specific instructions or examples, and the use of Visual Studio is emphasized, which may not be available or preferred on Linux systems. While Azure CLI is mentioned, there is no guidance for Linux-specific environments or workflows, and no mention of common Linux editors or shell environments.

Recommendations:

Present Visual Studio Code and Azure CLI instructions before Visual Studio, or at least in parallel, to avoid implying a Windows-first workflow.
Explicitly mention that all Azure CLI and .NET Core commands work on Linux, and provide example commands run in a Linux shell (e.g., bash).
Include instructions or links for setting up and using Azure Functions with Linux-native tools and editors (e.g., JetBrains Rider, Vim, or Emacs).
Add a note clarifying that Visual Studio is optional and not required for Linux users.
Provide sample commands and screenshots from a Linux terminal to demonstrate parity.
Ensure that any referenced sample code repositories include Linux setup instructions (e.g., requirements for dotnet SDK on Linux, troubleshooting tips).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the only CLI method for managing local storage accounts, without mentioning or providing examples for Linux-compatible tools such as Azure CLI or Bash scripts. The instructions for configuring clients and accessing resources are oriented around PowerShell, and there are no Linux-specific or cross-platform command-line examples. This may create the impression that only Windows environments are supported or recommended.

Recommendations:

Include Azure CLI (az) command examples alongside or instead of Azure PowerShell for all management tasks, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
Explicitly mention that management can be performed from Linux, macOS, or Windows, and provide Bash or shell script examples where applicable.
Add a section or callout for Linux users, detailing any prerequisites or differences in procedure.
Where PowerShell is referenced, clarify whether PowerShell Core (which is cross-platform) is supported, and provide installation instructions for non-Windows systems if relevant.
Review all referenced links and included content to ensure Linux parity in instructions and examples.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates some Windows bias by referencing the PowerShell interface as a primary method for querying module status and IP addresses, without providing equivalent Linux CLI examples. The mention of 'Connect to the PowerShell interface' appears before any alternative, and no Linux-native commands or tools are suggested for these management tasks. The rest of the documentation is largely OS-agnostic, focusing on Docker/Kubernetes JSON configurations, but the management and troubleshooting guidance leans toward Windows/PowerShell.

Recommendations:

Provide Linux CLI (e.g., bash) equivalents for all PowerShell-based instructions, especially for querying module status and IP addresses.
When referencing management interfaces, mention both Windows (PowerShell) and Linux (bash/CLI) options together, or list Linux first if the device is recommended to run Linux.
Include example commands using standard Linux tools (e.g., kubectl, iotedge CLI) for monitoring and troubleshooting modules.
Clarify that the PowerShell interface is optional and provide guidance for users who may not have access to Windows environments.
Audit other sections for subtle Windows-first language or assumptions, and ensure parity in tooling and examples.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on Azure PowerShell for command-line instructions, with all examples and scripts using PowerShell cmdlets and syntax. There are no examples or guidance for Linux users (e.g., Bash, Azure CLI), and the only command-line tooling discussed is PowerShell, which is traditionally associated with Windows environments. This creates a bias toward Windows users and may hinder Linux users from following the instructions.

Recommendations:

Provide equivalent instructions and examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
Include Bash shell examples for Linux users, especially for scripting and environment setup.
Clarify that the Azure Cloud Shell supports both PowerShell and Bash, and show how to switch between them.
Mention any platform-specific considerations (e.g., file paths, prerequisites) for both Windows and Linux.
Ensure screenshots and sample outputs are not exclusively from Windows environments if the process is cross-platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes certificate export procedures using Windows-specific tools (certlm.msc, Certificate Export Wizard) and graphical steps, with no mention of Linux or cross-platform alternatives. All instructions and screenshots are Windows-centric, and there are no command-line or Linux/macOS examples provided.

Recommendations:

Add equivalent instructions for exporting certificates on Linux (e.g., using openssl commands to export .cer and .pfx files).
Include command-line examples for both Windows (e.g., PowerShell) and Linux/macOS to ensure parity.
Mention and link to cross-platform certificate management tools where appropriate.
Clearly indicate if the process is supported only on Windows, or provide guidance for users on other operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. In certificate import instructions, Windows PowerShell and Windows Server UI steps are provided in detail with screenshots, while Linux instructions are more generic and lack equivalent step-by-step detail or visuals. Windows tools and terminology (e.g., PowerShell, Windows Server UI) are mentioned first and more prominently. However, AzCopy usage is shown for both Linux and Windows, and Linux command-line examples are present, reducing the overall bias.

Recommendations:

Provide step-by-step, distribution-specific Linux certificate import instructions, including example commands for popular distributions (e.g., Ubuntu, RHEL) and screenshots where possible.
Present Linux and Windows instructions in parallel or in separate, equally detailed sections, rather than listing Windows first and in more depth.
Include troubleshooting tips and common issues for Linux users, similar to what is often provided for Windows.
Ensure all tools and UI references (e.g., Storage Explorer) clarify cross-platform availability and usage.
Where possible, use neutral language and ordering (e.g., 'On Linux or Windows, do X' instead of 'On Windows, do X. On Linux, ...').

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., Windows Server Update Services), mentioning Windows update infrastructure before any cross-platform alternatives, and omitting Linux-specific instructions or examples for device configuration, network setup, and certificate management. There are no explicit Linux or cross-platform command-line examples, and the documentation assumes familiarity with Windows-centric patterns.

Recommendations:

Include explicit Linux examples for network configuration (e.g., how to set a static IP on Linux, not just via Windows network adapter settings).
Mention and provide guidance for using Linux-compatible update servers or clarify if WSUS is optional or required.
Offer cross-platform instructions for certificate generation and management, including Linux tools such as OpenSSL.
Where possible, avoid referencing Windows tools exclusively (e.g., WSUS) or provide Linux alternatives (e.g., using public NTP servers, Linux-based update mechanisms).
Add notes or sections for Linux/macOS users, especially for steps involving connecting to the device, configuring network settings, and interacting with the local web UI.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased towards Windows environments, as all examples and operational instructions are provided exclusively using PowerShell cmdlets and Windows-centric tools. There is no mention of Linux or cross-platform alternatives, and the documentation assumes the use of Windows-based management interfaces and file paths. This creates barriers for users managing Azure Stack Edge devices from Linux or non-Windows systems.

Recommendations:

Provide equivalent command-line examples using cross-platform tools (e.g., Azure CLI, Bash, or PowerShell Core on Linux) where possible.
Clarify whether remote support and diagnostics features are available or supported when managing Azure Stack Edge devices from Linux systems.
Include instructions for connecting to the device and managing remote support sessions from Linux/macOS, if supported.
Document any limitations or requirements for non-Windows users, and offer workarounds or alternative workflows.
Where file paths are referenced (e.g., C:\ProgramData\...), note the equivalent locations or access methods for Linux-based management.
Explicitly state if the device or management interface is Windows-only, to set correct expectations for cross-platform users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples and troubleshooting steps reference PowerShell cmdlets (e.g., Add-AzureRmEnvironment, connect-AzureRmAccount) and PowerShell-specific instructions. There are no CLI or Bash/Linux command equivalents provided, and Linux/Mac troubleshooting is only mentioned in the context of a certificate error, not as a first-class workflow. Instructions for validating client setup focus exclusively on PowerShell and Windows tools, with no mention of Azure CLI, Bash, or cross-platform alternatives.

Recommendations:

Provide equivalent Azure CLI (az) commands for all PowerShell cmdlet examples, and show both side-by-side where possible.
Include Linux and macOS-specific instructions for client configuration, such as validating Python, OpenSSL, and certificate installation.
Reference cross-platform tools (e.g., Azure CLI, Bash, SSH) in addition to or before Windows/PowerShell tools.
Explicitly document any platform-specific differences or requirements, and ensure Linux/Mac users are not treated as an afterthought.
Add troubleshooting steps and examples for common Linux/Mac issues beyond the single certificate store mention.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows moderate Windows bias. Powershell is used for both Windows and Linux command examples, even when Linux-native shells (bash) would be more appropriate. In some troubleshooting sections, Windows solutions and file paths are described in more detail or appear before Linux equivalents. Windows-specific tools and registry commands are referenced without always providing Linux alternatives or parity in explanation. Some Linux troubleshooting steps lack the same level of detail or example commands as their Windows counterparts.

Recommendations:

Use bash shell syntax for Linux command examples instead of Powershell, especially in code blocks intended for Linux VMs.
Ensure that for every Windows-specific troubleshooting step or log file path, the Linux equivalent is provided with equal prominence and detail.
When referencing Windows tools (e.g., registry edits), provide Linux alternatives or explicitly state when there is no equivalent.
Balance the order of presentation so that Linux and Windows instructions are given equal weight, or alternate which is presented first.
Expand Linux troubleshooting sections with more detailed examples, commands, and explanations to match the depth provided for Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing only Windows-based instructions and examples, such as mounting Azure file shares using Windows-specific guides and creating Windows VMs. There are no Linux equivalents or alternative instructions for users on Linux systems. The SharePoint Migration Tool (SPMT), which is Windows-only, is recommended without mentioning alternatives or workarounds for Linux users.

Recommendations:

Include parallel instructions for Linux users, such as how to mount Azure file shares on Linux VMs using SMB or NFS.
Provide guidance on creating both Windows and Linux VMs in Azure, with links to relevant documentation for each.
Acknowledge that SPMT is Windows-only and suggest alternative migration strategies or tools for Linux environments, if available.
Present steps for both operating systems side by side or clearly indicate OS-specific steps to ensure inclusivity.
Add a section or note clarifying OS requirements and limitations for the SharePoint Migration Tool.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias in several areas. In error resolutions, Windows file paths (e.g., C:\Windows\System32\drivers\etc\hosts) are often mentioned before Linux equivalents, or Linux is omitted entirely in some entries. Instructions for importing SSL certificates focus on Azure Storage Explorer, a GUI tool primarily used on Windows, with no mention of Linux CLI alternatives. Some troubleshooting steps reference only Windows paths or tools, and Linux-specific commands or methods are inconsistently provided.

Recommendations:

Ensure that every example or file path provided for Windows is immediately accompanied by the Linux equivalent, not just in some cases.
When referencing tools like Azure Storage Explorer, also mention CLI or cross-platform alternatives (e.g., how to import certificates using Linux commands or scripts).
Provide explicit Linux command-line examples for tasks such as editing /etc/hosts or importing certificates into the system store.
Avoid listing Windows instructions or paths first by default; alternate the order or present both together.
Clarify when a tool or method is Windows-only, and offer a Linux-compatible workflow where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell/Hyper-V (Windows-only) tooling for VHD conversion and inspection, referencing Windows-specific procedures first, and omitting Linux-based alternatives or examples. There are no instructions or links for Linux users to perform equivalent tasks, such as using qemu-img or Azure CLI on Linux.

Recommendations:

Add Linux-based instructions for preparing and converting VHDs, such as using qemu-img or Azure CLI.
Include examples and links for Linux tools that can inspect and convert VHD formats.
Ensure that both Windows and Linux workflows are presented in parallel, or at least mention Linux alternatives where only Windows tools are referenced.
Where PowerShell is suggested, provide equivalent Bash/Azure CLI commands for Linux users.
Link to documentation or community guides for Linux users managing VHDs for Azure Stack Edge.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is emphasized as a primary management and deployment tool, with multiple references and dedicated sections. Windows-specific tools and extensions (such as password reset via PowerShell) are highlighted, and Windows image preparation is listed before Linux or generalized approaches. While Linux is mentioned as a supported VM OS, Linux-specific examples, tools, or workflows are not provided or are less visible, and there is a lack of parity in example depth and guidance for Linux users.

Recommendations:

Provide Linux-specific examples and workflows alongside Windows/PowerShell instructions, such as using Bash, Azure CLI, or SSH for VM management.
Ensure that Linux image preparation and deployment guides are as detailed and prominent as Windows guides.
When listing options (e.g., image preparation, connection methods), alternate the order or present Windows and Linux equally.
Include Linux-native tools and extensions (e.g., cloud-init, SSH key reset) where applicable, not just Windows/PowerShell-based solutions.
Expand the 'Connect to your VM' and management sections with explicit Linux command-line examples and troubleshooting tips.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by referencing Windows-specific tools and update mechanisms (e.g., WSUS, Windows Update server) without mentioning Linux equivalents or alternatives. There are no explicit examples or instructions for Linux users, and Windows patterns are mentioned first or exclusively in areas such as update server configuration. Additionally, there is a lack of Linux-specific guidance for tasks like network readiness checks or device management.

Recommendations:

Include references to Linux-compatible update mechanisms or clarify if only Windows Update is supported.
Provide alternative instructions or notes for Linux users where Windows tools (e.g., WSUS) are mentioned.
Add examples or guidance for performing network readiness checks and device management from Linux systems.
Ensure parity in mentioning both Windows and Linux tools, especially in sections about device setup, network configuration, and certificate management.
Explicitly state any platform limitations or requirements so Linux users are aware of potential constraints.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools (such as Windows PowerShell and Windows Firewall), providing log examples and instructions that are Windows-centric, and omitting equivalent Linux commands, tools, or log formats. The only command-line interface mentioned is Windows PowerShell, and the only firewall logs discussed are from Microsoft Windows Firewall. There are no Linux or cross-platform examples or instructions, nor are Linux log formats or tools referenced.

Recommendations:

Include instructions and examples for collecting logs and running diagnostics using Linux command-line tools (e.g., Bash, SSH, Linux firewall logs).
Mention and provide examples for Linux equivalents of Windows PowerShell commands, such as using SSH and Linux shell scripts to collect support packages.
Reference Linux log file locations and formats (e.g., /var/log/syslog, /var/log/messages, or iptables logs) alongside Windows log examples.
Clarify if the device or management interface is Windows-only, or explicitly state cross-platform support and provide parity in documentation.
Add troubleshooting steps and log collection methods for users managing Azure Stack Edge devices from Linux or macOS systems.

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 Windows PowerShell examples, referencing Windows-specific tools and environments (such as 'elevated Windows PowerShell session'), and omitting any Linux or cross-platform CLI examples. There is no mention of Azure CLI, Bash, or other Linux-compatible scripting approaches, and all sample outputs are from a Windows environment.

Recommendations:

Add equivalent instructions and examples using Azure CLI (az commands), which is cross-platform and works on Linux, macOS, and Windows.
Provide Bash script examples for blob tiering operations, especially for users on Linux or macOS.
Explicitly mention that Azure PowerShell can be used on Linux and macOS (via PowerShell Core), and provide any necessary adjustments for those platforms.
Include sample outputs from non-Windows environments to demonstrate parity.
Rephrase steps to avoid assuming a Windows environment (e.g., 'Open a terminal' instead of 'Open an elevated Windows PowerShell session').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation repeatedly emphasizes Windows-specific behaviors and limitations, such as the device being Windows-based, lack of support for case-sensitive file names, and reliance on Windows protocols (SMB). There is no mention of Linux-specific usage patterns, tools, or caveats, nor are there examples or guidance for Linux users. The documentation assumes a Windows environment as the default and does not provide parity for Linux users.

Recommendations:

Include explicit guidance and examples for Linux users, such as how to connect to Data Box using NFS from Linux systems.
Document any Linux-specific caveats or limitations, such as file system compatibility, case sensitivity, and supported protocols.
Balance the mention of Windows and Linux tools and patterns, ensuring that Linux equivalents (e.g., NFS, rsync, Linux file system behaviors) are described alongside Windows/SMB.
Add troubleshooting tips and best practices for both Windows and Linux environments.
Where Windows limitations are described (e.g., case insensitivity), clarify the impact on Linux users and suggest workarounds if available.

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 scripts and cmdlets (e.g., Test-NetConnection, PowerShell functions) are used for troubleshooting and management tasks, with no equivalent Linux command-line examples provided. Windows/PowerShell tools are mentioned exclusively or before Linux alternatives. While some Linux-specific troubleshooting is included (e.g., cloud-init, waagent.conf), the main workflow and scripting guidance are Windows-centric, and Linux users are left to infer equivalent steps.

Recommendations:

For every PowerShell or Windows command example (e.g., Test-NetConnection, PowerShell scripts for Azure Resource Manager), provide equivalent Linux shell commands (e.g., curl, wget, ping, netcat, az CLI).
When listing troubleshooting steps, avoid always presenting Windows/PowerShell first; alternate or present both Windows and Linux options together.
For VM image preparation and management, include explicit Linux-based workflows and commands (e.g., using qemu-img, Azure CLI on Linux, shell scripts).
Where Windows tools or patterns are mentioned (e.g., Hyper-V, PowerShell), clarify Linux equivalents or note if not applicable.
Add Linux-specific troubleshooting for network and resource issues (e.g., using ip, ifconfig, systemctl, journalctl for logs).
Ensure that all users, regardless of OS, have clear, actionable steps without needing to translate Windows-centric instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in the data copy section by listing Windows/SMB/Robocopy as the first and most detailed example, while Linux/NFS is mentioned only secondarily and with less detail. The use of Windows-specific tools (Robocopy) is highlighted, and there are no explicit Linux command-line examples (e.g., mounting SMB shares from Linux, or using Linux-native tools for SMB). There is also an implicit assumption of Windows environments in the share connection instructions (UNC paths), and no PowerShell or Linux shell parity is provided for all steps.

Recommendations:

Provide explicit Linux examples for copying data to SMB shares, such as using the 'mount -t cifs' command or 'smbclient', alongside the Windows/Robocopy example.
List Linux/NFS and Windows/SMB options in parallel, not with Windows first.
Include Linux command-line examples for connecting to SMB shares and copying data, not just referencing 'cp' or 'rsync' for NFS.
Clarify that both Windows and Linux hosts are supported for all relevant steps, and provide parity in instructions and troubleshooting.
Where UNC paths are shown (\\<IP>\ShareName), also show the equivalent Linux mount or access syntax.
If PowerShell or Windows-specific tools are mentioned, provide equivalent Bash/Linux shell commands where possible.

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 defaults (e.g., Windows Server Update Services, time.windows.com as the default NTP server, and Microsoft Update server) without mentioning Linux equivalents or alternatives. There are no examples or guidance for Linux-based environments, and Windows-centric terminology and services are presented as the primary or only options.

Recommendations:

Include Linux-friendly update options, such as mentioning support for update servers based on Linux (e.g., apt, yum repositories, or custom update endpoints).
When referencing NTP servers, provide examples of neutral or Linux-associated public NTP servers (e.g., pool.ntp.org) alongside time.windows.com.
Clarify whether the device supports integration with Linux-based update management solutions and provide instructions if so.
Avoid presenting Windows tools (e.g., WSUS) as the only or primary option; instead, list them alongside any supported Linux alternatives.
Add explicit examples or notes for administrators managing the device from Linux systems, including certificate management and network configuration.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented toward Windows users by exclusively referencing Visual Studio (a Windows-centric IDE) and its .http file support for making API calls. There are no examples or guidance for Linux users or for cross-platform tools/editors. The workflow assumes the use of Visual Studio and does not mention alternatives like VS Code, curl, Postman, or HTTPie, which are commonly used on Linux and macOS. While Azure CLI is cross-platform, the entire process is framed within the context of Visual Studio on Windows.

Recommendations:

Add equivalent instructions for using cross-platform tools such as Visual Studio Code with the REST Client extension, curl, HTTPie, or Postman to make API requests.
Provide explicit examples for Linux and macOS users, including how to structure and send HTTP requests outside of Visual Studio.
Clarify that Visual Studio is primarily a Windows tool and suggest alternatives for non-Windows environments.
Include screenshots or terminal examples from Linux environments where appropriate.
Consider restructuring the article to present cross-platform methods first or in parallel with Visual Studio instructions, rather than focusing solely on Windows tooling.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by referencing PowerShell for VPN configuration without mentioning Linux or cross-platform alternatives. BitLocker is described as the encryption technology, which is Windows-specific, with no mention of Linux-compatible encryption solutions. There are no Linux command-line or tool examples, and the only scripting/configuration guidance is for Windows/PowerShell environments.

Recommendations:

Include Linux-based instructions for VPN configuration, such as using Azure CLI or relevant Linux VPN tools.
Mention and provide examples for Linux-compatible encryption-at-rest solutions (e.g., dm-crypt/LUKS) if supported, or clarify if BitLocker is the only supported method.
Provide cross-platform certificate management instructions, including Linux command-line examples (e.g., using OpenSSL for certificate handling).
Ensure that any references to PowerShell or Windows tools are accompanied by equivalent Linux/macOS guidance, or explicitly state platform limitations.
Add a section or callout clarifying platform support and any OS-specific requirements for device management.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page for Azure Data Box demonstrates a Windows bias by referencing Windows-specific tools (e.g., SharePoint Migration Tool, Veeam for Hyper-V, SQL Server) and omitting explicit Linux usage examples or Linux-native tools. The workflow and setup instructions do not mention Linux hosts or provide Linux-specific guidance for mounting shares or copying data. The documentation also references Windows-centric scenarios (e.g., VM farm, SQL Server) before mentioning more cross-platform or Linux-relevant use cases (e.g., HDFS).

Recommendations:

Add explicit Linux usage examples for mounting SMB/NFS shares and copying data to/from Data Box devices, including relevant commands (e.g., mount, rsync, cp).
Reference Linux-native tools and scenarios (e.g., using rsync, tar, or Linux backup solutions) alongside Windows tools.
Include guidance for both Windows and Linux environments in workflow/setup steps, ensuring parity in instructions and troubleshooting.
Mention Linux-based workloads (e.g., PostgreSQL, MySQL, Linux VMs) as migration examples, not just Windows-centric ones.
Where third-party tools are referenced (e.g., Veeam, Commvault), clarify their Linux support or suggest Linux alternatives if available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows environments by referencing PowerShell cmdlets (e.g., Set-HcsKubeClusterNetworkInfo) as the only method for certain configurations, without providing Linux or cross-platform alternatives. There are no Linux command-line examples or mentions of how to perform equivalent tasks on non-Windows systems. The documentation assumes access to Windows-native tools and interfaces, which may not be available to Linux users.

Recommendations:

Provide equivalent Linux command-line instructions (e.g., using SSH and standard Linux tools) for tasks currently described only with PowerShell.
Clarify whether the PowerShell interface is accessible from non-Windows systems (e.g., via PowerShell Core on Linux or remote SSH), and provide guidance for Linux users.
Where device management is possible via REST API or other cross-platform tools, include those options alongside Windows-specific instructions.
Explicitly state platform requirements and, if Windows is required for certain steps, explain why and suggest workarounds or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias primarily through its exclusive use of Windows-centric terminology, log formats, and user account references (e.g., 'WIN-DATABOXADMIN', 'NT AUTHORITY', 'Workgroup'). There are no explicit PowerShell commands or Windows command-line examples, but the audit log samples and explanations are clearly based on Windows event logs and authentication models. There are no Linux-specific examples, log samples, or instructions, and the documentation does not mention or demonstrate parity for Linux users or administrators.

Recommendations:

Include Linux-specific log samples, such as syslog or auditd entries, to illustrate how Data Box events appear on Linux systems.
Add instructions or examples for tracking and auditing Data Box events on Linux, including relevant tools (e.g., journalctl, grep, auditctl).
Clarify whether the Data Box device supports Linux authentication and logging mechanisms, and if so, provide guidance for Linux administrators.
When presenting sample logs or user accounts, provide both Windows and Linux variants (e.g., show a sample with a Linux user and group, or NFS authentication).
Explicitly mention any differences in experience or available features between Windows and Linux environments, if applicable.
Ensure that troubleshooting and verification steps (such as checksum validation) include Linux command-line examples (e.g., using sha256sum or cksum).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas: Windows tools (Robocopy) are mentioned by name and linked, while Linux equivalents (cp, rsync) are referenced generically without links or examples. Windows hosts and SMB are described first, with NFS/Linux as a secondary note. There are no explicit Linux command examples or screenshots, and no mention of Linux-specific troubleshooting or nuances. The documentation assumes familiarity with Windows-centric tools and patterns.

Recommendations:

Provide explicit Linux command-line examples for data copy (e.g., sample rsync and cp commands with flags).
Include links to Linux documentation for cp and rsync, similar to the Robocopy link.
Add screenshots or step-by-step instructions for Linux/NFS hosts, not just Windows/SMB.
Mention Linux/NFS options before or alongside Windows/SMB, not after.
Include troubleshooting tips or common issues for Linux/NFS environments.
Clarify that both Windows and Linux hosts are fully supported, and provide parity in documentation depth.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in the 'Copy data' section by mentioning Windows/SMB/Robocopy first and providing a link to Robocopy documentation, while Linux/NFS commands are only briefly referenced without examples or links. There are no detailed Linux copy command examples or parity in tool guidance. The rest of the documentation is largely OS-neutral, but the copy step lacks Linux parity.

Recommendations:

Provide explicit Linux/NFS copy examples, such as sample cp and rsync commands, alongside the Windows/Robocopy example.
Include links to official documentation for Linux tools (e.g., GNU cp, rsync) similar to the Robocopy link.
Present Windows and Linux instructions in parallel, or in separate clearly-labeled sections, to ensure equal visibility.
Avoid listing Windows tools or instructions before Linux equivalents; consider alphabetical or scenario-based ordering.
Clarify any OS-specific requirements or differences in supported protocols (SMB/NFS) and provide troubleshooting tips for both platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments by referencing the PowerShell interface and its commands as the primary method for device monitoring and management. There are no equivalent Linux shell (bash) examples or references, and the documentation does not mention or provide guidance for Linux users, despite the cross-platform nature of container and edge workloads.

Recommendations:

Include equivalent Linux (bash) command examples alongside PowerShell commands for device monitoring and management.
Explicitly mention whether the 'dkr' commands can be run from a Linux shell or provide Linux-specific instructions if the workflow differs.
Clarify if the PowerShell interface is required or if SSH/Linux shell access is supported, and document both access methods if available.
Add a section or callouts for Linux users, ensuring parity in instructions and troubleshooting steps.
Review all included links and referenced documentation to ensure Linux users are not excluded or disadvantaged.

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 (such as Hyper-V and a YouTube link for adding a hard drive to a Hyper-V VM) without mentioning Linux or cross-platform equivalents. There are no Linux-specific instructions or examples, and the only virtualization workflow described is for Hyper-V, which is Windows-specific. This may leave Linux users without clear guidance for equivalent tasks.

Recommendations:

Provide Linux-specific instructions for increasing device capacity, such as adding a data disk to a KVM or VMware-based virtual machine.
Include links or references to documentation for managing disks in common Linux hypervisors (e.g., KVM, VMware, VirtualBox).
When referencing tools or workflows (like Hyper-V), also mention Linux alternatives and provide parity in examples.
Ensure that any included videos or guides have Linux equivalents or at least note the differences for Linux users.
Explicitly state supported operating systems and clarify any platform-specific steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias by exclusively providing instructions and command-line examples for Windows systems (e.g., using netsh via Command Prompt), referencing Windows-specific tools and documentation, and omitting any mention of Linux or cross-platform alternatives for exporting or managing Wi-Fi profiles. There are no Linux or macOS instructions or examples, and all workflow descriptions assume a Windows environment.

Recommendations:

Add equivalent instructions for exporting Wi-Fi profiles on Linux (e.g., using nmcli or editing NetworkManager configuration files) and macOS (e.g., using networksetup or security commands).
Include Linux/macOS command-line examples alongside Windows examples, or provide a cross-platform table or section.
Reference Linux and macOS documentation for Wi-Fi profile management, not just Windows/Intune links.
Clarify in the prerequisites or introduction that the instructions are Windows-specific, or explicitly state support for other platforms if available.
Where possible, provide generic XML profile templates and describe how to adapt or generate them on non-Windows systems.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page shows evidence of Windows bias by referencing Windows-specific tools (such as WSUS and the default use of the public Windows Update server) and omitting Linux equivalents or alternatives. There are no Linux-specific instructions or examples, and Windows tools are mentioned without noting cross-platform or Linux-compatible options. The documentation also assumes the use of the Azure portal (which is web-based and cross-platform), but for update and management scenarios, only Windows-centric solutions are referenced.

Recommendations:

Include information about how to configure update servers for Linux environments, such as using local Linux-based update mirrors or repositories.
Mention cross-platform or Linux-compatible alternatives to WSUS, or clarify if only Windows Update is supported.
Add explicit notes or examples for Linux users, especially for device management, network configuration, and certificate handling.
Where Windows tools or defaults are mentioned (e.g., WSUS), provide guidance for users in non-Windows environments or clarify platform limitations.
Ensure parity in instructions by including both Windows and Linux approaches where applicable, or state if a feature is Windows-only.

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 certificates in Windows File Explorer, and omitting 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 tools or commands mentioned.

Recommendations:

Provide equivalent Linux-based instructions for generating, converting, and installing certificates (e.g., using OpenSSL, Linux CLI commands).
Include screenshots or walkthroughs for certificate management on Linux systems (such as using Nautilus or command-line tools).
Mention and link to cross-platform tools (e.g., Azure CLI, OpenSSL) alongside Windows-specific tools like Azure PowerShell.
When referencing certificate conversion or installation, offer both Windows and Linux command examples and file paths.
Avoid assuming the client system is Windows; clarify that instructions apply to both Windows and Linux clients, or provide parallel sections for each.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates Windows bias by referencing only the PowerShell interface and the `Set-HcsMacAddressPool` cmdlet for configuring MAC addresses, with no mention of equivalent Linux commands or tools. There are no Linux shell or cross-platform examples provided for device configuration tasks, and the documentation assumes the use of Windows-native tools.

Recommendations:

Provide equivalent Linux shell commands or instructions for configuring MAC addresses and other device settings, if supported.
Mention whether the device management interface (such as PowerShell) is available or supported on Linux, or provide alternatives (e.g., Azure CLI, SSH).
Include cross-platform or OS-agnostic instructions where possible, especially for tasks like downloading configuration files or accessing the Kubernetes cluster.
If certain features are only available via PowerShell/Windows, explicitly state this limitation and suggest workarounds or alternatives for Linux users.

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 examples use PowerShell cmdlets, and the prerequisites explicitly require Windows 10/Server and PowerShell 5.1 or later. There is no mention of Linux or cross-platform alternatives, nor are there any Bash, CLI, or Linux-native instructions. The documentation assumes the user is on a Windows system and does not address Linux users at all.

Recommendations:

Add explicit guidance for Linux users, including supported platforms and any limitations.
Provide equivalent instructions using Azure CLI, Bash, or cross-platform PowerShell Core (pwsh), if supported.
Clarify whether the PowerShell module can be used on Linux/macOS with PowerShell Core, and provide installation steps for those environments.
If Windows-only tooling is required, state this clearly at the top and suggest alternative management approaches for Linux users (e.g., Azure CLI, REST API, or web UI).
Include at least one end-to-end example for Linux users or explicitly document the lack of Linux support.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation shows evidence of Windows bias, particularly in the clustering and network topology sections. Windows Server concepts and tools (such as NIC Teaming, Failover Clustering, Cloud Witness, File Share Witness) are referenced directly, with links to Microsoft Windows Server documentation. PowerShell is mentioned as the CLI method for certain configuration tasks, and no Linux or cross-platform CLI alternatives are provided. The documentation assumes familiarity with Windows networking patterns and does not mention or provide parity for Linux-based equivalents.

Recommendations:

Provide Linux-based or cross-platform CLI examples (e.g., using Azure CLI, Bash, or REST API) alongside or instead of PowerShell for configuration tasks.
When referencing clustering, networking, or witness concepts, include Linux-native equivalents (e.g., Pacemaker/Corosync for clustering, Linux bonding/teaming for NIC redundancy) or clarify if only Windows-based approaches are supported.
Avoid linking exclusively to Windows Server documentation for core concepts; instead, provide neutral explanations or link to cross-platform/Azure-native resources.
Explicitly state OS requirements or limitations if only Windows-based management is supported, and offer guidance for Linux administrators where possible.
Add notes or sections addressing how Linux administrators can perform similar tasks, or clarify if the device is managed entirely through the web UI regardless of admin OS.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows-based update mechanisms (Microsoft Update server, Windows Server Update Services/WSUS), defaulting to time.windows.com as the NTP server, and omitting any mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for Linux-based update servers (such as apt/yum repositories or Linux NTP defaults), nor is there any mention of Linux administration tools or patterns.

Recommendations:

Include examples or references for configuring update servers using Linux-based solutions (e.g., apt, yum, or local Linux update mirrors) if supported by the device.
Mention alternative, platform-neutral NTP servers (e.g., pool.ntp.org) alongside time.windows.com.
Clarify whether the device supports integration with non-Windows update infrastructures, and provide guidance if so.
Avoid defaulting to Windows-centric terminology and tools; provide parity for Linux environments where possible.
If the device is Windows-only, explicitly state this limitation to set expectations for Linux administrators.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits some Windows bias, particularly through the mention of the PowerShell cmdlet (`Set-HcsMacAddressPool`) as the only method for configuring MAC addresses on the device. There are no equivalent Linux command-line examples or references, and the only explicit tool for device management is Windows PowerShell. Additionally, the troubleshooting link for Kubernetes issues points to a PowerShell interface, with no mention of Linux-based alternatives. There are no Linux-specific instructions or parity in examples for device management.

Recommendations:

Provide equivalent Linux command-line instructions or tools for configuring device settings (e.g., MAC address pool), or clarify if such functionality is only available via PowerShell.
If device management is possible via SSH, REST API, or other cross-platform tools, include those options and examples.
When referencing troubleshooting or management interfaces, mention both Windows and Linux options, or state platform limitations explicitly.
Ensure that all examples and instructions are provided for both Windows and Linux environments where possible, or clarify platform-specific requirements.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (e.g., WSUS, Windows Update server), omitting Linux equivalents for update management, and generally assuming a Windows-centric environment for device management and network readiness. There are no explicit Linux or cross-platform examples or guidance for users who may be deploying from non-Windows systems.

Recommendations:

Include Linux equivalents for update server configuration, such as mentioning support for Linux-based update mirrors or repositories.
Reference cross-platform or Linux-compatible tools for network readiness checks, or clarify if the provided tools are Windows-only.
Provide explicit examples or notes for Linux/macOS users in sections that mention device connection, network configuration, or credential management.
Avoid assuming the use of Windows Update or WSUS by default; mention alternative update mechanisms where possible.
Ensure parity in instructions for device setup and management regardless of the administrator's operating system.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation primarily references PowerShell as the CLI tool for advanced configuration (e.g., changing Kubernetes workload profiles, pod/service subnets), with no mention of Linux shell equivalents or cross-platform CLI options. There are no Linux/Unix-specific instructions or examples, and the only command-line guidance points to PowerShell documentation. The UI instructions are platform-neutral, but the CLI guidance is Windows-centric.

Recommendations:

Provide equivalent Linux shell (bash) or cross-platform Azure CLI examples alongside PowerShell instructions for all command-line operations.
Explicitly mention and link to Linux-compatible tools (e.g., Azure CLI, az commands) where possible.
Clarify whether all configuration steps can be performed from non-Windows systems, and if not, provide workarounds or alternatives.
Add a section or note addressing Linux/macOS users, including any prerequisites or differences in workflow.
Ensure that all referenced scripts or automation steps are cross-platform or have Linux alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias primarily by only referencing Windows PowerShell for device management in the 'Next steps' section. There are no examples or references to Linux tools, Bash, or cross-platform CLI usage. The documentation does not mention or provide parity for Linux users, nor does it offer alternative instructions or links for non-Windows environments.

Recommendations:

Include equivalent instructions or links for managing Azure Stack Edge devices using Azure CLI or Bash scripts, which are cross-platform.
Add references to Linux and macOS environments where appropriate, ensuring that examples are not limited to Windows/PowerShell.
Where PowerShell is mentioned, also mention Azure CLI or REST API usage, and provide links or examples for those methods.
Review all 'Next steps' and guidance links to ensure Linux users are not excluded and have clear, supported pathways for device management.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (e.g., Windows Server Update Services, time.windows.com) and update patterns, without mentioning or providing Linux equivalents. The update server configuration focuses on Microsoft Update and WSUS, and the default NTP server is time.windows.com, a Microsoft service. There are no examples or guidance for Linux-based update or time synchronization solutions, nor is there mention of cross-platform alternatives.

Recommendations:

Include references to Linux-compatible update mechanisms or clarify if only WSUS/Microsoft Update are supported.
When mentioning NTP servers, provide examples of neutral/public NTP servers (e.g., pool.ntp.org) alongside time.windows.com.
If the device supports Linux-based management or integration, provide examples or notes for Linux admins (e.g., how to configure updates or time sync from a Linux environment).
Avoid assuming the environment is Windows-centric; mention cross-platform options where possible.
Add a note clarifying platform compatibility for update and time server configuration, especially if only Windows-based solutions are supported.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-native tools and patterns, such as BitLocker for encryption and Windows Defender Application Control (WDAC) for application whitelisting. Remote management is described only via PowerShell, with no mention of SSH or Linux-based management options. There are no Linux command-line examples or references to Linux-native security tools, and Windows terminology and technologies are presented as the default or only option.

Recommendations:

Provide equivalent Linux-based management instructions, such as using SSH for remote access and Linux-native command-line examples.
Mention and document Linux-compatible encryption solutions (e.g., LUKS/dm-crypt) if supported, or clarify if the device is Windows-only.
Include examples or references for managing the device from Linux or cross-platform environments, not just PowerShell.
If the device is Windows-specific, explicitly state this early in the documentation to set user expectations.
Reference or provide parity for security tools and practices common in Linux environments, such as auditd for logging or SELinux/AppArmor for application control, where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation displays a Windows-first bias by listing Windows-specific tools, paths, and troubleshooting steps before their Linux equivalents. Sections such as 'Errors seen in AzCopy for Windows' precede 'AzCopy for Linux', and Windows paths (e.g., C:\Windows\System32\drivers\etc\hosts) are mentioned first. Some recommendations reference Windows-specific services (e.g., time.windows.com) without Linux alternatives. There is also a lack of parity in example commands and troubleshooting steps for Linux, especially in sections not explicitly labeled for Linux.

Recommendations:

Present Linux and Windows instructions side-by-side or in parallel tables to ensure equal visibility.
When referencing file paths or system actions (e.g., editing hosts file), always provide both Windows and Linux examples together.
Avoid using Windows-specific services (e.g., time.windows.com) as the only example; mention Linux-appropriate NTP servers or general best practices for both OSes.
Include explicit Linux troubleshooting steps and example commands wherever Windows examples are given (e.g., importing certificates into the system store).
Where possible, use cross-platform tools and terminology, or clarify when a tool or step is OS-specific.
Review section ordering to avoid always listing Windows before Linux; consider alternating or grouping by task rather than OS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the recommended tool for managing blob tiers, and by providing monitoring commands only via the PowerShell interface. There are no equivalent Linux CLI or Bash examples, nor is there mention of cross-platform alternatives such as Azure CLI. This may leave Linux users without clear guidance for performing the same tasks.

Recommendations:

Provide equivalent Azure CLI (az) commands alongside or in place of PowerShell instructions for tasks such as setting blob tiers and monitoring.
Explicitly mention that both Windows and Linux clients are supported, and provide examples for both platforms where relevant.
Include Bash or shell script examples for common operations, especially for monitoring and management tasks.
Clarify when a feature is only available via PowerShell, and suggest workarounds or alternatives for Linux users if possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing PowerShell as the only command-line interface example for device reset, referencing Windows-centric tools and workflows, and omitting equivalent Linux instructions or tools. The local web UI is mentioned as an alternative, but no Linux CLI or shell examples are provided. Additionally, there is no mention of Linux-native tools or guidance for users operating from non-Windows environments.

Recommendations:

Add equivalent Linux shell (bash) or CLI instructions for device reset and management, alongside PowerShell examples.
Reference cross-platform tools or provide explicit guidance for Linux/macOS users where PowerShell or Windows-specific tools are mentioned.
Ensure that any downloadable scripts or automation steps are available in both PowerShell and bash (or other common Linux shells).
Where possible, use neutral language (e.g., 'command-line interface' instead of 'PowerShell') and provide parity in screenshots and UI walkthroughs for different platforms.
Explicitly state platform support and provide links to Linux/macOS documentation or troubleshooting guides.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased toward Windows environments. All troubleshooting steps, error messages, and examples reference Windows tools (e.g., net use, Event Viewer, Local Security Policy, Registry Editor) and Windows-specific concepts (Group Policy, Active Directory OUs, GPOs). There are no Linux or macOS equivalents provided for connecting to SMB shares, diagnosing issues, or adjusting authentication settings. The documentation assumes the user is on Windows and does not address cross-platform scenarios.

Recommendations:

Add Linux and macOS examples for connecting to SMB shares (e.g., using smbclient or mount.cifs).
Include troubleshooting steps for common Linux SMB errors and how to view relevant logs (e.g., dmesg, journalctl, /var/log/syslog, or /var/log/samba).
Document how to adjust SMB authentication settings on Linux (e.g., editing /etc/samba/smb.conf or mount options for NTLMv2).
Mention Linux equivalents for Windows tools (e.g., Event Viewer → journalctl/log files, net use → smbclient/mount.cifs).
Reorganize sections to present both Windows and Linux solutions in parallel, or clearly indicate which steps are OS-specific.
Clarify that the documentation is currently Windows-centric and provide links to cross-platform SMB troubleshooting resources if available.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a Windows bias by exclusively referencing Windows-specific security tools (e.g., Windows Defender Device Guard, BitLocker) and remote management via PowerShell. There are no mentions of Linux equivalents, nor are Linux-based management or security options discussed. All examples and instructions assume a Windows environment, with no parity for Linux users.

Recommendations:

Include information on whether the Azure Stack Edge Pro FPGA device supports Linux-based management interfaces (e.g., SSH, Linux CLI tools) and, if so, provide equivalent instructions.
If only Windows management is supported, explicitly state this limitation for transparency.
Mention Linux security tools or practices where applicable, or clarify if only Windows-based security features (like BitLocker and Device Guard) are available.
Provide examples or guidance for Linux users where possible, such as how to connect to the device or manage it from a Linux system.
Ensure that references to tools and procedures are platform-neutral where possible, or provide parallel instructions for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias: it repeatedly emphasizes that Data Box is a Windows-based device, all log event providers are Windows-specific (e.g., Microsoft-Windows-Kernel-General, BitLocker, PowerShell), and there are no references to Linux tools, patterns, or equivalents. No Linux or cross-platform log event examples or access methods are provided.

Recommendations:

Clarify early in the documentation that Data Box is a Windows-based appliance, but explicitly state whether Linux users can interact with the device or logs in any way.
If Data Box supports any Linux-compatible protocols (e.g., SMB, NFS, REST APIs), provide examples or references for Linux users.
If log access or troubleshooting can be performed from Linux systems (e.g., via SMB mounts, SCP, or REST API), add Linux command-line examples alongside any PowerShell or Windows instructions.
If the device is strictly Windows-only, add a note to set expectations for Linux users and suggest alternative workflows or tools where possible.
Review all event provider and tool references to see if there are cross-platform equivalents or abstractions that could be mentioned (e.g., general log formats, open standards).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias, particularly in the installation instructions for the Azure Developer CLI. The only command-line installation example provided uses PowerShell, with no mention of Bash or Linux/macOS alternatives. This may confuse or exclude Linux/macOS users. Additionally, the PowerShell installation command is presented before any cross-platform or alternative instructions, and there is no explicit guidance for non-Windows environments.

Recommendations:

Provide installation instructions for the Azure Developer CLI for all major platforms (Windows, Linux, macOS), including Bash/cURL examples alongside PowerShell.
Present platform-specific instructions in parallel tabs or sections (e.g., Windows, Linux, macOS), rather than only or first showing Windows/PowerShell.
Explicitly mention platform compatibility and link to official cross-platform installation guides.
Ensure all command-line examples are available in both PowerShell and Bash (or note when a command is platform-specific).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias in several areas: PowerShell scripts are the only provided example for building and pushing custom container images in both the ARM-Bicep and Terraform sections, with no equivalent Bash or Linux shell script examples. The instructions specifically reference 'Docker Desktop', a tool most commonly associated with Windows and Mac, and do not mention Linux-native Docker installations. There is no mention of running the scripts or workflows on Linux, nor are there alternative commands or guidance for Linux users. This may create barriers for users on Linux or those using non-Windows environments.

Recommendations:

Provide equivalent Bash (.sh) script examples for building and pushing images, or clarify if the provided scripts are cross-platform.
Include explicit instructions or notes for Linux users, such as how to run the scripts on Linux, or how to adapt PowerShell scripts for Bash.
Mention Linux-native Docker installation as an alternative to Docker Desktop.
Where PowerShell commands are shown, provide a Bash alternative or clarify platform compatibility.
Audit all prerequisites and steps to ensure they are not Windows-specific, or clearly indicate platform-specific requirements.
Consider adding a platform-agnostic section or table summarizing the steps for both Windows (PowerShell) and Linux (Bash).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily uses Azure CLI commands, which are cross-platform, but several command-line examples use Windows/PowerShell-specific syntax (e.g., variable assignment with $VAR and Write-Output), and there is no mention of Linux or macOS shell equivalents. This could confuse or exclude Linux/macOS users who expect bash syntax. Additionally, where scripting is shown, the examples default to Windows/PowerShell conventions without offering Linux alternatives.

Recommendations:

Provide both PowerShell and bash/zsh equivalents for variable assignment and output (e.g., $VAR=... vs VAR=...).
Explicitly mention that the Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
Where scripting or environment-specific commands are shown, use neutral syntax or show both Windows and Linux/macOS versions side by side.
Add a note or section for Linux/macOS users, clarifying any differences in command usage or syntax.
Avoid using Write-Output and PowerShell variable syntax in generic CLI documentation unless paired with bash equivalents.

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 (`), which are specific to PowerShell and not compatible with Bash or other Linux shells. There are no equivalent Bash/Linux shell examples provided, nor is there any mention of how to adapt the commands for Linux or macOS users. The documentation implicitly assumes a Windows/PowerShell environment throughout.

Recommendations:

Provide equivalent Bash/Linux shell examples for all commands that use PowerShell syntax, including variable assignment and line continuation.
Clearly indicate which commands are for PowerShell and which are for Bash, or provide side-by-side examples for both environments.
Avoid using Windows-specific syntax (such as backtick line continuations and $VAR assignment) in generic Azure CLI documentation, or at least supplement with POSIX-compliant alternatives.
Add a note at the beginning of the page clarifying which shell environment the examples target, and link to guidance for running Azure CLI on Linux/macOS.
Test all example commands in both Windows (PowerShell) and Linux (Bash) environments to ensure parity and usability.

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 tailored to PowerShell, which is more familiar to Windows users. While the text briefly mentions that Azure CLI can be used, it does not provide any CLI or Linux-native command examples, nor does it prioritize cross-platform tooling.

Recommendations:

Add equivalent Azure CLI examples for all deployment steps, using Bash syntax where appropriate.
Present both PowerShell and CLI/Bash examples side by side, or allow the user to toggle between them.
Explicitly mention that the Azure CLI is cross-platform and suitable for Linux/macOS users.
Ensure that instructions for opening and using the Cloud Shell clarify that both Bash and PowerShell environments are available.
Consider listing Azure CLI examples before or alongside PowerShell to avoid implicit Windows-first bias.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses Windows-specific tools and commands (PowerShell, Hyper-V, Windows network configuration dialogs) for configuring virtual switches, without providing any Linux equivalents or cross-platform guidance. All examples and instructions assume a Windows environment, and there is no mention of how to achieve similar results on Linux-based dev boxes or with Linux virtualization technologies.

Recommendations:

Provide parallel instructions for Linux environments, such as using libvirt/virt-manager, KVM, or other Linux virtualization tools.
Include example commands for creating virtual switches and NAT networks on Linux (e.g., using virsh, nmcli, or iptables/nftables).
Mention Linux prerequisites (e.g., KVM, bridge-utils) alongside Windows prerequisites.
Add screenshots or configuration steps for Linux network settings where applicable.
Clarify in the introduction that the guide is Windows-specific, or restructure to present both Windows and Linux options equally.

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 examples use PowerShell, and the prerequisites specifically mention installing Azure PowerShell on Windows. There are no examples or instructions for using Linux or Bash, and the image customization steps use Windows-specific tools (e.g., Chocolatey, PowerShell scripts). The template and gallery creation steps assume a Windows environment, and file paths use Windows conventions (e.g., c:/temp/mytemplate.txt). Azure CLI is mentioned only in passing, with no examples provided.

Recommendations:

Provide parallel examples using Azure CLI and Bash for Linux/macOS users.
Include instructions for installing Azure CLI and/or PowerShell on Linux and macOS.
Show how to create and edit template files using cross-platform file paths (e.g., /tmp/mytemplate.txt).
Offer a Linux-based image customization example (e.g., using shell scripts and apt/yum instead of PowerShell and Chocolatey).
Explicitly state which steps are Windows-specific and provide alternatives for Linux where possible.
Reorder or balance the 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 for Microsoft Dev Box architecture exhibits a Windows-centric bias. It exclusively references Windows management tools (e.g., Microsoft Intune), Windows device management, and Windows-specific identity services (Microsoft Entra join/hybrid join, Active Directory). There are no examples or mentions of Linux-based dev boxes, Linux management tools, or cross-platform development scenarios. The documentation assumes the dev box is a Windows VM and does not address Linux developer needs.

Recommendations:

Explicitly state whether Linux-based dev boxes are supported or not. If supported, provide equivalent guidance for Linux dev boxes, including management, connectivity, and configuration.
Include examples and references for managing Linux dev boxes (e.g., using SSH for connectivity, Linux configuration management tools, and relevant identity integration).
Mention cross-platform development scenarios and how Microsoft Dev Box can be used for non-Windows environments.
If only Windows is supported, clarify this limitation early in the documentation to set expectations for Linux users.
Provide parity in documentation structure and detail for both Windows and Linux environments if both are supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page for Microsoft Dev Box deployment is heavily oriented toward Windows environments. It references Windows-specific management tools (Microsoft Intune, Entra ID, Active Directory), and all device management and configuration examples assume Windows as the guest OS. There are no examples or mentions of Linux-based dev boxes, Linux management tools, or cross-platform considerations. Windows tools and patterns are discussed exclusively, with no Linux equivalents or alternatives provided.

Recommendations:

Explicitly state whether Linux-based dev boxes are supported or not. If supported, provide parallel guidance for deploying, configuring, and managing Linux dev boxes.
Include examples and documentation for managing Linux dev boxes, such as using Azure CLI, SSH, or Linux-native configuration management tools.
Mention Linux-compatible alternatives to Windows-specific tools (e.g., alternatives to Intune for Linux, or how to manage Linux device configuration and access control).
Provide sample customization tasks for Linux environments (e.g., using apt/yum/pacman for package installation instead of only WinGet/Chocolatey/PowerShell).
Clarify any limitations or differences in feature support between Windows and Linux dev boxes, if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows-centric bias. It references Windows-specific services (Windows 365, Windows activation, Group Policy), tools (Event Viewer, Windows logs), and troubleshooting steps that assume a Windows environment. There are no Linux-specific instructions, examples, or troubleshooting steps, and all references to client connectivity, troubleshooting, and configuration are framed in terms of Windows tools and patterns. Linux or cross-platform client scenarios are not addressed.

Recommendations:

Add explicit guidance for Linux and macOS clients, including how to connect to Dev Box using cross-platform Remote Desktop clients.
Provide troubleshooting steps using Linux tools (e.g., journalctl, system logs) alongside Windows Event Viewer instructions.
Include examples of network configuration and connectivity checks using Linux commands (e.g., curl, dig, netstat) in addition to or instead of Windows-specific tools.
Clarify which requirements and steps apply to all platforms, and which are Windows-specific.
Reference cross-platform documentation for remote desktop clients and network troubleshooting.
Mention and link to open-source or cross-platform alternatives where possible (e.g., FreeRDP, Remmina for Linux).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows bias by exclusively referencing PowerShell and WinGet as the primary scripting and package management tools for Dev Box customizations. There are no examples or mentions of Linux-based tools, shell scripts, or package managers (such as Bash, apt, or yum). The documentation assumes a Windows environment and does not address cross-platform or Linux developer scenarios.

Recommendations:

Include examples and guidance for using Linux shell scripts (e.g., Bash) as customization tasks, alongside PowerShell.
Document support for Linux-based Dev Boxes, if available, or clarify platform limitations.
Mention and provide examples for Linux package managers (such as apt, yum, or zypper) in addition to WinGet.
Ensure that references to scripting and automation tools are platform-neutral where possible, or provide parallel instructions for both Windows and Linux environments.
Explicitly state whether Dev Box customizations are intended only for Windows-based environments, and if so, recommend alternatives or workarounds for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page for Microsoft Dev Box exhibits a Windows-centric bias. It references PowerShell and Winget as primary scripting and package management primitives, with no mention of Linux equivalents (such as Bash or apt/yum). The focus is on Windows tools and workflows, and there are no examples or explicit support statements for Linux-based development environments or tools. WSL is mentioned only in passing, and always as a feature within a Windows context. There are no Linux-first or cross-platform examples or guidance.

Recommendations:

Include examples and references to Linux scripting and package management tools (e.g., Bash, apt, yum) alongside PowerShell and Winget.
Explicitly mention support for Linux-based Dev Box environments, if available, and provide parity in documentation for Linux users.
When describing features (such as debugging tasks or customization workflows), provide both Windows and Linux command examples.
Clarify whether features like the CLI, VS Code extension, and Dev Box customization are cross-platform, and document any limitations or differences.
Highlight WSL as a bridge for Linux workflows on Windows, but also address native Linux development scenarios if supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows bias by exclusively using PowerShell and Microsoft Graph PowerShell SDK for all command-line instructions, with no mention of Linux or cross-platform alternatives. The prerequisite to install PowerShell 7.x and the absence of bash, Azure CLI, or other Linux-native instructions further reinforce this bias. All examples and tool references assume a Windows-centric environment, and there are no notes or guidance for Linux or macOS users.

Recommendations:

Provide equivalent instructions using Azure CLI or Microsoft Graph CLI, which are cross-platform and commonly used on Linux and macOS.
Explicitly mention that PowerShell 7.x is cross-platform, and provide installation instructions for Linux and macOS, not just Windows.
Include bash or shell script examples where possible, or clarify if certain steps are Windows-only.
Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.
Where screenshots or UI navigation are shown, clarify if the experience is the same across platforms or note any differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page exhibits a strong Windows bias. All image examples are Windows-based (Windows 10/11, Visual Studio), and all technical instructions (such as sysprep, DISM, enabling features, and disk maintenance) reference Windows tools, commands, and PowerShell. There are no examples or guidance for creating or managing Linux-based images, nor are Linux-compatible tools or workflows mentioned. The requirements and optimizations are tailored exclusively for Windows environments.

Recommendations:

Include examples and requirements for Linux-based images (e.g., Ubuntu, CentOS) where supported by Azure Compute Gallery and Dev Box.
Provide equivalent Linux commands and workflows for image preparation, such as generalizing a Linux VM (using waagent -deprovision+user), resizing partitions, and optimizing images.
Mention Linux-compatible tools (e.g., bash, cloud-init) alongside Windows tools (PowerShell, DISM).
Clarify in prerequisites and requirements whether Linux images are supported or not. If not supported, state this explicitly to avoid confusion.
If Linux is supported, add screenshots and step-by-step instructions for Linux image creation and attachment, ensuring parity with the Windows-focused sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a strong Windows bias: all configuration steps, compatibility notes, and troubleshooting guidance are written exclusively for Windows environments. There are no Linux-specific instructions, examples, or considerations. All references to OS-level settings (such as enabling nested virtualization or disabling Memory Integrity) are Windows-specific, and the only OS type shown in CLI examples is Windows. There is no mention of Linux images, tools, or workflows.

Recommendations:

Explicitly state whether Linux-based dev boxes support hibernation, and if so, provide equivalent instructions for Linux images.
Include CLI examples for both Windows and Linux image types (e.g., using --os-type linux in az sig image-definition create).
If hibernation is not supported on Linux dev boxes, clearly document this limitation and provide guidance or alternatives for Linux users.
Add troubleshooting steps and compatibility considerations for Linux images, if applicable.
Balance references to Windows tools and settings with Linux equivalents (e.g., how to enable nested virtualization or manage power settings on Linux).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing Windows Terminal as the default shell environment and omitting any mention of Linux or cross-platform alternatives. All example commands are shown in the context of Windows, and there are no instructions for Linux or macOS users. The workflow assumes the user is operating in a Windows-based Dev Box, with no guidance for those using Linux shells or tools.

Recommendations:

Provide equivalent instructions and examples for Linux and macOS users, including how to launch the GPU shell from common Linux terminals (e.g., GNOME Terminal, Konsole, xterm) and macOS Terminal.
Clarify whether the devbox CLI and GPU features are available and supported on non-Windows Dev Boxes, and if so, document any differences in setup or usage.
Include screenshots or terminal output examples from Linux/macOS environments where applicable.
Avoid referencing Windows-specific tools (like Windows Terminal) as the only option; instead, use neutral language such as 'Open your terminal' and specify alternatives for different platforms.
Explicitly state platform requirements and support in the prerequisites section.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-centric bias by exclusively referencing Windows-specific tools and services (such as Microsoft Remote Desktop, Windows 365, and Windows Azure Service Management API) and by not providing any Linux-specific examples or guidance. All application references and scenarios assume a Windows environment, with no mention of Linux clients, tools, or workflows for accessing or managing Dev Boxes. There are no instructions or examples for Linux users, nor is there any discussion of cross-platform compatibility.

Recommendations:

Include examples and instructions for accessing Dev Boxes from Linux clients, such as using open-source RDP clients (e.g., FreeRDP, Remmina) or SSH where applicable.
Mention and document any differences or limitations when connecting to Dev Boxes from Linux or macOS environments.
Add a section or table listing supported platforms (Windows, Linux, macOS) for each access method and tool, with links to relevant client downloads and setup guides.
Provide parity in step-by-step instructions for configuring Conditional Access policies as they apply to non-Windows endpoints, including any required configuration for Linux devices in Intune.
Clarify whether Intune device compliance and Conditional Access policies can be enforced on Linux endpoints, and provide references to relevant documentation if supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation exclusively describes steps for connecting Android devices to a dev box using Windows tools and workflows. All instructions reference Windows-specific utilities (Device Manager, Local Group Policy Editor, cmd), and there are no examples or guidance for Linux or macOS users. This presents a strong Windows bias and lacks parity for developers on other platforms.

Recommendations:

Add equivalent instructions for Linux (and optionally macOS), including how to check device connectivity (e.g., using `lsusb`, `adb devices`), and how to manage USB permissions.
Describe how to configure USB redirection for remote desktop solutions commonly used on Linux (such as FreeRDP, Remmina, or xrdp), including relevant configuration files or command-line options.
Include troubleshooting steps for ADB device detection on Linux, such as adding udev rules for Android devices.
Clearly separate platform-specific instructions, labeling sections for Windows, Linux, and macOS, to ensure all users can follow the documentation.
Avoid assuming the use of Windows-only tools (like Device Manager or gpedit.msc) as the default or only method.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows environments, with all examples and instructions focused on PowerShell scripts and Windows-native tools like WinGet and Desired State Configuration (DSC). There is no mention of Linux scripting, shell examples, or cross-platform compatibility. The documentation assumes the use of Windows-based tooling and does not provide Linux equivalents or guidance for non-Windows environments.

Recommendations:

Include examples using Bash or shell scripts alongside PowerShell, especially for tasks that could be cross-platform.
Mention and provide guidance for Linux package managers (e.g., apt, yum) in addition to WinGet.
Clarify whether Dev Box supports Linux-based dev boxes and, if so, provide instructions and examples relevant to those environments.
Add a section or callout explaining how to author tasks for Linux or cross-platform scenarios, including YAML examples referencing non-Windows scripts.
Ensure that documentation for customizing dev boxes is inclusive of both Windows and Linux developer workflows.

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 recommended and described in detail as the default and enhanced experience, with legacy Remote Desktop (a Windows technology) also highlighted. There is no mention of Linux-native remote desktop clients or workflows, nor are there examples or guidance for Linux users. The only cross-platform mention is that the Windows App is available on macOS, iOS, Android, and web, but Linux is omitted. The CLI section references Azure CLI but does not provide parity examples or considerations for Linux environments.

Recommendations:

Explicitly mention and provide instructions for connecting to a dev box from Linux, including recommended Linux-compatible RDP clients (e.g., Remmina, FreeRDP, rdesktop).
Clarify whether the Windows App is available for Linux or, if not, suggest alternative methods for Linux users.
Add Linux-specific examples or notes in sections discussing remote desktop connections and CLI usage.
Ensure that all cross-platform tools are introduced together, or that Linux options are not omitted or relegated to secondary status.
Include troubleshooting tips or links specifically for Linux users who may encounter issues connecting to dev boxes.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes configuring Intune Endpoint Privilege Management for Windows-based dev boxes, with all examples, screenshots, and instructions focused on Windows 10/11. There is no mention of Linux or macOS support, nor are there any examples or guidance for non-Windows environments. All tools, UI elements, and file paths are Windows-specific.

Recommendations:

Clearly state in the prerequisites or introduction whether Endpoint Privilege Management is only supported on Windows, and if so, mention any plans or alternatives for Linux/macOS.
If Linux or macOS support is available or planned, provide equivalent configuration steps, examples, and screenshots for those platforms.
Include a comparison table or section outlining feature parity and differences between Windows and other operating systems.
If only Windows is supported, suggest alternative privilege management solutions for Linux (e.g., sudo policies, polkit) and reference relevant documentation.
Avoid using language that implies Windows is the default or only environment unless it is a hard product limitation, and make this explicit for cross-platform clarity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based workflows, terminology, and tools. All examples and instructions assume the use of the Azure portal and Microsoft Entra authentication, which are tightly integrated with Windows environments. There is no mention of Linux-based dev boxes, Linux authentication flows, or cross-platform considerations. The only referenced user experience is for Windows sign-on, and related content links are also Windows-specific.

Recommendations:

Explicitly state whether Linux-based dev boxes are supported for SSO and, if so, provide equivalent instructions and screenshots for Linux environments.
Include examples or notes for users connecting from Linux or macOS clients, addressing any differences in the SSO experience.
Reference or link to documentation about SSO for non-Windows environments if available, or clarify any limitations.
Avoid using Windows terminology exclusively (e.g., 'sign in to Windows') unless the feature is truly Windows-only; otherwise, use more neutral language such as 'sign in to your dev box.'
Add a section on troubleshooting or expected behavior for Linux users, if supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows environments, specifically Microsoft Dev Box and Visual Studio on Windows. All command-line examples use PowerShell or Windows-specific tooling (e.g., devenv.exe), and there are no Linux or cross-platform alternatives provided. The workflow assumes the use of Windows-based images and does not mention or support Linux-based development environments.

Recommendations:

Provide equivalent instructions and examples for Linux-based dev boxes, if supported.
Include cross-platform or Linux-specific commands for cache generation, or explicitly state if the feature is Windows-only.
Mention and document any limitations or lack of support for Linux environments up front.
If possible, suggest alternative workflows or tools for Linux users (e.g., using VS Code with similar caching or performance optimizations).
Balance the order of presentation so that Linux and Windows options are given equal prominence where both are supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (RDP app, Windows App) and troubleshooting steps that assume RDP usage. There are no Linux-specific examples or mentions of Linux remote desktop clients or workflows, and the only CLI example is generic (Azure CLI) without platform-specific guidance. The 'Windows App' is mentioned as a way to resume a dev box, but no Linux equivalent is provided.

Recommendations:

Include instructions or notes for Linux users, such as how to connect to a dev box using common Linux RDP clients (e.g., Remmina, FreeRDP).
When referencing the 'Windows App', also mention if there are equivalent applications or methods for Linux and macOS, or clarify if such options are unavailable.
In troubleshooting, provide guidance for Linux users (e.g., what errors might appear in Linux RDP clients and how to resolve them).
Review all screenshots and UI references to ensure they are not Windows-exclusive, or provide Linux/macOS equivalents where possible.
Explicitly state platform compatibility and any differences in experience between Windows, Linux, and macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing Windows-specific tools and workflows (such as Windows App, Remote Desktop client, and WSL) without providing equivalent instructions or examples for Linux or macOS users. The only mention of Linux is through WSL, which is a Windows feature, and there are no native Linux or macOS setup or connection examples. This may leave non-Windows users unclear on how to use Dev Box tunnels from their platforms.

Recommendations:

Add explicit instructions and screenshots for connecting to Dev Box tunnels from Linux and macOS clients, including any required tools or steps.
Mention and provide examples for using SSH or other cross-platform remote access methods where applicable.
Clarify whether the Dev Box extension and tunnel features are fully supported on Linux/macOS, and if not, specify any limitations.
Provide parity in documentation by listing Linux/macOS steps and tools alongside Windows ones, rather than only referencing Windows-specific features like WSL or Remote Desktop.
Include troubleshooting steps and FAQs relevant to Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows, with all troubleshooting steps, tools, and UI references specific to Windows (e.g., Task view, Registry Editor, Windows App). There are no Linux or cross-platform examples, and the instructions assume the user is on Windows. Linux users are not addressed, and no equivalent troubleshooting steps or tools are mentioned for non-Windows environments.

Recommendations:

Add a section clarifying whether Task view and Windows App are available or relevant on Linux or macOS. If not, state this explicitly.
If Linux or macOS clients can connect to dev boxes, provide equivalent troubleshooting steps for those platforms, or link to relevant documentation.
Mention any cross-platform alternatives or limitations for managing dev boxes from non-Windows systems.
If the Windows App is available on other platforms, include installation and troubleshooting instructions for those systems.
Avoid assuming all users are on Windows; structure the documentation to address multiple platforms where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Remote Desktop Protocol (RDP) connectivity, which is primarily associated with Windows environments. All troubleshooting steps, tool descriptions, and terminology (such as 'Windows Guest OS readiness') are Windows-centric. There are no references to Linux-based dev boxes, alternative remote access protocols (like SSH), or troubleshooting steps relevant to Linux users.

Recommendations:

Include guidance for Linux-based dev boxes, such as troubleshooting SSH connectivity issues.
Mention and provide examples for alternative remote access protocols (e.g., SSH, VNC) where applicable.
Clarify whether the Troubleshoot & Repair tool supports non-Windows dev boxes, and if not, provide equivalent troubleshooting steps for Linux environments.
Add parity in troubleshooting checklists (e.g., 'Linux Guest OS readiness') if Linux dev boxes are supported.
Ensure screenshots and terminology are inclusive of both Windows and Linux scenarios, or clearly state the scope if only Windows is supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily Windows-centric, providing step-by-step instructions and troubleshooting steps that exclusively reference Windows tools (e.g., Task Manager, reg.exe, Group Policy Editor, registry keys) and Windows-specific processes (msrdc.exe, msrdcw.exe). While there is a brief mention of macOS, there are no examples or guidance for Linux users, nor are Linux-compatible tools or workflows discussed. All registry and policy changes are described only for Windows, and the overall troubleshooting flow assumes a Windows environment.

Recommendations:

Add equivalent troubleshooting steps for Linux users, including how to check and restart RDP clients (such as Remmina, FreeRDP, or rdesktop) on Linux.
Provide Linux-specific commands for checking process status, killing hung RDP clients, and gathering logs (e.g., using ps, kill, journalctl, or syslog).
Include instructions for configuring RDP protocol settings (TCP/UDP) on Linux RDP clients, if supported.
Mention Linux equivalents for Windows tools (e.g., instead of Task Manager, use top/htop/ps; instead of reg.exe, explain relevant config file edits or client settings).
Ensure that all steps referencing registry or Group Policy changes are either accompanied by Linux/macOS alternatives or clearly marked as Windows-only, with parallel guidance for other platforms.
Consider restructuring the guide to address all major platforms (Windows, macOS, Linux) in each troubleshooting step, or provide platform-specific sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation lists Windows and PowerShell shells alongside Linux/Bash, but Windows environments (CMD, PowerShell) are mentioned as primary local shell options. PowerShell and CMD are referenced before or equally with Bash, and escaping guidance refers to backtick (PowerShell/Windows) before backslash (Bash/Linux). There are no explicit Linux-specific examples or troubleshooting steps, and Linux/Bash is not prioritized.

Recommendations:

Provide explicit Linux/Bash examples for escaping special characters, including common pitfalls with Bash.
List Linux/Bash environments before or alongside Windows/PowerShell when suggesting alternative shells.
Include sample error messages or command lines as they would appear in both Bash (Linux/macOS) and PowerShell/CMD (Windows).
Clarify which escape characters are used in which shells, with clear tables or examples for both Linux and Windows.
Reference Linux-native tools and environments (e.g., Ubuntu Terminal, macOS Terminal) in addition to Windows tools.

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 references are specific to Windows environments (e.g., Windows Update, Hyper-V, Windows Hello, certutil, PowerShell cmdlets). There are no examples or troubleshooting steps for Linux or macOS clients or dev boxes, nor are cross-platform tools or alternative workflows mentioned. The guidance assumes the user is operating in a Windows-centric environment.

Recommendations:

Add troubleshooting steps and examples for connecting to dev boxes from Linux and macOS clients, including using open-source RDP clients (e.g., Remmina, FreeRDP, rdesktop).
Include guidance for dev boxes running Linux (if supported), such as handling remote desktop protocols (e.g., xrdp, VNC) and relevant troubleshooting steps.
When mentioning tools like certutil or PowerShell cmdlets, provide equivalent commands or approaches for Linux/macOS (e.g., using OpenSSL, SSH, or native certificate management tools).
Avoid assuming Windows as the default environment; structure sections to address both Windows and non-Windows scenarios, or clearly indicate when a step is Windows-specific.
Reference cross-platform documentation or official Microsoft Remote Desktop clients for Linux/macOS where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows bias. It exclusively references Windows-specific tools and patterns, such as WinGet and PowerShell, and mentions User Account Control (UAC) prompts, which are unique to Windows. There are no examples or instructions for Linux or cross-platform environments, and no mention of Linux package managers or shell environments. The workflow assumes the use of Windows-based Dev Boxes and does not address Linux-based development scenarios.

Recommendations:

Include examples and instructions for customizing Linux-based Dev Boxes, if supported.
Mention Linux equivalents for tools (e.g., apt, yum, bash scripts) alongside WinGet and PowerShell.
Clarify whether the agentic workflow and imagedefinition.yaml support Linux environments, and provide relevant guidance if so.
Avoid assuming UAC prompts or other Windows-specific UX patterns; note differences for Linux users.
Provide at least one Linux-focused prompt or scenario in the natural language examples.
Explicitly state platform limitations if only Windows is supported, to set user expectations.

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), and references to PowerShell tasks, without any mention of Linux or cross-platform equivalents. There are no examples or guidance for Linux-based Dev Boxes or customization tasks, and all directory and command patterns are Windows-specific.

Recommendations:

Add parallel Linux examples, including directory paths (e.g., /home/dev/Workspaces) and shell commands (e.g., Bash).
Explicitly mention support for Linux-based Dev Boxes if available, and provide YAML examples that use Linux images and tasks.
Clarify whether the built-in tasks (like git-clone) are cross-platform, and if so, show usage in both Windows and Linux contexts.
Avoid using only Windows-specific tools or patterns (like PowerShell) in examples; include Bash or other common Linux shells where appropriate.
State any platform limitations or differences in secret handling between Windows and Linux Dev Boxes.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a strong Windows bias. All examples and built-in tasks focus exclusively on Windows tools such as PowerShell and WinGet, with no mention of Linux equivalents or support. The use of Desired State Configuration (DSC), a PowerShell technology, is highlighted as the primary method for configuration as code. There are no examples or guidance for Linux-based development environments, scripting, or package management tools. The documentation assumes Windows as the default and only supported platform for Dev Box customizations.

Recommendations:

Add explicit statements about platform support (Windows-only or cross-platform) early in the documentation.
If Linux-based dev boxes are supported, provide equivalent examples using Linux tools (e.g., Bash scripts, apt/yum/dnf/pacman for package management, cloud-init, Ansible, or shell scripts for configuration).
Include sample YAML image definition files that demonstrate Linux customizations, such as installing packages or configuring user environments.
Mention and document any limitations or differences in customization capabilities between Windows and Linux dev boxes.
If Linux is not supported, clearly state this to set user expectations and avoid confusion.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Windows-specific tools and workflows, such as WinGet and Desired State Configuration (DSC), without mentioning or providing equivalent Linux tools or examples. All customization examples and references are tailored to Windows environments, and there is no discussion of Linux-based dev boxes or how to customize them. This may exclude or confuse users who wish to use or manage Linux-based development environments.

Recommendations:

Add examples and guidance for customizing Linux-based dev boxes, including sample YAML files that use Linux package managers (e.g., apt, yum) or shell scripts.
Mention and provide parity for Linux equivalents to WinGet and DSC, such as using bash scripts, Ansible, or cloud-init for configuration management.
Explicitly state whether the customization features and Dev Box extension support Linux dev boxes, and if so, provide step-by-step instructions for those scenarios.
Ensure that references to tools and configuration approaches are not Windows-first; introduce cross-platform options or clarify platform-specific limitations.
Include screenshots or terminal output from Linux environments where applicable, not just Windows/VS Code on Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides detailed instructions and code samples for enabling diagnostic logging using the Azure Portal and Azure PowerShell, but does not include equivalent examples for Linux users, such as using the Azure CLI (az) or Bash scripts. The only command-line automation shown is via PowerShell, which is primarily a Windows-centric tool, though it is available cross-platform. There are no explicit Linux or Bash examples, and the documentation does not mention or prioritize Linux-native tools or workflows.

Recommendations:

Add equivalent step-by-step instructions and code samples for enabling diagnostic logging using the Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
Where PowerShell examples are provided, also provide Bash/Azure CLI examples side-by-side or in tabs to ensure parity for Linux users.
Explicitly mention that PowerShell is available cross-platform, but clarify that Azure CLI is often the default on Linux and macOS.
Review all sections for references to Windows-specific tools or workflows and ensure Linux alternatives are equally represented and easy to find.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation for Microsoft Dev Box demonstrates a Windows-centric bias. It exclusively references Windows tools and management patterns (such as Microsoft Intune, Windows device management, and expedited Windows updates), and does not mention Linux or provide Linux-specific examples or guidance. There is no discussion of Linux-based dev boxes, nor are there examples or instructions for configuring or managing non-Windows environments.

Recommendations:

Explicitly state whether Linux-based dev boxes are supported, and if so, provide examples and guidance for creating and managing Linux dev boxes.
Include Linux-specific management scenarios, such as integration with Linux configuration management tools or update mechanisms.
Balance references to Windows tools (like Intune and Windows updates) with equivalent Linux tooling or management strategies.
Add examples or screenshots that show Linux environments in the Dev Box workflow.
Clarify any limitations or differences in experience between Windows and Linux dev boxes, if applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows environments by providing only Azure PowerShell/Windows-centric deployment instructions and code examples. There are no equivalent Linux/bash/CLI examples, and the workflow assumes familiarity with PowerShell and Windows-based tooling. While Azure CLI is briefly mentioned, no concrete Linux or cross-platform instructions are provided.

Recommendations:

Provide equivalent deployment instructions and code examples using Azure CLI (bash) that work natively on Linux and macOS.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
Include sample Bash scripts or CLI commands for each PowerShell example, ensuring parity in guidance.
Reorder or parallelize instructions so that Linux/macOS (CLI/bash) and Windows (PowerShell) users are equally supported.
Clarify any platform-specific requirements or differences in the prerequisites and deployment steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows operating systems (Windows 10/11 Enterprise) and recommending Windows-based images (e.g., 'Visual Studio 2022 Enterprise on Windows 11 Enterprise'). There are no examples or mentions of Linux-based dev box images, nor are Linux tools or workflows discussed. The prerequisites and licensing requirements are also Windows-centric, with no guidance for Linux users or scenarios.

Recommendations:

Explicitly mention support for Linux-based dev box images if available, and provide examples of creating dev box definitions with popular Linux distributions (e.g., Ubuntu, CentOS).
Include screenshots and walkthroughs for selecting Linux images in the Azure portal.
Clarify in the prerequisites whether Linux-based dev boxes are supported, and if so, what licensing or identity requirements apply.
Provide guidance for configuring dev boxes for Linux development workflows, including common tools and environments.
Ensure parity in documentation by presenting both Windows and Linux options side-by-side where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-based licensing, images, and tools. The only dev box image mentioned is 'Visual Studio 2022 Enterprise on Windows 11 Enterprise + Microsoft 365 Apps 24H2', and all licensing requirements are for Windows. There are no examples or mentions of Linux-based dev boxes, nor any guidance for users who may want to use Linux environments. The documentation assumes a Windows-centric workflow and does not provide parity for Linux users.

Recommendations:

Include examples and instructions for deploying Linux-based dev box images, if supported.
List Linux-compatible licensing and requirements alongside Windows requirements.
Mention and provide guidance for using Linux tools and environments within Dev Box, if available.
Ensure screenshots and walkthroughs are not exclusively tied to Windows images or workflows.
Clarify whether Linux dev boxes are supported or not, and provide links to relevant documentation if they are.

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 use Windows-specific tools (PowerShell, WinGet), and there is no mention of Linux or cross-platform alternatives. The schema and task definitions assume PowerShell as the scripting environment, and all sample commands and built-in tasks are Windows-centric. There are no examples or guidance for Linux users or for using Bash, shell scripts, or Linux package managers.

Recommendations:

Add examples using Bash or shell scripts for task definitions, alongside PowerShell.
Document support (or lack thereof) for Linux-based dev boxes, and clarify if only Windows is supported.
If Linux is supported, provide equivalent built-in tasks for Bash and Linux package managers (e.g., apt, yum, dnf).
Include Linux image examples in the image attribute section.
Explicitly state OS compatibility for each built-in task and provide parity where possible.
Where only Windows is supported, clearly call this out 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 Windows bias by providing detailed instructions and scripts exclusively using Azure PowerShell, with no equivalent Bash or Linux-native scripting examples. The deployment sections and automation guidance are PowerShell-centric, and there is no mention of Linux command-line tools or cross-platform scripting approaches. While the Azure CLI is briefly mentioned as an alternative for ARM template deployment, no CLI or Bash examples are actually provided, and all code samples and step-by-step automation are in PowerShell.

Recommendations:

Provide equivalent Azure CLI (az) and Bash script examples for adding artifact repositories, including full scripts and parameter explanations.
Include Linux/macOS-specific instructions for running scripts and managing authentication, such as using environment variables for tokens.
When listing deployment options (e.g., ARM template deployment), present Azure CLI and Bash examples before or alongside PowerShell examples, not after.
Clarify that all automation steps can be performed on Linux/macOS as well as Windows, and provide any necessary prerequisites or differences.
Add a section or tab for Linux users, mirroring the structure used for PowerShell, to ensure parity and inclusivity.

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 examples for scripting and automation, with no equivalent examples for Linux users (e.g., Azure CLI, Bash). The prerequisites and automation sections focus exclusively on PowerShell, and the portal instructions do not clarify cross-platform considerations. There is no mention of Linux-native tooling or scripting approaches, and the only command-line automation path described is via PowerShell, which is traditionally associated with Windows environments.

Recommendations:

Add equivalent Azure CLI and/or Bash examples for adding artifacts to VMs, ensuring Linux users have clear, native instructions.
In the prerequisites section, mention both Azure PowerShell and Azure CLI as supported automation tools, with links to installation and usage guides for each.
Where scripting is discussed, provide both PowerShell and Bash/CLI scripts side-by-side or in tabs, so users on any platform can follow along.
Clarify in the introduction and relevant sections that both Windows and Linux VMs and users are supported, and provide examples that reflect this parity.
If certain features are only available via PowerShell, explicitly state this and provide workarounds or alternatives for Linux users where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing extensive PowerShell examples and cmdlet references, mentioning PowerShell tools and patterns first and in greater detail, and omitting explicit Linux/bash shell examples. While Azure CLI is mentioned, the CLI example is brief and lacks parity with the PowerShell guidance. There is no discussion of Linux-native tools or scripting environments, and the workflow assumes familiarity with Windows/PowerShell conventions.

Recommendations:

Provide equivalent bash/Azure CLI examples for all PowerShell commands, including how to retrieve object IDs and deploy ARM templates from Linux/macOS environments.
List Azure CLI and bash examples before or alongside PowerShell examples to avoid Windows-first ordering.
Reference cross-platform tools (e.g., uuidgen for GUID generation) and explain how to perform prerequisite steps (like generating GUIDs or retrieving object IDs) in Linux/macOS shells.
Clarify that both PowerShell and CLI commands can be run on any OS, and provide guidance for installing and using Azure CLI and PowerShell Core on Linux/macOS.
Add notes or sections specifically addressing Linux/macOS users, including any differences in command syntax or environment setup.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows bias. All examples and scripts are provided in PowerShell, with no mention of Linux or cross-platform alternatives. The tooling and patterns referenced (e.g., IIS, RDGatewayFedAuth.msi, System Center VMM, RDP file workflow) are Windows-centric. There is no guidance for Linux-based remote desktop solutions or how to connect from Linux clients. The documentation assumes the use of Windows infrastructure and tools throughout.

Recommendations:

Provide equivalent instructions and scripts for Linux environments, such as using OpenSSL for certificate creation and Bash/Azure CLI for automation.
Include examples of connecting to lab VMs using open-source RDP clients available on Linux (e.g., xfreerdp, Remmina), and clarify token authentication compatibility.
Mention and, where possible, support Linux-based gateway solutions (such as xrdp or guacd) or clarify if only Windows gateways are supported.
When listing tools or scripts, present cross-platform or Linux options alongside Windows/PowerShell examples, not just after them.
Explicitly state any limitations or lack of support for Linux clients or servers, so users can plan accordingly.
Reference Azure Bastion as a cross-platform alternative more prominently, and provide a comparison table for remote access options across OSes.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation displays a Windows bias in several ways: Windows is the default OS for cluster VMs, certificate creation instructions are provided only for PowerShell (with a .ps1 script), and there are no equivalent Linux/bash examples or references to Linux tooling for certificate management. The documentation mentions that clusters can be created on Linux or Windows, but all concrete steps and scripts are Windows-centric.

Recommendations:

Provide Linux/bash equivalents for certificate creation, such as using OpenSSL, alongside the PowerShell example.
Explicitly mention that the .ps1 script is for Windows and offer a Linux alternative or link to Linux instructions.
When describing the OS selection, avoid making Windows the default or at least give equal prominence to Linux.
Include screenshots or CLI steps that demonstrate the process on a Linux system where applicable.
Reference Linux tools (e.g., bash, OpenSSL) in parallel with Windows tools (e.g., PowerShell, .ps1 scripts).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by emphasizing Windows client operating systems, Windows-specific licensing (MSDN, Visual Studio subscriptions), and RDP as a primary remote access method. There is no mention of Linux-specific scenarios, tools, or licensing, and no examples are provided for Linux VM setup or access, despite Azure DevTest Labs supporting both Windows and Linux environments.

Recommendations:

Include explicit references to Linux VM support in DevTest Labs, both in prerequisites and example scenarios.
Provide guidance on using Linux images, including licensing and marketplace options.
Mention SSH as a primary remote access method for Linux VMs, and provide parity in remote access instructions (e.g., 'connect via RDP (for Windows) or SSH (for Linux)').
List Linux development/test scenarios alongside Windows scenarios in all relevant sections.
Reference open source tools and workflows (e.g., GitHub, GitLab, Jira, Slack) in addition to Microsoft tools for collaboration.
Add example proof-of-concept plans that include Linux-based teams or mixed OS environments.

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 automation examples using Azure PowerShell, referencing only PowerShell and not Azure CLI or Bash. Prerequisites and instructions focus on PowerShell, and there are no examples or guidance for Linux/macOS users or for using cross-platform tools like Azure CLI. Microsoft account documentation links also point to Windows Server resources, further reinforcing the Windows-centric approach.

Recommendations:

Add equivalent Azure CLI examples for adding users to lab roles, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash script snippets or instructions for Linux/macOS users where appropriate.
Reference Microsoft account documentation that is not Windows Server-specific, or provide alternative guidance for non-Windows environments.
In the prerequisites and tool installation sections, mention both Azure PowerShell and Azure CLI, and provide links and instructions for each.
Ensure that the order of presentation does not always place Windows/PowerShell first; consider alternating or presenting cross-platform methods before Windows-specific ones.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by using a Windows 11 Pro image as the example for VM creation, without mentioning or providing a Linux-based example. In the 'Copy existing Azure VMs into a lab' section, only a PowerShell script is referenced, with no mention of a Linux/CLI/bash alternative. The documentation also lists PowerShell before Azure CLI in the introductory paragraph, and does not provide parity in examples or tooling for Linux users.

Recommendations:

Include a parallel example using a popular Linux image (e.g., Ubuntu) when demonstrating VM creation, and note any Linux-specific settings or differences.
In the 'Copy existing Azure VMs into a lab' section, provide an equivalent Azure CLI or bash script example for Linux users, or at least reference one if available.
When listing automation options (PowerShell, CLI, ARM template), alternate or balance the order, or explicitly state that both Windows and Linux users are supported equally.
Where screenshots or instructions are OS-specific, clarify applicability or provide Linux alternatives.
Ensure artifact examples or references include both Windows and Linux use cases.

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 examples for artifact installation commands, referencing Windows-specific tools (such as Chocolatey), and using a sample artifact that is explicitly for Windows. There are no equivalent Linux shell script examples, nor is there a Linux-focused artifact sample or command. The guidance and screenshots are centered around Windows patterns, with Linux support mentioned only as an option in parameter values.

Recommendations:

Add parallel Linux examples throughout the documentation, such as showing a bash shell script artifact and corresponding 'commandToExecute' using 'bash' or 'sh'.
Include a sample artifactfile.json and script for a Linux VM (e.g., installing a package with apt or yum).
When referencing repositories or samples, provide both Windows and Linux artifact examples, or at least mention where Linux examples can be found.
Balance the order of presentation so that Linux and Windows are treated equally (e.g., do not always show Windows first).
Mention Linux-specific tools or patterns (such as apt, yum, bash scripting) alongside Windows tools like PowerShell and Chocolatey.
Ensure screenshots and folder structures are not Windows-centric, or provide Linux equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing Windows virtual machines and tools before or instead of Linux equivalents. The only direct link to VM documentation is for Windows VMs, and examples of artifacts mention Windows-specific tools like Visual Studio and Fiddler, with no mention of Linux tools or distributions. There are no Linux-specific examples, links, or references, and the documentation does not clarify that Linux VMs and artifacts are equally supported.

Recommendations:

Include references and links to both Windows and Linux VM documentation (e.g., add a link to 'Linux virtual machines in Azure').
Provide examples of artifacts and tools relevant to Linux environments (e.g., Git, Apache, NGINX, or other common Linux software).
Explicitly state that DevTest Labs supports both Windows and Linux VMs, and provide parity in examples and explanations.
When listing base images or custom images, mention both Windows and Linux options.
Ensure that any step-by-step guides or referenced templates include Linux scenarios alongside Windows ones.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing detailed automation instructions and scripts exclusively for Azure PowerShell, with no equivalent Bash or Linux-native examples. While the Azure CLI is briefly mentioned, all step-by-step automation is shown using PowerShell, and the script is written in a Windows-centric style. There are no Linux/Bash shell examples or references to cross-platform scripting approaches.

Recommendations:

Provide equivalent automation instructions and sample scripts using Azure CLI with Bash, suitable for Linux and macOS users.
Include explicit Bash/Linux command-line examples for deploying ARM templates and managing DevTest Labs environments.
Ensure that references to automation tools (PowerShell, CLI) are presented in parallel, with neither platform prioritized over the other.
Add notes or sections clarifying cross-platform compatibility and any OS-specific considerations.
Where screenshots or UI instructions are given, clarify that the Azure portal is web-based and platform-agnostic.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page shows a moderate Windows bias. PowerShell is mentioned as an alternative method for creating custom images, and uploading VHDs via PowerShell is listed as a primary option. Windows-specific tools (PowerShell, sysprep) are referenced directly, while Linux equivalents (deprovision) are mentioned but with less prominence. The ordering of upload methods and examples tends to favor Microsoft/Windows tools, and there are no explicit Linux CLI or cross-platform examples (e.g., Bash, Azure CLI).

Recommendations:

Add explicit examples and links for using Azure CLI (az) and Bash scripts to upload VHDs and create custom images, ensuring parity with PowerShell instructions.
List Linux and cross-platform upload methods (e.g., AzCopy, Azure CLI) before or alongside Windows/PowerShell options to avoid implicit prioritization.
Provide more detailed guidance for Linux users, such as step-by-step instructions for preparing and uploading VHDs from Linux environments.
Where Windows-specific tools (like sysprep) are mentioned, ensure the Linux equivalent (deprovision) is described with equal detail and visibility.
Consider including screenshots or terminal output from Linux environments to balance the visual representation.

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 Bash, Azure CLI, or Linux-friendly example. The automation section is Windows/PowerShell-centric, and there is no mention of cross-platform tools or alternatives for Linux/macOS users.

Recommendations:

Add an Azure CLI (az) example for deleting all VMs in a lab, as Azure CLI is cross-platform and commonly used on Linux/macOS.
Include Bash script examples or instructions for Linux users where automation is discussed.
Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, and provide installation guidance for non-Windows systems.
Ensure that any automation or scripting guidance is presented with parity for both Windows and Linux users, ideally showing both PowerShell and CLI/Bash alternatives side by side.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page references executing PowerShell scripts and REST APIs as ways to interact with Azure DevTest Labs in CI/CD pipelines, but does not mention or provide examples for Linux shell scripting or other Linux-native tools. The mention of PowerShell comes before Azure CLI, and there are no explicit Linux or cross-platform examples, which may give the impression of a Windows-centric workflow.

Recommendations:

Explicitly mention Bash/shell scripting as an option alongside PowerShell for automation tasks.
Provide examples using both PowerShell and Bash/Azure CLI to demonstrate cross-platform compatibility.
List Azure CLI before or alongside PowerShell to avoid the perception of Windows-first bias.
Include references to Linux-based build agents and workflows in the context of DevTest Labs integration.
Ensure that all scripting and automation guidance is presented in a platform-neutral way, or with parallel examples for 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 and Azure PowerShell cmdlets for all examples and instructions, with no mention of Linux, Bash, Azure CLI, or cross-platform alternatives. All command-line examples are in PowerShell, and there is an explicit requirement to install Azure PowerShell. No Linux or macOS-specific guidance or parity is provided.

Recommendations:

Provide equivalent examples using Azure CLI, which is cross-platform and works on Windows, Linux, and macOS.
Include Bash script examples alongside PowerShell, or at least mention that the steps can be performed using Azure CLI on Linux/macOS.
Add a section or note clarifying that these tasks can also be accomplished on non-Windows platforms, and link to relevant Azure CLI documentation.
Rephrase instructions to avoid assuming the user is on Windows (e.g., avoid 'PS C:\>' prompts or reference to Windows file paths).
List both PowerShell and CLI approaches, or provide a table comparing the commands for both environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates several types of Windows bias. PowerShell is the only scripting example mentioned for automation (e.g., adding users, deleting VMs), with no reference to Bash, CLI, or Linux scripting alternatives. In the 'Lab creation' section, all code sample links reference Windows VMs (e.g., Bicep, ARM, Terraform templates for Windows), with no mention of Linux VM creation. Tools and artifacts examples are Windows-centric (e.g., Visual Studio, Fiddler), and Windows-specific patterns (Active Directory domain join) are referenced without Linux equivalents. Linux is only mentioned in passing, with no concrete examples or parity in instructions.

Recommendations:

Provide parallel examples for Linux VM creation using Bicep, ARM templates, and Terraform, and link to those alongside Windows examples.
Include automation instructions and scripts using Azure CLI and Bash, not just PowerShell.
Mention and provide examples of Linux tools and artifacts (e.g., installing common Linux development tools, editors, or agents).
When referencing domain join or other Windows-specific features, also mention Linux equivalents (e.g., joining to LDAP or using SSH keys).
Ensure that all user-facing instructions and quickstarts are available for both Windows and Linux scenarios, and present them with equal prominence.

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 are native to Windows environments. There is no mention of how to perform the same steps on Linux or macOS, and the only code samples and automation guidance are Windows-centric.

Recommendations:

Provide a Bash (or POSIX shell) script example that performs the same deployment steps, using az CLI and standard Linux shell conventions.
Explicitly mention that the steps can be performed from Linux/macOS as well as Windows, and clarify any OS-specific requirements.
Where possible, use cross-platform scripting (e.g., az CLI commands in Bash) in the main flow, and move PowerShell-specific automation to a separate section or appendix.
Ensure that all prerequisite tools and instructions are described in a cross-platform manner, including installation steps for Linux/macOS.
Add notes or callouts for any steps that are different or require adaptation on Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a Windows bias by using Windows 11 Pro as the default example for VM creation, referencing 'Windows VM' in screenshots and instructions, and omitting any explicit mention or example of Linux-based VMs. There are no Linux-specific instructions, screenshots, or clarifications about hibernation support or differences for Linux VMs. The documentation also uses patterns and language (such as 'Connect' options) that are typically associated with Windows environments.

Recommendations:

Include explicit examples and screenshots for creating and managing Linux VMs with hibernation enabled.
Clarify whether hibernation is supported for Linux distributions, and if so, list supported versions and any caveats.
When referencing VM images, provide both Windows and Linux options (e.g., 'The following instructions use Windows 11 Pro or Ubuntu 22.04 LTS').
Avoid referring to 'Windows VM' in a way that implies exclusivity; use neutral terms or mention both Windows and Linux where appropriate.
If there are differences in the hibernation process or prerequisites for Linux VMs, document them clearly.
Ensure screenshots and instructions are balanced between Windows and Linux scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by presenting the Windows RDP connection method before the Linux SSH method, and by providing a detailed, step-by-step instruction for Windows users (including a pre-configured RDP file download), while Linux users are only given a brief description without a concrete SSH command example. There is also a lack of parity in actionable examples for Linux users.

Recommendations:

Present Windows and Linux instructions in parallel, or alternate which is presented first.
Provide explicit SSH command-line examples for Linux users (e.g., ssh username@contoso.westus3.cloudapp.azure.com -p 65013).
Include screenshots or step-by-step instructions for Linux SSH connections, similar to the RDP instructions for Windows.
Avoid assuming the user is on Windows; mention cross-platform tools where possible.
Clarify that SSH can be used from Windows, macOS, or Linux, and provide guidance for each.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively mentioning Windows-centric tools and patterns, such as the Remote Desktop Gateway (RDP) and referencing Windows Server documentation. There are no examples or mentions of Linux-based remote access (e.g., SSH), nor are Linux administration tools or patterns discussed. Automation examples mention PowerShell first, and there is no parity in examples or guidance for Linux environments.

Recommendations:

Include Linux-based remote access options (e.g., SSH bastion hosts, Linux jump boxes) alongside or before Windows RDP solutions.
Reference Linux documentation and tools (such as OpenSSH, Linux firewall configuration) when discussing connectivity and security.
Provide automation examples using Bash scripts and Azure CLI, not just PowerShell.
Explicitly mention that DevTest Labs supports both Windows and Linux VMs, and provide Linux-specific considerations where relevant.
Balance references to Windows and Linux tools and patterns throughout the documentation to ensure cross-platform parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing detailed, step-by-step troubleshooting instructions and examples exclusively for Windows virtual machines, including PowerShell commands, Windows file paths, and screenshots of Windows tools (File Explorer, Command Prompt). Linux troubleshooting is only referenced via external links, with no in-page examples or equivalent walkthroughs. Windows tools and patterns are mentioned first and in detail, while Linux users are directed elsewhere.

Recommendations:

Provide parallel Linux examples for all troubleshooting steps, including equivalent Bash/CLI commands and Linux file paths.
Include screenshots or terminal output from Linux environments where Windows screenshots are shown.
Add in-page instructions for locating and inspecting Custom Script Extension logs on Linux VMs, not just a link.
Show how to check the Azure VM Agent status and logs on Linux, with sample log snippets.
Demonstrate how to run artifact installation scripts on Linux (e.g., using bash or sh), including how to handle script parameters and errors.
Ensure that references to tools (e.g., File Explorer, Command Prompt) are paired with their Linux equivalents (e.g., file managers, terminal).
When mentioning PowerShell or Windows-specific commands, immediately follow with the Linux/CLI equivalent, not just a reference link.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references Azure PowerShell as a primary interface for managing DNS records (e.g., for TXT records and Etag handling), without mentioning or providing parity for Linux-native tools or CLI usage. There are no explicit Linux or cross-platform command-line examples, and the only tooling called out by name is PowerShell, which is most closely associated with Windows environments.

Recommendations:

Include Azure CLI examples alongside or instead of PowerShell, as Azure CLI is cross-platform and widely used on Linux.
When referencing management interfaces, mention both PowerShell and CLI equally, and provide links or examples for both.
Avoid implying PowerShell is the default or only scripting interface; clarify that both PowerShell and CLI are supported.
If discussing tooling-specific behaviors (such as Etag handling), describe how these work in both PowerShell and CLI contexts.
Add explicit Linux/Bash shell examples where relevant, especially for common DNS management tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. It explicitly states that AzCopy is a Windows-only utility, provides only Windows Command Prompt and PowerShell instructions and screenshots, and omits any Linux or cross-platform alternatives or examples. The instructions assume a Windows environment throughout, with no mention of how Linux or macOS users could perform the same tasks.

Recommendations:

Update the documentation to reflect that modern versions of AzCopy (v10 and above) are cross-platform and available for Windows, Linux, and macOS.
Provide Linux and macOS installation instructions and example commands (e.g., using bash shell).
Include screenshots or terminal examples from Linux environments where appropriate.
Avoid language that implies exclusivity to Windows unless it is truly the case; clarify version-specific limitations if any.
If PowerShell is referenced, also provide equivalent bash or shell commands for Linux/macOS users.
Link to cross-platform AzCopy documentation and downloads.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page, while stating that Azure Storage Explorer is cross-platform, demonstrates a Windows bias in several ways. It directs users to obtain the storage account name by following a workflow that explicitly references PowerShell and the 'Upload a VHD using PowerShell' link, with screenshots and instructions focused on the Windows Azure portal experience. There are no Linux- or macOS-specific examples, nor are alternative CLI-based workflows (such as using Azure CLI or azcopy) mentioned. The related content section also prioritizes PowerShell-based guidance.

Recommendations:

Provide explicit instructions or examples for Linux and macOS users, including screenshots where appropriate.
Include alternative workflows using Azure CLI or azcopy for users who may not use PowerShell or the Azure portal.
Avoid referencing PowerShell as the primary or only method for obtaining required information (such as the storage account name); instead, describe a platform-neutral method or provide parallel instructions for different OSes.
Balance related content links by including Linux/macOS/CLI-based documentation alongside PowerShell resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows Server VM examples, providing detailed PowerShell automation instructions, and referencing Windows-centric tools and workflows. There is a lack of Linux-specific examples or guidance, and Linux VM deployment is not mentioned alongside Windows. PowerShell is emphasized for automation, with no mention of Bash or Linux shell scripting alternatives.

Recommendations:

Include Linux VM deployment examples alongside Windows Server VM examples in the ARM quickstart section.
Provide equivalent Bash or Azure CLI scripts for automation tasks currently demonstrated only with PowerShell.
Reference Linux-compatible tools and workflows, such as Bash scripting, when discussing automation.
Ensure that instructions and screenshots are not Windows-specific, or provide Linux equivalents where appropriate.
Explicitly mention that ARM templates can be used to deploy both Windows and Linux VMs, and provide links to relevant Linux template samples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation primarily uses Azure CLI commands, which are cross-platform, but there are subtle Windows biases. Cloud Shell (browser-based, but often associated with Windows users) is referenced heavily, and file upload instructions are written in a GUI-centric way. There are explicit notes about escaping characters in Bash and PowerShell, but the main recommendation is to use Bash, with PowerShell only mentioned as a caveat. There are no explicit Linux-specific instructions or examples (e.g., using Linux-native tools or file paths), and the workflow assumes a Windows-style user experience (e.g., manual file downloads and uploads via browser).

Recommendations:

Provide explicit Linux shell (bash) examples for file operations, such as using wget or curl to download model files directly from GitHub, instead of instructing users to manually copy and paste file contents.
Include Linux-native file path examples (e.g., /home/user/Room.json) alongside or instead of generic file names.
Offer instructions for uploading files to Cloud Shell using CLI tools (e.g., az storage file upload, scp) in addition to GUI-based upload steps.
When discussing escaping characters, provide both Bash and PowerShell examples side by side, and clarify which applies to which environment.
Add a section or callout for Linux/macOS users, highlighting any differences in workflow or commands, to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a moderate Windows bias. While the Azure CLI is correctly described as cross-platform and most command-line examples are OS-agnostic, the documentation repeatedly references Windows-specific tools, paths, and usage patterns before or instead of Linux equivalents. For example, the location of DNS zone files is given for Windows DNS with explicit paths and UI instructions, while the BIND/Linux equivalent is mentioned only briefly. The only explicit example for verifying DNS records uses the Windows Command Prompt and nslookup, with no mention of Linux/macOS alternatives (e.g., dig or nslookup on Unix shells). There are no shell-specific examples for Linux/macOS users.

Recommendations:

When mentioning the location of DNS zone files, provide equal detail for both Windows DNS and BIND/Linux (e.g., typical BIND zone file locations such as /etc/bind/).
When giving verification steps, include both Windows (cmd) and Linux/macOS (bash) examples, e.g., show how to use nslookup and dig from a Unix shell.
Avoid phrases like 'Use Windows Command Prompt...' unless also providing the equivalent for other platforms.
Where file paths are referenced, show both Windows and Unix-style path examples.
Consider adding a short section or callout noting that all Azure CLI commands work identically on Windows, Linux, and macOS, and provide shell-appropriate syntax where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing special instructions and examples for escaping special characters in PowerShell, without mentioning or providing equivalent guidance for Linux shells (e.g., Bash). The only shell-specific examples are for PowerShell, and there is no discussion of how to handle these cases on Linux or macOS. This may confuse or disadvantage users on non-Windows platforms.

Recommendations:

Add equivalent examples and instructions for escaping special characters in common Linux shells (e.g., Bash, Zsh) and macOS.
When discussing shell-specific behavior, present Linux/Bash guidance alongside or before PowerShell instructions to ensure parity.
Explicitly state that the examples are for PowerShell and provide a clear section for Linux/macOS users.
Consider including a table or side-by-side examples showing how to escape special characters in both PowerShell and Bash.
Audit other sections for similar shell-specific instructions and ensure cross-platform coverage.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. All step-by-step instructions and screenshots are based on Visual Studio, a Windows-centric IDE, with no mention of cross-platform alternatives (e.g., VS Code, CLI-based deployment). The only code samples referenced are C# and PowerShell, both of which are traditionally Windows-first technologies. The walkthrough for creating a service principal lists Azure CLI, PowerShell, and Portal, but the rest of the guide assumes Visual Studio usage. There are no Linux/macOS-specific instructions, nor are there examples for deploying or developing the sample from non-Windows environments. The 'ApplyWindowsUpdateArtifact' function and artifact are Windows-specific, and there is no mention of Linux VM management or update artifacts.

Recommendations:

Provide equivalent instructions for developing, building, and deploying the sample using cross-platform tools such as Visual Studio Code, Azure CLI, and/or GitHub Actions.
Include Linux/macOS-specific steps for cloning, building, and deploying the Azure Functions sample.
Offer examples of managing Linux VMs in DevTest Labs, including applying Linux update artifacts, alongside the Windows Update example.
Reference and provide links to Linux-compatible tools and workflows, such as using the Azure CLI or VS Code for function development and deployment.
Add code samples or walkthroughs for Python or JavaScript Azure Functions, which are popular and cross-platform.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell-based examples for disk migration and referencing Windows-specific tools and patterns (e.g., PowerShell, Windows VM with RDP) before Linux equivalents. The only command-line example for moving disks uses PowerShell, and while there is a brief mention of Linux VMs (with SSH port 22), there are no Linux shell (bash/CLI) examples for key steps such as using AzCopy or managing disks. The guidance for swapping OS disks links to a Windows/PowerShell article, with no Linux/CLI equivalent. The overall workflow assumes familiarity with Windows tools and environments, with Linux parity lacking in practical, step-by-step guidance.

Recommendations:

Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for disk migration and AzCopy usage.
Include explicit Linux VM management steps and examples (e.g., swapping OS disks using Azure CLI or Bash).
When showing code snippets for VM network configuration, present Linux and Windows examples side by side, not with Windows first.
Reference both Windows and Linux documentation for advanced tasks (e.g., swapping OS disks) to ensure parity.
Review all instructions to ensure that Linux users are equally supported and not required to translate PowerShell or Windows-centric steps themselves.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows bias by exclusively referencing Azure PowerShell scripts and PowerShell-based automation, without mentioning or providing examples for Linux shell scripts or cross-platform alternatives. The tools and patterns described (e.g., PowerShell, VSTS/DevOps extensions) are primarily Windows-centric, and there is no discussion of Linux-native scripting or automation options. No Linux or Bash examples are provided, and the documentation assumes the reader is using Windows tooling.

Recommendations:

Include equivalent Bash or Azure CLI script examples for Linux users alongside PowerShell scripts.
Explicitly mention cross-platform compatibility of the solution, and clarify which parts are Windows-specific.
Reference and link to Linux-friendly tools or extensions where available.
Rephrase sections to avoid assuming PowerShell is the only or primary automation method.
Add a section or note describing how Linux users can implement or adapt the image factory process.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exclusively uses PowerShell scripts and Azure Automation runbooks, which are Windows-centric tools. There are no examples or instructions for Linux users, such as Bash, Azure CLI, or Python runbooks. The workflow and tooling described are tailored for Windows environments, with no mention of Linux alternatives or parity.

Recommendations:

Provide equivalent examples using Azure CLI and/or Bash scripts for Linux users.
Include instructions for creating and running Python runbooks in Azure Automation, which are cross-platform.
Mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.), and link to relevant Linux-friendly documentation.
Where possible, use cross-platform Azure modules (e.g., Az instead of AzureRM) and clarify their compatibility.
Add a section or note explicitly addressing Linux/macOS users and how they can achieve the same VM startup order using their preferred tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All scripting and automation examples use Azure PowerShell, with no mention of Bash, Azure CLI, or Linux scripting alternatives. The sample configuration references only Windows images (e.g., Win2012R2, Win2016), and there are no examples or guidance for Linux VM image creation or distribution. The documentation assumes familiarity with Windows-centric tools and workflows, omitting Linux equivalents.

Recommendations:

Provide parallel examples using Azure CLI and Bash scripts for saving and distributing images, alongside PowerShell.
Include Linux VM image examples in the labs.json configuration and discuss any differences in generalizing Linux VMs (e.g., using waagent for deprovisioning).
Mention and illustrate how to add Azure CLI tasks in Azure DevOps build definitions, not just Azure PowerShell.
Balance the documentation by referencing both Windows and Linux workflows, tools, and image types throughout.
Add a section or callout for Linux users, highlighting any special considerations or steps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses Azure PowerShell tasks and scripts for all automation and cleanup steps, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. All screenshots and instructions are PowerShell-centric, and there are no Linux or macOS examples or guidance. This creates a strong Windows bias and may alienate users who prefer or require Linux-based automation.

Recommendations:

Provide equivalent examples using Azure CLI and/or Bash scripts for all automation steps, alongside the PowerShell examples.
Include screenshots and instructions for adding Bash or Azure CLI tasks in Azure DevOps build definitions.
Explicitly mention that the process can be performed on Linux/macOS agents using cross-platform tools.
Add a section comparing PowerShell and CLI approaches, helping users choose the best fit for their environment.
Ensure terminology and instructions are inclusive of both Windows and Linux users (e.g., avoid assuming PowerShell is the only or default scripting environment).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on using Azure PowerShell scripts and Windows-centric tools and patterns (such as Windows Task Scheduler), with no mention or examples of Linux equivalents (e.g., Bash, Azure CLI, cron). All scripting and automation steps assume PowerShell usage, and there are no instructions or guidance for users on Linux or macOS platforms.

Recommendations:

Include parallel examples using Azure CLI and Bash scripts for Linux/macOS users.
Mention and provide instructions for using Linux-native automation tools such as cron or systemd timers alongside Windows Task Scheduler.
Clarify that the image factory scripts can be adapted for non-Windows environments, and provide guidance or references for doing so.
Add notes or sections on how to run the image factory from Linux-based Azure DevOps agents or self-hosted runners.
Ensure all screenshots and UI instructions are platform-neutral or provide alternatives for Linux/macOS users where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing detailed PowerShell instructions and scripts for importing VMs, with no equivalent examples or scripts for Linux users (e.g., Bash, Azure CLI). PowerShell is a Windows-centric tool, and its exclusive use may hinder Linux users. The REST API section is platform-neutral, but the only scripted example is for PowerShell, and there is no mention of Linux command-line tools or workflows.

Recommendations:

Add equivalent instructions and sample scripts using Azure CLI (az) for Linux/macOS users.
Provide Bash shell examples for invoking the REST API (e.g., using curl or httpie).
Mention that PowerShell Core is cross-platform, but clarify if the provided script works on Linux/macOS or only on Windows PowerShell.
Include a table or section comparing Windows and Linux approaches to importing VMs.
Ensure that any downloadable scripts are compatible with both Windows and Linux environments, or provide separate versions if necessary.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing a PowerShell script as the only method for converting an existing lab to network isolation mode, without providing equivalent Bash, Azure CLI, or Linux-native instructions. While Azure CLI is briefly mentioned as an automation option, no concrete CLI or Linux shell examples are provided. The exclusive use of PowerShell and lack of Linux-specific guidance or parity in scripting options may disadvantage users on non-Windows platforms.

Recommendations:

Provide Azure CLI and/or Bash script equivalents for the PowerShell script (Convert-DtlLabToIsolatedNetwork.ps1) used to convert existing labs to network isolation.
Include example commands for both PowerShell and Azure CLI (or Bash) wherever automation is discussed, ensuring parity for Linux and macOS users.
Explicitly mention cross-platform tooling (e.g., Azure CLI, REST API) as first-class options alongside PowerShell.
Add a section or callout for Linux/macOS users, clarifying how to perform all steps without requiring Windows or PowerShell.
Review all automation and scripting references to ensure they are not Windows-centric and provide equal support for Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only Azure PowerShell examples for exporting personal data, with no mention of Linux-compatible tools or cross-platform alternatives such as Azure CLI, Bash, or REST API. The instructions and code samples are tailored exclusively to Windows/PowerShell users, implicitly prioritizing Windows tooling and omitting guidance for Linux or macOS environments.

Recommendations:

Add equivalent examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
Include Bash shell script examples for common operations, or reference how to perform the same actions in a Linux terminal.
Mention REST API options for exporting data, with sample curl commands.
Clearly state that the export functionality is not limited to PowerShell/Windows and provide links or references to official Azure CLI and REST API documentation.
Reorganize the section to present cross-platform or Linux-friendly options before or alongside PowerShell examples, ensuring parity and inclusivity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by primarily referencing PowerShell and Windows-centric tools and workflows. PowerShell is the only command-line example provided, and there are no Linux shell (bash/CLI) examples or explicit mentions of Linux tools. Windows tools like Power BI and SQL Server are mentioned before cross-platform or Linux-native alternatives. The documentation does not address Linux users or provide parity in instructions or tooling.

Recommendations:

Provide equivalent bash/CLI examples for exporting resource usage, using Azure CLI or REST API with curl.
Explicitly mention that Azure Functions and Automation can be implemented in Python or other cross-platform languages, and provide sample code or links.
Include Linux-friendly storage and visualization options, such as PostgreSQL, Grafana, or open-source BI tools, alongside Power BI and SQL Server.
Ensure that instructions and examples are platform-agnostic or provide both Windows and Linux workflows side by side.
Clarify that PowerShell Core is cross-platform if recommending it, and provide installation guidance for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides a detailed PowerShell script example for specifying a resource group for Azure DevTest Labs VMs, but does not include equivalent examples for Linux shells (such as Bash). The scripting section is labeled 'Use PowerShell' and only demonstrates usage with PowerShell, which is primarily associated with Windows environments. There is no mention of Bash, Azure CLI in Bash, or cross-platform scripting approaches. The ordering also places the PowerShell example before the ARM template and API sections, reinforcing a Windows-first approach.

Recommendations:

Add an equivalent Azure CLI example using Bash syntax to demonstrate how Linux or cross-platform users can accomplish the same task.
Include explicit mention that the Azure CLI commands can be run in any shell (Bash, zsh, etc.), not just PowerShell.
Reorganize the scripting examples to present cross-platform (Bash/Azure CLI) and PowerShell examples side by side, or clarify that both are supported.
Where possible, use neutral Azure CLI commands in documentation, as they are cross-platform and widely used.
Add a note or section for Linux/macOS users 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 environments. It assumes the use of Visual Studio (a primarily Windows tool), requires a Windows-based DevTest Labs VM, and only provides instructions for connecting via RDP and using File Explorer to access the Azure file share. There are no examples or guidance for Linux-based VMs, nor are alternative tools or workflows (such as VS Code, SCP, or SMB mounting on Linux) mentioned.

Recommendations:

Include instructions for publishing and accessing apps from Linux-based DevTest Labs VMs, such as mounting Azure file shares using SMB on Linux.
Provide alternative examples using cross-platform tools (e.g., Visual Studio Code, dotnet CLI) for publishing applications.
Add guidance for connecting to Linux VMs (e.g., using SSH) and accessing the file share via the Linux file system.
Mention and link to documentation for mounting Azure file shares on Linux and macOS.
Clarify in the prerequisites and throughout the article that the instructions are Windows-specific, and provide parity for other platforms where possible.

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 ARM template deployments, without mentioning Azure CLI or Bash alternatives. No Linux-specific examples or tools are provided, and the only automation example is Windows-centric. This may make Linux users feel unsupported or require them to translate instructions themselves.

Recommendations:

Include equivalent Azure CLI (az) or Bash examples alongside PowerShell for ARM template deployments.
Mention both Windows and Linux automation tools when discussing deployment scripting.
Explicitly state that instructions apply to both Windows and Linux environments, or provide OS-specific guidance where relevant.
Add troubleshooting steps or references for common Linux shell environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation shows a moderate Windows bias: PowerShell (a Windows-centric tool) is presented first in all sections, and its usage is described in greater detail. In the Azure CLI section, both Bash (Linux) and Windows command syntaxes are provided, but Windows batch syntax is given equal prominence, and 'REM' (a Windows batch comment) is used in the CLI example. There are no Linux-specific tools or shell scripting examples beyond Bash variable assignment, and the PowerShell section is more detailed and prominent.

Recommendations:

Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI (which is more cross-platform) first.
Provide more detailed Bash/Linux shell scripting examples, including error handling and output, to match the PowerShell example's depth.
Use cross-platform comment syntax in CLI examples (e.g., '#' for Bash, 'REM' for Windows), and clearly separate Bash and Windows batch examples.
Highlight that Azure CLI is fully cross-platform and can be used in Linux, macOS, and Windows environments.
Consider adding Linux-native automation examples (e.g., using shell scripts or cron jobs) for starting/stopping VMs.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias by referencing PowerShell cmdlets (e.g., New-AzRoleAssignment) and their parameters as the primary or only automation example for role assignments. There are no CLI (e.g., Azure CLI) or Linux shell examples provided for equivalent tasks, and no mention of cross-platform tooling for automation. This may hinder Linux or cross-platform users from easily following automation guidance.

Recommendations:

Provide equivalent Azure CLI examples (e.g., using 'az role assignment create') alongside PowerShell cmdlets for role assignment automation.
Explicitly mention that both PowerShell and Azure CLI are supported, and clarify which tools are cross-platform.
Where automation is discussed, offer both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) command examples.
Link to documentation for both PowerShell and Azure CLI modules relevant to Azure Digital Twins and RBAC.
Review other sections for implicit Windows-first assumptions and ensure parity in tool and example coverage.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias. While it generally references cross-platform tools like the Azure CLI and AzCopy, it tends to mention Windows-centric tools (such as the Azure portal and .NET SDK) first or exclusively. There are no explicit Linux or macOS-specific instructions, examples, or mentions of alternative tools (e.g., Bash, curl, or Python SDKs). The only sample project referenced is written in .NET (C#), and there are no code snippets or walkthroughs for Linux command-line environments. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users.

Recommendations:

Include explicit Linux/macOS instructions and examples alongside Windows/portal instructions, such as using Bash, curl, or wget for API calls and blob uploads.
Provide sample projects or code snippets in additional languages (e.g., Python, Java, JavaScript) that are popular in Linux environments, not just .NET (C#).
When listing tools or methods (e.g., for uploading blobs), mention cross-platform CLI tools (like Azure CLI and AzCopy) before or alongside the Azure portal.
Add example commands for both Windows (PowerShell/CMD) and Linux (Bash) where relevant, especially for authentication and file operations.
Reference SDKs for multiple languages and platforms, not just .NET, and provide links or examples for each.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides examples and guidance for Bash, PowerShell, and Windows CMD environments. However, PowerShell and Windows CMD receive more detailed attention, with specific sections and examples for each, and PowerShell is mentioned in CLI version requirements. Bash is covered, but Linux-specific shells beyond Bash (e.g., zsh, fish) are not mentioned. The order of presentation places Bash first, but PowerShell is referenced in requirements and receives more nuanced discussion. There is a subtle Windows bias in the prominence and detail given to Windows-native shells and tools.

Recommendations:

Expand Linux parity by including examples for additional common Linux shells (e.g., zsh, fish) or explicitly stating that Bash examples apply to most POSIX shells.
Clarify that the Azure CLI and its extensions are fully cross-platform, and highlight any Linux/macOS-specific considerations if they exist.
Balance the depth of examples and troubleshooting tips between Bash and PowerShell/Windows CMD sections.
In CLI version requirements, avoid referencing PowerShell specifically unless there is a unique requirement for it; otherwise, generalize to all supported shells.
Consider adding a table summarizing shell-specific syntax differences for quick reference, ensuring equal visibility for Linux and Windows environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a bias towards Windows environments by only providing C#/.NET Core sample code and referencing Windows-centric workflows (such as downloading ZIP files and using .NET tools) without mentioning or providing equivalent Linux or cross-platform alternatives. There are no Linux-specific instructions, shell commands, or examples, and the tools highlighted (dotNetRDF, .NET Core CLI) are more familiar to Windows users. The documentation assumes a Windows workflow (e.g., ZIP extraction, .NET usage) and does not address Linux users' needs or provide parity in examples.

Recommendations:

Include Linux-specific instructions for running the sample applications, such as using the .NET CLI on Linux and alternative ways to extract ZIP files (e.g., using unzip command).
Provide equivalent shell (bash) command examples for downloading and running the converter tools on Linux/macOS.
Mention and, if possible, provide sample code in other cross-platform languages commonly used on Linux (such as Python with RDFLib).
Explicitly state that the .NET Core tools and libraries are cross-platform, and provide installation instructions for Linux and macOS.
Add troubleshooting tips or notes for common Linux issues (e.g., file permissions, dependency installation).
Consider including Docker-based instructions or containers to ensure parity across operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by using Windows-style paths (backslashes), referencing Windows tools (File Explorer), and providing screenshots from Windows environments. There are no explicit Linux or macOS instructions, examples, or screenshots, and some steps (such as zipping files) assume familiarity with Windows tooling. The language and examples do not address cross-platform differences or provide parity for Linux users.

Recommendations:

Provide parallel instructions and screenshots for Linux/macOS environments, including terminal commands for file navigation and zipping files (e.g., using 'zip' command).
Use platform-agnostic path notation or clarify both Windows (\) and Linux/macOS (/) path formats in file navigation steps.
Include notes or sections that address common differences in running .NET projects and Azure CLI commands on Linux/macOS, such as prerequisites or shell differences.
Replace or supplement Windows-specific tool references (like File Explorer) with cross-platform alternatives (e.g., using the terminal or Finder on macOS).
Add explicit statements confirming that all steps are supported on Linux/macOS, and provide troubleshooting tips for non-Windows users where applicable.

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 are provided exclusively using Azure PowerShell, with no Azure CLI (bash) or Linux shell examples. The validation step uses Windows command prompt syntax (cmd) for nslookup, and there are no Linux or macOS equivalents. The instructions and screenshots reference Windows tools and workflows first or exclusively, making it less accessible for Linux or cross-platform users.

Recommendations:

Add Azure CLI (az) examples alongside or before the Azure PowerShell examples for deploying ARM templates.
Provide Linux/macOS shell equivalents for validation steps (e.g., using nslookup or dig in bash/zsh).
Include screenshots or terminal output from Linux/macOS environments where appropriate.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
Avoid using only Windows command prompt syntax; show cross-platform alternatives.
Ensure all steps and code blocks have parity between Windows and Linux/macOS environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell and the Azure portal for quickstarts and next steps, without mentioning or linking to Linux-native tools or CLI examples (such as Azure CLI or Bash). There are no Linux-specific instructions or examples, and PowerShell is presented as the primary automation/scripting interface, which may disadvantage Linux users.

Recommendations:

Add equivalent quickstart and how-to links for Azure CLI (az) and Bash scripting, ensuring Linux users have first-class guidance.
In the 'Next steps' and 'For more information' sections, list Azure CLI and Linux/Bash options alongside or before PowerShell to provide parity.
Include explicit examples or references for configuring on-premises DNS forwarders using Linux-based DNS servers (e.g., BIND, dnsmasq), not just generic 'conditional forwarder' instructions.
Review and update all automation and scripting recommendations to include cross-platform options, not just PowerShell.
Where possible, use neutral language (e.g., 'using Azure CLI or PowerShell') instead of defaulting to Windows-centric tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently presents Azure PowerShell examples before Azure CLI examples, and in some cases (such as record set level resource locks), only PowerShell commands are provided, with explicit notes that the functionality is not available in the Azure CLI or portal. There are no references to Linux-specific tools, shell environments, or considerations, and the use of PowerShell as the primary scripting example may implicitly favor Windows users. No Linux shell or cross-platform scripting guidance is provided.

Recommendations:

Wherever possible, provide Azure CLI examples first or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
Explicitly mention that Azure CLI and Azure PowerShell are both cross-platform, and clarify any platform-specific limitations.
For scenarios where only PowerShell is supported, offer guidance for Linux users on how to install and use Azure PowerShell on Linux, or provide alternative approaches if available.
Include examples using Bash or other common Linux shells when demonstrating CLI usage, especially for scripting or automation.
Add a section or note addressing Linux/macOS users, highlighting any differences or additional steps required.
Where features are not available in the CLI or portal, consider linking to feedback channels or roadmaps for feature parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides both Azure PowerShell and Azure CLI examples for most operations, which supports cross-platform usage. However, there is a notable bias in the 'Protecting individual records' section, where record set level resource locks can only be configured using Azure PowerShell, with no Azure CLI or Linux-native alternative. This effectively prioritizes Windows tooling and excludes Linux-only users from performing this operation. Additionally, the documentation does not mention or provide any Linux-native shell scripting or automation examples outside of Azure CLI, and does not clarify platform requirements for PowerShell usage.

Recommendations:

Work with the Azure product team to enable record set level resource lock management via Azure CLI, ensuring Linux parity.
Where PowerShell is required, clarify that Azure PowerShell is cross-platform and provide installation/use instructions for Linux users.
Explicitly state platform requirements or limitations for each tool (Azure PowerShell, Azure CLI, Portal) at the start of the documentation.
Where possible, provide bash/shell scripting examples for Linux users, especially for automation scenarios.
Add a note or workaround for Linux users when a feature is only available via Azure PowerShell, such as using Azure Cloud Shell (which supports PowerShell on Linux) or requesting the feature in Azure CLI.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Azure PowerShell (and classic PowerShell) examples before CLI equivalents, providing only PowerShell-based instructions for Cloud Services, and omitting Linux/Unix-native command examples (such as Bash, dig, or nslookup). The use of PowerShell-specific cmdlets and the absence of Linux shell or cross-platform DNS validation tools further reinforce this bias.

Recommendations:

Provide Linux-native command examples (e.g., Bash, dig, nslookup) for verifying reverse DNS records alongside PowerShell examples.
Include instructions and examples for configuring reverse DNS using cross-platform tools and scripts, not just PowerShell.
When listing command-line examples, present Azure CLI (which is cross-platform) before or alongside PowerShell, rather than always leading with PowerShell.
Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample shell environments where appropriate.
For Cloud Services, clarify if there are any cross-platform or REST API alternatives to PowerShell, and provide those if available.
Add a section or callout for Linux users, summarizing the parity and any limitations or differences in the process.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by only mentioning Azure PowerShell as a configuration method and omitting any references to cross-platform or Linux-native tools (such as Azure CLI, Bash, or REST API). No Linux or cross-platform command-line examples are provided, and the only automation tool referenced is PowerShell, which is most commonly associated with Windows environments.

Recommendations:

Include Azure CLI examples alongside PowerShell for all configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that DNS security policy can be configured using Azure CLI, REST API, or ARM templates, and provide links or examples for each.
Avoid referencing only Windows-centric tools (like PowerShell) as the primary or sole automation method.
Where screenshots or UI steps are shown, clarify that the Azure portal is platform-agnostic.
Add a section or note highlighting cross-platform support and parity for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by consistently using Windows command prompt syntax (e.g., 'C:\>') for DNS query examples, referencing 'command prompt' and 'cmd', and showing nslookup and dig commands prefixed with Windows-style prompts. There are no explicit Linux or macOS shell examples, nor is there mention of running these commands from a Bash shell or Linux VM. The instructions for running DNS queries assume a Windows environment, and there is no guidance for Linux users, despite the cross-platform nature of Azure VMs.

Recommendations:

Provide parallel Linux/macOS shell examples for DNS queries (e.g., show '$ dig ...' and '$ nslookup ...' in Bash).
Explicitly mention that the DNS query steps can be performed from either Windows or Linux VMs, and clarify any OS-specific differences.
Include screenshots or terminal output from Linux environments where appropriate.
Avoid using only Windows command prompt syntax (e.g., 'C:\>')—use a neutral prompt ('$') or show both.
In the prerequisites, clarify that the virtual machine used for DNS queries can be Windows or Linux, and provide instructions for both.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by exclusively using Windows Server as the example VM OS, referencing RDP and PowerShell for management and testing, and omitting any Linux-based examples or instructions. All command-line and remote management examples use Windows tools (PowerShell, RDP), and there is no mention of Linux VMs, SSH, or Bash/CLI alternatives. This may make the documentation less accessible or relevant for users who primarily work with Linux environments.

Recommendations:

Include parallel instructions and screenshots for creating a Linux virtual machine (e.g., Ubuntu) alongside the Windows VM example.
Provide examples for connecting to the VM using SSH (for Linux) in addition to RDP (for Windows).
Show how to test DNS resolution from a Linux VM using Bash commands (e.g., ping, dig, nslookup) as well as from Windows/PowerShell.
Mention both PowerShell and Bash/CLI options for running remote commands, or reference the Azure CLI/Cloud Shell where appropriate.
Balance the order of presentation so that Linux and Windows options are given equal prominence, or clearly indicate that both are supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools and workflows, such as Visual Studio and NuGet Package Manager, without mentioning or providing alternatives for Linux users. The instructions for creating a service principal link to a PowerShell-based guide, and there are no examples or guidance for performing these steps using Linux-friendly tools (e.g., .NET CLI, VS Code, or Azure CLI). There is also no mention of cross-platform development environments or package management approaches outside of Visual Studio.

Recommendations:

Include instructions for installing required NuGet packages using the .NET CLI (e.g., 'dotnet add package') for Linux and macOS users.
Reference cross-platform editors such as Visual Studio Code, and provide guidance for users not on Windows.
Provide links and examples for creating service principals and resource groups using the Azure CLI, which is available on all platforms.
Avoid assuming the use of Visual Studio or Windows-specific tools; offer alternative steps for common Linux development environments.
Explicitly state that the .NET SDK and Azure DNS Management libraries are cross-platform, and clarify any platform-specific requirements if they exist.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exclusively uses Azure PowerShell cmdlets for all DNS record creation and management examples, and demonstrates DNS record validation using nslookup in a Windows PowerShell context. There are no CLI, Bash, or Linux-native examples provided, nor are cross-platform tools or commands mentioned. The workflow assumes a Windows environment and does not address Linux or macOS users.

Recommendations:

Provide equivalent Azure CLI (az) commands for all DNS record operations alongside PowerShell examples.
Include Linux/macOS-friendly instructions for DNS validation, such as using dig or host commands, in addition to nslookup.
Explicitly mention that the steps can be performed on any OS, and clarify which tools are cross-platform.
Consider reordering or parallelizing examples so that Linux/macOS and Windows users see relevant instructions at the same level of prominence.
Add a section or callout for using Azure Cloud Shell, which supports both Bash and PowerShell, to emphasize cross-platform accessibility.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell as the primary tool for managing Azure DNS (e.g., Etags section), without mentioning or providing parity for Linux-native tools or CLI usage. There are no examples or guidance for Linux users, and the only command-line tool referenced is PowerShell, which is most commonly associated with Windows environments.

Recommendations:

Provide Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that PowerShell Core is available cross-platform, if PowerShell examples are retained, and provide installation guidance for non-Windows users.
Include bash or shell script examples where relevant, especially for common DNS management tasks.
Ensure that all tool references (e.g., for Etags or record management) include both PowerShell and Azure CLI approaches, with equal prominence.
Add a section or callout for Linux/macOS users, highlighting any differences or special considerations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All automation and scripting examples are provided exclusively in PowerShell, with no equivalent Azure CLI, Bash, or Linux-native instructions. The PowerShell tab is the only programmatic method shown, and all command-line examples (including DNS query tests) use Windows paths and tools. There are no Linux-specific instructions, nor are Linux tools or workflows mentioned. The documentation assumes a Windows environment for scripting and management, leaving Linux users without clear guidance.

Recommendations:

Add Azure CLI and/or Bash examples for all resource creation, configuration, and management steps, ensuring parity with PowerShell instructions.
Include Linux-native command-line examples (e.g., using dig or nslookup from a Bash shell) for DNS query and testing sections.
When referencing file paths or environment variables, provide both Windows and Linux equivalents (e.g., C:\bin\PSRepo vs. ~/bin/PSRepo).
Explicitly mention that the instructions apply to both Windows and Linux environments, and provide guidance for each where workflows differ.
Consider adding a 'Linux' or 'Azure CLI' tab alongside the existing 'PowerShell' and 'Portal' tabs for all relevant sections.
Reference cross-platform tools and patterns (such as Azure Cloud Shell, which supports both Bash and PowerShell) earlier and more prominently.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. PowerShell is given a dedicated section, and the Azure CLI examples use 'dig.exe' (the Windows version of dig) rather than simply 'dig', which is more common on Linux/macOS. There are no explicit Linux or macOS command-line examples, nor is there mention of Linux-native tools or shell environments. The documentation assumes a Windows environment for command-line operations and does not provide parity for Linux users.

Recommendations:

Add explicit Linux/macOS examples for command-line operations, including Azure CLI usage in bash/zsh.
Replace 'dig.exe' with 'dig', and clarify that 'dig' is available on Linux/macOS by default, while Windows users may need to install it.
Provide sample commands for installing required tools (e.g., dig) on Linux distributions.
Include screenshots or instructions for Linux/macOS terminal environments where relevant.
Ensure that all PowerShell examples have equivalent bash (or generic shell) examples for cross-platform parity.
Review terminology and tool references to avoid Windows-specific language unless necessary.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides detailed instructions for the Azure Portal, Azure CLI, and PowerShell. While the Azure CLI is cross-platform, the explicit inclusion of PowerShell (which is traditionally associated with Windows environments) and the use of PowerShell-specific cmdlets indicate a bias towards Windows users. Additionally, the PowerShell section is given equal prominence to the CLI, and there are no explicit Linux shell (bash) examples or references to Linux-native tools or workflows. The CLI examples use the Azure CLI, which is available on Linux, but there is no mention of running these commands in a Linux environment or using bash scripting, and the CLI section is labeled with 'azurepowershell-interactive', which may be confusing.

Recommendations:

Add explicit bash shell examples for the Azure CLI section, showing usage in a Linux/macOS terminal.
Clarify that the Azure CLI commands can be run on Linux, macOS, and Windows, and provide example shell prompts (e.g., $ for bash).
If PowerShell is included, also include bash equivalents for parity.
Avoid labeling CLI code blocks as 'azurepowershell-interactive' when they are standard Azure CLI commands.
Mention that PowerShell Core is cross-platform if you intend to support Linux, or clarify that the PowerShell examples are for Windows users.
Consider the order of sections: present the Azure CLI (cross-platform) before PowerShell to avoid a 'windows_first' impression.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias primarily in its examples and tool recommendations. PowerShell (Resolve-DnsName) is presented first and in more detail than Linux/Unix equivalents. Windows-specific tools and concepts (such as Group Policy, NRPT, and explicit references to Windows 10/11 clients) are mentioned without Linux parallels. The dig command is shown, but only as a secondary example, and there is no mention of Linux-native environments or tools like host or unbound. There are no Linux shell prompt examples, and the guidance assumes a Windows-centric audience.

Recommendations:

Provide Linux/Unix shell examples (e.g., bash prompt, dig, host) alongside or before Windows/PowerShell examples.
Mention Linux/Unix DNSSEC validation tools (e.g., unbound, bind, dnssec-trigger) and how to configure them.
Balance references to Windows-specific features (like Group Policy and NRPT) with Linux equivalents (such as systemd-resolved, resolvconf, or dnssec-trigger).
Clarify that dig is a cross-platform tool and provide installation instructions for both Windows and Linux.
Include guidance or links for DNSSEC validation and troubleshooting on Linux systems.
Use neutral language when describing client operating systems (e.g., 'Windows, Linux, and macOS clients...') where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a strong Windows bias in the testing and validation sections. All VM creation examples use Windows images, and all instructions for configuring and testing DNS resolution are written exclusively for Windows (PowerShell commands, Windows firewall, and output). There are no Linux VM creation examples, nor are there any Linux shell or firewall commands provided. The documentation assumes the user is operating in a Windows environment for all post-deployment steps.

Recommendations:

Provide parallel Linux examples for VM creation (e.g., using --image UbuntuLTS) and show both Windows and Linux VM creation commands.
Include instructions for configuring the firewall to allow ICMP on Linux VMs (e.g., using ufw or firewalld).
Show how to test DNS resolution from a Linux shell (e.g., using ping, dig, or nslookup in bash).
Present both Windows and Linux command outputs for DNS resolution tests.
Explicitly mention that the steps apply to both Windows and Linux, and clarify any OS-specific differences.
Consider alternating the order of Windows and Linux examples, or presenting them side-by-side to avoid 'windows_first' bias.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by mentioning Windows DNS and its file locations before Linux/BIND equivalents, and by providing specific details for Windows tools (e.g., %systemroot%\system32\dns) while only briefly referencing BIND and its configuration. No explicit Linux command-line examples or file paths are given, and the only concrete example of obtaining a zone file is for Windows DNS. There are no Linux-specific instructions or troubleshooting tips, despite BIND being called out as a common Linux DNS server.

Recommendations:

Provide explicit Linux/BIND examples, such as sample named.conf entries and typical zone file paths (e.g., /etc/bind/zones/db.example.com).
List Linux/BIND instructions before or alongside Windows instructions, especially since BIND is the most common DNS server.
Include example commands for exporting a zone file from BIND (e.g., using cp or cat to copy the file), and clarify permissions or file locations.
Add troubleshooting tips or notes relevant to Linux users, such as file permissions or SELinux considerations.
Ensure parity in detail and clarity between Windows and Linux instructions throughout the documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily in the 'Next steps' section, where the link to 'create a Private DNS zone' points specifically to a PowerShell-based guide, which is Windows-centric. There are no examples or references to Linux tools, CLI, or cross-platform approaches for managing Azure Private DNS zones. The absence of Linux or Azure CLI examples and the exclusive mention of PowerShell suggest a bias towards Windows users.

Recommendations:

Include links to equivalent Linux/Azure CLI documentation for creating and managing Private DNS zones.
Provide examples using Azure CLI and/or REST API alongside PowerShell to ensure cross-platform accessibility.
Avoid referencing only Windows-specific tools (like PowerShell) in primary navigation or 'Next steps'; instead, offer parallel options for Linux and macOS users.
Explicitly mention that Azure DNS management can be performed from any platform, and provide guidance for non-Windows environments.

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 no mention of Linux, Bash, or cross-platform alternatives. The instructions assume the use of an 'elevated PowerShell window' and reference Windows-specific tools and installation methods. There are no examples or guidance for users on Linux or macOS, nor are there alternative scripts or CLI-based migration paths provided.

Recommendations:

Provide equivalent migration instructions using Azure CLI and Bash scripts that can be run on Linux and macOS.
Include Linux/macOS prerequisites, such as ensuring Azure CLI is installed and up-to-date, and provide installation instructions for non-Windows environments.
Offer a cross-platform migration script (e.g., Python or Bash) or document how to perform the migration manually using Azure CLI commands.
Clearly indicate which steps are Windows-specific and provide alternative steps for Linux/macOS users.
Add screenshots or terminal output examples from Linux/macOS environments to improve inclusivity.
Mention that PowerShell Core is available cross-platform and provide instructions for installing and running the script on Linux/macOS if no alternative is available.

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 equivalent Linux/CLI/Bash instructions. No Linux tools, commands, or examples are provided, and the 'get started' link specifically points to a PowerShell tutorial, which is typically associated with Windows environments. There are no examples or guidance for Linux users or those preferring cross-platform Azure CLI.

Recommendations:

Include links to both PowerShell and Azure CLI (Bash/Linux) guides for creating and managing Private DNS zones.
Add example commands using Azure CLI alongside PowerShell, ensuring parity in instructions for both platforms.
Explicitly mention that Azure DNS management can be performed from Windows, Linux, and macOS, and provide platform-agnostic examples where possible.
Where only PowerShell is referenced, add a note or section for Linux/macOS users, directing them to appropriate CLI documentation.
Review all 'Next steps' and instructional links to ensure they are not Windows-centric and provide equal visibility to cross-platform tooling.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by specifically referencing PowerShell and providing instructions tailored to it (e.g., how to format VM SKU identifiers for use in PowerShell scripts). There are no equivalent examples or explicit mentions of Linux shell scripting or tools. The language and examples prioritize Windows/PowerShell usage, with Linux alternatives either omitted or only referenced generically as 'other scripts.'

Recommendations:

Include explicit examples for both PowerShell (Windows) and Bash (Linux/macOS) when referencing scripting tasks, such as how to use VM SKU identifiers in deployment scripts.
Avoid language that prioritizes Windows tools (e.g., 'PowerShell or Azure CLI scripts'); instead, use neutral phrasing like 'deployment scripts using PowerShell, Bash, or Azure CLI.'
Add a note or section demonstrating how to perform equivalent tasks on Linux, such as using Azure CLI in Bash or shell scripts.
Where possible, provide cross-platform code snippets or links to platform-specific documentation for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides only a Windows/Powershell-based example for testing DNS resolution (using nslookup with a C:\> prompt), with no Linux or cross-platform command-line examples. The command-line prompt and syntax are Windows-specific, and there is no mention of how to perform the same operation on Linux or macOS. This may lead Linux users to feel unsupported or unclear about how to verify reverse DNS functionality.

Recommendations:

Include Linux and macOS examples for testing DNS resolution, such as showing the nslookup or dig command with a $ prompt.
Present both Windows and Linux/macOS command-line examples side by side, or use a neutral prompt (e.g., 'nslookup 10.1.2.5') without platform-specific context.
Explicitly mention that the steps for verifying DNS resolution can be performed on any OS, and provide sample outputs for both Windows and Linux.
If using screenshots or code blocks, alternate between Windows and Linux environments, or provide both to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows and PowerShell in procedural examples, omitting Linux/BIND equivalents, and focusing on Windows DNS server tools for on-premises configuration. Linux-based DNS servers and command-line tools are not mentioned or demonstrated, leaving a gap for cross-platform administrators.

Recommendations:

Add parallel instructions and screenshots for configuring conditional forwarders on common Linux DNS servers (e.g., BIND/named.conf).
Include CLI examples using Azure CLI and bash, not just PowerShell, for Azure resource creation and management.
When referencing on-premises DNS, explicitly mention and provide steps for both Windows DNS and Linux/BIND (and optionally other popular DNS servers).
Ensure that Linux examples are presented alongside or before Windows examples to avoid 'windows_first' bias.
Provide sample dig/nslookup commands from both Windows and Linux environments to demonstrate DNS resolution.
In the 'Next steps' section, link to Linux/BIND documentation or community guides for hybrid DNS scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The tutorial exclusively uses Windows Server virtual machines for the web server setup, with detailed steps for installing IIS via the Windows GUI and RDP. There are no examples or instructions for deploying Linux-based VMs or using common Linux web servers (e.g., Apache, Nginx). All configuration and testing steps assume a Windows environment, and no Linux alternatives are mentioned.

Recommendations:

Add parallel instructions for creating Linux virtual machines (e.g., Ubuntu) and installing a web server such as Apache or Nginx.
Provide CLI-based steps for web server setup (using Azure CLI, SSH, and Linux package managers) alongside the Windows/RDP/IIS instructions.
Include Linux-based examples for editing the web root (e.g., using nano or vim to edit /var/www/html/index.html).
Demonstrate testing the setup from a Linux client (e.g., using curl or a browser on a Linux desktop).
Clearly indicate that both Windows and Linux are supported, and offer a choice at the start of the tutorial.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a clear Windows bias in the section on configuring on-premises DNS forwarding. Only Windows Server and PowerShell-based instructions are provided, with no mention of Linux-based DNS servers (such as BIND or dnsmasq) or their configuration. All command-line examples and screenshots are Windows-centric, and the documentation does not acknowledge or provide parity for Linux environments, which are common in enterprise and hybrid cloud scenarios.

Recommendations:

Add equivalent instructions and examples for configuring DNS forwarding on popular Linux DNS servers, such as BIND and dnsmasq.
Include Linux command-line examples (e.g., editing named.conf.options for BIND) alongside PowerShell examples.
Explicitly mention that the procedure applies to both Windows and Linux DNS servers, and provide links or references to official documentation for Linux DNS server configuration.
Reorganize the documentation to present both Windows and Linux options in parallel, or at least acknowledge Linux as a supported and common scenario.
Where screenshots are used, consider including Linux-based management interfaces or configuration file snippets as well.

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 connectivity (a Windows-centric tool). There are no examples or options provided for deploying a Linux VM, nor are SSH or Linux-related connectivity methods mentioned. This creates a clear Windows-first bias and omits Linux user scenarios.

Recommendations:

Include instructions and screenshots for deploying a Linux VM (e.g., Ubuntu or CentOS) alongside the Windows example.
Provide guidance for configuring SSH access (port 22) for Linux VMs, including how to use SSH keys and connect from Linux/macOS/Windows clients.
Mention both RDP (for Windows) and SSH (for Linux) in the 'Connect to virtual machine' section, with steps for each.
In the 'Image' selection step, show how to choose both Windows and Linux images.
Add a note or table summarizing differences in connection methods and initial setup between Windows and Linux VMs.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by predominantly listing Microsoft and Windows-centric developer tools (such as Visual Studio, Windows Server, Hyper-V, and Windows 10/11) and omitting Linux-specific tools or examples. There are no references to Linux distributions, Linux-compatible software, or cross-platform usage scenarios. The documentation also highlights Windows virtual machines and Windows Store app publishing, with no mention of Linux VM deployment or open-source alternatives. Visual Studio for Mac is mentioned, but Linux is not.

Recommendations:

Include examples and references for deploying Linux virtual machines alongside Windows VMs.
List Linux-compatible developer tools and clarify which tools are available for Linux (e.g., Visual Studio Code, SQL Server on Linux).
Mention open-source and cross-platform alternatives where appropriate (e.g., VS Code, .NET Core, Azure CLI on Linux).
Provide parity in tool listings by including Linux distributions (Ubuntu, CentOS, etc.) and their availability in Azure for Education.
Add guidance or links for Linux users on how to access and use Azure for Education resources.
Ensure that product lists and benefit descriptions do not exclusively or primarily highlight Windows tools, and that Linux options are given equal prominence.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments by exclusively providing PowerShell-based deployment instructions and referencing PowerShell as a prerequisite, without offering equivalent Bash or Linux shell examples. There is no mention of Linux-specific tools or deployment patterns, and the sample deployment script is only provided for PowerShell, which may hinder accessibility for Linux or macOS users.

Recommendations:

Provide equivalent Bash shell deployment instructions and scripts for Linux/macOS users alongside PowerShell examples.
List both PowerShell and Bash as prerequisites, with installation links for each platform.
Explicitly mention cross-platform compatibility of the deployment scripts, or provide separate scripts for Windows (PowerShell) and Linux/macOS (Bash).
Include notes or callouts clarifying any platform-specific steps or differences.
Ensure that screenshots and instructions referencing terminal commands or environments are inclusive of both Windows and Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias towards Microsoft and Windows-centric tools and workflows. It exclusively mentions Microsoft products (SharePoint, Synapse, Power BI, Entra ID) for integration and extensibility, with no mention of Linux-based tools, open-source alternatives, or cross-platform command-line examples. The documentation assumes the use of the Microsoft ecosystem, which is more common on Windows, and does not provide parity for Linux users.

Recommendations:

Include examples and references to cross-platform or Linux-native tools for data ingestion, transformation, and visualization (e.g., Apache NiFi, Jupyter, Grafana).
Mention compatibility with open-source identity providers or authentication mechanisms commonly used on Linux.
Provide command-line examples for both Windows (PowerShell) and Linux (Bash) in future quickstart or how-to guides.
Highlight integration possibilities with non-Microsoft applications and services to demonstrate platform openness.
Clarify whether the platform supports Linux-based workflows and tools, and provide documentation or links for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by listing Windows prerequisites and tools first, referencing Windows-specific tools (e.g., Microsoft C++ Build Tools, WSL), and providing activation commands for Windows before Linux. Some instructions and notes are tailored to Windows or WSL users, and there is a lack of parity in detailed Linux/Mac-specific guidance, especially regarding package management and environment setup.

Recommendations:

List Linux and Mac prerequisites before or alongside Windows, not after.
Provide Linux and Mac equivalents for all Windows-specific tools and commands (e.g., recommend GCC or Clang for C++ build tools on Linux, and clarify how to install dependencies using native package managers).
Avoid referencing WSL as the primary Linux environment for Windows users; instead, treat native Linux and WSL as separate, equally valid platforms.
Ensure all command examples (such as activating virtual environments) are shown for all platforms, and not just Windows first.
Expand on Linux/Mac installation steps, including common package manager commands (apt, yum, brew) and troubleshooting tips.
Where possible, use cross-platform commands and avoid Windows-centric paths or syntax.
Add explicit sections or callouts for Linux/Mac users wherever there are differences in workflow or tooling.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas: it references enabling managed identities specifically on a Windows VM, provides detailed PowerShell examples for disabling local authentication, and does not provide equivalent Linux shell or cross-platform CLI examples for some operations. The Azure CLI example is present, but PowerShell is given a dedicated section and example, while Linux-specific instructions or screenshots are missing. There is also a lack of explicit Linux or cross-platform guidance for environment variable setup and SDK usage, with examples using Windows-centric tools and patterns.

Recommendations:

Add explicit Linux/Unix shell (bash) examples for all operations currently shown only in PowerShell, such as creating resources and setting environment variables.
When referencing enabling managed identities, provide links and instructions for both Windows and Linux VMs, not just Windows.
Ensure screenshots and portal instructions are not Windows-specific, or clarify that the UI is the same across platforms.
In code samples that require environment variables (e.g., AZURE_CLIENT_ID), show both Windows (set in PowerShell/cmd) and Linux (export in bash) syntax.
Review all tool references to ensure cross-platform parity, and avoid giving Windows tools or patterns prominence over their Linux equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides deployment instructions for both Azure CLI and Azure PowerShell, but the PowerShell example is given equal prominence to the CLI example, which may suggest a Windows-centric approach. There are no explicit Linux-specific instructions or examples, and the PowerShell tab may be confusing or irrelevant for Linux users. The documentation does not mention or link to Linux shell alternatives or clarify cross-platform compatibility for the CLI commands.

Recommendations:

Clearly indicate that Azure CLI commands are cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows (unless using PowerShell Core).
List the Azure CLI example first, as it is the most cross-platform option, and consider making it the default tab.
Add a note clarifying that Azure CLI works on Windows, Linux, and macOS, and provide installation links for each OS.
If PowerShell is included, specify that it is for users who have PowerShell installed (Windows or PowerShell Core on Linux/macOS).
Consider providing bash/zsh shell examples for Linux users, especially for common tasks like file upload to Blob storage.
Explicitly mention that all steps (except PowerShell) are fully supported on Linux, and provide troubleshooting tips or links for Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell examples alongside Azure CLI, referencing Visual Studio (a primarily Windows IDE) and its GUI workflows, and omitting explicit Linux or cross-platform alternatives (such as Bash scripting or VS Code on Linux). There are no Linux-specific instructions or examples, and Windows tools and patterns are mentioned first or exclusively.

Recommendations:

Provide Bash shell equivalents for all PowerShell examples, especially for variable assignment and command usage.
When referencing IDEs, mention cross-platform options such as VS Code on Linux and Mac, and include instructions for those environments.
Avoid assuming the use of Windows tools (e.g., Visual Studio, Solution Explorer) as the default; instead, present VS Code or CLI-based workflows first or equally.
Explicitly state that the Azure CLI commands work on all platforms, and provide examples of running them in Bash or other common Linux shells.
Include a section or callout for Linux/macOS users, highlighting any differences or additional steps required.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides comprehensive coverage for both Azure CLI and PowerShell, but the PowerShell section is notably detailed and includes full sample scripts, which may favor Windows users. PowerShell is a Windows-centric tool, and its inclusion as a primary automation method can be seen as a Windows bias. The documentation does not mention or provide examples for Linux-native scripting environments (such as Bash), nor does it clarify cross-platform PowerShell Core compatibility. The order of presentation (CLI before PowerShell) is good, but the heavy PowerShell focus and lack of Linux-native examples indicate some Windows bias.

Recommendations:

Add explicit Bash shell script examples for Linux/macOS users, especially for automation scenarios.
Clarify that Azure CLI commands work cross-platform and can be run in Bash, Zsh, or other Linux shells.
If PowerShell examples are included, specify whether they are compatible with PowerShell Core (cross-platform) or only Windows PowerShell.
Consider including a section or note for Linux users, highlighting any differences or prerequisites.
Ensure parity in the depth and complexity of examples between CLI and PowerShell sections.

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 it consistently lists PowerShell alongside CLI, and refers to 'PowerShell command' without clarifying cross-platform support. The only explicit command-line example provided is for Azure CLI, which is cross-platform, but references to PowerShell are present without corresponding Linux shell (bash) or scripting examples. There are no explicit Linux- or macOS-specific instructions, nor are there any bash or shell script examples. The documentation does not mention platform-specific differences, but the pattern of referencing PowerShell and CLI together, and the absence of Linux-specific examples or notes, suggests a subtle Windows-first bias.

Recommendations:

When referencing PowerShell, clarify that Azure PowerShell is cross-platform, or provide equivalent bash/shell examples where appropriate.
Include explicit bash or shell script examples for common Linux/macOS usage scenarios, especially where PowerShell is mentioned.
When linking to further documentation (e.g., 'Set retry policy'), ensure that both PowerShell and bash/CLI examples are present and equally prominent.
Avoid phrasing such as 'CLI and PowerShell' as the only options; mention bash/shell scripting or note that Azure CLI works on all platforms.
Add a note or section on platform compatibility for all command-line tools referenced, making it clear that Linux/macOS users are equally supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. While it does provide Azure CLI and cURL examples (which are cross-platform), it consistently references Windows-centric tools and workflows first, such as Visual Studio Code with .NET/C#, and provides detailed Azure PowerShell instructions. The PowerShell example is given equal prominence to the CLI example, and the workflow assumes familiarity with Visual Studio Code and the Azure portal, both of which are more commonly used on Windows. There are no explicit Linux-specific instructions, troubleshooting tips, or alternative editors/IDEs mentioned.

Recommendations:

Add explicit Linux/macOS instructions or notes, especially for environment setup and tool installation.
Include examples using other popular languages and runtimes (such as Python or Node.js) that are commonly used on Linux.
Mention alternative editors (such as Vim, Emacs, or JetBrains IDEs) or at least clarify that Visual Studio Code is cross-platform.
Provide troubleshooting tips for Linux users (e.g., file permissions, shell differences).
Clarify that both Azure CLI and cURL commands work natively on Linux/macOS, and provide any necessary adjustments (such as date command syntax differences).
Consider adding a section or callout for Linux users to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), using only PowerShell commands for package installation, and providing step-by-step instructions and screenshots that assume a Windows environment. There are no instructions or examples for Linux or cross-platform .NET development tools (such as VS Code, JetBrains Rider, or the .NET CLI), nor are alternative package installation methods (like 'dotnet add package') shown. This may hinder accessibility for Linux and macOS users.

Recommendations:

Add instructions for using the .NET CLI (e.g., 'dotnet new console', 'dotnet add package Azure.Messaging.EventGrid.Namespaces') alongside Visual Studio steps.
Include screenshots and steps for cross-platform editors like VS Code, or provide generic instructions not tied to a specific IDE.
Replace PowerShell-only package installation commands with cross-platform alternatives, or provide both PowerShell and shell/bash equivalents.
Explicitly mention that the sample code and instructions work on Linux and macOS, and provide any OS-specific notes if needed.
Consider a 'tabbed' format for instructions, allowing users to select their OS or preferred development environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by requiring Visual Studio (a Windows-centric IDE) for publishing the Azure Functions app and running the sample generator, with no mention of cross-platform alternatives. All development and deployment steps involving code are described using Visual Studio, and there are no instructions or examples for Linux or macOS users (e.g., using VS Code, Azure Functions Core Tools, or .NET CLI). The prerequisites and workflow assume a Windows environment, omitting Linux-native development tools and workflows.

Recommendations:

Add instructions for publishing the Azure Functions app using cross-platform tools such as Azure Functions Core Tools and the .NET CLI, which work on Linux and macOS.
Include examples for running the sample data generator using the .NET CLI (dotnet run) instead of only referencing the Windows .exe file.
Mention and provide guidance for using Visual Studio Code as an alternative to Visual Studio, including relevant extensions for Azure Functions and C# development.
Explicitly state that the tutorial can be completed on Linux and macOS, and provide any necessary setup steps for those platforms.
Ensure that all code publishing, deployment, and sample running steps have Linux/macOS equivalents, and present them alongside or before Windows-specific instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. While it provides code samples for multiple languages and includes an Azure CLI example, it also features a dedicated PowerShell tab and references to Windows-centric tools and patterns. The instructions for obtaining Azure region names use the Azure CLI, which is cross-platform, but the presence of both CLI and PowerShell tabs (with no explicit mention of Bash or Linux shell scripting) suggests a preference for Windows environments. There are no explicit Linux-specific examples or guidance, and the sample web application links do not mention Linux deployment or setup. The documentation does not address Linux-specific development environments or tools, and the order of examples (PowerShell is included, but no Bash or Linux shell) further reinforces the Windows-first approach.

Recommendations:

Add explicit Linux/Bash shell scripting examples alongside PowerShell, especially for common setup and management tasks.
Include instructions or notes for Linux/macOS users regarding environment setup, authentication, and running the CLI commands.
Provide sample code or deployment instructions for Linux-based environments (e.g., Ubuntu, CentOS) in the 'Samples with detailed instructions' section.
Ensure parity in tooling references—if PowerShell is included, also include Bash or other popular Linux shells.
Clarify that Azure CLI is cross-platform and provide any Linux-specific caveats or tips where relevant.
Consider the order of code tabs: avoid placing Windows-specific tools (PowerShell) before cross-platform or Linux-native options.

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 as an event handler for Event Grid. However, it includes detailed PowerShell instructions and examples, which are primarily relevant to Windows environments, without offering equivalent Linux-native scripting examples (such as Bash or shell scripting). The PowerShell sections are given equal prominence to the CLI, and there is no mention of Linux-specific tools or patterns. This may give the impression of a Windows-centric approach, especially for users seeking Linux-native automation guidance.

Recommendations:

Clarify that Azure CLI commands are fully cross-platform and can be run on Linux, macOS, and Windows.
Consider providing Bash or shell script examples for automation scenarios, especially in sections where PowerShell is featured.
Explicitly mention that PowerShell Core is available cross-platform, or provide links to Linux installation instructions if PowerShell examples are retained.
Add a note or section highlighting Linux and macOS support for all command-line operations, and recommend CLI as the default for cross-platform compatibility.
Where possible, include troubleshooting or environment setup notes relevant to Linux users (e.g., authentication, environment variables).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and PowerShell examples for configuring dead-letter and retry policies in Azure Event Grid. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and there are explicit references to installing Azure PowerShell, which is most commonly used on Windows. There are no Linux shell-specific examples (e.g., Bash scripting), and the sample application linked is .NET-based, which is also more common in Windows environments. The documentation does not mention or demonstrate Linux-native tools or workflows, and PowerShell is presented as a primary automation option alongside Azure CLI.

Recommendations:

Add explicit Bash shell examples for all CLI commands, demonstrating variable assignment and command usage in a Linux context.
Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows, and provide installation links for all platforms.
De-emphasize PowerShell as a primary automation tool by placing Azure CLI (and Bash) examples before PowerShell examples.
Include sample applications or links for other languages and platforms (e.g., Python, Node.js) that are popular in Linux environments.
Mention that all features described are available and supported on Linux, and provide troubleshooting tips for common Linux-specific issues if any.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias by exclusively using PowerShell scripts and the Azure Cloud Shell (with PowerShell environment) for all scripting and automation steps. There are no Bash, Linux shell, or cross-platform scripting examples provided. The instructions assume the user is familiar with PowerShell and do not mention or provide alternatives for Linux users, despite Azure Cloud Shell supporting Bash. This could hinder Linux users or those who prefer Bash scripting from following the guide effectively.

Recommendations:

Provide equivalent Bash shell script examples for all PowerShell scripts and commands, especially for steps involving Microsoft Graph and Azure CLI.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and offer instructions for both environments.
Where referencing downloadable scripts, provide both .ps1 (PowerShell) and .sh (Bash) versions.
Ensure that all variable setup and authentication steps are shown in both PowerShell and Bash syntax.
Review diagrams and screenshots to ensure they are not Windows-specific (e.g., showing only PowerShell prompts or Windows UI elements).
Add a note at the beginning clarifying that the instructions are cross-platform and that users can choose their preferred shell environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing code samples and command-line instructions that are Windows-centric. The only code sample is in C# (commonly associated with Windows development), and the CLI example for Azure Relay Bridge uses a Windows-style executable invocation ('.\azbridge.exe'), with no Linux equivalent shown. There are no Linux shell or cross-platform code examples, and Windows tools and patterns are mentioned or implied before any Linux alternatives.

Recommendations:

Provide equivalent Linux/bash shell command examples for running Azure Relay Bridge (e.g., './azbridge' instead of '.\azbridge.exe').
Include code samples in additional languages commonly used on Linux (such as Python, Node.js, or Java), or explicitly mention that the logic can be implemented in any language.
Clarify that Azure Relay Bridge can be run on Linux, and provide Docker usage examples.
When showing CLI commands, use cross-platform syntax or show both Windows and Linux variants.
Avoid using only Windows file path and executable conventions; include Linux equivalents.
Explicitly state the cross-platform nature of the tools and provide links or instructions for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

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 traditionally Windows-centric, though now available cross-platform) and the absence of any Linux shell-specific examples (e.g., Bash scripting, environment variable usage, or Linux-native tools) indicates a bias towards Windows users. Additionally, PowerShell examples are given equal prominence to CLI, and there are no Linux-first or Linux-specific instructions or troubleshooting notes. The documentation also uses PowerShell cmdlets and patterns that are more familiar to Windows administrators.

Recommendations:

Add explicit Bash/Linux shell examples, especially for scripting or automation scenarios (e.g., using environment variables, piping, jq for JSON parsing).
Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
If PowerShell is included, consider also including Bash or shell script equivalents for common tasks.
Highlight cross-platform compatibility in the introduction and in each section, reassuring Linux users.
If there are any differences in behavior or prerequisites on Linux (e.g., authentication, file paths), call these out in notes or tips.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows a clear Windows bias: PowerShell/Windows tools (psping.exe) are featured prominently, with Windows commands given first and in more detail. Linux alternatives are either missing or only briefly mentioned. For example, the main port-checking example uses a Windows-only tool, and the Linux example (telnet) is less robust and not equivalent. Other troubleshooting steps reference Windows tools without Linux parity.

Recommendations:

Provide Linux-native command examples (e.g., use 'nc' or 'nmap' instead of 'telnet' for port checking, and show full command syntax).
Present Windows and Linux examples side-by-side for all troubleshooting steps, ensuring parity in detail and capability.
Mention cross-platform or Linux tools (e.g., 'tcpping' for Linux, or 'hping3') wherever Windows tools are referenced.
Avoid giving Windows examples first by default; alternate or present both at the same time.
Clarify tool availability and installation steps for both platforms.
Ensure that all troubleshooting steps are actionable on both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides examples for Azure CLI, Azure PowerShell, and Azure Portal. However, it demonstrates a Windows bias by including extensive PowerShell examples (which are primarily associated with Windows environments) and referencing Azure PowerShell modules, which are more familiar to Windows users. There is no mention of Bash, Linux shell scripting, or cross-platform scripting alternatives. Additionally, PowerShell examples are given equal prominence to CLI examples, and the documentation does not clarify that Azure CLI is cross-platform and preferred for Linux/macOS users. There are no Linux-specific notes or troubleshooting tips.

Recommendations:

Explicitly mention that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
Add Bash shell scripting examples or notes for Linux users, especially for scripting and automation scenarios.
Clarify that Azure PowerShell is available cross-platform, but is more familiar to Windows users, and recommend Azure CLI for Linux/macOS users.
Include troubleshooting tips or environment setup notes for Linux users (e.g., installing Azure CLI on Ubuntu, handling authentication).
Avoid assuming PowerShell as the default scripting environment; consider reordering sections to present Azure CLI before PowerShell, or add a note explaining the intended audience for each.
Where screenshots or portal instructions are given, note any differences in experience for Linux/macOS users if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides code samples for multiple languages (NodeJS, Java, PHP, C#, PowerShell, Bash) when generating SAS tokens, which is positive for cross-platform parity. However, the PowerShell example appears before the Bash example, and the Bash example is provided last, which may indicate a subtle 'windows_first' ordering. The PowerShell example is also more detailed and uses Windows-specific .NET libraries, which may not be available or work the same way on Linux. There are no explicit Linux command-line (e.g., curl, openssl) examples outside of Bash, and no mention of Linux-specific tools or patterns. The documentation references Azure portal and ARM templates for configuration, which are cross-platform, but does not mention Azure CLI or other Linux-native tools for disabling SAS authentication. There is also a heavy focus on .NET/.NET samples in the 'Samples' section, with no direct links to Linux/JavaScript/Python samples.

Recommendations:

Reorder code samples so that Bash (or other cross-platform scripting languages) appear before PowerShell, or present them side-by-side to avoid implying a Windows-first approach.
Provide explicit Linux command-line examples (e.g., using curl and openssl) for generating SAS tokens and authenticating, in addition to Bash functions.
Include references to Azure CLI commands for configuration tasks (such as disabling SAS authentication), as Azure CLI is widely used on Linux.
Add links to sample code repositories for non-.NET languages (e.g., Java, Python, Node.js) in the 'Samples' section to ensure parity.
Where PowerShell is used, clarify if it is cross-platform (PowerShell Core) or Windows-only, and provide equivalent Bash or shell commands for Linux users.
Mention Linux tools or patterns where appropriate, such as using jq, curl, or openssl, and ensure that all steps can be performed on both Windows and Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. While it is mostly platform-neutral, it references Azure PowerShell before Azure CLI in the 'Related content' section, and the sample code and walkthroughs focus on .NET and Java, which are more commonly associated with Windows development environments. There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-specific tools or workflows. The documentation does not provide parity in terms of Linux shell (bash) or cross-platform scripting examples for authentication or role assignment.

Recommendations:

Present Azure CLI examples before or alongside Azure PowerShell, as CLI is cross-platform and widely used on Linux.
Include bash or shell script examples for authentication and role assignment to demonstrate Linux parity.
Add explicit notes or sections on how to perform key steps (such as registering applications, assigning roles, and acquiring tokens) from Linux or macOS environments.
Provide sample code or links for Python or Node.js SDKs, which are popular in Linux development, in addition to .NET and Java.
Ensure that screenshots and walkthroughs do not assume a Windows environment (e.g., avoid showing only Windows-style file paths or UI).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page does not provide explicit command-line examples for either Windows or Linux, but all code samples and references are exclusively to .NET (C#) libraries and samples, which are most commonly associated with Windows development environments. There are no Bash, Linux CLI, or cross-platform code examples, nor are there references to Linux-specific tools or workflows. The documentation also omits any mention of Linux authentication patterns (such as using Azure CLI in Bash) or cross-platform SDKs (like Python or Java), and all sample links point to .NET code.

Recommendations:

Add Linux/Bash command-line examples for authenticating and authorizing with Microsoft Entra ID (e.g., using Azure CLI in Bash).
Include code samples in cross-platform languages such as Python, Java, or Node.js, not just .NET.
Reference Linux tools and workflows (such as az CLI usage in Linux shells) alongside or before Windows/PowerShell equivalents.
Provide explicit instructions or links for Linux users, including how to set up managed identities and assign roles from a Linux environment.
Ensure that sample repositories include folders or instructions for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by mentioning PowerShell and Azure CLI as configuration options, but listing PowerShell before Azure CLI and not providing any explicit Linux or cross-platform command-line examples. There are no Linux-specific instructions or examples, and the mention of PowerShell as a primary tool may alienate Linux users. The phrase 'via PowerShell or Azure CLI' puts the Windows tool first, and there is no parity in examples or guidance for Linux environments.

Recommendations:

When listing command-line tools, mention Azure CLI before or alongside PowerShell, as Azure CLI is cross-platform.
Include explicit Linux/macOS examples or clarify that Azure CLI commands work on all platforms.
Avoid assuming PowerShell as the default scripting environment; provide Bash or shell script examples where appropriate.
Add a section or note for Linux users, highlighting any platform-specific considerations or steps.
Ensure that all instructions and examples are equally accessible and relevant to both Windows and Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for configuring Event Hub properties, but PowerShell (a Windows-centric tool) is given a dedicated section and is mentioned alongside cross-platform tools. There are no explicit Linux shell or scripting examples, and the PowerShell section could be perceived as prioritizing Windows users. The GUI instructions also implicitly assume the Azure Portal, which is platform-agnostic but often associated with Windows workflows.

Recommendations:

Add explicit Linux/Bash shell examples for using the Azure CLI, including command-line snippets that demonstrate usage in a Linux environment.
Clarify that Azure CLI is cross-platform and works on Windows, Linux, and macOS.
Consider including examples for automation using Bash scripts or other Linux-native tools where appropriate.
If mentioning PowerShell, also mention that PowerShell Core is available cross-platform, or provide equivalent Bash/Unix shell alternatives.
Ensure that the order of examples does not always place Windows/PowerShell first; alternate or clarify cross-platform applicability.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by presenting PowerShell as the first and most detailed example for updating partition counts, followed by the Azure CLI. PowerShell is a Windows-centric tool, and its prominence suggests a preference for Windows environments. There is no explicit Linux shell example (e.g., Bash), and the CLI example, while cross-platform, is not highlighted as such. Additionally, references to Windows-specific SDKs (e.g., WindowsAzure.ServiceBus) further reinforce the Windows bias.

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.
Include Bash or shell script examples where appropriate, especially for automation scenarios.
When referencing SDKs or libraries, avoid Windows-specific naming or clarify cross-platform support.
Add a note or section for Linux users, highlighting any differences or additional steps required.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a significant Windows/Powershell bias. Most command-line examples for deploying and configuring resources (such as deploying ARM templates, setting access policies, and retrieving identities) are provided exclusively using PowerShell, with no equivalent Azure CLI (bash/shell) examples. The instructions for running these commands assume a Windows environment, and there is no guidance for Linux or macOS users. While some sections mention that Azure CLI can be used, all concrete step-by-step examples default to PowerShell, and no bash/CLI scripts are shown for critical tasks. This may hinder Linux/macOS users or those who prefer cross-platform tooling.

Recommendations:

For every PowerShell example, provide an equivalent Azure CLI (bash/shell) example, especially for deployment, access policy, and identity management steps.
When referencing command-line tools, mention both PowerShell and Azure CLI options, and do not assume a Windows environment.
Where possible, use Azure CLI as the primary example, as it is cross-platform, or present CLI examples before PowerShell to avoid a 'Windows-first' impression.
Explicitly state that all steps can be performed on Linux/macOS using Azure CLI, and provide links or code blocks for those workflows.
Add a section or callout for Linux/macOS users, summarizing any differences or additional steps required.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns (such as 'command prompt', backslash path separators, and lack of Linux/MacOS terminal instructions). There are no explicit Linux or cross-platform instructions for running scripts or handling file paths, and all examples assume a Windows environment.

Recommendations:

Provide equivalent instructions for Linux and MacOS, such as using 'terminal' instead of 'command prompt', and show relevant shell commands.
Use platform-agnostic path handling in code examples (e.g., os.path.join instead of hardcoded backslashes).
Show both Windows and Linux/MacOS commands for installing dependencies and running scripts.
Explicitly mention that the scripts are cross-platform and note any platform-specific considerations.
Include screenshots or terminal output from Linux/MacOS environments where appropriate.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a Windows/.NET bias by providing only .NET (C#) code samples, referencing Windows-centric tools and workflows, and prioritizing Windows/PowerShell instructions for prerequisites. There are no examples or guidance for Linux users or for other programming languages/platforms commonly used on Linux.

Recommendations:

Add equivalent code samples in other languages/platforms commonly used on Linux, such as Python (using Azure SDK for Python) or Java.
Include explicit instructions and examples for Linux environments, such as using Bash or Azure CLI for authentication and management tasks.
Reorder or balance prerequisite instructions so that Azure CLI (cross-platform) is listed before or alongside Azure PowerShell.
Clarify that the management libraries are currently only available for .NET, and provide alternative approaches for Linux users if possible (e.g., using REST API or Azure CLI for management tasks).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a strong Windows bias. All instructions for project creation, package installation, and tool usage are centered around Visual Studio 2022 and the NuGet Package Manager Console (PowerShell-based), with no mention of cross-platform alternatives like the .NET CLI or Visual Studio Code. There are no Linux or macOS-specific instructions or screenshots, and the workflow assumes a Windows/Visual Studio environment throughout.

Recommendations:

Add parallel instructions for Linux/macOS users, including steps for using the .NET CLI (e.g., 'dotnet new console', 'dotnet add package ...') for project creation and package management.
Include guidance for using Visual Studio Code or JetBrains Rider, which are cross-platform IDEs.
Replace or supplement Visual Studio-specific steps and screenshots with .NET CLI commands and generic editor instructions.
Explicitly state that the .NET SDK and Azure SDK libraries are cross-platform, and provide any necessary notes for running on Linux/macOS (e.g., authentication differences, environment variables).
Where PowerShell commands are shown, also provide Bash/zsh equivalents if applicable.
Review all tool references (e.g., 'Tools > NuGet Package Manager > Package Manager Console') and ensure Linux/macOS users are not excluded from the workflow.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows/.NET bias. While the article is cross-platform in its protocol focus (Kafka, AMQP, HTTPS) and provides both Java and C# (.NET) code samples, the .NET examples are consistently present and sometimes more detailed, especially in serialization/deserialization sections. There is an implicit assumption of .NET usage (e.g., references to BitConverter endianness on x86/x64, which is Windows-centric), and no Linux-specific considerations or examples are provided. There are no Linux shell or tool examples, and the .NET code is always C# (not F# or VB.NET, which are less common, but still Windows-centric). There is no mention of Linux-specific issues, tools, or patterns, and the .NET examples sometimes precede or are more detailed than their Java counterparts.

Recommendations:

Add explicit Linux/Unix examples or notes, especially where endianness or filesystem differences may matter.
Include shell (bash) or Linux command-line examples for interacting with Event Hubs via HTTPS (e.g., using curl), not just code samples in Java or C#.
Balance the depth and order of .NET and Java examples, ensuring neither is consistently prioritized.
Mention cross-platform .NET Core/5+/6+ usage explicitly, rather than implicitly assuming Windows/.NET Framework.
Where platform-specific behavior is discussed (e.g., endianness), clarify that .NET runs cross-platform and note any differences on Linux/macOS.
Consider adding Python or other popular cross-platform language examples to further reduce perceived Windows bias.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates subtle Windows bias by referencing Microsoft Excel's CSV limitations as the primary example for CSV file handling, without mentioning Linux or cross-platform alternatives. There are no explicit Linux or macOS examples or tool mentions, and the only workaround suggested for CSV issues is to use 'another program that supports CSV files,' without naming any non-Windows options. No command-line or scripting examples (e.g., PowerShell, Bash) are present, but the only tool specifically named is a Windows product. The documentation assumes a Windows-centric environment, which may leave Linux users without clear guidance.

Recommendations:

When discussing CSV file exports, explicitly mention popular Linux (and macOS) tools such as LibreOffice Calc, Gnumeric, or command-line utilities like 'csvkit' or 'awk' as alternatives to Microsoft Excel.
Provide examples or notes for users on non-Windows platforms regarding how to open and manipulate CSV files, including any known limitations or best practices.
Avoid referencing only Windows tools or behaviors (such as Excel's cell limit) without also noting whether similar issues exist in Linux/macOS tools.
Where possible, include screenshots or instructions that are platform-agnostic or show parity between Windows and Linux environments.
If command-line or scripting is discussed in future documentation, ensure both PowerShell (Windows) and Bash (Linux/macOS) examples are provided.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias in its presentation of manual failover methods. In the 'Manual failover' section, the Azure portal (GUI), Azure CLI, PowerShell, and C# methods are listed, but there is no explicit mention of Linux-specific tools or scripting languages (e.g., Bash, Python). PowerShell is highlighted as a primary automation method, which is traditionally Windows-centric, and there are no Linux shell script or REST API examples. Additionally, the CLI example is generic and does not provide a full command-line walkthrough, and there are no Bash or cross-platform scripting examples. The documentation also lacks explicit mention of Linux environments or considerations for Linux administrators.

Recommendations:

Provide explicit Bash shell script examples for common operations (e.g., using Azure CLI in Bash for failover).
Include REST API examples with curl commands to demonstrate cross-platform automation.
Clarify that Azure CLI is fully supported on Linux and macOS, and provide sample commands in a Linux terminal context.
Add Python or other cross-platform SDK examples alongside C#.
Avoid listing PowerShell before CLI or cross-platform tools, or alternate the order to avoid implying preference.
Explicitly mention that all operations can be performed from Linux/macOS as well as Windows, and provide links to relevant setup guides.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing a detailed Azure PowerShell example for configuring firewall rules, while not offering equivalent command-line examples for Linux users (e.g., Bash or Azure CLI scripting). The PowerShell example is given its own section and is more comprehensive than the brief mention of Azure CLI. There is no explicit Linux/Bash example, and the CLI section lacks sample commands. The deployment instructions for ARM templates link to a PowerShell deployment guide, further reinforcing the Windows-centric approach.

Recommendations:

Add detailed Azure CLI examples for managing firewall rules, including sample commands for adding, listing, updating, and removing IP rules, similar in depth to the PowerShell example.
Provide Bash scripting examples for ARM template deployment, or at least link to cross-platform deployment instructions (e.g., Azure CLI or Bash).
Ensure that Azure CLI examples are presented before or alongside PowerShell examples to avoid the impression of Windows-first bias.
Explicitly mention that all Azure CLI commands work cross-platform (Windows, Linux, macOS) to encourage non-Windows users.
Where possible, include screenshots or references to command-line tools available on Linux/macOS, not just the Azure portal or PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits mild Windows bias. It instructs users to 'open a Command Prompt window' to install npm packages, and the sample output for running the receiver is shown with a Windows path prompt (e.g., 'C:\Self Study\Event Hubs\JavaScript>'). There are no explicit Linux/macOS terminal examples or mentions of common Linux shells (e.g., bash, zsh), and the guidance assumes familiarity with Windows tools and conventions.

Recommendations:

Replace 'open a Command Prompt window' with 'open a terminal window' or mention both Command Prompt (Windows) and Terminal (Linux/macOS).
Provide sample commands and outputs using generic POSIX-style paths (e.g., '/home/user/EventHubs/JavaScript>') or show both Windows and Linux/macOS examples side by side.
Explicitly state that the instructions apply to Windows, Linux, and macOS, and that Node.js/npm commands work the same way across platforms.
Where IDEs are mentioned, note that Visual Studio Code is cross-platform, and users may use any editor or terminal of their choice.
Avoid using Windows-specific path separators (\) in examples, or provide both Windows and Linux/macOS path formats.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page shows a mild Windows bias. It specifically references running commands on a Windows machine and mentions using a 'Node.js command prompt' on Windows, but does not provide equivalent instructions or considerations for Linux or macOS users. There are no Linux-specific examples or notes, and the only environment-specific guidance is for Windows.

Recommendations:

Add explicit instructions for running the Java/Maven commands on Linux and macOS, including any differences in environment setup or command syntax.
Replace or supplement references to 'Node.js command prompt' and 'Windows machine' with cross-platform alternatives, such as 'terminal' or 'command line interface', and clarify that the commands work on all major operating systems.
Include a note or section confirming that the steps and commands are applicable to Linux/macOS, and mention any OS-specific prerequisites or troubleshooting tips.
If screenshots or UI references are OS-specific, provide alternatives or clarify that the experience may differ on other platforms.

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 deployment, validation, and cleanup examples use Azure PowerShell exclusively, with no mention or example of Azure CLI, Bash, or other cross-platform tools. This leaves out Linux and macOS users who may prefer or require CLI-based instructions not tied to PowerShell.

Recommendations:

Add equivalent Azure CLI (az) examples for deployment, validation, and cleanup steps, ideally using Bash syntax.
Present both PowerShell and CLI examples side-by-side or allow the user to select their preferred environment.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
Ensure that references to scripts, commands, and tooling are not exclusively PowerShell-centric, and avoid implying PowerShell is the default or only option.
Consider including a table or toggle for users to choose between Windows/PowerShell and Linux/Bash/CLI 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 commands in a dedicated section after Azure CLI, without providing any Linux-specific or cross-platform command-line examples. The only explicit command-line examples are for Azure CLI and PowerShell, both of which are available on Windows, but PowerShell is traditionally associated with Windows environments. There are no Linux shell (bash) examples, and no mention of Linux-specific tools or workflows. Additionally, the 'Next steps' section links to PowerShell deployment instructions, reinforcing a Windows-centric approach.

Recommendations:

Provide explicit bash or Linux shell examples for all command-line operations, especially for Azure CLI usage.
Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
Include links to Linux/macOS deployment guides alongside PowerShell guides in the 'Next steps' section.
When listing command-line tools, present Azure CLI before PowerShell, or present them together with equal prominence.
Add notes or examples for using Resource Manager templates with Linux-native tools (e.g., az deployment group create) rather than only referencing PowerShell deployment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell CLI examples for scripting, omitting equivalent Azure CLI (cross-platform) or Bash examples. Additionally, the validation steps explicitly instruct users to create and use a Windows virtual machine, with no mention of Linux VM alternatives. This approach assumes a Windows-centric workflow and does not offer parity for Linux or cross-platform users.

Recommendations:

Provide equivalent Azure CLI (az) and/or Bash scripting examples alongside PowerShell for all automation and resource creation steps.
In the validation section, include instructions for creating and using a Linux virtual machine, or make the instructions OS-agnostic (e.g., show both Windows and Linux VM creation links, and provide nslookup commands for both environments).
Where screenshots or UI steps are shown, clarify that the Azure portal is cross-platform and accessible from any OS.
Explicitly state that all steps can be performed from Windows, Linux, or macOS, and provide links to relevant cross-platform tooling documentation.
Review for any other Windows-specific terminology or assumptions, and ensure Linux and macOS users are equally supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. While it covers cross-platform SDKs and mentions Azure CLI (which is cross-platform), it specifically highlights PowerShell as a management tool and provides a PowerShell example link, but does not provide equivalent Linux shell or Bash examples. The order of mention also places PowerShell alongside Azure CLI, which may suggest a Windows-first approach. There is no explicit example or guidance for Linux-native tools or shell scripting, and the management samples section omits Bash or Linux command-line usage.

Recommendations:

Add explicit Bash or Linux shell examples for schema management tasks, especially for adding schemas to schema groups.
Ensure that CLI examples are presented before or alongside PowerShell to avoid a Windows-first impression.
Where PowerShell is mentioned, clarify that it is primarily for Windows users and provide equivalent commands for Linux/macOS users.
Consider including a section or links for Linux-native management workflows, such as Bash scripts or usage with common Linux tools.
Review the order of tool presentation to ensure cross-platform parity and avoid prioritizing Windows tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias by exclusively referencing Windows tools (Visual Studio, Package Manager Console), providing only Windows-oriented instructions (e.g., Visual Studio UI steps, PowerShell/Install-Package commands), and omitting any Linux or cross-platform alternatives for project setup, dependency management, or authentication. There are no instructions for using .NET CLI, VS Code, or command-line workflows common on Linux/macOS, nor any mention of Linux-specific considerations.

Recommendations:

Add parallel instructions for Linux/macOS users, including how to create and manage .NET projects using the dotnet CLI (e.g., 'dotnet new console', 'dotnet add package').
Include examples of installing dependencies using the dotnet CLI instead of only 'Install-Package' via Package Manager Console.
Mention and provide steps for using cross-platform editors like VS Code, and clarify that Visual Studio is not required.
Provide authentication guidance for non-Visual Studio environments (e.g., Azure CLI login, environment variables).
Explicitly state that all code and tools are cross-platform, and note any platform-specific differences or requirements.
Where screenshots or UI steps are given for Visual Studio, offer equivalent command-line or VS Code instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing detailed PowerShell examples (a Windows-centric tool), listing PowerShell before CLI in several sections, and omitting any Linux-specific shell or scripting examples. There are no bash or Linux-native command examples, and the use of PowerShell is assumed as a primary automation tool. The CLI examples are present but are not explicitly shown in a Linux context, and there are no references to Linux tools or scripting patterns.

Recommendations:

Add explicit bash/Linux shell examples for all CLI commands, including sample scripts and environment variable usage.
Clarify that Azure CLI commands work cross-platform and provide sample outputs from both Windows (CMD/PowerShell) and Linux (bash).
Avoid listing PowerShell before CLI unless there is a technical reason; alternate the order or clarify parity.
Include notes or sections on using these commands in Linux environments, including any differences in authentication, file paths, or environment setup.
Where automation is discussed, provide both PowerShell and bash scripting examples to ensure Linux users are equally supported.
Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, and provide Linux installation instructions if relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by prioritizing Windows-specific instructions and tools, such as PowerShell and WSL, and by providing more detailed, step-by-step guidance for Windows users. Linux and macOS instructions are less detailed and often grouped together, with some steps (like directory navigation) omitted. There is also a focus on Docker Desktop, which is more common on Windows, and explicit notes about Windows path conventions, while Linux equivalents are not discussed.

Recommendations:

Provide equally detailed, step-by-step instructions for Linux and macOS users, including terminal commands for directory navigation and script execution.
List Linux and macOS instructions before or alongside Windows instructions, rather than after.
Include Linux-native Docker installation links and prerequisites, not just Docker Desktop (which is Windows/macOS-centric).
Offer explicit examples of file path conventions for Linux/macOS in addition to Windows.
Avoid requiring WSL for Windows users unless absolutely necessary, and clarify when native Linux/macOS environments are supported.
Ensure that all scripts and commands are shown in both PowerShell (Windows) and Bash (Linux/macOS) formats where applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only a .NET example for configuring TLS, which is most commonly associated with Windows environments, and references Fiddler—a Windows-centric tool—for verifying TLS versions. There are no examples or tool recommendations for Linux or cross-platform environments, and Windows tools are mentioned first and exclusively.

Recommendations:

Add examples for configuring TLS in client applications using common Linux-compatible languages and frameworks (e.g., Python, Java, Node.js).
Include instructions or examples for verifying TLS versions using cross-platform or Linux-native tools such as Wireshark, tcpdump, or OpenSSL.
When mentioning tools, provide both Windows and Linux alternatives, or recommend cross-platform tools first.
Clarify that the .NET example is applicable on both Windows and Linux (if true), or provide equivalent Linux-specific guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in the section on checking the minimum required TLS version. It exclusively provides instructions and examples using ARMClient.exe (a Windows executable) and PowerShell commands for authentication, with no mention of Linux or cross-platform alternatives. There are no CLI, Bash, or platform-agnostic REST examples for obtaining the Bearer token or querying the API, which may hinder Linux or macOS users.

Recommendations:

Provide cross-platform instructions for obtaining a Bearer token, such as using Azure CLI (az account get-access-token) or curl commands.
Include Bash or shell script examples alongside PowerShell/Windows-specific instructions.
Mention and demonstrate the use of ARMClient alternatives or REST API calls that can be executed on any platform.
Ensure that any tool or command referenced is available on both Windows and Linux, or provide equivalent alternatives for each platform.
Explicitly state when a tool is Windows-only and offer a Linux/macOS-compatible workflow in parallel.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing troubleshooting commands and tool recommendations that are Windows-centric (e.g., psping.exe, PowerShell commands), mentioning Windows tools first, and omitting explicit Linux equivalents or examples. While there is a brief mention of using 'wget' for connectivity checks, the majority of actionable examples and tool links are tailored to Windows users, with little guidance for Linux users.

Recommendations:

Provide equivalent Linux commands and tools alongside Windows examples (e.g., use 'nc' or 'nmap' for TCP connectivity tests on Linux, and show example commands).
List cross-platform tools first, or present both Windows and Linux options together, rather than defaulting to Windows tools.
Include explicit Linux shell command examples for tasks like checking connectivity, dropped packets, and network tracing.
Mention and link to Linux-compatible tools (e.g., 'netcat', 'ss', 'tcpdump') where appropriate.
Clarify that 'psping.exe' is Windows-only and suggest alternatives for Linux/Mac users.
Ensure parity in troubleshooting steps and tool recommendations for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation lists PowerShell as a primary method for upgrading circuit bandwidth, and mentions it before Azure CLI, which is more cross-platform and Linux-friendly. There are no explicit Linux or Bash examples, and the focus on PowerShell may suggest a Windows-centric approach.

Recommendations:

Present Azure CLI examples before or alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux.
Include explicit Bash/Linux shell command examples where relevant, especially for common administrative tasks.
Clarify that all operations can be performed from Linux, macOS, or Windows, and provide parity in step-by-step instructions for each platform.
Avoid implying 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 page references Azure PowerShell specifically as a configuration method for ExpressRoute FastPath, without mentioning or providing parity for Linux/CLI-based alternatives. The 'Next steps' section lists PowerShell before any cross-platform tools, and there are no explicit examples or guidance for Linux users (e.g., Azure CLI or Bash scripting). This creates a Windows-first impression and lacks Linux parity.

Recommendations:

Add explicit instructions and examples for configuring ExpressRoute FastPath using Azure CLI, which is cross-platform and commonly used on Linux.
In the 'Next steps' section, list Azure CLI and PowerShell options together, or list CLI first to avoid Windows-first bias.
Wherever PowerShell is mentioned, provide equivalent Bash or Azure CLI commands.
Include notes or links for Linux/macOS users to ensure they can follow along without needing Windows-specific tools.
Review all configuration steps and ensure that none are exclusive to Windows or PowerShell, and that Linux users are not left out.

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 or REST-based examples that are cross-platform. The initial setup steps assume the use of PowerShell, which is most commonly used on Windows, and there is no mention of Linux or macOS workflows. All other API interactions are shown as REST calls, which are platform-neutral, but the critical first step (provider registration) lacks Linux parity.

Recommendations:

Add Azure CLI examples for subscription registration and provider feature registration, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that the REST API and Azure CLI can be used from any OS, and provide equivalent commands for each step where possible.
Consider reordering or presenting Azure CLI and REST examples before or alongside PowerShell to avoid the impression of Windows-first workflows.
Include a note or section addressing cross-platform usage, clarifying that all API operations can be performed from Linux, macOS, or 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 examples and instructions use Windows PowerShell cmdlets, and there is no mention of Linux or cross-platform alternatives. The prerequisites specifically require the Windows PowerShell module, and there are no Bash, Azure CLI, or Linux-native instructions or examples. This makes the documentation less accessible to users on Linux or macOS platforms.

Recommendations:

Provide equivalent instructions and examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
Include Bash shell examples for retrieving ARP tables or interacting with Azure resources.
Mention and link to Linux/macOS installation guides for Azure CLI or other relevant tools.
Clearly indicate which steps are Windows-specific and provide parity for non-Windows users.
Review prerequisites to ensure they are not Windows-exclusive unless absolutely necessary, and offer alternatives where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for command-line configuration, with no mention of Azure CLI or Bash equivalents that are commonly used on Linux and macOS. The PowerShell steps are presented as the sole scripting option, and the documentation references Windows-centric tools and patterns without offering Linux alternatives or parity.

Recommendations:

Add equivalent Azure CLI (az) command examples alongside PowerShell for all configuration steps.
Explicitly mention that the steps can be performed from any OS using Azure CLI or Cloud Shell, not just from Windows/PowerShell.
Include Bash script examples or note cross-platform compatibility where possible.
Reorder or present PowerShell and CLI steps in parallel, or provide a clear choice for users based on their platform.
Review included content (INCLUDE files) to ensure Linux and cross-platform instructions are present.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively showing command-line examples using Windows file paths (e.g., C:\Users\...), and referencing the ARMClient tool as if it is being run from a Windows environment. There are no Linux or cross-platform shell examples, and no mention of Linux-compatible tools or usage patterns. The documentation assumes a Windows user context throughout, which may hinder Linux users.

Recommendations:

Provide equivalent Linux/macOS shell examples (e.g., using bash/zsh) alongside Windows command-line examples.
Clarify whether ARMClient is available and supported on Linux/macOS, and provide installation and usage instructions for those platforms if so.
Use platform-neutral file paths in documentation, or show both Windows and Linux path examples where relevant.
Explicitly mention that the API can be accessed from any OS, and provide curl or HTTPie examples for REST API calls, which are available on all platforms.
Avoid assuming a Windows user context in narrative or examples; strive for parity in tool recommendations and usage instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by prominently featuring Azure PowerShell cmdlets as the only explicit command-line tooling for managing IP Groups. While it mentions the Azure portal, Azure CLI, and REST API as options, it provides detailed links and examples only for PowerShell, which is primarily associated with Windows environments. There are no Azure CLI (cross-platform) or REST API command examples or references, and no Linux-specific guidance is provided.

Recommendations:

Add equivalent Azure CLI commands and documentation links for all PowerShell cmdlets listed, ensuring Linux and macOS users have clear, first-class instructions.
Include REST API examples or references alongside PowerShell and CLI, to support automation and cross-platform use.
When listing tools or commands, present Azure CLI and REST API options before or alongside PowerShell to avoid implying Windows-first workflows.
Explicitly state that all management operations can be performed from Linux, macOS, and Windows, and provide examples for each where relevant.

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 cmdlets and REST APIs as primary configuration tools, and omitting equivalent Azure CLI (cross-platform) or ARM template examples. There are no Linux-native or cross-platform command examples, and PowerShell is presented as the default automation method.

Recommendations:

Add Azure CLI examples alongside PowerShell for all configuration steps, especially for gateway subnet creation.
Include ARM template snippets or Bicep examples for users who prefer declarative infrastructure-as-code approaches.
Explicitly mention that all operations can be performed from any OS using Azure CLI, not just Windows/PowerShell.
Reorganize technical resources to list Azure CLI and REST API before or alongside PowerShell, emphasizing cross-platform options.
Where PowerShell is referenced, provide a parallel Azure CLI command block to ensure parity for Linux and macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits a subtle Windows bias by consistently listing Azure PowerShell before CLI in supported mechanisms, mentioning PowerShell specifically for migration and classic rules, and omitting explicit Linux or Bash examples or tools. There are no Linux-specific instructions or parity in example commands, and the documentation assumes familiarity with PowerShell, which is more common on Windows.

Recommendations:

Ensure that Azure CLI (which is cross-platform) is listed before or alongside PowerShell in all supported mechanisms and migration instructions.
Provide explicit Bash/Linux shell examples or references where PowerShell is mentioned.
Include notes or links for Linux/macOS users, especially in sections discussing migration or management via command line.
Avoid assuming PowerShell as the default scripting environment; clarify that both PowerShell and CLI are supported equally.
Where possible, add sample commands for both PowerShell and Bash/CLI to demonstrate parity.

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 commands for onboarding to ExpressRoute Direct, with no equivalent Azure CLI (cross-platform) or Bash examples. The instructions and code snippets assume the use of PowerShell, which is traditionally associated with Windows environments, and there is no mention of how to perform these steps on Linux or macOS. This can make the onboarding process less accessible to users on non-Windows platforms.

Recommendations:

Add equivalent Azure CLI (az) command examples alongside PowerShell commands for all onboarding and configuration steps.
Clearly indicate that both PowerShell and CLI can be used, and provide guidance for users on Linux/macOS.
Where possible, provide Bash script examples or note any platform-specific differences.
Reorganize sections so that cross-platform tools (like Azure CLI) are mentioned before or alongside Windows-specific tools.
Include a note or table summarizing which tools/commands are available on which platforms (Windows, Linux, macOS).

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 repeatedly mentioned as a primary or sole automation tool for managing ExpressRoute (e.g., 'PowerShell cmdlet', 'how-to-routefilter-powershell.md'), and REST API/CLI are mentioned but often after PowerShell. There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-native tools or shell environments. Where automation or scripting is referenced, Windows/PowerShell is prioritized or assumed. This may make it less accessible or less clear for Linux users.

Recommendations:

Provide Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
When referencing automation or scripting, mention both PowerShell and Bash/CLI options, and link to relevant documentation for both.
Avoid using 'PowerShell' as the default or only example in links and code samples (e.g., 'how-to-routefilter-powershell.md'); provide or link to equivalent Azure CLI or Bash guides.
Explicitly state that all management operations can be performed from Linux, macOS, and Windows, and provide guidance for each.
Where screenshots or UI instructions are shown, ensure they are not Windows-specific unless necessary, or provide Linux/macOS equivalents if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-centric management APIs, linking to Windows documentation, and providing PowerShell as the only example for ExpressRoute routing configuration. There are no Linux or cross-platform CLI examples, and Windows tools and patterns are mentioned exclusively or before any Linux alternatives.

Recommendations:

Include Azure CLI and/or Bash examples alongside or instead of PowerShell for ExpressRoute configuration tasks.
Reference cross-platform management APIs and documentation, not just Windows-specific ones.
Provide links and examples for Linux-based management and automation tools (e.g., Azure CLI, REST API usage from Bash).
Ensure that documentation for ExpressRoute routing and circuit management covers both Windows and Linux environments equally.
Avoid linking only to Windows documentation (such as previous-versions/windows/mt844538) and instead use platform-neutral or cross-platform Azure docs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing PowerShell-based instructions and references, with no mention of Linux, Bash, or cross-platform CLI alternatives. The only non-portal automation example referenced is PowerShell, and the structure and links present PowerShell before any Linux-friendly options. There are no Linux or Azure CLI examples or references, and no mention of Bash or cross-platform scripting.

Recommendations:

Add Azure CLI (az) instructions and links alongside or before PowerShell examples, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
Ensure that all automation or scripting references include both PowerShell and Azure CLI options.
Rephrase references such as '[PowerShell instructions]' to '[PowerShell or Azure CLI instructions]' and provide corresponding links.
Consider including a section or selector for Linux/macOS users, or clarify that the portal and Azure CLI are fully supported on all platforms.
Audit all referenced articles to ensure Linux parity in examples and instructions.

Create pull request

Bias Types:

⚠️ linux_example_present

⚠️ windows_missing

⚠️ no_os_bias

Summary:

The documentation does not exhibit Windows bias. In fact, the only explicit OS-specific example is for Linux (using dig for DNS queries). There are no PowerShell or Windows command-line examples, nor are Windows tools or patterns mentioned exclusively or preferentially. All Azure CLI examples are cross-platform. No Windows-specific instructions or screenshots are present.

Recommendations:

Maintain parity by continuing to provide cross-platform (Azure CLI) examples.
Optionally, add Windows (e.g., nslookup) and macOS (e.g., dig) equivalents alongside the Linux dig example for DNS troubleshooting to further enhance inclusivity.
Continue to avoid OS-specific bias by not assuming a particular client OS in future documentation updates.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell commands for gateway configuration and explicitly instructing users to use PowerShell for certain steps. There are no CLI or Linux-native command examples, and no mention of cross-platform tools like Azure CLI. This may hinder Linux or macOS users who do not have access to PowerShell or prefer other tooling.

Recommendations:

Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for gateway configuration and management steps.
Mention that PowerShell is available cross-platform, but clarify that Azure CLI is often preferred on Linux/macOS.
Wherever a command-line example is given, present both PowerShell and Azure CLI versions, or link to cross-platform documentation.
Review the documentation for other implicit Windows-first assumptions, such as screenshots or terminology, 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 strong Windows/Powershell bias. The primary example for deploying an ExpressRoute circuit using an ARM template is provided only in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash example. Instructions and workflow steps are written specifically for PowerShell users, and the guidance assumes use of the Azure Cloud Shell in PowerShell mode. While there is a brief mention of Azure CLI and REST API as alternative deployment methods, no concrete CLI or Bash examples are provided. This prioritization of PowerShell and lack of Linux-native or cross-platform command examples may hinder accessibility for Linux and macOS users.

Recommendations:

Add equivalent Azure CLI (az) examples for all PowerShell scripts, especially for deploying and deleting ExpressRoute circuits.
Include Bash shell instructions and examples where appropriate, or clarify that Azure Cloud Shell supports both Bash and PowerShell.
Present CLI and PowerShell examples side-by-side or in tabs, ensuring neither platform is prioritized over the other.
Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
Review and update workflow steps to be platform-neutral, avoiding assumptions about the user's operating system or shell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is heavily biased towards Windows environments, specifically PowerShell. All configuration steps and code samples use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tools. File paths and command syntax are Windows-centric (e.g., C:\NetworkConfig.xml). There are no examples or guidance for users on Linux or macOS platforms, and the installation instructions focus solely on PowerShell modules.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Linux/macOS file path examples (e.g., /home/user/NetworkConfig.xml) alongside Windows paths.
Add a section or callouts for users on Linux/macOS, including installation instructions for Azure CLI and/or PowerShell Core on those platforms.
Where possible, use platform-agnostic language and tools, or clearly indicate when a step is Windows-specific.
Consider reordering or parallelizing instructions so that Linux/macOS methods are presented alongside Windows methods, rather than Windows-first.

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 Azure PowerShell cmdlets, and file paths are Windows-centric (e.g., C:\Users\SampleUser\Downloads). There is only a brief mention of Cloud Shell with a Linux-style path, but no Bash, Azure CLI, or Linux-native examples are provided. Windows tools and conventions are assumed throughout, and Linux alternatives are not discussed.

Recommendations:

Provide equivalent Azure CLI (az) command examples for all operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Linux/macOS file path examples alongside Windows paths, especially when referencing file downloads or script outputs.
Explicitly mention that Azure PowerShell can be used on Linux/macOS, or provide installation instructions for non-Windows users.
Structure sections so that cross-platform or Linux-native approaches (e.g., Azure CLI, Bash) are presented alongside or before Windows/PowerShell examples.
Add notes or links to documentation for using Cloud Shell, Bash, or other cross-platform tools to perform the same tasks.
Where possible, avoid Windows-specific terminology or clarify when a step is platform-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias primarily in the 'Before you begin' section, where Azure PowerShell is required for subscription enrollment and registration, with no equivalent Azure CLI or Linux-native instructions provided. Additionally, file path examples (e.g., for LOA document download) use Windows-style paths without Linux alternatives. The rest of the guide uses Azure CLI, which is cross-platform, but the initial steps and some examples assume a Windows environment.

Recommendations:

Provide Azure CLI commands for subscription enrollment and provider feature registration, or explicitly state if these steps can only be performed via PowerShell.
Include Linux/macOS file path examples (e.g., '~/Downloads/LOA.pdf') alongside Windows paths when specifying output destinations.
If PowerShell is required for certain steps, clarify this limitation and offer guidance for Linux users (e.g., using Azure Cloud Shell or installing PowerShell Core on Linux).
Review all command and output examples to ensure they are platform-agnostic or provide platform-specific variants where necessary.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exclusively uses Azure PowerShell cmdlets and assumes the reader is using PowerShell, which is traditionally a Windows-centric tool. There are no examples or guidance for users on Linux or macOS, such as using Azure CLI, Bash, or cross-platform scripting. All setup and configuration steps are shown with PowerShell, and there is no mention of Linux-native tools or alternative workflows.

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.
Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or PowerShell Core, and provide instructions for installing and using these tools on non-Windows systems.
Include Bash script examples or references for common tasks, especially for secret management and resource creation.
Add a section or callouts for Linux users, highlighting any differences or additional considerations (e.g., authentication, environment setup).
Avoid assuming the use of Windows or PowerShell as the default; present cross-platform options side-by-side or in parallel sections.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exclusively uses Azure PowerShell cmdlets for all configuration steps, with no mention of Azure CLI, Bash, or cross-platform alternatives. All 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. The prerequisites and setup sections also reference Azure PowerShell specifically, reinforcing a Windows-centric approach.

Recommendations:

Provide equivalent Azure CLI (az) command examples for all configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include a section or notes on how to perform these tasks using Bash or in a Linux/macOS environment, clarifying any differences or prerequisites.
Mention that Azure PowerShell can be used on Linux and macOS, but also highlight the availability and parity of Azure CLI.
Reorganize the documentation so that cross-platform tools (like Azure CLI) are presented before or alongside PowerShell, rather than only after or not at all.
Add links to official Azure CLI documentation for ExpressRoute where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Azure PowerShell commands as a prerequisite for ExpressRoute Direct enrollment, without mentioning Azure CLI or Bash alternatives. There are no Linux-specific instructions or parity in tooling examples, and the only command-line tooling mentioned is PowerShell, which is traditionally associated with Windows environments.

Recommendations:

Wherever Azure PowerShell is mentioned, also provide equivalent Azure CLI (az) commands and Bash examples, or at least reference that these alternatives exist.
Explicitly state that both Windows and Linux users can manage ExpressRoute resources, and link to cross-platform tooling documentation.
Add a section or note clarifying that all required steps can be performed from Linux/macOS via Azure CLI, and provide links to relevant guides.
Review all command references and ensure that Linux and cross-platform options are presented equally and not as an afterthought.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively uses PowerShell cmdlets for all configuration, management, and status-checking examples, with no mention or examples of Azure CLI, Bash, or cross-platform tools. There are explicit instructions to download PowerShell cmdlets, and no Linux-native or cross-platform alternatives are provided. This creates a strong Windows/PowerShell bias and limits accessibility for Linux or macOS users.

Recommendations:

Provide equivalent Azure CLI examples for all configuration, management, and status-checking tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include a section or callout at the beginning of the article explaining that all tasks can be performed using Azure CLI, with a link to the relevant CLI documentation.
Where PowerShell-specific instructions are given (such as installing cmdlets), provide parallel instructions for installing and using Azure CLI.
Consider restructuring the article or adding tabs/switchers to allow users to select their preferred tool (PowerShell or Azure CLI), ensuring parity in instructions and examples.
Explicitly mention that PowerShell Core is available cross-platform, if relevant, and provide installation guidance for non-Windows users if PowerShell must be used.

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 Azure PowerShell modules and providing only PowerShell command examples for migration tasks. There is no mention of Azure CLI or Bash equivalents, which are commonly used on Linux and macOS platforms. The guidance assumes the use of Windows tools and patterns, and does not address cross-platform scenarios or provide parity for Linux users.

Recommendations:

Include Azure CLI (az) command examples alongside PowerShell for all migration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that the migration can be performed from any OS using Azure CLI, not just from Windows with PowerShell.
Provide links to Azure CLI installation and usage documentation, similar to the PowerShell references.
Where PowerShell modules are referenced, also reference Azure CLI equivalents and their documentation.
Review all code snippets and ensure that for every PowerShell example, a CLI/Bash example is also provided.
Avoid language that assumes the user is on Windows or using Windows-specific tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only a PowerShell example (Remove-AzResourceGroup) for resource cleanup, with no equivalent CLI or Bash example. Additionally, the firewall policy example specifically references a Windows Update FQDN tag, and there are no Linux-specific scenarios or tools mentioned. This creates a bias toward Windows users and omits guidance for Linux users.

Recommendations:

Add Azure CLI (az group delete) and Bash examples alongside the PowerShell example for resource cleanup.
Include Linux-relevant FQDN tags or application rule examples (e.g., Ubuntu repositories) in the firewall policy.
Ensure that all command-line instructions are provided in both PowerShell and Bash/Azure CLI formats.
Mention cross-platform tools and patterns, not just Windows-specific ones, to ensure parity for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively provides instructions and examples using PowerShell cmdlets for retrieving ARP tables on Azure ExpressRoute circuits. There are no examples or guidance for performing equivalent operations using Azure CLI, Bash, or other cross-platform tools. The prerequisites specifically require the Azure PowerShell module, and all code samples are in PowerShell. There is no mention of Linux or macOS workflows, nor are alternative tools or commands referenced.

Recommendations:

Provide equivalent instructions and examples using Azure CLI (az) commands, which are cross-platform and work on Linux, macOS, and Windows.
Explicitly mention that the steps can be performed from any OS using Azure CLI, and provide installation links for both PowerShell and CLI.
Include Bash or shell script examples where appropriate, especially for common troubleshooting or data retrieval tasks.
Clarify any limitations or differences in output or capabilities between PowerShell and CLI, if applicable.
Add a section or note for Linux/macOS users, outlining the recommended approach for retrieving ARP tables and interacting with ExpressRoute resources.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias throughout. All code examples are in PowerShell, and the workflow is centered around the AzureCT PowerShell module, which is only available for Windows. The instructions for installing and running tools (iPerf, PSPing) are Windows-centric, including references to Windows Firewall and installation paths (e.g., C:\ACTTools). There is no step-by-step guidance or command-line examples for Linux users, and Linux is only mentioned passively as a possible remote host. Even in the test setup and results, only Windows Server is used. The documentation does not provide Linux equivalents for the PowerShell-based workflow, nor does it mention or demonstrate how to perform equivalent tests on Linux systems.

Recommendations:

Provide parallel Linux instructions and examples for each step, including how to install and use iPerf and PSPing (or Linux alternatives) on Linux hosts.
Include bash or shell command examples for Linux users, alongside PowerShell examples.
Document how to perform link performance tests between two Linux hosts, or between Windows and Linux, without requiring the AzureCT PowerShell module.
Clarify which parts of the workflow are Windows-only and offer alternative workflows for Linux environments.
Include sample output from Linux command-line tools to help Linux users interpret their results.
Mention Linux firewall configuration (e.g., ufw, firewalld, iptables) where Windows Firewall is discussed.
In test setup and results, include scenarios using Linux VMs and servers, not just Windows Server.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both cross-platform (ssh command) and Windows-specific (PuTTY) instructions for creating SSH tunnels. However, it gives detailed, step-by-step instructions for PuTTY, a Windows-only tool, and highlights browser limitations specific to Windows (e.g., Edge, Internet Explorer, Chrome's reliance on Windows proxy settings). The PuTTY section is more extensive than the ssh command section, and no Linux GUI alternatives (such as GNOME Terminal, KDE Konsole, or Linux SSH GUI clients) are mentioned. The document also references Windows proxy settings and browser behaviors before discussing cross-platform solutions.

Recommendations:

Add step-by-step instructions for creating SSH tunnels using common Linux GUI SSH clients (e.g., GNOME Terminal, KDE Konsole, or tools like Remmina or OpenSSH GUI frontends).
Balance the detail level between the ssh command section and the PuTTY section, ensuring Linux users have equally detailed guidance.
Explicitly mention that the ssh command works on Linux, macOS, and Windows (via WSL or native OpenSSH), and provide example commands for these platforms.
Include screenshots or walkthroughs for Linux-based SSH tunnel setup using graphical tools, if available.
When discussing browser proxy settings, include Linux-specific instructions (e.g., for Firefox or Chrome on Linux) and note any differences.
Avoid focusing on Windows proxy limitations first; instead, present cross-platform solutions up front, then note any OS-specific caveats.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation references PowerShell and the Azure portal as primary verification and configuration methods, with CLI mentioned only as an afterthought. There are no explicit Linux or cross-platform command-line examples, and the workflow implicitly assumes familiarity with Windows-centric tools and patterns.

Recommendations:

Include explicit Azure CLI examples for all verification and configuration steps, especially for circuit and peering state checks.
When listing tools or methods (e.g., 'Verify provisioning using PowerShell, the Azure portal, or CLI'), mention CLI first or equally, and clarify that Azure CLI is cross-platform.
Add Linux shell (bash) command examples where appropriate, especially for common tasks such as querying circuit status.
Provide links to both PowerShell and Azure CLI documentation for each relevant step.
Review for any other Windows-centric terminology or assumptions and ensure parity for Linux and macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by listing PowerShell migration instructions as the only command-line example in the 'Next steps' section, without mentioning Azure CLI or Bash alternatives. There are no Linux-specific tools, patterns, or examples provided, and PowerShell is referenced before any cross-platform options. This may make the documentation less accessible for Linux or cross-platform users.

Recommendations:

Add Azure CLI (az) examples and links alongside PowerShell instructions for all migration and troubleshooting tasks.
In the 'Next steps' section, include a link to a Linux/Bash/Azure CLI migration guide, or combine PowerShell and Azure CLI instructions in a unified guide.
Ensure that all command-line instructions are presented in both PowerShell and Azure CLI formats, with equal prominence.
Explicitly mention that migration can be performed from Linux, macOS, or Windows environments using Azure CLI.
Review the documentation for any implicit assumptions about the user's operating system and clarify cross-platform compatibility where relevant.

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 steps and subnet management, with no mention of Azure CLI or Bash/Linux alternatives. This focus on PowerShell and omission of cross-platform tools may hinder Linux or macOS users seeking parity in migration guidance.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside PowerShell instructions for all migration and subnet management tasks.
Explicitly mention that PowerShell examples are also available on Linux and macOS, or clarify when features are Windows-only.
Include Bash or shell script snippets where appropriate, especially for validation and monitoring steps.
Ensure that all references to tooling (e.g., 'supported only via PowerShell') are accompanied by notes on CLI support status and roadmap, or links to relevant GitHub issues/feature requests.
Add a section or callout for Linux/macOS users, summarizing supported cross-platform tools and any known limitations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates bias towards Windows environments by referencing Azure PowerShell as a configuration method without mentioning Azure CLI or other cross-platform tools. There are no Linux-specific or cross-platform command examples, and the only tool explicitly mentioned for configuration is Azure PowerShell, which is more commonly associated with Windows environments.

Recommendations:

Include Azure CLI examples alongside or instead of Azure PowerShell for configuration steps, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that configuration can be performed from Linux, macOS, or Windows environments using Azure CLI or portal.
Where PowerShell is referenced, provide equivalent Bash/Azure CLI commands to ensure parity for Linux users.
Review all instructions to ensure that no step assumes a Windows environment or toolset by default.

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 users, while Linux instructions are manual and less automated. Windows tools and workflows (such as PowerShell scripts for firewall configuration) are mentioned first and in more detail, with Linux alternatives being less prominent or requiring manual intervention. There is also a lack of parity in verification steps and troubleshooting guidance for Linux compared to Windows.

Recommendations:

Provide equivalent automation for Linux users, such as shell scripts to open firewall ports and configure agents, similar to the provided PowerShell script for Windows.
Present Linux and Windows instructions in parallel, giving equal prominence and detail to both platforms.
Include verification and troubleshooting steps for Linux agents, not just for Windows (e.g., how to verify agent connectivity on Linux).
Avoid referencing Windows tools (like Control Panel) without Linux equivalents; provide Linux-specific guidance where appropriate.
Where possible, use cross-platform tools or commands, or clearly indicate when a step is platform-specific.
Consider including screenshots or examples for Linux agent installation and configuration, matching the level of detail given for Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively deploying and referencing Windows Server 2019 virtual machines for testing, instructing users to use Remote Desktop and Internet Explorer (both Windows-specific tools), and omitting any mention or example of Linux-based virtual machines or tools for firewall validation. While deployment steps are provided for both Azure CLI and PowerShell, the validation and testing sections assume a Windows environment only.

Recommendations:

Include parallel instructions for deploying and testing with Linux virtual machines, such as Ubuntu or CentOS.
Provide examples of connecting to Linux VMs using SSH, and testing allowed/blocked outbound connections with tools like curl or wget.
Mention and demonstrate browser-based validation steps that are OS-agnostic, or show how to test connectivity from a Linux shell.
Avoid referencing only Windows-specific tools (e.g., Remote Desktop, Internet Explorer) and instead offer cross-platform alternatives.
Explicitly state that the scenario works for both Windows and Linux VMs, and provide guidance for both.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell command examples for all CLI-based troubleshooting steps, without offering Azure CLI (cross-platform) or Bash equivalents. Additionally, the only explicit connectivity test tool recommended is PsPing, which is a Windows-only utility. There are no Linux-native or cross-platform alternatives mentioned for command-line operations or connectivity testing.

Recommendations:

Provide Azure CLI (az) command examples alongside PowerShell for all resource and peering validation steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash or shell script examples for relevant troubleshooting steps, especially for Linux users.
Recommend cross-platform connectivity testing tools (such as hping3, nping, or standard ping/traceroute) in addition to or instead of PsPing, and provide example usage for both Windows and Linux environments.
Explicitly mention that the PowerShell examples are for Windows and provide equivalent instructions for Linux/macOS users.
Where screenshots or portal instructions are given, clarify that the steps are platform-agnostic or note any differences for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses Azure PowerShell for all configuration steps, with no mention of Azure CLI, Bash, or Linux-native tools. All code samples are PowerShell scripts, and the workflow assumes familiarity with PowerShell, which is more common on Windows systems. There are no examples or guidance for users on Linux or macOS platforms.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and commonly used on Linux and macOS.
Explicitly mention that the configuration can be performed from any OS using Azure CLI or Cloud Shell, not just PowerShell.
Add a section or callout for Linux/macOS users, guiding them to use Azure CLI or Bash scripts.
Where possible, use neutral terminology (e.g., 'command line' instead of 'PowerShell') and avoid assuming a Windows environment.
Ensure that all prerequisite and sign-in steps include both PowerShell and CLI alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is heavily focused on PowerShell and Azure Automation runbooks using PowerShell scripts, with no mention of Linux alternatives or Bash/Azure CLI examples. All scripting and automation steps are described using PowerShell, and there is no guidance for users who may prefer or require Linux-based tooling or scripting environments. The documentation assumes familiarity with Azure PowerShell and does not provide parity for Linux users.

Recommendations:

Provide equivalent examples using Azure CLI (az) commands and Bash scripts for automation, especially for collecting ExpressRoute gateway route information.
Mention that Azure Automation supports Python runbooks and provide a sample Python script for the same monitoring task.
Clarify whether the described workflow is possible using Linux-based automation (e.g., using Azure CLI in Automation Accounts or Logic Apps) and provide instructions if so.
Add a section or note for Linux/macOS users, outlining how to perform the same steps without relying on PowerShell.
Where PowerShell modules are referenced, also reference Azure CLI equivalents and provide installation instructions for Linux environments.
Ensure that any prerequisites or 'before you begin' sections mention both PowerShell and CLI options, not just PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing the PowerShell command `Get-AzExpressRouteCircuitStats` for traffic monitoring during failover validation, without providing equivalent CLI or Linux-native commands. No Linux or cross-platform command-line examples (such as Azure CLI or REST API) are given for monitoring or validation tasks, and the only tool mentioned for direct interaction is a Windows-centric one.

Recommendations:

Provide Azure CLI examples (e.g., `az network express-route`) alongside or instead of PowerShell commands for monitoring and validation tasks.
Include REST API or cross-platform scripting options for users on Linux or macOS.
Explicitly mention that monitoring and management can be performed from any OS, and provide sample commands for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI).
Where possible, link to documentation or guides for Linux-based network monitoring and ExpressRoute management.
Avoid assuming the use of Windows tools by default; present cross-platform options first or in parallel.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias by providing only Azure PowerShell examples for deploying the ARM template, referencing PowerShell-specific cmdlets and output, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The instructions and screenshots are tailored to PowerShell users, with no mention or guidance for Linux or macOS users who may prefer or require CLI/Bash. While the text briefly mentions that Azure CLI and REST API are also supported, no examples or step-by-step instructions are given for those methods.

Recommendations:

Provide Azure CLI (az) command examples alongside PowerShell for all deployment and cleanup steps.
Include Bash shell instructions or note that Azure CLI commands work cross-platform (Windows, Linux, macOS).
Add screenshots or output examples from Azure CLI to ensure parity.
Reorder or parallelize instructions so that CLI and PowerShell are presented equally, rather than PowerShell first or exclusively.
Explicitly mention that Cloud Shell supports both Bash and PowerShell, and guide users to choose their preferred shell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by exclusively deploying Windows Server virtual machines for testing, instructing users to use Remote Desktop and Internet Explorer (both Windows-specific), and providing only PowerShell (Remove-AzResourceGroup) for resource cleanup. There are no Linux VM deployment options, no SSH or Linux-based validation steps, and no CLI/Bash examples for resource management.

Recommendations:

Include Linux virtual machine deployment options in the ARM template and documentation steps.
Provide validation instructions for Linux VMs (e.g., using SSH to connect, using curl or a browser to test connectivity).
Offer Azure CLI or Bash examples for resource cleanup alongside PowerShell commands.
Mention both RDP (for Windows) and SSH (for Linux) as connection methods.
Avoid referencing Windows-only tools (like Internet Explorer) as the sole example; suggest cross-platform browsers or command-line tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides detailed instructions exclusively for Azure PowerShell, which is primarily a Windows-centric tool, and does not offer equivalent CLI or Bash examples for Linux users. There is no mention of Azure CLI or cross-platform scripting, and the only command-line instructions are for PowerShell.

Recommendations:

Add equivalent Azure CLI (az) command examples for resetting an ExpressRoute circuit, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash shell examples where appropriate, or clarify that the steps can be performed on any OS using Azure CLI.
Explicitly mention that PowerShell Core is available cross-platform if PowerShell must be used, and provide installation instructions for Linux/macOS.
Ensure that future documentation sections provide parity between Windows (PowerShell) and Linux (CLI/Bash) tooling.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for Azure-side configuration and validation, referencing the Azure portal (which is cross-platform but often Windows-centric in documentation), and omitting Azure CLI (cross-platform) or Linux-native command examples. All device-side configuration examples are for Cisco IOS-XE, with no mention of Linux-based VPN solutions (e.g., strongSwan, libreswan). There are no Linux/Unix command-line examples for validation or configuration, and PowerShell is consistently used for Azure operations.

Recommendations:

Add Azure CLI examples alongside or in place of PowerShell for all Azure-side configuration and validation steps, as Azure CLI is fully cross-platform and widely used on Linux.
Include Linux-based VPN device configuration examples (e.g., strongSwan, libreswan) in addition to Cisco IOS-XE, to support organizations using Linux appliances.
When referencing how to obtain information (such as public IPs or connection status), provide both PowerShell and Azure CLI commands.
Ensure that validation and troubleshooting steps include Linux-native tools (e.g., ipsec status, journalctl, ip route) for parity with Cisco and Windows/PowerShell examples.
Where possible, avoid presenting PowerShell as the default or only automation/scripting option for Azure, and highlight the cross-platform nature of Azure CLI.

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 using Azure PowerShell (Windows-centric) command-line examples and referencing Windows file paths (e.g., C:\CustomRoles\...). There are no examples or instructions for Linux users (e.g., using Azure CLI or Bash), and the documentation does not mention Linux tools or provide cross-platform guidance. The ordering and content assume a Windows environment by default.

Recommendations:

Provide equivalent Azure CLI (az) command examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
Use platform-neutral file paths in examples (e.g., ~/CustomRoles/ or /home/user/CustomRoles/ for Linux/macOS) or explicitly show both Windows and Linux paths.
Add a section or callouts indicating that all steps can be performed on Linux/macOS, and provide any necessary differences or prerequisites.
Reference both PowerShell and Bash (or shell) scripting where automation is discussed, or provide links to relevant cross-platform scripting documentation.
Consider reordering or parallelizing example blocks so that Linux and Windows users see their options side by side, rather than Windows-first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by exclusively using Windows Server images for virtual machines, instructing users to connect via Remote Desktop (RDP), and providing only PowerShell-based test commands. There are no examples or instructions for deploying or testing with Linux VMs, nor are there Linux shell command alternatives for testing firewall rules.

Recommendations:

Include parallel instructions and examples for deploying Linux-based virtual machines (e.g., using Ubuntu images) alongside the Windows examples.
Provide SSH-based connection instructions for Linux VMs, in addition to RDP for Windows.
Offer Linux shell command equivalents (e.g., using dig or curl) for testing DNS resolution and HTTP access, alongside the PowerShell commands.
Explicitly mention that the procedure is cross-platform and clarify any differences in steps or tools between Windows and Linux environments.
Where possible, use neutral language and examples that apply to both Windows and Linux, or present both options side by side.

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 template, referencing only Windows-based admin workflows (e.g., admin username/password for Windows VMs), and providing cleanup instructions solely via a PowerShell command. There are no Linux VM deployment options, nor are there CLI/bash examples for resource cleanup or management.

Recommendations:

Include Linux VM options in the deployment template and documentation steps, or provide a parallel example using Linux distributions (e.g., Ubuntu).
When describing admin credentials, clarify differences for Linux (e.g., SSH key vs. password) and provide relevant instructions.
Add resource cleanup instructions using Azure CLI (az group delete) and bash, not just PowerShell.
Where possible, present both Windows and Linux options side-by-side, or at least mention Linux alternatives.
Avoid assuming the user is working from a Windows environment; provide cross-platform guidance.

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 it demonstrates a Windows bias by including detailed PowerShell instructions (a Windows-centric tool) and referencing Azure PowerShell modules. The PowerShell examples are given equal prominence to CLI, but there are no explicit Linux shell (bash) or cross-platform scripting examples. The documentation also uses terminology and patterns (such as PowerShell object manipulation) that are specific to Windows environments. Additionally, the custom metadata includes 'devx-track-azurepowershell', further indicating a Windows/PowerShell focus.

Recommendations:

Add explicit bash or shell scripting examples for Linux users, especially for tasks currently shown only in PowerShell.
Clarify that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
Where possible, provide bash scripting equivalents for multi-step PowerShell object manipulations (e.g., updating DNS server lists).
Balance the order of examples: sometimes show CLI or bash first, not always PowerShell.
Remove or balance custom metadata tags (such as 'devx-track-azurepowershell') to reflect cross-platform support.
Explicitly state that all configuration steps can be performed from Linux/macOS using Azure CLI, and provide troubleshooting tips for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. PowerShell is mentioned as an option for cluster management, but no equivalent Bash or Linux shell example is provided. The Azure portal (a GUI, often associated with Windows workflows) is referenced first for cluster information, with Azure CLI (cross-platform) following, and PowerShell mentioned next. There are no explicit Linux command-line examples for common troubleshooting tasks (e.g., viewing logs, restarting services), except for the use of curl and netstat, which are standard on Linux. The documentation refers to the Ambari UI, which is Linux-based, but does not provide parity in command-line examples for Linux users. The directory path for script action logs uses backslashes (\), which is a Windows convention, not Linux.

Recommendations:

When mentioning PowerShell, also provide Bash or Linux shell equivalents for all commands.
List cross-platform or Linux-native tools (e.g., Azure CLI, Bash scripts) before or alongside Windows/PowerShell tools.
Use forward slashes (/) for directory paths when referring to Linux-based clusters.
Add explicit Linux/Bash command examples for common troubleshooting tasks (e.g., viewing logs, restarting services, checking cluster health) to ensure Linux users have clear guidance.
Clarify when instructions or tools are specific to Windows or Linux, and provide alternatives where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page mentions PowerShell as a supported method for performing Azure Firewall SKU upgrades/downgrades, but does not mention or provide examples for equivalent Linux/Unix command-line tools (such as Azure CLI). The order of mention (Azure portal, then PowerShell, then Terraform) also places a Windows-centric tool before cross-platform alternatives. No Linux-specific or cross-platform command-line examples are provided.

Recommendations:

Include Azure CLI examples for performing upgrade/downgrade operations, as Azure CLI is cross-platform and widely used on Linux.
Mention Azure CLI alongside PowerShell and Terraform in the list of supported tools, ideally listing the cross-platform option first or at least equally.
Provide sample commands or links to documentation for both PowerShell and Azure CLI to ensure parity for Linux users.
Review other documentation pages for similar patterns and update them to ensure equal representation of Linux-compatible tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell and Windows-centric tools are frequently mentioned as primary or sole scripting/programmatic examples for log management, with Linux/Unix alternatives often omitted or mentioned only in passing. Windows tools (e.g., Visual Studio, Power Query for Excel, System Center) are listed before or instead of cross-platform or Linux-native tools. Linux-specific log management techniques (e.g., logrotate) are only briefly referenced, and there are few concrete Linux shell or scripting examples compared to the detailed PowerShell guidance.

Recommendations:

Provide equivalent Linux shell (bash) or Python scripting examples wherever PowerShell is referenced, especially for log collection, archiving, and Azure Storage access.
List cross-platform or Linux-native tools (e.g., Azure CLI, AzCopy, Linux text processing utilities) before or alongside Windows tools like PowerShell, Visual Studio, and Excel.
Expand on Linux log management techniques (e.g., logrotate, cron jobs, rsyslog) with concrete configuration and usage examples.
Include explicit Linux/Unix command-line examples for common log management tasks, such as downloading logs from Azure Storage, rotating logs, and aggregating logs.
Ensure third-party monitoring/logging tools mentioned include both Windows and Linux options, and clarify platform support where relevant.
Where the Ambari UI or SSH is referenced, provide step-by-step Linux command-line alternatives for accessing and managing logs.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the deployment method in the 'Next steps' section, without mentioning or linking to equivalent Linux/CLI instructions. No Linux or cross-platform command-line examples are provided, and the only deployment guidance is via PowerShell, which is more commonly associated with Windows environments.

Recommendations:

Add links or references to Azure CLI and ARM template deployment guides alongside the PowerShell example.
Include explicit instructions or examples for configuring and deploying the explicit proxy feature using cross-platform tools (e.g., Azure CLI, Bash scripts).
Ensure that all configuration steps (such as uploading PAC files, generating SAS URLs) are described in a platform-agnostic way, or provide both Windows and Linux/macOS workflows.
Where possible, avoid assuming the use of Windows tools or environments; mention cross-platform alternatives early and equally.

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), mentioning PowerShell and CLI support together but not distinguishing or providing parity for Linux/Unix users, and omitting Linux-specific or cross-platform command-line examples. There are no explicit Linux/Unix command examples or tool references, and PowerShell is assumed as the default scripting environment for management tasks.

Recommendations:

For every PowerShell example or reference, provide an equivalent Azure CLI (az) example, which is cross-platform and widely used on Linux and macOS.
When mentioning PowerShell and CLI support, clarify which commands are available in each and provide explicit Linux/Unix usage notes where relevant.
Where a workaround or mitigation references a PowerShell cmdlet (e.g., Set-AzFirewallPolicy), include the equivalent Azure CLI command (e.g., az network firewall policy update) if available.
Avoid assuming PowerShell as the default scripting environment; instead, present both PowerShell and CLI options side by side.
Add a section or note addressing Linux/macOS users, highlighting any differences or limitations in tooling or support.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. It references and provides migration details for several Windows-centric tools (Visual Studio, Visual Studio Code, Azure Data Lake and Stream Analytics Tools for Visual Studio, Az.HDInsight PowerShell) and .NET SDKs. PowerShell is given a dedicated migration section, and the only command-line examples for role assignment use Azure CLI (which is cross-platform, but often associated with Windows in Azure docs). Linux-specific tools, shell examples, or patterns are not mentioned. The order of tools and SDKs generally places Windows/PowerShell/.NET before Linux/Java/Python/Go equivalents.

Recommendations:

Include migration or usage examples for Linux-native environments, such as Bash shell scripts or references to Linux package managers for SDK installation.
Provide parity in documentation for Linux tools (e.g., Azure CLI in Bash, or scripting examples in Bash/zsh, not just PowerShell).
Add explicit mention of Linux and macOS compatibility for all tools and SDKs, especially Azure CLI and VS Code.
Balance the order of presentation: alternate or group Windows and non-Windows tools/SDKs together, or explicitly call out cross-platform support.
If possible, include examples or references for managing HDInsight access from Linux-based automation (e.g., using REST API with curl, Python scripts, or Bash).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily biased towards Windows and PowerShell usage. All deployment and configuration steps are provided exclusively using Azure PowerShell cmdlets, with no mention or examples for Azure CLI, Bicep, ARM templates, or Terraform, which are commonly used on Linux and cross-platform environments. The only command-line example for SFTP connection is generic, but the setup and management instructions assume a Windows/PowerShell environment throughout.

Recommendations:

Provide equivalent Azure CLI examples for all deployment and configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bicep or ARM template snippets for infrastructure-as-code parity.
Add a note at the beginning clarifying that the instructions are PowerShell-specific, and link to cross-platform alternatives.
Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI, and provide links or examples.
Ensure that any references to tools or commands (such as 'command prompt') are platform-neutral or include both Windows and Linux/macOS equivalents.
Consider including a table or section comparing PowerShell and CLI commands for each major step.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first and Windows-heavy bias. Most FQDN tags and examples focus on Windows or Microsoft-specific services (e.g., Windows Update, Windows Diagnostics, Windows 365, Windows Virtual Desktop), with no mention of Linux-specific services or scenarios. There are no examples or guidance for Linux administrators or non-Windows environments.

Recommendations:

Include examples of FQDN tags relevant to Linux-based workloads or popular open-source services (if supported by Azure Firewall).
Add a section or examples addressing how Linux administrators might use FQDN tags, or clarify if the feature is equally applicable to Linux-based environments.
Balance the documentation by mentioning both Windows and non-Windows scenarios where possible, or explicitly state the Windows-centric nature if it is by design.
If Azure Firewall supports FQDN tags for non-Microsoft or cross-platform services, provide examples and documentation for those cases.

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 referencing PowerShell-based deployment and update workflows first and in more detail. While Azure CLI and ARM template options are mentioned, there are no explicit Linux shell (bash) examples or guidance, and the PowerShell workflow is given prominence and more explanation. There is no mention of Linux-native tools or workflows, and the CLI section lacks example commands.

Recommendations:

Add explicit bash/Azure CLI command examples for both deployment and updating scenarios, similar to the PowerShell examples.
Present Azure CLI and ARM template instructions before or alongside PowerShell, rather than after.
Include notes or examples relevant to Linux users, such as using Azure CLI in bash or cloud shell.
Ensure parity in detail and explanation between PowerShell and CLI/ARM template sections.
Where possible, avoid assuming PowerShell as the default automation tool, and clarify that all examples are cross-platform unless otherwise stated.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation presents Azure PowerShell examples before Azure CLI, which is more commonly used on Linux and cross-platform environments. There are no Bash or Linux-specific shell examples, and the PowerShell section is labeled and presented first, suggesting a Windows-centric approach. No mention is made of Linux tools or workflows, and all command-line examples are either PowerShell or Azure CLI, with no explicit Linux context.

Recommendations:

Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
Include explicit Bash/Linux shell examples, especially for users working in Linux environments.
Add a note clarifying that Azure CLI commands can be run on Windows, Linux, and macOS, and provide guidance for Linux users if there are any differences.
Ensure parity in documentation by referencing both Windows and Linux environments where relevant, and avoid assuming PowerShell as the default shell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments by exclusively listing Azure PowerShell cmdlets for managing IP Groups, without providing equivalent Azure CLI (cross-platform) or Bash examples. There are no Linux-specific instructions or examples, and the only command-line tooling referenced is PowerShell, which is traditionally associated with Windows, despite its cross-platform availability. This may disadvantage Linux users or those preferring CLI/Bash workflows.

Recommendations:

Add Azure CLI examples for all IP Group management tasks alongside PowerShell cmdlets.
Explicitly mention that Azure CLI and REST API can be used, and provide links or code snippets.
Include Bash shell examples for common operations, especially for tasks like exporting/importing CSVs.
Balance the 'Related Azure PowerShell cmdlets' section with a 'Related Azure CLI commands' section.
Clarify that PowerShell is available cross-platform, but highlight CLI/Bash parity for Linux 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 Azure PowerShell command examples for managing the Azure Firewall Management NIC, with no mention of Azure CLI (cross-platform) or Bash/shell equivalents. The only automation examples use PowerShell cmdlets, which are primarily associated with Windows environments. There is no guidance or parity for Linux/macOS users, and the documentation implicitly assumes a Windows-centric workflow.

Recommendations:

Add equivalent Azure CLI (az) command examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that both PowerShell and Azure CLI can be used, and provide side-by-side examples where possible.
Include Bash/shell script snippets for common tasks, or at least reference how to perform the same actions from non-Windows environments.
Review the documentation for other Windows-centric terminology or assumptions, and ensure instructions are inclusive of all supported platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell command examples for enabling and disabling diagnostic logs (Top flows and Flow trace), with no equivalent Azure CLI, Bash, or Linux-native instructions. The only command-line tooling referenced is PowerShell, which is most commonly associated with Windows environments, and there is no mention of cross-platform or Linux-first alternatives.

Recommendations:

Provide equivalent Azure CLI (az) command examples for all PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and clarify any platform-specific requirements.
Where possible, include Bash script examples alongside PowerShell, especially for enabling/disabling diagnostic settings.
Reference Azure Portal UI steps as an alternative for users who may not use PowerShell or CLI.
Add a note or table summarizing all available tooling (PowerShell, Azure CLI, REST API, Portal) for each operation, with links to relevant documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation displays a subtle Windows bias. It references Windows-centric tools (Excel, Power BI, Visual Studio, C#) and specifically calls out Azure PowerShell for enabling certain features (e.g., Fat Flow Log), without mentioning or providing parity for Linux or cross-platform alternatives (such as Azure CLI, Linux-compatible log viewers, or editors). There are no explicit Linux or cross-platform command-line examples, and the only tooling guidance for log conversion is for Visual Studio/C# users.

Recommendations:

Provide Azure CLI examples alongside or instead of Azure PowerShell for configuration steps, especially for enabling features like Fat Flow Log.
Mention and provide examples for Linux-compatible tools for viewing and analyzing logs (e.g., jq, csvkit, LibreOffice Calc, or open-source BI tools).
If referencing Visual Studio/C# tools, also mention scripting or conversion options in Python or Bash that are platform-agnostic.
Ensure that any references to downloading and converting logs (e.g., JSON to CSV) include command-line examples that work on Linux/macOS (such as using jq or csvkit).
Explicitly state that all features and steps can be performed from Linux/macOS environments, and provide links or examples where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased towards Windows environments. All certificate management steps rely on Windows-specific tools (certtmpl.msc, Internet Explorer, Windows Certificate Export Wizard), and prerequisites assume Active Directory and Windows CA infrastructure. There are no Linux or cross-platform alternatives or examples provided for certificate creation, request, or export. The workflow is not accessible to administrators using Linux or non-Windows PKI solutions.

Recommendations:

Provide equivalent instructions for Linux environments, such as using OpenSSL for certificate requests and exports.
Include examples for managing certificates with non-Windows CAs (e.g., OpenSSL, EJBCA, or HashiCorp Vault).
Describe how to interact with Azure Key Vault and import certificates using CLI tools available on Linux (e.g., Azure CLI, REST API).
Avoid assuming the use of Internet Explorer or Windows Certificate Export Wizard; offer browser-agnostic or command-line alternatives.
Clarify which steps are Windows-specific and provide cross-platform alternatives wherever possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing a Windows test virtual machine (WorkerVM) for all hands-on steps, such as running curl commands and opening browsers. There are no Linux VM deployment instructions or examples, and the process for installing certificates is only described for Windows. The use of 'administrator command prompt' and browser-based testing is also presented only in a Windows context.

Recommendations:

Provide parallel instructions for deploying and configuring a Linux-based WorkerVM, including certificate installation steps for common distributions (e.g., Ubuntu).
Include Linux-specific command-line examples (e.g., using bash or terminal) alongside Windows examples.
Clarify that curl and browser-based tests can be performed on both Windows and Linux, and provide any necessary Linux-specific guidance (such as installing curl or updating CA certificates).
When describing certificate deployment, include steps for both Windows and Linux VMs.
Use neutral language (e.g., 'open a terminal') instead of 'administrator command prompt' where possible.

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 code examples and automation scripts are provided exclusively in PowerShell, with no mention of Azure CLI, Bash, or Linux-native tooling. The instructions for module installation and validation are PowerShell-specific, and there are no Linux or cross-platform alternatives presented. Even though Azure PowerShell is technically cross-platform, the documentation assumes a Windows/PowerShell environment and does not address Linux users' needs or workflows.

Recommendations:

Provide equivalent Azure CLI (az) commands for all migration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash script examples or at least command-line snippets for Linux users.
Clearly state that Azure PowerShell is available on Linux and macOS, and provide installation instructions for those platforms.
When referencing tooling (such as module installation), include both PowerShell and Azure CLI alternatives.
Where possible, add screenshots or walkthroughs using the Azure Portal, which is platform-agnostic.
Review the order of presentation so that cross-platform methods (Azure CLI, Portal) are mentioned before or alongside PowerShell.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias towards Windows by emphasizing Microsoft-centric BI tools (Power BI, Excel with Power Query, Microsoft Hive ODBC Driver), most of which require Windows. There are no equivalent Linux-based BI tool examples or instructions, and the documentation does not mention or recommend cross-platform alternatives. The development tools section also lists primarily Microsoft and Windows-friendly IDEs before others, and does not highlight Linux-native tools or workflows.

Recommendations:

Include examples and instructions for connecting to HDInsight from Linux-based BI tools (e.g., Tableau on Linux, Apache Superset, DBeaver, or other cross-platform SQL/ODBC clients).
Explicitly mention and provide guidance for using open-source or cross-platform ODBC/JDBC drivers to connect to Hive/Spark from non-Windows environments.
Balance the listing of development tools by including Linux-native editors (e.g., Emacs, Vim, Atom) and clarify that IntelliJ, Eclipse, and VS Code are cross-platform.
Where features or integrations are Windows-only (such as Power Query in Excel), clearly label them as such and suggest Linux alternatives where possible.
Add Linux-specific examples or walkthroughs for common tasks, such as submitting jobs, querying data, or visualizing results, to ensure parity with Windows instructions.

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 Azure Virtual Desktop deployments, referencing Windows-specific service tags, and providing proxy configuration examples only for Microsoft Edge. There are no examples or guidance for Linux-based session hosts or cross-platform scenarios, and Linux tools or patterns are not mentioned.

Recommendations:

Include explicit guidance and examples for Linux-based Azure Virtual Desktop session hosts, such as required FQDNs, endpoints, and firewall rules.
When discussing proxy configuration, provide examples for popular Linux browsers (e.g., Firefox, Chromium) and command-line tools.
Mention and link to documentation about deploying and managing Azure Virtual Desktop on Linux, if available.
Use neutral terminology (e.g., 'session host' instead of 'Windows session host') where possible, and clarify when instructions are Windows-specific.
If certain features are Windows-only, clearly state this and provide alternative recommendations for Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by focusing on RDP access to Windows Server VMs, referencing Azure PowerShell as a primary tool, and omitting Linux-specific examples or scenarios (such as SSH access to Linux VMs). The clean-up instructions use only PowerShell, and there is no mention of Linux tools or workflows.

Recommendations:

Include examples for accessing Linux VMs (e.g., SSH) alongside RDP/Windows examples.
Provide clean-up instructions using Azure CLI, not just PowerShell.
Mention both Azure CLI and PowerShell equally when describing deployment and management steps.
Reference documentation for deploying and accessing both Windows and Linux VMs through the firewall.
Balance the use of Windows and Linux terminology and tools throughout the documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing configuration instructions and examples exclusively for the Azure portal and Azure PowerShell, both of which are Windows-centric tools. There are no equivalent examples or guidance for Linux users, such as Azure CLI or ARM templates. The PowerShell example is given as the only command-line method, and there is no mention of cross-platform alternatives.

Recommendations:

Add Azure CLI examples for all configuration steps to ensure Linux and macOS users have clear, supported instructions.
Mention ARM template or Bicep deployment options for infrastructure-as-code parity.
When listing configuration methods, present cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools (e.g., PowerShell).
Explicitly state that the instructions apply to all platforms, or clarify any platform-specific limitations.
Include screenshots or walkthroughs from non-Windows environments 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 Azure PowerShell examples for configuring Azure Firewall service tags. There are no examples using Azure CLI (which is cross-platform and commonly used on Linux/macOS), nor are there references to Linux-native tools or shell environments. The configuration section leads with and exclusively details PowerShell commands, reinforcing a Windows-centric approach.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell commands shown, ensuring Linux/macOS users can follow along without needing PowerShell.
Explicitly mention that Azure CLI can be used from any platform and provide links to relevant CLI documentation.
Consider including Bash shell examples where appropriate, especially for scripting or automation scenarios.
Reorder the configuration section to present Azure CLI and PowerShell examples side by side, or start with the more cross-platform Azure CLI.
Review and update any references or links that are PowerShell-specific to include CLI alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing detailed Azure PowerShell (Windows-centric) examples before Azure CLI, and by not including any Linux-specific shell or scripting examples (e.g., Bash). The PowerShell examples are more extensive and detailed than the CLI ones. There are no references to Linux tools, shell environments, or considerations for Linux users. The documentation assumes familiarity with PowerShell, which is traditionally a Windows tool, and does not offer parity for Linux-native workflows.

Recommendations:

Provide Bash shell examples alongside Azure CLI commands to demonstrate Linux-native workflows.
Ensure that Azure CLI examples are as detailed and comprehensive as the PowerShell examples, including notes on prerequisites and environment setup for Linux users.
Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any OS-specific considerations if applicable.
Where PowerShell is referenced, clarify that PowerShell Core is cross-platform, or provide alternative scripts for Bash/zsh users.
Add a section or notes addressing Linux users, including any differences in command syntax, environment variables, or deployment steps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides configuration steps using Azure CLI, Azure PowerShell, and the Azure portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric and still most commonly used on Windows) and the absence of Linux-native tools or explicit Linux shell examples (such as Bash scripts) indicate a Windows bias. Additionally, the PowerShell section is given equal prominence to the CLI, and there are no Linux-specific troubleshooting or environment notes. There are no examples or guidance tailored for Linux users beyond the CLI, and no mention of Linux-specific considerations.

Recommendations:

Add explicit Bash shell examples for Azure CLI commands, including any necessary environment setup or differences for Linux users.
Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any Linux-specific notes if applicable (e.g., line continuation differences, authentication nuances).
If PowerShell is included, consider also including Bash or shell script equivalents for parity.
Mention that Azure PowerShell is available cross-platform, but note any differences or prerequisites for Linux users.
Include troubleshooting steps or references for common issues on Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a clear Windows bias. All virtual machine creation examples use Windows Server images, and all configuration and extension installation steps use PowerShell commands. There are no Linux VM examples, no Bash/Azure CLI commands, and no mention of Linux tools or patterns. The only method shown for installing IIS is via a PowerShell script, and the test scenarios exclusively use RDP and Windows-based workflows.

Recommendations:

Add parallel Linux examples for VM creation, such as using Ubuntu or other popular Linux distributions.
Provide Bash/Azure CLI equivalents for all PowerShell commands, especially for VM extension installation and configuration.
Include instructions for installing and testing with Apache or Nginx on Linux VMs, not just IIS on Windows.
Demonstrate SSH access and Linux-native tools for connectivity and firewall testing, in addition to RDP.
Ensure screenshots and walkthroughs are not exclusively Windows-centric; show Linux VM portal configuration where appropriate.
Explicitly mention that the tutorial is applicable to both Windows and Linux environments, and provide guidance for both.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias in several ways: it exclusively uses Windows Server virtual machines for all examples, provides only PowerShell-based automation (no Bash or CLI), and omits any Linux VM or Linux-based configuration steps. The installation of IIS and remote access instructions are all Windows-centric, and there are no parallel instructions or notes for Linux users. The only scripting example is PowerShell, and the Cloud Shell is set to PowerShell by default. No mention is made of deploying or testing with Linux VMs, nor are there examples using Azure CLI/Bash.

Recommendations:

Provide parallel examples for deploying and configuring Linux virtual machines (e.g., Ubuntu) in both the spoke and on-premises subnets.
Include Azure CLI (Bash) commands alongside PowerShell for automation steps, such as installing web servers or configuring resources.
Demonstrate how to install and test with a Linux web server (e.g., Apache or Nginx) as an alternative to IIS.
Add instructions for connecting to Linux VMs (e.g., using SSH) and testing firewall rules with Linux tools (curl, wget, etc.).
Explicitly mention that the steps apply to both Windows and Linux, and highlight any OS-specific differences.
When referencing Cloud Shell, note that both Bash and PowerShell are available, and provide command examples for both.

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 as a primary scripting option alongside Azure CLI and Python, but does not provide explicit Linux or Bash examples, nor does it mention Linux-specific tools or workflows. The ordering of scripting options (CLI, PowerShell, Python) may also suggest a Windows-first perspective, and there is no discussion of Linux shell environments or cross-platform considerations.

Recommendations:

Include explicit Bash or Linux shell script examples for each step, especially for authentication and automation.
Mention that the Azure CLI works cross-platform (Windows, Linux, macOS) and provide guidance for Linux users where appropriate.
Add references or quickstarts for Linux-specific workflows, such as using Bash scripts or integrating with Linux automation tools (e.g., cron, systemd).
Balance the mention of Azure PowerShell with equivalent Linux-native tools or scripting languages.
Clarify that the steps and commands are platform-agnostic unless otherwise noted, and highlight any platform-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page shows a Windows bias by prominently featuring Azure PowerShell and CLI documentation and quickstarts, with PowerShell (a Windows-centric tool) mentioned alongside the CLI and before Linux-native tools or workflows. There is no mention of Linux shell examples or Linux-specific instructions, and the focus on PowerShell and Azure CLI (which is often used in Windows environments) suggests a preference for Windows tooling.

Recommendations:

Add explicit Linux shell (bash) examples for common tasks, such as uploading and analyzing firmware images.
Include quickstart links or sections specifically for Linux users, demonstrating usage in a Linux terminal environment.
When listing tools or commands, present cross-platform options together, or list Linux-native options first when the underlying technology (firmware analysis) is Linux-focused.
Clarify that Azure CLI is cross-platform and provide Linux installation and usage instructions.
Avoid presenting PowerShell as the default or primary automation tool; balance with bash or other Linux-native scripting examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively using Windows batch scripting syntax (set, for /f, %var%) in all variable and workflow examples, with no equivalent Bash/Linux examples provided. Windows command patterns are used throughout, and Linux/macOS users are only briefly mentioned in the context of running Azure CLI in Docker, but not in the main command examples.

Recommendations:

Provide equivalent Bash/Linux command examples for all workflows, especially for variable assignment and loops (e.g., using export, $(...), and while/read loops).
Present both Windows and Linux/macOS command examples side-by-side or in tabs, ensuring parity for all steps.
Avoid using only Windows batch scripting in example workflows; include Bash as a first-class citizen.
Explicitly mention that the provided examples are for Windows, and direct Linux/macOS users to corresponding Bash examples.
Where possible, use cross-platform Azure CLI features that work identically on all OSes, and highlight any OS-specific differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias, particularly in the March 2024 update, where both Azure CLI and PowerShell are mentioned for automation, but no explicit mention or example of Linux shell usage is provided. PowerShell, a Windows-centric tool, is highlighted alongside Azure CLI, but there is no parity in showing Linux command-line workflows or tools. Throughout the document, there are no Linux-specific instructions, examples, or references, and Windows tools are mentioned first or exclusively.

Recommendations:

Include explicit Linux shell (bash) examples for firmware analysis automation, alongside or before PowerShell examples.
Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell/CMD) and Linux (bash/zsh).
Where PowerShell is mentioned, also mention equivalent Linux-native tools or workflows, ensuring equal visibility.
Add screenshots or instructions demonstrating the workflow on Linux systems, not just Windows/Azure Portal.
Review and update documentation to ensure Linux users are equally supported and addressed in all automation and usage scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Azure PowerShell explicitly as a migration method, both in the FAQ and the Next Steps section, without mentioning or providing equivalent examples for Azure CLI (which is cross-platform and commonly used on Linux/macOS). There are no Linux-specific tools or examples, and the ordering of migration instructions puts PowerShell (a Windows-centric tool) on equal or higher footing than more platform-neutral options. No Linux or bash command line examples are provided.

Recommendations:

Add Azure CLI examples and documentation links alongside Azure PowerShell for all migration instructions.
Explicitly mention that both Azure CLI and Azure PowerShell can be used for management and migration, and provide parity in documentation.
Wherever PowerShell is referenced, ensure a corresponding CLI/bash example is present, or at least mention the CLI alternative.
Consider including a table or section comparing management options (Portal, PowerShell, CLI, Terraform) with notes on cross-platform compatibility.
Review for any other Windows-centric language or tool references and ensure Linux/macOS parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for all deployment, validation, and cleanup steps. However, PowerShell (a Windows-centric tool) is always presented as the alternative to CLI, and screenshots explicitly show PowerShell output. There are no Linux shell-specific examples (e.g., bash scripting), and no mention of Linux-native tools or environments. The CLI examples are cross-platform, but the documentation implicitly centers Windows by pairing CLI with PowerShell and by using PowerShell output in visuals.

Recommendations:

Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and consider mentioning bash or zsh as common shells.
Include example terminal output from a Linux shell (e.g., bash) in addition to or instead of PowerShell screenshots.
Clarify that PowerShell Core is cross-platform, but also note that many Linux users will use bash or other shells.
If scripting is discussed, provide bash script snippets alongside PowerShell scripts.
Avoid language or visuals that suggest PowerShell is the default or primary way to interact with Azure, especially for cross-platform documentation.

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 deploying the ARM template, referencing PowerShell-specific cmdlets, and showing PowerShell output screenshots. While it briefly mentions that Azure CLI and REST API are alternative options, it does not provide any Linux-friendly (Bash/Azure CLI) examples or instructions, nor does it mention or show Linux terminal usage. The step-by-step deployment and cleanup instructions are exclusively tailored to Windows/PowerShell users.

Recommendations:

Add equivalent Azure CLI (az) command examples for all deployment and cleanup steps, using Bash syntax.
Include screenshots or output examples from Azure CLI/Bash terminals alongside PowerShell examples.
Present both PowerShell and CLI examples in parallel, or provide a tabbed interface for users to select their preferred environment.
Explicitly mention that the steps work on both Windows and Linux, and provide clear guidance for Linux/macOS users.
Avoid using only PowerShell-specific cmdlets and terminology; ensure parity in instructions and explanations for both Windows and Linux users.

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 the PowerShell example is given equal prominence to the CLI example, despite PowerShell being primarily associated with Windows. There are no explicit Linux shell (bash) or scripting examples, and no mention of Linux-specific tools or patterns. The ordering of examples (CLI first, then PowerShell, then Bicep) is reasonable, but the lack of explicit Linux/bash scripting guidance or examples may disadvantage Linux users.

Recommendations:

Add explicit bash shell scripting examples for Linux users, especially for automation scenarios.
Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide sample invocations in bash/zsh.
Consider de-emphasizing PowerShell unless there are Windows-specific steps, or move PowerShell examples after CLI/bash examples.
Where possible, mention that Bicep and ARM templates are platform-agnostic.
Add a note or section on cross-platform usage, highlighting any differences or considerations for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by presenting SCP and SSH commands in Windows (cmd) syntax first, and in some cases exclusively, while Linux/Unix equivalents are either not shown or are only implied. There is also mention of Windows-specific tools (e.g., Windows Subsystem for Linux, Bash on Windows 10, and Chrome with Foxy Proxy) before or instead of native Linux approaches. The documentation does not provide clear, parallel Linux command-line examples or instructions, which may hinder Linux users.

Recommendations:

For every command-line example, provide both Windows (cmd/PowerShell) and Linux/macOS (bash) syntax side by side.
When referencing tools like SCP or SSH, clarify the command structure for both Windows and Linux environments, including any differences in syntax or prerequisites.
Avoid mentioning Windows-specific tools (e.g., Windows Subsystem for Linux, Bash on Windows 10) as the primary or only method; instead, present native Linux workflows first or equally.
Include explicit instructions for Linux users, such as how to install necessary tools (e.g., OpenSSH client, SCP) and how to use them in a Linux shell.
Where GUI steps are described (e.g., using the Azure portal), clarify if there are differences for Linux users or provide CLI alternatives where possible.
Review all code blocks and ensure that bash commands are not labeled as cmd, and vice versa, to avoid confusion.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. In the prerequisites, Windows tooling (Invoke-WebRequest in PowerShell) is mentioned alongside Linux (wget), but Windows is listed second. However, in the hosts file editing instructions, the Windows path is given before the Linux path, and the instructions are more detailed for Windows. The documentation references Windows-specific tools (PowerShell, Windows hosts file path) and patterns, and provides more explicit guidance for Windows users. There are no Linux-specific command examples beyond mentioning wget and the Linux hosts file path. No Bash or Linux-native command-line examples are provided for other steps.

Recommendations:

When mentioning command-line tools, provide both Windows (PowerShell/CMD) and Linux (Bash) examples side by side, and in equal detail.
List Linux and Windows instructions in parallel, or alternate which comes first to avoid implicit prioritization.
For hosts file editing, provide explicit editing instructions for both Linux and Windows, including example commands (e.g., using sudo nano /etc/hosts for Linux).
Include Linux-native command examples for steps such as DNS lookups (e.g., dig, host, nslookup) and file editing.
When referencing tools, mention cross-platform or Linux alternatives where possible, and avoid assuming the user is on Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several areas: it provides a VM deployment example using only a Windows 10 image, references RDP and Windows licensing, and suggests using a command prompt for SSH access. PowerShell is mentioned before Azure CLI for cluster creation, and there are no explicit Linux or cross-platform examples for VM deployment or SSH testing. The documentation also references Windows-specific tools and patterns (RDP, Windows licensing) without Linux equivalents.

Recommendations:

Provide parallel Linux-based examples for deploying a test VM (e.g., Ubuntu Server) and accessing the cluster using SSH from a Linux terminal.
When referencing VM images, include both Windows and popular Linux distributions, and clarify that either can be used.
Present Azure CLI and PowerShell examples together, or default to Azure CLI for cross-platform parity.
For SSH access instructions, use generic terminal language and avoid assuming a Windows command prompt; mention how to open a terminal on both Windows and Linux.
When discussing remote access, mention both RDP (for Windows) and SSH (for Linux) as options, and clarify port usage for each.
Remove or supplement Windows licensing notes with Linux-specific guidance where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation references Azure PowerShell and CLI for migration but does not provide any explicit Linux or cross-platform examples. The 'Next steps' section specifically links to a PowerShell-based migration guide, and throughout the document, PowerShell is mentioned before CLI, API, and Terraform. There are no Linux shell or Bash examples, nor is there mention of Linux-specific tools or workflows. This may create a perception that Windows/PowerShell is the primary or preferred platform for managing Azure Front Door migrations.

Recommendations:

Provide explicit Bash/Azure CLI examples for migration steps, especially in the 'Next steps' section.
Ensure that CLI commands are given equal prominence to PowerShell, and consider mentioning CLI before PowerShell to avoid 'windows_first' ordering.
Include links to Linux/macOS-compatible migration guides or scripts.
Add a note clarifying that Azure CLI and Terraform are fully cross-platform and suitable for Linux/macOS users.
Where scripts or automation are discussed, provide both PowerShell and Bash/CLI equivalents.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. The PowerShell approach is described in detail and appears before the Azure CLI approach, with extensive use of PowerShell cmdlets and scripts. There are multiple references to PowerShell and Windows-specific tools (such as references to the 'Set up the Azure Monitor agent on Windows client devices' documentation). The CLI approach is provided, but it is positioned after the PowerShell approach, and some instructions (such as using 'azcopy' and 'jq') assume familiarity with Linux tooling but are less detailed than the PowerShell section. There are no explicit Linux shell or Bash examples for direct agent management, and the documentation does not mention Linux-specific considerations, even though HDInsight clusters are often Linux-based.

Recommendations:

Reorder the instructions so that Azure CLI examples appear before or alongside PowerShell examples, reflecting the cross-platform nature of HDInsight clusters.
Add explicit Bash/Linux shell examples for common operations, especially for agent management and DCR association, to better support Linux users.
Avoid referencing Windows-specific documentation (such as 'Set up the Azure Monitor agent on Windows client devices') unless there is a Linux equivalent or a clear note about Linux applicability.
Clarify that both PowerShell and CLI approaches are fully supported on Linux-based HDInsight clusters, and note any differences or prerequisites for Linux environments.
Where possible, provide parity in detail and troubleshooting steps for both PowerShell and CLI/Bash workflows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing and providing examples for Windows-native network troubleshooting tools (tracert, pathping) and omitting Linux/macOS equivalents (such as traceroute, mtr). The instructions and command-line examples for network path analysis are tailored to Windows users, with no parallel guidance for users on Linux or macOS platforms.

Recommendations:

Include Linux/macOS equivalents for all Windows-specific tools mentioned (e.g., mention 'traceroute' and 'mtr' alongside 'tracert' and 'pathping').
Provide example commands for Linux/macOS users wherever Windows command-line examples are given.
When referencing tools, use platform-neutral language (e.g., 'use a network path analysis tool such as tracert (Windows), traceroute (Linux/macOS), or mtr').
Consider providing a table or section summarizing equivalent commands for common platforms.
Ensure that troubleshooting steps are inclusive and actionable for users on all major operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias by listing Azure PowerShell as a primary method for cluster creation and management, and by referencing Windows-centric tools (PowerShell) before or alongside cross-platform or Linux-native alternatives. While Linux-based cluster creation is mentioned, and there are CLI and cURL options, the prominence and explicit mention of Azure PowerShell (a Windows-first tool) and the lack of explicit Linux shell (bash) examples or emphasis on Linux-native workflows suggest a subtle preference for Windows patterns.

Recommendations:

Ensure that Linux-native command-line examples (e.g., bash scripts) are provided and highlighted equally alongside PowerShell.
When listing management options, alternate the order or explicitly state parity between PowerShell and CLI/cURL to avoid implying Windows-first workflows.
Include explicit Linux shell (bash) usage examples where PowerShell is mentioned, especially in quickstart or how-to sections.
Clarify that Azure CLI and cURL are fully cross-platform and may be preferable for Linux users.
Consider adding a section or callout specifically for Linux users, summarizing recommended tools and workflows.

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 PowerShell-based instructions and examples for rebooting HDInsight cluster VMs, without offering equivalent CLI or Bash examples for Linux users. The PowerShell method is presented first and in detail, while no Azure CLI, SSH, or Linux-native tooling is mentioned. This may disadvantage users working from Linux or macOS environments.

Recommendations:

Add equivalent instructions and examples using Azure CLI (az hdinsight) for listing and rebooting nodes, as Azure CLI is cross-platform and widely used on Linux.
Provide Bash or shell script examples for interacting with the REST API (e.g., using curl or httpie) to reboot nodes, including sample request bodies and authentication guidance.
Explicitly mention that PowerShell examples are for Windows users, and provide parallel guidance for Linux/macOS users.
Consider reordering or presenting PowerShell and CLI/Bash examples side-by-side to ensure parity and inclusivity.
Reference relevant Linux tools or commands (such as SSH, if applicable) for troubleshooting or interacting with cluster VMs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation generally provides both Linux and Windows options, but there is a tendency to mention or provide Windows/PowerShell examples before Linux/Azure CLI equivalents. PowerShell is often listed before Azure CLI, and Windows Server DNS configuration is referenced before Linux/BIND in some places. There is also a direct link to Windows Server DNS documentation, while Linux/BIND instructions are more detailed but not always referenced as the primary or only option.

Recommendations:

Present Azure CLI and Linux-based examples before or alongside PowerShell/Windows examples to avoid the appearance of Windows-first bias.
When referencing DNS server configuration, provide equal prominence and links to both Windows Server and Linux/BIND documentation.
Ensure that all steps and examples are available for both Linux and Windows environments, and that neither is presented as the default or primary approach.
In sections where PowerShell is used, always provide an equivalent Azure CLI example immediately adjacent, or vice versa.
Where possible, clarify that both Windows and Linux DNS servers are supported and provide clear, parallel instructions for each.

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 used as the only scripting example for deploying ARM templates and enabling encryption at host, with no equivalent Bash or Linux shell examples. Windows/PowerShell tooling (e.g., Undo-AzKeyVaultKeyRemoval) is mentioned before or instead of Linux/CLI alternatives. There is a lack of Linux-native command-line examples (e.g., Bash scripts) for ARM template deployment and key recovery. The documentation assumes familiarity with Windows tools and workflows, which may disadvantage Linux users.

Recommendations:

Provide Bash or Azure CLI script examples for all operations currently shown only in PowerShell, especially for ARM template deployment and enabling encryption at host.
When referencing tools or commands for key recovery or management, include both PowerShell and Azure CLI (or Bash) equivalents, and list them in parallel or alternate order.
Avoid assuming the user's platform; clarify when steps are platform-agnostic and when they are not.
Add explicit Linux/Bash examples for common workflows, such as deploying ARM templates (e.g., using 'az deployment group create') and managing resources.
Ensure that screenshots and UI walkthroughs are not specific to Windows unless unavoidable, and note any platform-specific differences.

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 the PowerShell client GUID for authentication, and using Windows command prompt syntax (e.g., %HBASE_HOME%\bin) in the HBase section. There are no Linux/bash equivalents for these steps, and the .NET SDK usage is presented in a way that assumes a Windows development environment. Linux-specific instructions, tools, or examples are missing throughout.

Recommendations:

Provide Linux/bash equivalents for all PowerShell commands, such as using dotnet CLI or NuGet CLI for package installation.
Include Linux shell syntax (e.g., $HBASE_HOME/bin) alongside Windows command prompt examples in the HBase section.
Clarify that the .NET SDK can be used cross-platform and provide explicit instructions for Linux/macOS environments (e.g., using VS Code or dotnet CLI on Linux).
Avoid referencing Windows-specific tools or GUIDs (such as the PowerShell client) without mentioning cross-platform alternatives.
Add a section or callouts for Linux users, ensuring parity in setup, authentication, and usage instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Azure PowerShell and Azure Classic CLI as the primary automation/deployment tools, without mentioning Azure CLI (which is cross-platform and more commonly used on Linux). The instructions and examples focus exclusively on the Azure Portal (a GUI), which is more familiar to Windows users, and PowerShell/Classic CLI, with no command-line examples using Bash or Linux-native tools. There are no explicit Linux command-line examples or instructions, and the documentation does not provide parity for Linux users who may prefer scripting or automation via Bash or Azure CLI.

Recommendations:

Add examples and instructions using Azure CLI (az), which is cross-platform and widely used on Linux, for deploying and managing HDInsight applications.
Include Bash shell command examples for common tasks, such as connecting via SSH, listing applications, or deploying templates.
When mentioning automation or scripting options, list Azure CLI before or alongside PowerShell and Classic CLI to avoid Windows-first ordering.
Explicitly state that all features are available and supported on Linux, and provide links to Linux-specific documentation where appropriate.
Provide parity in troubleshooting and next steps sections by referencing Linux-native tools and workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows-related FQDNs (e.g., WindowsUpdate, login.windows.net), describing 'Windows login activity', and referencing Windows-centric services before Linux equivalents. There are no explicit Linux or cross-platform command-line examples (e.g., Bash, CLI), and the only Linux-specific mention is a single rule for Ubuntu updates, which is less emphasized. The documentation lacks parity in examples or guidance for Linux users, especially regarding SSH access, firewall rules for Linux tools, or Linux-specific update sources.

Recommendations:

Provide Linux-focused examples and explanations alongside Windows ones, such as referencing both Windows and Linux update sources and login endpoints.
Include explicit Bash or Azure CLI command-line examples for configuring firewall rules, route tables, and network settings, not just portal-based instructions.
Clarify that HDInsight clusters can run Linux and Windows workloads, and specify any differences in firewall or network configuration for each OS.
Expand the 'Target FQDNs' section to include common Linux package repositories (e.g., for CentOS, Red Hat, or other supported distributions) if applicable.
Add SSH access examples and troubleshooting steps relevant to Linux users, including how to configure firewall and NSG rules for Linux SSH clients.
Ensure that all references to 'Windows login activity' are balanced with explanations of authentication flows for Linux-based clusters.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is presented as the primary scripting example for adding users, with a detailed, multi-step PowerShell script provided before the bash/curl example. Windows tools and patterns (PowerShell, Invoke-WebRequest, Set-ExecutionPolicy) are featured prominently, and the PowerShell example appears before the bash/curl example, suggesting a Windows-first approach. While a bash/curl example is included, it is described as requiring 'slight modifications' for Windows, reinforcing the Windows-centric perspective.

Recommendations:

Present bash/curl (Linux/macOS) and PowerShell (Windows) examples side-by-side or in parallel sections, rather than listing PowerShell first.
Explicitly mention that both Linux and Windows users are supported, and provide equal detail and troubleshooting for both environments.
Avoid Windows-specific terminology (e.g., Set-ExecutionPolicy) unless necessary, or provide equivalent Linux/macOS context.
Where possible, use cross-platform tools (e.g., curl, REST API) as the primary example, and supplement with OS-specific scripts.
Clarify any differences in behavior or requirements between Windows and Linux environments, especially for script execution.

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. It mentions creating PowerShell scripts and scheduling them with Azure Automation as an example for cluster lifecycle automation, without providing equivalent Linux/bash scripting guidance. The only scripting example is PowerShell, and no Linux shell or cross-platform CLI alternatives are mentioned. Additionally, the order of mention puts Windows tools (PowerShell, Azure Automation) before any Linux-native or cross-platform options. There are no explicit Linux examples or references to bash scripting, and the portal UI screenshots do not indicate platform, but the scripting guidance is Windows-centric.

Recommendations:

Provide equivalent Linux/bash scripting examples for cluster provisioning and deletion, alongside PowerShell.
Mention cross-platform tools such as the Azure CLI (az hdinsight ...) for automation, and provide sample commands.
When referencing automation, list both Azure Automation (which can run PowerShell or Python) and Linux-native schedulers (e.g., cron jobs) as options.
Ensure scripting and automation guidance is presented in a platform-neutral or parallel fashion (e.g., 'You can use PowerShell scripts or bash scripts...').
Add explicit Linux examples or links to Linux-focused automation documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only C#/.NET examples, referencing NuGet (a Windows-centric package manager), and linking to PowerShell-based authentication guides. There are no Linux-specific instructions, CLI examples, or cross-platform considerations. The workflow assumes development on Windows and omits parity for Linux users or those using non-Windows tools.

Recommendations:

Add equivalent examples using Azure CLI and Bash scripts for authentication and resource management, which are cross-platform.
Include instructions for setting up and running .NET applications on Linux (e.g., using dotnet CLI, installing dependencies on Ubuntu).
Reference Linux-friendly package managers and development environments (e.g., dotnet CLI instead of only NuGet/Visual Studio).
Provide links to documentation for authenticating service principals using Azure CLI or REST APIs, not just PowerShell.
Explicitly state that the instructions are cross-platform, or provide separate sections for Windows and Linux/Mac users.

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 (e.g., 7z.exe, winutils.exe) and providing only Windows-style paths (e.g., C:\Program Files\, D:\winutils) for configuration settings. There are no Linux or macOS equivalents or examples provided for these settings, and the documentation does not mention how to configure these paths or tools on non-Windows platforms.

Recommendations:

For each configuration property that references a Windows-specific tool or path (such as 7z.exe, winutils.exe, JAVA_HOME, SCALA_HOME, SPARK_HOME), provide equivalent Linux/macOS examples (e.g., /usr/bin/7z, /usr/local/hadoop/bin, /usr/lib/jvm/java-8-openjdk-amd64, /usr/share/scala, /opt/spark).
Explicitly state when a setting is Windows-only, and provide guidance or alternatives for Linux/macOS users.
Add a section or table column for Linux/macOS paths and tool locations where applicable.
Include notes or links to documentation on installing required tools (like 7-Zip, winutils) on Linux/macOS, or clarify if they are not needed on those platforms.
Ensure that screenshots and instructions (such as keyboard shortcuts) are cross-platform, or provide platform-specific variants.

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 automation examples for managing DNS records and cluster configuration, with no equivalent Bash, Azure CLI, or Linux-native scripting examples. References to PowerShell and Az.* modules are prominent, and PowerShell is mentioned before Azure CLI in the 'Create clusters' section. There is no guidance for users who may be working from Linux or macOS environments, and no mention of cross-platform tooling or alternative workflows.

Recommendations:

Provide equivalent Bash or Azure CLI scripts for all PowerShell examples, especially for DNS record management and cluster configuration.
When referencing automation, mention both PowerShell and CLI options together, or present CLI/Bash first to balance the order.
Include explicit notes or sections for Linux/macOS users, clarifying that all operations can be performed cross-platform.
Reference cross-platform tools (e.g., Azure CLI, REST API) wherever possible, and avoid assuming the user is on Windows.
Where PowerShell is used, provide a parallel example using Azure CLI commands and/or Bash scripting.
Audit the documentation for other areas where only Windows-centric tools or patterns are described, and add Linux-friendly alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides a detailed PowerShell script for verifying additional storage accounts but does not offer equivalent Linux/Unix shell (bash) or Azure CLI examples. The verification section leads with PowerShell and omits command-line or scripting guidance for Linux users, despite the cluster being Linux-based. This creates a Windows-first impression and leaves Linux users without parity in operational instructions.

Recommendations:

Add a Linux/bash example for verifying additional storage accounts, such as using curl and jq to query the HDInsight REST API and parse the results.
Include Azure CLI examples for verification, as Azure CLI is cross-platform and commonly used on Linux.
Present PowerShell and Linux/bash examples side-by-side or in parallel sections to ensure equal visibility.
Explicitly mention that the PowerShell example is for Windows users and provide equivalent steps for Linux users.
Review other sections for similar bias and ensure all operational steps have both Windows and Linux guidance where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a moderate Windows bias. The primary script referenced for adding Hive libraries is a PowerShell (.ps1) script, with the Bash script URI only appearing later in a table. The script location section exclusively highlights the PowerShell script, and the instructions for uploading files to Azure Storage recommend Azure Storage Explorer (a Windows-centric GUI tool) before mentioning any command-line or Linux-native alternatives. Additionally, the mention of Azure PowerShell and the .NET SDK as provisioning options precedes any Linux-native tooling.

Recommendations:

Present both PowerShell and Bash script locations equally and prominently, ideally side-by-side.
Include Linux-native tools (such as azcopy, Azure CLI, or sftp) as alternatives for uploading files to Azure Storage, not just Azure Storage Explorer.
When listing provisioning methods, mention Linux-friendly options (such as Azure CLI, ARM templates, or REST API) before or alongside Azure PowerShell and .NET SDK.
Provide explicit Bash/Linux command-line examples for all steps, not just GUI or Windows-centric tools.
Clarify which instructions or scripts are for Windows and which are for Linux, and ensure Linux instructions are not secondary.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a bias toward Windows by exclusively providing Azure PowerShell scripts for resource creation and setup, with no equivalent Bash/CLI or Linux-native instructions. The use of PowerShell is assumed throughout, and there are no references to Azure CLI or Bash scripting, which are more common in Linux environments. This may hinder Linux users or those preferring cross-platform tools.

Recommendations:

Provide equivalent Azure CLI (az) commands and Bash script examples alongside PowerShell scripts for all resource creation and management steps.
Explicitly mention that users can use either PowerShell or Azure CLI, and link to both installation guides.
Where possible, use cross-platform tools and patterns (e.g., Azure CLI, REST API) in examples, or at least present them before or alongside Windows/PowerShell-specific instructions.
Add a section or callout for Linux/macOS users, clarifying any differences or additional steps required.
Review all step-by-step instructions to ensure parity between Windows and Linux environments, especially for scripting and automation tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned before Azure CLI, and Visual Studio (a Windows-centric tool) is highlighted as a primary development environment for deploying templates. The .NET client library example in the 'Next steps' section also links to a Windows-specific page. While Azure CLI is included, Linux-native tools and workflows are not given equal prominence or examples.

Recommendations:

Ensure Azure CLI examples and references are presented before or alongside PowerShell, emphasizing its cross-platform nature.
Include examples or guidance for using Linux-native editors (such as Vim, Emacs, nano) and command-line tools for template editing and deployment.
Highlight cross-platform development environments (e.g., Visual Studio Code) more prominently than Windows-only tools like Visual Studio.
Provide links to .NET client library examples that are not Windows-specific, or include Python/Java SDK examples which are more common on Linux.
Add a section or callout explicitly addressing Linux users, summarizing recommended tools and workflows for template deployment.

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-based instructions and examples for setting up and verifying the Azure Migrate appliance. All command-line examples use Windows tools (e.g., CertUtil), and the installer script is run via PowerShell with Windows-style paths. There are no Linux or cross-platform alternatives or guidance for users deploying the appliance on Linux servers, nor are Linux verification or scripting methods mentioned.

Recommendations:

Provide parallel instructions and examples for Linux environments, including how to verify file hashes using common Linux tools (e.g., sha256sum, md5sum).
Clarify whether the Azure Migrate appliance can be hosted on Linux, and if so, include Linux-specific setup steps and script execution instructions (e.g., bash commands).
If the appliance is Windows-only, state this explicitly early in the documentation to set expectations for Linux users.
When referencing command-line instructions, offer both Windows (PowerShell/CMD) and Linux (bash) equivalents where possible.
Include troubleshooting and log file locations for Linux, if supported.
Review screenshots and UI references to ensure they are not exclusively Windows-centric if the product supports Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by listing PowerShell instructions before Azure CLI, referencing PowerShell-specific cmdlets, and not providing explicit Linux shell or Bash examples. The use of 'PowerShell' as a primary automation tool and the lack of parity in example ordering or depth for Linux users may disadvantage those on non-Windows platforms.

Recommendations:

Present Azure CLI instructions before or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
Include explicit Bash/shell command examples where appropriate, especially for common Linux administration tasks.
Balance the depth and detail of PowerShell and Azure CLI sections to ensure Linux users receive equally comprehensive guidance.
Consider adding a section or callout specifically for Linux/macOS users, highlighting any differences or best practices.
Review linked resources to ensure they also provide Linux-friendly instructions and not just Windows/PowerShell guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias by listing PowerShell as the first utility for scaling clusters, providing PowerShell-specific cmdlets, and referencing Windows-style paths in some command examples. While Azure CLI and SSH/bash commands are included, the ordering and emphasis on PowerShell and Windows tools suggest a preference for Windows environments. There are no missing Linux examples, but the documentation could better balance the presentation of Windows and Linux tools and workflows.

Recommendations:

List Azure CLI before PowerShell in the utilities table, as CLI is cross-platform and more commonly used on Linux/macOS.
Explicitly mention that all CLI and SSH/bash commands work on Linux, macOS, and Windows (with WSL or compatible shells).
Where Windows-style paths (e.g., %HBASE_HOME%\bin) are used, provide equivalent Linux-style paths (e.g., $HBASE_HOME/bin) or clarify that the instructions apply to both environments.
Ensure that all PowerShell examples are paired with equivalent bash/CLI examples where applicable.
Add a note or section highlighting Linux/macOS usage, especially for SSH and command-line operations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page is heavily biased toward Windows and PowerShell usage. All code samples and detailed walkthroughs are provided exclusively in PowerShell, with no equivalent Bash, CLI, or Linux-native scripting examples. The prerequisites and appendix focus solely on Windows tooling (PowerShell, .NET SDK), and the only mention of Linux is a link to a separate page, rather than integrated examples. There is no demonstration of how to perform the same tasks using Azure CLI, Bash scripts, or Linux-native tools.

Recommendations:

Add equivalent examples using Azure CLI and Bash scripts for customizing HDInsight clusters, demonstrating parity with the PowerShell examples.
Include Linux prerequisites (e.g., Azure CLI installation) alongside PowerShell/Az Module instructions.
Present cross-platform options (Azure CLI, REST API, ARM templates) before or alongside Windows-specific tools like PowerShell.
Integrate Linux-focused examples directly into the main documentation, rather than relegating them to separate pages.
Explicitly mention that all approaches are cross-platform where applicable, and clarify any Windows-only limitations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides both Bash (Linux/macOS) and Azure CLI examples for most operations, but when it comes to triggering the Azure Data Factory pipeline, it gives a detailed PowerShell example and only mentions the Azure portal as an alternative. There is no equivalent Bash or Azure CLI example for triggering the pipeline, which may disadvantage Linux users. Additionally, Power BI Desktop (a Windows-only tool) is the only visualization tool mentioned, and its steps are detailed without Linux alternatives. PowerShell is presented before the portal method, reinforcing a Windows-first approach.

Recommendations:

Provide an Azure CLI or Bash example for triggering the Data Factory pipeline, not just PowerShell.
Mention and, if possible, provide steps for using Power BI on the web or suggest open-source, cross-platform alternatives for data visualization.
When listing ways to trigger pipelines, present CLI or cross-platform methods before or alongside PowerShell.
Explicitly state which steps are cross-platform and which are Windows-only, and offer alternatives where possible.
Consider including a table summarizing which tools/steps are available on Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation is generally Linux-focused, as expected for HDInsight on Linux, with Bash and Linux command-line examples (curl, jq, hdfs dfs). However, there are subtle Windows biases: Windows tools (PowerShell, Visual Studio) are mentioned as access methods for Azure Data Lake Storage, and in some lists, Windows-centric tools or SDKs (e.g., .NET, Visual Studio) are mentioned before Linux-native equivalents. PowerShell is listed as a primary method for accessing Data Lake Storage, and there is no explicit mention of Linux alternatives for some tasks (e.g., Data Lake Tools for Visual Studio).

Recommendations:

Where PowerShell or Visual Studio tools are mentioned, also explicitly list equivalent Linux-native tools or workflows (e.g., Bash scripts, Linux SDKs, cross-platform editors).
When listing SDKs or tools, avoid putting Windows-centric tools (PowerShell, Visual Studio, .NET) before Linux-native options unless there is a technical reason; consider alphabetical or platform-neutral ordering.
For every PowerShell example or reference, provide a Linux/Bash/CLI equivalent if possible.
Highlight cross-platform tools (e.g., Azure CLI, Python SDKs) as primary options, and clarify when a tool is Windows-only.
If a tool is only available on Windows (e.g., Data Lake Tools for Visual Studio), note this explicitly and suggest Linux alternatives where possible.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is heavily focused on Linux-based IoT Edge deployments, with detailed step-by-step instructions and examples for Ubuntu/Debian and RHEL. Windows is only mentioned to state that native Windows containers are not supported and to direct users to use Linux containers (EFLOW) on Windows. There are no PowerShell or Windows command-line examples, but also no native Windows instructions or parity. The troubleshooting and update commands are all Linux-centric. The only Windows-specific content is a note about lack of support and a pointer to a separate EFLOW page.

Recommendations:

If Windows support is not available, clarify this at the top of the page and remove the Windows tab to avoid confusion.
If EFLOW (IoT Edge for Linux on Windows) is the only supported scenario, provide a summary of the EFLOW update process or link to the EFLOW update guide more prominently.
If/when Windows-native support is added, ensure that all update, verification, and troubleshooting steps are provided with both Windows (PowerShell/cmd) and Linux (bash) examples.
For parity, consider providing a table or matrix at the top summarizing which OSes are supported and linking to the relevant instructions.
Explicitly state that all commands are for Linux unless otherwise noted, to avoid confusion for Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows-first bias by focusing on migration from Windows-based HDInsight and providing instructions that rely exclusively on Windows tools (Visual Studio, .NET Portability Analyzer as a Visual Studio extension). There are no examples or guidance for performing portability analysis, building, or testing on Linux systems, nor are cross-platform or Linux-native tools mentioned.

Recommendations:

Include instructions for running portability analysis using cross-platform tools or command-line alternatives (e.g., .NET Portability Analyzer CLI, if available).
Provide examples of building and testing .NET applications using Mono or .NET SDK on Linux (e.g., using dotnet CLI or msbuild on Linux).
Mention Linux-native editors or IDEs (such as VS Code or JetBrains Rider) for users who may not have access to Visual Studio on Windows.
Add explicit examples of file path handling and other platform-specific code considerations, with Linux path examples.
Reorder sections or add parallel Linux workflows so that Linux-native approaches are presented alongside or before Windows-specific instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a clear Windows bias. PowerShell is the first and most detailed method shown for all major operations, with full scripts provided. The Azure CLI section uses Windows-style variable syntax (set VAR=VALUE, %VAR%), and explicitly notes that 'the use of variables in this section is based on a Windows environment', without providing a Bash/Linux equivalent. There are no Bash/Linux-native CLI examples, and no mention of Linux tools for scripting or automation. The C# example assumes Visual Studio, a Windows-centric IDE. While the prerequisites mention SSH and Python, the main automation and configuration flows are Windows/PowerShell-centric, and Linux users are left to adapt the examples themselves.

Recommendations:

Provide Azure CLI examples using Bash syntax (export VAR=VALUE, $VAR) alongside or before Windows CMD syntax.
Include Bash shell scripts for automation tasks, especially for cluster creation and storage configuration.
Offer guidance or examples using cross-platform editors/IDEs (e.g., VS Code) instead of only Visual Studio.
Reorder sections to present cross-platform or Linux-native methods (Azure CLI with Bash, Python) before or alongside PowerShell and Windows-specific tools.
Explicitly call out any differences or required adaptations for Linux users, and link to relevant Linux documentation where appropriate.
Where PowerShell is used, note the availability of PowerShell Core on Linux, or provide equivalent Bash commands.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page shows a moderate Windows bias. Windows-specific tools (Azure PowerShell, Cerulea, CloudXplorer, CloudBerry Explorer) are listed, sometimes without Linux equivalents. Azure PowerShell is included as a main utility for uploading data, but no Linux shell or Bash/Azure CLI example is provided in parallel. In tool tables, Windows-only tools are present, and the order of presentation sometimes puts Windows tools before Linux alternatives. There are no explicit Linux command-line examples for uploading data outside of the Hadoop command, and no Bash/Azure CLI walkthrough is shown.

Recommendations:

Add explicit Linux/Bash/Azure CLI examples for uploading data to Azure Storage, not just Hadoop commands.
Provide PowerShell and Bash/Azure CLI examples side-by-side where possible.
Ensure that for every Windows-only tool mentioned, a Linux-compatible alternative is also listed or recommended.
Reorder tool tables and examples so that cross-platform or Linux tools are not presented after Windows-only tools.
Highlight cross-platform utilities (like AzCopy, Azure CLI, Azure Storage Explorer) before Windows-only tools.
Consider adding a section specifically for Linux users, detailing common workflows and tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses PowerShell for all scripting and automation examples, with no mention of alternatives such as Python or Bash. All runbooks are created as PowerShell scripts, and the only tooling referenced is Azure PowerShell modules. There are no examples or guidance for users who may prefer or require Linux-native tools, Bash scripting, or cross-platform automation languages. The structure and language assume PowerShell as the default, which is historically associated with Windows environments, even though Azure Automation supports Python runbooks and HDInsight clusters are often Linux-based.

Recommendations:

Provide equivalent examples using Python runbooks, which are supported in Azure Automation and are cross-platform.
Include Bash/CLI-based automation examples for users who prefer Linux-native scripting.
Mention and link to Azure CLI and REST API alternatives for cluster management, not just PowerShell modules.
Rephrase sections to refer to 'PowerShell or Python' runbooks, rather than only PowerShell.
Add a note clarifying that PowerShell Core is cross-platform, but also highlight other supported scripting languages.
Ensure screenshots and instructions are not exclusively tied to Windows/PowerShell environments.

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 is not fully cross-platform (it uses PowerShell-style variable assignment and arrays), and the PowerShell example is given in full. There are no explicit Linux shell (bash) examples, and the CLI example is not presented in a Linux-friendly format. PowerShell is mentioned and shown in detail, which may bias the documentation towards Windows users.

Recommendations:

Provide a true bash/Linux shell example using Azure CLI, with standard bash variable assignment and array handling.
Clearly separate Azure CLI (cross-platform) and PowerShell (Windows-centric) examples, labeling them as such.
Present the Azure CLI (bash) example before the PowerShell example to avoid Windows-first bias.
Avoid using PowerShell array syntax in CLI examples; use bash-compatible syntax instead.
Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide guidance for each platform if necessary.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias towards Windows by highlighting SQL Server Integration Services (SSIS) and the Azure Feature Pack—both Windows-centric tools—for running Pig jobs, without mentioning equivalent Linux-native options or command-line examples. There are no walkthroughs or examples for running Pig jobs from a Linux shell or using cross-platform tools, and the only integration scenario described is with a Windows-based toolset.

Recommendations:

Add examples for running Pig jobs directly from a Linux shell using SSH, Bash, or cross-platform tools like PuTTY or OpenSSH.
Include walkthroughs for submitting Pig jobs via the Azure CLI, which is cross-platform.
Mention and provide examples for using Linux-native scheduling and orchestration tools (e.g., cron, Airflow) to run Pig jobs.
Balance integration examples by describing both Windows (SSIS) and Linux (shell scripting, CLI) approaches.
Explicitly state that HDInsight clusters are Linux-based by default and provide guidance for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell for custom role creation, without mentioning cross-platform or Linux-native alternatives such as Azure CLI. There are no command-line examples for Linux users, and the only automation tool referenced is PowerShell, which is traditionally associated with Windows environments.

Recommendations:

Provide Azure CLI examples alongside or instead of PowerShell for custom role creation, 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 referenced.
Add Linux/macOS-specific instructions or notes where relevant, especially for command-line operations.
Ensure that any references to tools or scripts are balanced between Windows and Linux environments, or use platform-agnostic tools 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-centric tools and workflows. For example, it instructs users to use Remote Desktop Protocol (RDP) to access a VM, which is primarily a Windows method. There are no examples or instructions for Linux users (e.g., using SSH to access a Linux VM), nor are there any command-line examples that would apply to Linux environments. The documentation assumes the use of the Azure Portal GUI, which is cross-platform, but when it comes to VM access and verification, only Windows methods are mentioned.

Recommendations:

Include parallel instructions for Linux users, such as using SSH to access a Linux VM.
Provide command-line examples (e.g., using curl or wget) to test endpoints from both Windows and Linux environments.
Mention both RDP (for Windows) and SSH (for Linux) as options for accessing VMs.
Clarify that the steps apply to both Windows and Linux VMs, and provide any OS-specific considerations.
Where screenshots or UI steps are shown, note any differences for Linux users if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes the creation and connection to a Windows-based lab VM, with all examples and instructions centered around Windows (e.g., selecting 'Windows 11 Pro' as the VM image, connecting via Remote Desktop). There is no mention of Linux-based lab options, nor are any Linux-specific tools, images, or connection methods (such as SSH) discussed. The documentation assumes the use of Windows tools and workflows throughout.

Recommendations:

Include parallel instructions for creating a Linux-based lab VM, such as selecting an Ubuntu or other Linux image from the Marketplace.
Provide examples for connecting to Linux VMs, including SSH connection steps for Windows, macOS, and Linux clients.
Mention and demonstrate the availability of Linux images and their configuration options within Azure Lab Services.
Clarify in the introduction that both Windows and Linux labs are supported, and provide links or sections for each.
Ensure troubleshooting and cleanup sections also address Linux-specific scenarios.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a subtle Windows bias, primarily through the exclusive mention and linking of a PowerShell script (Set-SynapseEnvironment.ps1) for setting up Synapse environments, with no equivalent Bash or Linux instructions provided. Additionally, tools and workflows such as SSMS (SQL Server Management Studio) and Power BI are referenced, which are traditionally Windows-centric. There are no explicit Linux or cross-platform command-line examples, and the documentation does not mention or prioritize Linux-compatible alternatives or instructions.

Recommendations:

Provide Linux/bash equivalents for all scripts and setup instructions, especially for critical steps like Synapse environment setup.
Explicitly mention and link to cross-platform tools or alternatives where Windows-specific tools (e.g., SSMS, Power BI) are referenced.
Add examples or documentation sections that demonstrate workflows on Linux and macOS, ensuring parity with Windows instructions.
When referencing scripts or tools, indicate their platform compatibility and provide guidance for users on non-Windows systems.
Consider listing cross-platform or Linux-first tools before or alongside Windows tools to avoid implicit prioritization.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation repeatedly references PowerShell and Azure CLI scripts as primary automation methods, often listing PowerShell before Azure CLI. There is no mention of Linux-specific tools or workflows, and PowerShell (a traditionally Windows-centric tool) is emphasized for tasks such as registering applications, granting permissions, and obtaining tokens. While cURL and Python are mentioned for API access, the overall pattern prioritizes Windows-native tools and patterns, with no explicit Linux parity.

Recommendations:

Provide explicit Linux and macOS instructions and examples alongside or before PowerShell, especially for automation tasks.
Highlight Azure CLI as a cross-platform tool and give it equal or greater prominence than PowerShell.
Include bash shell script examples and references to native Linux tools where appropriate.
Clarify that PowerShell Core is cross-platform if recommending it, or otherwise avoid implying PowerShell is the default.
Add screenshots and walkthroughs using Linux environments (e.g., Azure Cloud Shell, Ubuntu terminal) where possible.
Ensure that all code snippets and instructions are validated on both Windows and Linux platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides a workaround for a known issue using only PowerShell commands and the Az PowerShell module, which are Windows-centric tools. There are no equivalent instructions or examples for Linux or cross-platform environments (such as Azure CLI or Bash scripts). This creates a bias toward Windows users and may hinder Linux or macOS users from resolving the issue efficiently.

Recommendations:

Provide equivalent Azure CLI (az) command examples alongside PowerShell commands for all workarounds.
Explicitly mention cross-platform options and note which tools are available on Windows, Linux, and macOS.
Where possible, use Bash or shell-agnostic scripting examples in addition to PowerShell.
Add a note clarifying that the Az PowerShell module can be installed on Linux/macOS, but also recommend Azure CLI as a first-class alternative.
Review all troubleshooting and workaround sections to ensure Linux and macOS users are not excluded.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias primarily in the 'Certificates & secrets' section, where only the PowerShell command 'New-SelfSignedCertificate' is mentioned for creating a self-signed certificate. No equivalent Linux or cross-platform methods (such as using OpenSSL) are provided. The rest of the documentation is largely portal-based and platform-neutral, but the only command-line tool referenced is Windows-specific.

Recommendations:

Provide equivalent Linux/macOS instructions for creating self-signed certificates, such as using OpenSSL (e.g., 'openssl req -x509 ...').
Mention cross-platform tools or methods alongside Windows-specific tools, ensuring parity in all procedural steps.
Where PowerShell or Windows tools are referenced, add a note or section for Linux/macOS users with appropriate commands.
Review other sections for subtle platform assumptions and ensure all examples and tool references are inclusive of major operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes deployment scenarios for Azure IoT Edge for Linux on Windows using Windows-based virtual machines and hypervisors (Hyper-V, VMware with Windows VMs, Azure VMs with Windows). All configuration steps, requirements, and references are tailored to Windows environments, with no mention of Linux-based virtualization hosts, tools, or workflows. There are no examples or instructions for deploying EFLOW on Linux hosts or using Linux-native hypervisors (e.g., KVM, QEMU), and all tooling and troubleshooting guidance is Windows-centric.

Recommendations:

Add equivalent deployment instructions for Linux-based virtualization hosts (e.g., Ubuntu with KVM/QEMU, or other popular Linux distributions).
Provide Linux-native examples for enabling nested virtualization and configuring networking for EFLOW.
Include troubleshooting notes and requirements specific to Linux environments.
Reference Linux tools and commands (e.g., virsh, virt-manager) alongside or before Windows tools where applicable.
Clarify in the introduction whether Linux host support is possible or not, and if not, explain the limitation.

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 server instructions and requirements are consistently presented before Linux equivalents, with more detailed guidance and troubleshooting for Windows (e.g., PowerShell remoting, WMI, WinRM, domain/local accounts). Windows-specific tools and patterns (PowerShell, WinRM, WMI) are emphasized, and setup scripts are referenced as PowerShell scripts. For SQL Server and web app discovery, Windows is prioritized or exclusively supported, with Linux support limited or absent (e.g., SQL Server discovery not supported on Linux). Example scripts and troubleshooting are provided only for Windows authentication, with no equivalent Linux examples for database or web app discovery.

Recommendations:

Present Linux and Windows instructions in parallel, or alternate which OS is described first in each section.
Provide equivalent detail for Linux, including troubleshooting steps and example commands/scripts for common scenarios (e.g., database discovery, permissions).
Where setup scripts are referenced (e.g., PowerShell), offer Bash or cross-platform alternatives for Linux users.
Explicitly call out feature gaps (such as lack of SQL Server discovery on Linux) and provide roadmap or workarounds if possible.
Balance the use of Windows-specific terminology (e.g., domain accounts, WMI, WinRM) with Linux equivalents (e.g., SSH, sudoers, PAM), and provide links to relevant Linux documentation.
For sections where only Windows is supported (e.g., ASP.NET web apps, SQL Server discovery), clearly state this early and suggest alternative approaches for Linux users if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively mentioning Windows-centric identity management tools (Active Directory Domain Services, Microsoft Entra ID) and providing no mention or examples of Linux-native identity management solutions (such as LDAP, FreeIPA, or SSSD). All examples and resources are focused on Windows technologies, with no Linux equivalents or guidance provided.

Recommendations:

Include Linux-native identity management solutions such as LDAP, FreeIPA, or SSSD alongside Active Directory and Entra ID.
Provide example configurations or references for integrating Linux HPC clusters with identity management systems.
Add resources and links to documentation for Linux identity management tools and their integration with Azure or hybrid environments.
Ensure that best practices and tool recommendations are platform-neutral or provide parity between Windows and Linux options.

Create pull request

Bias Types:

⚠️ windows_missing

⚠️ linux_first

⚠️ missing_windows_example

Summary:

The documentation page demonstrates a bias toward Linux environments, particularly Slurm, with all example commands and job submission scripts using Linux shell syntax and Linux-native tools. There are no Windows or PowerShell examples, nor is there mention of Windows-native job schedulers or Windows-specific configuration patterns. The documentation assumes a Linux-based HPC environment throughout.

Recommendations:

Add examples for deploying and configuring job schedulers on Windows-based compute nodes, if supported by CycleCloud.
Include PowerShell equivalents for job submission and scheduler configuration commands.
Mention Windows-native HPC schedulers (such as Microsoft HPC Pack) if relevant, or clarify their support status.
Provide guidance on integrating Windows workloads or mixed-OS clusters if supported by the platform.
Explicitly state OS requirements and compatibility for each scheduler and tool discussed.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias by prioritizing Windows-centric technologies such as Active Directory for identity management and Azure-specific node health checks. While some Linux-relevant tools (e.g., Slurm, spack, easybuild) are mentioned, there is a lack of Linux-specific examples or parity in recommendations, especially for identity and monitoring. The document also references Azure and Bicep (Microsoft-centric), with no equivalent Linux-native or cross-platform alternatives highlighted or explained.

Recommendations:

For identity management, mention and provide examples for Linux-native solutions such as FreeIPA, OpenLDAP, or SSSD, and discuss their integration with cloud environments.
When recommending monitoring and node health checks, include open-source, cross-platform tools (e.g., Nagios, Prometheus, Ganglia) and describe how they can be used in cloud HPC clusters.
Balance references to Azure and Bicep with examples using Terraform, Ansible, or other cross-platform Infrastructure as Code tools, and provide Linux-based quick start setups.
Ensure that for every Windows-centric tool or pattern mentioned (e.g., Active Directory, Azure-specific features), an equivalent Linux or open-source alternative is described, with guidance on usage.
Add explicit Linux command-line or configuration examples alongside any Windows/Azure examples to ensure parity and inclusivity for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Azure-specific tools and services (such as Azure Files, Azure Active Directory, and RBAC) are emphasized, and Windows-centric protocols (SMB, CIFS) and tools (AzCopy, Azure Data Box) are mentioned prominently. While Linux/NFS examples are included, Windows tools and patterns are often mentioned first or exclusively, and there is a lack of parity in providing Linux-native alternatives or examples for some scenarios (e.g., no Linux-native command-line data transfer tools like scp/rsync are discussed in detail). The documentation assumes Azure as the only platform and does not address cross-platform or Linux-first workflows in depth.

Recommendations:

Provide Linux-native command-line examples for data transfer (e.g., using rsync, scp, or sftp) alongside AzCopy.
When mentioning protocols, list NFS (Linux/UNIX) before or alongside SMB/CIFS (Windows), and provide equal detail for both.
Include examples of configuring storage access and permissions using Linux-native identity and access management tools (e.g., POSIX ACLs, LDAP) in addition to Azure AD/RBAC.
Offer guidance for integrating with non-Azure, open-source, or Linux-based storage solutions to support hybrid or multi-cloud scenarios.
Explicitly state when a tool or protocol is cross-platform, and clarify any Windows-specific limitations or requirements.
Balance the order and depth of examples so that Linux and Windows users receive equal attention and actionable guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides detailed instructions and examples for Azure PowerShell and Azure CLI, but the PowerShell section is prominent and detailed, reflecting a Windows-centric approach. There are no Linux-specific instructions, nor are there any Bash or shell script examples. The CLI examples are generic, but the PowerShell module is highlighted, and there is no mention of Linux tools or workflows. The documentation does not address Linux-specific considerations or provide parity for Linux users beyond the CLI.

Recommendations:

Add explicit Bash or shell script examples for Linux users alongside PowerShell examples.
Include a section or notes on using Azure CLI from Linux environments, mentioning any Linux-specific prerequisites or differences.
Balance the order of presentation: do not always present PowerShell before CLI, or alternate the order, or provide a unified example section.
Mention Linux-native tools or workflows where relevant (e.g., using Bash, curl, or jq for automation).
Clarify that Azure CLI is cross-platform and provide links or tips for installing and using it on Linux.
If PowerShell is mentioned, note that PowerShell Core is available cross-platform, and provide installation guidance for Linux if relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing detailed instructions and examples for Windows-centric tools such as PowerShell and the WAImportExport.exe utility, without offering equivalent Linux command-line examples or guidance. The unlock step for exported drives relies exclusively on a Windows executable, and there is no mention of Linux-compatible alternatives or workflows. Additionally, PowerShell examples are given equal or greater prominence compared to Azure CLI, and Windows tools are referenced without Linux parity.

Recommendations:

Provide explicit instructions and examples for unlocking BitLocker-encrypted drives on Linux, such as using dislocker or cryptsetup, including command-line examples.
Mention and document any cross-platform or Linux-native tools that can be used in place of WAImportExport.exe, or clarify platform limitations if none exist.
Ensure that all steps involving command-line utilities (e.g., unlocking drives, reviewing logs) include both Windows and Linux workflows.
Where PowerShell is referenced, ensure Azure CLI (which is cross-platform) is given equal or greater prominence, and clarify when steps are Windows-only.
Add a section or callout summarizing platform support and any known limitations for Linux/Mac users.
If certain steps are only possible on Windows, clearly state this and provide recommended workarounds or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased towards Windows environments. All prerequisites, setup steps, and tooling (BitLocker, NTFS, WAImportExport.exe, manage-bde, PowerShell examples) are Windows-specific. There are no instructions, examples, or tool alternatives for Linux or macOS users, nor is there any mention of cross-platform support or limitations. The documentation assumes the user has access to a Windows system and does not address Linux-based workflows.

Recommendations:

Clearly state at the beginning if the Import/Export tool and process are Windows-only, and provide rationale.
If possible, provide Linux/macOS alternatives or clarify lack of support for non-Windows OSes.
If the WAImportExport tool is Windows-only, suggest workarounds for Linux users (e.g., using a Windows VM, or Azure VM, or third-party tools).
Mention disk preparation and encryption requirements for Linux (e.g., using LUKS or other encryption tools) if supported, or explicitly state that BitLocker/NTFS is required.
Add a section addressing frequently asked questions for Linux/macOS users.
If Azure CLI or REST API steps are cross-platform, clarify which steps require Windows and which can be done from any OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias: all instructions, examples, and tooling are exclusively for Windows. The prerequisite explicitly requires a Windows system, all command-line examples use Windows paths and PowerShell, and the only tool provided (WAImportExport.exe) is a Windows executable. There is no mention of Linux or cross-platform alternatives, nor any guidance for non-Windows users.

Recommendations:

Clarify early in the documentation whether the Azure Import/Export tool is available for Linux or if there are alternative workflows for Linux users.
If a Linux version of the tool exists, provide download and usage instructions, including Linux shell command examples.
If only Windows is supported, explicitly state this limitation and suggest workarounds (e.g., using a Windows VM or container).
Where possible, use platform-neutral language and file paths, or provide both Windows and Linux examples side by side.
Highlight any cross-platform REST API options that could be used from Linux, and provide sample scripts or commands for Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All command-line examples use Windows-style paths (e.g., C:\Users\bob\Pictures), and the only tool referenced is WAImportExport.exe, which is a Windows executable. There are no Linux or cross-platform examples, nor is there any mention of Linux-compatible tools or usage patterns. The documentation refers to 'Windows Azure' and assumes a Windows file system and environment throughout.

Recommendations:

Provide equivalent Linux command-line examples using Linux-style paths (e.g., /home/bob/Pictures).
Clarify whether the WAImportExport tool is available for Linux, or suggest alternative methods for Linux users if not.
Mention any prerequisites or compatibility notes for non-Windows users.
Use neutral terminology such as 'Azure Blob Storage' instead of 'Windows Azure Blob service'.
Include guidance for handling BitLocker-encrypted drives on Linux, or note if this is unsupported.
If the tool is Windows-only, explicitly state this early in the documentation and link to Linux alternatives or workarounds where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-centric tools first or exclusively when discussing enabling soft-delete and key recovery. While the Azure portal is cross-platform, command-line examples and recovery instructions are primarily given for PowerShell, with CLI mentioned secondarily and no explicit Linux shell or cross-platform command examples provided. There are no Linux-specific instructions or parity in troubleshooting steps.

Recommendations:

Provide Azure CLI examples alongside or before PowerShell examples, especially for enabling soft-delete and key recovery.
Include explicit Linux shell (bash) command examples where relevant, ensuring parity for Linux users.
When referencing documentation for enabling features or troubleshooting, link to both PowerShell and CLI (bash) guides equally, or use CLI as the default since it is cross-platform.
Add a section or notes clarifying that all steps can be performed from Linux/macOS using Azure CLI, and provide sample commands.
Avoid referencing Windows tools or patterns (such as PowerShell) exclusively or as the primary method.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation for Azure Import/Export service is heavily Windows-centric. Only Windows operating systems are listed as supported, and all examples (such as checking disk sector size) use PowerShell commands. There is no mention of Linux or macOS support, nor are there equivalent instructions or tools for non-Windows platforms. The requirements and tooling (e.g., BitLocker, .NET Framework, WAImportExport tool) are all specific to Windows environments.

Recommendations:

Explicitly state whether Linux and macOS are supported or not for the WAImportExport tool and the Import/Export process.
If Linux/macOS are not supported, provide a clear rationale and suggest alternatives or workarounds for users on those platforms.
If partial support exists (e.g., for AzCopy or other steps), provide equivalent Linux/macOS instructions and examples.
Include Linux command-line examples (e.g., using lsblk, fdisk, or other tools) for checking disk sector size.
Mention cross-platform tools where possible, and avoid assuming only Windows users will use the service.
If BitLocker is required, clarify if there are alternative encryption options for non-Windows users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exhibits a strong Windows bias by exclusively referencing the WAImportExport tool, which is only available for 64-bit Windows operating systems. There are no Linux or cross-platform alternatives or instructions provided. The documentation does not mention any Linux-compatible tools or workflows, nor does it offer guidance for users on non-Windows platforms.

Recommendations:

Clearly state the lack of Linux support early in the documentation and provide guidance for Linux users (e.g., using a Windows VM or container).
Develop and document a cross-platform or Linux-compatible tool for data preparation and import/export jobs.
If possible, provide PowerShell and Bash (or other Linux shell) command examples side by side.
Mention any workarounds or third-party solutions for Linux users, if available.
Ensure parity in documentation by including Linux-specific instructions, troubleshooting, and requirements.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references the Windows Azure Import/Export Tool (WAImportExport.exe), provides only Windows-style command-line examples (e.g., C:\ paths, .exe extension), and uses Windows-centric terminology (e.g., BitLocker, drive letters). There are no Linux equivalents, examples, or mentions of cross-platform support, which may exclude or confuse users on Linux or macOS systems.

Recommendations:

Explicitly state whether the Azure Import/Export Tool is available for Linux/macOS, and if not, provide guidance or alternatives for non-Windows users.
If a Linux version or cross-platform tool exists, provide equivalent Linux command-line examples (e.g., using /mnt or ~/ paths, and appropriate executable names).
Mention Linux-compatible encryption/decryption tools if BitLocker is referenced (e.g., dislocker or cryptsetup).
Avoid using only Windows drive letters and backslashes in file paths; provide POSIX-style examples as well.
Clarify any platform limitations early in the documentation, so users know if they need to use a Windows environment or VM.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows environments. All prerequisites, setup, and tooling (WAImportExport.exe) are Windows-only. Instructions for preparing drives, running the import tool, and even enabling long paths are specific to Windows. No Linux or macOS equivalents, tools, or examples are provided. The only cross-platform sections are the Azure CLI and PowerShell examples for creating jobs, but the core data preparation workflow is Windows-exclusive.

Recommendations:

Clearly state at the beginning that the Import/Export tool and workflow are only supported on Windows, if that is the case. If Linux/macOS support is planned, provide a roadmap or alternatives.
If partial Linux support exists (e.g., for job creation via CLI), clarify which steps can be done from Linux and which require Windows.
If possible, develop and document a Linux-compatible version of the WAImportExport tool, or provide guidance for Linux users (e.g., using a Windows VM, Docker container, or Azure-hosted VM for the preparation steps).
Add explicit notes or callouts for Linux/macOS users about the lack of support and any available workarounds.
Where possible, provide Linux shell command equivalents for Azure CLI and job management steps, even if the core data preparation remains Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias. It assumes the development machine is Windows, provides only Windows-specific installation commands (e.g., vcpkg bootstrap with .bat, use of Visual Studio, Windows file paths), and references Windows tools and patterns (e.g., Developer Command Prompt, Visual Studio Solution Explorer) without offering equivalent Linux instructions or examples. Linux is mentioned primarily as a target for deployment, not as a development environment. There are no Linux shell commands for setup, no Visual Studio for Linux guidance, and no parity in tool installation or usage instructions.

Recommendations:

Provide explicit instructions for setting up the development environment on Linux, including installation of Visual Studio Code or other supported IDEs, and relevant extensions.
Include Linux shell command examples for all setup steps (e.g., vcpkg installation, Docker installation, Azure CLI installation).
Offer Linux file path examples alongside Windows paths, especially for template and project locations.
Clarify which features and workflows are available or not available on Linux, and offer alternatives where possible.
Add screenshots and walkthroughs for Linux-based development, including debugging and deployment.
Where Windows-only tools are referenced (e.g., Visual Studio 2022), suggest cross-platform alternatives or note the limitations for Linux users.
Rephrase the prerequisites to not assume Windows as the default, or provide parallel Linux sections.
Ensure all CLI commands are shown in both Windows (cmd/PowerShell) and Linux (bash) syntax.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows. All prerequisites, instructions, and examples assume a Windows environment, with explicit requirements for Windows OS, .NET Framework, BitLocker, and the use of Windows drive letters and paths. There are no references to Linux or cross-platform alternatives, nor are there any Linux-specific instructions or examples.

Recommendations:

Clearly state if the tool is Windows-only, or provide information about Linux/macOS support if available.
If cross-platform support exists, add equivalent Linux (and macOS) installation and usage instructions, including command-line examples using Linux paths and conventions.
Mention Linux-compatible alternatives for prerequisites (e.g., disk encryption, file system preparation) if possible.
If the tool is not supported on Linux, suggest alternative workflows for Linux users or clarify the limitations up front.
Ensure that documentation structure and examples do not assume Windows as the default or only environment.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_error_codes

⚠️ windows_terms

Summary:

The documentation page exhibits subtle Windows bias, primarily through the use of Windows-centric error codes (e.g., 'UploadErrorWin32', Win32 error codes like 267 and 123) and terminology. There are no explicit PowerShell or Windows-only command examples, but the error reporting and log samples reference Windows filesystem errors and Win32 error categories, with no mention of Linux equivalents or how errors would appear on non-Windows systems. This may leave Linux users uncertain about how to interpret or troubleshoot similar issues on their platforms.

Recommendations:

Include examples or explanations of how errors manifest on Linux systems, such as typical error codes or messages encountered when using Linux filesystems.
Clarify whether 'UploadErrorWin32' and related error codes are also used for Linux-originated errors, or provide a mapping/reference for Linux error codes if different.
Add a section or note addressing cross-platform considerations, explicitly stating whether the logs and error categories apply equally to Linux and macOS environments.
If possible, provide sample logs or troubleshooting steps for Linux users, or link to relevant Linux documentation.
Avoid using Windows-specific terminology (e.g., 'Win32') without explanation, or supplement with Linux equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias in several areas. The instructions for creating a Standard logic app resource explicitly require a Windows-based App Service plan and state that Linux-based plans are not supported. The storage account error message references a Windows file path (C:\home\data\Functions\secrets\Sentinels). The troubleshooting section instructs users to use the Kudu Advanced Tools and CMD shell, which are Windows-centric tools and terminology, without mentioning Linux alternatives or clarifying cross-platform compatibility. There are no examples or guidance for Linux users, and no mention of Linux command-line equivalents or considerations.

Recommendations:

Clearly state early in the prerequisites and plan selection sections that Standard logic apps currently only support Windows-based App Service plans, and explain any roadmap or alternatives for Linux users.
Where Windows-specific tools or paths are referenced (e.g., Kudu, CMD, Windows file paths), clarify whether these are accessible from Linux/macOS environments via the Azure portal, and provide equivalent instructions or notes for non-Windows users.
If certain features or troubleshooting steps are only available on Windows, explicitly call this out and suggest alternative approaches for Linux users where possible.
Add a section or callout summarizing platform support and limitations, so Linux users can quickly determine applicability.
Where possible, provide cross-platform command-line examples (e.g., using Bash or Azure CLI) alongside or in place of Windows CMD instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by exclusively mentioning Azure PowerShell and the Azure portal as the means to set up peering, without referencing equivalent Linux-native tools or CLI options. There are no examples or instructions for Linux users, such as using Azure CLI (az), and the only automation example is PowerShell, which is primarily associated with Windows environments.

Recommendations:

Include instructions and examples for setting up peering using Azure CLI (az), which is cross-platform and widely used on Linux.
Mention both Azure PowerShell and Azure CLI as supported automation tools, listing them together or in a neutral order.
Provide explicit guidance or links for Linux and macOS users, ensuring parity in setup steps and tooling.
Avoid implying that PowerShell is the only or primary automation method, and clarify that all major platforms are supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by directing users to a PowerShell-based guide for creating or modifying a direct peering, without mentioning or linking to equivalent Linux/CLI instructions. The only explicit tooling reference is to PowerShell cmdlets, and there are no Bash, Azure CLI, or Linux-native examples provided.

Recommendations:

Add parallel instructions or links for performing direct peering setup and management using Azure CLI (az) or REST API, which are cross-platform and commonly used on Linux.
Explicitly mention that PowerShell cmdlets can be run on Linux (if applicable), or clarify platform requirements.
Provide example commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) users in all procedural sections.
Ensure that references to tooling and scripts are balanced and not Windows-centric, to improve accessibility for Linux administrators.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references PowerShell cmdlets for deleting exchange peering, but does not mention equivalent Linux/CLI tools or provide cross-platform examples. There is an implicit assumption that users are operating in a Windows/PowerShell environment, with no guidance for Linux or macOS users.

Recommendations:

Include Azure CLI examples alongside PowerShell cmdlets for all operations, especially for deleting exchange peering.
Explicitly mention cross-platform tools and provide command-line instructions that work on Linux and macOS.
Add a section or note clarifying that all tasks can be performed using Azure CLI or REST API, and link to relevant documentation.
Avoid assuming PowerShell is the default or only supported tool; present both Windows and Linux options equally.

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, referencing PowerShell as the environment to run Azure CLI commands, and omitting equivalent instructions for Linux/macOS users. There are no Linux shell (bash) examples or explicit mention of cross-platform compatibility for the CLI steps.

Recommendations:

Provide Azure CLI command examples in both PowerShell and Bash syntax, or clarify that the commands are cross-platform.
Explicitly mention that Azure CLI can be used on Windows, Linux, and macOS, and provide links to installation instructions for all platforms.
Avoid instructing users to open PowerShell specifically; instead, use neutral language such as 'open your terminal' or 'command prompt or terminal'.
Include notes or callouts for any platform-specific differences in command usage or prerequisites.
Add screenshots or references that reflect both Windows and Linux environments where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by referencing Windows-specific features and tools before or instead of their Linux equivalents. For example, the Windows certificate store is mentioned as a storage location for certificates, but no Linux alternatives (such as OpenSSL, PKCS#11, or Linux certificate stores) are discussed. TPM support is highlighted as being standard on Windows devices, with no mention of Linux TPM support or tooling. There are no concrete examples or guidance for Linux-based manufacturing environments, and no Linux command-line or tool references are provided.

Recommendations:

When mentioning certificate storage, include Linux equivalents such as OpenSSL, PKCS#11 modules, or Linux system certificate stores alongside the Windows certificate store.
When discussing TPM integration, note that Linux has robust TPM 2.0 support (e.g., tpm2-tools, tpm2-tss) and provide links or references to relevant Linux documentation.
Provide example workflows or tool recommendations for both Windows and Linux environments, especially for certificate installation and TPM management.
Avoid phrasing that implies Windows is the default or only supported platform (e.g., 'TPMs are included as standard hardware on many Windows devices') and instead acknowledge cross-platform support.
Add Linux-specific guidance or examples wherever Windows-specific tools or features are mentioned.

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 and Windows-centric tools (WMI, PowerShell, Registry, Windows-specific cmdlets) are consistently presented before Linux equivalents, and in some sections (e.g., web app discovery, storage metadata), only Windows examples or tools are described in detail. Linux coverage is often grouped at the end of sections, sometimes with less detail or with generic command references. There is heavy reliance on Windows-native tools and patterns, with Linux alternatives sometimes missing or less thoroughly explained.

Recommendations:

Reorganize sections to present Windows and Linux information in parallel (side-by-side tables or subsections), rather than always listing Windows first.
Where PowerShell or Windows-specific tools are referenced, provide equivalent Linux commands or scripts with equal detail.
For sections like ASP.NET, Java, and Spring Boot web app data, clarify if Linux is supported and, if so, provide Linux-specific collection details or explicitly state limitations.
In the storage metadata section, add equivalent Linux storage metadata collection commands (e.g., using lsblk, df, lsscsi, etc.) and describe how NFS, SMB, and iSCSI are discovered on Linux.
Ensure that all examples, especially for dependency data and software inventory, include both Windows and Linux command references with similar depth.
Review the order of presentation throughout the document to avoid reinforcing a Windows-centric perspective.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias throughout. Windows-specific tools (Visual Studio, PowerShell) are mentioned before or instead of Linux equivalents, and setup instructions often assume a Windows environment. While some Linux alternatives are referenced, they are often secondary or require following external links. Several code and command examples default to Windows command prompts or tools, with Linux instructions either missing, less detailed, or presented after Windows instructions.

Recommendations:

Present Linux and Windows instructions in parallel, giving equal prominence to both platforms.
For each prerequisite or setup step, provide explicit Linux (and macOS, if relevant) instructions alongside Windows instructions, rather than referring users to external documentation.
When mentioning tools like Visual Studio, also mention common Linux IDEs or build systems (e.g., GCC, Clang, VS Code) and provide equivalent setup steps.
For command-line examples, show both Windows (cmd/PowerShell) and Linux (bash) commands side by side, using tabbed or clearly separated sections.
Avoid language that frames Windows as the default or primary environment (e.g., 'This tutorial is oriented toward a Windows-based workstation'), or balance it with an explicit statement of Linux parity.
Ensure all code samples and build/run instructions are fully documented for both Windows and Linux, including environment variable setup, build commands, and troubleshooting tips.
Where possible, use cross-platform tools (e.g., Azure CLI, Git Bash, VS Code) and highlight their use to minimize OS-specific dependencies.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page references both Azure CLI and PowerShell when discussing connectivity issues and firewall rules, but does not mention or provide examples for Linux-native tools or workflows. PowerShell is called out alongside Azure CLI, which can be used on both Windows and Linux, but the explicit mention of PowerShell (a Windows-first tool) without mentioning Bash or other Linux shells suggests a Windows-centric bias. There are no Linux-specific examples or references to Linux firewall tools (e.g., iptables, ufw), and the guidance assumes familiarity with Windows tools and patterns.

Recommendations:

Include explicit references to Linux-native tools and workflows (e.g., Bash, iptables, ufw) alongside PowerShell and Azure CLI.
When mentioning PowerShell, also mention Bash or other common Linux shells to ensure parity.
Provide example commands for both Windows (PowerShell) and Linux (Bash) environments when discussing firewall configuration or automation.
Clarify that Azure CLI is cross-platform and provide usage examples in both Windows and Linux contexts.
Avoid listing PowerShell before Linux alternatives unless there is a clear reason to do so.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a clear Windows bias. It assumes a Windows development environment by default, provides detailed instructions and tooling references (e.g., Visual Studio, .exe simulators, Windows-specific command prompts) primarily for Windows, and often omits or relegates Linux/macOS instructions to external links. Many code/build/run steps reference Windows tools or paths, and Linux equivalents are not provided inline or are only referenced indirectly.

Recommendations:

Provide explicit, inline instructions for Linux and macOS environments alongside Windows steps, not just as external links.
Include Linux/macOS equivalents for all Windows-specific tools (e.g., Visual Studio alternatives, .exe simulator alternatives, command-line instructions using bash/zsh).
When referencing command prompts, include bash/zsh examples and clarify which commands are cross-platform.
Ensure that all code samples and build instructions are tested and documented for Linux/macOS, including any required dependencies or environment setup.
Avoid assuming the use of Windows-only features or tools (e.g., .exe files, Visual Studio) without providing alternatives.
Where possible, use platform-agnostic language and tooling, or clearly indicate platform-specific requirements in each section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a clear Windows bias. It repeatedly refers to 'your Windows machine' and assumes a Windows development environment by default. Instructions and examples prioritize Windows tools (Visual Studio, CMD, Git Bash, etc.), and environment setup steps are Windows-centric. Linux and macOS are only mentioned as alternatives, often with links out to other documentation rather than inline parity. Command-line instructions use Windows syntax (cmd, set) and do not provide Linux equivalents (bash, export, etc.). Visual Studio is emphasized for C/C++ development, with only a brief mention of Linux/macOS alternatives. There are no explicit Linux/macOS command examples or screenshots, and the initial framing and prerequisites are Windows-first.

Recommendations:

Provide parallel Linux/macOS instructions and examples alongside Windows ones, including shell commands (e.g., use both 'set' and 'export' for environment variables).
Include explicit instructions for installing prerequisites (e.g., compilers, SDKs) on Linux/macOS, not just links to external setup guides.
Offer build and run instructions for Linux/macOS environments (e.g., using gcc/clang, make, or cmake with Unix Makefiles, and running from bash/zsh).
Add Linux/macOS screenshots where appropriate, or clarify when steps are identical across platforms.
Avoid language that assumes Windows as the default (e.g., 'on your Windows machine'); instead, use neutral phrasing or mention all supported OSes.
For Visual Studio-specific steps, provide equivalent instructions for common Linux IDEs (e.g., VS Code, CLion) or command-line workflows.
Ensure all code snippets and commands are cross-platform, or provide platform-specific tabs/pivots.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation repeatedly assumes or prioritizes Windows as the development environment, particularly in the .NET and Java sections. Instructions such as 'Open a Windows command prompt' are given, and there are no explicit Linux or cross-platform command-line instructions, even though the SDKs and tools are available for Linux. There is a lack of Linux-specific guidance or parity in setup and execution steps, and Windows terminology is used by default.

Recommendations:

Provide explicit Linux (and macOS) instructions alongside Windows for all command-line steps, including terminal commands and environment setup.
Replace phrases like 'Open a Windows command prompt' with 'Open a terminal window' or provide both Windows and Linux/macOS alternatives.
Where commands differ (e.g., path separators, shell syntax), show both Windows (cmd) and Linux/macOS (bash/sh) examples.
Clarify that the SDKs and samples work cross-platform, and ensure that all prerequisites and steps are validated on Linux.
For Java and .NET, include Linux-specific notes for installing dependencies and running samples, such as using apt, yum, or Homebrew.
Avoid assuming the user is on Windows unless the SDK or tool is truly Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by consistently referencing Windows environments first or exclusively, especially in prerequisites and sample instructions. Several steps explicitly instruct users to use a Windows command prompt, and some certificate creation links and instructions default to Windows-specific tabs or tools. There are missing or unclear instructions for Linux users, particularly regarding command-line environments and tool usage. While some sections mention Linux compatibility, practical Linux-specific guidance is lacking.

Recommendations:

For all command-line instructions (e.g., creating projects, running samples), provide both Windows (cmd/PowerShell) and Linux/macOS (bash/sh) equivalents, or clarify when commands are cross-platform.
In prerequisites, avoid specifying 'Windows-based machine' unless truly required. Instead, list requirements for both Windows and Linux/macOS, and clarify when steps differ.
When linking to certificate creation tutorials, ensure that both Windows and Linux tabs are referenced or provide a neutral link, not just the Windows tab.
In sample creation steps, avoid phrases like 'Open a Windows command prompt.' Instead, use 'Open a terminal window' and specify differences if necessary.
For Java and Node.js sections, clarify that the samples can be run on Linux/macOS as well, and provide any necessary adjustments (e.g., path syntax, shell commands).
Where Git Bash or similar tools are referenced, explain their relevance for both Windows and Linux users, and suggest native alternatives for Linux.
Add explicit Linux/macOS examples for certificate manipulation (e.g., using openssl, sed, etc.), and clarify any OS-specific nuances.
Review all screenshots and UI instructions to ensure they are not Windows-specific, or provide Linux/macOS equivalents where the Azure portal UI differs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias, especially in the ordering and emphasis of solutions. Windows-based services (Azure Virtual Desktop, Windows 365 Cloud PC, Microsoft Dev Box) are described in detail and listed before Linux-supporting options. There is a strong focus on Windows desktop experiences, Windows-specific management tools (Intune, Entra ID), and Windows VM scenarios. While Azure DevTest Labs and some partner solutions mention Linux support, there are no Linux-specific examples, workflows, or feature highlights. Linux use cases are only referenced in passing, and there are no explicit instructions or guidance for Linux-based labs.

Recommendations:

Explicitly mention Linux support and scenarios in the main Microsoft solution sections, not just in partner solution summaries.
Provide Linux-specific examples and workflows, such as setting up a Linux-based lab or using Linux images in Azure DevTest Labs.
Balance the order of presentation: introduce cross-platform or Linux-supporting solutions before or alongside Windows-centric ones.
Highlight Linux management and access tools (e.g., SSH, Azure CLI) where relevant, not just Windows tools like Intune or Entra ID.
Include a comparison table or matrix showing Windows and Linux feature parity across all recommended solutions.
Add links to Linux-focused documentation or guides for transitioning Linux-based labs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by prioritizing Windows-specific tools (Visual Studio), providing detailed instructions for Windows environments first, and only referencing Linux or macOS alternatives via external links. PowerShell and Windows command prompt examples are given alongside Bash, but the development environment setup and simulation steps are heavily oriented toward Windows/Visual Studio, with Linux instructions deferred or omitted.

Recommendations:

Provide step-by-step instructions for setting up the development environment and building/running the Azure IoT C SDK on Linux (e.g., using gcc, make, cmake, and VS Code or other editors).
Include Linux/macOS command-line examples (e.g., bash, sh) alongside Windows/PowerShell/cmd examples throughout the tutorial, not just for environment variable setup.
Offer explicit guidance for running and debugging the simulated device sample on Linux, including how to build and execute the sample without Visual Studio.
Reference Linux prerequisites (e.g., gcc, make, cmake, git) directly in the prerequisites section, not only via external links.
Where UI steps are described (e.g., Azure Portal), note any differences for Linux users if applicable, or confirm parity.
Ensure that all critical steps (such as building, running, and troubleshooting the sample) are fully documented for both Windows and Linux users within the main tutorial, not just in linked resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a strong Windows bias: instructions and examples are consistently presented for Windows first, often exclusively referencing Windows tools (e.g., Visual Studio, Windows command prompt, Git Bash on Windows). Linux and macOS users are repeatedly referred out to SDK documentation or alternate tutorials, and step-by-step parity is lacking. Even when Linux commands are shown, they are secondary to Windows, and the overall workflow assumes a Windows-centric development environment.

Recommendations:

Provide full, step-by-step instructions for Linux (and macOS) alongside Windows in each section, not just links to external SDK setup guides.
Present Linux and Windows instructions in parallel (e.g., using tabs or clear subsections), ensuring equal prominence and completeness.
Include Linux-native toolchain examples (e.g., gcc, make, standard Bash) rather than focusing on Visual Studio and Windows command prompt.
Avoid assuming the use of Git Bash on Windows as a substitute for a real Linux shell; provide native Linux shell instructions.
Ensure all code samples, environment variable setups, and build/run instructions are fully documented for Linux, not just Windows.
Where Windows-specific tools are mentioned (e.g., Visual Studio), provide Linux equivalents (e.g., VS Code, CLion, or command-line tools) with equal detail.
Consider adding a Linux/macOS quickstart page or a unified cross-platform quickstart with clear pivots for each OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias throughout. Prerequisites, environment setup, and all code execution instructions are presented for Windows first, with explicit references to Windows tools (Visual Studio, Windows command prompt, certmgr.msc, .NET SDK for Windows, etc.). Linux and macOS users are repeatedly directed to external SDK documentation rather than being provided with in-page, step-by-step instructions or examples. All shell commands for device provisioning, SDK setup, and certificate management are shown using Windows command prompt or Git Bash on Windows, with only brief notes about differences for Linux (e.g., subject name slashes in OpenSSL). There are no full Linux-native or macOS-native walkthroughs, and Windows-specific tools and patterns (e.g., certificate store, Visual Studio solution files) are assumed as defaults.

Recommendations:

For each programming language section, provide in-page, step-by-step instructions for Linux and macOS environments, not just links to SDK docs.
Include Linux/macOS command-line examples (bash, zsh, etc.) for cloning, building, and running SDKs, alongside Windows examples.
When referencing tools like Visual Studio, also mention and give instructions for common Linux/macOS IDEs or build systems (e.g., gcc, clang, make, cmake, VS Code).
For certificate management, provide Linux-native instructions (e.g., using update-ca-certificates, trust, or manual copying to /etc/ssl/certs) alongside Windows certmgr.msc steps.
Ensure all OpenSSL commands and file path examples are shown in both Windows and Linux/macOS formats.
Avoid assuming the use of Windows command prompt or Git Bash; clarify which shell is being used and provide alternatives.
Where environment variables are set, show both Windows (set VAR=val) and Linux/macOS (export VAR=val) syntax.
Summarize any platform-specific differences in a dedicated section or table for quick reference.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows is frequently mentioned first when listing supported platforms and development environments. There are references to Windows-specific tools and patterns, such as IoT Edge for Linux on Windows (EFLOW), and examples include PowerShell output. Some instructions and examples are tailored to Windows users, and Linux-specific guidance is sometimes less prominent or missing. While Linux is supported and mentioned, parity in examples and tool usage could be improved.

Recommendations:

Ensure all code snippets and command outputs are shown for both Windows (PowerShell/CMD) and Linux/macOS (bash) where relevant, especially for commands like 'docker ps' and file paths.
When listing supported platforms or development environments, alternate the order or explicitly state that all platforms are equally supported.
Provide Linux/macOS-specific troubleshooting tips and notes alongside Windows-specific ones, especially for Docker Desktop and remote debugging.
Avoid using Windows-specific screenshots or outputs exclusively; include Linux/macOS equivalents.
Where Windows-only tools or patterns are mentioned (e.g., EFLOW), provide equivalent Linux-native workflows or clearly state their scope.
Add explicit Linux/macOS setup and usage instructions for all major steps, including Docker, SSH, and Visual Studio Code extensions.
Review all sections for implicit assumptions of Windows usage (e.g., file paths, environment variables) and provide cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments, with all setup, configuration, and deployment instructions using Windows tools (PowerShell, Device Manager, winver). There are no Linux-native examples or instructions, and the only Linux context is within a Windows-hosted VM (EFLOW). The documentation assumes Windows as the host and does not provide parity for users who might want to run similar workloads on native Linux systems or need Linux-based setup/configuration steps.

Recommendations:

Add equivalent Linux-native instructions or clarify that EFLOW is only supported on Windows hosts, and provide references for native Linux GPU acceleration with Azure IoT Edge.
Include Linux shell (bash) command examples for tasks such as checking GPU availability, driver installation, and deployment, even if only for the guest VM.
Mention Linux tools (e.g., lspci, nvidia-smi, glxinfo) alongside Windows tools like Device Manager and winver.
If EFLOW is strictly a Windows-hosted solution, explicitly state this at the beginning and provide links to Linux-native Azure IoT Edge GPU acceleration documentation for users on Linux.
Ensure that any references to driver installation or system requirements include both Windows and Linux perspectives where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. All setup, configuration, and file transfer steps are described using Windows tools (PowerShell, Visual Studio, Windows file paths, and cmdlets like Copy-EflowVmFile). There are no equivalent Linux-based instructions or examples for users who may be running the host or development environment on Linux. The documentation assumes Visual Studio and NuGet usage on Windows, and all initial steps are Windows-centric, with Linux commands only appearing after the executable is copied to the EFLOW VM.

Recommendations:

Provide equivalent instructions for users developing on Linux hosts, including how to build and publish the .NET executable using the dotnet CLI.
Offer Linux shell (bash) commands for file packaging (tar) and transfer (e.g., using scp or rsync) to the EFLOW VM, not just PowerShell and Windows cmdlets.
Include instructions for initializing the TPM NV index from a Linux environment, if possible, or clarify if this is only possible from Windows.
Present both Windows and Linux command examples side by side where appropriate, or clearly label which steps are Windows-only.
Mention and link to cross-platform tools (such as VS Code, dotnet CLI) as alternatives to Visual Studio and NuGet Package Manager GUI.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-specific tools and workflows (such as RDP and OneDrive), mentioning Windows scenarios and features before Linux equivalents, and lacking detailed Linux-specific setup or examples. Linux is mentioned as an option, but without the same level of guidance or tool integration as Windows.

Recommendations:

Provide parallel, detailed instructions for Linux VM setup, including recommended SSH clients and RDP/GUI installation steps.
Include examples and guidance for configuring Linux VMs with external storage solutions (e.g., mounting NFS, using Dropbox or other cross-platform tools) alongside OneDrive.
Offer cost-control and auto-shutdown instructions specific to Linux VMs, clarifying any differences in behavior or setup.
Ensure that all references to client tools (such as Remote Desktop clients) include Linux-compatible options and are not Windows-centric.
Where Windows-specific features (like OneDrive or Office setup) are highlighted, provide equivalent Linux alternatives or note their absence.
Add Linux-focused troubleshooting and best practices sections to match the depth provided for Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. In the X.509 self-signed authentication section, the Windows (PowerShell) openssl command is listed before the Linux (Bash) equivalent, and the Windows command is not clearly differentiated from the Linux one. The use of PowerShell syntax for openssl on Windows may confuse Linux users, and the Linux command is only shown as a variant. There are no explicit Linux-specific tools or instructions for certificate management, and the guidance for copying certificates mentions Azure Key Vault and SCP generically, without platform-specific details. There are no Linux-first or Linux-only examples, and the overall flow assumes familiarity with Windows tooling and ordering.

Recommendations:

Present Linux and Windows commands side-by-side or in parallel, rather than listing Windows first.
Use neutral shell syntax (e.g., bash) for openssl commands, or provide both PowerShell and bash examples with clear headings.
Include explicit Linux instructions for certificate management, such as using scp, chmod, and file permissions.
Where tools or scripts are referenced, clarify their compatibility with both Windows and Linux, and provide platform-specific notes if needed.
Ensure screenshots and UI instructions are not Windows-centric, or provide Linux/CLI alternatives where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented towards Windows, with all configuration steps relying exclusively on PowerShell commands and Windows-specific tools. There are no Linux-native examples or alternative instructions for users who may wish to interact with the EFLOW VM or its networking from a Linux environment. The workflow assumes the user is operating from a Windows host, and Linux commands are only mentioned for in-VM inspection, not for configuration.

Recommendations:

Provide equivalent instructions for managing EFLOW networking from a Linux host, if supported, or clarify host OS limitations.
Include examples using cross-platform tools (e.g., Azure CLI, SSH) where possible, not just PowerShell cmdlets.
If PowerShell is required, mention PowerShell Core and its availability on Linux/macOS, and provide guidance for those platforms.
Add a section explicitly addressing Linux/macOS users, outlining what is and isn't possible from those environments.
Where only Windows is supported, clearly state this limitation at the start of the article.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Ubuntu and Windows instructions for installing certificates, but Windows instructions are consistently presented after Ubuntu. However, the Windows section is more detailed, offering multiple methods (PowerShell, certlm GUI, .NET APIs), while the Ubuntu section only covers the standard CLI method. The Windows instructions reference specific tools (PowerShell Import-Certificate, certlm, Schannel) and provide more context about the Windows TLS stack. There is no explicit omission of Linux examples, but the Windows ecosystem is described in greater depth, and more Windows-specific tooling is mentioned.

Recommendations:

Expand the Ubuntu/Linux section to include alternative certificate installation methods (e.g., using update-ca-trust on RHEL/CentOS, or using GUI tools like GNOME Certificates).
Provide parity in troubleshooting and background information for Linux, such as mentioning OpenSSL, NSS, or GnuTLS as common TLS stacks and how they interact with the OS certificate store.
Add examples for programmatic certificate installation on Linux (e.g., using shell scripts or with .NET APIs on Linux).
Where Windows-specific tools are mentioned (e.g., certlm, Schannel), provide Linux equivalents (e.g., update-ca-certificates, OpenSSL) and explain their roles.
Ensure that all language-specific SDK instructions clarify any OS-specific steps or differences, especially for .NET and C, which may behave differently on Linux vs. Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation generally focuses on Linux container development and provides a Linux-first workflow, but there are subtle signs of Windows bias. The sample images are sourced from a repository named 'Cognitive-CustomVision-Windows', and there is no mention of a Linux-specific sample image repository. In the prerequisites, both Linux and Windows device setup links are provided, but the Windows link is listed second. However, there are no PowerShell or Windows command-line examples, and all CLI instructions use Bash syntax. The documentation does not provide explicit Linux shell alternatives for every step, and some references (such as the sample repo and image paths) are Windows-centric. There is also a lack of explicit instructions for running the workflow on a native Linux desktop (as opposed to a VM or container), and no mention of Linux-specific troubleshooting or differences.

Recommendations:

Provide sample image repositories or paths that are not Windows-specific, or clarify that the sample repo is cross-platform.
Include explicit Linux-native instructions and troubleshooting steps, not just for containerized environments but also for common Linux distributions.
Where sample paths or repositories are named with 'Windows', also mention or provide equivalent Linux-named resources.
Ensure all screenshots and file path examples use cross-platform or Linux-style paths (e.g., forward slashes), or provide both styles.
Add a section or notes about any differences or considerations when running the workflow on Windows vs. Linux hosts.
If referencing Windows devices or tools, ensure Linux equivalents are always mentioned first and with equal detail.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on Windows, specifically on deploying Azure IoT Edge for Linux on Windows (EFLOW). All device-side installation and configuration steps are provided exclusively as PowerShell commands, with no equivalent Linux-native instructions. Windows tools and patterns (e.g., Hyper-V, MSI installers, PowerShell cmdlets) are used throughout, and Linux is only referenced as the OS running inside a Windows-managed VM. Linux-native workflows, tools, or direct installation on a Linux host are not covered, and Linux command-line examples only appear after the Windows setup, for module management inside the EFLOW VM.

Recommendations:

Provide equivalent instructions for installing and configuring Azure IoT Edge directly on a native Linux device, including supported distributions and package managers.
Include Linux shell (bash) command examples alongside or before PowerShell commands, especially for common tasks like installation, configuration, and troubleshooting.
Mention Linux-native virtualization/containerization options (e.g., Docker, systemd) where Hyper-V or Windows-specific features are referenced.
Clarify in the introduction that this guide is Windows-specific, and link prominently to a Linux-native quickstart for users on Linux devices.
Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or provide a platform selection tab/switcher at the top of the page.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily Windows-centric, focusing almost exclusively on Windows tools (usbipd-win, PowerShell, Windows Package Manager) and workflows. All example commands are given in PowerShell, and there are no Linux command-line examples or instructions for performing similar tasks on a native Linux host. The only mention of Linux is in the context of the EFLOW VM, which is managed from Windows. Linux tools and workflows are not discussed, and Windows-specific patterns (such as using 'Add or Remove Programs', 'Services' app, and PowerShell modules) are presented without Linux equivalents.

Recommendations:

Provide equivalent Linux command-line instructions for attaching USB devices using usbip (e.g., using 'usbip' and 'usbipd' on Linux).
Include examples of how to perform the USB/IP setup and device attachment from a Linux host, not just from Windows.
When listing steps or tools, mention Linux-native approaches alongside Windows ones, or clarify that the instructions are Windows-only if no Linux equivalent exists.
Add a section or note explaining how to achieve similar functionality on a pure Linux environment, or link to relevant Linux documentation.
Balance PowerShell examples with bash or shell script examples where possible, especially for actions that can be performed inside the EFLOW VM.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ windows_examples

⚠️ missing_linux_example

Summary:

The documentation generally covers both Linux and Windows, but there are several instances of Windows bias. Windows-specific networking (NAT) is mentioned before Linux (bridge) in the runtime section, and Windows-specific error messages and patterns (e.g., hnsCall failed in Win32, Windows VM hostname length) are highlighted. Some troubleshooting steps and examples are tailored to Windows environments or Azure Portal/GUI workflows, with less emphasis on Linux CLI or configuration file methods. There are also sections where Windows tools or behaviors are discussed without equivalent Linux examples or with Linux mentioned only as an aside.

Recommendations:

Ensure Linux and Windows troubleshooting steps are presented in parallel, with equal detail and prominence.
For every Windows-specific error or tool mentioned (e.g., NAT, hnsCall, Windows VM hostname), provide the Linux equivalent (e.g., bridge networking, relevant Linux error messages).
Where Azure Portal or GUI steps are given, also provide CLI or configuration file alternatives for Linux users.
Add explicit Linux examples and commands where only Windows or portal-based instructions are present.
Review for sections where Windows is discussed first or exclusively, and restructure to present Linux and Windows options side by side or in a neutral order.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Linux and Windows instructions, but Windows-specific details and PowerShell examples are more extensive and appear before or in greater detail than Linux equivalents in some sections. Windows tools and patterns (e.g., PowerShell, registry edits) are described in depth, while Linux instructions are sometimes more concise or refer out to external documentation. The Windows installation process is described with multiple PowerShell code blocks and parameter explanations, while Linux installation is summarized and links to external guides.

Recommendations:

Ensure Linux instructions are as detailed and self-contained as Windows instructions, including explicit command-line examples for all steps (e.g., show apt/yum/dnf proxy configuration inline, not just as a link).
Provide Linux examples first in each section, or present both OSes in parallel to avoid a 'Windows-first' impression.
Where Windows-specific tools (like PowerShell or registry edits) are shown, provide equivalent Linux commands (e.g., using sed, systemctl, or editing files with nano/vim) with the same level of detail.
Include troubleshooting tips and environment variable configuration examples for both Linux and Windows, not just for Windows.
Avoid referring to Linux instructions as 'see external documentation' when Windows instructions are inline; instead, summarize or reproduce the key steps for Linux within the doc.
Balance the number and depth of code examples between platforms to ensure Linux users are equally supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ cmd_examples

⚠️ missing_linux_example

Summary:

The documentation is generally cross-platform, with most examples using 'bash' and 'iotedge' CLI commands that are applicable to both Linux and Windows. However, there are several instances where Windows-specific (cmd) syntax is used or presented first, such as for 'iotedge logs', 'docker rm', and 'iotedge restart'. There are no explicit PowerShell examples, but the use of 'cmd' blocks and lack of explicit Linux alternatives in some sections may confuse Linux users. Additionally, some commands (like 'docker rm') are shown only in Windows cmd syntax, and the documentation does not clarify platform differences where they may exist.

Recommendations:

For every 'cmd' example, provide a corresponding 'bash' example or clarify that the command is identical on both platforms.
When presenting commands, avoid using 'cmd' blocks unless there is a Windows-specific syntax difference; otherwise, use 'bash' or a neutral code block.
If there are platform-specific behaviors or prerequisites (such as service names, log file locations, or command syntax), explicitly document them for both Windows and Linux.
Consider adding a section at the top clarifying that all commands are cross-platform unless otherwise noted, and specify any exceptions.
Where tools or commands are platform-specific (e.g., service management), provide both Windows and Linux instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is generally focused on Linux containers and development, but there are subtle Windows biases: Windows device setup is mentioned before Linux in some places, Windows tools and patterns (e.g., Visual Studio Code, .NET, C#) are used exclusively, and there are no examples for Linux-native tools or alternative workflows (e.g., using VS Code on Linux, or using non-Microsoft languages). The SQL Server module is Windows-centric, and there is no mention of Linux-native SQL tools or alternative database engines in the main workflow.

Recommendations:

When listing device setup options, mention Linux devices before Windows devices to reflect the Linux container focus.
Provide explicit examples for using VS Code and Docker on Linux hosts (e.g., Ubuntu), including any Linux-specific commands or troubleshooting.
Include alternative workflows using Linux-native tools (e.g., using Azure CLI or Docker CLI directly, or using editors like Vim or nano for editing files).
Offer examples or notes for using other database engines (e.g., MySQL, PostgreSQL) in addition to SQL Server, especially since the intro mentions them.
Clarify that the tutorial is cross-platform and provide links or notes for Linux users where steps may differ (e.g., file paths, permissions).
Add a section or callout for common Linux troubleshooting steps (e.g., Docker permissions, SELinux/AppArmor issues).

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: it explicitly states that the tutorial uses a Windows computer, references Windows-specific features (such as Docker Desktop for Windows and Windows Subsystem for Linux), and provides Windows-style paths and commands before (or instead of) Linux equivalents. While the content claims to note differences for Linux/macOS, actual Linux-specific instructions, examples, or troubleshooting steps are often missing or less prominent. The use of PowerShell/Windows command prompts and the focus on Windows tools (e.g., Docker Desktop for Windows) further reinforce this bias.

Recommendations:

Provide parallel Linux/macOS instructions and examples wherever Windows-specific steps are given (e.g., directory creation, Docker installation, command-line usage).
List Linux and macOS installation steps and links before or alongside Windows, not after.
Use platform-agnostic paths (e.g., ~/dev/iotedgesolution or /home/user/dev/iotedgesolution) and commands in code snippets, or provide both Windows and Linux/macOS variants.
Include troubleshooting steps and tips specific to Linux/macOS environments, not just Windows.
When referencing tools like Docker Desktop, also mention and link to Linux-native alternatives (e.g., Docker Engine, Podman) and clarify their usage.
Avoid assuming the development machine is Windows; instead, explicitly support all major platforms in instructions and examples.
Ensure that environment variable instructions and path settings are clear for both Windows (%APPDATA%) and Linux/macOS (~/.local/), with equal prominence.

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 (e.g., Windows System Restore), and disk drive letters (C: and D:) without providing equivalent Linux examples or guidance. Troubleshooting steps and data storage recommendations are also Windows-centric, with no mention of Linux alternatives or tools.

Recommendations:

Include Linux-specific troubleshooting steps and examples, such as referencing common Linux file paths and commands.
When mentioning Windows System Restore, provide equivalent Linux recovery or rollback options (e.g., using Timeshift, snapshots, or manual recovery steps).
Clarify disk references for Linux VMs (e.g., /, /mnt, /tmp) alongside Windows drive letters.
When discussing storing user data, mention cross-platform solutions (e.g., OneDrive, but also Dropbox, Google Drive, or native Linux options like NFS or rsync).
Ensure all instructions and examples are presented for both Windows and Linux environments, or clearly indicate when a step is OS-specific.

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 for obtaining authorization tokens, while omitting equivalent Linux or cross-platform scripting examples (e.g., Bash, curl, Python). The PowerShell MSAL example is given more prominence and detail than the Azure CLI example, and there are no Linux-native command-line or scripting alternatives shown. This may hinder Linux users or those working in cross-platform environments.

Recommendations:

Add equivalent Linux/Bash/curl examples for obtaining OAuth tokens, such as using curl with the Microsoft identity platform endpoints.
Provide Python or other cross-platform scripting examples using MSAL libraries.
Ensure that Azure CLI examples are as detailed as the PowerShell examples, and clarify that Azure CLI is cross-platform.
When listing command-line options, present cross-platform tools (e.g., Azure CLI, REST with curl) before or alongside Windows-specific tools like PowerShell.
Explicitly mention that the PowerShell examples are primarily for Windows users, and provide guidance for Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation references PowerShell and Visual Studio Code (VS Code) as alternative tools for managing device identities, both of which are commonly associated with Windows environments. PowerShell is mentioned explicitly, and VS Code is referenced with an Azure IoT Hub extension, which may be more familiar to Windows users. The 'Other tools' section lists PowerShell before REST API, which is platform-neutral. However, the main how-to instructions use the Azure CLI, which is cross-platform, and there are no explicit Windows-only command examples or screenshots. There are no Linux-specific tools or workflows mentioned, nor are there any Linux-first examples or troubleshooting tips.

Recommendations:

Add explicit mention and examples of using the Azure CLI on Linux/macOS, including any OS-specific considerations (e.g., installation, permissions, shell differences).
If referencing PowerShell, clarify that PowerShell Core is cross-platform and provide Linux/macOS usage notes or examples.
Include alternative Linux-native tools or scripts (e.g., Bash scripts, curl commands for REST API usage) where appropriate.
Balance the order of tool mentions in the 'Other tools' section by listing REST API or CLI before PowerShell, or grouping them by platform neutrality.
Consider adding troubleshooting or environment setup notes for Linux users, especially for certificate management and CLI usage.

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), providing links and troubleshooting steps that focus on Windows environments (such as adjusting client experience settings for RDP via Windows Server documentation), and omitting equivalent Linux troubleshooting examples or commands. Powershell and Windows-centric Azure portal tabs are mentioned, while Linux/SSH troubleshooting is only referenced generically and not exemplified. Linux-specific tools, commands, or user experiences are not addressed, leading to a lack of parity for Linux users.

Recommendations:

Include Linux-specific troubleshooting steps and examples alongside Windows ones, such as using 'ping', 'traceroute', or 'ssh' for connectivity testing.
When referencing tools like PsPing, also mention cross-platform or Linux-native alternatives (e.g., 'iperf', 'nmap', 'netcat').
Provide links to both Windows and Linux documentation for adjusting RDP/SSH client settings.
Ensure that troubleshooting steps for SSH connectivity (common for Linux VMs) are as detailed as those for RDP.
When referencing Azure portal features or logs, include CLI and Bash examples, not just Powershell.
Add screenshots or error messages relevant to Linux SSH clients (e.g., OpenSSH errors) in addition to Windows RDP dialogs.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references a PowerShell script as the only example for querying lab quotas, without providing equivalent Bash, Azure CLI, or Linux-native alternatives. This suggests a bias toward Windows tooling and scripting, and does not offer parity for users on Linux or macOS platforms.

Recommendations:

Provide equivalent Bash or Azure CLI scripts for querying lab quotas, alongside the PowerShell example.
When referencing scripts or automation, include cross-platform options and note compatibility.
Explicitly mention that Azure CLI is available on all platforms and provide examples using it for common administrative tasks.
Review the documentation for other areas where only Windows-centric tools or scripts are referenced, and add Linux/macOS alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively providing instructions and examples for Windows environments, particularly in the sections on enabling ICMP (using PowerShell) and creating labs (defaulting to Windows 11 Pro images). There are no equivalent Linux commands or walkthroughs, and Windows tools and patterns are mentioned first or exclusively.

Recommendations:

Provide parallel Linux instructions for enabling ICMP (e.g., using ufw or firewalld commands to allow ICMP on Ubuntu/CentOS).
Include examples of creating labs with Linux VM images, and note any differences in setup or configuration.
When discussing remote access, mention SSH (for Linux) and RDP (for Windows) equally, and provide connection instructions for both.
Add screenshots or command-line examples for Linux environments where relevant.
Explicitly state that the tutorial applies to both Windows and Linux VMs, and highlight any OS-specific steps.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing only Windows-based tools and workflows, such as Visual Studio Code and the .NET/C# SDK, without providing equivalent Linux or cross-platform alternatives. The code example for message decoding is given exclusively in C# and references a Windows-style file path. There are no explicit Linux or cross-platform code samples or instructions for viewing or decoding the stored messages, and the guidance for opening downloaded files assumes a Windows environment.

Recommendations:

Provide equivalent code samples for Linux users, such as Python or Bash scripts, for decoding and reading the stored messages.
Reference cross-platform editors (e.g., VS Code, Vim, nano) and provide instructions for both Windows and Linux environments.
When mentioning file paths or actions like 'double-click', include Linux alternatives (e.g., using cat, less, or xdg-open).
Include explicit instructions for Linux users on how to download, locate, and open the files, and how to decode the messages using common Linux tools.
If referencing SDKs, mention and link to cross-platform SDKs (e.g., Azure IoT SDK for Python or Node.js) alongside .NET/C#.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias in the .NET/C# section by presenting Windows/PowerShell/ETW instructions before Linux/dotnet-trace equivalents. It also references Windows-specific tools (Event Tracing for Windows, PowerShell scripts) and provides more detailed, step-by-step instructions for Windows users. Linux instructions are present but appear after the Windows section, and the Windows approach is given more prominence.

Recommendations:

Present Linux and Windows instructions in parallel or in a unified table, rather than listing Windows first.
Ensure both platforms receive equally detailed, step-by-step instructions and troubleshooting notes.
Where possible, use cross-platform tools or highlight them first if available.
Avoid referencing Windows-only tools (like ETW and PowerShell scripts) without offering equivalent Linux-native alternatives or context.
Explicitly state platform support in each section and avoid implying Windows is the default or primary environment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily biased toward Windows environments, as it exclusively references PowerShell scripts and the Azure PowerShell module for automation. There are no examples or instructions for Linux or cross-platform scripting (e.g., Bash, Azure CLI). All script examples use Windows/PowerShell conventions, and there is no mention of how to perform these tasks on Linux or macOS systems.

Recommendations:

Provide equivalent automation scripts using Azure CLI and/or Bash to support Linux and macOS users.
Include instructions for installing and using the Azure CLI as an alternative to Azure PowerShell.
Add examples of running migration automation from a Linux shell, including script execution syntax.
Clearly state the platform requirements and, if scripts are Windows/PowerShell-only, offer guidance or links for Linux users.
Consider offering cross-platform PowerShell Core (pwsh) compatibility and document any differences or requirements.

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, instructions, and tooling references are specific to Windows (Hyper-V, PowerShell, Windows Firewall, SysPrep, etc.), with no mention of Linux-based workflows or alternatives. The process assumes the source image is Windows and the tooling is Windows-centric, with no guidance for users working from Linux environments or with Linux images.

Recommendations:

Include parallel instructions for importing Linux images, including preparation steps (e.g., using qemu-img for disk conversion, cloud-init for initialization, and Linux-specific configuration).
Provide examples using Linux-native tools (e.g., KVM/virt-manager for VM creation, shell commands for disk management, and Azure CLI for uploads).
Mention and link to documentation for preparing and uploading Linux VMs to Azure, ensuring users know both Windows and Linux are supported.
Avoid assuming the reader is using Windows by default; structure the documentation to present both Windows and Linux paths where applicable.
If the service only supports Windows images, state this explicitly at the beginning to avoid confusion.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows by exclusively providing C#/.NET code samples, referencing the Microsoft Azure IoT SDK for .NET, and assuming the use of Windows-centric development tools and workflows. There are no examples or guidance for Linux users, alternative SDKs (such as Python or Node.js), or cross-platform command-line usage. The instructions for obtaining connection strings and managing resources are tailored to the Azure Portal UI, which is more commonly used on Windows, and there is no mention of Azure CLI or Powershell alternatives for Linux/macOS users.

Recommendations:

Provide code samples using cross-platform SDKs, such as Python or Node.js, in addition to C#/.NET.
Include instructions and examples for performing import/export operations using the Azure CLI, which is available on all platforms.
Explicitly mention that the SDK and examples can be used on Linux and macOS, and provide setup instructions for those environments.
Add guidance for obtaining connection strings and managing resources using command-line tools (Azure CLI, az commands) rather than only through the Azure Portal.
Where possible, avoid referencing Windows-specific tools or workflows, or provide Linux/macOS equivalents alongside them.

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 for building and running the Azure IoT C SDK are provided only for Windows (using Visual Studio, Windows command prompt, and .exe executables). There are no equivalent Linux or macOS build/run instructions, and Windows-specific tools and patterns (e.g., Visual Studio, .exe output) are mentioned exclusively or before any cross-platform alternatives.

Recommendations:

Provide parallel instructions for building and running the C SDK sample on Linux and macOS, including required dependencies (e.g., gcc/clang, make, cmake) and example shell commands.
Mention and demonstrate use of cross-platform editors and tools (e.g., VS Code, nano, vim) alongside Windows-specific ones.
Show Linux/macOS terminal commands (e.g., bash shell, ./iothub_ll_telemetry_sample) in addition to Windows command prompt examples.
Clarify that the SDK and distributed tracing features are cross-platform, and link directly to Linux/macOS-specific build guides where appropriate.
Avoid assuming Visual Studio or Windows as the default development environment; present all supported platforms equally.

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 there are no explicit Linux or Bash shell examples. The CLI examples are cross-platform, but there is no mention of Linux-specific considerations, nor are there any screenshots or instructions referencing Linux environments. The PowerShell section assumes familiarity with Windows tooling, and there are no alternative examples for Linux users who might use Bash scripting or other shell environments.

Recommendations:

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 compatibility.
Add a short Bash script example for retrieving and updating IP filters using Azure CLI, demonstrating piping and jq for JSON parsing if needed.
Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux users (e.g., Bash with Azure CLI).
Include at least one screenshot or terminal snippet from a Linux environment to visually reinforce parity.
If there are any platform-specific caveats (such as differences in CLI installation or authentication), mention them in a dedicated section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation lists Azure CLI and Azure PowerShell as command-line methods for configuring message enrichments, with PowerShell (a Windows-centric tool) given equal prominence to Azure CLI. There are no explicit Linux/bash examples or mention of Linux-native tools. The ordering of methods (Portal, Azure CLI, Azure PowerShell) is neutral, but the inclusion of PowerShell without Linux/bash parity and the lack of Linux-specific guidance or examples suggests a subtle Windows bias.

Recommendations:

Add explicit bash/Linux shell examples for configuring message enrichments using Azure CLI.
Clarify that Azure CLI is cross-platform and provide example commands for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh).
If PowerShell is mentioned, also mention Linux-native shells to ensure parity.
Consider reordering the command-line methods to list Azure CLI before PowerShell, as CLI is more cross-platform.
Explicitly state that all features are available on Linux and macOS, not just Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several ways: instructions for setting environment variables and running commands are presented with Windows examples first, and in greater detail. Steps for running the sample application reference Windows-specific tools (such as NotePad and Visual Studio) and workflows (like using the command prompt and .sln files), with only brief or secondary mention of Linux equivalents. The Linux instructions for setting environment variables are present but less emphasized, and there are no examples for running the sample on Linux terminals or using Linux-native editors/IDEs. The overall workflow assumes familiarity with Windows tools and patterns, and lacks parity in Linux-focused guidance.

Recommendations:

Present Linux and Windows instructions in parallel, or alternate which comes first in each section.
Provide equivalent Linux command-line examples for running the sample application, including using bash/zsh and common Linux editors (e.g., nano, vim, gedit) instead of only Visual Studio/NotePad.
Include instructions for running the sample in popular Linux IDEs (e.g., VS Code on Linux, JetBrains Rider) and clarify that .NET Core is cross-platform.
Expand environment variable setup instructions for Linux, including how to persist variables in shell profiles.
Avoid referencing Windows-only tools (like NotePad) without Linux alternatives.
Add troubleshooting tips relevant to Linux environments (e.g., permissions, shell differences).
Ensure screenshots and UI references are not Windows-centric, or provide Linux equivalents where applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows development, specifically using Visual Studio and .NET. All code examples and setup instructions assume a Windows environment, with no mention of Linux-compatible tools, editors, or workflows. There are no Linux or cross-platform code samples, and the only development environment referenced is Visual Studio, which is primarily a Windows tool.

Recommendations:

Add parallel instructions for Linux users, such as using VS Code or JetBrains Rider, and include relevant terminal commands.
Provide .NET CLI commands for project creation, dependency installation, and running the app, which work cross-platform.
Include code snippets and instructions for running the sample on Linux/macOS, including any required dependencies or environment setup.
Mention and link to cross-platform SDKs and editors earlier in the prerequisites section.
Where screenshots are used, consider including those from cross-platform editors (e.g., VS Code) or clarify that the steps are similar in other environments.

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 (such as Cloud Witness and Windows Server Failover Clusters), linking to Windows-focused best practices, and omitting equivalent Linux guidance or examples. There are no Linux-specific instructions, screenshots, or references to Linux-based SQL Server deployments, and the high availability/disaster recovery sections focus exclusively on Windows clustering technologies.

Recommendations:

Include explicit guidance and examples for assessing SQL Server instances running on Linux, including any differences in discovery, assessment, or migration steps.
Add references and links to Linux-specific best practices for SQL Server on Azure Virtual Machines, such as performance tuning and high availability options for Linux.
When discussing high availability and disaster recovery, mention Linux clustering solutions (e.g., Pacemaker) and provide links to relevant documentation.
Ensure that any tool or feature (such as Cloud Witness or Shared Disk) is described with both Windows and Linux applicability, or clarify if it is Windows-only.
Provide screenshots and walkthroughs that include Linux-based SQL Server environments, not just Windows.
Balance references to Windows and Linux in all sections, especially when discussing licensing (e.g., mention RHEL/SLES subscriptions in parity with Windows Server licenses).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by referencing Visual Studio Code (a Microsoft tool popular on Windows), providing .NET/C# code samples, and suggesting the use of Windows-centric tools and workflows. There are no explicit Linux or cross-platform command-line examples for tasks like decoding messages, and the only code sample for message decoding is in C#. The instructions for downloading and opening files assume a GUI file explorer, which is more typical for Windows users, and there are no alternative instructions for Linux or macOS users.

Recommendations:

Include cross-platform or Linux-specific instructions for tasks such as decoding base64/UTF-8 messages (e.g., using Python or command-line tools like base64 and iconv).
Provide alternative examples for downloading and opening files using command-line tools (e.g., wget, curl, cat, base64) suitable for Linux/macOS users.
Reference code samples in other languages (such as Python or Node.js) in addition to C#/.NET, especially for common IoT SDK tasks.
When suggesting tools like Visual Studio Code, mention that it is available cross-platform and provide alternatives (e.g., Vim, nano, or other editors) for Linux users.
Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and avoid language that assumes a Windows environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While it primarily uses Azure CLI (which is cross-platform), several subtle cues and omissions indicate a Windows-centric approach: the use of Windows command prompt syntax (e.g., 'cmd/sh'), references to local command lines without clarifying cross-platform differences, and the exclusive use of .NET/C# for the simulated device sample. There are no explicit Linux or macOS-specific instructions, nor are there alternative code samples or troubleshooting notes for non-Windows environments. The tutorial assumes familiarity with Windows tools and patterns, and does not address potential differences in file paths, shell syntax, or package management on Linux/macOS.

Recommendations:

Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide example shell commands for both Bash (Linux/macOS) and PowerShell/Command Prompt (Windows) where syntax differs.
Include a note or section for Linux/macOS users regarding any environment-specific prerequisites or differences (e.g., file paths, shell commands, package installation).
Offer alternative device simulation samples in Python or Node.js, which are more commonly used on Linux/macOS, or at least link to such samples.
Clarify in the 'Run the simulated device app' section how to build and run the .NET sample on Linux/macOS, including any required dependencies or troubleshooting tips.
Where screenshots or navigation steps are shown, note any UI differences that may appear on non-Windows platforms (if applicable).
Avoid using 'cmd/sh' as a command block language; instead, specify 'bash' or 'powershell' as appropriate, or provide both variants.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias in several areas. In the 'Tools to connect and manage devices' section, Windows-centric tools such as Azure PowerShell are listed alongside cross-platform options, but there is no mention of Linux-specific tools or guidance. The order of tool presentation often puts Windows-first tools (PowerShell) before Linux-native alternatives. There are no explicit Linux command-line examples or references to Linux package managers or shell environments. The documentation does not provide parity in examples or tool recommendations for Linux users, and the language and tool choices may implicitly favor Windows development environments.

Recommendations:

Explicitly mention Linux compatibility for all tools, especially Azure CLI and VS Code extensions.
Include Linux-specific instructions or examples (e.g., bash commands, package installation via apt/yum, using Azure CLI in Linux shells).
Add references to Linux-native tools or workflows for IoT device management, if available.
Reorder tool listings to alternate or balance Windows and Linux options, or group cross-platform tools first.
Clarify that PowerShell Core is cross-platform, if relevant, and provide examples for both Windows PowerShell and bash/zsh.
Ensure that all tutorials and next steps include Linux as a first-class development environment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing only PowerShell-based examples and instructions for managing dependency analysis (enabling/disabling, exporting data), with no equivalent CLI or scripting guidance for Linux users. Windows terminology and tools (PowerShell, Connect-AzAccount, select-azsubscription) are used exclusively, and Windows credential requirements are described before Linux. There is no mention of Bash, Azure CLI, or Linux-native automation, making it harder for Linux administrators to follow or automate these tasks.

Recommendations:

Provide equivalent instructions and examples using Azure CLI and/or Bash scripts for all PowerShell-based operations (enabling/disabling dependency analysis, exporting data, etc.).
Explicitly mention and demonstrate how Linux users can authenticate and interact with Azure Migrate (e.g., using az login and az account set commands).
List Linux credential requirements before or alongside Windows requirements to avoid 'windows_first' ordering.
If PowerShell is required for some operations, clarify cross-platform support (e.g., PowerShell Core on Linux/macOS) and provide installation instructions.
Include screenshots or terminal outputs from Linux environments where applicable.
Reference Linux-native tools and patterns (e.g., cron jobs, shell scripting) for automation scenarios.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias towards Windows environments and tooling. It references only .NET/NuGet-based tools (ModelsRepositoryClient in C#), provides code samples exclusively in C#, and does not mention or provide examples for Linux-native tools, cross-platform SDKs, or command-line alternatives. There are no Linux shell, Python, or REST API examples, and no mention of how to use these features on Linux or macOS. The focus on NuGet and C# implicitly prioritizes Windows development environments.

Recommendations:

Add equivalent code samples in cross-platform languages such as Python, JavaScript, or Java, using their respective Azure SDKs.
Provide REST API usage examples (e.g., using curl or HTTPie) to demonstrate platform-agnostic access.
Mention and demonstrate how to install and use the Azure CLI or Azure SDKs on Linux/macOS, including package installation instructions.
Include shell script examples for retrieving models or interacting with IoT Hub, where applicable.
Reorganize sections to present cross-platform or platform-neutral approaches before Windows/.NET-specific ones.
Reference package managers and tools common on Linux (e.g., pip for Python, npm for Node.js) alongside NuGet.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation generally treats Windows and Linux as equivalent in most places, but there is a subtle Windows bias. In scenario 1, 'Windows' is consistently mentioned before 'Linux' ("for Linux and Windows", "Windows or Linux devices"), and Windows-specific technologies (e.g., Schannel, Win32 sockets) are called out alongside cross-platform ones, but Linux-specific equivalents (e.g., GnuTLS, epoll) are not. There are no explicit Linux command-line or tool examples, and no Linux-specific integration details are provided. The documentation also lists Windows as a recommended platform for the C SDK, but does not provide Linux-specific guidance or examples.

Recommendations:

Alternate the order of 'Windows' and 'Linux' mentions, or use 'Windows and Linux' consistently to avoid perceived prioritization.
Include Linux-specific details where Windows-specific technologies are mentioned (e.g., mention GnuTLS or other common Linux TLS stacks alongside Schannel).
Provide Linux-specific examples, such as command-line usage, build instructions, or integration tips, to ensure parity with Windows.
Highlight any Linux-specific considerations or optimizations, especially in areas where Windows-specific tools (like Schannel or Win32 sockets) are discussed.
Ensure that tables and recommendations do not list Windows before Linux unless there is a technical reason to do so.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows environments and tools for the on-premises SAP system configuration. All SAP system steps assume a Windows virtual machine, and the SAP Connector for Microsoft .NET is only described for Windows x64. File paths and instructions are Windows-specific, with no mention of Linux alternatives or parity. There are no examples or guidance for Linux-based SAP deployments.

Recommendations:

Add parallel instructions and screenshots for configuring SAP systems running on Linux, including using SAP GUI for Java or web-based SAP interfaces.
Document the use of SAP connectors and gateways on Linux, such as SAP NetWeaver RFC SDK or Java connectors, and provide installation and configuration steps for Linux environments.
Include Linux file paths and command-line examples where relevant, or clarify any platform limitations.
Explicitly state platform requirements and, if Windows is required for certain components, provide rationale and suggest workarounds or alternatives for Linux users.
Ensure that all references to tools (e.g., SAP Connector for Microsoft .NET) are accompanied by Linux equivalents or a note about their availability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by consistently referencing Windows-specific workflows, such as instructing users to use the Windows command prompt and Windows Subsystem for Linux (WSL) to access Linux tools. There are no native Linux or macOS instructions or examples, and the use of WSL is presented as the default way to run Linux commands. This approach assumes a Windows environment and omits guidance for users on Linux or macOS systems.

Recommendations:

Provide native Linux and macOS instructions alongside Windows instructions, especially for command-line operations.
Replace or supplement WSL-based steps with direct Linux/macOS shell commands and clarify any differences in environment setup.
Avoid assuming the user is on Windows; use neutral language such as 'In your terminal' instead of 'From a Windows command prompt'.
Where Windows-specific tools or portals are referenced, include equivalent steps for Linux/macOS users (e.g., accessing Azure portal, setting environment variables, etc.).
Add a prerequisites section that clearly states supported platforms and any platform-specific requirements or alternatives.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a mild Windows bias. While it is generally cross-platform and focuses on Azure-native and Kubernetes-based solutions, there are specific instances where Windows tools (e.g., BitLocker) are mentioned for encryption, and Windows is referenced before Linux in some cases (e.g., 'IoT Edge for Linux on Windows'). There are no explicit Linux command-line or tool examples, and Linux-native encryption solutions are not mentioned alongside Windows ones. No PowerShell-specific commands or Windows-only patterns dominate, but Linux parity could be improved.

Recommendations:

When recommending OS-level encryption (e.g., 'Encrypt data at rest'), mention Linux-native solutions such as LUKS/dm-crypt alongside BitLocker.
Where Windows is referenced (e.g., 'IoT Edge for Linux on Windows security'), also mention standard Linux deployments and link to their security guidance.
Provide examples or references for both Windows and Linux where OS-level or device-level security tools are discussed.
Audit for any other implicit Windows-first language and ensure Linux equivalents are given equal prominence.
Consider including a table or section summarizing security tool recommendations for both Windows and Linux environments.

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) as primary integration platforms for migration, both of which are traditionally Windows-centric technologies. There are no Linux or cross-platform integration tools mentioned as migration sources or alternatives, and no examples or guidance for users coming from Linux-based integration stacks. The focus on Windows tools and migration paths may leave Linux users underserved.

Recommendations:

Include references to common Linux-based integration platforms (such as Apache Camel, Talend, or MuleSoft) and provide migration guidance or comparison for users coming from those environments.
Mention and provide examples for integration scenarios that originate from Linux or open-source tools, not just Windows-based ones.
Balance the migration narrative by including Linux-native workloads or open-source ETL tools as potential sources for Azure Integration Services.
Clarify that Azure Integration Services are cross-platform and highlight support for Linux-based environments where applicable.

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, tools, and screenshots before Linux equivalents. Windows installation steps are more detailed and include multiple installation options (GUI, command line, automation tools), while Linux instructions are brief and lack comparable detail. References to Windows-specific tools (e.g., Configuration Manager, Intigua) and the absence of Linux automation or package manager examples further reinforce this bias.

Recommendations:

Present Windows and Linux instructions in parallel or in clearly separated, equally detailed sections.
Provide Linux installation options using common package managers (e.g., apt, yum, zypper) and automation tools (e.g., Ansible, shell scripts), similar to the Windows automation examples.
Include Linux-specific screenshots or terminal output where Windows screenshots are provided.
Mention Linux prerequisites and supported distributions with the same level of detail as Windows OS support.
Reference Linux equivalents for Windows tools (e.g., suggest using configuration management tools like Ansible or Puppet for Linux agent deployment).
Avoid always listing Windows steps first; alternate or group by OS to give equal prominence.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias, particularly in the CLI section for cloud-based solutions, where PowerShell is presented before Azure CLI and receives a dedicated section with multiple examples and links. There is also a reference to 'PowerShell functions for IoT Edge for Linux on Windows,' which is a Windows-specific scenario. While Azure CLI is covered, the prominence and ordering of PowerShell, as well as the lack of explicit Linux/Bash examples or mention of native Linux tools, indicate a bias toward Windows environments.

Recommendations:

Present Azure CLI examples before PowerShell in CLI sections, as Azure CLI is cross-platform and more commonly used on Linux.
Ensure parity in example depth and coverage between Azure CLI and PowerShell, especially for cloud-based scenarios.
Add explicit Bash/Linux shell examples or references where appropriate, especially for automation and scripting.
Avoid referencing Windows-specific tools (such as 'PowerShell functions for IoT Edge for Linux on Windows') without providing native Linux alternatives or clarifying their applicability.
Where possible, clarify that all Azure CLI commands work natively on Linux, macOS, and Windows, and provide guidance for Linux users.
Consider adding a section or callout 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 demonstrates a Windows bias by referencing Windows-specific limitations (such as maximum path length), linking to Windows documentation, and suggesting the use of Windows Device Manager for troubleshooting. There are no equivalent instructions or references for Linux or macOS users, and no examples or troubleshooting steps tailored to non-Windows environments.

Recommendations:

For path length issues, mention that this is a Windows-specific problem and clarify that Linux/macOS users are not affected. Optionally, provide guidance for long path handling on those platforms if relevant.
When suggesting the use of Windows Device Manager to identify COM ports, also provide instructions for Linux (e.g., using `dmesg`, `ls /dev/tty*`, or `lsusb`) and macOS (e.g., `ls /dev/tty.*`).
Wherever Windows-specific tools or settings are mentioned, add parallel instructions for Linux and macOS users.
Include examples and troubleshooting steps that are platform-agnostic or explicitly cover all major operating systems.
Review all links and references to ensure that they are not exclusively Windows-focused, or provide equivalent references for other platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a strong Windows bias. It specifies Windows 10/11 as a prerequisite, uses Windows-specific tools and commands (e.g., ESP-IDF CMD, Windows Device Manager), and provides file paths and instructions only for Windows environments. There are no instructions or examples for Linux or macOS users, and Linux equivalents for key steps (such as finding the serial port or running the ESP-IDF environment) are missing.

Recommendations:

Add a section in prerequisites listing supported Linux distributions (e.g., Ubuntu) and macOS, or clarify if only Windows is supported.
For each step involving Windows-specific tools (e.g., ESP-IDF CMD, Device Manager), provide equivalent instructions for Linux (e.g., using terminal, lsusb, dmesg, or /dev/ttyUSB*) and macOS.
Include Linux/macOS file path examples alongside Windows paths (e.g., ~/espbuild instead of C:\espbuild).
When referencing enabling long paths or other Windows-specific settings, provide analogous guidance for Linux/macOS if relevant, or state if not needed.
Mention and show how to launch the ESP-IDF environment on Linux/macOS (e.g., source export.sh, use terminal).
For flashing and monitoring, show how to identify the serial port on Linux/macOS and provide example commands.
If Azure IoT Explorer is Windows-only, suggest cross-platform alternatives or clarify platform limitations.

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, with all instructions, examples, and tooling focused exclusively on Windows environments. There are no Linux-based setup instructions, examples, or equivalent tooling mentioned. PowerShell and Hyper-V are assumed as the only options, and Linux is only referenced as a guest OS, not as a host or for management tasks.

Recommendations:

Provide equivalent instructions for enabling and managing nested virtualization using Linux-based hosts (if supported in Azure Lab Services), or clearly state if not supported.
Include Linux command-line examples (e.g., using KVM/QEMU or libvirt) where possible, or explain why only Hyper-V is supported.
Mention Linux-native tools and patterns for managing nested VMs, or provide guidance for Linux users.
If only Windows/Hyper-V is supported, make this limitation explicit at the beginning of the documentation and suggest alternatives for Linux users.
Add parity in recommendations and troubleshooting sections for Linux environments, or clarify support boundaries.

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 lists Windows 10/11 as a prerequisite, only provides instructions and scripts for Windows (e.g., .bat files), and references Windows-specific tools and workflows (e.g., File Explorer, Device Manager, Termite, and Windows CMD/PowerShell). There are no equivalent instructions, scripts, or tool recommendations for Linux (or macOS) users, and Linux alternatives for serial monitoring or flashing are not mentioned.

Recommendations:

Add Linux (and optionally macOS) as supported platforms in the prerequisites, or clearly state if they are unsupported.
Provide equivalent setup scripts for Linux (e.g., get-toolchain.sh) and include instructions for running them.
List Linux-compatible tools for serial port monitoring (e.g., minicom, screen, picocom) alongside or instead of Termite, and provide configuration steps for these tools.
Replace or supplement Windows-specific instructions (e.g., File Explorer, Device Manager) with cross-platform or Linux-specific alternatives (e.g., using the terminal, lsusb, dmesg, or /dev/tty* devices).
Ensure all command-line examples are cross-platform or provide both Windows and Linux variants.
If certain steps are only possible on Windows, clearly indicate this and suggest workarounds or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page demonstrates a moderate Windows bias, primarily through the exclusive mention of Windows-specific tools (e.g., BizTalk Administration Console, MMC snap-ins, Windows registry, PowerShell, Windows Authentication, and references to Windows Server/SQL Server/Visual Studio). In several sections, Windows-centric patterns and tools are described in detail, often without Linux or cross-platform alternatives being mentioned or prioritized. While Azure Logic Apps and related services are cross-platform, the migration narrative and tooling references frequently assume a Windows background and ecosystem.

Recommendations:

Wherever possible, provide Linux or cross-platform equivalents for administrative tools and configuration patterns (e.g., mention Azure CLI, Bash, or cross-platform SDKs alongside PowerShell and MMC).
When discussing deployment and automation, include examples or references for both PowerShell and Bash/CLI scripts.
Avoid assuming Windows registry or Windows-specific configuration files as the only configuration store; highlight cross-platform options (e.g., environment variables, Azure App Configuration) equally.
In developer tooling sections, mention cross-platform IDEs and editors (e.g., Visual Studio Code) before or alongside Visual Studio, and clarify their support on Linux/macOS.
For authentication and security, discuss alternatives to Windows Authentication (e.g., OAuth2, managed identities) and clarify their applicability in non-Windows environments.
In sections referencing hosting or infrastructure, explicitly note Linux support for Azure App Service, containers, and hybrid deployments.
Review all examples and tool mentions to ensure Linux users are not excluded or left to infer their own paths.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a clear Windows bias: deployment instructions exclusively use a Windows 11 Enterprise VM, require RDP for access, and reference Windows-specific tools (e.g., Windows Subsystem for Linux, Windows command prompt). There are no instructions or examples for deploying or running the solution natively on Linux or macOS systems, nor are there alternatives to Windows-specific steps. Linux is only mentioned as a subsystem within Windows, not as a first-class platform.

Recommendations:

Provide parallel instructions for deploying and running the production line simulation and edge infrastructure on native Linux VMs (e.g., Ubuntu Server) and/or macOS, including setup steps for Docker, Kubernetes (K3s), and related tools.
Include Linux-native commands and shell script examples outside of WSL context, and clarify any OS-specific differences.
Offer guidance for connecting to Linux VMs (e.g., via SSH) instead of only RDP/Windows.
Mention and support Linux-based Azure VM images as deployment targets.
Ensure all scripts and tools referenced are cross-platform or provide alternatives for Linux/macOS users.
Reorder sections or provide tabs so that Linux and Windows instructions are presented with equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias. It explicitly requires Windows 10 or 11 as a prerequisite, provides only Windows batch scripts (e.g., .bat files) for toolchain setup and build, and references Windows-specific tools (Termite, File Explorer, Device Manager). There are no equivalent instructions, scripts, or tool recommendations for Linux users, nor are Linux terminal commands or alternatives provided. The use of Windows CMD, PowerShell, and Git Bash for Windows is mentioned, but no mention is made of native Linux shells or workflows.

Recommendations:

Add Linux as a supported platform in the prerequisites, or clarify if it is unsupported.
Provide equivalent shell scripts (e.g., get-toolchain.sh, rebuild.sh) for Linux users, and document their usage.
List Linux alternatives for Windows-only tools such as Termite (e.g., minicom, screen, picocom) and provide setup instructions.
Replace or supplement File Explorer and Device Manager steps with Linux equivalents (e.g., using the terminal, lsusb, dmesg, or /dev/tty* for serial ports).
Include Linux command-line examples alongside Windows commands throughout the tutorial.
Explicitly state any platform limitations or differences in the workflow.

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 optimizing Windows Dockerfiles) in the 'Next steps' section, without mentioning Linux equivalents. There are no Linux or cross-platform examples, and the guidance for Dockerfile optimization and best practices is explicitly Windows-focused, despite AKS and App Service supporting Linux workloads. No Linux-specific tools, commands, or considerations are provided.

Recommendations:

Include Linux-focused examples and links, such as optimizing Linux Dockerfiles and best practices for Linux containers on AKS.
Balance references to Windows and Linux in the 'Next steps' section, ensuring both are covered equally.
Add notes or sections that highlight any differences or considerations for Linux-based SQL workloads and web apps.
Wherever Windows-specific guidance is given, provide a parallel Linux example or link to Linux documentation.
Review all referenced links to ensure Linux users are not excluded from further reading or optimization guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates some Windows bias, primarily by listing Windows prerequisites and tools (such as Visual Studio) before Linux equivalents, and by providing more detailed setup steps for Windows. The use of Windows-specific tools (Visual Studio) and the ordering of instructions (Windows first, then Linux) reinforce this bias. However, the tutorial does provide Linux instructions and examples, and the main sample build and run commands are cross-platform.

Recommendations:

Alternate the order of Windows and Linux instructions or present them in parallel tabs to avoid always listing Windows first.
Provide equivalent detail for Linux as for Windows, e.g., mention recommended Linux IDEs or editors (such as VS Code, CLion, or gedit) and any relevant Linux-specific setup tips.
Avoid assuming Visual Studio is the default C++ development environment; mention cross-platform alternatives.
Ensure all command-line examples are provided for both Windows (cmd or PowerShell) and Linux (bash), especially for git clone and build steps.
Where possible, use neutral, cross-platform language and tools in explanations and code snippets.
Explicitly state that all steps are supported on both Windows and Linux, and ensure parity in troubleshooting or notes sections.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias, particularly in the 'Endpoint management' section, where only Windows-specific tools (e.g., SysPrep, PsGetSid) and scenarios are discussed. There are no equivalent Linux tools or considerations mentioned for endpoint management, nor are Linux-specific examples provided elsewhere. While the document does reference a 'Data Science VM for Linux' in passing, the operational guidance and tooling focus almost exclusively on Windows environments.

Recommendations:

Include Linux-specific endpoint management considerations, such as handling machine IDs (e.g., /etc/machine-id) and tools for verifying uniqueness.
Provide examples or references for managing Linux VMs in lab environments, including common Linux configuration management or imaging tools (e.g., cloud-init, Ansible, or Linux image generalization).
When mentioning Windows tools like SysPrep and PsGetSid, also mention Linux equivalents or note if the issue (e.g., SID uniqueness) is not applicable or handled differently on Linux.
Ensure that examples and operational guidance are balanced between Windows and Linux, especially in sections discussing VM preparation, management, and troubleshooting.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a mild Windows bias, particularly in the 'Endpoint management' section, where only Windows-specific tools (such as SysPrep and PsGetSid) are mentioned for managing machine SIDs. Additionally, GPU VM sizes for visualization are labeled as '(Windows only)' without Linux alternatives or guidance. There are no Linux-specific endpoint management or content filtering examples, and Windows tools/patterns are referenced exclusively in relevant contexts.

Recommendations:

Include Linux-specific examples and tools for endpoint management (e.g., how to ensure unique machine IDs/SIDs on Linux VMs, such as using cloud-init or other Linux imaging best practices).
For GPU VM sizes, clarify Linux support or provide Linux-compatible alternatives for visualization workloads, or explicitly state if such options are unavailable.
In sections discussing tools like SysPrep and PsGetSid, add parallel Linux guidance (e.g., using 'machine-id', 'hostnamectl', or other relevant Linux utilities).
In content filtering, mention popular Linux-compatible filtering solutions or note any differences in approach for Linux VMs.
Review all examples and tool recommendations to ensure Linux and Windows parity, or clearly indicate platform-specific limitations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on using the Microsoft Remote Desktop app (a Microsoft/Windows-centric tool) for connecting to lab VMs from a Chromebook. It provides detailed steps and screenshots for this tool, with only a brief mention of alternative RDP clients (like Chrome Remote Desktop) in a note, and no instructions or examples for using them. The process for connecting to Linux VMs is only mentioned in passing, with no Linux-specific RDP client guidance or parity in examples.

Recommendations:

Provide step-by-step instructions for using alternative, platform-neutral or open-source RDP clients (such as Chrome Remote Desktop, Remmina, or FreeRDP) on Chromebook.
Include screenshots and examples for connecting to both Windows and Linux VMs, highlighting any differences in the process.
Mention and link to documentation for configuring and using SSH for Linux VMs, as SSH is often the preferred method for Linux remote access.
Rephrase recommendations to not exclusively promote Microsoft Remote Desktop, but to present it as one of several supported options.
Ensure that Linux VM connection workflows are given equal prominence and detail as Windows VM workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by consistently listing Windows instructions and tools before Linux equivalents, especially in SSH connection steps. Windows-specific tools (e.g., PuTTY, Windows built-in SSH) are highlighted, while Linux and macOS SSH instructions are missing or underexplained. There is also a lack of parity in example commands and tool recommendations for non-Windows users.

Recommendations:

Provide explicit SSH connection instructions for Linux and macOS users, including example commands and terminal usage.
List instructions for all platforms (Windows, Linux, macOS) in parallel tables or sections, rather than always leading with Windows.
Mention native SSH clients on Linux and macOS, and provide guidance for their use.
Balance tool recommendations by including popular Linux and macOS SSH clients (e.g., Terminal, GNOME Terminal, iTerm2) alongside Windows tools.
Ensure that all examples and screenshots are platform-agnostic or include variants for each major OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. Windows-specific guidance (such as installing and stopping Windows updates, configuring OneDrive, and autoshutdown for RDP sessions) is provided in detail, while equivalent Linux instructions or alternatives are either missing or less emphasized. Windows tools and patterns (e.g., OneDrive, Windows Update) are mentioned without Linux counterparts, and Windows-specific features are sometimes described before or in more detail than Linux equivalents.

Recommendations:

Provide equivalent Linux guidance for all Windows-specific instructions, such as how to update Linux VMs, disable automatic updates, and configure backup solutions (e.g., using rsync, Nextcloud, or other cross-platform cloud storage).
When mentioning tools like OneDrive, also mention Linux-compatible alternatives or clarify if/how OneDrive can be used on Linux VMs.
For features like autoshutdown, clarify if similar functionality exists for Linux VMs and provide instructions or references.
Ensure that examples and instructions are balanced between Windows and Linux, and avoid presenting Windows steps or tools first unless there is a technical reason.
Explicitly mention and link to Linux-specific documentation or how-to guides wherever Windows-specific guides are referenced.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by primarily describing and illustrating the process using Windows-specific tools (Hyper-V Manager, PowerShell), and by assuming the user is operating from a Windows environment. Linux-native workflows and tooling (such as KVM, qemu-img, or Linux shell commands) are only briefly mentioned or referenced externally, with no step-by-step guidance provided for users on Linux hosts. The upload process also references Windows-centric tools and documentation, and PowerShell is suggested for disk operations without Linux equivalents.

Recommendations:

Provide a parallel, step-by-step workflow for preparing and converting a Linux image using Linux-native tools (e.g., KVM, qemu-img, virt-manager).
Include Linux command-line examples for resizing and converting disk images, such as using qemu-img.
When referencing upload tools, mention and provide examples for AzCopy and Azure CLI usage on Linux, not just from a Windows context.
Ensure links to documentation for Linux-based image preparation are as prominent as those for Windows/Hyper-V.
Avoid assuming the user is on Windows; clarify which steps are OS-specific and offer alternatives.
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 page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions and examples for retrieving the public IP address of Azure Lab Services labs. There are no equivalent command-line examples for Linux or macOS users (e.g., using Azure CLI or Bash). The references and links are all centered around PowerShell modules, reinforcing the Windows-centric approach and omitting cross-platform alternatives.

Recommendations:

Add equivalent instructions and code examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
Include Bash shell script examples for retrieving the public IP address, demonstrating parity with the PowerShell example.
Mention both PowerShell and Azure CLI options at the start of the 'Find public IP for a lab' section, rather than only referencing PowerShell.
Provide links to Azure CLI documentation alongside PowerShell references.
Explicitly state that the instructions apply to Windows and provide alternative steps for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for deployment, review, and cleanup tasks. However, PowerShell (a Windows-centric tool) is consistently presented alongside or immediately after CLI, and is referenced as a primary method for deployment and resource management. There is no explicit mention of Linux-specific shell environments (e.g., Bash), nor are there any examples or notes tailored for Linux users. The documentation assumes familiarity with PowerShell and Windows tools, and does not address potential differences or considerations for Linux users.

Recommendations:

Explicitly state that Azure CLI commands work cross-platform (Windows, macOS, Linux) and can be run in Bash or other Linux shells.
Add Bash-specific notes or examples where relevant, especially for file paths and shell syntax.
Clarify that PowerShell is optional and primarily relevant for Windows users; suggest Bash or other shells for Linux users.
Include troubleshooting tips or environment setup instructions for Linux users (e.g., installing Azure CLI on Linux, using chmod for file permissions).
Where PowerShell modules are referenced (e.g., Az.LabServices), note their availability and support on Linux PowerShell Core, or provide alternative CLI commands.
Ensure that any screenshots or UI references do not assume a Windows environment.

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 management tasks, but PowerShell is given equal or sometimes more prominence than CLI. PowerShell is a Windows-centric tool, and there is no mention of Linux-specific shell environments or examples (e.g., Bash). The documentation does not clarify cross-platform compatibility for PowerShell, and there are no Linux-specific notes or examples, which may lead Linux users to feel less supported.

Recommendations:

Explicitly state that both Azure CLI and Azure PowerShell are cross-platform, and clarify installation instructions for Linux and macOS users.
Add Bash-specific examples or notes, especially for common deployment and file management tasks.
When presenting multiple command-line options, consider listing Azure CLI (which is more universally cross-platform) before PowerShell.
Include a section or callout for Linux/macOS users, mentioning any differences or prerequisites.
Avoid assuming PowerShell is the default or primary shell; clarify that users can use their preferred shell environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-based VM images (e.g., 'microsoftwindowsdesktop.windows-11.win11-21h2-pro') in the code sample, omitting any Linux alternatives. Additionally, the 'Next steps' section highlights Azure PowerShell and Az.LabServices cmdlets, which are traditionally more familiar to Windows users, without mentioning cross-platform or Linux-native tools. There are no Linux VM image examples or references to Linux command-line tools.

Recommendations:

Include examples that use Linux VM images (e.g., Ubuntu, CentOS) in the code samples, either as alternatives or alongside the Windows example.
In the 'Next steps' section, add links to Azure CLI documentation and examples, which are cross-platform and widely used on Linux.
Explicitly mention that the Python SDK and code samples work on both Windows and Linux, and provide any necessary Linux-specific setup instructions if applicable.
Where PowerShell is referenced, also reference Bash or other Linux-native scripting environments to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias by mentioning Windows-centric tools (e.g., Visual Studio, Azure Storage Explorer) as example software to install, and by listing Remote Desktop Protocol (RDP) before Secure Shell (SSH) when describing connection methods. There are no explicit Linux-specific examples or tools mentioned, and no Linux-focused workflow or screenshots are provided.

Recommendations:

Provide Linux-specific examples of software to install (e.g., GCC, Python, Gedit) alongside or instead of Windows examples.
Alternate the order of connection methods (mention SSH before RDP when the template is Linux-based, or clarify which applies to which OS).
Include screenshots or instructions that show connecting to a Linux VM, including SSH command-line examples.
Mention Linux tools and workflows (e.g., package installation with apt/yum, configuring systemd services) in the update steps.
Explicitly state that the process applies to both Windows and Linux VMs, and highlight any OS-specific considerations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily biased toward Windows environments, specifically Windows 11 and Windows Server, with all setup instructions and tooling (PowerShell, Hyper-V, Windows Settings) being Windows-specific. There are no instructions or examples for enabling nested virtualization with Linux-based template VMs, nor is there mention of Linux virtualization technologies (such as KVM or VirtualBox). Even when Linux is referenced (e.g., nested Ubuntu VMs), the host and configuration steps are always Windows-centric.

Recommendations:

Add explicit guidance on whether Linux-based template VMs are supported for nested virtualization in Azure Lab Services. If not supported, state this clearly at the beginning.
If Linux hosts are supported, provide equivalent instructions for enabling nested virtualization on Linux template VMs, including examples using KVM or other common Linux virtualization tools.
Include Linux command-line examples (e.g., using virsh, virt-manager, or qemu) alongside PowerShell/Windows examples.
Mention Linux tools and patterns (e.g., SSH, systemd, libvirt) where relevant, and not only as guest OSes.
If only Windows is supported as a host, clarify this limitation early and suggest alternatives or workarounds for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias. While it states that both Windows and Linux VMs are supported, it references Windows-specific behaviors and resources more prominently. For example, the warning about shutdown behavior links only to a Windows-specific guide, and there are no Linux-specific troubleshooting or configuration examples. The documentation also mentions RDP sessions (primarily a Windows protocol) without referencing Linux equivalents, and does not provide Linux command-line or tool-based examples for configuring or troubleshooting auto-shutdown.

Recommendations:

Provide equivalent Linux-specific troubleshooting and configuration guidance, such as linking to a guide on controlling Linux shutdown behavior.
Include examples or references for Linux remote connection protocols (e.g., SSH, VNC) alongside RDP.
Ensure that any warnings or tips are balanced with both Windows and Linux contexts, not just Windows.
Add Linux command-line examples or screenshots where appropriate, especially for common distributions.
Reference Linux tools and patterns (e.g., systemd, shutdown commands) where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing PowerShell as a management tool without mentioning Linux CLI alternatives, mentioning Windows and Linux images but providing more detail and default behaviors for Windows, and referencing Windows-centric tools (Az.LabServices PowerShell module) without Linux equivalents. There are no CLI or scripting examples for Linux users, and the only explicit command-line management option is PowerShell.

Recommendations:

Include Azure CLI and/or Bash examples for managing labs, alongside or before PowerShell examples.
Mention and link to cross-platform management tools (e.g., Azure CLI, REST API) wherever PowerShell is referenced.
Provide parity in instructions and screenshots for both Windows and Linux VM scenarios, including connection methods and credential management.
Clarify default behaviors for both Windows and Linux images equally, and ensure that Linux-specific workflows are as detailed as Windows ones.
Add troubleshooting and management guidance for Linux users, not just Windows/PowerShell users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_heavy

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a Windows-first bias. Most examples and explanations focus on Windows virtual machines, especially for idle detection and automatic disconnect features, which are described as Windows-only. Linux support is mentioned only as an exception or limitation, with no equivalent Linux-specific instructions or examples. The 'Next steps' section highlights PowerShell (a Windows-centric tool) for lab management, without mentioning cross-platform or Linux-native alternatives.

Recommendations:

Provide Linux-specific examples and instructions where features are supported (e.g., how idle detection or shutdown works on Linux VMs).
Clarify feature parity and limitations for Linux VMs up front, and offer workarounds or alternatives if possible.
Include CLI (az cli) or REST API examples for lab management, which are cross-platform, alongside or instead of PowerShell.
Ensure that Linux tools and workflows are presented with equal prominence to Windows/PowerShell options.
Add screenshots or terminal output relevant to Linux scenarios where applicable.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation demonstrates a mild Windows bias, primarily in the tools and command-line examples provided. Windows-centric tools such as Visual Studio and Azure PowerShell are mentioned explicitly and often before cross-platform or Linux-native alternatives. The only explicit command-line example for retrieving the tenant ID uses PowerShell, with no mention of Bash or Azure CLI equivalents. Visual Studio (Windows-only) is listed before Visual Studio Code (cross-platform) as a function creation tool. There are no Linux-specific instructions or examples, and the documentation assumes familiarity with Windows-based workflows and tools.

Recommendations:

When listing tools for creating Azure Functions, mention cross-platform options (e.g., Visual Studio Code, Azure CLI) before or alongside Windows-only tools like Visual Studio.
Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for common tasks like retrieving tenant IDs.
Explicitly state when steps or tools are cross-platform, and provide guidance for Linux/macOS users where applicable.
Include screenshots or instructions from non-Windows environments (e.g., terminal, VS Code on Linux/macOS) to demonstrate parity.
Audit all command-line and tool references to ensure Linux users are equally supported and not required to use Windows-specific tooling.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias. While the main instructions are platform-neutral and focus on the Azure Lab Services web portal, 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 examples or notes about Linux VMs, and the only references to file systems and data loss are Windows-centric. No Linux-specific instructions or terminology are provided.

Recommendations:

When referring to OS and temporary disks, include Linux equivalents (e.g., 'the OS disk (C: drive on Windows, / on Linux)' and 'the temporary disk (D: drive on Windows, /mnt on Linux)').
Add notes or examples that clarify behavior for both Windows and Linux VMs, especially regarding disk persistence and data loss.
Where screenshots or instructions reference Windows-specific concepts, provide parallel information for Linux users if applicable.
Consider including a section or note that explicitly addresses differences in managing Windows vs. Linux lab VMs, if any exist.
Ensure that links to further instructions (e.g., connecting to a VM) are clear about supporting both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell automation for gateway management, mentioning the 'gateway Windows service account', and lacking any Linux-specific instructions or examples for installing or managing the on-premises data gateway. There is no mention of Linux support, tools, or equivalent automation methods, and all troubleshooting and operational guidance assumes a Windows environment.

Recommendations:

Explicitly state whether the on-premises data gateway supports installation and operation on Linux systems. If not supported, clarify this limitation early in the documentation.
If Linux is supported, provide installation and management instructions for Linux, including command-line examples (e.g., using bash, systemd for service management).
Include Linux-specific troubleshooting steps, such as how to restart the gateway service on Linux.
Offer automation examples for Linux environments (e.g., using shell scripts or Azure CLI) alongside PowerShell examples.
Avoid referring exclusively to 'gateway Windows service account'; instead, use OS-neutral language or provide both Windows and Linux variants.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing PowerShell-based installation and usage instructions as the primary method, referencing Windows-style file paths and tools (e.g., func.exe), and showing output examples with Windows directory structures. While a Bash alternative is mentioned, it still relies on PowerShell scripts, which are not native to Linux/macOS environments. There are no native Linux/macOS installation instructions or examples, and the overall workflow assumes a Windows-centric development environment.

Recommendations:

Provide native Bash or shell script alternatives for installing and managing extensions, not just using PowerShell via Bash.
Include Linux/macOS-specific instructions and examples, such as using dotnet CLI directly or alternative scripting methods.
Show output examples from Linux/macOS terminals (e.g., with /home/user paths) alongside Windows examples.
Clarify cross-platform compatibility for all tools and scripts mentioned, and link to any prerequisites for Linux/macOS environments.
Avoid assuming the presence of PowerShell on non-Windows systems, or provide guidance on installing and using it if required.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a Windows bias by explicitly stating that the custom functions capability is only available on Visual Studio Code running on Windows. There are no instructions, troubleshooting, or examples for Linux or macOS users. All references to file paths, tools, and environment setup implicitly assume a Windows environment, and there is no mention of Linux equivalents or cross-platform considerations.

Recommendations:

Clearly indicate platform support and, if possible, provide a roadmap or alternatives for Linux/macOS users.
If the feature is Windows-only, suggest workarounds or alternative approaches for non-Windows users.
Include explicit statements about the lack of Linux/macOS support in the prerequisites and throughout the documentation.
Provide equivalent instructions, examples, and troubleshooting steps for Linux/macOS if/when support becomes available.
Avoid using only Windows-style file paths and environment variables; include cross-platform examples where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas: troubleshooting and cluster validation steps are provided only with PowerShell and Windows command prompt examples, with no equivalent Linux/bash commands. The use of 'Run Visual Studio Code as administrator' and references to Windows-specific ports and tools (e.g., SMB file share, PowerShell scripts) further reinforce a Windows-centric approach. Linux or cross-platform alternatives are not mentioned or are missing in key operational and troubleshooting sections.

Recommendations:

Provide Linux/bash equivalents for all PowerShell and Windows command prompt commands, especially for kubectl, helm, and az CLI usage.
Include instructions for running Visual Studio Code and required commands on Linux/macOS, not just Windows (e.g., clarify 'run as administrator' for non-Windows platforms).
Mention and provide guidance for using NFS or other Linux-friendly file share options alongside SMB, or clarify SMB support on Linux.
Ensure troubleshooting scripts and instructions (such as troubleshoot.ps1) have cross-platform alternatives (e.g., bash scripts) or note their compatibility.
When referencing tools (e.g., PowerShell, Windows command prompt), always provide parity with bash/zsh or other common Linux shells.
Review all screenshots and UI instructions to ensure they are not exclusively Windows-centric, or provide Linux/macOS equivalents where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias: Windows terminology and tools (such as 'File Server role', 'IIS web server', and 'local admin privileges') are mentioned explicitly and in detail, while Linux equivalents are either omitted or only briefly referenced. Several discovery features (e.g., File Server discovery) are Windows-only, and there are no concrete Linux command examples or explicit Linux tool references. Linux is mentioned in passing, often as an afterthought, and there is a lack of parity in examples and guidance for Linux environments.

Recommendations:

Provide explicit Linux examples and instructions alongside Windows ones, such as how to identify file server roles or web server roles on Linux (e.g., using Samba, NFS, Apache, or Nginx).
When mentioning Windows-specific tools or roles (like 'File Server role' or 'IIS'), also mention and document the Linux equivalents (e.g., Samba/NFS for file servers, Apache/Nginx for web servers).
Add Linux command-line examples (e.g., shell commands for credential setup, service discovery, or permissions) wherever Windows or PowerShell instructions are given.
Clarify which features are supported on Linux, and if not supported, provide a roadmap or alternatives.
Ensure that credential and permission requirements are described in detail for both Windows and Linux, not just Windows (e.g., what Linux user/group permissions are needed for discovery).
Where features are Windows-only (such as File Server discovery), explicitly state this limitation and suggest possible workarounds or future support for Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias in its troubleshooting section by providing only Windows command prompt examples (e.g., 'C:\>nslookup', 'C:\psping'), referencing Windows-style paths (e.g., 'C:\home\site\wwwroot'), and omitting equivalent Linux/Bash commands and file paths. There are no Linux or cross-platform command-line examples, and the tools mentioned (psping, tcpping) are Windows-centric. The main deployment instructions focus on Azure Portal and Visual Studio Code, which are cross-platform, but the troubleshooting guidance assumes a Windows environment.

Recommendations:

Provide equivalent Linux/Bash command examples for troubleshooting steps (e.g., 'nslookup', 'dig', 'ping', 'nc' or 'curl' for port checks).
Include Linux-style file paths (e.g., '/home/site/wwwroot') alongside Windows paths in error messages and troubleshooting.
Mention cross-platform or Linux-native tools (e.g., 'nc' or 'nmap' instead of 'psping') for network connectivity testing.
Explicitly state that the troubleshooting steps apply to both Windows and Linux VMs, and provide command examples for both.
Where possible, use environment-agnostic language and tools to ensure parity for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation exhibits a Windows bias in several ways: Windows-specific tools and paths are mentioned first or exclusively in key sections (e.g., Windows Defender Firewall, regedit, .exe files, C:\ paths), and some setup and troubleshooting steps are only described for Windows (e.g., registry edits, firewall prompts). Linux/macOS equivalents are missing or only briefly mentioned later, and some examples (such as editing registry keys or handling firewall prompts) are not cross-platform. There is also a tendency to use Windows terminology and screenshots throughout, with limited parity for Linux/macOS users.

Recommendations:

Provide Linux and macOS equivalents alongside Windows instructions for all setup, configuration, and troubleshooting steps (e.g., firewall configuration, file paths, environment variables, and permissions).
Include Linux/macOS-specific examples and screenshots where relevant, especially for common tasks like editing configuration files, running commands, or handling permissions.
Avoid using Windows-specific terminology or tools (such as regedit, Windows Defender Firewall, .exe files) without offering alternatives for other platforms.
When referencing file paths, use cross-platform notation or provide both Windows and Linux/macOS examples (e.g., C:\Users\ vs. ~/).
For tools like ngrok, show command-line usage for Linux/macOS, not just Windows (e.g., avoid only referencing ngrok.exe).
Explicitly state when a feature or step is Windows-only, and provide guidance or workarounds for Linux/macOS users where possible.
Review all code snippets and configuration examples to ensure they are valid on all supported platforms, or provide platform-specific variants.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing explicit mention and guidance for creating Logic App templates using Azure PowerShell (with the LogicAppTemplate module), but does not mention or provide equivalent examples for Linux or cross-platform CLI tools (such as Azure CLI). The only automation tool referenced for template creation is PowerShell, which is primarily associated with Windows environments. There are no Linux shell or Azure CLI examples, nor is there a discussion of cross-platform approaches. This may leave Linux or macOS users without clear guidance for automating Logic App deployments.

Recommendations:

Add equivalent instructions and examples for creating and deploying Logic App templates using Azure CLI, which is cross-platform and widely used on Linux and macOS.
When referencing automation tools, mention Azure CLI before or alongside Azure PowerShell to avoid implying a Windows-first workflow.
Provide sample shell (bash) scripts or command-line snippets for Linux/macOS users where appropriate.
Explicitly state that all template deployment steps can be performed on any OS using Azure CLI, and link to relevant cross-platform documentation.
Review and update any tips or notes that currently reference only PowerShell to include Azure CLI alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several ways: (1) Instructions for accessing the Kudu environment and file paths in the Azure portal use Windows-centric terminology (e.g., CMD, backslashes in paths), with no mention of Linux alternatives or Bash; (2) The 'WEBSITE_NODE_DEFAULT_VERSION' setting is described as applying 'when running your logic app workflows on Windows', with no equivalent guidance for Linux; (3) There are no examples or instructions for managing app or host settings using Linux-native tools or environments (e.g., Bash, Linux file paths, or Linux-based Azure App Service environments).

Recommendations:

Include Linux/Bash equivalents alongside Windows-specific instructions, especially for accessing the Kudu environment and navigating file paths (e.g., show both CMD and Bash navigation).
Clarify which settings or behaviors differ between Windows and Linux hosting environments, and provide explicit guidance for both.
When referencing settings like 'WEBSITE_NODE_DEFAULT_VERSION', explain how this applies (or not) to Linux environments, and provide Linux-specific configuration steps if needed.
Add examples of managing app and host settings using Linux-native tools (e.g., Bash scripts, Linux file navigation, or Linux-based Azure CLI usage).
Review all file path examples to ensure both Windows (backslash) and Linux (forward slash) conventions are represented where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-centric environments (VMware, Hyper-V, physical servers) in prerequisites, and by linking to Windows Dockerfile optimization and best practices in the 'Next steps' section. There are no explicit Linux or cross-platform examples, nor are Linux-specific tools, patterns, or migration considerations mentioned. The guidance and links focus on Windows workloads and tools, with no parity for Linux-based web apps or Dockerfiles.

Recommendations:

Include explicit guidance and links for Linux-based environments (e.g., Linux VMs, Linux web servers) in the prerequisites and discovery steps.
Provide examples or references for optimizing Linux Dockerfiles and managing Linux containers, alongside the Windows Dockerfile optimization link.
Mention Linux migration considerations and best practices for App Service and AKS targets, ensuring parity with Windows guidance.
Balance references to Windows and Linux tools, patterns, and migration strategies throughout the documentation.
Add sample scenarios or walkthroughs for both Windows and Linux web apps to illustrate cross-platform support.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page focuses exclusively on SQL Server Agent (a Windows-centric tool) and Azure Elastic Job Agent for job orchestration, with all management examples and screenshots referencing SQL Server Management Studio (SSMS), which is primarily a Windows application. There are no examples or mentions of Linux-native tools or cross-platform alternatives for managing jobs or interacting with SQL Server/Azure SQL. The documentation does not provide parity for Linux users in terms of tooling or workflow.

Recommendations:

Include examples or references to cross-platform tools such as Azure Data Studio, sqlcmd, or PowerShell Core (which runs on Linux) for managing jobs and interacting with SQL Server/Azure SQL.
Mention and provide examples for using Linux-compatible automation/orchestration tools (e.g., cron jobs, systemd timers, or Azure CLI) to trigger or monitor long-running stored procedures.
Add screenshots and walkthroughs using cross-platform tools (e.g., Azure Data Studio) in addition to or instead of SSMS.
Clarify which steps or tools are Windows-only and provide Linux alternatives where possible.
Highlight any differences or requirements for users running SQL Server on Linux (e.g., SQL Server Agent is available on SQL Server for Linux, but management is different).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias. All installation instructions, screenshots, and operational details assume a Windows environment. There is no mention of Linux or macOS support, nor are there any examples or instructions for non-Windows systems. The documentation references Windows-specific tools (e.g., PowerShell cmdlets, Windows service accounts), and even basic commands (like 'whoami /upn') are Windows-only. The use of PowerShell for automation is highlighted without Linux alternatives.

Recommendations:

Explicitly state whether the on-premises data gateway is supported on Linux or macOS. If not, clarify this early in the documentation.
If Linux/macOS support exists, provide parallel installation and configuration instructions, including relevant screenshots and command-line examples.
Offer automation examples using cross-platform tools (e.g., Azure CLI, bash scripts) in addition to PowerShell.
Reference Linux equivalents for commands (e.g., how to find the UPN or equivalent on Linux).
Discuss service management (start/stop/restart) for the gateway on Linux if supported, or clarify that only Windows services are available.
When mentioning Windows-specific tools or patterns, provide context or alternatives 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 listing Azure PowerShell before Azure CLI when mentioning automation tools, referencing Visual Studio (a primarily Windows IDE) with detailed steps, and omitting equivalent Linux/CLI workflows or editors. There are no explicit Linux or cross-platform editor instructions, and PowerShell is mentioned before CLI, reinforcing a Windows-first perspective.

Recommendations:

List Azure CLI before or alongside Azure PowerShell when mentioning automation tools, to reflect cross-platform parity.
Provide explicit instructions or examples for editing workflow JSON using cross-platform editors such as VS Code on Linux/macOS, or command-line tools (e.g., nano, vim, or code command).
Include Linux/macOS-specific deployment and editing workflows, such as using Azure CLI in Bash or other shells.
Balance Visual Studio references with equivalent steps for Visual Studio Code or other cross-platform tools.
Avoid assuming Visual Studio as the default editor; clarify that it is Windows-only and suggest alternatives for other platforms.

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 and Windows OS credentials exclusively, requiring PowerShell and VMware Tools for discovery, and providing no examples or instructions for Linux-based environments. The credential and discovery instructions focus on Windows authentication patterns, and there is no mention of Linux tools, authentication methods, or discovery steps for Linux servers.

Recommendations:

Include explicit instructions and examples for discovering SQL Server instances running on Linux servers, including supported authentication methods (e.g., SQL authentication, Linux user credentials).
Mention any required tools or prerequisites for Linux-based appliances (e.g., bash, SSH, required packages) alongside PowerShell and VMware Tools.
Provide parity in credential management instructions, such as how to add Linux credentials or handle discovery on non-Windows OS.
Add notes or sections clarifying support (or limitations) for SQL Server on Linux and how the discovery process differs, if at all.
Ensure screenshots and UI references are not exclusively Windows-centric, or provide Linux-specific alternatives where applicable.

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 and instructions are provided exclusively using PowerShell commands and Windows file paths (e.g., C:\template.json). There is no mention of Linux or macOS equivalents, nor are there CLI/bash examples or cross-platform instructions. The tools and modules referenced (such as LogicAppTemplate and ARMClient) are presented in a PowerShell-centric manner, and installation steps assume a Windows/PowerShell environment.

Recommendations:

Provide equivalent examples using Azure CLI and bash shell commands for Linux/macOS users.
Include file path examples using both Windows (C:\...) and Linux/macOS (/home/user/...) conventions.
Clarify whether the LogicAppTemplate and ARMClient tools are cross-platform, and if so, provide installation and usage instructions for Linux/macOS.
Add a section or callout specifically addressing Linux/macOS users, outlining any differences or prerequisites.
Where possible, present Azure CLI examples before or alongside PowerShell examples to promote cross-platform parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell as the only command-line example for creating Microsoft Entra application identities, with no equivalent Bash, Azure CLI, or Linux-native instructions. The PowerShell section is explicitly called out, and there is no mention of cross-platform tools or commands. Additionally, the documentation refers to 'PowerShell' and 'commandlet' terminology, which are strongly associated with Windows environments. There are no examples or guidance for users on Linux or macOS platforms.

Recommendations:

Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
Clearly label both PowerShell and Azure CLI sections, and present them in parallel tabs or sections to ensure parity.
Avoid using Windows-specific terminology (such as 'commandlet') without also referencing cross-platform equivalents.
Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant documentation.
Consider including Bash script examples or references for Linux users where appropriate.

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 before Azure CLI, and scripting examples for OAuth consent reference PowerShell specifically, with no mention of Bash or Linux-native alternatives. The Azure DevOps and Azure Pipelines sections focus on Microsoft-centric tools, which are more commonly used in Windows environments. There are no explicit Linux or Bash examples, and no mention of cross-platform scripting approaches.

Recommendations:

Provide Bash or shell script examples alongside PowerShell for deployment and OAuth authorization tasks.
Explicitly state that Azure CLI commands are cross-platform and can be run on Windows, macOS, and Linux.
When referencing scripting for OAuth consent, include or link to Bash/Linux-compatible scripts or note how to adapt the process for non-Windows environments.
Balance the order of sections by presenting Azure CLI before or alongside PowerShell, as CLI is often preferred in Linux/macOS environments.
Mention cross-platform CI/CD tools (such as GitHub Actions) in addition to Azure DevOps, or clarify that Azure Pipelines can run on Linux agents.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows by exclusively referencing PowerShell cmdlets for critical disaster recovery operations (such as incrementing control numbers) and does not provide equivalent instructions or examples for Linux or cross-platform environments. There are no CLI, Bash, or REST API alternatives mentioned, and the only automation tooling discussed is PowerShell, which is traditionally associated with Windows, despite now being cross-platform. This may hinder Linux users or those preferring non-Windows automation tools.

Recommendations:

Provide equivalent Azure CLI commands or Bash script examples for all PowerShell cmdlet instructions, especially for incrementing control numbers and managing integration accounts.
Mention REST API alternatives where available, with example requests, to ensure platform-agnostic automation.
Explicitly state if PowerShell Core (cross-platform) is supported and provide installation guidance for Linux/macOS if PowerShell is required.
Ensure that all automation steps are demonstrated with both Windows (PowerShell) and Linux (CLI/Bash) tooling, or clarify any platform limitations.
Add a section or callout for Linux users, summarizing supported tools and approaches for disaster recovery tasks.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references PowerShell scripts and provides only PowerShell (.ps1) examples for automating VM migration. There is no mention of Bash, shell scripts, or cross-platform scripting alternatives, nor any guidance for Linux or macOS users. The documentation assumes a Windows-centric workflow, both in tool choice and script format.

Recommendations:

Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the scripts are compatible with PowerShell Core on Linux.
Explicitly mention cross-platform compatibility if the PowerShell scripts work with PowerShell Core on Linux/macOS, and provide installation/setup guidance for those platforms.
Include references to Azure CLI or REST API alternatives for users who prefer or require non-PowerShell automation.
Reorder or supplement examples so that Linux and cross-platform options are presented alongside or before Windows-specific instructions.
Add a section addressing common Linux automation patterns and how they can be used in conjunction with Azure Migrate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-only tool) and its extensions for creating maps and schemas, without mentioning any Linux-compatible alternatives or workflows. Troubleshooting steps and installation instructions are also tailored to Visual Studio on Windows. While Visual Studio Code is mentioned as an option for managing and deploying logic apps, there are no Linux-specific examples or guidance, and PowerShell (primarily associated with Windows, though cross-platform) is listed before any Linux-native tools or CLI alternatives.

Recommendations:

Provide explicit guidance and examples for Linux users, such as using the Azure CLI or Visual Studio Code for all artifact creation and deployment steps.
List cross-platform tools (e.g., Visual Studio Code, Azure CLI) before or alongside Windows-only tools like Visual Studio.
Clarify which steps or tools are Windows-specific and offer Linux/macOS alternatives where possible.
Include troubleshooting and installation notes relevant to Linux environments.
If certain features (like map/schema design) are only available on Windows, state this clearly and suggest possible workarounds or roadmap plans 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 Visual Studio (a Windows-only tool) and the Microsoft Azure Logic Apps Enterprise Integration Tools Extension for schema creation, without mentioning cross-platform or Linux alternatives. Troubleshooting steps and notes focus on Windows-specific issues (e.g., DPI awareness, registry edits). No Linux or macOS equivalents or instructions are provided for schema creation or tool installation, and Visual Studio Code is only mentioned for uploading schemas, not for schema creation.

Recommendations:

Include instructions for creating schemas using cross-platform tools (e.g., XML editors available on Linux/macOS, or command-line tools like xmllint or xsd).
Mention and provide examples for using Visual Studio Code (which is cross-platform) with relevant extensions for schema creation and editing.
If possible, provide guidance for using open-source or platform-agnostic tools to generate and validate schemas.
Add troubleshooting notes relevant to Linux/macOS environments, or clarify when steps are Windows-specific.
Ensure that all tool recommendations and examples are either cross-platform or have clear Linux/macOS alternatives documented.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references running PowerShell scripts from Standard workflows and includes a section on running PowerShell, but does not mention Bash, shell scripts, or Linux-native scripting options. There are no explicit Linux/Unix-specific examples or references to Linux tools, and the scripting section is Windows-centric. Additionally, there are no deployment or management instructions that highlight Linux CLI or Bash usage, and the examples for code execution focus on Windows technologies.

Recommendations:

Add examples and documentation for running Bash or shell scripts from Logic Apps workflows, alongside PowerShell.
Include references to Linux-native tools and scripting environments where applicable, such as using Azure CLI in Bash.
Provide parity in code execution examples by showing both PowerShell (Windows) and Bash (Linux) script integration.
Where PowerShell is mentioned, clarify that cross-platform PowerShell Core is supported, or provide Linux-specific guidance if available.
In deployment and management sections, add examples using Linux-based automation tools and shell environments.

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 using Azure PowerShell for all command-line examples and automation steps. There are no CLI (az), Bash, or Linux-native instructions or examples provided. References to documentation for creating disk encryption sets and double encryption also point to Windows/PowerShell-specific guides. The workflow assumes a Windows environment (e.g., file paths like C:\Users\Administrator\Downloads\template.json) and does not mention or illustrate how to perform these tasks from a Linux or cross-platform perspective.

Recommendations:

Provide equivalent examples using the Azure CLI (az) in addition to PowerShell, especially for key steps like creating disk encryption sets, retrieving VM details, and deploying ARM templates.
Include Bash shell command examples and Linux file path conventions where relevant (e.g., ~/Downloads/template.json).
Link to both Windows/PowerShell and Linux/Azure CLI documentation for referenced tasks (such as disk encryption set creation).
Explicitly state that the process can be performed from Linux/macOS environments and highlight any differences or prerequisites.
Consider adding a section or callout for cross-platform users, summarizing which tools and commands are supported on which OS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias in several areas. PowerShell is used as the primary or only example for certificate conversion and base64 encoding, with no equivalent Linux or cross-platform commands provided. When troubleshooting certificate issues, the guidance focuses on Windows tools (cert mmc/PowerShell) and only mentions OpenSSL as an afterthought, without providing Linux-specific instructions. This approach may hinder Linux or macOS users, as it assumes familiarity with Windows tooling and does not offer parity in examples or guidance.

Recommendations:

For all code or command-line examples (such as converting PFX to base64), provide both Windows (PowerShell) and Linux/macOS (OpenSSL, shell) equivalents side by side.
When troubleshooting certificate issues, include Linux/macOS-specific steps and error messages, not just Windows tools.
Avoid referencing Windows tools (e.g., cert mmc, PowerShell) as the default or only method; instead, present cross-platform alternatives first or equally.
Where screenshots or UI steps are shown, clarify if any steps are platform-specific and provide alternatives if needed.
Review all sections for implicit Windows assumptions and ensure Linux users can follow the documentation without needing to translate or research missing steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by prioritizing Windows-centric tools (Visual Studio, Azure PowerShell) and workflows, mentioning them before or instead of Linux-friendly alternatives. There are no explicit Linux or cross-platform CLI examples, and the quickstart and getting started sections focus on the Azure portal and Visual Studio, which are traditionally Windows-first tools. Linux-native development tools and workflows (such as Azure CLI, Bash, or VS Code on Linux) are not highlighted or exemplified.

Recommendations:

Include explicit examples and quickstarts using cross-platform tools such as Azure CLI and Visual Studio Code, especially on Linux.
Mention and provide links to Linux-friendly workflows and tools (e.g., Bash scripts, deployment from Linux terminals, VS Code on Linux).
Balance the order of tool mentions so that Visual Studio Code and Azure CLI are listed before or alongside Visual Studio and Azure PowerShell.
Add sample commands or walkthroughs for Linux users, such as deploying Logic Apps or Functions from a Linux shell.
Clarify that all major development workflows are supported on Linux, macOS, and Windows, and provide documentation links for each platform.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Microsoft-centric tools (such as Host Integration Server, Visual Studio, HIS Designer, and 3270 Design Tool) for mainframe and midrange integration. There are no mentions of Linux-based tools, development environments, or cross-platform alternatives. All example tooling and workflows assume a Windows environment, and there are no instructions or guidance for Linux users.

Recommendations:

Include information about cross-platform or Linux-compatible alternatives for mainframe and midrange integration, if available.
Provide examples or workflows using non-Windows development environments (such as VS Code on Linux or Mac, or command-line tools).
Explicitly state platform requirements and, where possible, offer guidance for Linux users (e.g., running tools in containers, using remote development, or alternative open-source tools).
Balance tool recommendations by mentioning both Windows and Linux options, or clarify if certain features are Windows-only and suggest workarounds.
Add a section addressing Linux developer scenarios, even if only to acknowledge limitations and provide suggested approaches.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows environments, specifically Visual Studio on Windows. All examples, tool references, and workflows assume the use of Visual Studio, Cloud Explorer, and Azure PowerShell—tools that are either unavailable or have limited support on Linux. There are no instructions or alternatives for Linux users, such as using Visual Studio Code, Azure CLI, or cross-platform editors. The documentation does not mention Linux or macOS compatibility, nor does it provide parity in tooling or workflow for non-Windows platforms.

Recommendations:

Add equivalent instructions for managing Logic Apps using Visual Studio Code, which is cross-platform, and the Azure Logic Apps (Standard) extension.
Include examples using Azure CLI (az logicapp) for tasks such as deployment, downloading, and managing Logic Apps, as Azure CLI is available on Linux, macOS, and Windows.
Document how to edit and manage Logic Apps using other cross-platform editors (e.g., VS Code, JetBrains Rider) and JSON templates.
Explicitly state the platform limitations of Visual Studio and Cloud Explorer, and provide links or references to Linux/macOS-compatible alternatives.
Where PowerShell is mentioned, provide equivalent Azure CLI commands.
Add a section or callout for Linux/macOS users, outlining supported workflows and tools for Logic Apps management.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows terminology, tools, and patterns are often mentioned first or exclusively (e.g., 'roles and features (Windows servers only)', SQL Server, .NET/IIS web apps). Linux is referenced, but with less detail and fewer examples. There are no Linux-specific database or web app examples, and the documentation does not provide parity in describing Linux workloads or tools. The credential and permissions section for Linux is more technical, but lacks practical examples or guidance compared to Windows.

Recommendations:

Provide Linux-specific examples for database and web application discovery and inventory (e.g., MySQL, PostgreSQL, Apache, Nginx).
When listing workload types, alternate the order or explicitly mention both Windows and Linux equivalents (e.g., 'a server can be a Linux or Windows server').
Expand the 'Software inventory' section to clarify what is collected on Linux servers and provide examples.
Include more details and examples for Linux credential setup, troubleshooting, and permissions, similar to the Windows guidance.
In tables and attribute lists, ensure Linux workloads and technologies are represented equally alongside Windows ones.
Add screenshots or walkthroughs that show Linux server discovery and inventory views, not just Windows-centric ones.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by consistently referencing Windows-specific SQL Server deployment patterns (such as SQL Server on Azure VM with Windows), linking exclusively to Windows-based best practices, and omitting any mention of Linux-based SQL Server deployments or examples. There are no Linux or cross-platform scenarios, tools, or migration considerations discussed, despite SQL Server's support for Linux.

Recommendations:

Include explicit references to SQL Server on Linux as a supported source and target for Azure Migrate assessments.
Provide parallel guidance and examples for migrating SQL Server workloads running on Linux, including any differences in assessment, readiness, or sizing.
Link to best practices and performance guidelines for SQL Server on Linux VMs in Azure, not just Windows.
Clarify whether the assessment tool supports both Windows and Linux SQL Server sources, and highlight any platform-specific considerations.
Add examples or notes for Linux-specific configurations (e.g., file system layouts, disk mapping, or high availability patterns like Pacemaker clusters).

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 exclusively for Windows Server environments. Only PowerShell scripts and Windows command-line tools (such as CertUtil) are referenced, with no mention of Linux equivalents or support. The appliance is described as being installed on Windows Server 2019/2022, and all examples and screenshots are Windows-centric. There are no instructions or even references for deploying or managing the scale-out appliance on Linux systems.

Recommendations:

Provide explicit information on whether Linux-based deployment of the Azure Migrate appliance is supported. If not, state this clearly at the beginning.
If Linux deployment is supported, add parallel instructions for Linux environments, including shell script equivalents, Linux prerequisites, and command-line examples (e.g., using sha256sum for checksum validation).
Include Linux-based examples for downloading, installing, and running the appliance, as well as for exporting/importing configuration files.
Mention Linux tools and commands alongside Windows ones (e.g., bash, curl, openssl, etc.), and provide screenshots from Linux desktops where appropriate.
If only Windows is supported, briefly explain the rationale and suggest alternatives or workarounds for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias primarily by referencing PowerShell as the only scripting language example for running scripts within workflows, without mentioning or providing examples for Linux-native scripting options such as Bash or shell scripts. There is also a lack of Linux-specific tooling or development environment references, with a focus on Visual Studio Code and PowerShell, both of which are traditionally associated with Windows environments, even though VS Code is cross-platform. No Linux-first or cross-platform command-line examples are provided.

Recommendations:

Include examples for running Bash or shell scripts in Standard workflows, alongside PowerShell and C#.
Explicitly mention and provide examples for developing and deploying Logic Apps from Linux and macOS environments, not just Windows.
Reference cross-platform tools and editors (such as VS Code) in a way that highlights their availability and parity on Linux and macOS.
If PowerShell is mentioned, clarify that PowerShell Core is cross-platform, and provide Linux usage examples.
Add a section or note about how to perform local development, debugging, and deployment from Linux systems, including any prerequisites or differences.

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, with no mention of Linux or macOS alternatives. Windows-specific tools (Visual Studio, Azure PowerShell) are required, and there are no examples or guidance for Linux users. The use of PowerShell for deployment prompts further reinforces the Windows-centric approach.

Recommendations:

Provide equivalent instructions for Linux and macOS users, such as using Visual Studio Code or the Azure CLI for Logic Apps development and deployment.
Include references and links to cross-platform tools and workflows, e.g., how to use VS Code with the Logic Apps extension, or how to deploy Logic Apps using the Azure CLI.
Add Linux/macOS-specific setup and deployment steps, including screenshots where appropriate.
Clearly indicate at the beginning that the guide is Windows-specific, and direct users on other platforms to alternative guides.
Where PowerShell is mentioned, also provide Bash/Azure CLI equivalents for 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 (e.g., SQL Server Management Studio, MSI installers), mentioning Windows authentication for local development, and omitting explicit Linux or cross-platform command-line examples. The setup and development workflows are described primarily in the context of Visual Studio Code and Azure portal, but there is no mention of Linux-specific development environments, tools, or authentication methods. The documentation assumes a Windows-centric environment for local development and SQL server setup.

Recommendations:

Add explicit instructions and examples for Linux environments, such as using Azure CLI, Bash, or cross-platform SQL tools (e.g., Azure Data Studio, sqlcmd).
Mention and provide examples for Linux-compatible authentication methods (e.g., SQL authentication, managed identities when available) and clarify any differences in setup between Windows and Linux.
Reference cross-platform installers for required tools (e.g., Azure Functions Core Tools via npm or apt/yum, not just MSI).
Include notes or sections on developing and running Logic Apps on Linux or macOS, including any limitations or required workarounds.
List cross-platform SQL management tools alongside SSMS, such as Azure Data Studio or command-line utilities.

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 references Windows Server and PowerShell-based workflows before or instead of Linux alternatives, uses Windows-specific tools (such as Chocolatey for installing kubectl and Helm), and provides detailed SMB file share setup instructions only for Windows, with no equivalent Linux example. While some Linux commands are present (e.g., apt-get in a test pod), the overall guidance and tooling favor Windows environments, and Linux-native approaches for key steps (such as SMB share setup) are missing.

Recommendations:

Provide parallel instructions for setting up SMB file shares on Linux systems, including step-by-step guides for common distributions (e.g., Ubuntu, CentOS).
Include Linux-native installation commands for kubectl and Helm (e.g., using apt, yum, or direct downloads) alongside or before Windows/Chocolatey examples.
Reference Linux-based Kubernetes clusters and workflows (e.g., AKS on Ubuntu, generic Linux clusters) equally or before Windows Server-based clusters.
Offer PowerShell and Bash script examples side-by-side, or default to Bash/Azure CLI where possible, as these are cross-platform.
Clarify when instructions or scripts are Windows-specific and provide equivalent Linux alternatives (e.g., for setting execution policy, environment variables, or running scripts).
Expand the SMB file share testing and troubleshooting section to include Linux-native tools and commands (e.g., mount.cifs, smbclient).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-centric encodings (such as 'windows-1250', 'windows-1252') in examples, referencing .NET and Azure Functions exclusively (which are historically Windows-first technologies), and omitting any Linux/Unix command-line or open-source tool examples (such as iconv or recode). There are no Linux shell, Python, or cross-platform code samples, nor is there mention of Linux-native encoding workflows.

Recommendations:

Add Linux/Unix command-line examples for encoding conversion, such as using 'iconv' or 'recode' to convert files between encodings.
Include Python or other cross-platform code samples for encoding conversion, demonstrating parity with the .NET/Azure Functions approach.
Provide examples using Linux file systems and connectors (e.g., SFTP, NFS) and mention Linux-native encoding names (e.g., ISO-8859-1, UTF-16LE) alongside Windows code pages.
Clarify that .NET and Azure Functions are cross-platform, and provide guidance for running these examples on Linux hosts.
List encoding names as recognized on both Windows and Linux, and link to cross-platform encoding documentation (such as the Python codecs module or iconv encoding list).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Microsoft/Windows-centric tools and services. It exclusively uses Office 365 Outlook and Outlook.com for email actions, with only a brief mention of Gmail (and with restrictions). There are no examples or guidance for Linux users or for integrating with non-Microsoft email services, and all screenshots and workflow steps are based on the Azure Portal UI, which is most familiar to Windows users. There is no mention of using CLI tools (such as Azure CLI or Bash scripts), nor are there examples for Linux-based workflows or open-source alternatives.

Recommendations:

Provide examples using non-Microsoft email providers (such as generic SMTP, SendGrid, or other open standards) and show how to integrate them into Logic Apps.
Include guidance or examples for users who prefer to use the Azure CLI or Bash scripts to create and manage Logic Apps, in addition to the Azure Portal UI.
Add explicit Linux-friendly instructions, such as how to authenticate or manage resources from Linux/macOS environments.
Balance the documentation by mentioning and demonstrating non-Windows tools and connectors earlier and more prominently, not just as afterthoughts.
Consider including screenshots or walkthroughs from cross-platform tools (e.g., Azure CLI, VS Code) to ensure parity for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows tools (such as Microsoft Azure Storage Explorer), referencing Windows as the default or example operating system, and providing PowerShell examples and links before or alongside Azure CLI, with no explicit Linux or cross-platform alternatives. There are no instructions or screenshots for Linux users, and the use of Windows-specific features (like in-portal editing only on Windows) is highlighted without offering Linux workarounds or parity.

Recommendations:

Provide explicit Linux and macOS instructions and screenshots alongside Windows steps, especially for tool installation and usage (e.g., Storage Explorer).
When referencing command-line tools, present Azure CLI examples before or alongside PowerShell, and clarify cross-platform compatibility.
Avoid using Windows as the default or only example for operating system selection; include Linux and macOS as equal options.
Mention and link to Linux-compatible tools and workflows where available, and note any limitations or differences for non-Windows users.
For features only available on Windows (e.g., in-portal editing), suggest alternative approaches for Linux users, such as local development with VS Code or other editors.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows environments, specifically Hyper-V and Windows-based tools. All command-line examples use Windows commands (CertUtil, PowerShell), and instructions reference Windows-only tools (Hyper-V Manager, Local Group Policy Editor). There are no Linux equivalents or alternative instructions for Linux hosts or appliances, and Windows terminology and patterns are used exclusively or presented first throughout.

Recommendations:

Provide equivalent Linux-based instructions or clarify if Linux is unsupported for this scenario.
Where PowerShell or Windows commands are given (e.g., CertUtil, Get-FileHash, Enable-WSManCredSSP), offer Linux alternatives (e.g., sha256sum for hashing).
If the appliance can be run on Linux (or if a Linux-based appliance is available), include setup instructions for Linux hosts (e.g., using KVM, QEMU, or VirtualBox).
Clarify in the introduction that the instructions are Windows/Hyper-V specific, and link to Linux/KVM/VMware documentation if available.
When discussing credential types, provide more detailed Linux-specific guidance and permissions, not just mention Linux in a list.
If the appliance is Windows-only, explicitly state this limitation early in the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows/Microsoft-centric bias by exclusively using Microsoft services (Office 365 Outlook, Outlook.com) for email triggers and actions, referencing only the Azure portal (which is most commonly accessed via Edge/Windows), and not providing Linux-friendly alternatives or examples. There is no mention of Linux-native email providers, open-source tools, or cross-platform command-line instructions. The workflow assumes the user has access to Microsoft accounts and tools, and does not discuss parity with Linux-based environments or non-Microsoft email providers beyond a brief mention of Gmail (with restrictions).

Recommendations:

Provide explicit examples using non-Microsoft email providers (e.g., generic IMAP/SMTP, Gmail with Linux clients) and show how to configure them in Logic Apps.
Include screenshots or instructions for accessing the Azure portal from Linux systems, or mention the Azure CLI as an alternative to the portal for resource creation and management.
Add a section or callout for Linux users, highlighting any differences or additional steps required when using non-Windows environments.
Reference open-source or cross-platform tools (e.g., Thunderbird, Evolution, mutt) for email testing, and provide sample workflows using these clients.
Ensure that connector documentation links and workflow steps are not solely focused on Microsoft products, and provide equal visibility to alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. All setup and deployment instructions are written for Windows environments, using PowerShell, Windows command prompt, and referencing Windows-specific tools (e.g., CertUtil, Registry Editor, IIS, Windows Activation Service). There are no Linux equivalents or alternative instructions for deploying or running the Azure Migrate appliance on Linux servers. Even when Linux servers are mentioned (for discovery), the appliance itself is assumed to be running on Windows, and no Linux-based installation or management steps are provided.

Recommendations:

Provide parallel instructions for deploying and running the Azure Migrate appliance on Linux-based hosts, including supported distributions.
Include Linux shell (bash) equivalents for all PowerShell and Windows command prompt steps (e.g., extracting files, verifying hashes with sha256sum, running installer scripts).
Reference Linux-native tools (e.g., systemd for services, Apache/Nginx for web apps if supported, Linux file paths) alongside Windows tools.
Clarify OS requirements and explicitly state if the appliance can only run on Windows, or provide guidance for Linux users if a Linux appliance is not supported.
Ensure all screenshots and code snippets have Linux alternatives where applicable.
Mention Linux-specific troubleshooting steps and log file locations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation shows evidence of Windows bias. The 'Create resource group' step is included via a Powershell-specific include file, and there is no explicit Linux or cross-platform shell example for this critical Azure setup step. The prerequisites mention OpenSSL on 'Windows or Linux', but the only shell commands shown are generic Bash, with no explicit Windows CMD or Powershell equivalents. The resource cleanup step uses Azure CLI (cross-platform), but the initial resource group creation is Powershell-only, and the documentation does not clarify how Linux users should proceed for that step.

Recommendations:

Provide both Azure CLI and Powershell examples for resource group creation, with Azure CLI (cross-platform) shown first or equally.
Explicitly state that all shell commands (e.g., mkdir, go mod init) work on both Linux and Windows (with Git Bash or WSL), or provide Windows CMD equivalents if needed.
Replace or supplement the Powershell-specific include with an Azure CLI example, or provide both side-by-side.
Review all included snippets to ensure Linux users are not left without clear instructions for any step.
Consider adding a note or table summarizing which commands work on which platforms, and recommend Azure CLI for cross-platform compatibility.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. It references PowerShell for resource group creation (via an include), mentions Windows before Linux in several places, and highlights Windows-specific tools and workflows (such as Visual Studio and PowerShell) before or instead of their Linux equivalents. While Linux is mentioned, examples and instructions are not equally balanced or explicitly provided for Linux users.

Recommendations:

Provide explicit Linux (bash/Azure CLI) examples alongside or before PowerShell examples, especially for resource group creation.
Avoid phrasing that lists Windows before Linux by default; use neutral or alternating order (e.g., 'Windows or Linux').
When mentioning tools like Visual Studio, also mention popular Linux IDEs (e.g., VS Code, IntelliJ IDEA) and clarify cross-platform support.
Ensure that all setup and authentication steps are clearly documented for both Windows and Linux environments.
If using includes that are PowerShell-specific, add or link to equivalent bash/Azure CLI instructions for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates several forms of Windows bias. Resource group creation is handled via an included PowerShell script, with no mention of Bash or Azure CLI alternatives. The setup steps and code snippets do not clarify cross-platform usage, and where command-line tools are referenced, PowerShell is implied or used by default. While OpenSSL is mentioned as available on both Windows and Linux, the overall flow and examples assume a Windows-first environment, with no explicit Linux or Bash shell instructions or screenshots. There are no Linux-specific notes or parity in the resource group creation or setup steps.

Recommendations:

Provide both PowerShell and Bash/Azure CLI examples for resource group creation and other setup steps.
Explicitly mention and show command-line instructions for both Windows and Linux environments.
Where scripts are included via markdown includes, ensure there are Linux/Bash equivalents or links.
Clarify that .NET and the Azure SDK are cross-platform, and show usage in both Windows and Linux shells.
Add screenshots or terminal output examples from both Windows and Linux environments.
Review all included content (e.g., create-member.md, register-provider.md) for similar bias and update as needed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by including a PowerShell-based resource group creation step (via an include file) without providing equivalent Linux (Bash/Azure CLI) instructions. The use of PowerShell is implied as the default, and there are no explicit Linux command-line examples or parity in tooling. While OpenSSL is mentioned as a prerequisite for both Windows and Linux, the operational steps and examples are Windows-centric.

Recommendations:

Provide parallel instructions for resource group creation using Azure CLI (Bash) alongside the PowerShell example.
Explicitly mention and show Linux command-line examples where applicable, not just Windows/PowerShell.
Ensure that all included snippets (such as resource group creation) have both Windows (PowerShell) and Linux (Bash/CLI) variants, or clarify that the instructions are cross-platform.
Review included files (e.g., powershell-resource-group-create.md) to ensure Linux parity or add a note linking to Linux equivalents.
Consider reordering or presenting Windows and Linux instructions side-by-side to avoid implicit prioritization of Windows.

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 for resource group creation (via include), mentioning Windows before Linux in the OpenSSL prerequisite, and suggesting Visual Studio/Visual Studio Code (commonly associated with Windows) for authentication. There are no explicit Linux/macOS-specific instructions or examples, and the setup steps (such as creating a virtual environment) link to documentation that defaults to Windows command prompt. No Linux shell (bash) or cross-platform CLI examples are provided for resource group creation or authentication.

Recommendations:

Provide explicit Linux/macOS shell (bash) examples alongside or before PowerShell/Windows examples for resource group creation and other CLI steps.
Rephrase prerequisites to mention Linux/macOS before or alongside Windows, e.g., 'on a computer running Linux, macOS, or Windows.'
Include instructions for using cross-platform tools (e.g., Azure CLI) for all steps, not just cleanup.
Avoid suggesting Windows-centric tools (like Visual Studio) as the primary authentication method; mention cross-platform editors and tools equally.
Ensure all included snippets (such as resource group creation) have both PowerShell and bash equivalents, or use Azure CLI as the default.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation shows mild Windows bias by listing Windows before Linux in the prerequisites, referencing Windows tools (such as Visual Studio) without Linux alternatives, and not providing explicit Linux/macOS command-line examples or guidance. Some steps reference PowerShell-based includes for resource group creation, which may default to Windows-centric instructions. There are no explicit Linux shell (bash) or macOS Terminal examples, and the authentication tooling mentions Visual Studio/VS Code (primarily Windows-focused) before CLI-based authentication.

Recommendations:

Ensure all command-line instructions are provided for both Windows (PowerShell/CMD) and Linux/macOS (bash), or use cross-platform Azure CLI examples as the default.
When referencing tools for authentication, mention cross-platform options (Azure CLI, VS Code) before Windows-only tools (Visual Studio), and clarify that VS Code is available on all platforms.
In prerequisites and setup sections, list Linux/macOS alongside Windows, or use neutral phrasing (e.g., 'on your computer' instead of 'on a computer running Windows or Linux').
If includes reference PowerShell, ensure equivalent bash/CLI instructions are also linked or shown.
Explicitly state that all examples work on Linux/macOS as well as Windows, and provide troubleshooting notes for common cross-platform issues (e.g., OpenSSL installation, npm usage).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas: it provides only Windows/PowerShell-based installer instructions as an alternative to the OVA method, uses Windows-specific tools (e.g., CertUtil in Command Prompt) for security verification, and references Windows file paths and conventions. There are no Linux equivalents or examples for these steps, and Linux tooling or commands are not mentioned. The documentation assumes the user is operating from a Windows environment when interacting with the appliance or verifying files.

Recommendations:

Provide Linux-based instructions and examples alongside Windows ones, such as using sha256sum or openssl for hash verification of the OVA file.
Include a Linux shell script or manual steps for setting up the appliance on a Linux server, not just a PowerShell script.
When referencing file paths or commands, offer both Windows and Linux variants.
Explicitly mention Linux support and provide parity in troubleshooting, validation, and configuration steps.
Clarify if the PowerShell script is cross-platform (PowerShell Core) or Windows-only, and offer a bash alternative if possible.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by repeatedly referencing Windows Server, SQL Server, and related licensing and security update scenarios, without providing equivalent details or examples for Linux-based workloads. The cost and savings calculations, as well as security and management features, are described primarily in the context of Windows technologies. There are no explicit Linux examples or mentions of Linux-specific migration considerations, tools, or licensing, and Windows-specific features (such as Extended Security Updates and Azure Hybrid Benefit) are discussed in detail before or instead of Linux equivalents.

Recommendations:

Include explicit examples and cost/savings breakdowns for Linux workloads, such as common Linux distributions (e.g., Ubuntu, Red Hat, SUSE) and open-source databases (e.g., MySQL, PostgreSQL).
Describe how Azure Migrate handles Linux licensing, support status, and migration scenarios, including any unique benefits or challenges.
Mention Linux security and management options (e.g., Azure Defender for Linux, Azure Monitor for Linux VMs) alongside Windows-focused features.
Ensure that sections referencing Windows Server and SQL Server also provide parallel information for Linux servers and databases.
Add screenshots or report samples that include Linux workloads to demonstrate parity in the assessment and reporting process.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows/Azure-centric bias by exclusively referencing Azure-specific tools and workflows (Azure portal, Azure CLI, Microsoft Entra ID) for managing Grafana permissions. There are no examples or instructions for Linux-native tools, non-Azure CLI environments, or generic Grafana administration outside of the Azure ecosystem. The command-line example uses Azure CLI, which is available cross-platform but is primarily associated with Azure and Windows environments. No mention is made of Linux shell commands, native Grafana CLI, or alternative identity providers.

Recommendations:

Include examples of managing Grafana roles and permissions using the native Grafana CLI or REST API, which are platform-agnostic and commonly used in Linux environments.
Provide instructions or references for managing permissions in self-hosted Grafana (outside Azure), highlighting differences and Linux-native workflows.
Clarify that Azure CLI is cross-platform, but also suggest how to perform equivalent tasks using bash, curl, or other Linux-native tools.
Mention or link to documentation for integrating non-Microsoft identity providers, if supported, to broaden applicability beyond Microsoft Entra ID.
Consider reordering sections or adding parallel Linux/generic Grafana examples alongside Azure-specific instructions to improve parity.

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-specific instructions, tools, and screenshots before Linux equivalents. Windows examples are detailed with PowerShell commands, screenshots, and explicit tool references (e.g., diskpart, Windows Azure Guest Agent), while Linux sections are less detailed, with fewer explicit command examples and no screenshots. Linux instructions often refer users to external documentation for distribution-specific steps, and some manual steps for Linux are described only in general terms or for specific distributions (e.g., RedHat), leaving out parity for other Linux distributions.

Recommendations:

Provide Linux command-line examples for all manual steps, similar to the detailed PowerShell examples given for Windows.
Include screenshots or terminal output for key Linux steps (e.g., checking waagent status, editing network configuration files).
Present Linux and Windows instructions in parallel or side-by-side, rather than always listing Windows first.
Expand Linux instructions to cover a broader range of distributions, not just RedHat (e.g., include Ubuntu/Debian equivalents for network and initrd steps).
Reference Linux tools/utilities (e.g., systemctl, nmcli, update-initramfs) explicitly where appropriate, just as Windows tools are referenced.
Ensure that all steps described for Windows (such as agent installation verification) have clear, equivalent Linux instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows/Hyper-V environments, with all examples, tools, and instructions tailored exclusively to Windows systems. There are no references to Linux environments, tools, or migration scenarios, and all operational steps (e.g., registry edits, MMC snap-ins) are Windows-specific.

Recommendations:

Include equivalent guidance for migrating Linux-based VMs (e.g., KVM, Xen) to Azure using Azure Migrate.
Provide examples and instructions for controlling upload throughput and tuning replication performance on Linux hosts, if supported.
Mention or link to Linux migration documentation where relevant, clarifying the scope of Hyper-V (Windows) vs. Linux migrations.
If agentless migration is not supported for Linux, explicitly state this and suggest alternative approaches for Linux workloads.
Balance the order of presentation by including Linux scenarios or clearly stating that the page is Windows/Hyper-V specific in the introduction.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias by consistently listing Windows credential types and features before Linux equivalents, providing more detailed guidance for Windows scenarios, and referencing Windows-specific tools and authentication (e.g., Active Directory, DPAPI, Windows authentication for SQL Server). Linux support is often mentioned as 'not supported' or with minimal detail, and there are no Linux-specific examples or walkthroughs.

Recommendations:

Provide Linux-specific examples and walkthroughs for adding credentials, including screenshots or command-line instructions where applicable.
List Linux and Windows credential types and required permissions in parallel, rather than always listing Windows first.
Expand documentation on Linux support, including supported discovery features, limitations, and best practices.
Offer guidance for common Linux authentication scenarios (e.g., SSH key-based authentication, integration with LDAP or other directory services).
Clarify the roadmap or plans for supporting currently unsupported Linux features (e.g., SQL Server discovery, web app discovery) to set user expectations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented towards Windows environments. It references Windows-specific paths (e.g., %ProgramFiles%), tools (MinimumPrivilegedUser.exe), and patterns (command prompt navigation), with no mention of Linux equivalents or instructions for non-Windows environments. There are no examples or guidance for Linux-based SQL Server instances or how to perform these steps from a Linux system.

Recommendations:

Add explicit instructions and examples for provisioning least privileged accounts on SQL Server instances running on Linux.
Provide cross-platform command-line examples, including bash or shell commands for Linux environments.
Clarify whether the provisioning utility is available for Linux, and if not, suggest alternative approaches for Linux users (e.g., manual SQL scripts).
Replace or supplement Windows-specific paths and environment variables with Linux equivalents where applicable.
Include a section or note addressing Linux users, outlining any differences or additional steps required.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows file paths, registry keys, and tools (such as MMC snap-in and Windows registry), without providing equivalent instructions or examples for Linux environments. All examples and operational details (e.g., antivirus exclusions, bandwidth throttling) are Windows-centric, and there is no mention of Linux commands, tools, or file paths, despite the Mobility service supporting Linux servers as well.

Recommendations:

Provide Linux-specific instructions for installing and managing the Mobility service, including relevant file paths and commands (e.g., systemd service management, Linux package installation).
List antivirus exclusion paths for common Linux distributions alongside Windows paths.
Describe how to throttle upload bandwidth on Linux process servers, including configuration file locations or relevant Linux utilities.
Mention Linux equivalents for Windows tools (e.g., instead of MMC snap-in, reference CLI or config files for Linux).
Ensure that all operational guidance (such as port usage, scaling, and monitoring) includes Linux-specific details where applicable.
When referencing registry keys or Windows-specific settings, clarify if and how these apply to Linux, or provide alternative Linux instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation for the Azure Migrate appliance demonstrates a strong Windows bias. All deployment and operational instructions assume or require Windows Server (2019/2022) as the host OS for the appliance, with no mention of Linux-based deployment options. All deployment scripts and manual steps use PowerShell, and all troubleshooting and configuration references are for Windows tools (e.g., Registry Editor, Control Panel). Even in scenarios where Linux servers are discovered, the appliance itself must run on Windows. There are no Linux-based installation, management, or upgrade instructions, and Linux tooling is not addressed for any administrative tasks.

Recommendations:

Provide explicit documentation on whether the Azure Migrate appliance can be deployed on Linux hosts. If not supported, clarify this limitation early in the documentation.
If technically feasible, develop and document a Linux-based deployment option for the appliance, including equivalent shell scripts and management instructions.
For all deployment and management steps (installation, upgrades, service checks), provide Linux equivalents (e.g., bash scripts, systemd/service management, file hash verification with sha256sum, etc.) alongside Windows/PowerShell instructions.
Where Windows tools (e.g., Registry Editor, Control Panel) are referenced, offer Linux alternatives (e.g., config files, systemctl, journalctl) if/when a Linux appliance is supported.
Ensure that examples and instructions for discovering and managing Linux servers are as detailed and prominent as those for Windows servers.
Clearly state OS requirements and limitations in the prerequisites section, and consider a comparison table for Windows vs. Linux support.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by focusing on Windows-centric workloads (e.g., ASP.NET on IIS), omitting explicit Linux workload examples, and referencing Windows tools and patterns (such as IIS and Hyper-V) without mentioning Linux equivalents. There is no discussion of Linux-based web apps, databases, or migration considerations, and no Linux-specific tooling or assessment scenarios are presented.

Recommendations:

Include examples and guidance for assessing and migrating Linux-based workloads, such as Apache/Nginx web servers, MySQL/PostgreSQL databases, and Linux VMs.
Mention Linux environments (e.g., KVM, bare metal Linux servers) alongside VMware and Hyper-V in assessment scenarios.
Provide parity in migration tool recommendations for Linux workloads, such as Azure Migrate agentless/agent-based migration for Linux, or third-party Linux migration tools.
Add Linux-specific troubleshooting tips and common issues (e.g., SSH connectivity, Linux disk partitioning, OS detection nuances).
Ensure that all sections referencing Windows tools or patterns also mention Linux equivalents where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias: Windows examples and tools are often presented first, with more detailed step-by-step instructions and screenshots for Windows (e.g., WMI Control Panel configuration), while Linux instructions are more concise and sometimes lack equivalent detail or visual aids. Windows-specific tools and patterns (WMI, WinRM, Windows authentication, SQL Server) receive more attention, and some sections (like database discovery) focus almost exclusively on Windows technologies, with Linux or open-source alternatives only briefly mentioned or omitted.

Recommendations:

Ensure Linux instructions are as detailed as Windows ones, including step-by-step guides, command-line examples, and screenshots where appropriate.
Present Linux and Windows examples in parallel or alternate their order to avoid always listing Windows first.
Include Linux-native tools and authentication methods (e.g., SSH, Linux-based SQL authentication) with equal prominence.
Expand database discovery sections to cover common Linux database scenarios (e.g., PostgreSQL, MariaDB) with least-privilege setup instructions.
Where Windows-specific tools (like WMI or WinRM) are discussed, provide Linux equivalents (e.g., SSH, systemd, or other monitoring tools) and explain how to configure them for Azure Migrate.
Add troubleshooting and permission validation steps for Linux environments similar to those provided for Windows.
Review all tables and code blocks to ensure Linux and Windows examples are equally represented and easy to follow.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. All deployment and hardening instructions are focused on Windows Server, with explicit references to PowerShell scripts, Windows security baselines, and Windows-specific tools (such as the Security Compliance Toolkit and DPAPI). There are no equivalent instructions, tools, or examples provided for deploying or securing the appliance on Linux systems, nor is there mention of Linux-based installation or hardening procedures. Even when Linux servers are referenced (e.g., port 22), the appliance itself is always assumed to be Windows-based.

Recommendations:

Provide explicit guidance for deploying and securing the Azure Migrate appliance on Linux-based systems, if supported.
Include Linux command-line examples (e.g., Bash scripts) alongside PowerShell for installation and configuration.
Reference Linux security hardening resources (e.g., CIS Benchmarks, SELinux, AppArmor) in the OS image hardening section.
Describe how credentials are protected on Linux (e.g., using keyrings, encrypted files) if Linux appliances are supported.
Ensure that all tooling and automation instructions are cross-platform or clearly indicate platform limitations.
If the appliance is Windows-only, state this explicitly at the start of the documentation to set expectations.

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 almost exclusively reference PowerShell scripts and Windows tools (e.g., certificate manager, group policy editor, Windows Update). Troubleshooting and certificate management steps are described only for Windows environments, with screenshots and instructions specific to Windows UI. There are no Linux-specific deployment, management, or troubleshooting examples, and Linux tooling is not mentioned except in passing (credentials).

Recommendations:

Provide equivalent Linux-based deployment instructions, including shell script alternatives to PowerShell where possible.
Include Linux-specific troubleshooting steps for certificate management, such as using OpenSSL or Linux certificate stores.
Add examples and screenshots for managing the appliance on Linux-based systems (e.g., Ubuntu, CentOS).
Clarify whether the appliance can be run on Linux hosts, and if not, explicitly state this limitation.
When discussing credential types and agent support, include explicit instructions for Linux server discovery and management.
Ensure that all UI and command-line instructions are provided for both Windows and Linux environments, or clearly indicate OS-specific requirements.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows tools and patterns first or exclusively in several places. Agent installation and automation examples mention PowerShell scripts and Microsoft Configuration Manager, with no explicit Linux command-line or automation examples. The Microsoft Monitoring Agent (MMA) is linked primarily to its Windows documentation, and Linux support is only mentioned as a secondary note. There are no Linux-specific examples or guidance for agent installation, automation, or troubleshooting.

Recommendations:

Provide explicit Linux command-line examples for agent installation and automation (e.g., bash scripts, systemd service setup).
Mention Linux tools (such as Ansible, shell scripts, or native package managers) alongside Windows tools like PowerShell and Configuration Manager.
Ensure that links to agent documentation include both Windows and Linux installation guides, and present them in parallel.
Include troubleshooting steps and prerequisites for Linux environments, not just Windows.
Balance the order of presentation so that Linux and Windows are treated equally, rather than listing Windows first or exclusively.

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 virtualization platform) VMs to Azure, with all examples, instructions, and tooling references specific to Windows environments. There are no Linux or cross-platform examples, and all operational steps assume the use of Windows tools and patterns (e.g., Hyper-V Replication provider, Recovery Services agent, Windows Server licensing). Linux environments, tools, or migration scenarios are not mentioned or addressed.

Recommendations:

Include parallel documentation or references for migrating Linux-based virtual machines (e.g., KVM, Xen, or other hypervisors) to Azure using Private Link.
Provide examples and instructions for agent installation, DNS configuration, and network validation on Linux systems.
Mention and link to equivalent migration guides for VMware and Linux-based hypervisors, if available.
Clarify in the introduction that this guide is specific to Hyper-V/Windows environments and direct users to Linux/VMware migration documentation as appropriate.
Where possible, use cross-platform terminology and highlight any steps that are Windows-specific, offering Linux alternatives or noting limitations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While it covers both Windows and Linux migration scenarios in general descriptions and OS support tables, practical examples and tooling guidance are almost exclusively Windows-centric. Powershell and Windows-specific tools are used for bandwidth throttling, with no Linux equivalents provided. Windows migration scenarios, features, and upgrades are often discussed first or in more detail, and some advanced features (like in-place OS upgrade during migration) are only available for Windows, with Linux explicitly excluded. There are no Linux command-line or tooling examples for common administrative tasks, and Linux users are left to infer or research their own solutions.

Recommendations:

Provide Linux-equivalent examples for operational tasks, such as bandwidth throttling (e.g., using tc, wondershaper, or firewalld on Linux appliances).
When showing Powershell or Windows command-line examples, include a corresponding Linux shell (bash) example if the appliance can run on Linux, or clarify if only Windows is supported.
Balance the order of presentation: alternate or parallelize Windows and Linux examples and feature descriptions, rather than listing Windows first or exclusively.
Document any limitations or differences for Linux-based appliances or migrations, and provide links to Linux-specific guidance where available.
If certain features (such as in-place OS upgrade during migration) are Windows-only, explicitly state this and provide a roadmap or workaround for Linux users.
Add troubleshooting and operational guidance for common Linux distributions in parity with Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page, while highlighting improved Linux support, demonstrates Windows bias by mandating the use of Windows Server 2019 as the replication appliance and not mentioning any Linux-based alternatives. There are no Linux-specific examples or guidance for Linux administrators, and Windows tooling is presented as the default and only option.

Recommendations:

Provide information on whether a Linux-based replication appliance is supported or planned, or clarify why only Windows Server is used.
Include step-by-step examples or guidance for Linux administrators, especially for common migration scenarios.
Mention any Linux-native tools or scripts that can be used in conjunction with the migration stack, or explicitly state if none are available.
Ensure parity in documentation structure by presenting Linux and Windows options side by side where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first and Windows-heavy bias. Windows operating systems are listed in detail and always before Linux, with extensive version-specific guidance and support notes. Linux is mentioned only generically, with a single reference to a link for supported distributions and no detailed breakdown or examples. There are no Linux-specific examples, troubleshooting, or migration caveats, and the documentation does not provide parity in OS-level detail or guidance for Linux environments.

Recommendations:

Provide a detailed table of supported Linux distributions and versions, similar to the Windows OS table, including migration caveats and support notes.
Include Linux-specific examples, such as how to collect kernel version information, common migration issues, or best practices for Linux VMs.
List Linux operating systems before or alongside Windows in all tables and lists to avoid the perception of Windows primacy.
Add troubleshooting guidance for Linux VMs, such as handling unsupported distributions, kernel modules, or disk/boot compatibility.
Ensure all instructions and recommendations (e.g., for security readiness, disk sizing, and network configuration) explicitly address both Windows and Linux scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific technologies (e.g., IIS, Windows Server Failover Clusters, Windows-specific best practices links) and omitting Linux-specific examples or guidance. References to high availability, disaster recovery, and migration scenarios are framed around Windows tools and patterns, with no mention of Linux-based SQL Server deployments or their migration nuances. Where links to best practices are provided, they point to Windows-specific documentation. There are no Linux or cross-platform PowerShell/Bash/CLI examples, and the documentation assumes a Windows-centric environment throughout.

Recommendations:

Add explicit guidance and examples for assessing and migrating SQL Server instances running on Linux (including supported distributions).
Include links to best practices for SQL Server on Linux in Azure, not just Windows.
When discussing high availability and disaster recovery, mention Linux-based clustering and failover options (e.g., Pacemaker, Linux witness options) alongside Windows Server Failover Clusters.
Provide parity in migration steps, screenshots, and configuration options for both Windows and Linux SQL Server sources.
Where PowerShell or Windows-specific tools are referenced, also provide equivalent Bash/CLI/Linux-native commands and workflows.
Clarify in each section whether the guidance applies to both Windows and Linux SQL Server deployments, or specify differences as needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation for the Azure Migrate replication appliance demonstrates a strong Windows bias. The appliance is described as running exclusively on Windows Server (2016 or 2012 R2), with no mention of Linux support or examples. All instructions, requirements, and file paths (e.g., C:\Temp\ASRSetup) are Windows-specific. Windows tools and settings (such as Group Policies, IIS, .NET Framework, and Windows Server roles) are referenced exclusively, and there are no Linux equivalents or guidance for Linux-based deployments. MySQL installation instructions are tailored to Windows (MSI installer, Windows file paths).

Recommendations:

Explicitly state whether Linux-based replication appliances are supported or not. If not, clarify this early in the documentation.
If Linux support is available or planned, provide equivalent instructions, requirements, and examples for Linux deployments (e.g., supported distributions, package installation commands, file paths, service management).
For MySQL installation, include Linux installation steps (e.g., using apt, yum, or other package managers) and Linux file paths.
Reference Linux equivalents for configuration (e.g., SELinux/AppArmor, systemd services, firewall configuration) where Windows-specific settings are discussed.
Where only Windows is supported, provide a rationale for the lack of Linux support and suggest alternatives for Linux users if possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by focusing primarily on ASP.NET web apps running on IIS (a Windows technology), mentioning Windows-based SKUs (I1, P1v2, P1v3), and linking to Windows-specific App Service pricing. There are no explicit examples or guidance for Linux-based web apps (such as those running on Apache, Nginx, or Java on Linux), nor are Linux migration scenarios or tools discussed. The documentation implicitly assumes a Windows/IIS environment as the default for web app migration.

Recommendations:

Include explicit examples and guidance for migrating Linux-based web apps (e.g., Java apps on Tomcat/Apache/Nginx on Linux).
Mention Linux App Service plans and provide links to Linux-specific App Service pricing and documentation.
Clarify that Azure App Service supports both Windows and Linux, and provide parity in assessment steps and recommendations for both platforms.
Add references to Linux migration tools or patterns where applicable, and ensure that Linux scenarios are not omitted.
Avoid using Windows/IIS as the default or only example; present both Windows and Linux scenarios side by side where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by focusing heavily on Windows Server, SQL Server, Hyper-V, and Microsoft management tools (e.g., System Center, Windows ESU). Linux is only briefly mentioned in passing (e.g., in license amortization and support), with no detailed examples, cost breakdowns, or migration scenarios specific to Linux workloads. There are no Linux-specific tools, patterns, or parity in the discussion of migration, management, or security. All detailed examples, cost models, and management scenarios are centered on Windows environments.

Recommendations:

Include explicit examples and cost breakdowns for Linux workloads, such as common Linux distributions and open-source database/application stacks.
Discuss Linux-specific migration scenarios, including considerations for licensing, support, and open-source management tools.
Mention and provide parity for Linux management and monitoring tools (e.g., integration with Azure Monitor for Linux, Linux patch management, open-source backup solutions).
Clarify how the Azure Migrate appliance discovers and assesses Linux servers, and provide links to Linux-specific guidance.
Ensure that Linux is referenced alongside Windows in all relevant tables, cost models, and migration strategies, not just as an afterthought.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by specifically highlighting Windows Server scenarios (such as end-of-support and OS upgrade), mentioning Windows-specific tools and features (like the Custom Script Extension for Windows), and omitting equivalent Linux migration or upgrade workflows. There are no Linux-specific examples, recommendations, or parity in migration/upgrade tooling discussed, despite mentioning Linux in passing (e.g., Azure Hybrid Benefit for Linux subscriptions).

Recommendations:

Include explicit Linux migration scenarios, such as guidance for migrating Linux VMs, handling end-of-support Linux distributions, and any Azure Migrate features specific to Linux.
Provide examples or references for Linux OS upgrades during migration, or clarify if such functionality is not available.
When discussing tools like the Custom Script Extension, mention both Windows and Linux variants (e.g., link to both Windows and Linux documentation for custom scripts).
Balance references to Windows and Linux in tables and examples (e.g., when filtering for end-of-support OS, include major Linux distributions that are EOL).
Add Linux-specific troubleshooting, best practices, and links to relevant Azure Migrate documentation for Linux workloads.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows environments, specifically requiring Windows Server, IIS, and PowerShell for web app migration. Linux servers are explicitly not supported, and there are no examples or guidance for Linux-based web apps or tools. All migration requirements and instructions are tailored to Windows-only scenarios.

Recommendations:

Add support and documentation for migrating Linux-based web apps to Azure App Service, if technically feasible.
Include equivalent Linux migration tools and workflows (e.g., Bash scripts, Linux web servers like Apache/Nginx) alongside Windows/PowerShell examples.
Clearly state future plans or alternatives for Linux users if support is not currently available.
Provide parity in documentation structure and detail for both Windows and Linux scenarios to ensure inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-centric workloads (e.g., Hyper-V, Windows-hosted web apps), mentioning Windows tools and environments (such as ASP.NET and SQL Server) without equivalent Linux examples, and omitting explicit guidance or examples for Linux servers, databases, or web applications. Linux migration scenarios and tools are not addressed, and the only web app migration example is for 'Web apps hosted on Windows in a VMware environment.'

Recommendations:

Add explicit examples and guidance for migrating Linux-based servers (e.g., Ubuntu, CentOS) and workloads, including discovery, assessment, and migration steps.
Include Linux database migration scenarios (e.g., MySQL, PostgreSQL) and reference relevant tools or Azure services.
Provide examples for migrating Linux-hosted web applications (e.g., Apache, Nginx, Node.js, Python) to Azure App Service or Azure Kubernetes Service.
Ensure that tables and feature lists mention both Windows and Linux workloads where applicable, and avoid language that implies Windows is the default or only supported platform.
Reference Linux-compatible tools and scripts, and provide parity in documentation for both Windows and Linux environments.

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 Server and related tools in requirements and examples. Windows-specific tools and patterns (e.g., Windows Firewall, RDP, .NET Framework) are mentioned explicitly and in detail, while Linux equivalents are either missing, less detailed, or only referenced generically. Instructions for post-migration connectivity are more comprehensive for Windows (with step-by-step firewall and RDP guidance), whereas Linux instructions are briefer and lack equivalent detail (e.g., no mention of SELinux, UFW/iptables, or SSH hardening). The documentation also lists Windows URLs and services (e.g., time.windows.com) before Linux-relevant alternatives, and does not provide Linux-specific troubleshooting or preparation steps.

Recommendations:

Provide Linux-specific examples and instructions alongside Windows ones, such as how to configure SSH, firewall (e.g., UFW, firewalld, iptables), and SELinux/AppArmor settings for migration.
List Linux and Windows requirements in parallel, rather than always listing Windows first.
Include Linux-specific troubleshooting steps and preparation guidance, similar to the detailed steps given for Windows (e.g., integration services, SAN policy).
Reference Linux time synchronization sources (e.g., ntp.ubuntu.com, pool.ntp.org) in addition to or instead of time.windows.com.
Where Windows tools or patterns are mentioned (e.g., .NET Framework, Windows Firewall), provide Linux equivalents or clarify when they are not required for Linux hosts.
Ensure that all examples, especially for connectivity and post-migration steps, are equally detailed for both Windows and Linux VMs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a strong Windows bias, as expected for Hyper-V scenarios, but with several areas where Linux parity is lacking or Linux is treated as an afterthought. Windows tools and patterns (e.g., PowerShell remoting, WinRM, WMI) are mentioned first and in detail, with Linux alternatives (SSH, Linux commands) often appearing later or with less detail. SQL Server and web app discovery are either unsupported or only partially supported for Linux. Example scripts and detailed instructions are provided only for Windows authentication and SQL Server, with no equivalent Linux database or web server examples. Some features (e.g., SQL Server instance discovery, ASP.NET web apps) are not supported for Linux at all.

Recommendations:

Where possible, provide Linux-first or at least Linux-equal examples and instructions, especially for discovery, permissions, and connectivity (e.g., sample SSH configuration, Linux user setup).
Explicitly state limitations for Linux support up front and provide guidance or workarounds if available.
For SQL Server and web app discovery, clarify Linux support status and, if unsupported, suggest alternative approaches or roadmap.
Include Linux command-line examples and configuration steps alongside PowerShell/Windows instructions (e.g., for enabling required ports, setting up user permissions).
Ensure that all tables and requirement lists mention Linux and Windows in parallel, not just as an afterthought.
If a feature is Windows-only, explain why and provide links to relevant Linux migration/assessment tools if possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias in several areas. PowerShell cmdlets (e.g., New-NetQosPolicy) are used exclusively for bandwidth throttling examples, and the configuration file paths (e.g., C:\ProgramData\Microsoft Azure\Config) are Windows-specific. There are no Linux or cross-platform equivalents provided for these operations, and the documentation assumes the Azure Migrate appliance is running on Windows without mentioning Linux deployment or management options. This may hinder Linux users or those deploying the appliance on non-Windows platforms.

Recommendations:

Provide equivalent Linux-based examples for bandwidth throttling, such as using 'tc' or 'iptables' for traffic shaping.
Document the location and format of configuration files on Linux-based appliances, if supported (e.g., /var/lib/ or /etc/ paths).
Clarify whether the Azure Migrate appliance can be deployed on Linux, and if so, provide Linux-specific instructions for management tasks (e.g., restarting services, editing config files).
Where PowerShell or Windows tools are mentioned, add parallel Linux shell commands or scripts.
Adopt more neutral language that does not assume a Windows environment by default, and explicitly call out platform-specific steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting Windows-specific tools, requirements, and connection instructions before or in more detail than their Linux equivalents. Windows terminology (such as BitLocker, Windows Firewall, RDP) is used extensively, and Linux instructions are less detailed or appear after Windows instructions. There is also a lack of parity in troubleshooting and configuration guidance for Linux systems.

Recommendations:

Provide Linux connection instructions with equal detail and prominence as Windows (e.g., include firewall configuration commands for common Linux distributions, not just a generic SSH mention).
When listing requirements or steps, alternate the order or present Windows and Linux instructions side-by-side to avoid always listing Windows first.
Include examples for both Windows and Linux for tasks like enabling remote access, configuring firewalls, and preparing disks.
Mention Linux-specific tools and scenarios (e.g., SELinux, iptables, firewalld, LUKS encryption) where Windows-specific tools (like BitLocker or Windows Firewall) are referenced.
Expand on Linux filesystem and bootloader support, and provide troubleshooting steps for common Linux migration issues.
Ensure parity in post-migration steps for both Windows and Linux, such as guidance for fixing boot issues, network configuration, and user access.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell and Windows-centric tools are referenced for appliance deployment and replication configuration, with no equivalent Linux CLI or automation examples. Windows requirements and instructions are often listed before Linux, and some sections (such as appliance OS requirements) assume or require Windows Server. There is a lack of Linux-native deployment or management options, and Linux guidance is less detailed or appears as an afterthought.

Recommendations:

Provide Linux CLI (e.g., Bash, shell script) examples for deploying and managing the Azure Migrate appliance, alongside or before PowerShell examples.
Offer guidance for deploying the appliance from Linux workstations or automation pipelines, not just from Windows/PowerShell environments.
Where possible, support and document Linux-based appliances or provide instructions for running the appliance on Linux VMs.
Ensure that Linux requirements and instructions are presented with equal prominence and detail as Windows, and avoid always listing Windows first.
Include troubleshooting and preparation steps for Linux VMs that are as comprehensive as those for Windows (e.g., firewall, SSH, agent installation).
Clarify any limitations or differences for Linux users up front, and provide workarounds or alternatives where Windows-only tooling is referenced.

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 technologies (PowerShell, WMI, WinRM) are mentioned more prominently and with more detail than their Linux equivalents. Windows requirements and examples (such as SQL Server discovery and authentication) are provided in depth, while Linux support is often limited, less detailed, or explicitly not supported (e.g., SQL Server discovery on Linux). Where both platforms are supported, Windows is usually listed first and with more comprehensive instructions. There are also missing Linux-specific examples, particularly for tasks like SQL Server discovery and web app discovery.

Recommendations:

Provide equivalent Linux-focused examples and instructions wherever Windows examples are given, especially for authentication, credential setup, and agent installation.
When listing supported operating systems or requirements, alternate the order or group Windows and Linux together to avoid always listing Windows first.
Expand documentation for Linux-specific tools and patterns (e.g., Bash, SSH, Linux package requirements) to match the detail given for Windows (e.g., PowerShell, WMI).
Where a feature is not supported on Linux (e.g., SQL Server discovery), clearly state the limitation and, if possible, provide workarounds or roadmap information.
Include Linux-specific troubleshooting, configuration, and permission guidance (e.g., sudoers configuration, SELinux/AppArmor considerations, systemd service requirements) alongside Windows guidance.
For web app discovery, provide parity in instructions and examples for Linux-based stacks (e.g., Apache, Nginx, Tomcat) similar to the detail for IIS/ASP.NET on Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by consistently mentioning Windows tools (WinRM, PowerShell) before Linux equivalents, providing detailed Windows-specific instructions (such as running 'winrm qc'), and referencing Windows authentication and permissions patterns. Linux instructions are present but less detailed, and Linux-specific tooling or command examples are largely absent. There are also references to using PowerShell for Azure tasks without equivalent Linux/CLI alternatives.

Recommendations:

Provide Linux/Unix command examples (e.g., SSH configuration, firewall rules) with equal detail and prominence as Windows examples.
When referencing Azure service principal creation, include Azure CLI and Bash examples alongside PowerShell and portal instructions.
Avoid always listing Windows steps first; alternate or present both OS instructions in parallel where possible.
Clarify Linux authentication and permissions requirements with concrete examples (e.g., sudo usage, SSH key setup).
Include troubleshooting steps and error messages specific to Linux environments, not just Windows/WinRM.
Mention and link to Linux-specific documentation or tools where relevant, ensuring parity in guidance.

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 server preparation steps and examples before Linux, providing detailed PowerShell and Windows command-line instructions (with screenshots), and referencing Windows-specific tools (e.g., diskpart, registry, PowerShell) without equivalent Linux command-line examples or screenshots. Linux instructions are less detailed, with fewer concrete command examples and no screenshots, and some steps refer users to external documentation for specifics.

Recommendations:

Alternate the order of Windows and Linux sections or present both in parallel to avoid a Windows-first impression.
Provide Linux command-line examples and screenshots for key steps (e.g., checking/setting DHCP, verifying agent installation), similar to the detailed Windows examples.
Include Linux-specific troubleshooting tips and manual validation steps, not just references to external documentation.
Where Windows tools (e.g., diskpart, PowerShell) are shown, provide direct Linux equivalents (e.g., nmcli, systemctl, ip, etc.) with commands and output.
Ensure that all steps described for Windows (such as verifying agent installation, checking service status, or modifying boot/network settings) have clear, actionable Linux equivalents.
Add a summary table comparing manual steps for Windows and Linux to highlight parity and differences.

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-specific instructions, tools, and examples before their Linux equivalents. Windows tools (such as PowerShell, diskpart, and Windows Firewall) are mentioned explicitly, while Linux instructions are less detailed or lack equivalent command-line examples. The 'Prepare to connect after migration' section provides step-by-step instructions for Windows (including PowerShell usage) but offers only brief, high-level guidance for Linux. Additionally, the documentation provides more granular troubleshooting and configuration steps for Windows than for Linux.

Recommendations:

Provide Linux command-line examples (e.g., for enabling SSH, updating firewall rules with iptables/firewalld/ufw, checking required services, and verifying agent installation) alongside Windows examples.
Present Windows and Linux instructions in parallel or in a more balanced order, rather than consistently listing Windows first.
Include Linux-specific troubleshooting steps and configuration details (such as how to check for pending updates, or how to enable serial console access) similar to the Windows sections.
Reference common Linux tools (e.g., systemctl, iptables, ufw, firewalld) where Windows tools like PowerShell or diskpart are mentioned.
Expand the 'Prepare to connect with Linux Azure VMs' section with detailed steps and links, matching the depth provided for Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-centric tools (e.g., MAP Toolkit), mentioning Windows migration scenarios, and omitting Linux-specific examples or tools. Scripting skills are listed in a cross-platform way (Bash, PowerShell, Python), but concrete migration examples, tool references, and assessment tools are Windows-focused. There are no Linux-specific migration scenarios, tools, or examples provided.

Recommendations:

Include references to Linux migration tools or scenarios, such as guidance for migrating Linux servers or workloads.
Mention Linux assessment and planning tools (e.g., Azure Migrate's support for Linux, or third-party Linux migration tools) alongside Windows tools like MAP Toolkit.
Provide example migration workflows or FAQs specifically for Linux environments, including common challenges and solutions.
Ensure that when listing skills, Linux administration and scripting (e.g., shell scripting, Linux networking) are explicitly mentioned.
Balance tool and scenario descriptions so that Linux and Windows are treated with parity, or at least clarify cross-platform support where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Hyper-V environments, which are exclusive to Windows. All examples, instructions, and tool references are centered around Hyper-V and Windows-based workflows, with no mention of Linux-based hypervisors (such as KVM or Xen), nor any Linux-specific instructions or parity guidance. The Azure Migrate appliance is only described as a Hyper-V VM, and there are no Linux or cross-platform alternatives or examples provided.

Recommendations:

Include parallel documentation or references for assessing Linux-based virtualization environments (e.g., KVM, Xen, VMware on Linux).
Provide examples or links for deploying the Azure Migrate appliance on Linux-based hypervisors, if supported.
Explicitly state if the described process is only applicable to Windows/Hyper-V, and provide guidance for Linux users or link to relevant Linux documentation.
Add a comparison table or section outlining differences and supported features between Windows/Hyper-V and Linux-based environments in Azure Migrate.
Ensure that future documentation includes Linux command-line examples or workflows where applicable, not just Windows/Hyper-V scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by specifying that the Azure Migrate appliance must be deployed on a Windows server, with no mention of Linux support or alternatives. There are no Linux-specific instructions, examples, or considerations, and Windows is the only platform discussed for the on-premises appliance. This may give the impression that Linux environments are not supported or are an afterthought.

Recommendations:

Explicitly state whether the Azure Migrate appliance supports Linux hosts, and if not, clarify this limitation.
If Linux support exists, provide parallel instructions for deploying the appliance on Linux servers, including prerequisites and setup steps.
Include Linux-specific considerations or troubleshooting steps for heterogeneous environments.
When mentioning deployment requirements, list both Windows and Linux options (if available), or clearly explain the rationale for Windows-only support.
Add examples or references for assessing Linux physical servers, including any differences in process or requirements.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits 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-specific instructions, tools, or file paths, and all operational guidance assumes a Windows environment.

Recommendations:

Include equivalent instructions and file paths for Linux-based Azure Migrate appliances, if supported (e.g., /home/public/Desktop/DiagnosticsReport or similar).
Clarify whether the Azure Migrate appliance is only supported on Windows, or provide parity documentation for Linux deployments if available.
Mention Linux-specific considerations for time sync, file permissions, and agent/service management.
Provide screenshots or command-line examples for Linux environments (e.g., using systemctl, journalctl, or Linux file explorers).
Explicitly state OS requirements and supported platforms at the beginning of the documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows environments by providing migration automation and command-line examples exclusively with Azure PowerShell, without mentioning or linking to equivalent Azure CLI or Linux-native tooling. There are no Linux-specific instructions or examples, and the use of PowerShell is assumed for automation, which may not be familiar or available to Linux users.

Recommendations:

Include Azure CLI examples alongside or in place of Azure PowerShell examples, especially for automation and command-line migration steps.
Explicitly mention that migration steps can be performed from Linux or macOS environments, and provide relevant instructions.
Where PowerShell is referenced, add notes or links to documentation on using Azure CLI or Bash scripts for users on non-Windows platforms.
Ensure that any downloadable tools or scripts are cross-platform or provide alternatives for Linux users.
Review linked tutorials to ensure Linux parity and update this overview page to reflect that parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing only Windows file paths (e.g., C:\ProgramData\...), using Windows-specific navigation instructions (File Explorer, 'Hidden items'), and omitting equivalent Linux instructions or file paths. There are no examples or guidance for users running the App Containerization tool or accessing artifacts on Linux systems, despite mentioning Linux deployments in the 'Next steps' section. The focus on Windows tools and patterns may hinder Linux users from following the tutorial effectively.

Recommendations:

Include Linux file paths and navigation instructions alongside Windows examples (e.g., /var/lib/azure-migrate-app-containerization or similar).
Provide guidance for accessing hidden directories and files on Linux (e.g., using ls -a or similar commands).
Explicitly state whether the Azure Migrate App Containerization tool is supported on Linux, and if so, provide Linux-specific steps for locating artifacts.
Balance the order of presentation by mentioning Linux and Windows artifact locations together, or in parallel sections.
Where screenshots or UI instructions are given (e.g., File Explorer), offer Linux equivalents (e.g., Nautilus, command line).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. Troubleshooting steps and examples often reference Windows tools, commands, and patterns first or exclusively (e.g., Control Panel, admin command prompt, PowerShell, Notepad, Windows file paths, WMI, WinRM, registry edits). Linux examples are sometimes present, but are less detailed, appear later, or are missing in some sections. Some remediation steps are only described for Windows, with Linux equivalents omitted or less emphasized.

Recommendations:

For every troubleshooting step involving Windows-specific tools (e.g., Control Panel, Notepad, PowerShell), provide equivalent Linux commands or GUI steps where applicable.
When giving command-line examples, present both Windows and Linux commands side-by-side or in parallel tabs, not just in separate sections or as an afterthought.
Avoid assuming the appliance or troubleshooting host is always Windows; clarify when steps are OS-specific.
For file edits (e.g., hosts file), include Linux file paths and editing instructions (e.g., /etc/hosts with nano or vi).
For time synchronization, provide Linux commands (e.g., timedatectl, ntpdate) alongside Windows w32tm commands.
For service management (e.g., restarting services), include Linux systemctl/service commands as well as Windows net stop/start.
Ensure all error scenarios (e.g., connectivity, authentication, permissions) have both Windows and Linux remediation steps where relevant.
Review for any missing Linux-specific troubleshooting (e.g., SELinux, firewall-cmd, system logs) and add as needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias primarily by referencing Windows-specific technologies (e.g., Hyper-V, Windows licensing), mentioning Windows scenarios before Linux ones, and omitting Linux-specific troubleshooting examples or considerations. There is a lack of parity in details for Linux environments, especially regarding licensing, performance data collection, and troubleshooting steps.

Recommendations:

Include explicit troubleshooting steps and examples for Linux servers and distributions, especially in sections discussing performance data collection and assessment confidence.
Address Linux licensing considerations in cost assessments, or clearly state the current limitations and provide guidance for Linux users.
Balance the order of presentation by alternating or grouping Windows and Linux scenarios, rather than consistently mentioning Windows/Hyper-V first.
Provide Linux-specific guidance for common issues (e.g., missing performance counters, network adapter discovery) and reference relevant Linux tools or commands.
Where Windows tools or patterns are mentioned (such as Hyper-V or Windows licensing), add equivalent Linux context or note if a feature is not applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a noticeable Windows bias. Troubleshooting steps, error remediations, and validation commands are predominantly presented using Windows tools (PowerShell, WMI, Windows environment variables, IIS), with detailed, step-by-step instructions for Windows scenarios. Linux is mentioned, but Linux-specific troubleshooting commands and examples are sparse or missing. Where Linux is referenced, it is often as an afterthought or in a secondary position to Windows. Several error codes and their remediations are Windows-centric, and Linux troubleshooting is not given equal depth or clarity.

Recommendations:

For every PowerShell or Windows-specific command or remediation, provide an equivalent Linux shell (bash) command or procedure where applicable.
Include Linux-specific troubleshooting steps for common errors (e.g., how to check SSH connectivity, required packages, permissions, or logs on Linux).
When describing prerequisites or port requirements, present Linux and Windows information in parallel, not with Windows first.
Expand error tables to include Linux-specific causes and actions, not just Windows (e.g., for errors involving PowerShell, also describe what happens on Linux and what to check).
For validation and mitigation verification, provide Linux-native commands (e.g., using SSH, systemctl, journalctl, etc.) alongside PowerShell.
For web app discovery, mention and provide guidance for common Linux web servers (Apache, Nginx) if supported, or clearly state if only IIS/Windows is supported.
Review all examples and ensure Linux is treated as a first-class platform, with equal detail and clarity as Windows.

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 protocols (WinRM, WMI, PowerShell cmdlets) are mentioned explicitly and often before their Linux equivalents. Troubleshooting steps and error codes reference Windows technologies in detail, while Linux guidance is less specific or missing. For example, adding IPs to WinRM TrustedHosts is described, but no equivalent SSH configuration for Linux is provided. Several error codes and fixes focus on Windows (e.g., WMI, application pools, ISAPI filters) with little or no Linux context or examples.

Recommendations:

Provide equivalent Linux troubleshooting steps and examples wherever Windows-specific instructions are given (e.g., SSH configuration, sudoers, firewall rules).
When mentioning Windows tools or protocols (WinRM, WMI), also mention the Linux equivalents (SSH, relevant Linux services or commands) and provide parallel instructions.
Avoid listing Windows steps or tools first by default; alternate or present both Windows and Linux guidance together.
For error codes and scenarios that are Windows-specific (e.g., WMI, application pools), clarify if there are Linux equivalents or explicitly state that the issue is Windows-only.
Include Linux-specific error codes, troubleshooting steps, and common issues to ensure parity.
Where PowerShell or Windows cmdlets are referenced, provide corresponding Bash or Linux command-line examples where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments, with all troubleshooting steps, command-line examples, and tool references assuming the Azure Migrate appliance is running on Windows. Only PowerShell, Windows command prompt, and Windows-specific tools (e.g., services.msc, MMC snap-in, Windows hosts file path) are mentioned. There are no examples or instructions for performing equivalent tasks on Linux-based appliances, nor is there any mention of Linux shell commands or tools. This creates a bias that may exclude users running the appliance on Linux or those more comfortable with Linux tooling.

Recommendations:

Provide equivalent Linux shell (bash) commands for all PowerShell and Windows command prompt examples, such as using 'curl', 'nc', or 'telnet' for connectivity tests.
Include instructions for managing services on Linux (e.g., using 'systemctl' or 'service' commands) alongside Windows service management steps.
Reference Linux file paths and hosts file locations (e.g., /etc/hosts) when discussing DNS resolution and static host entries.
Clarify whether the Azure Migrate appliance is only supported on Windows, or if Linux-based appliances are also supported; if so, ensure parity in documentation.
Mention cross-platform tools where possible, or provide links to platform-specific documentation for both Windows and Linux.
Add screenshots or terminal output examples from Linux environments where applicable.

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 tools and PowerShell commands are frequently mentioned first or exclusively, with Linux equivalents sometimes missing or less detailed. Troubleshooting steps and error remediations often focus on Windows-specific tools (e.g., PowerShell, WMI, Registry Editor), and Windows-centric terminology and instructions are more comprehensive. Linux guidance, where present, is sometimes less detailed or appears after Windows instructions.

Recommendations:

Ensure Linux troubleshooting steps are as detailed and prominent as Windows steps, including explicit Linux command examples and error resolutions.
Where PowerShell or Windows-specific tools are referenced, provide equivalent Linux commands (e.g., bash, systemctl, journalctl) and clarify when steps differ between OSes.
Avoid listing Windows instructions before Linux ones by default; consider parallel structure (Windows and Linux side-by-side) or alternating order.
For error codes and remediation tables, ensure Linux-specific errors and solutions are equally represented and not grouped as afterthoughts.
Where registry edits or WMI/PowerShell steps are given for Windows, provide corresponding Linux configuration file or command-line steps (e.g., editing /etc files, using systemctl, etc.) where applicable.
Expand Linux agent and dependency troubleshooting sections to match the depth and clarity of Windows sections, including links to relevant Linux documentation.
Review all examples and ensure that for every Windows-centric example, a Linux equivalent is provided, unless the feature is truly Windows-only (in which case, state this explicitly).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing appliance-side instructions exclusively for Windows environments (e.g., using Remote Desktop, referencing Windows file paths, and using PowerShell commands to restart services). There are no equivalent instructions or examples for Linux-based appliances, nor is there any mention of how to perform these steps on Linux. This may hinder users operating the Azure Migrate appliance on Linux or in mixed environments.

Recommendations:

Provide equivalent instructions for Linux-based appliances, including file paths (e.g., /etc or /var locations), service management commands (e.g., systemctl or service), and text editors (e.g., nano or vi).
When referencing remote access, mention SSH or console access for Linux in addition to Remote Desktop for Windows.
Include both PowerShell and Bash (or shell) command examples for service restarts and file editing.
Clearly state whether the Azure Migrate appliance is only supported on Windows, or if Linux is supported, and provide parity in documentation.
Avoid assuming the use of Windows tools and patterns (e.g., %programdata%, PowerShell) as the default; always provide cross-platform alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively providing PowerShell-based instructions for interacting with Azure resources (steps 4-8), including the use of ARMClient, a tool distributed as a Windows zip file. There are no equivalent instructions or examples for Linux or macOS users, nor are cross-platform CLI alternatives (such as Azure CLI) mentioned. The documentation assumes the user is on a Windows workstation and does not address Linux environments.

Recommendations:

Provide equivalent Linux/macOS instructions for finding the Principal ID, including commands using Azure CLI (az) or bash.
Mention and demonstrate cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools like ARMClient.
Clarify that PowerShell steps are for Windows, and offer alternative steps for Linux/macOS users.
Ensure screenshots and examples are not exclusively from Windows environments.
Review all troubleshooting steps to ensure they are applicable and accessible for users on non-Windows platforms.

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) in a Windows context (e.g., 'c:\ >nslookup ...'), referencing PowerShell-specific tools (Test-NetConnection), and using Windows terminology (editing the 'hosts file' on the 'on-premises appliance') without offering equivalent Linux or cross-platform instructions. There are no explicit Linux/Bash examples or mentions of Linux tools for network troubleshooting, and the default context for command-line operations is Windows.

Recommendations:

Provide Linux/Bash equivalents for all command-line examples (e.g., show both 'nslookup' and 'dig' commands, and show Linux shell prompts like '$').
Include instructions for editing the hosts file on Linux systems (e.g., '/etc/hosts') alongside Windows instructions.
For PowerShell-specific tools like 'Test-NetConnection', offer cross-platform alternatives such as 'telnet', 'nc' (netcat), or 'curl' for port testing on Linux.
Use neutral or cross-platform language when referring to the command line or appliance OS (e.g., 'on the command line' instead of 'on the on-premises appliance').
Add screenshots or terminal outputs from Linux environments where appropriate.
Explicitly state that the troubleshooting steps apply to both Windows and Linux appliances, and call out any OS-specific differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is exclusively focused on Windows OS upgrade issues, with all examples, terminology, and troubleshooting steps tailored to Windows environments. There are no references to Linux, Linux-based VMs, or cross-platform considerations. The tools, links, and workflows described are all Windows-specific, and there is no mention of equivalent Linux upgrade or migration scenarios.

Recommendations:

Include parallel documentation or sections addressing Linux VM upgrade issues during migration, with Linux-specific troubleshooting steps.
Provide examples and recommended actions for both Windows and Linux VMs, or clarify early in the document that this page is Windows-specific and link to Linux documentation.
Reference Linux tools and commands (e.g., using SSH, Linux disk management commands) where appropriate.
Ensure that migration workflows and prerequisites are described for both Windows and Linux environments, or provide clear navigation to Linux-focused resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on Windows-based web app migrations, specifically those involving IIS and PowerShell. All troubleshooting steps, error codes, and examples are tailored to IIS servers and PowerShell scripting, with no mention of Linux-based web servers (such as Apache or Nginx) or Linux migration scenarios. There are no Linux-specific troubleshooting steps, tools, or commands provided.

Recommendations:

Add equivalent troubleshooting steps and error codes for common Linux web servers (e.g., Apache, Nginx) and migration scenarios.
Include Linux-based examples and commands (such as Bash scripts or relevant Linux tools) alongside or before Windows/PowerShell examples.
Clarify in the introduction that the guide is specific to IIS/Windows migrations, or provide separate sections for Linux and Windows migrations.
Reference Linux migration documentation or tools if available, and provide links to relevant resources.
Ensure parity in troubleshooting guidance for both Windows and Linux environments to support a broader range of users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily biased toward Windows environments. All prerequisites, installation steps, and operational instructions are centered on Windows OS, PowerShell, and Microsoft-specific tools (e.g., Web Deploy). There are no Linux equivalents or examples for containerizing ASP.NET applications, and Linux is only mentioned in the context of Java/Tomcat workloads. The documentation assumes the user has access to and is operating from a Windows machine, with no guidance for Linux users wishing to containerize ASP.NET apps.

Recommendations:

Provide equivalent instructions and tooling support for running the App Containerization tool on Linux (or clarify if not supported).
Include Linux shell (bash) examples alongside PowerShell commands where applicable.
If the tool is Windows-only, explicitly state this limitation early and suggest alternative approaches for Linux users (e.g., using Docker CLI, manual Dockerfile creation, or other open-source tools).
Offer guidance or links for containerizing ASP.NET Core applications on Linux, which is a common cross-platform scenario.
Balance the mention/order of Windows and Linux tools and patterns, ensuring Linux is not always secondary or omitted.
Where possible, provide troubleshooting and artifact locations for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows environments. All instructions, prerequisites, and tooling are centered on Windows OS, with explicit requirements for Windows machines, PowerShell, and Windows-specific tools (e.g., Microsoft Web Deploy). There are no Linux-based examples or alternatives for containerizing ASP.NET apps, and Linux is only mentioned in the context of Java/Tomcat scenarios. The documentation assumes the user is operating in a Windows environment and does not provide parity for Linux users.

Recommendations:

Provide equivalent instructions and tooling for Linux environments, such as supporting the installation and execution of the App Containerization tool on Linux machines.
Include Linux shell (bash) examples alongside PowerShell commands for all relevant steps.
Offer guidance for containerizing ASP.NET Core applications running on Linux, and clarify the support matrix for .NET Framework vs. .NET Core/5+/6+.
Mention and, where possible, support Linux-native deployment and discovery tools (e.g., SSH-based discovery, Linux package managers).
Clearly state any platform limitations up front and provide links to alternative workflows for Linux users.
Where Windows-only tools are required, suggest open-source or cross-platform alternatives if available, or provide a roadmap for Linux support.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. The Azure Migrate: App Containerization tool is only available for Windows, and all installation and usage instructions assume a Windows environment (including PowerShell commands and references to Windows file paths). There are no instructions or examples for installing or running the tool from a Linux or macOS machine, nor are there alternative workflows for non-Windows users. The troubleshooting section also only references Windows-specific log locations.

Recommendations:

Provide a Linux-compatible version of the Azure Migrate: App Containerization tool, or clearly state its unavailability and suggest alternative approaches for Linux users.
Include installation and usage instructions for Linux (and optionally macOS), with corresponding shell commands and file paths.
Offer troubleshooting guidance for Linux environments if/when a Linux version is available.
If the tool is fundamentally Windows-only, add a prominent note at the top of the documentation clarifying this limitation and linking to alternative migration/containerization approaches for Linux users.
Where possible, avoid assuming the user's workstation is Windows—present cross-platform instructions or alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias: the Azure Migrate: App Containerization tool can only be installed and run on Windows machines, with explicit requirements for Windows Server or Windows 10/11. All installation and usage instructions (including PowerShell commands and file paths) are Windows-specific, with no mention of Linux or macOS alternatives for running the tool. Troubleshooting and artifact storage paths are also Windows-centric. While the tool targets containerizing Java apps running on Linux servers, the management and orchestration are exclusively Windows-based, and there are no Linux-native usage examples or instructions.

Recommendations:

Provide a Linux version of the Azure Migrate: App Containerization tool, or clarify if it is not available.
If the tool is Windows-only, explicitly state this limitation at the start of the documentation.
Offer equivalent installation and usage instructions for Linux (e.g., bash scripts, Linux file paths) if/when the tool supports it.
Include troubleshooting and artifact location instructions for Linux environments if supported.
Consider providing a containerized version of the tool itself, so it can be run cross-platform.
If Windows is required only for the tool, suggest using a lightweight Windows VM or container for Linux users, and provide guidance on how to set this up.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias, particularly in the ASP.NET assessment flow. It references Windows-specific requirements (e.g., ASP.NET apps needing a Windows node pool), and the 'Next steps' section highlights optimizing Windows Dockerfiles without mentioning Linux equivalents. There are no Linux-specific examples, tools, or guidance for users running Java or .NET apps on Linux, and the documentation does not provide parity in Linux containerization or migration scenarios.

Recommendations:

Include explicit guidance and examples for Linux-based ASP.NET Core and Java web apps, covering both Windows and Linux containerization paths.
In the 'Cost details' and assessment sections, clarify when Linux node pools are recommended (e.g., for Java or ASP.NET Core apps) and provide cost breakdowns for both Windows and Linux scenarios.
In the 'Next steps' section, add links to resources on optimizing Linux Dockerfiles and best practices for Linux containers on AKS.
Ensure that any references to Dockerfile optimization, node pool selection, or migration steps are presented for both Windows and Linux, or clarify the applicability to each platform.
Wherever Windows-specific requirements are mentioned (such as the need for a Windows node pool), provide parallel information for Linux-based workloads.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows a Windows bias by referencing Windows-specific tools and patterns (such as Windows Server Failover Clusters and Cloud Witness), linking to Windows-specific best practices, and omitting Linux-specific guidance or examples. There are no Linux or cross-platform examples for SQL Server deployments, high availability, or licensing, and Windows terminology is used exclusively in several key sections.

Recommendations:

Include Linux-specific examples and guidance, such as SQL Server on Linux VM migration scenarios and high availability configurations (e.g., Pacemaker clusters).
Reference both Windows and Linux best practices for SQL Server on Azure VMs, providing links to both sets of documentation.
When discussing features like Azure Hybrid Benefit, clarify how it applies to both Windows and Enterprise Linux (RHEL/SLES) subscriptions, and provide examples for each.
In sections discussing high availability and disaster recovery, include Linux-supported options (e.g., Pacemaker, witness disk configurations) and not just Windows Server Failover Clusters.
Ensure screenshots and step-by-step instructions are platform-neutral or provide parallel instructions for both Windows and Linux environments.
Review terminology to avoid assuming Windows as the default (e.g., replace 'Windows Server Failover Clusters' with 'Failover Clusters (Windows or Linux)').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows Server licensing and Azure Hybrid Benefit for Windows Server before mentioning Linux equivalents. The 'Supportability' section highlights Windows Server versions specifically, and there are no Linux-specific examples or screenshots. Additionally, there are no Linux command-line or OS-specific instructions, and the only Linux mention is in the context of licensing (RHEL and SLES), not operational guidance or parity in examples.

Recommendations:

Include Linux-specific examples and screenshots, such as assessing VMs running popular Linux distributions (e.g., Ubuntu, CentOS, RHEL).
In the 'Supportability' and 'Assessment properties' sections, provide equal detail for Linux OS support and licensing, not just Windows Server.
Add notes or sections on how to interpret assessment results for Linux VMs, including common issues and remediation steps.
Ensure that any references to Azure Hybrid Benefit or cost optimization mention Linux options (RHEL, SLES) with equal prominence and detail as Windows Server.
Where possible, provide command-line or operational examples relevant to Linux environments, not just GUI-based workflows.

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 (such as Cloud Witness and Windows Server Failover Clusters) without mentioning Linux equivalents. There are no Linux-specific instructions, examples, or references to Linux-based SQL Server deployments or high availability patterns. The only mention of Linux is in the context of licensing (RHEL and SLES), not in operational or migration steps.

Recommendations:

Include explicit instructions and examples for assessing SQL Server instances running on Linux, including supported distributions and any differences in the assessment process.
Mention and link to Linux-based high availability and disaster recovery options (such as Pacemaker or Linux clustering solutions) alongside Windows Server Failover Clusters.
Provide parity in tooling references, such as how to configure or assess SQL Server on Linux VMs, and clarify any differences in Azure Migrate appliance setup or data collection for Linux environments.
Where Windows-specific features (like Cloud Witness) are mentioned, add corresponding Linux alternatives or note if they are not applicable.
Add screenshots or command-line examples relevant to Linux environments, not just Windows GUIs or PowerShell.

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 running on Windows Server, with no mention of Linux as a supported OS for the appliance itself. All setup and verification steps (e.g., running PowerShell scripts, using CertUtil for hash verification, installing Windows roles like IIS and PowerShell ISE) are Windows-centric. There are no Linux equivalents or instructions for running the appliance or scripts on Linux. While Linux server discovery is supported, all operational and administrative examples and tooling are Windows-only.

Recommendations:

Provide explicit instructions for deploying and running the Azure Migrate appliance on Linux-based EC2 instances, if supported.
Include Linux shell (bash) equivalents for all PowerShell and Windows command-line examples, such as verifying file hashes (e.g., using sha256sum).
Document Linux-native prerequisites and installation steps (e.g., required packages, services, and permissions) for the appliance, or clearly state if Linux is not supported as a host for the appliance.
If the appliance is Windows-only, clarify this early in the prerequisites and suggest alternatives or workarounds for Linux-only environments.
Ensure that all operational steps (such as extracting files, running scripts, and troubleshooting) have Linux equivalents or clear guidance for Linux administrators.
Balance the order of presentation so that Linux and Windows instructions are given equal prominence where both are supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. All setup, deployment, and configuration instructions are written for Windows Server and Hyper-V environments, with exclusive use of Windows tools (PowerShell, WinRM, Hyper-V Manager, Local Group Policy Editor) and commands. PowerShell scripts and commands are provided throughout, with no equivalent Linux shell or cross-platform alternatives. While Linux servers are mentioned as supported for discovery, there are no Linux-based examples or instructions for deploying or managing the Azure Migrate appliance, nor for preparing Linux-based Hyper-V hosts (if such exist). The documentation assumes the reader is operating entirely within a Windows ecosystem.

Recommendations:

Provide explicit instructions or references for deploying and managing the Azure Migrate appliance from a Linux or cross-platform environment, if supported.
Include Linux shell (bash) equivalents for PowerShell commands where applicable, or clarify if such operations are Windows-only.
Where Windows tools (e.g., Hyper-V Manager, Local Group Policy Editor) are referenced, note whether there are cross-platform or web-based alternatives, or explicitly state the requirement for Windows.
Add Linux-based examples for credential management, appliance configuration, and connectivity validation.
Clarify any limitations or requirements for Linux users, and provide guidance for mixed-OS environments.

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 is the only supported OS for the Azure Migrate appliance, with explicit instructions and examples using Windows tools (PowerShell, CertUtil, IIS, registry edits). The setup and installation process is described exclusively with Windows commands and patterns, with no equivalent Linux instructions or support. While Linux server discovery is mentioned, there are no examples or guidance for running the appliance or installer on Linux, nor are Linux-native tools referenced.

Recommendations:

Provide parity by supporting and documenting installation of the Azure Migrate appliance on Linux hosts, or explicitly state if this is not possible.
Include Linux shell (bash) equivalents for all PowerShell and Windows command-line examples, or clarify that the appliance is Windows-only.
Reference Linux-native tools (e.g., sha256sum for hash verification) alongside Windows tools like CertUtil.
If the appliance cannot run on Linux, explain the rationale and suggest best practices for mixed-OS environments.
Ensure that all steps involving Windows-specific features (IIS, registry, PowerShell ISE) are either accompanied by Linux alternatives or clearly marked as Windows-only requirements.
Consider restructuring sections so that Linux and Windows instructions are presented in parallel where possible, rather than Windows-first.

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 setup instructions and examples are presented before Linux, with more detailed steps and troubleshooting for Windows accounts, permissions, and tools. The installer script and appliance setup are described using PowerShell and Windows command-line tools (e.g., CertUtil), and the installation process assumes a Windows environment (e.g., references to IIS, registry keys, and Windows file paths). There are no equivalent Linux command-line examples or explicit instructions for running the installer or verifying hashes on Linux. Linux instructions are present but less detailed, and Linux-specific troubleshooting or parity for installer setup is missing.

Recommendations:

Provide Linux-first or parallel instructions where possible, ensuring Linux setup steps are as detailed and prominent as Windows steps.
Include Linux command-line examples for verifying file hashes (e.g., using sha256sum) alongside CertUtil for Windows.
Clarify whether the Azure Migrate appliance can be installed and run on Linux, and if so, provide explicit installation and troubleshooting steps for Linux environments.
When referencing tools or commands (e.g., PowerShell, IIS, registry keys), note their Windows specificity and offer Linux alternatives or state if not applicable.
Balance the troubleshooting and permission guidance for both Windows and Linux, ensuring Linux users have equivalent support and clarity.
Where screenshots or UI steps are shown, indicate any differences for Linux users or note if the process is identical.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas: it provides explicit PowerShell-based setup instructions for the Azure Migrate appliance only for Windows Server (with no equivalent Linux-based script or VM option), references Windows tools (e.g., PowerShell, Windows authentication, IIS) more frequently and in greater detail than their Linux counterparts, and often lists Windows procedures or requirements before Linux ones. While Linux is mentioned as supported, practical Linux setup examples and parity in tooling are lacking.

Recommendations:

Provide a Linux-based script or VM option for setting up the Azure Migrate appliance, or clarify if only OVA import is supported for Linux environments.
Include explicit Linux command-line examples (e.g., using SSH, scp, or Linux-native automation) for appliance setup and configuration, not just PowerShell/Windows.
Balance the order of presentation: when listing supported OSes, tools, or procedures, alternate or group Windows and Linux equally, rather than defaulting to Windows-first.
Offer detailed Linux authentication and troubleshooting guidance, similar to the depth provided for Windows (e.g., for SSH key setup, permissions, and validation).
When referencing tools like VMware VDDK, clarify installation paths and procedures for both Windows and Linux hosts.
Expand documentation on discovering and assessing Linux-specific workloads (e.g., Apache, Nginx, PostgreSQL) to match the detail given for Windows workloads (IIS, SQL Server).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas: Windows-specific tools and requirements are mentioned first or exclusively (e.g., the replication appliance must run on Windows Server 2012 R2/2016), and some steps and troubleshooting sections focus on Windows management services or activation issues. While Linux instructions are present, they are sometimes less detailed or appear after Windows instructions. There is no mention of using a Linux-based replication appliance, and some examples (e.g., screenshots, troubleshooting) are Windows-centric.

Recommendations:

Provide parity by offering Linux-based options for the replication appliance, if supported, or clearly state if only Windows is supported and why.
When listing steps for both Windows and Linux, alternate the order or present them in parallel to avoid always putting Windows first.
Expand Linux-specific troubleshooting and post-migration guidance to match the detail given for Windows (e.g., mention common Linux boot or driver issues, not just Windows activation).
Include Linux-specific screenshots or examples where appropriate, not just Windows-centric visuals.
If certain features or tools are Windows-only, explicitly note the lack of Linux support and suggest workarounds or alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas. The replication appliance required for migration must be a Windows Server (2012 R2 or 2016) VM, with no mention of a Linux-based alternative. In step-by-step instructions, Windows prerequisites and ports (WinRM) are listed before Linux, and some troubleshooting steps reference Windows management services. While Linux VM migration is supported and some Linux-specific instructions are present, the overall workflow and tooling are centered around Windows environments, and there is no parity in appliance OS support or in-depth Linux automation examples.

Recommendations:

Provide a Linux-based replication appliance option, or clearly state if only Windows is supported and explain the rationale.
When listing prerequisites or configuration steps, present Linux and Windows instructions in parallel or in separate, equally detailed sections.
Include Linux-specific troubleshooting steps and examples, not just Windows-centric ones (e.g., errors related to SSH, systemd, or Linux firewalls).
Offer automation examples for Linux environments (e.g., using shell scripts or Ansible) for agent installation and configuration, similar to Windows examples.
Avoid assuming Windows as the default environment for appliance deployment or management tasks; clarify OS requirements early and provide alternatives where possible.

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 Server is consistently referenced as the default or primary environment for the replication appliance, with explicit instructions to copy files to a Windows Server 2016 machine. PowerShell is the only command-line automation method detailed for appliance setup, with no Bash or Linux-native alternatives. Registry and Group Policy checks are described exclusively for Windows, and troubleshooting/upgrade notes focus on Windows tools (e.g., SetupDiag). While Linux is mentioned as a supported OS and some Linux agent installation steps are provided, Linux-specific guidance is less detailed, and Linux automation or appliance deployment methods are not covered. There are also more links and troubleshooting steps for Windows than for Linux.

Recommendations:

Provide parallel Linux-based instructions for deploying the replication appliance, including supported Linux distributions and setup steps (e.g., using a Linux VM or container as the appliance host).
Include Bash or shell script examples for automation alongside PowerShell, especially for agent installation and appliance setup.
Document Linux-specific prerequisites and troubleshooting steps (e.g., SELinux, firewall, systemd services) in parity with Windows registry and Group Policy checks.
Ensure that all references to Windows tools (e.g., SetupDiag, registry keys) are matched with Linux equivalents or clearly marked as Windows-only, with Linux alternatives provided where possible.
Balance the order of presentation so that Linux and Windows instructions/examples are given equal prominence, or clearly separate them into OS-specific sections.
Expand the Linux agent installation section to include automation options (e.g., Ansible, shell scripts) and troubleshooting tips.
Add more Linux-focused post-migration best practices and links, such as integration with Azure Update Manager for Linux, and guidance for securing and monitoring Linux VMs.

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-specific instructions and tools (e.g., registry edits, Windows Server 2016 appliance, Azure VM agent auto-installation on Windows but not Linux) are presented first or exclusively, while Linux instructions are minimal or secondary. PowerShell/Windows-centric patterns are assumed (e.g., VMware PowerCLI, registry changes), and Linux alternatives or detailed examples are often missing or less emphasized.

Recommendations:

Provide parallel, detailed Linux instructions and examples wherever Windows-specific steps are given (e.g., registry edits for Windows, provide equivalent Linux configuration steps).
When describing the setup of the replication appliance, clarify if a Linux-based appliance is supported or provide guidance for Linux-based environments.
For agent installation, include explicit Linux command-line examples (e.g., using SSH and package managers) alongside Windows instructions.
When referencing tools like PowerCLI or Windows Server, mention Linux-compatible alternatives or clarify cross-platform support.
In post-migration steps, give equal detail for Linux (e.g., how to install the Azure VM agent on Linux, how to remove Linux-specific tools).
Avoid always listing Windows steps or tools first; alternate or group by OS to show parity.
Ensure all troubleshooting and best practices sections include Linux-specific guidance, not just Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows environments, specifically Hyper-V on Windows Server. All command-line examples use Windows paths, executables, and conventions (e.g., .exe files, %Programdata% variables, C:\ paths). There are no Linux equivalents or cross-platform instructions for any step, and the only OS-specific troubleshooting or upgrade guidance is for Windows. The documentation assumes the use of Windows-native tools and does not mention or provide parity for Linux-based Hyper-V hosts or management via Linux shells.

Recommendations:

Explicitly state that the documented process is only supported on Windows-based Hyper-V hosts, or clarify if Linux-based Hyper-V management is unsupported.
If any steps can be performed from a Linux environment (e.g., using Azure CLI, REST API, or PowerShell Core on Linux), provide equivalent Linux/bash examples.
Where possible, use cross-platform tools (such as Azure CLI) for steps like registration, monitoring, or automation, and provide corresponding examples.
Add a section addressing migration of Linux VMs running on Hyper-V, including any special considerations or differences in the process.
Ensure that post-migration steps and best practices include Linux-specific guidance (e.g., troubleshooting, activation, security, and update management for Linux VMs).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows-specific tools, upgrade paths, and troubleshooting steps. Windows OS upgrade options and tools (e.g., SetupDiag, Windows Server upgrade) are mentioned explicitly, while equivalent Linux migration, upgrade, or troubleshooting guidance is absent. The only script-based appliance setup method references PowerShell, with no mention of Bash or Linux-native alternatives. Linux is only briefly mentioned in passing, with no concrete examples or instructions.

Recommendations:

Provide parallel Linux-specific instructions and examples wherever Windows-specific steps are detailed (e.g., OS upgrades, troubleshooting).
Include Linux migration/upgrade best practices, such as guidance for common distributions (Ubuntu, RHEL, etc.), and reference tools like cloud-init or distribution-specific upgrade methods.
When referencing script-based setup, clarify if the PowerShell installer script is compatible with Linux (e.g., via PowerShell Core), or provide a Bash/shell script alternative.
Add troubleshooting steps and post-migration checks for Linux VMs, similar to the Windows activation troubleshooting section.
Ensure screenshots and UI references are OS-neutral or provide both Windows and Linux perspectives where relevant.
Explicitly state any differences or limitations for Linux VMs in agentless migration scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation for Azure Migrate demonstrates a Windows bias in several ways. Windows-specific tools (PowerShell, Windows Server, IIS, SCOM) are frequently mentioned, often without Linux equivalents or with Windows examples appearing first. PowerShell is referenced as the primary automation/scripting tool, and Windows-centric migration scenarios (e.g., ASP.NET on IIS, Windows OS upgrades) are highlighted more prominently than Linux scenarios. Linux support is mentioned, but often as an afterthought or in less detail, and Linux-specific tooling or automation examples are largely absent.

Recommendations:

Provide Linux-specific examples alongside Windows examples, especially for automation (e.g., Bash scripts, Ansible, or shell commands for appliance setup and migration tasks).
Mention Linux tools and workflows (e.g., systemd, SSH, Linux package managers) where relevant, not just PowerShell or Windows tools.
Ensure Linux migration scenarios (e.g., Apache, NGINX, Tomcat, Java apps) are given equal prominence and detail as Windows/IIS/ASP.NET scenarios.
When referencing automation or scripting, include both PowerShell and Bash (or other Linux scripting) examples.
Highlight Linux-specific features or challenges (such as SELinux, sudo/root access, package dependencies) in migration guidance.
Avoid always listing Windows/PowerShell options first; alternate the order or present both together.
Add troubleshooting and best practices sections for Linux migrations, not just for Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides extensive Azure PowerShell examples and guidance, which is a Windows-centric toolset, and references PowerShell-specific installation and usage patterns. PowerShell is presented before Azure CLI in both prerequisites and procedural sections, and there is no mention of native Linux shell scripting or Linux-specific nuances. While Azure CLI is cross-platform, the documentation's structure and emphasis favor Windows/PowerShell users.

Recommendations:

Present Azure CLI examples before PowerShell examples, as CLI is more universally available across platforms.
Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide any Linux-specific notes if needed.
Add Bash script examples for common tasks, especially in sections where PowerShell scripting is demonstrated.
Avoid assuming PowerShell as the default scripting environment; clarify that both PowerShell and CLI are supported and highlight cross-platform compatibility.
Where PowerShell installation is discussed, provide equivalent instructions for Bash/CLI environments on Linux and macOS.
Consider adding a short section or callout for Linux/macOS users, summarizing the parity and any differences.

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 the PowerShell sections are notably more detailed and verbose than their CLI (cross-platform) counterparts. PowerShell (a Windows-centric tool, though available on Linux) is often presented with more context, explanations, and step-by-step breakdowns. In several places, PowerShell is listed before CLI, and guidance on installing and updating Azure PowerShell is included, but there is no equivalent Linux shell or Bash-specific guidance. The documentation assumes familiarity with PowerShell cmdlets and patterns, which may be less accessible to Linux-first users.

Recommendations:

Ensure CLI (az) examples are as detailed as PowerShell examples, including explanations and context for each step.
Add explicit Bash/Linux shell guidance where appropriate, such as using Bash variables, loops, or environment setup.
When listing deployment methods, alternate the order or explicitly state that CLI is cross-platform and suitable for Linux/macOS/Windows.
Provide links or references for installing/updating Azure CLI on Linux, similar to the PowerShell installation guidance.
Where PowerShell-specific patterns are explained (e.g., use of hashtables, cmdlet pipelines), offer analogous Bash/CLI scripting tips.
Review all sections for assumptions of Windows/PowerShell familiarity and add clarifying notes for Linux users as needed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias. It exclusively references connecting to the Azure Stack Edge device via Windows PowerShell, both in the prerequisites and in the registration steps. There are no instructions or examples for Linux or cross-platform users, and only Windows tools and patterns are mentioned. The documentation assumes the user is operating from a Windows environment, with no mention of alternatives for Linux or macOS.

Recommendations:

Provide equivalent instructions for connecting to Azure Stack Edge from Linux and macOS clients, including supported shells (e.g., Bash, Azure CLI).
Include Linux/macOS command-line examples alongside PowerShell, or clarify if cross-platform support is not available.
If only Windows is supported, explicitly state this limitation early in the documentation.
Reference cross-platform tools (such as Azure CLI or REST API) where possible, and provide examples for those.
Review all prerequisite and procedural steps to ensure parity for non-Windows users, or document any platform-specific requirements.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a moderate Windows bias. Troubleshooting steps and examples reference Windows-specific tools (such as 'ps ping', 'netsh', and PowerShell usage with curl) without providing equivalent Linux commands or guidance. There are no Linux or cross-platform examples for network troubleshooting, and the only code/tooling examples are Windows-centric. The mention of PowerShell and Windows tools appears before or instead of Linux alternatives, and there is no mention of common Linux utilities (e.g., ping, traceroute, tcpdump, ip, netcat) for network diagnostics.

Recommendations:

Provide equivalent Linux command-line examples alongside Windows/PowerShell commands (e.g., use 'ping', 'nc', 'ss', 'tcpdump', 'traceroute' for Linux).
When referencing tools like 'ps ping' or 'netsh', add corresponding Linux alternatives (e.g., 'ping', 'ss', 'tcpdump', 'ip route').
Avoid using only PowerShell-specific flags (such as '-DisableKeepalive') in examples; show how to achieve the same in Bash or Linux shells.
Explicitly mention that the troubleshooting steps apply to both Windows and Linux VMs, and clarify any OS-specific differences.
Include .NET examples for both Windows and Linux environments, or provide cross-platform code samples.
Balance the order of presentation so that Linux and Windows tools are mentioned together or in alternating order, rather than Windows-first.

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 are provided for resolving failed network interface states, but there are no equivalent CLI or Linux-native instructions. In the connectivity validation table, Windows-specific tools (PsPing, PowerShell Invoke-WebRequest) are listed, while Linux tools are mentioned but with less detail. The PowerShell method is described first and in more detail than the Azure Resource Explorer method, and there is no mention of Azure CLI or Linux-native alternatives for managing network interfaces. This may disadvantage users working primarily in Linux environments or using cross-platform automation.

Recommendations:

Provide equivalent Azure CLI commands for all PowerShell examples, especially for managing network interfaces in failed states.
Expand Linux tool recommendations in the connectivity validation table (e.g., suggest 'ss', 'telnet', or 'curl' for UDP where appropriate).
Ensure that Linux and cross-platform tools are mentioned alongside or before Windows-specific tools, or present both together.
Where PowerShell is used, add corresponding Bash/Azure CLI scripts to ensure parity.
Clarify that all operations can be performed from Linux/macOS using Azure CLI or REST API, and provide links or examples.
Consider adding a section or callout for cross-platform troubleshooting approaches.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by consistently presenting Windows instructions and tools (such as PowerShell and Windows Admin Center) before their Linux equivalents. PowerShell is emphasized as a cross-platform automation tool, but Linux-specific automation (e.g., Bash, shell scripts, or Ansible) is not mentioned. Windows Admin Center is highlighted as a management tool, with no Linux-native alternatives discussed. While Linux installation steps are present, they are less detailed and not given parity in automation or tooling recommendations.

Recommendations:

Alternate the order of Windows and Linux instructions or present them side-by-side to avoid always listing Windows first.
Include Linux-native automation options (e.g., Bash scripts, Ansible, or shell-based onboarding) alongside PowerShell.
Mention or link to Linux management tools (such as Cockpit or other open-source solutions) if relevant, or clarify that similar Linux-native tooling is not available.
Ensure that Linux examples are as detailed as Windows examples, including troubleshooting and verification steps.
Where PowerShell is recommended for automation, clarify its cross-platform nature and provide equivalent Bash or shell script examples for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. PowerShell is presented as the primary scripting method, even for Linux scenarios, rather than using native Linux shells (e.g., Bash). In all code tab groups, Windows examples are listed before Linux, and the use of Windows-specific tools and naming conventions (such as PowerShell cmdlets and 'WindowsAgent' naming) is prevalent. There are no Bash or native Linux shell examples, and Linux instructions are essentially adaptations of the Windows/PowerShell workflow.

Recommendations:

Provide native Bash or shell script examples for Linux scenarios, especially when using the Azure CLI.
List Linux and Windows examples in parallel or alternate the order to avoid always presenting Windows first.
When referencing tools, clarify if they are cross-platform or provide Linux-native alternatives where possible.
Use more neutral language and variable names (e.g., avoid 'WindowsAgent' as the default unless contextually necessary).
Explicitly mention any differences or considerations unique to Linux environments beyond just swapping agent names.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Azure PowerShell, providing only PowerShell-based examples and instructions. There are no examples or guidance for using Azure CLI, Bash, or other cross-platform tools, even though the scenario (diagnosing VM network issues) is relevant for both Windows and Linux users. The prerequisites and step-by-step instructions assume the use of PowerShell, which is more familiar to Windows users, and there is no mention of Linux-native workflows or tools.

Recommendations:

Add equivalent Azure CLI (az) command examples alongside PowerShell commands for each step.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
Include a section or callout for Linux users, highlighting any differences or additional considerations.
Where possible, use cross-platform terminology and avoid assuming PowerShell as the default shell.
Link to documentation for both Azure PowerShell and Azure CLI installation and usage.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a notable Windows bias, particularly in the testing and validation phases. While the infrastructure setup is cross-platform (Portal, PowerShell, CLI), the test virtual machines in both spokes are exclusively Windows Server 2022, and all test/validation steps (IIS installation, browser-based tests using Microsoft Edge, PowerShell scripts) are Windows-centric. There are no equivalent examples or instructions for deploying or testing with Linux-based VMs in the spokes, nor are Linux tools (e.g., curl, Apache/nginx, SSH) mentioned for validation. The use of PowerShell and Windows tools is prevalent, and Windows-based patterns are presented as the default for validation.

Recommendations:

Provide parallel Linux-based test VM instructions for the spokes, including deployment, configuration, and validation steps (e.g., using Ubuntu or CentOS, installing Apache/nginx, and using curl or wget for testing).
Include Linux command-line examples for validation (e.g., curl http://<ip-address> to test web server connectivity, or using lynx/w3m as text browsers).
When demonstrating IIS installation and testing, also show how to install and test a web server on Linux (e.g., sudo apt install apache2, echo 'Hello World' > /var/www/html/index.html).
Instruct on using SSH and Linux shell commands for connectivity and troubleshooting, not just RDP/Edge/PowerShell.
Balance the use of Windows and Linux tools in all test and validation sections, and avoid assuming the user will always use Windows VMs or Microsoft browsers.
Explicitly mention that either Windows or Linux VMs can be used for testing, and provide guidance for both.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates subtle Windows bias. It references Windows-specific tools and extensions (e.g., Network Watcher extension for Windows), and provides links and instructions that are Windows-centric. Linux support is mentioned, but Linux-specific instructions, examples, or agent documentation are missing. Automation examples mention PowerShell before Azure CLI and Terraform, and there are no Linux command-line or agent installation examples.

Recommendations:

Provide explicit Linux agent installation and migration instructions, including links to Linux-specific documentation.
Include Linux command-line examples (e.g., Bash, Azure CLI) alongside or before PowerShell examples.
When referencing extensions or agents, mention both Windows and Linux versions, and provide links to both.
Ensure automation tooling is presented in a cross-platform order (e.g., Azure CLI, Terraform, then PowerShell), or group them together without preference.
Add a section or callout for Linux users highlighting any differences or additional steps required.
Review all references to ensure Linux parity in troubleshooting, error messages, and integration guidance.

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) before Azure CLI in both prerequisites and procedural sections. PowerShell-specific instructions and terminology are detailed, and PowerShell is referenced as the method for advanced customization (e.g., naming resources), sometimes to the exclusion of CLI or Linux-native alternatives. There is no explicit mention of Linux or Bash, and no Linux-specific examples or guidance are provided, even though Azure CLI is cross-platform.

Recommendations:

Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI first in some sections to avoid the impression of Windows-first bias.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific usage notes or examples where relevant.
Where PowerShell is referenced for advanced scenarios (e.g., custom naming), ensure equivalent Azure CLI methods are described, or clarify if not possible.
Add a brief section or note in prerequisites highlighting that Azure CLI is available natively on Linux and macOS, and that Cloud Shell supports both Bash and PowerShell.
Avoid language that implies PowerShell is the default or preferred scripting environment unless there is a technical reason.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

Although the documentation is focused on managing the Network Watcher Agent VM extension for Linux, there is a notable emphasis on PowerShell usage, which is traditionally a Windows-centric tool. PowerShell is presented as a primary automation/scripting method alongside Azure CLI, and instructions for deploying ARM templates reference Azure PowerShell before Azure CLI. There is also a minor error in the Azure CLI install example referencing 'Network Watcher Agent for Windows' instead of Linux. No Linux-native tools or shell scripting examples (e.g., Bash) are provided, and the documentation assumes the use of Azure-specific tools rather than generic Linux administration patterns.

Recommendations:

Provide Bash shell script examples for common operations (install, list, uninstall) using Azure CLI, to better align with Linux administrator workflows.
When listing automation options, present Azure CLI before PowerShell, as CLI is cross-platform and more familiar to Linux users.
Clarify that PowerShell is available cross-platform, but highlight that Azure CLI is often preferred for Linux environments.
Correct the minor error in the Azure CLI install example that refers to 'Network Watcher Agent for Windows' instead of Linux.
Consider including examples of how to automate extension management using native Linux tools (e.g., curl with Azure REST API) for advanced users.
Explicitly state that no Linux-native package management (apt, yum, etc.) is involved, to avoid confusion.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several ways: (1) The only provided script for bulk updating extensions across multiple VMs is a PowerShell script, which is inherently Windows-centric and requires Azure PowerShell modules. (2) The 'Update your extension using a PowerShell script' section exclusively targets Windows VMs, with no equivalent Bash or Azure CLI script for Linux VMs. (3) In several sections, PowerShell is presented as the primary or first method, with Linux/Azure CLI alternatives appearing later or not at all. (4) There is no example of a Bash or shell script for bulk updating Linux VMs, and no mention of automation approaches for Linux outside of Azure CLI one-liners.

Recommendations:

Provide a Bash or Azure CLI script example for bulk updating the Network Watcher extension across multiple Linux VMs, similar to the PowerShell script for Windows.
Ensure that automation examples for both Windows and Linux are given equal prominence and detail, ideally in parallel sections or tabs.
When listing manual update options, present Azure CLI and PowerShell examples side-by-side, or alternate which is shown first.
Explicitly mention cross-platform automation options (such as using Azure CLI in Bash or Python scripts) for managing both Windows and Linux VMs at scale.
Review the order of examples and ensure Linux and Windows are treated equally throughout the documentation.

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 scripting examples use PowerShell, and the instructions reference PowerShell-specific cmdlets and naming conventions. There are no examples or guidance for users on Linux or macOS, nor are cross-platform tools or alternatives mentioned. The documentation assumes familiarity with Windows tooling and does not address how to achieve the same results using Bash, Azure CLI, or other cross-platform scripting environments.

Recommendations:

Provide equivalent examples using Azure CLI (az commands), which is cross-platform and works on Linux, macOS, and Windows.
Include Bash script samples for Linux users, demonstrating how to automate VPN gateway monitoring and notifications.
Mention that Azure Automation supports Python runbooks and provide a Python example for the scenario.
Clarify which steps are platform-agnostic (e.g., using the Azure Portal) and which are specific to Windows/PowerShell.
Add a section or note for Linux/macOS users, outlining how to set up and monitor VPN gateways using non-Windows tools.
Reference documentation or guides for setting up Azure Automation runbooks with languages other than PowerShell.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on using Power BI Desktop, a Windows-only tool, for visualizing Azure NSG flow logs. There are no instructions or examples for Linux users, nor are alternative cross-platform or Linux-native visualization tools mentioned in the main body of the guide. The workflow assumes access to and use of Windows-specific software, and Linux alternatives are only referenced in a 'Next steps' link at the end.

Recommendations:

Add explicit instructions or a parallel workflow for Linux users, such as using Power BI on the web (if supported for this scenario), or open-source alternatives like Grafana or Kibana.
Mention cross-platform or Linux-compatible tools earlier in the documentation, not just as a 'next step'.
Provide example commands or steps for accessing and preparing NSG flow logs on Linux (e.g., using Azure CLI, Python scripts, or other tools).
Clarify in the prerequisites that Power BI Desktop is only available for Windows, and suggest alternatives for users on other operating systems.
Consider offering a downloadable template or dashboard for open-source tools alongside the Power BI template.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a strong bias toward Windows and PowerShell usage. All scripting and automation examples are provided exclusively as PowerShell scripts (.ps1), with no mention of Bash, CLI, or Linux-native alternatives. The prerequisites and instructions assume the use of PowerShell, and there are no Linux- or cross-platform-specific examples or guidance, despite PowerShell Core being cross-platform. The documentation also references Windows-centric tools and patterns, such as the .ps1 script and Windows-style command prompts, without clarifying or demonstrating usage on Linux or macOS.

Recommendations:

Provide equivalent Bash or Azure CLI scripts/examples for Linux/macOS users, or at least mention how to run the PowerShell script on Linux/macOS using PowerShell 7.
Clarify in the prerequisites and instructions that PowerShell 7 is cross-platform, and provide explicit instructions for installing and running the script on Linux and macOS.
Add notes or sections that address common Linux/macOS environments, such as file extraction, script execution permissions (chmod +x), and how to invoke the script from a Linux shell.
Where screenshots or command prompts are shown, include examples from both Windows and Linux terminals to demonstrate parity.
If the migration process is only supported via PowerShell, explicitly state this limitation and provide a roadmap or alternatives for Linux users if possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exclusively uses Azure PowerShell for deployment instructions and examples, with no mention of Azure CLI, Bash, or Linux-native workflows. File paths use Windows conventions (e.g., C:\MyTemplates\azuredeploy.json), and there are no Linux or cross-platform alternatives provided. This creates a strong Windows and PowerShell bias, making it less accessible for users on Linux or macOS.

Recommendations:

Add equivalent Azure CLI (az) examples for deploying ARM templates, using Bash syntax and Linux file paths (e.g., ~/MyTemplates/azuredeploy.json).
Mention both PowerShell and CLI as supported options in the introduction and prerequisites.
Where file paths are shown, provide both Windows and Linux/macOS examples.
Include notes or links for users on Linux/macOS, clarifying how to perform the same steps in their environments.
Consider reordering or parallelizing instructions so that neither Windows nor Linux is presented as the default or primary platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a clear Windows bias: the only VM image used is Windows Server, and all instructions for connecting to the VM are via RDP, a Windows-specific protocol. There are no examples or guidance for deploying or connecting to a Linux VM (e.g., using SSH), nor are Linux images or tools mentioned. The workflow assumes a Windows environment throughout.

Recommendations:

Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM steps.
Include examples for connecting to the Linux VM using SSH, both via the Azure portal and from a local terminal.
Mention Linux-compatible tools for viewing and analyzing the downloaded flow logs (e.g., using cat, jq, or less).
When listing VM images, present both Windows and Linux options, or make it clear that the tutorial applies to both.
Add notes or callouts indicating how steps differ for Linux users, especially in sections involving remote access and credential setup.

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 command-line tool shown for configuring NSG flow log settings (e.g., setting FlowTimeoutInMinutes), with no equivalent Azure CLI, Bash, or Linux-native example. The reference to PowerShell (Set-AzVirtualNetwork) appears before any mention of other platforms, and there is no guidance for Linux users. The documentation also references tools like Power BI (a Microsoft/Windows-centric tool) before open-source or cross-platform alternatives, and does not provide parity in example commands or workflows for Linux environments.

Recommendations:

Add Azure CLI examples (az network vnet update ...) alongside or before PowerShell for all configuration tasks, especially for setting properties like FlowTimeoutInMinutes.
Include Bash or shell script snippets where appropriate, to demonstrate cross-platform usage.
When listing visualization tools, alternate or balance the order (e.g., mention Grafana or Elastic Stack before or alongside Power BI) and provide links to Linux-friendly guides.
Explicitly state that all features and workflows are available on both Windows and Linux, and provide links to relevant Linux documentation.
Where PowerShell is referenced, add a note or section for Linux/macOS users with equivalent commands.
Ensure that troubleshooting and setup sections include steps for both 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. All code samples and automation steps use PowerShell exclusively, with no equivalent Bash, CLI, or Python examples for Linux users. The authentication and environment setup instructions assume a Windows-style file system and scripting environment. While there are brief mentions of a Linux VM extension, all practical guidance and tooling focus on Windows-first approaches, leaving Linux users without clear, actionable instructions.

Recommendations:

Provide equivalent examples using Azure CLI and/or Bash scripts for Linux environments, especially for authentication, environment variable setup, and packet capture initiation.
Include Python or other cross-platform scripting options for Azure Functions, not just PowerShell.
Show how to generate and store encrypted credentials on Linux (e.g., using OpenSSL or GPG) instead of only using Windows file paths and PowerShell encryption.
Explicitly mention and demonstrate how to use the Linux Network Watcher extension, including any differences in setup or operation.
Balance the order of presentation: introduce both Windows and Linux approaches side-by-side, or alternate which is presented first.
Reference Linux-friendly tools for downloading and analyzing packet captures (e.g., azcopy, wget, tcpdump, tshark) alongside Windows tools.

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 method, and file path examples (e.g., C:\Capture\myVM_1.cap) are consistently shown before Linux equivalents. Download examples and tool recommendations (e.g., Azure Storage Explorer) are Windows-centric, and Linux-specific instructions or examples are minimal or only mentioned as afterthoughts. There are no explicit Linux shell (bash) examples for downloading files or handling packet captures locally, and guidance for Linux users is limited to brief notes about file paths.

Recommendations:

Provide Linux-first or at least parallel Linux examples (e.g., show /var/captures/myVM_1.cap alongside C:\Capture\myVM_1.cap in all relevant code and tables).
Include bash or Linux shell command examples for downloading packet captures from Azure Storage (e.g., using azcopy, wget, or curl).
Mention and link to cross-platform tools (such as azcopy or rclone) for managing Azure Storage, not just Azure Storage Explorer.
When referencing local file paths, always show both Windows and Linux formats together, not just as a note.
In PowerShell and CLI sections, explicitly call out any OS-specific differences or requirements.
Consider adding a dedicated section or callout for Linux/macOS users, summarizing key differences and recommended tools.

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: it references Azure PowerShell and the Azure portal (which is often Windows-centric) before Azure CLI or REST API, and provides no Linux-specific instructions or examples. The log file examples and error messages reference Windows error codes and paths (e.g., C:\Resources\...), and troubleshooting steps mention PowerShell as an alternative to Azure CLI without mentioning Bash or Linux-native tools. There are no Linux command-line examples or guidance for Linux administrators.

Recommendations:

Provide explicit Linux/Bash/Azure CLI examples alongside or before PowerShell examples.
Include Linux file path formats and clarify if logs can be interpreted on Linux systems.
Reference Linux-native tools (e.g., az CLI on Bash, or third-party tools for log analysis) where appropriate.
When mentioning downloading blobs, include instructions for Linux (e.g., using azcopy, wget, or the Azure CLI in Bash).
Clarify that the Azure portal and PowerShell are cross-platform, or provide links to Linux installation guides if relevant.
Where Windows error codes are referenced, provide guidance for interpreting similar errors on Linux VPN devices.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exclusively uses PowerShell cmdlets and examples for VPN troubleshooting, with no Azure CLI, Bash, or Linux-native command examples provided. The prerequisites and instructions focus on Azure PowerShell and Cloud Shell, which, while available cross-platform, are more familiar to Windows users. There is no mention of Linux shell scripting or CLI workflows in the main content, and the only reference to CLI is in the 'Related content' section, not in the main instructional flow.

Recommendations:

Add parallel Azure CLI examples for all PowerShell commands, ideally using Bash syntax.
Update prerequisites to mention both Azure PowerShell and Azure CLI as supported options, with links to installation guides for each.
Where PowerShell is referenced, clarify that Azure CLI is also available and provide a tabbed interface or side-by-side examples for both.
Include Linux/Bash-specific notes or tips where relevant, such as accessing logs or using CLI tools.
Ensure that links to CLI-based troubleshooting are more prominent, not just in 'Related content'.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation implicitly assumes a Windows development environment by referencing Windows-centric UI actions (e.g., 'Right click', 'click Save'), and does not provide any explicit Linux or cross-platform command-line alternatives for common tasks such as file creation, editing, or package management. There are no PowerShell-specific commands, but the absence of Linux/CLI examples and the use of GUI instructions suggest a Windows-first bias.

Recommendations:

For every step that uses a GUI action (e.g., 'Right click', 'click Save'), provide equivalent command-line instructions suitable for Linux/macOS users (e.g., using 'touch' or 'nano' to create/edit files).
Explicitly mention that the steps can be performed on Linux/macOS and provide any necessary differences (such as file paths or command syntax).
If referencing Azure Data Studio or SQL editors, clarify their cross-platform availability and provide installation or usage notes for Linux/macOS.
Include terminal-based package installation commands (e.g., 'dotnet add package ...') alongside or instead of GUI-based instructions.
Review all instructions for assumptions about file system navigation or UI elements that may not exist on Linux/macOS, and provide alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows-first bias, particularly in the 'Guest configuration' section, which only references the installation of Windows security baselines and does not mention Linux equivalents. There are no explicit Linux examples or references to Linux-specific best practices, tools, or configuration baselines, despite Azure Automanage supporting both Windows and Linux VMs.

Recommendations:

Include information about Linux guest configuration, such as supported Linux security baselines or compliance policies, alongside the Windows example.
Explicitly state which services and features are available for both Windows and Linux VMs, and highlight any differences or limitations.
Provide links to Linux-specific documentation where appropriate (e.g., for configuring security baselines or monitoring on Linux VMs).
Ensure that examples and descriptions are balanced between Windows and Linux, or clearly indicate when a feature is Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page lists a client setup guide specifically for Windows 10, with no mention of Linux or cross-platform client setup. This suggests a Windows-first bias and a lack of Linux parity in client setup instructions.

Recommendations:

Add equivalent client setup documentation for Linux workstations, including mounting procedures and troubleshooting.
Ensure that all client setup examples and tutorials are provided for both Windows and Linux platforms.
Where possible, mention cross-platform tools or provide guidance for both operating systems in each relevant section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation assumes the use of Visual Studio (a primarily Windows IDE) and does not mention or provide instructions for Linux or cross-platform development environments. There are no examples or guidance for running or developing the .NET applications on Linux, nor are alternative tools (such as VS Code or command-line .NET CLI) mentioned.

Recommendations:

Include instructions for setting up and running the .NET applications using cross-platform tools such as Visual Studio Code or the .NET CLI.
Explicitly mention that .NET Core/.NET 5+ applications can be developed and run on Linux and macOS, not just Windows.
Provide Linux-specific steps or notes where relevant, such as installing the .NET SDK on Linux, and running the applications from the terminal.
Avoid assuming Visual Studio as the only development environment; offer alternatives suitable for Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page shows a subtle Windows bias by referencing the Azure portal, PowerShell, and CLI clients as ways users are immediately aware of backup job results, but does not mention Linux-specific tools or workflows. There are no explicit Linux or cross-platform command-line examples, and the only agent mentioned by name is the Microsoft Azure Recovery Services (MARS) agent, which is Windows-only. Notification configuration is stated as only available via the Azure portal, with no mention of Linux-friendly automation or CLI alternatives.

Recommendations:

Include explicit examples or references for Linux users, such as using Azure CLI or REST API (even if not currently supported, clarify roadmap or alternatives).
Mention Linux-compatible backup agents or clarify if only Windows workloads are supported for classic alerts.
Balance references to PowerShell with Azure CLI or Bash equivalents where possible.
If certain features are Windows-only (e.g., MARS agent), clearly state this and provide Linux alternatives or workarounds.
Add documentation or links for Linux administrators to monitor and manage alerts using tools available on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is given equal prominence to Azure CLI, despite being a Windows-centric tool. There is no explicit mention of Linux-specific tools or shell environments (such as Bash), and PowerShell is presented as a primary option alongside Azure CLI, which may suggest a bias towards Windows users.

Recommendations:

Clarify that Azure CLI commands are cross-platform and can be used on Windows, Linux, and macOS.
Consider providing Bash shell examples or explicitly mentioning that CLI commands work in Bash/Terminal on Linux/macOS.
If PowerShell is included, note that it is available cross-platform, but that Bash is the default shell on most Linux systems.
Add a section or note for Linux/macOS users, confirming that all CLI steps are fully supported on those platforms.
Avoid presenting PowerShell as an equally primary option unless there is a specific need for it, or at least indicate the typical platform usage for each tool.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references Microsoft-centric backup tools (MABS, DPM-A, MARS Agent), which are primarily Windows-based, and does not mention or provide examples for Linux environments or tools. There are no Linux-specific instructions, examples, or references to Linux-compatible backup agents or workflows, indicating a bias toward Windows platforms.

Recommendations:

Explicitly state whether Linux-based backup agents or workflows are supported or not for offline backup scenarios.
If Linux is supported, provide examples and instructions for performing offline backups from Linux systems, including any required tools or agents.
Mention any Linux-compatible utilities or command-line tools that can be used for preparing and transferring backup data.
Include a comparison or support matrix indicating platform compatibility (Windows/Linux) for each offline backup method.
If Linux is not supported, clearly document this limitation to set customer expectations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively discusses copying and pasting to and from Windows virtual machines, with no mention of Linux VMs or their specific considerations. All prerequisites and instructions are Windows-centric, and there are no examples or guidance for Linux users.

Recommendations:

Add equivalent instructions and examples for Linux virtual machines, including any differences in clipboard handling or keyboard shortcuts.
Update the prerequisites section to mention both Windows and Linux VMs, or clarify if the feature is Windows-only.
If there are limitations or differences for Linux VMs, document them explicitly.
Provide screenshots or illustrations showing the process on Linux desktops where applicable.

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 examples are included as a primary tab alongside Azure CLI, which can be interpreted as a Windows-first approach. There is no explicit mention of Linux or macOS environments, nor are there Bash-specific examples or notes about cross-platform usage. The PowerShell examples use Windows-style variable assignment, and there is no indication of parity for Linux users beyond the Azure CLI tab.

Recommendations:

Explicitly mention that the Azure CLI instructions are cross-platform and suitable for Linux, macOS, and Windows.
Add a Bash-specific tab or clarify that the Azure CLI tab uses Bash syntax, which is common on Linux/macOS.
If PowerShell is included, clarify that it is available cross-platform, or provide notes for Linux/macOS PowerShell users.
Consider listing the Azure CLI (Bash) tab first, as it is the most cross-platform option.
Add a short section in prerequisites or notes about supported operating systems and shells.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows by exclusively recommending Azure Storage Explorer (a GUI tool most commonly used on Windows) for file operations, without mentioning or providing examples for Linux-native tools or command-line alternatives. There are no Linux-specific instructions or CLI examples for creating/uploading files or managing Blob storage containers.

Recommendations:

Include examples using cross-platform command-line tools such as Azure CLI (az storage commands) and/or Azure PowerShell for all file and container operations.
Explicitly mention that Azure Storage Explorer is available on Windows, macOS, and Linux, and provide download links for each platform.
Provide Linux-native alternatives for file creation and upload, such as using the 'touch' and 'echo' commands to create files, and 'az storage blob upload' for uploading files.
Add a section or callout for Linux/macOS users, outlining equivalent steps using terminal commands.
Ensure screenshots and instructions do not assume a Windows environment; include examples or notes for other operating systems where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by linking exclusively to the Windows-specific 'Create a VM tutorial' for the prerequisite virtual machine setup, without mentioning or linking to the equivalent Linux VM creation guide. No Linux-specific instructions or examples are provided, and the only explicit VM creation reference is for Windows. However, the rest of the tutorial is largely platform-agnostic, focusing on Azure portal and Logic Apps UI, and does not use Windows-specific tools or PowerShell.

Recommendations:

In the prerequisites section, provide links to both the Windows and Linux VM creation tutorials, e.g., '/azure/virtual-machines/windows/quick-create-portal' and '/azure/virtual-machines/linux/quick-create-portal'.
Explicitly state that the tutorial applies to both Windows and Linux virtual machines, unless there are platform-specific limitations.
Where examples reference interacting with the VM (such as resizing or updating), ensure that the linked documentation covers both Windows and Linux scenarios.
Consider including a note or example that demonstrates monitoring changes on a Linux VM to reinforce cross-platform applicability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively deploys Windows Server virtual machines in the example environment, with no mention of Linux VM options. All VM references are to Windows, and the admin credential instructions assume a Windows context. While deployment and management commands are cross-platform (Azure CLI and PowerShell), the infrastructure example is Windows-centric, lacking Linux parity.

Recommendations:

Include an example or option for deploying Linux virtual machines (e.g., Ubuntu Server) alongside or instead of Windows Server VMs in the Bicep template.
Explicitly mention that the jump box and server VMs can be either Windows or Linux, and provide parameterization or instructions for both.
When describing admin credentials, clarify any differences for Linux VMs (e.g., SSH keys vs. passwords).
Ensure that screenshots, walkthroughs, and validation steps reference both Windows and Linux VM scenarios where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exclusively references RDP sessions as the trigger for auto-stop functionality, which is a Windows-centric remote access protocol. There is no mention of Linux remote desktop protocols (such as SSH or VNC), nor any examples or clarifications for Linux-based dev boxes. All examples and explanations assume a Windows environment.

Recommendations:

Clarify whether the auto-stop feature supports Linux-based dev boxes and, if so, specify which disconnect events (e.g., SSH, VNC) are supported.
Provide examples or notes for Linux users, including how disconnects are detected for non-Windows environments.
If the feature is Windows-only, explicitly state this limitation early in the documentation.
Consider including parity features or roadmap information for Linux support if it is not currently available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page, while describing Azure CLI scripts (which are cross-platform), shows evidence of Windows bias. The scripts are referenced as Bash scripts, but the code blocks are incorrectly labeled as 'powershell', which may confuse Linux users. Additionally, the first and only explicit VM creation example is for a Windows VM, with no mention of creating a Linux VM or providing a Linux-specific example.

Recommendations:

Correct the code block language tags from 'powershell' to 'bash' or 'azurecli' to accurately reflect the script content and avoid confusion for Linux users.
Include explicit examples for creating Linux VMs in addition to Windows VMs, or clarify that the scripts can be adapted for both.
Ensure that references to operating systems are balanced, and provide parity in documentation for both Windows and Linux scenarios.
If possible, add notes or links to documentation on how to adapt the scripts for Linux VM creation, including differences in authentication and image selection.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page predominantly describes password setting/resetting in a way that assumes Windows as the default, with screenshots and dialog text referencing Windows. There is only a brief mention of Ubuntu in a parenthetical note, and no Linux-specific instructions, screenshots, or examples are provided. The process for Linux VMs is not explained, and the UI appears Windows-centric.

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 beyond the single parenthetical note (e.g., how students set passwords, what dialog boxes look like, or if command-line tools are needed).
Ensure that examples and images alternate between Windows and Linux, or provide parallel sections for each platform.
Avoid language that assumes Windows as the default; instead, structure the documentation to address both Windows and Linux VMs equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides a hosts file modification example only for Windows (C:\Windows\System32\drivers\etc\hosts) and does not mention the equivalent process for Linux or macOS. This prioritizes Windows and omits guidance for users on other platforms.

Recommendations:

Include equivalent instructions for modifying the hosts file on Linux (e.g., /etc/hosts) and macOS.
Present cross-platform examples together, or mention all major platforms when giving file path or configuration instructions.
Review the documentation for other areas where platform-specific instructions may be needed to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation explicitly states that the Data Mapper tool only works in Visual Studio Code running on Windows operating systems. There are no instructions, examples, or troubleshooting steps for Linux or macOS users. All setup and usage guidance assumes a Windows environment, and there is no mention of parity or alternatives for non-Windows platforms.

Recommendations:

Clearly indicate at the top of the page that Data Mapper is currently Windows-only, and provide a roadmap or estimated timeline for Linux/macOS support if available.
Add a dedicated section addressing Linux/macOS users, explaining the current limitations and any possible workarounds (such as using a Windows VM, remote development, or alternative tools).
If possible, provide links to feature requests or feedback channels where users can express interest in cross-platform support.
Once Linux/macOS support is available, update the documentation with platform-specific installation and usage instructions, and ensure all examples are validated on all supported platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing only the Windows virtual machine quickstart in the prerequisites, without mentioning or linking to a Linux equivalent. There are no Linux-specific instructions or examples, and the only VM creation link is for Windows, which may lead Linux users to feel unsupported or overlooked.

Recommendations:

Include a link to the Linux virtual machine quickstart alongside the Windows quickstart in the prerequisites section.
Explicitly mention that the tutorial applies to both Windows and Linux VMs, unless there are platform-specific caveats.
Where examples or screenshots reference Windows VMs, consider providing parallel examples or clarifying that the steps are the same for Linux VMs.
Review the documentation for other subtle Windows-first language or assumptions and update to be platform-neutral where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a subtle Windows bias by prioritizing RDP (port 3389) as a primary example of a commonly checked port, without mentioning SSH (port 22), which is the standard for Linux VMs. There are no Linux-specific examples or references, and the troubleshooting workflow is described in a way that implicitly assumes Windows-centric usage patterns.

Recommendations:

Include SSH (port 22) as a commonly checked port alongside RDP, HTTP, and HTTPS.
Explicitly mention that the troubleshooter can be used for both Windows and Linux VMs.
Provide examples or screenshots that show troubleshooting for Linux VMs (e.g., checking SSH connectivity).
Clarify that the tool is platform-agnostic and applicable to both Windows and Linux environments.
Consider reordering the list of ports or providing parity in examples (e.g., 'Port 3389 (RDP, Windows)' and 'Port 22 (SSH, Linux)').

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 PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and there is no mention of Linux-specific considerations or shell environments (e.g., Bash). The structure and language (e.g., 'save to your local computer') are generic but do not explicitly address Linux users or provide Bash-specific guidance. The PowerShell example is presented immediately after the CLI example, which is common, but there is no explicit effort to highlight Linux parity or address potential differences.

Recommendations:

Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and can be run in Bash or other shells.
Add a Bash-specific tab or section, or clarify that the CLI example is suitable for Bash/Linux shells.
If there are any Linux-specific steps (e.g., file paths, permissions), call them out.
Consider reordering to present CLI/Bash examples first, as they are more universally applicable.
Add a note that PowerShell Core is available on Linux, if relevant, to clarify cross-platform support.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation mentions Microsoft PowerShell as an example HTTP client for testing the POST request, but does not mention any Linux or cross-platform alternatives such as curl or HTTPie. No command-line examples are provided for Linux or macOS users, and the only tool explicitly referenced is Windows-centric.

Recommendations:

Provide equivalent command-line examples using curl or HTTPie, which are available on Linux, macOS, and Windows.
Mention cross-platform tools (e.g., curl, Postman) alongside PowerShell when suggesting ways to test HTTP requests.
If including PowerShell examples, also include Bash/curl examples to ensure parity for Linux/macOS users.
Consider rephrasing to say 'any HTTP client such as curl, HTTPie, Postman, or PowerShell' to avoid implying a Windows-only approach.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is largely platform-neutral, focusing on HTTP requests and protocol details. However, in the section on testing POST HTTP requests, only Microsoft PowerShell is mentioned as an example HTTP client, with no mention of Linux or cross-platform alternatives such as curl or HTTPie. No Linux-specific tools or shell examples are provided.

Recommendations:

When suggesting tools for testing HTTP requests, mention cross-platform and Linux-native tools such as curl and HTTPie alongside PowerShell.
Provide example command lines for both Windows (PowerShell) and Linux/macOS (bash/curl) when demonstrating how to make HTTP requests.
Explicitly state that the HTTP requests can be tested using any HTTP client, and provide at least one example for each major platform.
Avoid implying that PowerShell is the default or only option for testing HTTP requests.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation contains a subtle Windows bias by linking to instructions for securing REST APIs that default to a 'windows' tab (e.g., 'secure-rest-api.md?tabs=windows'), without mentioning or providing equivalent Linux/macOS guidance. There are no explicit PowerShell or Windows command-line examples, but the referenced documentation may prioritize Windows tooling or workflows. No Linux-specific tools, commands, or parity notes are present.

Recommendations:

Wherever documentation links reference platform-specific instructions (such as 'secure-rest-api.md?tabs=windows'), ensure that Linux/macOS tabs are equally visible and referenced. Consider linking to a neutral or multi-platform version of the page.
Explicitly mention that the guidance applies to all platforms, and provide Linux/macOS equivalents or note when steps are platform-agnostic.
If any referenced workflows (such as API protection or token acquisition) have platform-specific steps, include both Windows and Linux/macOS examples inline or as expandable sections.
Review all linked documentation to ensure Linux users are not disadvantaged or forced to adapt Windows-centric instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page does not provide any OS-specific command-line examples, but it references the Azure portal and Azure CLI for configuration. However, there is a subtle Windows-first bias: the documentation does not explicitly mention Linux or provide Linux-specific guidance or examples, and the Azure CLI (which is cross-platform) is only mentioned in passing, with no concrete CLI commands or shell examples. The instructions and screenshots are oriented toward the Azure portal, which is platform-agnostic, but there is no effort to ensure Linux parity or to highlight cross-platform workflows.

Recommendations:

Add explicit Azure CLI command examples for all configuration steps, including app registration and setting application secrets, and show these commands in both Windows (cmd/PowerShell) and Linux (bash) syntax where relevant.
Include a note or section confirming that all steps can be performed from Linux, macOS, or Windows, and provide links to cross-platform CLI documentation.
If screenshots are provided, clarify that the Azure portal is accessible from any OS.
Where file paths or environment variables are referenced, show both Windows and Linux conventions.
Consider adding a troubleshooting section for common Linux-specific issues (e.g., file permissions, line endings, CLI installation).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. While it provides Linux, macOS, and Windows command examples for running the sample app, there are subtle indications of Windows-centric assumptions: the warning about path length ("Extract the sample file to a folder where the total length of the path is 260 or fewer characters") is a Windows-specific limitation, and the Windows example is listed last but uses the Windows-specific 'py' launcher. However, all platforms are represented in the run instructions, and there are no PowerShell-only commands or exclusive references to Windows tools.

Recommendations:

Clarify that the 260-character path length limitation applies only to Windows, and that Linux/macOS users are not affected.
Consider listing Linux or macOS instructions first, or randomizing the order, to avoid implicit prioritization of Windows.
Provide a note explaining the difference between 'python' and 'py' launchers, and suggest using 'python' on all platforms if possible for consistency.
Ensure any screenshots or UI references are cross-platform or clarify when they are Windows-specific.
Continue to provide explicit, parallel instructions for all major platforms (Linux, macOS, Windows) in future updates.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows development environments by focusing exclusively on Visual Studio and Visual Studio Code as prerequisites and editors, with no mention of Linux-specific tools, distributions, or command-line instructions. All examples and instructions are editor-agnostic but implicitly assume a Windows or cross-platform environment without addressing Linux-specific setup, such as package installation, path length limitations, or running .NET applications on Linux. There are no PowerShell-specific commands, but the lack of explicit Linux parity (e.g., mentioning Linux package managers, terminal commands, or troubleshooting) constitutes a subtle bias.

Recommendations:

Explicitly mention that Visual Studio Code and .NET SDK are cross-platform and provide links or instructions for Linux installation (e.g., using apt, yum, or snap).
Include a Linux-specific section in the prerequisites, listing supported distributions and any additional dependencies (such as libssl-dev for .NET on Linux).
Address path length limitations as they relate to both Windows and Linux, clarifying if the 260-character limit is a Windows-specific constraint.
Provide example terminal commands for building and running the .NET projects on Linux (e.g., using dotnet CLI in Bash).
Mention any known issues or differences when running the sample on Linux (such as file permissions, HTTPS development certificates, or case sensitivity in file paths).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing Visual Studio (a Windows-centric IDE) before Visual Studio Code, and by using a sample path and port (https://localhost:44316) that are typical defaults for Visual Studio on Windows. There are no explicit instructions or examples for running the sample on Linux (e.g., using the dotnet CLI, configuring HTTPS certificates, or handling path length limitations on Linux filesystems). No Linux-specific tools, commands, or troubleshooting tips are provided.

Recommendations:

Provide explicit instructions for running the sample on Linux, including using the dotnet CLI (e.g., 'dotnet run') and handling HTTPS development certificates.
Mention any Linux-specific prerequisites, such as installing .NET SDK on Ubuntu or other distributions.
Clarify that Visual Studio Code is cross-platform and provide example commands for both Windows and Linux environments.
Address path length limitations as they relate to both Windows and Linux, or clarify if this is only a Windows concern.
Include troubleshooting tips for common Linux issues, such as permissions or certificate trust.
When listing prerequisites, present cross-platform tools (like Visual Studio Code and dotnet CLI) before or alongside Windows-specific tools.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on Azure Portal UI and Microsoft 365 tools (Logic Apps, Microsoft Teams, Power Automate), which are primarily used in Windows-centric enterprise environments. There are no command-line examples, scripts, or alternative automation approaches for Linux users. The workflow assumes the use of Microsoft Teams for notifications, with no mention of alternatives like Slack or email, and all steps are described using the Azure Portal GUI, which is more familiar to Windows users. There is no coverage of CLI, REST API, or Infrastructure-as-Code (IaC) methods that would be more platform-neutral or Linux-friendly.

Recommendations:

Provide Azure CLI and/or Azure PowerShell command examples for each step, especially for resource creation, role assignment, and event subscription setup.
Include REST API examples for automation, which are platform-agnostic and can be used from any OS.
Offer alternative notification integrations (e.g., Slack, email, or webhooks) in addition to Microsoft Teams.
Document how to perform the workflow setup using Infrastructure-as-Code tools like Bicep, ARM templates, or Terraform.
Explicitly mention that all steps can be performed from Linux/macOS using the Azure CLI and provide links or examples.
If using screenshots, consider including CLI output or code snippets alongside portal images to ensure parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page is heavily focused on ASP.NET Core and C# code, which are most commonly associated with Windows development environments. There are no explicit instructions, examples, or notes for Linux or cross-platform users. The use of Windows-centric project structures (e.g., Startup.cs, appsettings.json) and references to Visual Studio conventions further reinforce a Windows-oriented approach. There are no command-line instructions, but if there were, they would likely be PowerShell or CMD by default given the context.

Recommendations:

Add explicit notes or sections clarifying that ASP.NET Core and related tools are cross-platform, and provide guidance for Linux and macOS users.
Include examples or references for setting up and running the sample projects on Linux (e.g., using the dotnet CLI, file paths, and environment variable configuration).
Mention common Linux editors (e.g., VS Code, Vim) and how to edit configuration files or run the application from the terminal.
If any scripts or commands are referenced, provide both Windows (PowerShell/CMD) and Linux (bash) equivalents.
Highlight any platform-specific considerations, such as file permissions or case sensitivity, that may affect Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on ASP.NET Core and Visual Studio tooling, which are traditionally Windows-centric. While .NET Core is cross-platform, the instructions and examples assume a Windows development environment (e.g., Visual Studio, Visual Studio Code) and do not mention or provide explicit guidance for Linux or macOS users. There are no Linux-specific instructions, troubleshooting tips, or references to Linux development workflows.

Recommendations:

Explicitly mention that all .NET Core CLI commands work cross-platform (Windows, Linux, macOS) and provide assurance that Linux is supported.
Add a section or callout for Linux/macOS users, including any prerequisites (e.g., installing .NET SDK on Linux, using editors like VS Code or JetBrains Rider).
Include Linux/macOS-specific instructions for running the app (e.g., using 'dotnet run' in a terminal), and clarify any differences in file paths or environment variables.
If referencing Visual Studio, also reference cross-platform editors (e.g., VS Code, Rider) and provide equivalent steps.
Add troubleshooting tips for common Linux/macOS issues (e.g., HTTPS certificate trust, file permissions).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by focusing exclusively on ASP.NET web applications (a Microsoft-centric technology), referencing Visual Studio and Visual Studio Code as development environments, and omitting any Linux-specific instructions or examples. There are no mentions of Linux tools, shell environments, or cross-platform considerations for running or deploying the application. All command-line instructions are generic or Windows-centric, and there is no guidance for users developing on Linux or macOS.

Recommendations:

Explicitly mention that .NET Core and ASP.NET Core are cross-platform and can be developed and run on Linux, macOS, and Windows.
Provide Linux/macOS equivalents for any command-line instructions, including package installation and project creation.
Include instructions for using popular Linux editors (e.g., VS Code on Linux, JetBrains Rider) and terminal environments.
Add troubleshooting notes or links for common Linux/macOS issues (e.g., HTTPS certificate trust, file permissions).
Clarify that the dotnet CLI commands work on all platforms, and avoid implying that Visual Studio (Windows) is required.
If referencing Visual Studio, also mention Visual Studio for Mac or cross-platform alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias by prioritizing PowerShell examples and instructions before CLI (Bash) and REST alternatives. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux or cross-platform users. However, the inclusion of Azure CLI (Bash) and REST API examples does provide Linux parity, though these are consistently presented after PowerShell, reinforcing a 'Windows-first' pattern.

Recommendations:

Present Azure CLI (Bash) examples before or alongside PowerShell examples to better serve Linux and cross-platform users.
Explicitly state that Azure CLI commands are cross-platform and can be used on Windows, Linux, and macOS.
Where possible, provide examples in a neutral scripting language (such as Bash or Python) or clarify that PowerShell Core is available cross-platform.
Review and balance the order of example tabs so that no single OS is consistently prioritized.
Add a brief section or note highlighting tool availability and parity across platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on using the Azure portal web UI for configuration, which is cross-platform, but where command-line or automation is implied, there are no examples for Linux (e.g., Azure CLI, Bash) or PowerShell. There is a subtle 'Windows-first' bias in that all UI instructions and terminology are oriented toward the Azure portal experience, which is identical on all platforms but is often associated with Windows-centric workflows. There are no explicit references to Windows-only tools, but there is also a lack of parity for Linux users who may prefer CLI or scripting approaches.

Recommendations:

Provide Azure CLI examples for key steps (e.g., app registration, secret creation, identity provider configuration) alongside portal instructions.
Explicitly mention that all portal steps can be performed from any OS/browser to reinforce cross-platform compatibility.
Where relevant, include Bash and PowerShell script snippets for automation, and clarify that both are supported.
Add a section or links to documentation for automating these tasks using CLI tools, which are popular in Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page lists a broad set of code samples for Azure AD B2C integration across platforms and languages. However, for desktop and console/daemon app scenarios, only .NET/Windows-specific samples are provided (e.g., WPF desktop app, .NET Core console app), with no equivalent Linux or cross-platform desktop/CLI examples. The only desktop sample is explicitly for Windows, and there are no Linux-native or cross-platform GUI/CLI samples. Additionally, the .NET samples are consistently listed before Node.js, Python, or other language samples, indicating a subtle 'windows_first' ordering bias.

Recommendations:

Add Linux-native or cross-platform desktop application samples (e.g., using Electron, Qt, or Java) to demonstrate Azure AD B2C integration outside of Windows.
Provide CLI/daemon application samples in languages commonly used on Linux (e.g., Python, Node.js, Go) and clarify their cross-platform compatibility.
Where possible, clarify if .NET Core samples are cross-platform and provide explicit instructions or notes for running them on Linux/macOS.
Balance the ordering of sample listings so that Windows/.NET samples are not always listed first; consider grouping by platform or language family.
For each sample, specify supported platforms (Windows, Linux, macOS) to help developers identify relevant examples.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively describes using the Azure Portal (a web-based GUI) for all steps and does not provide any command-line examples. There are no references to PowerShell, Windows-specific tools, or CLI commands, but there is also a complete absence of Linux-friendly alternatives such as Azure CLI or REST API examples. This omission can disadvantage Linux users or those who prefer automation and scripting over GUI-based workflows.

Recommendations:

Add Azure CLI examples for all major steps (e.g., app registration, permission assignment, role assignment, client secret creation), ensuring commands are cross-platform.
Include REST API examples (using curl or similar tools) for users who wish to automate the process or work on non-Windows platforms.
Explicitly mention that all steps can be performed using CLI or API, and provide links to relevant documentation.
If PowerShell or Windows-specific tools are ever referenced, ensure Linux equivalents are presented side-by-side or before the Windows examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias by specifically mentioning Windows Hello as the primary example of biometric authentication, both in the introduction and in the scenario walkthrough. Windows Hello is referenced before any mention of biometric options on other platforms, and there are no explicit examples or instructions for Linux or macOS users. The documentation does not provide parity in examples or guidance for non-Windows environments, and focuses on Windows-specific tools and terminology.

Recommendations:

Include explicit examples and instructions for enabling biometric authentication on Linux (e.g., using fprintd, libfprint, or other Linux-compatible biometric solutions) and macOS (e.g., Touch ID).
When describing scenarios, mention Linux and macOS biometric capabilities alongside Windows Hello, rather than focusing on Windows first.
Provide troubleshooting or compatibility notes for users on Linux and macOS, including any limitations or required setup steps.
Use platform-neutral language where possible (e.g., 'your device's biometric authentication' instead of 'Windows Hello'), and only reference Windows Hello as one of several options.
Add a table or section comparing biometric authentication support across Windows, Linux, and macOS, with links to relevant setup guides.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias primarily through the exclusive use of Azure Portal GUI instructions and the absence of any Linux-specific or cross-platform command-line examples. All step-by-step instructions assume use of the Azure Portal, which is platform-agnostic but often more familiar to Windows users. There are no references to Linux tools, shell commands, or PowerShell/CMD scripts, but also no mention of Bash or Linux CLI alternatives. The only code snippets are XML/PowerShell-like configuration blocks, which are not OS-specific, but the overall workflow and tooling references implicitly favor Windows users by not acknowledging or providing parity for Linux environments.

Recommendations:

Add CLI-based instructions using Azure CLI or Azure PowerShell, and specify cross-platform compatibility.
Include examples or notes for performing key steps (such as uploading policy files or managing secrets) using Bash or Linux shell environments.
Explicitly mention that the Azure Portal is accessible from any OS, and provide links to documentation for Linux users where relevant.
Where configuration files are edited or uploaded, provide command-line alternatives (e.g., using az ad b2c policy commands if available) and note any OS-specific considerations.
Review and update the documentation to ensure that Linux administrators can follow all steps without needing to switch to a Windows environment.

Create pull request

Bias Types:

⚠️ linux_first

⚠️ missing_windows_example

Summary:

The documentation page demonstrates a Linux-first bias, especially in the sections on Java key store management, where only Linux paths, tools, and instructions are provided. There are no equivalent instructions or examples for Windows-based App Service environments, such as Windows file paths, certificate store handling, or PowerShell/Windows command-line usage. This may leave Windows users without clear guidance for similar tasks.

Recommendations:

Add equivalent instructions for Windows-based App Service environments, including how certificates are loaded into the Java key store on Windows.
Provide Windows file paths (e.g., %JAVA_HOME%\lib\security\cacerts) and explain any differences in certificate handling between Linux and Windows.
Include examples of using Windows command-line or PowerShell to interact with the Java key store, such as using keytool on Windows.
Clarify in each section whether the instructions apply to both Linux and Windows, or specify the differences.
Ensure parity in troubleshooting and debugging steps for both platforms, such as how to open a remote terminal on Windows App Service.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates subtle Windows bias by referencing a SAML application guide with a URL parameter '?tabs=windows', suggesting that Windows-specific instructions or tabs are prioritized or default. There are no explicit Linux or cross-platform examples or tabs mentioned, and no indication that Linux users are equally supported in the SAML app registration flow. No PowerShell or Windows-only tools are directly mentioned, but the lack of Linux parity in tabbing and examples is notable.

Recommendations:

Ensure that all platform-specific instructions (such as for SAML apps) provide both Windows and Linux (and possibly macOS) tabs or examples.
Default to a neutral or cross-platform tab (e.g., '?tabs=linux' or '?tabs=cli') in documentation URLs, or provide a platform selector.
Explicitly mention Linux and other non-Windows platforms in relevant sections to assure users of parity.
Review all linked tutorials to confirm that Linux instructions are present and equally prominent.
Where applicable, provide CLI-based (e.g., Azure CLI, Bash) examples alongside any Windows/Powershell instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by consistently referencing 'command prompt' and using language and conventions familiar to Windows users, such as keyboard shortcuts (e.g., CTRL+C) and command prompt terminology. There are no explicit Linux or macOS shell examples, nor is there mention of alternative shells or terminal environments. The only command-line example is a generic 'devproxy' command, but the context and tips (such as downloading a preset in 'the command prompt') assume a Windows environment. No Linux-specific instructions, screenshots, or troubleshooting are provided.

Recommendations:

Include explicit Linux/macOS shell examples alongside Windows command prompt instructions (e.g., show both 'Command Prompt' and 'Bash' usage).
Replace or supplement 'command prompt' references with 'terminal' or 'shell' to be more platform-agnostic.
Add notes or tips for Linux/macOS users, such as installation steps, file path conventions, and keyboard shortcuts (e.g., CTRL+C is universal, but clarify if any hotkeys differ).
Provide at least one screenshot or terminal output from a Linux or macOS environment.
Mention any platform-specific requirements or troubleshooting steps for non-Windows users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation assumes the use of Visual Studio Code and Microsoft-centric tools, but does not provide any platform-specific instructions or examples. While VS Code is cross-platform, there are implicit biases: keyboard shortcuts are given in Windows format (Ctrl+Shift+P), and there is no mention of Linux or macOS equivalents. There are no terminal/CLI examples, and all instructions are GUI-based, which may disadvantage Linux users who prefer CLI workflows. The documentation also presumes the use of Microsoft Entra ID and Azure, which are more common in Windows environments.

Recommendations:

Explicitly mention that Visual Studio Code and the Azure API Center extension are available on Windows, Linux, and macOS.
Provide keyboard shortcut alternatives for macOS (e.g., Cmd+Shift+P) alongside Windows/Linux (Ctrl+Shift+P).
If there are CLI or terminal-based ways to perform tasks (such as connecting to the API Center), include those examples, especially for Linux users.
Clarify that all steps and screenshots apply equally to Linux and macOS, or note any platform-specific differences.
Consider including a section or note for users who prefer terminal workflows, especially common in Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and PowerShell examples for Azure CLI commands, but consistently lists Bash first and PowerShell second. There is no exclusive use of Windows tools, but the explicit inclusion of PowerShell syntax throughout, and references to Visual Studio Code (a cross-platform tool but with strong Windows association), may suggest a slight Windows bias. However, Linux users are not excluded, and Bash examples are always present and prioritized.

Recommendations:

Continue to provide both Bash and PowerShell examples, but clarify that Bash examples work on Linux/macOS and Windows (with WSL or Git Bash), and PowerShell is available cross-platform.
Explicitly mention that Visual Studio Code and Azure CLI are fully supported on Linux and macOS, not just Windows.
Where possible, include a short note or table at the start of the CLI sections explaining which shells/environments are supported for each example.
Consider adding a section or callout for Linux/macOS users, highlighting any platform-specific considerations (if any).
If there are any steps that are easier or different on Linux (e.g., using native package managers), mention them.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias by exclusively providing Azure CLI and Azure PowerShell examples for managing API Management regional gateways, with explicit mention of the Azure PowerShell cmdlet (set-azapimanagement) and no mention of Linux-specific tools or shell environments. While the Azure CLI is cross-platform, the absence of any Linux shell (bash) or scripting examples, and the ordering of PowerShell before CLI in the list of tools, subtly prioritizes Windows-centric tooling and usage patterns.

Recommendations:

Include explicit bash/Linux shell examples alongside Azure CLI commands, demonstrating usage in a Linux environment.
When listing management tools, mention cross-platform tools (Azure CLI, REST API) before Windows-specific tools (Azure PowerShell).
If referencing PowerShell, clarify that Azure CLI is fully supported on Linux/macOS and provide equivalent bash scripting examples where appropriate.
Add a note or section highlighting that all Azure CLI commands work identically on Linux, macOS, and Windows, and provide example shell commands for common Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally maintains cross-platform neutrality, but in the section on editing the hosts file for DNS testing, the Windows path (%SystemDrive%\drivers\etc\hosts) is listed before the Linux/macOS path (/etc/hosts). Additionally, a related content link points to a Windows 2000 Server DNS article, which is outdated and Windows-specific. No PowerShell-heavy or Windows-only command examples are present, but subtle prioritization of Windows paths and tools is evident.

Recommendations:

List Linux/macOS and Windows hosts file paths in parallel or in alphabetical order, or provide separate instructions for each platform to avoid implicit prioritization.
Replace or supplement the 'Creating a record in DNS' related link with a modern, cross-platform or Azure-native DNS documentation link.
Where platform-specific paths or tools are mentioned, ensure equal prominence and detail for Linux/macOS equivalents.
Consider including example commands or screenshots for both Windows and Linux environments where relevant (e.g., editing hosts file, DNS setup).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides detailed, step-by-step SSH access instructions and CLI examples exclusively for Linux containers, while Windows containers are only mentioned briefly and lack any equivalent command-line or PowerShell examples. The Windows section is presented first, but it only describes browser-based SSH access and notes that CLI-based SSH is not supported for Windows containers. There are no PowerShell or Windows-native SSH instructions, and the Linux section is much more comprehensive.

Recommendations:

Provide parity in documentation by including equivalent instructions or explicit statements for Windows containers, even if only to clarify limitations (e.g., 'SSH via CLI/PowerShell is not supported for Windows containers').
If possible, add PowerShell or Windows-native SSH client instructions for Windows containers, or explain why such access is not available.
Consider presenting Linux and Windows instructions in parallel or with equal prominence, rather than always listing Windows first.
Explicitly state the differences in SSH support between Linux and Windows containers at the top of the page for clarity.
If browser-based SSH is the only supported method for Windows containers, provide a detailed walkthrough and screenshots for that scenario, similar to the Linux CLI example.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally uses cross-platform tools (Git, Node.js, Azure CLI) and avoids OS-specific commands. However, in Step 6, it explicitly instructs users to '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, which may give the impression of a Windows-first or Windows-preferred workflow.

Recommendations:

In Step 6, explicitly mention Linux and macOS terminals alongside Windows Command Prompt and PowerShell (e.g., 'Open your terminal (Windows Command Prompt, PowerShell, Linux shell, or macOS Terminal)').
Wherever shell commands are shown, clarify that they work on all platforms unless otherwise noted.
If any step has platform-specific nuances (such as path separators or environment variable syntax), provide examples for both Windows and Linux/macOS.
Consider adding a short note in the prerequisites or introduction stating that the instructions are cross-platform and tested on Windows, Linux, and macOS.
If screenshots or UI instructions are given for Azure CLI or other tools, include Linux/macOS terminal screenshots where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on Azure-native and cross-platform tools but does not provide any OS-specific examples. However, it implicitly exhibits a 'windows_first' bias by only mentioning Microsoft-centric tools (Azure Pipelines, Visual Studio Code, dotnet-apim) and omits explicit Linux or non-Microsoft CI/CD tools and workflows. There are no CLI or shell command examples, but the absence of Linux-specific tools, editors, or pipelines (e.g., GitLab CI, Jenkins, or Linux shell usage) and the exclusive mention of Visual Studio Code and .NET tools suggest a lack of Linux parity.

Recommendations:

Include examples of using popular Linux-based CI/CD tools such as Jenkins, GitLab CI, or Travis CI for API deployment.
Mention and provide examples of using Linux-native editors (e.g., Vim, Emacs, or JetBrains IDEs) for API definition editing.
Provide CLI examples using bash or shell scripts for deploying APIs, in addition to or instead of Azure Pipelines or GitHub Actions.
Reference cross-platform or Linux-preferred tools for API linting, testing, and deployment where possible.
Explicitly state the cross-platform compatibility of the mentioned tools, and provide guidance for Linux users where workflows may differ.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently references Visual Studio Code and GitHub Copilot for testing and using the MCP server, but does not provide any Linux-specific instructions, CLI examples, or mention of alternative editors or tools commonly used on Linux. All configuration and usage steps are described in the context of the Azure Portal (web-based) and Visual Studio Code, which, while cross-platform, is often associated with Windows workflows. There are no explicit Linux shell, terminal, or non-GUI instructions, nor any mention of Linux-specific considerations.

Recommendations:

Add explicit instructions or notes confirming that all steps (including Visual Studio Code and GitHub Copilot usage) are fully supported on Linux, and mention any Linux-specific prerequisites if applicable.
Provide alternative examples using command-line tools (such as curl, httpie, or az CLI) for testing the MCP server, which are commonly used on Linux.
Include a section or callout for Linux users, highlighting any differences or confirming parity in experience.
Mention and, if possible, provide examples for other editors or tools popular on Linux (such as Vim, Emacs, or JetBrains IDEs) for interacting with the MCP server.
Ensure that screenshots and file path examples are not Windows-specific (e.g., avoid backslashes or Windows-style paths).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation does not provide any OS-specific command-line examples, but it does reference .NET (which is cross-platform but often associated with Windows) for calling gRPC services. There are no explicit Linux or macOS instructions, nor are there examples using Linux-native tools or patterns. The documentation also does not mention Powershell or Windows-specific tools directly, but the absence of Linux examples and the presence of .NET references may create a subtle Windows-first impression.

Recommendations:

Include examples or references for calling gRPC services using popular Linux tools (e.g., grpcurl, grpc_cli) or languages commonly used on Linux (such as Python, Go, or Java).
Explicitly mention that .NET is cross-platform and provide instructions for Linux and macOS users where relevant.
Add a section or links for testing or interacting with gRPC APIs from Linux/macOS environments.
Ensure parity in documentation by including both Windows and Linux/macOS command-line examples where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and PowerShell examples for all Azure CLI commands, but consistently lists Bash first, followed by PowerShell. There are no exclusive Windows tools or patterns, and no steps are limited to Windows. However, the presence of PowerShell examples throughout, and the explicit '[PowerShell](#tab/psh)' tabs, indicate a bias toward Windows users, as there are no explicit Linux-specific shell examples (e.g., zsh, fish) or notes about Linux environments. All CLI examples are cross-platform, but the dual Bash/PowerShell split may suggest a Windows-centric approach.

Recommendations:

Clarify that Bash examples are suitable for Linux, macOS, and Windows (with WSL or Git Bash), and that PowerShell is available cross-platform.
Add a brief note in the prerequisites or introduction explicitly stating that all CLI commands work on Linux, macOS, and Windows.
Consider including a generic 'Shell' tab for commands that are identical across Bash and other POSIX shells, to avoid over-emphasizing PowerShell.
If relevant, mention any Linux-specific considerations (such as file permissions, environment variable syntax differences, or package dependencies) to improve Linux parity.
Ensure that any troubleshooting or advanced sections include Linux-specific guidance if Windows-specific guidance is present.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias towards Windows by referencing only the Azure portal (a web GUI) and linking to a PowerShell-based guide for enabling DDoS IP Protection, without providing equivalent CLI or Linux-native instructions. There are no examples using Azure CLI, Bash, or other cross-platform tools, and the only automation example is PowerShell-centric.

Recommendations:

Add Azure CLI (az) command examples for enabling DDoS Protection on both VNets and public IP addresses, as Azure CLI is cross-platform and widely used on Linux.
Where PowerShell scripts or references are provided, include equivalent Bash or Azure CLI commands.
Explicitly mention that the Azure portal is accessible from any OS, but provide automation examples for both Windows (PowerShell) and Linux/macOS (CLI/Bash).
Review all linked guides (such as the one for enabling DDoS IP Protection) to ensure they include cross-platform instructions, not just PowerShell.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references Windows-specific tools (PowerShell) for backend management and omits mention of Linux-native or cross-platform alternatives. No Linux command-line or scripting examples are provided, and the only CLI tool referenced is PowerShell, which is traditionally associated with Windows.

Recommendations:

Include Azure CLI examples for managing backend entities, as Azure CLI is cross-platform and widely used on Linux.
Mention and link to Azure CLI documentation alongside PowerShell in the note about backend management.
If possible, provide Bash or shell script examples for relevant tasks to ensure parity for Linux users.
Clarify that PowerShell Core is available cross-platform, if referencing PowerShell, and provide installation guidance for Linux if appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page generally avoids overt Windows bias, but there are subtle indications. The mention of configuring auto-healing via web.config and references to iisnode settings for Node.js apps are Windows/IIS-specific concepts. While there is a brief mention of running Node.js apps on Linux with PM2, there are no equivalent Linux-native examples for configuring auto-healing or process management outside of Node.js. The documentation does not provide Linux-specific guidance for features like auto-healing or configuration files, and the primary configuration example (web.config) is Windows-centric.

Recommendations:

Provide Linux-native examples for configuring auto-healing, such as using app settings or startup scripts, instead of only referencing web.config.
When mentioning iisnode or web.config, clarify that these are Windows/IIS-specific and provide equivalent guidance for Linux-based App Service environments (e.g., using PM2, environment variables, or other process managers).
Include explicit Linux configuration file examples (such as appsettings.json, environment variables, or startup scripts) alongside Windows examples.
Review all troubleshooting and best practice sections to ensure Linux and Windows parity in examples and tool recommendations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and PowerShell examples for managing access restrictions, but PowerShell examples are featured prominently, including in advanced scenarios and inline code blocks. In several places, PowerShell is presented before or alongside Azure CLI, and some advanced examples (such as multi-source rules and Azure Front Door restrictions) are only shown in PowerShell. There are no explicit Linux shell or Bash-specific examples outside of Azure CLI, and the documentation assumes familiarity with PowerShell cmdlets, which are more common in Windows environments.

Recommendations:

For every PowerShell example, provide an equivalent Azure CLI (bash-friendly) example, especially in advanced scenarios such as multi-source rules and Azure Front Door restrictions.
When presenting code tabs, consider listing Azure CLI first or at least alternating the order to avoid implicit prioritization of PowerShell.
Where possible, provide Bash shell script snippets for common tasks, especially for advanced scenarios currently only shown in PowerShell.
Clarify in the introduction that all programmatic examples are cross-platform when using Azure CLI, and explicitly mention that PowerShell examples are primarily for Windows users.
Audit all advanced scenario sections to ensure Linux users have parity in example coverage and guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for key configuration steps, but consistently lists Azure PowerShell examples after Azure CLI, which is a mild form of 'windows_first' bias. Additionally, the PowerShell examples are given equal prominence to CLI, which can be seen as 'powershell_heavy' since PowerShell is primarily a Windows-centric tool, though it is now cross-platform. There are no Linux-specific shell (bash) examples, nor are Linux-native tools or patterns (such as environment variable export commands or bash scripting) mentioned, but Azure CLI is cross-platform and generally preferred on Linux, so this is not a strong bias. No Windows-only tools or patterns are referenced, and the documentation does mention a Linux-specific configuration caveat, indicating some awareness of Linux scenarios.

Recommendations:

Add explicit bash shell examples for all Azure CLI commands to demonstrate Linux parity and usability.
Clarify in the introduction that both Azure CLI and PowerShell examples are provided, and that Azure CLI is recommended for Linux/macOS users.
Where PowerShell is used, note that it is available cross-platform, but provide bash alternatives for Linux users.
Include troubleshooting steps or notes specific to Linux environments where relevant, such as file permissions or environment variable handling.
Consider adding a section or callout summarizing differences or additional steps for Linux vs. Windows deployments, if any.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a 'windows_first' bias by providing detailed ASP.NET Core and ASP.NET Web Forms (Windows-centric) code samples before other platforms, and by referencing Windows-specific request properties (e.g., HttpRequest.ClientCertificate) without equivalent Linux or cross-platform details. There is also a 'missing_linux_example' bias: the documentation does not show how to access the client certificate directly in a Linux-native environment (e.g., using NGINX/Apache on Linux), nor does it mention Linux command-line tools (such as OpenSSL) or Linux-specific configuration patterns for mutual TLS. All code samples assume the Azure App Service's forwarding of the certificate via the X-ARR-ClientCert header, which is platform-agnostic, but the narrative and ordering favor Windows/.NET scenarios.

Recommendations:

Add explicit examples or notes for configuring and validating client certificates in Linux-native environments, such as using NGINX or Apache as a reverse proxy in front of App Service (Linux), including relevant configuration snippets.
Include Linux command-line examples (e.g., using OpenSSL) for generating, inspecting, and testing client certificates, alongside or before any Windows-centric tools.
Reorder or balance the code sample sections so that Linux-friendly stacks (Node.js, Python, Java) are presented before or alongside Windows/.NET examples, or clarify that the order is not indicative of platform preference.
Where Windows-specific properties or patterns are mentioned (e.g., HttpRequest.ClientCertificate), provide equivalent guidance for Linux or cross-platform frameworks, or clarify their applicability.
Add a section or note about how mutual TLS works in App Service (Linux) and any differences in behavior or configuration compared to App Service (Windows), if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation references the Windows file path (C:\home\site\wwwroot) first and provides a detailed explanation for Windows path conventions, while the Linux equivalent is only mentioned later and lacks example parity. There are no Linux-specific examples or screenshots, and the primary example uses a Windows-style path.

Recommendations:

Present both Windows and Linux file paths/examples together, or start with Linux if usage is equally common.
Include explicit Linux file path examples (e.g., '/home/site/wwwroot/auth.json') alongside Windows examples in all relevant steps.
Clarify any platform-specific behaviors or limitations in a side-by-side or tabbed format to ensure parity.
Add a table or section summarizing differences between Windows and Linux deployments for this feature.
Avoid assuming Windows as the default; use neutral language or alternate which platform is mentioned first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page lists Windows-related pivots and examples (Visual Studio, PowerShell, CLI) before their Linux counterparts, and includes a dedicated PowerShell section for Windows without an equivalent for Linux. This ordering and tooling focus may suggest a Windows-first perspective and a heavier emphasis on Windows-native tools.

Recommendations:

Alternate the order of Windows and Linux pivots to avoid always listing Windows first.
Ensure Linux-specific tools (such as Bash or Linux CLI) are equally represented and not grouped after Windows tools.
Provide parity for PowerShell examples by including Bash or shell script examples for Linux.
Clearly label and balance the documentation so that Linux users can easily find relevant instructions without feeling secondary.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation contains a minor Windows bias: in the troubleshooting section, only the Windows-specific command ('ipconfig /flushdns') is provided for clearing the DNS cache, with no equivalent Linux or macOS instructions. No other platform-specific tools or examples are present, and the rest of the guide is platform-neutral.

Recommendations:

Add equivalent DNS cache flush instructions for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder') alongside the Windows example.
When mentioning OS-specific troubleshooting steps, always provide parity for major platforms (Windows, Linux, macOS) or link to official documentation for each.
Consider a short note or table summarizing common DNS cache flush commands for different operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates subtle Windows bias by referencing 'Windows apps' specifically in the External Git section, without mentioning Linux or cross-platform scenarios. There are no explicit Linux-specific instructions, examples, or references, and no mention of Linux tools or shell commands. The documentation assumes a generic approach but, where it diverges, it does so in favor of Windows (e.g., 'For Windows apps, you can select External Git...'). There are no PowerShell-heavy examples or Windows-specific tools, but the lack of Linux parity in examples and terminology is notable.

Recommendations:

Replace 'For Windows apps' with 'For Windows and Linux apps' or clarify if External Git is supported for both.
Add explicit instructions or notes for Linux users, including any differences in setup or troubleshooting.
Include Linux shell command examples (e.g., git CLI usage on Linux) where relevant, especially in the Local Git section.
Ensure that any references to platform-specific features or limitations are balanced and clearly documented for both Windows and Linux.
Consider adding a table or section summarizing platform-specific considerations for continuous deployment to Azure App Service.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only a C# code example for generating the client secret JWT, which relies on Microsoft.IdentityModel.Tokens and CngKey (Windows-specific cryptography APIs). There are no examples or guidance for Linux users or for using cross-platform tools (such as OpenSSL, Python, or Node.js). This may make it difficult for developers working on non-Windows platforms to follow the instructions.

Recommendations:

Add examples for generating and signing the JWT client secret using cross-platform tools such as OpenSSL, Python (e.g., PyJWT), or Node.js (e.g., jsonwebtoken).
Mention and provide code snippets for Linux/macOS environments, ensuring that users on those platforms can easily follow the steps.
Avoid relying solely on Windows-specific libraries (e.g., CngKey, ECDsaCng) in code samples; if C# is used, show alternatives that work on .NET Core/.NET 5+ on Linux.
Explicitly state that the process can be completed on any OS, and link to or reference platform-agnostic JWT generation resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides detailed C#/.NET examples and framework-specific notes for Windows-centric technologies (ASP.NET, .NET Core), while offering only brief mentions for PHP and Java. There are no explicit Linux or cross-platform shell (e.g., Bash) examples, and the primary code sample is in C#. This may make it less accessible for developers working on Linux or with non-Windows stacks.

Recommendations:

Add code examples for popular Linux-first languages and frameworks (e.g., Python/Flask, Node.js/Express) showing how to decode and use the X-MS-CLIENT-PRINCIPAL header.
Include shell (Bash) or cross-platform command-line examples for decoding the Base64-encoded header, demonstrating how to inspect claims outside of a .NET context.
Expand the 'Framework-specific alternatives' section to include guidance for Linux-centric frameworks and runtimes (e.g., Python WSGI, Node.js, Ruby on Rails).
Ensure that examples and explanations are presented in a cross-platform manner, not assuming .NET or Windows as the default environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing App Service pricing details specifically for Windows (via the link https://azure.microsoft.com/pricing/details/app-service/windows/) and not mentioning Linux-specific App Service plans or features. There are no command-line examples (such as PowerShell or Bash), but the absence of Linux-specific guidance or parity in pricing/feature discussion is notable.

Recommendations:

Include links and information about App Service Linux pricing tiers and features alongside or before Windows equivalents.
Explicitly mention if instructions or features apply to both Windows and Linux App Service plans, or clarify any differences.
Provide examples or notes for scaling up Linux-based App Service apps if there are any platform-specific considerations.
Ensure that related documentation (such as scaling databases) references both Windows and Linux compatible services where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides command-line examples for Azure CLI and Azure PowerShell, with PowerShell examples presented alongside or immediately after CLI examples. While the content is generally cross-platform, there is a subtle Windows bias: PowerShell is a Windows-centric tool (though available on Linux, it is less commonly used there), and there are no explicit Linux shell (e.g., Bash) or native Linux tool examples. The documentation does not mention or demonstrate Linux-specific patterns or tools, and PowerShell is given equal prominence to CLI, which is more universally cross-platform.

Recommendations:

Clarify that Azure CLI examples are cross-platform and can be run in Bash or other Linux shells.
Consider providing Bash script examples or explicitly noting that Azure CLI commands are intended for Linux/macOS users as well.
If PowerShell is included, clarify its availability on Linux and provide installation guidance or links for non-Windows users.
Avoid implying that PowerShell is the default or primary automation tool for all users; instead, emphasize Azure CLI for cross-platform parity.
Where appropriate, add notes or examples for Linux-native environments, such as using Bash scripting for automation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias in the 'Hybrid Connections' section, where it specifies that the required relay agent (Hybrid Connection Manager) must be installed on a Windows Server 2012 or newer host. There is no mention of Linux support or alternatives for this agent, nor are there Linux-specific instructions or examples. The rest of the documentation is generally platform-neutral, but the omission of Linux guidance in this key networking feature is a notable gap.

Recommendations:

Explicitly state whether Hybrid Connection Manager is available for Linux, and if so, provide installation and usage instructions for Linux environments.
If Hybrid Connection Manager is Windows-only, clarify this limitation and suggest alternative approaches for Linux-based deployments.
Wherever platform-specific requirements exist, provide equivalent guidance or workarounds for Linux users to ensure parity.
Review other networking features for any implicit Windows assumptions and add Linux-specific notes or examples where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and PowerShell examples for most steps, but PowerShell is given equal prominence to Bash, and in some cases, appears before or alongside Bash rather than being secondary. There is a notable focus on Azure CLI and PowerShell scripting, which are more common in Windows environments. There are no Linux-specific tools, patterns, or troubleshooting tips, and the documentation does not address Linux-specific nuances (such as differences in base64 encoding flags or shell environment setup). The use of Azure Cloud Shell (which is Linux-based) is mentioned, but the examples and structure do not prioritize Linux-native workflows or highlight Linux-specific considerations.

Recommendations:

Prioritize Bash examples before PowerShell in all code tabs and sections, as Bash is the default shell for most Linux environments.
Add Linux-specific troubleshooting notes (e.g., differences in base64 command flags, file permissions, or environment variable syntax).
Explicitly mention that all commands are tested in Linux environments and note any differences for Windows users as secondary.
Provide a section or callout for users running native Linux (outside Azure Cloud Shell), including any prerequisites or environment setup steps unique to Linux.
Where PowerShell is shown, clarify that it is optional and primarily for Windows users, and avoid presenting it as equally standard as Bash.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias by describing the feature architecture for Windows (IIS module) before Linux/containers, and by referencing Windows-specific technologies (IIS modules) without providing equivalent technical details or links for Linux. However, the page does not provide command-line examples that are Windows-specific (e.g., PowerShell), and the configuration examples use cross-platform Azure CLI (az rest), which is not Windows-specific. There are no missing Linux examples, but the technical depth and terminology favor Windows.

Recommendations:

Present Linux and Windows architectures in parallel, or start with a neutral overview before platform-specific details.
Provide equivalent technical details and links for Linux/container deployments (e.g., link to Ambassador pattern documentation, describe the Linux authentication module in more depth).
Avoid using Windows-specific terminology (such as 'IIS module') without also explaining the Linux/container equivalent.
Where possible, include diagrams or tables that compare Windows and Linux behaviors side by side.
Ensure that all configuration and troubleshooting instructions are clearly cross-platform, and explicitly mention any differences or limitations for Linux/container environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but the PowerShell examples are always presented immediately after the CLI examples, and no explicit Linux shell or Bash scripting examples are given. The CLI examples are cross-platform, but the presence of PowerShell (a Windows-centric tool, though now available on Linux) may suggest a slight Windows bias. There are no exclusive references to Windows-only tools, but the documentation does not explicitly mention Linux or provide Linux-specific guidance or troubleshooting.

Recommendations:

Clarify that Azure CLI commands are cross-platform and can be run on Windows, macOS, and Linux.
Consider providing Bash shell scripting examples or notes for Linux users, especially for common tasks like parsing output.
If PowerShell examples are included, mention that PowerShell Core is available on Linux and macOS, or provide equivalent Bash examples.
Explicitly state that all commands shown (unless otherwise noted) work on both Windows and Linux environments.
Add troubleshooting notes or links for common issues Linux users might encounter (e.g., permissions, path differences).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page uses a pivot structure to separate instructions for different Java stacks (Tomcat, Java SE, JBoss). However, for Java SE and JBoss, only Windows-based quickstart includes are referenced, while only Tomcat has a Linux-based quickstart. This results in missing Linux examples for Java SE and JBoss, and Windows instructions are prioritized for those stacks.

Recommendations:

Provide Linux-based quickstart documentation for Java SE and JBoss stacks, similar to the Tomcat example.
Ensure that for each Java stack, both Windows and Linux deployment instructions are available and equally discoverable.
Review included files to confirm parity in content depth and clarity between Windows and Linux instructions.
Consider a unified structure where both OS options are presented side-by-side or with clear pivots for each stack.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page lists Terraform samples for Azure App Service, but the examples provided focus exclusively on Windows-based web apps and containers. There are no Linux-based app or container examples, and the scripts specifically mention 'Windows' in their titles and descriptions. This demonstrates both a 'windows_first' and 'missing_linux_example' bias.

Recommendations:

Add equivalent Terraform samples for creating Linux web apps and Linux container apps on Azure App Service.
Ensure that for every Windows-specific example, a Linux counterpart is provided and clearly labeled.
Consider reordering or grouping examples so that Linux and Windows samples are presented with equal prominence.
Explicitly mention in the documentation that both Windows and Linux are supported, and provide guidance for both platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references Windows-specific tools and patterns (such as IIS diagnostic dumps, IIS processes, and deployment webhooks for Windows apps) without mentioning Linux equivalents or clarifying Linux support. There are no examples or features highlighted for Linux-based App Service environments, and the documentation does not provide parity in describing Linux-specific Kudu features or usage.

Recommendations:

Include information about Kudu features and diagnostics available for Linux-based App Service apps, such as how to access logs, manage processes, or run commands in the Kudu console for Linux.
Clarify which features (e.g., IIS diagnostic dumps, IIS process management, deployment webhooks) are Windows-only and provide Linux alternatives or note their absence.
Add explicit examples or walkthroughs for both Windows and Linux App Service environments to ensure users on both platforms understand how to use Kudu.
Mention Linux-specific deployment patterns or troubleshooting steps where relevant, to balance the Windows focus.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation presents both Linux and Windows examples for basic app deployment, but in several cases, Windows-specific scenarios (such as Windows container apps and Windows with MySQL) are included without equivalent Linux examples. Additionally, Windows examples are sometimes listed before Linux ones, and there is no parity in the types of connected resource scenarios offered for Linux (e.g., no 'App with MySQL on Linux'). There are no command-line or tooling examples, so no PowerShell or Windows tool bias is present.

Recommendations:

Add Linux equivalents for all Windows-specific scenarios (e.g., 'App with MySQL on Linux', 'App Service plan and Linux container app').
Ensure that for each scenario (basic app, connected resources, containers), both Linux and Windows examples are provided.
Alternate the order of Linux and Windows examples or group them together to avoid implicit prioritization.
Review connected resource scenarios to ensure Linux parity (e.g., CosmosDB is Linux-only, MySQL is Windows-only; provide both combinations).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation assumes the use of GitHub Codespaces and .NET tooling, but does not provide any Linux-specific instructions or examples. All terminal commands and deployment steps are generic, but there is an implicit bias toward Windows environments (e.g., App Service, .NET, and Azure Developer CLI), and there are no explicit Linux shell or deployment examples. There are no references to Linux-specific tools, nor are there instructions for running or deploying the app on a local Linux machine or using Linux-native workflows.

Recommendations:

Add explicit instructions or notes for running the tutorial on Linux, including any differences in environment setup, terminal commands, or file paths.
Provide Linux shell command equivalents where relevant (e.g., bash instead of PowerShell, if any OS-specific commands are used).
Include a section or callout for users developing on Linux or macOS, highlighting any differences or confirming that the steps are cross-platform.
Mention and provide examples for deploying from a local Linux environment, not just Codespaces or Azure CLI.
If using .NET, clarify that the SDK and CLI are cross-platform and provide links to Linux installation guides.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is generally platform-neutral, focusing on Azure Portal UI steps. However, in the troubleshooting section about clearing DNS cache, only the Windows-specific command (`ipconfig /flushdns`) is mentioned, with no equivalent instructions for Linux or macOS. This presents a subtle 'windows_first' and 'missing_linux_example' bias.

Recommendations:

When providing troubleshooting steps involving system commands (such as clearing DNS cache), include equivalent instructions for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo resolvectl flush-caches`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
Explicitly mention that the instructions apply to all platforms, or provide platform-specific tabs or notes where commands differ.
Review other troubleshooting or command-line examples to ensure parity across Windows, Linux, and macOS environments.

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 Azure CLI or ARM template examples, which are more commonly used on Linux and cross-platform environments. No Linux-specific tools or command-line examples are mentioned, and the only automation example is Windows-centric.

Recommendations:

Add Azure CLI examples alongside PowerShell for all configuration steps, especially for enabling HTTP/2 support.
Include ARM/Bicep template snippets for declarative configuration, which are platform-agnostic.
Explicitly mention that all features are available via Azure CLI and portal, and provide links or examples.
Where PowerShell is used, provide a note or tabbed code blocks to show equivalent commands for Linux/macOS users.
Review for any other sections where only Windows tooling is referenced and ensure Linux parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation exhibits a mild Windows bias by referencing 'windowscode' tabs in links for supported file types and CRON expressions across all language pivots, regardless of whether the example is Linux-based. The links such as [supported file types](webjobs-create.md?tabs=windowscode#acceptablefiles) and [CRON expressions](webjobs-create.md?tabs=windowscode#ncrontab-expressions) default to Windows-specific documentation, even when the rest of the instructions and code samples are Linux-oriented (using Bash scripts and Linux paths). There are no explicit PowerShell or Windows command-line examples, but the persistent use of 'windowscode' in documentation links may cause confusion or suggest Windows is the primary or preferred environment.

Recommendations:

Update all links to supported file types and CRON expressions to use a neutral or Linux-appropriate tab (e.g., 'linuxcode' or a generic tab) when the language pivot is for Linux-based stacks.
Ensure that referenced documentation and screenshots reflect the OS context of the current language pivot (e.g., show Linux file structures and tools for Python, Node, PHP, Java).
Where possible, clarify in the documentation that the instructions and scripts are for Linux environments, and provide Windows equivalents only if relevant.
Consider adding a short note explaining any OS-specific differences in WebJob packaging or execution, especially if users may be deploying to both Windows and Linux App Service plans.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation references both PowerShell and Azure CLI for configuration tasks, but PowerShell (a Windows-centric tool) is consistently mentioned before Azure CLI (cross-platform) in all relevant links. There are no Linux-specific examples or tools, and the ordering of examples and links subtly prioritizes Windows/PowerShell usage.

Recommendations:

Alternate the order of PowerShell and Azure CLI references so that CLI is sometimes mentioned first, or list them alphabetically to avoid perceived prioritization.
Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
Wherever possible, provide example commands for both PowerShell and Azure CLI side by side.
Consider adding a short section or note for Linux users, clarifying that all CLI instructions are fully supported on Linux.
If relevant, include Bash shell examples or references to Linux-native tools/utilities.

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 Windows-first approach. While both PowerShell and Azure CLI are mentioned, there is an implicit prioritization of Windows tooling. No explicit Linux examples or Linux-specific tools are highlighted.

Recommendations:

List Azure CLI before PowerShell in the 'Next steps' section to avoid implying Windows-first bias, as Azure CLI is cross-platform.
Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide links to installation guides for both.
Add a note or section highlighting cross-platform support, reassuring Linux and macOS users that all configuration steps can be performed on their systems.
Where possible, provide example commands for both Azure CLI and PowerShell in the main body, not just in linked articles.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page references the procedure to use ARM templates by linking to a guide that lists 'CLI, PowerShell, ARM' in its URL and description, but does not provide explicit Linux (Bash/Azure CLI) examples or instructions on this page. The only actionable deployment method shown is the 'Deploy to Azure' button, which opens the Azure Portal, a web-based tool, but there is no mention or example of how to deploy using cross-platform tools like Azure CLI from Linux/macOS. This may lead Linux users to feel unsupported or unclear about non-Windows deployment options.

Recommendations:

Add explicit Azure CLI (Bash) examples for deploying the ARM templates, suitable for Linux/macOS users.
Mention that ARM templates can be deployed using cross-platform tools such as Azure CLI, and provide a sample command.
Ensure that references to procedures or guides do not prioritize PowerShell or Windows tools in their naming or ordering.
If linking to external guides, clarify which steps are cross-platform and which are Windows-specific.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page primarily uses Azure CLI commands and references the Azure Portal for all examples and instructions. While Azure CLI is cross-platform, there are no explicit Linux shell or script examples, nor any mention of Linux-specific tools or workflows. The documentation assumes use of the Azure Portal (a web UI) and CLI, both of which are accessible from Windows, macOS, and Linux, but does not provide parity examples for Linux-native environments or mention Linux-specific considerations. There is also no mention of PowerShell, but the absence of Linux-specific examples or references constitutes a subtle Windows/Portal bias.

Recommendations:

Include explicit Linux shell (bash) examples where relevant, especially for scripting or automation.
Mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample commands for common Linux shells.
If referencing the Azure Portal, clarify that it is web-based and platform-agnostic, but also provide CLI-only workflows for users who prefer terminal-based management.
Add troubleshooting or migration notes for users running AKS clusters on Linux-based systems, if applicable.
Consider including Helm command examples for uninstalling AGIC, as Helm is often used in Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation generally maintains parity between Windows and Linux in most answers, but in the section about how a Hybrid Runbook Worker selects the Python interpreter, only the Windows process is described in detail with explicit examples (e.g., referencing C:\Python2\python.exe and environment variables). There is no equivalent explanation or example for Linux Hybrid Runbook Workers, leaving a gap in Linux-specific guidance.

Recommendations:

Add a parallel explanation for Linux Hybrid Runbook Workers in the section about Python interpreter selection, including which environment variables are checked (e.g., PYTHON_2_PATH, PYTHON_3_PATH) and typical Linux paths (e.g., /usr/bin/python3).
Provide Linux-specific examples alongside Windows examples when describing configuration or troubleshooting steps.
Review other sections for subtle Windows-first phrasing and ensure Linux is always mentioned equally where applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation focuses exclusively on deleting Azure Automation Run As accounts using PowerShell and the Azure portal, both of which are Windows-centric tools. There are no examples or instructions for performing the task using Linux-native tools, CLI, or scripts, nor is there mention of cross-platform alternatives such as Azure CLI or REST API.

Recommendations:

Add step-by-step instructions for deleting a Run As account using Azure CLI, which is cross-platform and widely used on Linux.
Include REST API examples for advanced users who may wish to automate the process from any OS.
Explicitly mention that the Azure portal and PowerShell examples are not limited to Windows, but provide parity by showing how to perform the same actions from Linux/macOS environments.
Where PowerShell is referenced, clarify if Azure PowerShell Core (cross-platform) can be used, or provide Bash equivalents.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on Windows Communication Foundation (WCF) Relays and .NET bindings, which are primarily Windows-centric technologies. There are no examples or guidance for Linux users, nor is there mention of cross-platform alternatives or how to configure equivalent functionality on Linux systems.

Recommendations:

Include information about using Azure Relay from non-Windows platforms, such as with .NET Core/.NET 5+ (which is cross-platform) or other supported SDKs.
Provide examples or references for configuring required ports and bindings on Linux systems, including common firewall configuration commands (e.g., using iptables, ufw, or firewalld).
Mention cross-platform alternatives to WCF, such as gRPC or REST-based approaches, where applicable.
Clarify which features or bindings are Windows-only and which are available cross-platform.
Add a section or note explicitly addressing Linux/macOS users and linking to relevant setup guides.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing only Windows-based examples for the SQL Server VM (specifically 'SQL Server 2022 Developer on Windows Server 2022') and by instructing users to use SQL Server Management Studio, a Windows-only tool, for connectivity testing. There are no Linux-based deployment or client examples, nor are cross-platform tools mentioned.

Recommendations:

Include instructions and screenshots for deploying a SQL Server VM on Linux (e.g., Ubuntu or Red Hat) as an alternative to Windows.
Provide examples for connecting to the SQL Server using cross-platform tools such as Azure Data Studio, sqlcmd, or other CLI/database clients available on Linux and macOS.
Explicitly mention that the process is similar on Linux and provide any Linux-specific configuration notes (e.g., firewall, authentication).
Wherever client tools are referenced, list both Windows and Linux options, and avoid assuming the user is on a Windows machine.
Consider including bash/CLI commands for relevant steps (e.g., using Azure CLI to create resources) alongside portal instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell before Azure CLI in both instructional text and example links. PowerShell-specific instructions are provided with more detail, and the PowerShell tutorial is consistently mentioned before the CLI equivalent. There are no explicit Linux/Windows tool differences in Azure CLI or PowerShell, but the ordering and emphasis may suggest a preference for Windows-centric tooling.

Recommendations:

Alternate the order of Azure CLI and Azure PowerShell references throughout the documentation to avoid implying a preference.
Provide equal detail and prominence to both Azure CLI and PowerShell instructions and examples.
Explicitly mention that both Azure CLI and PowerShell are cross-platform, and suitable for use on Windows, Linux, and macOS.
Consider including Bash or shell script examples where appropriate, especially for tasks that can be performed outside of Azure CLI/PowerShell.
Add a note or section clarifying that all features described are accessible from both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows by only including the creation of an Azure Windows Virtual Machine in the checklist, with no mention or example of creating a Linux virtual machine. There are no Linux-specific instructions or parity in the resource creation steps, and the only VM example is Windows-based.

Recommendations:

Include steps and Terraform resource examples for creating an Azure Linux Virtual Machine (using azurerm_linux_virtual_machine) alongside or as an alternative to the Windows VM example.
Update the checklist to mention both Windows and Linux VM creation, or provide a choice for the user.
Where applicable, provide verification and troubleshooting steps that are relevant for both Windows and Linux VMs.
Ensure that any scripts, commands, or code snippets (such as those for retrieving outputs or testing connectivity) are cross-platform or include both Windows and Linux command examples.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page does not provide any OS-specific command-line examples, but the only 'Next steps' link points to a PowerShell-based tutorial, which is Windows-centric. There is no mention of Linux tools, Bash, or cross-platform CLI alternatives, and the guidance implicitly assumes a Windows-first approach by directing users to PowerShell.

Recommendations:

Provide equivalent examples and tutorials using Azure CLI (az), which is cross-platform and works on Linux, macOS, and Windows.
Include links to both PowerShell and Bash/Azure CLI tutorials in the 'Next steps' section.
Explicitly mention that configuration can be performed from any OS using the Azure Portal or Azure CLI, not just PowerShell.
Where possible, add code snippets or configuration steps for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides generic ARM template instructions without explicit OS bias in the main content, but it lacks Linux-specific examples or guidance. The only mention of Linux is in the 'Next steps' section, which links to a Linux-specific page after the main instructions, suggesting a secondary status for Linux. No Linux-specific deployment nuances or examples are provided, and the documentation does not clarify if the instructions are equally applicable to Linux and Windows VMs.

Recommendations:

Add explicit statements clarifying that the ARM template and deployment steps apply to both Windows and Linux VMs, or call out any differences.
Include a Linux-specific example or scenario, such as onboarding a Linux VM, and note any parameters or considerations unique to Linux.
Present links to both Linux and Windows guidance equally and earlier in the document, not just in 'Next steps'.
If there are OS-specific prerequisites or limitations, highlight them in the prerequisites section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by linking only to the Windows virtual machine quick-create guide in the prerequisites and not mentioning or providing links/examples for Linux virtual machines. There are no Linux-specific instructions or parity in the examples or references.

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 provide separate examples if there are differences.
Add a note or section addressing any Linux-specific considerations for using Automanage with Go SDK.
Ensure that all references to virtual machines are inclusive of both operating systems, not just Windows.

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 and not mentioning or providing examples for Linux virtual machines. There are no Linux-specific instructions, links, or considerations, 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.
Explicitly state that the Java SDK and Automanage can be used with both Windows and Linux VMs, if applicable.
Provide at least one example or note for Linux VM users, such as any differences in configuration profile assignment or prerequisites.
Ensure that terminology and instructions are platform-neutral unless a step is truly platform-specific, in which case both platforms should be covered.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows-first 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 examples or references, which may lead Linux users to feel unsupported or unsure if the instructions are applicable to their environment.

Recommendations:

Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
Explicitly state that the JavaScript SDK and Automanage features are supported for both Windows and Linux VMs, if applicable.
Provide examples or notes relevant to Linux virtual machines where appropriate.
Ensure parity in documentation references and guidance for both operating systems to avoid alienating Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by linking only to the Windows virtual machine creation guide in the prerequisites section and not mentioning or providing equivalent Linux VM instructions or examples. There are no Linux-specific references or parity in the examples or links.

Recommendations:

Add a link to the Linux virtual machine creation quickstart alongside the Windows link in the prerequisites section.
Clarify that the instructions apply to both Windows and Linux virtual machines, or specify any differences if they exist.
Include examples or notes relevant to Linux VMs where appropriate, especially if there are any platform-specific considerations.
Review all links and references to ensure both Windows and Linux users are equally supported.

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 macOS/Linux (bash), and includes both Windows and PowerShell commands, which may indicate a slight Windows-first and PowerShell-heavy bias. However, Linux/macOS instructions are present and not omitted.

Recommendations:

Rotate the order of platform instructions so that Linux/macOS (bash) examples are sometimes listed first, or present all three (cmd, PowerShell, bash) in a tabbed or parallel format to avoid implicit prioritization.
Where possible, use platform-agnostic language and tools, or clearly indicate parity between platforms.
Explicitly mention that all platforms are equally supported and provide links to platform-specific troubleshooting if needed.
Consider including screenshots or examples of running/tested workflows on Linux/macOS in addition to Windows/Visual Studio.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for policy creation and assignment, but PowerShell examples are given equal prominence and detail as CLI, and PowerShell-specific guidance is included throughout. There are no Linux-specific command-line examples (e.g., Bash scripting), nor is there mention of Linux-native tooling or considerations for Linux users. The documentation assumes familiarity with PowerShell and does not clarify cross-platform support for the provided commands.

Recommendations:

Clarify that Azure CLI commands are fully cross-platform and can be run on Windows, macOS, and Linux, while PowerShell examples may require PowerShell Core for cross-platform compatibility.
Add explicit Bash shell examples for Linux users where appropriate, especially for file creation and command execution.
Note any differences in behavior or prerequisites when running commands on Linux versus Windows (e.g., file paths, authentication methods).
Consider reordering examples to present Azure CLI (cross-platform) before PowerShell, or clearly label both as equally supported.
Include a brief section or note about running these commands on Linux systems, including installation links for Azure CLI and PowerShell Core.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently presents Azure Portal (web UI) and Azure CLI examples, but does not provide any OS-specific command-line examples (e.g., PowerShell or Bash). However, the only CLI example is shown in Azure CLI syntax, which is cross-platform, but the instructions and screenshots focus on the Azure Portal, which is most familiar to Windows users. There are no explicit Linux-specific instructions, nor are there references to Linux tools, shells, or patterns. The documentation does not mention PowerShell, but it also does not provide parity for Linux users who may prefer Bash or command-line workflows.

Recommendations:

Add explicit Bash shell examples for relevant steps, especially for users deploying from Linux environments.
Include notes clarifying that Azure CLI commands work identically on Windows, macOS, and Linux.
Provide parallel instructions for creating resources (such as service endpoints) using Azure CLI or ARM templates, not just the Azure Portal.
Add screenshots or terminal output from Linux environments to balance the visual bias toward the Azure Portal.
Where possible, mention that all steps can be performed from any OS using the Azure CLI, and provide links to cross-platform installation guides.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by listing only Azure-based copy tools such as AzCopy, Azure PowerShell, and Azure Data Factory for data backup, without mentioning Linux-native tools or providing Linux/Unix command examples. There are no examples or guidance for performing backup or recovery tasks from a Linux environment, and the tools referenced (especially Azure PowerShell) are more commonly associated with Windows workflows.

Recommendations:

Include Linux-native tools such as Azure CLI (az storage blob copy), rsync, or rclone for copying data between Blob storage accounts.
Provide example commands for both Windows (PowerShell) and Linux (Bash/CLI) environments when describing backup and recovery steps.
Explicitly mention cross-platform tools and clarify their availability on both Windows and Linux.
Add a note or section on how to perform the same operations from a Linux or macOS environment, ensuring parity in guidance.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page shows a moderate Windows bias, primarily through the emphasis on WCF Relay, which is a Windows-specific (WCF/.NET Framework) technology. WCF Relay is described as a core feature and is given equal prominence to the cross-platform Hybrid Connections, despite being Windows-only. All WCF Relay examples and quick starts are Windows-centric, with no Linux equivalents or alternatives mentioned. However, the Hybrid Connections feature is highlighted as cross-platform, and quick starts for Node.js and Java are included, indicating some effort toward Linux parity.

Recommendations:

Clearly indicate that WCF Relay is Windows/.NET Framework-specific and not available on Linux.
Add explicit notes or sections for Linux users, clarifying which features are cross-platform and which are Windows-only.
Ensure that cross-platform (Linux-friendly) quick starts and samples are listed before or alongside Windows/.NET-specific ones.
Consider providing Linux command-line or scripting examples (e.g., using curl, bash, or other common Linux tools) where relevant.
When discussing features, lead with the cross-platform Hybrid Connections and only mention WCF Relay as a legacy or Windows-specific option.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation demonstrates a mild Windows bias by referencing PowerShell before Azure CLI in deployment instructions and error handling, and by providing explicit PowerShell parameter usage examples. While Azure CLI is mentioned, PowerShell is consistently listed first and receives more detailed treatment. There are no Linux-specific examples, and the documentation does not mention Linux tools or shell environments.

Recommendations:

Present Azure CLI and PowerShell instructions in parallel, or alternate which is listed first to avoid implying preference.
Provide explicit Linux shell (bash) examples for deploying ARM templates, including command-line syntax and parameter usage.
Include a section or callout for Linux/macOS users, clarifying that all steps are cross-platform and providing any OS-specific notes if needed.
Where error messages reference PowerShell, also show the equivalent CLI/Linux troubleshooting steps.
Avoid using 'PowerShell' as the default or primary example unless there is a technical reason to do so.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides an explicit example of consuming exported variables using PowerShell syntax (echo "$env:myBuildSetting"), but does not provide equivalent examples for Linux shells (such as Bash). There are no references to Linux-specific tools or patterns, and the only code example is Windows/PowerShell-centric. This may make it less accessible for users running pipelines on Linux agents or those more familiar with Bash.

Recommendations:

Provide equivalent Bash/Linux shell examples alongside the PowerShell example, e.g., echo "$myBuildSetting" or echo "$MYBUILDSETTING".
Explicitly mention that exported variables are available as environment variables in both Windows and Linux agents, and show how to access them in both environments.
If there are any platform-specific considerations (such as case sensitivity in environment variables), document them.
Review screenshots and UI instructions to ensure they are not Windows-only, or add notes if the experience differs on Linux/Mac agents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a subtle Windows bias by referencing Visual Studio Credential as the first and only concrete example of a development environment credential, which is primarily a Windows tool. There are no explicit Linux or cross-platform command-line examples (such as Azure CLI or Bash), nor are Linux development environments mentioned. The instructions for role assignment are given exclusively via the Azure Portal UI, with no mention of CLI or scripting alternatives, which are often preferred in Linux environments.

Recommendations:

Include Azure CLI and/or PowerShell command-line examples for role assignment, ensuring both Windows and Linux users can follow along.
Mention cross-platform development environments (e.g., VS Code, JetBrains Rider) and their credential options alongside Visual Studio.
Provide explicit Linux/macOS development workflow examples, such as using DefaultAzureCredential with the Azure CLI logged-in user.
Clarify that the Azure Portal is accessible from any OS, but also provide automation-friendly alternatives for role assignment.
Where possible, avoid listing Windows-centric tools or workflows first; instead, present cross-platform options or alternate between them.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates some Windows bias, particularly in the 'Build and run the app locally' section. Windows command prompt and PowerShell instructions are listed before Linux/macOS equivalents, and screenshots and instructions reference 'Command Prompt or PowerShell window' specifically. However, Linux/macOS commands are present, and Visual Studio Code is mentioned as cross-platform. There are no missing Linux examples, but the ordering and language prioritize Windows environments.

Recommendations:

Present environment variable instructions for Windows, macOS, and Linux in parallel (e.g., in a table or side-by-side), or list Linux/macOS first in some cases.
Use neutral language such as 'terminal window' instead of 'Command Prompt or PowerShell window' when referring to where the app is run.
Include screenshots or references to Linux/macOS terminals as well as Windows.
Ensure that all code and command examples are explicitly tested and confirmed to work on Linux/macOS, and note any platform-specific differences.
Where possible, avoid assuming the user is on Windows (e.g., do not say 'restart the command prompt' without also mentioning restarting the terminal on Linux/macOS).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides environment variable setup instructions with Windows Command Prompt and PowerShell examples before macOS and Linux, indicating a 'windows_first' bias. Additionally, both Windows Command Prompt and PowerShell are given separate, detailed sections, while Unix-like systems (macOS and Linux) are grouped together and presented after Windows, which is a common 'powershell_heavy' and 'windows_first' pattern. However, Linux and macOS instructions are present, and the rest of the tutorial is cross-platform.

Recommendations:

Present all platform instructions (Windows Command Prompt, PowerShell, macOS, Linux) in a tabbed or parallel format, without prioritizing Windows over others.
Group macOS and Linux separately if there are meaningful differences, or clarify when instructions are identical.
Consider leading with a neutral, cross-platform example (e.g., using .NET CLI or environment variable setting in code) before platform-specific instructions.
Explicitly state that all steps are applicable on Windows, macOS, and Linux, and avoid language that implies Windows is the default or primary platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides command-line examples for running curl using the Windows (cmd) prompt syntax (```cmd), and does not show equivalent Linux/macOS shell examples. The use of Azure Portal is platform-neutral, but the lack of explicit Linux or cross-platform command-line instructions (e.g., bash) and the use of Windows-first code block markers may cause confusion or suggest a Windows bias.

Recommendations:

Provide both Windows (cmd/PowerShell) and Linux/macOS (bash/sh) command-line examples for commands such as curl.
Use platform-neutral code block markers (e.g., ```shell) for commands that work across platforms, or provide separate blocks for each OS.
Explicitly mention that the Maven commands and curl examples work on Linux/macOS as well, or show both variants if there are differences.
Consider including screenshots or instructions for using the Azure CLI (which is cross-platform) for resource management tasks, as an alternative to the Azure Portal.

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, without mentioning or linking to Linux or macOS equivalents. All code and CLI examples are cross-platform, but the setup guidance assumes a Windows-first perspective.

Recommendations:

In the prerequisites, provide links to Python installation/setup documentation for Linux and macOS, alongside the Windows link.
Explicitly state that the code and CLI examples work on all major platforms (Windows, Linux, macOS).
If there are any platform-specific considerations (e.g., environment variable syntax differences), mention them or provide examples for both Windows and Linux/macOS.
Consider adding a note or section for common Linux/macOS development environments, such as using virtual environments or installing dependencies.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before macOS/Linux (bash), and includes both Windows command prompt and PowerShell examples. While Linux/macOS commands are present, Windows instructions are consistently listed first and in greater detail, which may suggest a subtle Windows-first bias. There are no missing Linux examples, but the ordering and emphasis favor Windows users.

Recommendations:

Alternate the order in which OS-specific instructions are presented, or group them in tabs so no platform is prioritized.
Use neutral language such as 'If you use Windows/macOS/Linux...' rather than always listing Windows first.
Ensure all command-line examples are equally detailed for all platforms.
Consider providing a single cross-platform command (where possible) or a summary table for environment variable setup.
Explicitly state that all steps are supported on Windows, Linux, and macOS at the beginning of the relevant sections.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page focuses exclusively on the Azure portal and does not provide any command-line examples. Where it does reference the CLI, it does not specify or provide examples for Linux or cross-platform usage. The only implementation link provided is for .NET, which is more commonly associated with Windows environments, and there are no references to Linux-specific tools, shell commands, or alternative platforms.

Recommendations:

Add explicit CLI examples for both Azure CLI (az) and PowerShell, ensuring parity between Windows and Linux command syntax.
Include instructions or links for implementing chat completion configuration in languages and frameworks popular on Linux (e.g., Python, Node.js).
When referencing the CLI, clarify that Azure CLI is cross-platform and provide example commands for both Bash (Linux/macOS) and PowerShell (Windows).
Expand the 'Continue to the following instructions' section to include quickstarts or guides for Linux-friendly languages and environments.
Ensure screenshots and UI instructions are supplemented with equivalent CLI or code-based steps for automation and scripting, which are common on Linux.

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 macOS/Linux equivalent. Both Windows shells are described in detail, while the Linux/macOS example is presented last. No Linux-specific tools or patterns are omitted, but the ordering and explicitness favor Windows users.

Recommendations:

Present environment variable setup instructions for all platforms in parallel (e.g., a table or side-by-side code blocks), or begin with Linux/macOS to avoid implicit prioritization of Windows.
Avoid giving two separate Windows shell examples before the Linux/macOS example; consider grouping by platform or using tabs.
Explicitly state that the instructions apply equally to all platforms, and ensure Linux/macOS users do not feel like an afterthought.
Where possible, provide parity in troubleshooting or platform-specific notes (e.g., how to persist environment variables on Linux shells if set in a terminal session).

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 or mention of Linux-specific shell usage. There are no explicit PowerShell or Windows-only tool references, but the file path examples and lack of Linux parity suggest a subtle Windows bias.

Recommendations:

For every CLI example using a Windows path (e.g., C:/Users/john/Downloads/data.json), add a parallel example using a Linux/macOS path (e.g., /home/alice/data.json).
Explicitly state that the Azure CLI commands work cross-platform (Windows, Linux, macOS) and that file paths should be adapted to the user's OS.
Where file paths are shown in parameter tables, provide both Windows and Linux/macOS variants.
Consider including a note or tabbed examples for Bash and PowerShell if there are any shell-specific considerations.
Review screenshots and ensure they do not exclusively show Windows environments if possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for all deployment, review, and cleanup steps. However, PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every example can be seen as a Windows bias. Additionally, PowerShell examples are always presented immediately after CLI, which is the cross-platform tool, but there is no mention of Linux-specific shell environments or considerations. There are no Linux-only examples or explicit references to Linux tools or patterns.

Recommendations:

Clearly state that Azure CLI commands work natively on Linux, macOS, and Windows, and are the recommended cross-platform approach.
Consider providing Bash shell script examples or mentioning that the CLI commands can be run in Bash or other Linux shells.
If PowerShell is included, clarify that it is available cross-platform (PowerShell Core), or note any differences for Windows PowerShell vs. PowerShell Core.
Add a note or section for Linux/macOS users highlighting any OS-specific considerations, such as file paths or prerequisites.
Ensure that Linux and macOS users are explicitly addressed in the prerequisites and deployment instructions.

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 macOS/Linux. The Windows and PowerShell commands are listed first, with the Linux/macOS example last. There are no Linux-specific tools or patterns missing, but the ordering prioritizes Windows environments.

Recommendations:

Present environment variable setup instructions for all platforms in parallel, or list Linux/macOS first to balance the order.
Use tabbed or collapsible sections for platform-specific instructions to give equal prominence to Windows, PowerShell, and Linux/macOS.
Ensure that any future troubleshooting or tool references include Linux/macOS equivalents alongside Windows tools.
Explicitly state that the .NET SDK and Azure App Configuration are cross-platform, and that the instructions apply equally to all supported operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides environment variable setup instructions for Windows Command Prompt and PowerShell before macOS/Linux, and includes both Windows and Linux/macOS examples. However, Windows-specific tools (setx, PowerShell) are always mentioned first, which may subtly prioritize Windows workflows. There are no missing Linux examples, but the ordering and emphasis could be improved for parity.

Recommendations:

Present environment variable instructions in a platform-neutral order, or alternate which platform appears first.
Consider grouping all OS instructions together in a table or tabbed format to avoid implicit prioritization.
Explicitly state that all .NET CLI commands work identically on Windows, Linux, and macOS to reinforce cross-platform parity.
Where possible, avoid Windows-specific tools (like setx) as the default, or provide a brief explanation of their Linux/macOS equivalents.
Ensure screenshots and terminal output are shown from both Windows and Linux/macOS terminals, or use a neutral terminal style.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias by recommending Docker Desktop as a prerequisite and not mentioning Linux-native alternatives (such as Docker Engine or Podman). All command-line examples are cross-platform (az CLI, dotnet, kubectl, helm), but there are no explicit Linux-specific instructions or troubleshooting notes. The documentation assumes the user will use Docker Desktop, which is primarily a Windows/macOS tool, and does not acknowledge that Linux users typically use Docker Engine or other container runtimes. There are no PowerShell-specific commands or Windows command prompt syntax, but the lack of Linux-specific notes or alternatives for Docker installation is a subtle bias.

Recommendations:

In the prerequisites, mention Docker Engine (for Linux) as an alternative to Docker Desktop, and provide a link to installation instructions for both.
Where Docker Desktop is referenced, clarify that Linux users should use Docker Engine or Podman, and provide relevant links.
Add a note or section indicating that all CLI commands are cross-platform and can be run in Bash, PowerShell, or other shells.
If any troubleshooting or file path instructions are OS-specific, provide both Windows and Linux/macOS examples.
Consider adding a table or callout summarizing installation steps for required tools (Docker, kubectl, helm, etc.) on both Windows and Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias towards Windows by focusing exclusively on an ASP.NET Core application (commonly associated with Windows development), omitting any Linux-specific instructions or examples, and not mentioning platform differences in Docker or Azure CLI usage. There are no explicit PowerShell or Windows-only commands, but the lack of Linux parity is evident in the absence of alternative examples or notes for Linux users.

Recommendations:

Include explicit notes or sections clarifying that all CLI and Docker commands work cross-platform, and highlight any differences for Linux/macOS users.
Provide at least one example using a non-Windows development stack (e.g., a Node.js or Python app) to illustrate broader applicability.
Mention that Docker Desktop is available for Windows, macOS, and Linux, and provide links or instructions for Linux installation.
If any commands or steps differ on Linux (such as file path syntax or environment variable conventions), call these out in side notes or tabs.
Add troubleshooting tips for common Linux/macOS issues (e.g., Docker permissions, case sensitivity in file names).

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 detailed Windows-specific guidance (e.g., setx and PowerShell commands). Linux/macOS instructions are present but always listed last. The prerequisites section links only to Windows-specific Python setup documentation, omitting Linux/macOS equivalents.

Recommendations:

Present environment variable instructions for Windows, macOS, and Linux in parallel (e.g., in a table or side-by-side tabs) rather than always listing Windows first.
Include links to official Python installation/setup documentation for Linux and macOS in the prerequisites section, not just Windows.
Ensure that Linux/macOS commands and workflows are given equal prominence and clarity as Windows examples.
Consider using a neutral, cross-platform approach (e.g., using Python's os.environ in code or referencing platform-agnostic tools) where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides environment variable setting instructions for Windows Command Prompt and PowerShell before mentioning Linux/macOS equivalents. Windows-specific tools (cmd, PowerShell) are described in detail, with Linux/macOS commands listed last. However, all major steps are covered for both platforms, and there are no missing Linux examples or exclusive use of Windows tools.

Recommendations:

Present Linux/macOS and Windows instructions in parallel tabbed sections, rather than listing Windows first.
Avoid giving Windows-specific instructions (cmd, PowerShell) priority over Linux/macOS; consider alphabetical or usage-based ordering.
Where possible, use cross-platform commands or highlight platform differences without bias.
Explicitly mention that all steps are supported on Linux/macOS, and provide troubleshooting tips for those environments if needed.

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 gives detailed PowerShell and Windows Command Prompt examples. Linux/macOS instructions are present but always listed last. There are no missing Linux examples, but the ordering and explicit mention of Windows tools first indicate a subtle Windows-first bias.

Recommendations:

Present Linux/macOS and Windows instructions in parallel tabs or side-by-side, rather than always listing Windows first.
Consider listing Linux/macOS instructions first, or randomizing the order across documentation pages to avoid implicit prioritization.
Where possible, use cross-platform commands (e.g., via the Azure CLI) as the primary example, and provide OS-specific instructions only as needed.
Explicitly state that all platforms are supported equally, and ensure parity in example detail and placement.
Review other documentation pages for similar ordering and adjust for consistency.

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 equivalent Linux/macOS bash command. Windows-specific tools (setx, PowerShell) are described in detail, with Linux/macOS instructions grouped together and placed last. There are no missing Linux examples, but the ordering and detail favor Windows users.

Recommendations:

Present environment variable instructions for Linux/macOS first or in parallel with Windows, rather than always listing Windows first.
Use tabbed or side-by-side formatting for OS-specific instructions to give equal prominence to Linux/macOS and Windows.
Briefly explain any Windows-specific tools (like setx) and provide context for Linux/macOS users if similar tools are needed.
Ensure that any troubleshooting or advanced sections also provide Linux/macOS guidance where relevant.
Consider including a table summarizing environment variable commands for all platforms at the start of the section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias, particularly in the 'Prerequisites' and 'Run the application' sections. Windows installation and environment variable instructions are mentioned before Linux/macOS equivalents, and Windows-specific tools (setx, PowerShell) are called out explicitly. However, Linux/macOS instructions are present and correct, and the code samples themselves are cross-platform.

Recommendations:

Present environment variable instructions in a neutral or parallel order (e.g., group Windows, PowerShell, and Linux/macOS together or alternate which comes first).
In the 'Prerequisites' section, link to both Windows and Linux/macOS Node.js installation guides, or use a neutral landing page.
Where Windows-specific tools (e.g., setx, PowerShell) are mentioned, ensure Linux/macOS equivalents are given equal prominence and not as an afterthought.
Consider using tabbed or side-by-side formatting for OS-specific instructions to visually reinforce parity.
Review for subtle language that implies Windows is the default or primary platform.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is focused exclusively on ASP.NET Core and C# (.NET), which are traditionally associated with Windows development, and does not provide equivalent examples or guidance for Linux-first or cross-platform frameworks (such as Java, Python, Node.js). There are no explicit Linux or cross-platform instructions, and the prerequisite tutorial is for ASP.NET Core, reinforcing a Windows-centric approach.

Recommendations:

Provide equivalent code samples and setup instructions for popular Linux-friendly languages and frameworks (e.g., Python with Flask, Node.js, Java Spring).
Include guidance on configuring auto-reload of secrets/certificates in non-.NET environments, especially those commonly deployed on Linux.
Clarify that the approach is cross-platform if applicable, and mention any OS-specific considerations.
Link to or reference tutorials for other platforms, not just ASP.NET Core.
Explicitly state OS requirements or parity, and ensure that Linux users are not excluded by omission.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. In the prerequisites, it links only to Windows-specific Python setup documentation, omitting Linux or macOS equivalents. When instructing users to set environment variables, Windows command prompt and PowerShell instructions are listed before Linux/macOS, and Windows-specific tools (setx, PowerShell) are explicitly mentioned. However, Linux/macOS instructions are present and correct, and the code samples themselves are cross-platform.

Recommendations:

In the prerequisites, provide links to official Python installation/setup guides for Linux and macOS, not just Windows.
When listing environment variable setup commands, present all platforms equally (e.g., group by OS or use tabs for each platform), or rotate the order in which platforms are presented.
Where Windows-specific tools (e.g., setx, PowerShell) are mentioned, ensure Linux/macOS equivalents are described with equal prominence and detail.
Consider adding a brief note at the start clarifying that all instructions are applicable to Windows, Linux, and macOS, and that platform-specific steps are provided for each.

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 given equal prominence to CLI, which can be seen as a Windows-centric approach. There is no explicit Linux bias, but the inclusion of PowerShell as a primary tool and its parity with CLI may disadvantage Linux/macOS users, for whom PowerShell is less common. Additionally, the order of presentation sometimes puts PowerShell before or alongside CLI, rather than prioritizing cross-platform tools.

Recommendations:

Prioritize Azure CLI examples before PowerShell, as CLI is more universally available and familiar to Linux/macOS users.
Clearly indicate that PowerShell is optional and primarily for Windows users, while CLI is cross-platform.
If PowerShell is included, provide a brief note or link on how to install and use PowerShell on Linux/macOS, or clarify its intended audience.
Ensure that all steps and examples are fully cross-platform, and avoid assuming familiarity with Windows-specific tools or patterns.
Consider adding explicit Linux/macOS shell examples where relevant, especially for common tasks like navigation or environment setup.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both Azure CLI and Azure PowerShell examples for creating the function app in Azure, but consistently lists Azure PowerShell (a Windows-centric tool) alongside or immediately after Azure CLI, without mentioning Linux-native alternatives or clarifying cross-platform compatibility. There are no explicit Linux shell (bash/zsh) or macOS-specific instructions, and PowerShell is given equal prominence to the CLI, which may suggest a Windows-oriented bias.

Recommendations:

Clearly state that Azure CLI commands work cross-platform (Windows, Linux, macOS), and consider listing CLI examples before PowerShell to emphasize platform neutrality.
Add explicit bash/zsh (Linux/macOS shell) command examples or notes where relevant, especially for steps involving environment variables, file paths, or shell-specific syntax.
Clarify in the prerequisites and tool installation sections that PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for all platforms.
Where PowerShell is shown, consider providing a corresponding bash/zsh example or a note indicating that the CLI commands are suitable for Linux/macOS users.
Review included snippets and links to ensure they do not assume a Windows file system or shell environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for creating the function app in Azure, but consistently lists Azure PowerShell after Azure CLI and does not mention or provide Linux-specific shell examples (e.g., bash/zsh). There is no explicit Windows-only tooling, but the presence of PowerShell as a first-class option and the lack of Linux-specific notes or troubleshooting tips suggest a mild Windows bias.

Recommendations:

Add explicit bash/zsh/Linux shell examples alongside Azure CLI and PowerShell, especially for common tasks such as file editing, environment variable management, or troubleshooting.
Include notes or troubleshooting tips relevant to Linux/macOS users (e.g., differences in using Ctrl+C, file permissions, or path formats).
Clarify that Azure CLI commands are cross-platform and, where relevant, provide example terminal prompts or screenshots from both Windows and Linux/macOS environments.
Consider providing parity in scripting examples, such as bash scripts for automation, not just PowerShell.
Review screenshots and instructions to ensure they are not Windows-centric (e.g., avoid only showing Windows terminal output).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by linking exclusively to the Windows-specific App Service pricing page and referencing the App Service plan primarily in the context of Windows hosting. There are no explicit Linux or cross-platform examples, and the terminology and links default to Windows-centric resources.

Recommendations:

Include links to both Windows and Linux App Service pricing pages, or clarify that the information applies to both platforms.
Explicitly mention Linux support for App Service plans and provide examples or notes where behavior may differ between Windows and Linux hosting.
Where relevant, reference both Windows and Linux tools or workflows for managing and scaling App Service plans.
Add clarifying statements or links for users deploying on Linux, especially regarding features like Always On and scaling.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally avoids OS-specific bias, but in the 'Limit scale-out' section, both Azure CLI and Azure PowerShell examples are provided, with PowerShell given its own tab. In the 'Scale-in behaviors' section, a specific note is made for 'app running on Windows in a Consumption plan', with no equivalent mention for Linux. There are no Linux shell or bash examples, and the only OS-specific scenario called out is for Windows. This subtly prioritizes Windows and PowerShell users, and omits parity for Linux users.

Recommendations:

Add explicit bash/Linux shell examples alongside Azure CLI and PowerShell, especially for configuration changes.
When mentioning Windows-specific behaviors (such as drain mode), clarify whether there are differences for Linux, or state explicitly if there are none.
If PowerShell is given a dedicated example, consider providing equivalent bash scripting for Linux users.
Review all examples and notes to ensure Linux users are equally represented and not left to infer behavior or commands.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page exhibits a subtle Windows bias by specifying 'os = windows' as the default in the Gradle configuration block, without mentioning or providing guidance for Linux or macOS users. The runtime OS setting is presented as 'windows' without alternatives, and there is no discussion of cross-platform deployment or local development differences. While command-line examples use Bash and cURL (which are cross-platform), the documentation implicitly assumes Windows as the primary target environment.

Recommendations:

Explicitly mention that the 'os' property in the Gradle configuration can be set to 'linux', and provide an example or table showing possible values and their implications.
Add a note or section for Linux/macOS users, clarifying any differences in setup, deployment, or supported Java versions (e.g., Java 21 is Linux-only).
Ensure that screenshots, instructions, and references to the Azure portal or CLI are platform-neutral or include platform-specific notes where relevant.
Consider providing a sample build.gradle snippet for Linux users, or at least mention that the default 'windows' value can be changed.
Review the documentation for any other implicit assumptions (such as file paths or environment variable syntax) that may be Windows-specific, and provide cross-platform guidance.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses the Azure Portal (web UI) for all steps and does not provide any command-line examples. There are no references to Windows-specific tools or PowerShell, but also no mention of Linux or cross-platform CLI alternatives (such as Azure CLI or Azure Functions Core Tools). This omission results in a bias by not addressing users who prefer or require command-line or Linux-native workflows.

Recommendations:

Add parallel instructions using Azure CLI and Azure Functions Core Tools for each step, including Cosmos DB account creation, function app deployment, and trigger setup.
Include code snippets for creating and managing resources via CLI, making it clear these commands work on Linux, macOS, and Windows.
Explicitly mention that all portal-based steps can be performed from any OS, but provide links or references to CLI-based documentation for users on Linux or who prefer automation.
Where screenshots or UI steps are given, consider adding CLI equivalents in expandable sections or as alternative workflows.

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 tab is present and the CLI examples use variable assignment syntax that is compatible with Bash (Linux/macOS) but not with Windows CMD. There are no explicit Windows-only tools, but PowerShell is a Windows-centric shell, and its inclusion as a primary tab can indicate a slight Windows bias. However, the main workflow (Terraform, Azure CLI) is cross-platform and the function app is explicitly stated to run on Linux.

Recommendations:

Clarify in the Azure CLI section that the examples are intended for Bash (Linux/macOS/WSL) and provide equivalent CMD syntax for Windows users.
Consider adding a note that Azure PowerShell is available cross-platform, but is most familiar to Windows users.
If possible, add a third tab for Windows CMD users, or clarify that PowerShell is the preferred shell for Windows.
Ensure that all shell commands are tested on both Linux/macOS and Windows environments, and document any differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively uses Windows Server as the example operating system for the virtual machine, with no mention of Linux alternatives or instructions. All screenshots, instructions, and default choices are Windows-centric, and there are no parallel steps or notes for deploying or accessing the function app from a Linux VM. This creates a Windows-first impression and omits guidance for users preferring or requiring Linux environments.

Recommendations:

Include 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 provide guidance for both.
Add notes or sections on how to connect to a Linux VM via Azure Bastion (using SSH), including any differences in browser-based access.
Ensure that any command-line or deployment steps (such as function deployment) include both Windows (PowerShell/Command Prompt) and Linux (Bash) examples where relevant.
Review all screenshots and UI instructions to ensure they are not exclusively Windows-focused, or provide Linux equivalents where the experience differs.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias toward Windows by exclusively using Azure Portal (web UI) instructions, which are platform-agnostic but omit any command-line examples. There are no CLI-based instructions (such as Azure CLI, PowerShell, or Bash), which are important for Linux users and automation. Additionally, there is no mention of Linux-specific tools or workflows, nor are there any examples using Bash or Linux shell commands.

Recommendations:

Add parallel instructions using Azure CLI commands for all steps (creating the function app, queue, and adding messages), with example commands that work on Linux and macOS.
Include Bash shell examples for interacting with Azure Storage queues, such as using az storage queue create and az storage message put.
Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide links to CLI documentation.
If PowerShell is mentioned in other related pages, ensure Bash/Linux equivalents are always provided and given equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently presents Windows as the default or primary operating system for Azure Functions, with explicit statements such as 'This tutorial uses C# and Windows' and 'This tutorial uses Windows but also works for Linux.' However, there are no Linux-specific instructions, screenshots, or examples provided. All steps and guidance are oriented around the Azure Portal UI, which is cross-platform, but the language and defaults reinforce a Windows-centric approach. There are no CLI, PowerShell, or Bash examples, but the lack of Linux parity is evident in the absence of Linux-specific guidance or troubleshooting.

Recommendations:

Explicitly provide parallel instructions and examples for Linux users, including any differences in setup or behavior.
Where the tutorial states 'This tutorial uses Windows but also works for Linux,' add a section or callout with Linux-specific considerations or steps.
Include screenshots or CLI commands (e.g., Azure CLI, Bash) that demonstrate how to perform the same actions on Linux systems.
If there are no differences, explicitly state that the steps are identical for Linux, and provide confirmation or validation steps for Linux environments.
Consider alternating the order of mention (e.g., 'Windows or Linux') or providing a neutral phrasing to avoid reinforcing Windows as the default.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally provides parity between Windows and Linux, offering explicit tabs and templates for both platforms and most languages. However, there is a subtle Windows-first bias: Windows is consistently listed before Linux in tabbed sections, and PowerShell (a Windows-centric shell) is included as a primary language example, even though it's less common on Linux. There are no missing Linux examples, and Linux is acknowledged as the only supported OS for Python. No Windows-only tools or patterns are mandated, but the ordering and language focus suggest a mild preference for Windows.

Recommendations:

Alternate the order of Windows and Linux tabs or present Linux first in some sections to avoid implicit prioritization.
Where PowerShell is shown, also provide Bash or shell script equivalents, especially for cross-platform scenarios.
Explicitly state that all workflows and tools are supported equally on both Windows and Linux where applicable.
Consider including a general-purpose shell scripting example (Bash) alongside PowerShell to better serve Linux users.
Review language and screenshots to ensure equal representation of both OS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is primarily focused on Windows-based Azure Functions, as explicitly stated in the introduction. It only provides examples and instructions for C# class library functions on Windows, with no equivalent Linux or cross-platform guidance. There are also references to Azure Files as the default file system for Windows deployments, but no mention of Linux file system options or differences in deployment patterns. The tutorial does not provide Linux-specific steps or highlight any differences for Linux-based function apps.

Recommendations:

Explicitly state in the introduction whether the steps are applicable to Linux-based function apps, and if not, provide a parallel Linux tutorial or note the differences.
Include Linux-specific instructions and examples, especially for ARM template configuration, environment variable settings, and deployment considerations.
Discuss storage options and behaviors for Linux function apps, such as how Azure Files is not the default for Linux Consumption plans, and provide guidance for secret management in those scenarios.
Where platform-specific behaviors exist (e.g., the use of AzureWebJobsStorage__accountName in Linux Consumption), provide clear, step-by-step Linux examples.
Ensure parity in prerequisites and tooling, mentioning any Linux-compatible tools or SDKs required for the tutorial.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally aims for cross-platform parity, but there is a subtle Windows bias. Visual Studio (Windows-only) is consistently listed first in C# sections, and Windows tools like PowerShell and Microsoft Edge Network Console are highlighted among HTTP test tools. Linux-specific tools or workflows are not given equal prominence or called out explicitly, and there are no Linux-first examples or mentions of Linux-specific editors or shells.

Recommendations:

Alternate the order of environment/tool listings so that Windows-only tools (e.g., Visual Studio) are not always listed first. For example, sometimes list Visual Studio Code or command-line options before Visual Studio.
Explicitly mention and provide examples for Linux/macOS shells (e.g., bash, zsh) where 'command prompt or terminal' is referenced, and clarify that these instructions apply equally to Linux/macOS.
In the HTTP test tools section, include Linux-native tools (e.g., httpie, wget) alongside curl, and avoid listing PowerShell or Microsoft Edge before cross-platform or Linux-native tools.
Where possible, add screenshots or example commands from Linux terminals in addition to Windows/PowerShell.
Call out any platform-specific differences or considerations, especially for file paths, environment variables, or tool installation steps.
Consider a dedicated section or callout for Linux/macOS users, especially in areas where the workflow or tooling may differ.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively references SQL Server Management Studio (SSMS), a Windows-only tool, and does not mention or provide guidance for Linux or cross-platform alternatives. There are no examples or instructions for connecting from Linux environments or using tools available on Linux.

Recommendations:

Include instructions for connecting to Azure Government SQL Server from cross-platform tools such as Azure Data Studio, sqlcmd, or other command-line utilities available on Linux.
Add a section or examples for Linux and macOS users, detailing how to configure and connect using supported tools.
Mention the platform limitations of SSMS and suggest alternatives for non-Windows users.
Ensure parity in documentation by providing equivalent steps and screenshots for Linux/macOS tools where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash (Linux/macOS) and Cmd (Windows) examples for all command-line steps, ensuring cross-platform coverage. However, in every case, the Windows (Cmd) examples are presented after the Bash examples, which may subtly prioritize Linux. There is no exclusive use of Windows tools (such as PowerShell), but the documentation does use Windows-specific command syntax (Cmd) alongside Bash. There are no missing Linux examples, and all tools used (Azure CLI, Maven, Azure Functions Core Tools) are cross-platform. There is no mention of PowerShell, only Cmd. The documentation is slightly 'powershell_heavy' in the sense that it uses Windows command prompt syntax, but not actual PowerShell. The bias is minimal and mostly in the order of presentation ('windows_first' bias would be present if Windows examples came first, but here Bash comes first).

Recommendations:

Consider presenting both Bash and Cmd examples side-by-side or in a tabbed interface (as is already done), but clarify that both are equally supported.
Explicitly mention that all tools and commands are cross-platform and supported on Windows, Linux, and macOS.
Optionally, include PowerShell examples for Windows users who prefer PowerShell over Cmd.
Ensure that any troubleshooting or environment setup steps (such as setting environment variables) include notes for both Bash and Windows (Cmd/PowerShell) users.
Continue to avoid referencing Windows-only tools or patterns unless a Linux/macOS equivalent is also provided.

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 shown, but the OS recommendation is clear and exclusive.

Recommendations:

Provide parallel instructions for creating the function app using Linux as the operating system, including any differences in configuration or limitations.
Add a note clarifying whether the steps and features (such as VNet Integration and NAT Gateway) are fully supported on Linux-based function apps, and link to relevant documentation.
If there are differences in the portal UI or required settings for Linux, include screenshots and step-by-step guidance for Linux users.
Mention other supported runtime stacks (e.g., Node.js, Python) and clarify if the tutorial is applicable to them, especially on Linux.
Avoid recommending Windows as the default unless there is a technical reason; if so, explain the reason and provide guidance for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally maintains parity between Linux and Windows, but there is a subtle Windows bias in the ordering and references. Windows is often listed first in tables and explanations, and some links (such as App Service plan pricing) default to Windows. There are no explicit Linux command-line or deployment examples, but also no Windows/Powershell examples, so the bias is mostly in ordering and framing rather than in example content.

Recommendations:

Alternate the order in which Windows and Linux are presented in tables and explanations, or use alphabetical order to avoid implicit prioritization.
Where pricing or documentation links are provided, ensure both Linux and Windows options are equally visible and accessible.
Add explicit Linux-focused examples or notes where relevant, especially in sections discussing deployment, scaling, or troubleshooting.
Clarify when features are Linux-only or Windows-only, and provide guidance for users of both platforms.
Review terminology to ensure that neither platform is implied as the default or primary option.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation includes a code sample for installing npm packages using PowerShell syntax (npm install --save-dev style-loader css-loader) and does not provide a corresponding Linux/macOS shell example. The only explicit command-line example uses PowerShell, and there is no mention of Linux or cross-platform shell usage. This may lead Linux or macOS users to feel the documentation is Windows-centric.

Recommendations:

Provide shell command examples using a generic shell prompt (e.g., $ or #) or include both Windows (PowerShell/cmd) and Linux/macOS (bash/sh) command examples.
Explicitly mention that the npm commands work across platforms, or note any platform-specific differences if they exist.
Avoid using PowerShell-specific prompts (>) unless the example is truly Windows-only.
Consider adding a note or section for Linux/macOS users, especially when discussing local development, npm, or bundler configuration.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is generally cross-platform and browser/JavaScript focused, but there is a subtle Windows bias in the proxy service example, which uses an .ashx handler (a Windows/IIS/ASP.NET-specific pattern). There are no explicit Linux or cross-platform proxy service examples, and the documentation does not mention how to implement the proxy on non-Windows platforms. No PowerShell or Windows command-line examples are present, but the only server-side implementation detail given is Windows-specific.

Recommendations:

Replace or supplement the .ashx proxy service example with cross-platform alternatives, such as Node.js (Express), Python (Flask), or Nginx proxy configurations.
Explicitly mention that the proxy service can be implemented in any language or platform, and provide links or code snippets for Linux-friendly implementations.
Avoid referencing Windows/IIS/ASP.NET-specific file extensions or handlers as the default or only example.
Add a note or section on deploying the proxy service on Linux-based environments (e.g., Azure App Service for Linux, Docker containers, etc.).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally provides parity between Windows and Linux, with explicit sections and code samples for both platforms throughout. However, there is a recurring pattern of presenting Windows examples and terminology before Linux equivalents (windows_first). Additionally, PowerShell is highlighted as a primary deployment method, with detailed PowerShell scripts and references, while Linux-native shell (bash) or cross-platform CLI examples are less emphasized (powershell_heavy). There are no significant omissions of Linux examples, but the ordering and tool emphasis may subtly prioritize Windows users.

Recommendations:

Alternate the order of Windows and Linux examples, or present Linux examples first in some sections to balance visibility.
Where PowerShell is shown, also provide equivalent bash/Azure CLI scripts for Linux/macOS users, especially in deployment and validation sections.
In lists of deployment options, avoid always listing PowerShell before CLI or portal; consider grouping by cross-platform tools first.
Explicitly state that all examples are cross-platform unless otherwise noted, and highlight any platform-specific differences up front.
Ensure that all referenced sample repositories and templates include both Windows and Linux variants, and link to both equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The tutorial assumes and instructs users to use Visual Studio Code (VS Code) and its integrated terminal for all steps, including installing Python packages and opening Jupyter Notebooks. There are no references to Linux-specific environments, tools, or alternative editors (such as JupyterLab, classic Jupyter Notebook, or command-line usage). All instructions and screenshots are tailored to the Windows/VS Code experience, with no mention of Linux or macOS workflows, terminal commands, or potential differences in file management or environment setup.

Recommendations:

Add explicit instructions for Linux and macOS users, including how to install Python packages using a standard terminal (e.g., bash/zsh) and how to open Jupyter Notebooks using JupyterLab or the classic Jupyter Notebook interface.
Include alternative steps for opening notebooks outside of VS Code, such as using the command line: `jupyter notebook EVrouting.ipynb` or `jupyter lab EVrouting.ipynb`.
Mention that the tutorial works on all major operating systems (Windows, Linux, macOS) and highlight any OS-specific considerations (such as file paths or package installation nuances).
Provide screenshots or notes that reflect the experience on Linux (e.g., GNOME Terminal, KDE Konsole) and macOS (Terminal.app), or at least clarify that the steps are similar across platforms.
Avoid implying that Visual Studio Code is required; clarify that any Jupyter-compatible environment can be used.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a bias toward Windows by explicitly noting that certain metrics are not supported or available for Linux plans, without providing Linux alternatives or guidance. Additionally, the documentation often describes features and metrics in the context of Windows or general App Service plans, with Linux-specific limitations mentioned as exceptions rather than being treated equally or first.

Recommendations:

Provide equivalent Linux examples or guidance where metrics or features are not supported, including workarounds or alternative monitoring strategies for Linux-based Azure Functions.
Clearly indicate feature parity (or lack thereof) in a dedicated section, and link to up-to-date tracking or roadmap items for Linux support.
Where features are unavailable on Linux, suggest best practices or third-party tools that Linux users can leverage for similar monitoring needs.
Avoid presenting Windows/App Service plan features as the default; instead, structure documentation to address both Windows and Linux scenarios equally, or lead with Linux where possible to balance historical bias.

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 connection strings, it references patterns and file names (such as 'local.settings.json' and 'Application settings') that are more familiar to Windows/Azure Portal users. There are no explicit Linux or cross-platform command-line examples (e.g., Bash, Linux environment variables), and the documentation does not mention Linux-specific tools or patterns for managing environment variables or configuration. The .NET examples dominate, and there is no mention of Linux shell usage or parity in configuration management.

Recommendations:

Include Linux/Bash shell examples for setting environment variables and managing configuration, especially for local development and deployment scenarios.
When referencing configuration files (like 'local.settings.json'), clarify how these are used or mapped in Linux environments, including deployment via CLI or containers.
Provide parity in code and configuration examples for both Windows and Linux environments, such as showing how to set connection strings using Azure CLI or environment variables in Bash.
Mention cross-platform tools (e.g., Azure CLI) and provide examples for both PowerShell (Windows) and Bash (Linux/macOS) where relevant.
Avoid assuming the reader is using Windows or the Azure Portal for configuration; explicitly address both Windows and Linux workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page shows a mild Windows bias by listing 'Connect with PowerShell' before 'Connect with CLI' in the Quickstarts section, and by highlighting PowerShell as a primary tool for connecting to Azure Government. There is also a focus on Visual Studio, a Windows-centric IDE, before mentioning cross-platform SDKs. No explicit Linux examples or Linux-specific tools are highlighted, and the ordering subtly prioritizes Windows/PowerShell workflows.

Recommendations:

Reorder the Quickstarts section to list cross-platform tools (CLI, Python SDK) before or alongside PowerShell and Visual Studio.
Explicitly mention Linux and macOS compatibility for CLI and SDK tools.
Add links or references to Linux/macOS setup guides for Azure CLI and SDKs.
Include examples or quickstart links that demonstrate connecting to Azure Government from Linux environments.
Balance tool mentions by including cross-platform editors (e.g., VS Code) alongside Visual Studio.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) and omitting any Linux or cross-platform development environment instructions. All configuration steps and code samples assume use of Visual Studio and ASP.NET Core, with no mention of Linux tools, editors, or deployment patterns. There are no examples or guidance for Linux users.

Recommendations:

Include instructions for setting up and configuring the application using cross-platform tools such as VS Code, JetBrains Rider, or command-line interfaces available on Linux.
Provide equivalent steps for Linux users, such as editing configuration files and running .NET Core applications using the dotnet CLI.
Add notes or sections that explicitly mention Linux compatibility and any differences in file paths, environment variables, or deployment steps.
Demonstrate how to deploy and test the application locally on Linux (e.g., using dotnet run) and how to register applications without relying on Visual Studio.
Ensure that all code/configuration samples are platform-agnostic or provide both Windows and Linux variants where necessary.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation assumes the use of a local Azure CLI installation and mentions the absence of Azure Cloud Shell in Azure Government, but does not provide explicit Linux/macOS installation or usage examples. It also references launching a browser for authentication, which may behave differently on Linux. There is no mention of Linux-specific considerations or alternative authentication flows.

Recommendations:

Add explicit instructions or notes for installing and using Azure CLI on Linux/macOS, including package manager commands (e.g., apt, yum, brew).
Clarify how the 'az login' browser-based authentication behaves on Linux and provide alternatives (such as device code login) if needed.
Mention any Linux-specific prerequisites or troubleshooting steps.
Include screenshots or terminal output examples from Linux environments.
If possible, provide parity with Cloud Shell by suggesting alternative Linux-compatible shells or containers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively demonstrates the creation of a Windows-based virtual machine ("Data Science Virtual Machine - Windows 2016 CSP") and only describes connecting to the VM via RDP, with no mention of Linux VM options or SSH access. All examples and screenshots are centered around Windows workflows, and there are no Linux or cross-platform alternatives provided.

Recommendations:

Include parallel instructions for creating a Linux-based virtual machine (e.g., Ubuntu, CentOS) alongside the Windows example.
Demonstrate how to connect to a Linux VM using SSH, and provide example commands for different platforms (Windows, macOS, Linux).
Mention and show how to select Linux images from the Azure Government marketplace.
Ensure screenshots and step-by-step instructions are not Windows-centric and reflect cross-platform usage.
Add a section or note about differences in provisioning and connecting to Windows vs. Linux VMs in Azure Government.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by recommending the use of Guidgen.exe (a Windows/Visual Studio tool) for generating GUIDs, without mentioning any Linux or cross-platform alternatives. There are no command-line or tool examples for Linux users, and the only tool explicitly referenced is Windows-specific.

Recommendations:

Mention cross-platform or Linux-native GUID generation tools, such as uuidgen (available on most Linux distributions) or online GUID generators.
Provide example commands for generating GUIDs on Linux/macOS (e.g., `uuidgen` in bash) alongside the Windows/Guidgen.exe example.
Review the documentation for other tool or workflow recommendations to ensure Linux and macOS users have clear, equivalent instructions.
Where possible, use neutral language and tool recommendations that apply to all platforms, or always provide both Windows and Linux/macOS alternatives.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a subtle Windows bias, particularly in its references to cryptographic validation and authentication. It repeatedly cites Windows-specific FIPS 140 validation programs and the use of Windows cryptographic modules as the basis for compliance. While it mentions that Azure uses both Linux and Windows, the detailed compliance and validation examples, as well as references to authentication modules, are Windows-centric. There are no Linux-specific examples, tools, or validation pathways described, and Windows is consistently mentioned first or exclusively in technical compliance contexts.

Recommendations:

Include explicit references to Linux-based cryptographic modules and their FIPS 140 validation status within Azure, if available.
Provide parity in compliance documentation by describing how Linux-based workloads and authentication methods meet CJIS and FIPS 140 requirements.
Add examples or guidance for Linux administrators (e.g., using OpenSSL or Linux-native tools) in relevant sections, especially where Windows tools or modules are highlighted.
Clarify whether Azure's compliance and security assurances apply equally to Linux-based services and workloads, and provide links to Linux-specific compliance resources if available.
Avoid referencing only Windows validation programs; instead, present a balanced view of both Windows and Linux compliance mechanisms.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation only describes how to find the subscription ID via the Azure portal, which is a graphical interface accessible from any OS, but does not mention command-line alternatives. There are no examples for Linux users (e.g., using Azure CLI), nor are there any PowerShell or Windows-specific tools, but the lack of CLI instructions may disadvantage Linux users who prefer or require terminal-based workflows.

Recommendations:

Add instructions for finding the subscription ID using Azure CLI, which is cross-platform and commonly used on Linux.
If mentioning PowerShell, ensure equivalent Azure CLI examples are provided and presented with equal prominence.
Explicitly state that the portal method works on all operating systems, but also provide terminal-based alternatives for users who may not use a GUI.
Consider including a table or section comparing methods (Portal, Azure CLI, PowerShell) to ensure parity and user choice.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently references Visual Studio Code (VS Code) and its terminal, but all instructions and screenshots assume a Windows environment. There are no explicit mentions or examples for Linux or macOS users, such as alternative ways to open files, install packages, or use Jupyter Notebooks outside VS Code. The 'Open Jupyter Notebook' section describes right-clicking and menu options specific to Windows Explorer and VS Code on Windows, with no mention of Linux file managers or command-line alternatives.

Recommendations:

Add instructions and screenshots for opening Jupyter Notebooks on Linux and macOS, including command-line alternatives (e.g., 'code weatherDataMaps.ipynb' or 'jupyter notebook weatherDataMaps.ipynb').
Clarify that pip commands can be run in any terminal (not just the 'Visual Studio terminal'), and provide guidance for Linux/macOS users (e.g., using 'python3 -m pip' if needed).
Mention that VS Code is cross-platform and provide links or notes about installing and using it on Linux/macOS.
Where file paths are referenced (e.g., './data/weather_dataset_demo.csv'), clarify that these are POSIX-style and will work on Linux/macOS, but also note any differences if relevant.
Include a note or section on using Jupyter Notebooks outside of VS Code, such as with the standalone JupyterLab or classic Jupyter Notebook interface, which are common on Linux.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented towards Autodesk's AutoCAD® software, which is primarily a Windows application. All CAD command examples and screenshots are based on AutoCAD, with no mention of Linux-compatible CAD tools or workflows. There are no examples or instructions for preparing drawing packages using Linux-based tools, nor is there guidance for users who may not have access to AutoCAD or Windows environments.

Recommendations:

Include references to cross-platform or Linux-compatible CAD software (e.g., LibreCAD, BricsCAD, DraftSight) and clarify which features/commands are required from the CAD tool.
Provide equivalent instructions or workflows for preparing DWG files and manifest files using Linux-based tools, or at least acknowledge the limitations and suggest alternatives.
Add screenshots and command references from at least one Linux-compatible CAD application.
Clarify any requirements that are specific to AutoCAD and suggest workarounds or alternatives for users on non-Windows platforms.
Consider providing a table or appendix comparing CAD commands and features across popular Windows and Linux CAD tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation references PowerShell limitations in a prominent callout and includes a shared include file about CLI & PowerShell, but does not provide any Linux-specific (bash, shell, or Linux CLI) examples or mention Linux-native tools. The only command-line context is PowerShell, and the documentation does not clarify parity or provide Linux-first or cross-platform examples, which may lead Linux users to feel unsupported.

Recommendations:

Add explicit Linux CLI (bash/az CLI) examples alongside or before PowerShell references.
Clarify whether all steps and tools are supported equally on Linux and Windows, especially for SAP HANA administrators who are often on Linux.
Replace or supplement the '[Application volume group CLI & PowerShell limitation]' include with a cross-platform note, or provide a Linux-specific limitations section if applicable.
Where screenshots or UI steps are shown, add notes or examples relevant to Linux environments (e.g., mounting NFS volumes from Linux hosts).
Ensure that any references to command-line tools or scripts are provided in both PowerShell and bash/az CLI formats.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by listing 'Windows Service' as a primary example of a daemon application and omitting explicit Linux equivalents (such as 'systemd service' or 'Linux daemon'). There are no command-line examples, but all references to hosting environments and tools are Azure-centric or Windows-first, with no mention of Linux-specific patterns, tools, or terminology. No Linux or cross-platform CLI examples are provided for key tasks such as certificate management or service hosting.

Recommendations:

Include Linux-specific examples of daemon applications, such as 'systemd service' or 'Linux background process', alongside 'Windows Service'.
When discussing hosting environments, explicitly mention Linux-based Azure hosting options (e.g., Azure App Service for Linux, Azure Virtual Machines running Linux) and on-premises Linux servers.
Provide cross-platform or Linux-specific instructions for tasks like certificate management (e.g., using OpenSSL), secret storage, and service registration.
Add example commands or scripts for both Windows (PowerShell) and Linux (Bash) where relevant, especially for authentication flows and API requests.
Use neutral terminology such as 'background service' or 'daemon' rather than only 'Windows Service' to ensure inclusivity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation shows 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 or macOS shell examples, and the use of the PowerShell prompt (>) may confuse users on other platforms. However, the overall content is largely cross-platform JavaScript/HTML, and no Windows-specific tools or patterns are otherwise promoted.

Recommendations:

Replace PowerShell prompt (>) in npm install commands with a generic shell prompt ($) or omit the prompt entirely to avoid confusion.
Explicitly mention that npm commands work on Windows, Linux, and macOS, and provide examples using the standard shell prompt.
Where command-line instructions are given, provide both Windows (PowerShell/cmd) and Linux/macOS (bash/zsh) examples if there are any differences.
Add a note clarifying that all JavaScript and npm instructions are cross-platform unless otherwise stated.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation consistently uses PowerShell syntax (e.g., 'npm install ...' and 'npm run build' shown as PowerShell code blocks) for all command-line examples, which may suggest a Windows-centric approach. There are no explicit Linux or macOS shell examples, nor any mention of platform-specific considerations for non-Windows users. While the content itself is cross-platform (Node.js/npm/webpack), the exclusive use of PowerShell code blocks and lack of bash/sh alternatives can be perceived as a Windows-first bias.

Recommendations:

Provide all command-line examples in both PowerShell and bash (or generic shell) formats, or use neutral code blocks without specifying a shell.
Add a note clarifying that all commands work on Windows, Linux, and macOS, and mention any platform-specific differences if applicable.
Where possible, use the 'sh' or no language tag for npm commands, as they are cross-platform.
Consider including screenshots or instructions for running the project on Linux/macOS, or at least acknowledge those platforms in the prerequisites or installation sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation generally presents Windows support and features before or more prominently than Linux equivalents, especially in recent release notes. For example, new features for Microsoft SQL Server on Windows are highlighted, and Windows support is called out as a major milestone. However, there are no explicit examples or instructions tailored for Linux users, nor are Linux-specific tools or patterns discussed, despite the tool supporting both platforms. This may give the impression of a Windows-centric focus and leaves Linux users with less guidance.

Recommendations:

When introducing new features, provide parity in examples and explanations for both Windows and Linux platforms.
Explicitly mention Linux support and features alongside Windows, rather than after or as an aside.
Include Linux-specific configuration examples, troubleshooting tips, and references to common Linux tools or patterns where relevant.
Ensure that documentation for environment variables, configuration files, and command usage includes Linux shell and scripting examples, not just generic or Windows-centric instructions.
Highlight any differences or considerations for Linux users, such as file paths, permissions, or service management, to improve clarity and usability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation is organized to present Windows and SQL Server solutions before Linux and open-source solutions in several sections, and references to Windows-specific tools (e.g., DFS Namespaces, FSLogix, SMB, Windows DFS-N) are present. However, Linux solutions are also well-represented, especially for SAP, Oracle, and HPC workloads. There are no clear cases of missing Linux examples where a Windows example is present, and Linux tools and patterns are included where relevant.

Recommendations:

Reorder sections or present Linux and Windows solutions in parallel to avoid the perception of Windows-first bias.
When referencing Windows-specific tools (e.g., DFS Namespaces, FSLogix), ensure that Linux/NFS equivalents or alternatives are also mentioned and linked where possible.
In sections like Virtual Desktop Infrastructure, provide explicit guidance or references for Linux-based VDI solutions if supported.
Where possible, use neutral terminology (e.g., 'file sharing' instead of 'SMB file sharing') and clarify when a solution is cross-platform.
Add a summary table or matrix mapping solution types to both Windows and Linux workloads to highlight parity and available guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively using the Azure portal for all configuration steps, without providing any command-line examples (such as Azure CLI or PowerShell). While the Azure portal is cross-platform, the lack of CLI examples means users on Linux or those preferring automation/scripting are not served. There are no Linux-specific instructions or examples, and no mention of Linux tools or shell commands.

Recommendations:

Add Azure CLI examples for all configuration steps (e.g., adding managed identities, configuring upstream settings, setting Key Vault permissions).
Include PowerShell examples as an option, but ensure Azure CLI (which is cross-platform) is presented first or alongside.
Explicitly mention that all steps can be performed from Linux, macOS, or Windows using the CLI, and provide sample commands.
Where screenshots are used, consider including CLI output or code blocks to improve accessibility for non-Windows users.
Review for any UI-specific instructions that may differ between OSes and clarify as needed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation demonstrates a mild Windows bias in the feature registration section, where Azure PowerShell commands are presented first and most prominently, with Azure CLI (cross-platform) only mentioned in passing. However, the main workflow examples for converting NFS volumes and client-side operations are Linux-centric, using Linux commands and file paths. There are no exclusive Windows tools or missing Linux examples in the core NFS conversion steps.

Recommendations:

Present Azure CLI commands alongside Azure PowerShell commands in the feature registration section, giving them equal prominence and example code blocks.
Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users, while PowerShell is often used on Windows.
Consider providing a brief note or example for users managing NFS mounts from Windows (if supported), or clarify that the workflow is intended for Linux/UNIX clients.
Maintain parity in all command-line examples by offering both PowerShell and CLI alternatives where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias by presenting Azure PowerShell commands first for feature registration and status checking, with Azure CLI commands mentioned only as an alternative in text. The only explicit command-line examples for feature registration are in PowerShell, while the rest of the process uses Azure CLI and REST, which are cross-platform. There are no Linux-specific examples or guidance, but the CLI and REST steps are platform-agnostic.

Recommendations:

Provide Azure CLI command examples alongside or before PowerShell examples for feature registration and status checking.
Explicitly state that all CLI and REST commands work on Linux, macOS, and Windows.
Where PowerShell is used, offer equivalent Bash/Linux shell commands if possible.
Add a note or section clarifying that the instructions are cross-platform and do not require Windows or PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally maintains parity between Windows and Linux, but in the 'Observing user quota settings and consumption' section, Windows client instructions are presented before Linux client instructions, and Windows-specific tools (Windows Explorer, dir command) are mentioned explicitly. Linux instructions are present and use the standard quota(1) tool, but the ordering and explicit mention of Windows tools indicate a mild 'Windows-first' and 'windows_tools' bias.

Recommendations:

Alternate the order of client instructions (e.g., present Linux first in some sections or use a neutral ordering such as alphabetical).
Explicitly mention equivalent tools or commands for both platforms in parallel, rather than describing Windows tools in more detail or first.
Where possible, provide screenshots or examples for both platforms with equal prominence.
In the 'Next steps' section, consider linking to Linux/UNIX identity documentation alongside the Windows Security Identifiers link.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias by mentioning Windows VMs and SMB mapping on Windows VMs before Linux equivalents, and by omitting explicit instructions or examples for Linux when discussing SMB shares. While NFS mounting is mentioned for both Windows and Linux VMs, SMB mapping is only described for Windows, with no mention of Linux SMB clients or usage.

Recommendations:

Provide explicit examples or instructions for mounting Azure NetApp Files SMB shares on Linux VMs, including references to common Linux tools (e.g., mount.cifs, smbclient).
When listing supported platforms or use cases, mention Linux and Windows in parallel (e.g., 'You can mount Azure NetApp Files NFS volumes on both Windows and Linux VMs. You can map SMB shares on both Windows and Linux VMs.').
Include links to relevant Linux documentation or guides for both NFS and SMB usage.
Review all integration scenarios to ensure Linux is given equal prominence and technical detail as Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by providing an Azure PowerShell example first for checking feature registration, with the Azure CLI (cross-platform) alternative only mentioned in passing and without a full example. No Linux-specific tools or shell commands are shown, and the only explicit code block is for PowerShell. However, the rest of the document is largely platform-neutral, and there is a reference to Linux performance benchmarks.

Recommendations:

Provide both Azure PowerShell and Azure CLI examples in code blocks, with equal prominence and detail.
Consider listing the Azure CLI (which is cross-platform and commonly used on Linux) example before or alongside PowerShell, not after.
Where possible, include Linux shell command examples (e.g., using az CLI in bash) to demonstrate parity.
Ensure that any references to tools or commands are balanced between Windows and Linux environments, or clearly indicate cross-platform compatibility.
If referencing performance benchmarks for Linux, consider also referencing any available for Windows, or clarify if Linux is the primary supported/tested platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation presents Windows (SMB) client instructions before Linux (NFS) client instructions, and provides more detailed, step-by-step guidance for Windows users (including both GUI and command-line options with screenshots). Windows-specific tools and patterns (File Explorer, dir command) are mentioned and illustrated, while the Linux section is more concise and only covers the df command. There is no evidence of missing Linux examples, but the ordering and depth favor Windows.

Recommendations:

Alternate the order of Windows and Linux sections, or present them in parallel to avoid implicit prioritization.
Provide equivalent depth for Linux instructions, such as including both GUI (if available, e.g., GNOME Files) and CLI examples, and screenshots for Linux tools.
Mention Linux-specific nuances or alternative commands (e.g., using 'lsblk', 'stat', or graphical disk utilities) where appropriate.
Ensure REST API and CLI sections reference cross-platform usage equally, and avoid linking PowerShell as the only scripting example.
Explicitly state that both Windows and Linux are equally supported and provide parity in troubleshooting tips and caveats.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation primarily uses Azure PowerShell commands for feature registration, with Azure CLI (cross-platform) only mentioned secondarily and without example syntax. This prioritizes Windows/PowerShell usage and may disadvantage Linux or macOS users who typically use Azure CLI.

Recommendations:

Provide Azure CLI command examples alongside PowerShell for all steps, not just a mention.
Present Azure CLI and PowerShell examples in parallel or with equal prominence, rather than PowerShell first.
Explicitly state that both Azure CLI and PowerShell can be used on all platforms, and link to installation guides for both.
Consider including Bash shell examples for relevant operations, especially for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides both Linux (NFS) and Windows (SMB) client instructions for restoring files from snapshots, with clear parity in basic restore steps. However, the Windows section includes additional restore options (using the 'Previous Versions' tab) and multiple screenshots, whereas the Linux section is limited to command-line instructions without mention of graphical tools or advanced features. The Windows instructions also reference Windows-specific UI elements and tools, potentially giving the impression of richer support or easier workflows on Windows.

Recommendations:

Add information about graphical file managers on Linux (e.g., Nautilus, Dolphin) and how users can access the .snapshot directory and restore files using a GUI, similar to the Windows screenshots.
If available, mention any Linux desktop environment features or third-party tools that provide snapshot browsing or file restoration (e.g., GNOME's file versioning, Timeshift, or integration with NetApp snapshots).
Include screenshots for the Linux workflow to match the visual guidance provided for Windows users.
If Windows 'Previous Versions' is highlighted, clarify whether there are equivalent features or recommended alternatives for Linux users, or explicitly state if such features are not available.
Ensure that advanced options or tips are presented for both platforms, or note platform-specific limitations to maintain transparency and parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides only Azure Portal (GUI) instructions and omits any command-line examples. There is no mention of PowerShell or Windows-specific tools, but the lack of CLI examples (such as Azure CLI or Bash) means Linux users do not have parity. The instructions do not reference Linux-specific tools or workflows, nor do they provide cross-platform command-line guidance.

Recommendations:

Add Azure CLI examples for deleting a volume, including sample commands that work on Linux, macOS, and Windows.
If applicable, include PowerShell examples, but ensure they are presented alongside Azure CLI/Bash examples to maintain parity.
Explicitly mention that the deletion can be performed via CLI and provide links to relevant CLI documentation.
Clarify any OS-specific steps for unmounting the volume (e.g., provide both Linux and Windows unmount instructions).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation for Azure NetApp Files generally maintains cross-platform parity, frequently referencing both Linux (NFS) and Windows (SMB) use cases. However, there is a notable emphasis on Windows-centric features and terminology, particularly around SMB, Active Directory, and Windows client behaviors. Windows tools and patterns (e.g., Windows File Explorer, NTFS, Windows client, FSLogix, Citrix App Layering, SQL Server on Windows) are mentioned more often and sometimes before their Linux/NFS equivalents. Some features are described with a Windows-first perspective, such as access-based enumeration and non-browsable shares, where the behavior is explained in terms of Windows client experience. There are also several features that are only relevant to Windows/SMB environments, with less emphasis on Linux/NFS-only enhancements.

Recommendations:

Where features are described in terms of Windows client experience (e.g., access-based enumeration, non-browsable shares), add equivalent explanations for Linux/NFS clients or clarify if the feature is not applicable.
When listing protocol support or describing new features, present NFS (Linux) and SMB (Windows) use cases in parallel, rather than defaulting to Windows-first explanations.
For features that are SMB/Windows-specific, explicitly state their relevance and, where possible, provide links or references to comparable Linux/NFS features or best practices.
Ensure that examples, troubleshooting steps, and user scenarios include both Linux and Windows perspectives where applicable.
Highlight Linux/NFS-only enhancements with equal prominence as Windows/SMB features to reinforce cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias, particularly in the ordering and depth of examples. In the VM-level monitoring section, Windows examples (Explorer, dir command, screenshots) are presented first and in greater detail, followed by Linux examples. In the CLI/PowerShell section, PowerShell screenshots and references are prominent, with no explicit Linux shell (bash) command-line examples or screenshots, even though Azure CLI is cross-platform. There are no exclusive Windows-only tools, but the documentation tends to prioritize Windows workflows and visuals.

Recommendations:

Alternate the order of Windows and Linux examples in sections to avoid always presenting Windows first.
Provide equivalent bash/Azure CLI command-line examples and screenshots alongside PowerShell examples, especially in the CLI/PowerShell section.
Include more detailed Linux workflow descriptions and visuals where possible (e.g., showing Linux file manager properties for mapped drives, if applicable).
Explicitly state that Azure CLI commands work identically on Linux, macOS, and Windows, and show examples in a Linux terminal.
Where possible, balance the number of screenshots and depth of explanation between Windows and Linux sections.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exclusively describes the process of moving an Azure Relay namespace using the Azure Portal, with all instructions and screenshots based on the portal's UI. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there any references to Linux tools or workflows. The only technical reference outside the portal is to Windows Communication Foundation (WCF) relays, a Windows-centric technology. This results in a bias toward Windows and GUI-based workflows, potentially disadvantaging Linux users or those who prefer automation and scripting.

Recommendations:

Add step-by-step instructions for exporting, editing, and deploying the Resource Manager template using Azure CLI and/or Azure PowerShell, and ensure Azure CLI examples are provided (as it is cross-platform and widely used on Linux).
Include sample Bash commands for unzipping the template and editing JSON files, or reference common Linux tools for these tasks.
Mention that the Azure Portal is accessible from any OS, but provide parity for users who prefer or require command-line or automated approaches.
Clarify the role of WCF relays and, if possible, provide context or alternatives for users not on Windows platforms.
Ensure that all screenshots and instructions are not overly specific to Windows UI conventions (e.g., file explorer paths, right-click context menus) and use neutral language where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides command-line configuration examples using 'dotnet user-secrets set' and references to 'web.config', both of which are more familiar to Windows users. There are no explicit Linux or cross-platform shell examples (e.g., bash), nor is there mention of Linux-specific configuration files or patterns. The documentation does not clarify if the commands or configuration steps differ on Linux, and it omits any Linux shell equivalents or guidance for Linux-based deployments.

Recommendations:

Add explicit bash/zsh shell examples for setting environment variables or secrets, especially for 'dotnet user-secrets set', to show parity with Windows cmd usage.
Clarify that 'dotnet user-secrets' works cross-platform, or provide alternative instructions for Linux environments if needed.
Include examples of configuring connection strings via environment variables, which is a common pattern on Linux and in containerized deployments.
Mention and provide samples for using 'appsettings.json' (already referenced in some sections) as the primary configuration file, which is cross-platform.
When referencing 'web.config', note that this is specific to IIS/Windows hosting, and provide guidance for equivalent configuration on Linux (e.g., using environment variables or appsettings.json).
Ensure that all command-line instructions are either cross-platform or have both Windows and Linux/macOS variants.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page is mostly cross-platform in its language and instructions, but it exhibits subtle Windows bias by referencing the Azure Storage Emulator (which is Windows-only) without mentioning or prioritizing its cross-platform replacement, Azurite. There are no explicit Linux/macOS-specific instructions or troubleshooting notes, and no shell or command-line examples that are unique to Linux/macOS. The documentation does not provide PowerShell-specific commands or Windows command prompt examples, but it does reference a Windows-only tool as the default for local storage emulation.

Recommendations:

Replace references to 'Azure Storage Emulator' with 'Azurite', which is cross-platform and recommended for all OSes.
Explicitly mention that all CLI commands (e.g., mvn, func) work on Windows, macOS, and Linux, and note any OS-specific prerequisites or differences.
Add troubleshooting notes or links for common Linux/macOS issues (such as file permissions, path separators, or Java installation).
If screenshots or UI steps are shown, ensure they are not Windows-only, or provide equivalent Linux/macOS visuals or notes.
Where possible, provide parity in instructions for all major platforms, especially for local development tools and environment setup.

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 their cross-platform availability or Linux alternatives. There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-specific workflows or tools.

Recommendations:

Clarify that sqlpackage is available cross-platform (Windows, Linux, macOS), and provide instructions or examples for Linux users (e.g., how to install and run sqlpackage on Linux).
Avoid referencing only Windows-specific tools like SQLPackage.exe; instead, use 'sqlpackage' and link to cross-platform installation guides.
Include Linux command-line examples (e.g., using bash, curl, or az CLI) for uploading files to Azure Blob storage and running sqlpackage.
Mention any differences or considerations for Linux users, such as file paths, permissions, or container volume mounts.
Ensure parity in instructions and terminology for both Windows and Linux environments throughout the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and PowerShell examples for compressing files, but Bash is presented first and more prominently. There is no exclusive focus on Windows tools, and Linux workflows are included throughout, especially in the deployment steps. However, the explicit labeling of 'Use Bash' and 'Use PowerShell' and the inclusion of PowerShell commands may indicate a slight Windows bias, especially since PowerShell is not as commonly used on Linux. All other steps use cross-platform tools (Azure CLI, git, npm), and there are no Windows-only tools or patterns.

Recommendations:

Ensure that both Bash and PowerShell examples are given equal prominence and are clearly marked as platform-specific (e.g., 'For Linux/macOS' and 'For Windows').
Consider providing a table or side-by-side comparison for commands that differ by platform, rather than listing Bash first and PowerShell second.
Explicitly mention which OS each command is for, and clarify that Bash commands work on Linux/macOS and PowerShell on Windows.
If possible, provide a note about using Windows Subsystem for Linux (WSL) for Windows users who prefer Bash, to further support Linux parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and PowerShell examples for Docker commands, but consistently lists the PowerShell (Windows) example after the Bash (Linux) example. However, the PowerShell examples are present throughout, which may suggest a slight Windows bias. There is also a notable focus on Docker volume mapping caveats for Windows and macOS, but Linux-specific issues are not discussed. No Linux-specific tools or patterns are omitted, and the documentation generally assumes a Linux-style file system layout. There are no missing Linux examples, but the presence of PowerShell examples in every code block may suggest a 'parity' bias toward Windows users.

Recommendations:

Continue to provide both Bash and PowerShell examples, but clarify when each should be used (e.g., 'For Linux/macOS, use Bash; for Windows, use PowerShell').
Consider listing Bash (Linux) examples first, as Azure SQL Edge is primarily Linux-based.
Add a brief section or note about common Linux-specific issues or troubleshooting tips, to balance the Windows/macOS caveats.
If possible, provide a table or tabbed interface for code examples, allowing users to select their OS/shell, rather than listing both inline.
Ensure that any references to file paths or permissions include both Linux and Windows equivalents where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation instructs users to 'open a command prompt' and uses backslashes in file paths, both of which are Windows-centric. There are no explicit Linux or cross-platform instructions or examples, and no mention of Linux-specific tools or terminal usage.

Recommendations:

Replace 'open a command prompt' with 'open a terminal or command prompt', or specify both Windows and Linux/Mac instructions.
Provide both Windows (backslash) and Linux/Mac (forward slash) path examples.
Include a note or section for Linux/Mac users, such as using Terminal and navigating with appropriate commands.
Verify that all steps and referenced scripts are cross-platform, or provide platform-specific guidance where necessary.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page lists several tools for working with Azure SQL Edge, with a notable emphasis on Windows-centric tools such as SQL Server Management Studio (SSMS) and SQL Server Data Tools in Visual Studio, both of which are primarily Windows applications. While cross-platform tools like Azure Data Studio and Visual Studio Code are mentioned, the order of presentation places Windows-only tools before cross-platform alternatives, and there are no Linux-specific examples or guidance. This subtly prioritizes Windows environments and may give the impression that Linux is less supported or an afterthought.

Recommendations:

Reorder the list of tools to mention cross-platform and Linux-compatible tools (Azure Data Studio, Visual Studio Code) before Windows-only tools (SSMS, SQL Server Data Tools).
Explicitly state which tools are available on Linux and provide links or instructions for installing them on Linux.
Include Linux-specific usage examples or references, such as command-line tools (sqlcmd, Azure CLI) and Docker/Kubernetes deployment instructions tailored for Linux environments.
Add a section or callout highlighting best practices for Linux users, including troubleshooting tips or common issues encountered on Linux platforms.
Ensure parity in documentation by providing equal detail and prominence to Linux-compatible workflows and tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page predominantly provides platform-agnostic guidance but demonstrates subtle Windows bias by referencing SQL Server documentation and best practices that are historically Windows-centric, without providing explicit Linux or cross-platform examples. Only at the end is Linux mentioned, and even then, only as a link to another page, with no in-place Linux-specific configuration examples or commands.

Recommendations:

Provide explicit Linux-based examples for configuration steps, such as editing mssql.conf or setting Docker memory limits using Linux command-line tools.
Balance references to SQL Server documentation with links to Linux-specific or cross-platform resources.
Include Linux shell command examples alongside any configuration recommendations, not just links.
Move the 'Linux OS configurations' section higher in the document or integrate Linux-specific notes throughout, rather than as an afterthought.
Where Windows-centric concepts or defaults are mentioned (e.g., tempdb practices), clarify any differences or additional steps needed for Linux deployments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally provides Linux-oriented troubleshooting steps and command examples (e.g., use of sudo, systemctl, bash shells). However, there is a subtle Windows bias in the ordering and phrasing: Windows-specific advice (such as running PowerShell as Administrator and quoting differences in PowerShell) is often mentioned before or more prominently than Linux equivalents. Additionally, PowerShell is referenced explicitly, and quoting issues in PowerShell are called out, but no equivalent shell-specific advice is given for Linux shells.

Recommendations:

Ensure that Linux and Windows troubleshooting steps are presented with equal prominence and in parallel structure, rather than mentioning Windows-specific advice first or more prominently.
When referencing shell-specific behaviors (such as quoting), provide equivalent advice for both Windows (PowerShell, CMD) and Linux (bash, sh, etc.), or clarify when an issue is platform-specific.
If mentioning PowerShell or Windows command prompts, also mention common Linux shells and their behaviors, especially for users who may be less familiar with Linux.
Consider providing side-by-side command examples for both Windows and Linux where applicable, especially for common tasks like checking Docker status, running containers, or accessing logs.
Review the documentation for any implicit assumptions about the user's platform, and strive for parity in the depth and clarity of instructions for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias, particularly in the 'Jump box and Azure Bastion' section, where only Windows 10 or Windows Server VMs are mentioned as jump boxes, with no mention of Linux alternatives. There are no Linux-specific examples or guidance, and the documentation assumes Windows-based infrastructure for identity (Active Directory) and DNS, without referencing Linux-compatible solutions.

Recommendations:

In the 'Jump box and Azure Bastion' section, explicitly mention that the jump box can be a Linux VM as well, and provide guidance or examples for both Windows and Linux jump boxes.
When discussing identity and DNS, reference Linux-compatible solutions (e.g., Samba for AD-compatible domains, BIND for DNS) or clarify that non-Windows environments are supported.
Wherever VM examples are given, provide both Windows and Linux options, or use neutral language (e.g., 'a Windows or Linux VM').
Add examples or notes for SSH access (for Linux) alongside RDP (for Windows) in remote access scenarios.
Ensure that all tooling and procedures described are applicable to both Windows and Linux environments, or clearly state any limitations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page primarily references the use of Azure VMware Solution Run command (e.g., Set-Tools-Repo) for remediating VMware Tools vulnerabilities, but does not specify whether this command is cross-platform or provide Linux-specific alternatives. Additionally, the only explicit mention of VMware Tools remediation is for Windows ("VMware Tools for Windows update"), with no mention of Linux guest tools or procedures. There are no PowerShell-heavy examples or overt Windows-first ordering, but Linux parity is lacking in the examples and remediation steps.

Recommendations:

Explicitly clarify whether the Azure VMware Solution Run command (e.g., Set-Tools-Repo) applies to both Windows and Linux VMs, or provide separate instructions for each platform.
Include remediation steps for Linux guests where VMware Tools updates are required, referencing the appropriate Linux packages or update mechanisms.
Where issues or vulnerabilities affect both Windows and Linux, ensure both are mentioned in the workaround/resolution columns.
If using platform-specific tooling or commands, provide equivalent Linux commands or procedures alongside Windows examples.
Review all guest OS-related issues to ensure Linux users are not excluded from guidance or support information.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias, particularly in the example for creating a security analytics rule, which exclusively references Windows server sign-in failures. There are no equivalent examples or explicit instructions for Linux VMs or Linux-specific security events, despite the cross-platform nature of Azure VMware Solution environments.

Recommendations:

Include parallel Linux-focused examples, such as detecting failed SSH login attempts, alongside Windows examples in the 'Create rules to identify security threats' section.
Explicitly mention that Microsoft Defender for Cloud and Microsoft Sentinel support both Windows and Linux VMs, and provide links to documentation for Linux integration and supported event types.
Where scripts are generated or run, clarify if both Windows and Linux scripts are available, and provide example commands for both platforms.
In all sections referencing operating systems, ensure Linux is mentioned with equal prominence to Windows.
Add screenshots or walkthroughs that demonstrate Linux VM onboarding and monitoring, not just Windows-centric scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias primarily in the instructions for accessing the VM, where it references connecting via RDP and links to a Windows-specific guide. The connection example and guidance are Windows-centric, and there is no mention of Linux or cross-platform alternatives (such as SSH or using a Linux/macOS terminal) for accessing the VM. However, subsequent steps for configuring the appliance use Linux commands.

Recommendations:

Provide parallel instructions for connecting to the VM from Linux/macOS systems, such as using SSH from a terminal.
Include links to cross-platform or Linux/macOS-specific documentation for connecting to Azure VMs.
When referencing remote access methods, mention both RDP (for Windows) and SSH (for Linux/macOS) where appropriate.
Ensure that all steps that involve accessing or managing VMs are inclusive of both Windows and Linux user workflows.

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 GUI) and the Azure CLI, with no mention of Linux-specific tools or shell environments. While Azure CLI is cross-platform, all CLI examples use Bash-style syntax (e.g., variable assignment with $()), which is not native to Windows Command Prompt or PowerShell. However, there are no PowerShell examples, and the documentation does not explicitly address Linux users or provide Linux-specific guidance. The 'Portal' instructions implicitly assume a GUI environment, which is more common on Windows. There is also no mention of Linux command-line environments or alternative tools (e.g., Azure CLI on Linux, Cloud Shell, etc.), and no explicit validation that the steps are tested or applicable on Linux.

Recommendations:

Explicitly state that Azure CLI commands are cross-platform and provide any necessary notes for running them on Linux, macOS, and Windows (e.g., differences in variable assignment syntax).
Add PowerShell examples for Windows users and Bash examples for Linux/macOS users, or clarify that the provided CLI examples use Bash syntax.
Mention and link to Azure Cloud Shell as a cross-platform, browser-based CLI option.
Include a note or section confirming that all steps and tools are supported and tested on both Windows and Linux environments.
Where GUI steps are described, clarify that the Azure Portal is accessible from any OS with a web browser.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation is generally cross-platform and focused on Azure CLI, which is available on all major OSes. However, there are subtle Windows biases: (1) The example CLI output includes a Windows file path (C:\Users\testuser\Downloads\...), which may confuse Linux/macOS users; (2) The instructions for installing Azure CLI mention Windows and macOS specifically and suggest using Docker, but do not mention Linux package managers or provide Linux-specific install guidance; (3) The Next Steps section lists Azure portal and PowerShell before CLI and REST API, which may imply a Windows-first approach.

Recommendations:

Replace or supplement the CLI example output with a Linux/macOS terminal prompt (e.g., ~/Downloads/CLIForAFS/azure-cli$) or use a generic prompt (e.g., $) to avoid Windows path bias.
In the prerequisites, explicitly mention Linux as a supported platform for Azure CLI and provide a link to Linux installation instructions or mention common package managers (apt, yum, etc.).
When listing alternative tools (portal, PowerShell, CLI, REST API), rotate or randomize the order, or list CLI first to match the page's focus.
Ensure that all example commands and outputs are OS-agnostic unless a platform-specific behavior is being demonstrated.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing only Windows virtual machines for validation steps and linking exclusively to Windows VM creation guides. There are no examples or instructions for performing these tasks using Linux VMs, nor are there references to Linux-specific tools or workflows.

Recommendations:

Include parallel instructions and links for creating and using Linux virtual machines in the validation steps.
Provide examples or screenshots that demonstrate the process on both Windows and Linux VMs.
Reference both Windows and Linux documentation where applicable, ensuring equal visibility.
Clarify that either Windows or Linux VMs can be used for network validation and management tasks.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented around Azure portal 'Run commands' for deployment and management, which are specific to the Azure VMware Solution environment and do not reference or provide examples for Linux-based or cross-platform CLI tools. There are no Linux shell, bash, or cross-platform PowerCLI/CLI examples, nor is there mention of how to perform these tasks outside of the Azure portal or Windows-centric workflows.

Recommendations:

Include equivalent Linux-based deployment and management instructions, such as using PowerCLI on Linux, or relevant shell/CLI commands.
Document how to deploy and manage VMware Cloud Director Availability appliances using standard VMware tools (e.g., ovftool, vSphere CLI) that are available on Linux.
Provide guidance or links for performing these operations outside of the Azure portal, for customers who may automate or script deployments from Linux environments.
Clarify whether the 'Run commands' can be invoked via cross-platform Azure CLI or REST API, and provide Linux-compatible examples if so.
Add a section comparing Windows and Linux approaches, or explicitly state platform requirements and alternatives.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation displays a mild Windows bias by highlighting the Zerto Cloud Appliance (ZCA) as a Windows-only VM and describing its Windows-based components (ZVM and VRA) in detail. The ZCA is presented as essential for certain scenarios, and its Windows nature is explicitly called out. While Linux is mentioned for other Zerto components (ZVMA, vRA), there are no Linux-based alternatives or parity for the ZCA functionality. Additionally, the documentation describes the Windows-based ZCA before discussing the Linux-based ZVMA and vRA in the architecture table, giving Windows tools a prominent position.

Recommendations:

If Linux-based alternatives for ZCA exist, mention them and provide equivalent instructions.
If ZCA must be Windows-only, clarify why and provide guidance for Linux users (e.g., how to interact with ZCA from Linux environments).
Ensure that examples, screenshots, and instructions are balanced between Windows and Linux where possible.
Consider reordering the architecture table to avoid giving Windows tools undue prominence, or explicitly state the OS requirements for each component in a neutral manner.
Where only Windows tools are available, acknowledge the limitation and suggest workarounds or future plans for Linux parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides detailed instructions for configuring VPN and network connectivity between VMware Cloud Director service and Azure VMware Solution, but all operational examples and verification steps assume the use of the Azure Portal and Azure VMs, with no mention of Linux-specific tools or command-line alternatives. Verification steps (e.g., 'ping' from Azure VM) implicitly assume Windows environments, and there are no CLI or Linux-native instructions for tasks such as VPN verification, firewall configuration, or connectivity testing. There is also no mention of PowerShell, but the absence of Linux/CLI parity and the focus on Azure Portal workflows indicate a Windows/Azure-centric bias.

Recommendations:

Include Linux-based examples for verifying connectivity (e.g., using SSH and ping from a Linux VM, or using Linux CLI tools to test VPN status).
Provide Azure CLI and/or ARM template instructions alongside Azure Portal steps for resource creation and configuration.
Explicitly mention that both Windows and Linux VMs can be used for connectivity tests, and provide sample commands for both environments.
Where possible, include cross-platform guidance for firewall and NAT configuration, such as using REST APIs or CLI tools.
Add notes or links to documentation for performing equivalent tasks on Linux-based systems or using automation tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides a general overview of Azure native monitoring for VMs but tends to mention Windows-specific features (e.g., Windows registry and files) before Linux equivalents and lacks concrete Linux command examples. While Linux is referenced, especially in the context of agent support and sudo configuration, there are no detailed Linux monitoring or management examples, and Windows-centric terminology is more prominent.

Recommendations:

Provide explicit Linux examples alongside Windows ones, such as sample commands for installing and configuring the Log Analytics agent on Linux VMs.
When describing what the Log Analytics agent monitors, list Linux features (e.g., daemons, syslog, systemd) before or alongside Windows features (e.g., registry, services).
Include screenshots or walkthroughs for both Windows and Linux VM extension installation and configuration.
Clarify any differences in capabilities or requirements between Windows and Linux VMs in Azure VMware Solution.
Add troubleshooting tips or common issues for Linux VMs, similar to any provided for Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation mentions both Linux and Windows VMs as supported clients for Azure NetApp Files, and describes both SMB (Windows) and NFS (Linux) protocols. However, it lacks concrete, step-by-step examples or command-line instructions for mounting shares on either platform. Where mounting is discussed, Windows (SMB) is mentioned first, and the only mounting instructions for Linux are vague references to 'command lines or /etc/fstab entries' without examples. No Linux-specific commands or screenshots are provided, and the documentation does not show parity in practical guidance for Linux users.

Recommendations:

Add explicit, step-by-step examples for mounting NFS shares on Linux VMs, including sample mount commands and /etc/fstab entries.
Provide equivalent, detailed instructions for mapping SMB shares on Windows VMs, including screenshots or command-line examples (e.g., using 'net use' or Windows Explorer).
Ensure that Linux and Windows instructions are presented with equal prominence, ideally in parallel sections or side-by-side.
Include troubleshooting tips or common issues for both Linux and Windows clients.
Where protocols are discussed, avoid always listing Windows/SMB first; alternate or present both together to avoid perceived prioritization.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation shows 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 instead of Bash, and provides explicit instructions for Windows environment variable setting (using 'set') before or alongside Linux ('export'). In the Java section, the initial directory creation uses 'cmd' syntax, and there is occasional mention of Windows-specific patterns. However, the majority of code and CLI examples are cross-platform, and Linux/Bash instructions are present throughout.

Recommendations:

When referencing command shells, present Bash/Linux instructions first, or equally with Windows, rather than as an alternative.
Avoid using Windows-specific command syntax (e.g., 'cmd') as the primary example; provide both Bash and Windows equivalents side by side.
Where environment variables are set, show both 'export' (Linux/macOS) and 'set' (Windows) examples together, or clarify which is for which OS.
Ensure all tool installation and usage instructions are platform-agnostic or provide clear, parallel instructions for both Windows and Linux.
Consider adding a table or section summarizing OS-specific differences for setup and commands, to make parity explicit.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses the Azure portal UI for instructions and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). However, where command-line automation is implied or would be expected, there are no examples for Linux users (e.g., Azure CLI in Bash), nor are there any PowerShell examples. The absence of Linux-specific or cross-platform command-line instructions can be considered a bias, as it assumes users will interact only via the Azure portal, which is more common in Windows-centric workflows. Additionally, there is no mention of Linux tools or scripting, and no guidance for users who may prefer or require automation from non-Windows environments.

Recommendations:

Add Azure CLI examples for all major tasks (creating VNets, gateways, ExpressRoute connections), using Bash syntax to ensure Linux parity.
If PowerShell examples are added, ensure they are accompanied by equivalent Azure CLI examples.
Explicitly mention that all tasks can be performed via the Azure CLI on any platform, not just through the Azure portal.
Include a section or callout for users who prefer command-line or automated deployments, with links to relevant Azure CLI documentation.
Review screenshots and UI references to ensure they do not assume a Windows-only environment (e.g., avoid showing Windows-specific UI elements if not necessary).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing resources, but consistently lists PowerShell (a Windows-centric tool) alongside or immediately after CLI, and sometimes before mentioning cross-platform alternatives. There is no explicit Linux bias, but the presence and parity of PowerShell examples may suggest a slight Windows bias, especially since PowerShell is less commonly used on Linux. However, all core workflows are covered with Azure CLI, which is cross-platform.

Recommendations:

Explicitly state that Azure CLI commands work on Windows, Linux, and macOS to reinforce cross-platform support.
When presenting both CLI and PowerShell, consider listing CLI first, as it is more universally available across platforms.
Clarify that PowerShell examples are optional and primarily for users already familiar with it.
Where possible, add notes or callouts for Linux/macOS users (e.g., file path differences, shell syntax) to ensure parity.
Avoid implying that PowerShell is the default or preferred automation tool unless targeting a Windows-specific audience.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exclusively lists Edge Secured-core certified devices that run Windows 10 IoT Enterprise or Windows 11 IoT Enterprise. There are no examples or mentions of devices running Linux or other operating systems, which demonstrates a strong Windows bias and omits Linux equivalents.

Recommendations:

Include certified devices that run Linux-based operating systems (such as Ubuntu Core, Yocto, or other common IoT Linux distributions) if available.
Add a note clarifying whether Edge Secured-core certification is available or planned for Linux devices, or explicitly state if it is Windows-only.
If Linux support is not currently available, provide a roadmap or guidance for Linux users seeking similar security assurances.
Ensure future updates to the documentation consider parity in listing and describing devices for both Windows and Linux platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation generally uses cross-platform tools (Azure CLI, Azure Functions Core Tools) and provides language-specific instructions in a tabbed format, which is good for parity. However, there is a subtle Windows bias in the storage emulator guidance: the only local storage emulator mentioned is the classic 'Storage Emulator', which is Windows-only. No mention is made of cross-platform alternatives like Azurite. Additionally, the note about browser compatibility specifically recommends Edge, a Microsoft browser, which may be perceived as a Windows-centric suggestion.

Recommendations:

Mention and provide instructions for using Azurite (the cross-platform Azure Storage emulator) alongside or instead of the classic Windows-only Storage Emulator.
Clarify that all command-line instructions (Azure CLI, func) are cross-platform and work on Linux, macOS, and Windows.
When referencing browser compatibility, avoid recommending a specific browser unless necessary, or provide a broader set of options (e.g., Chrome, Firefox, Edge, Safari) to avoid perceived bias.
Explicitly state that all steps and tools are supported on Linux and macOS as well as Windows, especially in the prerequisites and troubleshooting sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by explicitly supporting Windows IoT Enterprise and Azure Sphere OS, with Linux support only mentioned as 'coming in the future.' There are no Linux-specific examples, instructions, or references, and the focus is on Windows-based certification.

Recommendations:

Provide a clear roadmap or timeline for Linux support to assure Linux users of upcoming parity.
Include references to Linux equivalents or alternative processes, even if support is in preview or limited.
Add a section outlining what Linux users can do now (e.g., join a waitlist, participate in a preview, or follow updates).
Ensure future updates include Linux-specific examples, tools, and certification steps alongside Windows instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally provides cross-platform instructions, with shell commands and code examples for C#, JavaScript, Python, and Java. However, there is a subtle Windows bias in the way Windows-specific tools and command patterns are introduced before or alongside their Linux equivalents. For example, in several places, the Windows 'dir /s /b' command is mentioned as an alternative to the default 'ls -R' (Linux/macOS), and the .NET Secret Manager tool (which is Windows-centric) is referenced without a Linux-specific alternative. In most cases, Linux commands are primary, but Windows alternatives are always mentioned, sometimes immediately after the Linux example, which can signal a slight preference or assumption of Windows usage.

Recommendations:

When presenting command-line examples, consider grouping Windows and Linux/macOS commands separately, or use tabbed sections (as done for programming languages) to avoid mixing them and to give each platform equal prominence.
For tools like .NET Secret Manager, clarify cross-platform usage or provide explicit instructions for Linux/macOS environments, including any prerequisites or differences.
If referencing Windows commands (e.g., 'dir /s /b'), ensure that Linux/macOS equivalents are always given equal visibility and not just as the default with Windows as an afterthought.
Consider adding a short section at the start of the tutorial that explicitly states the tutorial is cross-platform and that all major OSes are supported, with clear navigation to OS-specific instructions where needed.
Review all included snippets and ensure that any platform-specific instructions are clearly labeled and not presented as the default or primary approach.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page implicitly prioritizes Windows environments by referencing System Center Data Protection Manager (DPM), which is a Windows-only tool, and by linking to a 'Try Azure Backup' guide that specifically mentions Windows with the MARS agent. There are no examples, screenshots, or instructions for Linux systems or cross-platform backup scenarios, and no mention of Linux-compatible tools or agents.

Recommendations:

Include explicit references to Linux backup scenarios, such as using Azure Backup with Linux VMs or workloads.
Provide examples, screenshots, or step-by-step guides for configuring backup and retention policies on Linux systems.
Mention Linux-compatible backup agents or integration options (e.g., Azure Backup for Linux VMs, Azure CLI usage).
Balance references to Windows-specific tools (like DPM and MARS agent) with Linux equivalents or alternatives.
Add links to Linux-focused documentation in the 'Next steps' section, such as 'Back up Linux VMs with Azure Backup'.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias by exclusively recommending the use of pgAdmin (a GUI tool popular on Windows) for database management tasks, without mentioning or providing examples for Linux-native or CLI-based tools such as psql. There are no command-line examples or references to Linux workflows, and all screenshots and tool recommendations focus on GUI-based approaches, which are more common in Windows environments.

Recommendations:

Include examples using the psql command-line tool for granting privileges and connecting to the database, as this is the default and most common tool on Linux systems.
Provide alternative instructions for Linux users, such as how to perform the same tasks using terminal commands.
Mention other cross-platform or Linux-native tools (e.g., DBeaver, Azure CLI, or direct psql usage) alongside pgAdmin.
Add screenshots or code snippets that demonstrate Linux terminal usage for key operations.
Ensure that REST API and CLI instructions are as prominent as portal/GUI instructions, and consider including a 'Linux' or 'Command-line' tab in relevant sections.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias, primarily by referencing Windows VM creation first and providing more detailed, step-by-step instructions for installing the VM agent on Windows (including download links, file paths, and UI actions), while the Linux instructions are more generic and less detailed. The initial link for VM creation points specifically to Windows VMs, and Windows-specific tools and file paths are mentioned explicitly.

Recommendations:

Provide parallel Linux examples and links wherever Windows examples or links are given (e.g., link to both Windows and Linux VM creation quickstarts).
Ensure installation instructions for the VM agent on Linux are as detailed as those for Windows, including example commands for RPM/DEB installation and verification steps.
Avoid mentioning Windows tools, file paths, or UI actions without providing Linux equivalents.
When referencing VM creation or management, use neutral language or present Linux and Windows options together, rather than Windows-first.
Include screenshots or command snippets for Linux where relevant, to match the level of detail given for Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page exhibits a mild Windows bias by referencing PowerShell objects as the default or canonical representation of backup policy structure for PostgreSQL backups. There are no explicit Linux or cross-platform CLI examples, and the only tooling or scripting context mentioned is PowerShell. However, the primary focus of the page is on REST API usage and JSON payloads, which are inherently cross-platform. Still, the repeated mention of PowerShell as the default object model may alienate Linux users or those using other shells.

Recommendations:

Replace or supplement references to 'PowerShell object' with neutral terms such as 'policy object' or 'JSON policy object', since the REST API and JSON are cross-platform.
If scripting examples are included, provide both PowerShell and Bash/cURL examples for invoking the REST API, so Linux users have parity.
Clarify that the REST API and JSON payloads can be used from any platform or scripting environment, not just PowerShell.
Avoid implying that PowerShell is the default or only way to interact with the API; instead, emphasize the cross-platform nature of REST and JSON.
Consider adding a short section or note for Linux/macOS users, demonstrating how to use cURL or similar tools to perform the same operations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page is largely neutral and platform-agnostic in its main REST API examples, but it demonstrates subtle Windows bias in two ways: (1) references to PowerShell are given before Azure CLI in the 'Next steps' section, and (2) the only explicit link for assigning permissions in prerequisites points to a PowerShell-based guide. There are no Linux-specific examples or explicit parity in tool references.

Recommendations:

When referencing command-line tools, always mention Azure CLI alongside PowerShell, and provide links to both PowerShell and CLI guides for tasks like assigning permissions.
In the 'Next steps' section, list Azure CLI before or alongside PowerShell, or alternate their order across documentation pages.
Explicitly state that all REST API operations can be performed from any OS, and provide example CLI commands (e.g., using curl or az CLI) for common operations.
Add a section or note clarifying that the REST API can be used from Linux, macOS, and Windows equally, and provide sample shell (bash) commands where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_heavy

Summary:

The documentation page lists supported VM SKUs for Azure Policy, presenting a long, detailed enumeration of Windows-based images and SKUs before Linux distributions. The Windows section is much more extensive and appears first, while Linux distributions are listed only after all Windows options, with less detail and fewer variants. There are no Linux-specific examples or parity in the level of detail provided.

Recommendations:

Reorder the table or split it into separate sections for Windows and Linux, or alternate between Windows and Linux entries to avoid the impression of prioritizing Windows.
Provide equal detail for Linux distributions, including variants, special configurations, and notes where applicable.
Add explicit mention of support for Linux in the introductory text, not just as a list at the end.
If there are any limitations or special considerations for Linux (as there is for CentOS), provide similar notes for Windows where relevant.
Consider including example policy assignments or usage scenarios for both Windows and Linux VMs to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently assumes the SQL Server is running on a Windows VM and does not mention or provide guidance for Linux-based SQL Server VMs. All examples, resource names, and container naming conventions (such as 'mssqlserver', 'testSQLVM') implicitly reference Windows environments. There are no examples or notes for managing SQL Server on Linux VMs, nor any mention of Linux-specific considerations or differences.

Recommendations:

Explicitly state whether the instructions apply to both Windows and Linux SQL Server VMs, or clarify if only Windows is supported.
If Linux SQL Server VMs are supported, provide parallel examples and notes for Linux environments (e.g., naming conventions, prerequisites, differences in agent installation or backup support).
Add a section or note about any limitations or differences when using Azure Backup for SQL Server on Linux VMs.
Use more neutral naming in examples (e.g., avoid 'mssqlserver' if not Windows-specific) or provide both Windows and Linux variants.
Reference relevant documentation for SQL Server on Linux in Azure VMs if available.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes how to create and delete Backup vaults using the Azure Portal UI, which is platform-agnostic but typically more familiar to Windows users. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux-specific tools or workflows. Additionally, where command-line automation is referenced, only REST API documentation is linked, with no Azure CLI or Bash scripting guidance. This may unintentionally favor Windows users or those accustomed to GUI workflows, while omitting parity for Linux users who often prefer CLI-based management.

Recommendations:

Add step-by-step instructions for creating and deleting Backup vaults using the Azure CLI, with example commands.
Include Bash script examples for Linux users to automate vault management.
If PowerShell examples are provided elsewhere, ensure equivalent Azure CLI/Bash examples are present and not secondary.
Reference both Windows and Linux environments explicitly when discussing automation or scripting options.
Link to documentation for managing Backup vaults via Azure CLI and Bash in the 'Next steps' or relevant sections.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides only Windows-style (DOS path) examples for npm commands (e.g., using C:\ paths), with no Linux or cross-platform path examples. This may confuse or exclude Linux/macOS users. While the YAML pipeline uses Ubuntu as the build agent, all explicit command-line examples and paths are Windows-centric, and Linux alternatives are not mentioned or shown.

Recommendations:

Provide Linux/macOS equivalent examples for all command-line instructions, especially for npm commands (e.g., use /home/user/DataFactories/DevDataFactory as a path example).
When showing file paths, use both Windows (C:\...) and Linux (/home/...) formats, or use environment variables and relative paths where possible.
Explicitly state that the npm package and commands are cross-platform, and clarify any OS-specific considerations.
In the 'Export ARM template' and 'Validate' sections, add Linux/macOS command-line examples alongside the Windows ones.
Consider using forward slashes in paths or note that both path styles are supported, depending on the OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation primarily describes migration using the Azure Portal UI and briefly references Azure CLI, but does not provide any explicit command-line examples for Linux users. While PowerShell is mentioned in a note about supported tools, there are no step-by-step CLI or PowerShell examples, and no Linux-specific guidance or screenshots. The only command-line reference is a link to the Azure CLI documentation, with no in-place example. This may disadvantage Linux users who prefer or require CLI-based workflows.

Recommendations:

Add explicit Azure CLI command examples for all migration operations, including sample commands and expected output.
Ensure that CLI examples are platform-agnostic or, where differences exist, provide both Windows (PowerShell) and Linux (Bash) command examples.
Include screenshots or terminal output for CLI-based workflows, not just portal UI.
Clarify in each section that all operations can be performed via CLI on both Windows and Linux, and provide links to relevant documentation for both platforms.
If PowerShell-specific features or commands are mentioned, provide equivalent Bash or shell commands for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally maintains platform neutrality by focusing on the Azure Portal UI, but in the 'Install the VM agent' section, Windows instructions are presented first and in more detail, including direct download links and file paths, while Linux instructions are less detailed and refer users to external package repositories. This ordering and detail level reflect a subtle Windows-first and Windows-tools bias.

Recommendations:

Present Linux and Windows agent installation instructions with equal detail and prominence, possibly in parallel columns or tabs.
Provide direct Linux command examples for installing the Azure Linux agent (e.g., using apt, yum, or zypper), similar to the explicit Windows MSI instructions.
Where possible, alternate the order of Windows and Linux instructions or use a neutral ordering (e.g., alphabetical) to avoid implicit prioritization.
Include troubleshooting and verification steps for Linux agent installation, matching the level of detail provided for Windows.
Ensure that any references to file paths, tools, or verification steps are provided for both platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a subtle Windows bias by mentioning BitLocker (the Windows disk encryption tool) before DM-Crypt (the Linux equivalent) when describing Azure Disk Encryption for VMs. BitLocker is named explicitly and first, while DM-Crypt is mentioned second, which may suggest a prioritization of Windows technologies. No Linux-specific tools or command-line examples are provided, and the only detailed encryption workflow (ADE) references BitLocker first.

Recommendations:

Present Linux and Windows encryption tools in parallel or alternate the order (e.g., 'ADE uses BitLocker for Windows VMs and DM-Crypt for Linux VMs') to avoid implicit prioritization.
Include explicit Linux examples or references where possible, such as links to documentation on using DM-Crypt with Azure VMs.
Add a section or examples that address Linux-specific backup and encryption scenarios to ensure parity.
Where possible, avoid listing Windows tools or patterns before Linux equivalents unless there is a technical reason.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page provides a comprehensive list of Azure Resource Manager and Bicep templates for Azure Backup scenarios. However, it demonstrates a subtle Windows bias: the only specific OS example given is for deploying a Windows Server VM with backup enabled, and there are no equivalent examples or explicit mentions of Linux VMs or Linux-specific backup scenarios. This may give the impression that Windows is the primary or only supported platform for certain backup operations.

Recommendations:

Add examples and templates for deploying and backing up Linux VMs, similar to the 'Deploy Windows Server VM with backup enabled' entry.
Explicitly mention Linux support where applicable, especially in sections that currently only reference Windows.
Where possible, provide parity in sample templates and descriptions for both Windows and Linux environments.
Review template descriptions to ensure they do not imply exclusivity to Windows unless that is a technical limitation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page refers to Azure VMs in a generic way but, in the section on restoring VMs, the example link for creating a new empty VM points specifically to the Windows VM creation documentation. There are no explicit Linux or cross-platform examples or references, and no mention of Linux-specific tools or procedures, despite SAP ASE being commonly run on Linux. This may lead Linux users to feel less supported or unsure if the instructions fully apply to their environments.

Recommendations:

Provide parallel links and examples for both Windows and Linux VM creation and management (e.g., link to both Windows and Linux quick-create guides).
Explicitly mention that the backup and restore procedures apply to both Windows and Linux VMs, and highlight any OS-specific considerations.
Include Linux-specific examples or notes where relevant, such as running the preregistration script on Linux, or restoring to a Linux VM.
Ensure that terminology and linked resources do not default to Windows unless the feature is Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a mild Windows bias. In the 'Related content' section, Azure PowerShell is listed before Azure CLI, which is more cross-platform and commonly used on Linux. There is also a relative emphasis on PowerShell-based workflows, with no explicit Linux-specific guidance or examples, and no mention of Bash or Linux shell environments.

Recommendations:

List Azure CLI examples before or alongside PowerShell examples to promote cross-platform parity.
Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows.
Add Bash or Linux shell script examples where command-line usage is discussed.
Ensure that any referenced guides or links include both PowerShell and CLI/Linux instructions.
Consider a dedicated section or callout for Linux users, highlighting any differences or additional steps.

Create pull request

Bias Types:

⚠️ linux_first

⚠️ missing_windows_example

Summary:

The documentation is strongly Linux-focused, referencing only Linux VMs for SAP ASE backup configuration. All instructions, prerequisites, and discovery steps assume a Linux environment (e.g., 'unprotected Linux VMs', 'sudo python3'), with no mention of Windows VMs, Windows command-line tools, or PowerShell. There are no Windows-specific examples or guidance, and the documentation does not address how to perform these tasks on Windows-based SAP ASE deployments.

Recommendations:

Add explicit guidance for configuring SAP ASE backup on Windows VMs, if supported.
Include Windows-specific prerequisites, such as verifying Python installation and running scripts with Windows command prompt or PowerShell.
Provide parallel examples for both Linux and Windows environments, including screenshots and command-line instructions.
Clarify in the introduction or prerequisites section whether Windows VMs are supported or not. If only Linux is supported, state this explicitly to avoid confusion.
If Windows is not supported, consider adding a note explaining this limitation and, if possible, provide a roadmap or alternatives for Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides only a Windows-style file path (C:\temp2\Policy.json) in the Azure CLI example and does not mention or show a Linux/macOS equivalent. There are no explicit Linux or cross-platform examples or notes, which may confuse or exclude users on non-Windows systems.

Recommendations:

Provide both Windows and Linux/macOS file path examples in CLI commands (e.g., C:\temp2\Policy.json and /tmp/Policy.json).
Add a note clarifying that file paths should be adapted to the user's operating system.
Where possible, use environment-agnostic examples or variables (e.g., <path-to-policy.json>) and explain with OS-specific examples below.
Explicitly mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI (Bash) and Azure PowerShell examples throughout, but there is a consistent pattern of presenting PowerShell (a Windows-centric tool) alongside or even before Bash/CLI in many sections. The prerequisites and setup instructions often mention PowerShell explicitly and sometimes in more detail than Bash, and the inclusion of PowerShell tabs and instructions may suggest a slight Windows bias. However, Linux users are not excluded, as Bash/CLI examples are present for all major steps. There are no exclusive Windows-only tools or missing Linux examples, but the parity in depth and order could be improved.

Recommendations:

Ensure that Bash/Azure CLI examples are always presented first, as CLI is cross-platform and more common for Linux users.
Where possible, provide additional context or troubleshooting tips specifically for Linux environments (e.g., file permissions, environment variable syntax differences).
Avoid giving more detailed or advanced PowerShell examples than Bash/CLI unless there is a technical reason.
Explicitly state that all CLI examples work on Linux, macOS, and Windows, and clarify any OS-specific requirements.
Consider adding a short section or note for Linux users highlighting any differences or best practices.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page for viewing Azure Backup reports demonstrates a mild Windows bias. It references Windows-centric backup solutions and tools (such as DPM, SQL in Azure VM, and SAP HANA 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 backup scenarios described (e.g., DPM server, SQL in Azure VM) are primarily Windows-focused. Linux workloads and tools are not mentioned, and Linux-specific backup scenarios are absent.

Recommendations:

Include examples and references for Linux-based backup workloads (e.g., Azure Backup for Linux VMs, Azure Database for PostgreSQL, MySQL, etc.) alongside Windows examples.
Provide parity in documentation by describing how to view and interpret reports for Linux-based backup items, not just Windows-centric workloads.
Explicitly mention and illustrate any differences or similarities in reporting for Linux and Windows workloads.
Add screenshots or walkthroughs that feature Linux backup items or mixed-environment scenarios.
Where tools or patterns are Windows-specific (e.g., DPM), offer Linux alternatives or clarify applicability.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation focuses exclusively on using RDP (a protocol and workflow traditionally associated with Windows) to connect to Linux VMs, requiring the installation of xrdp (a Windows-compatible RDP server for Linux). There are no examples or mentions of native Linux remote access tools (such as SSH or VNC), nor are there instructions for connecting from Linux clients. The documentation assumes a Windows-centric approach to remote desktop access, potentially neglecting Linux-native workflows.

Recommendations:

Include examples and guidance for connecting to Linux VMs using native Linux tools, such as SSH, alongside RDP.
Provide parity in instructions for connecting from both Windows and Linux client machines.
Mention and link to alternatives to xrdp (such as VNC or X2Go) for users who may prefer Linux-native remote desktop solutions.
Clarify that RDP is not the only or default method for Linux VM access, and explain scenarios where RDP (via xrdp) is preferable or necessary.
Add a section comparing RDP and SSH for Linux VM management, highlighting security and usability considerations.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation focuses on connecting to VM scale sets via Azure Bastion using the Azure portal, but implicitly assumes RDP/Windows usage by referencing 'Connect' without clarifying Linux/SSH scenarios. There are no explicit instructions or examples for connecting to Linux VMs (e.g., SSH), nor are Linux-specific workflows or terminology mentioned. The structure and language suggest a Windows-first perspective.

Recommendations:

Add explicit instructions and examples for connecting to Linux VM instances using SSH through Azure Bastion.
Clarify in the 'Connect' section that both RDP (for Windows) and SSH (for Linux) are supported, and provide step-by-step guidance for each.
Include screenshots or UI callouts that show both RDP and SSH options in the Azure portal.
Mention any Linux-specific prerequisites or settings (such as SSH key requirements) alongside the existing guidance.
Review terminology to ensure it is inclusive of both Windows and Linux scenarios (e.g., avoid assuming 'Connect' means RDP only).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page is generally focused on connecting to Linux VMs via Azure Bastion using the Azure portal, and does not exhibit overt Windows bias in its main instructions or examples. However, in the sections about storing SSH keys in Azure Key Vault, the documentation repeatedly references using PowerShell (and to a lesser extent, Azure CLI) for key management, and links to a 'quick-create-powershell' guide. There are no explicit Linux-native (e.g., Bash, shell script) examples or references for these operations, and PowerShell is mentioned before Azure CLI. This may subtly favor Windows users or those familiar with PowerShell, rather than providing parity for Linux users.

Recommendations:

Provide explicit Azure CLI and Bash/shell script examples for storing SSH keys in Azure Key Vault, alongside or before PowerShell examples.
When linking to guides (e.g., 'Create a key vault'), include links to both PowerShell and Azure CLI/Bash versions.
Clarify that Azure CLI can be used from any platform, and provide sample commands for Linux/macOS users.
Review all references to PowerShell and ensure that Linux-native alternatives are presented equally and not as secondary options.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell as the only command-line alternative to the Azure portal, without mentioning or providing examples for Linux/Unix-based tools such as Azure CLI. No Linux-specific instructions or parity is offered.

Recommendations:

Include Azure CLI instructions for configuring host scaling, as Azure CLI is cross-platform and widely used on Linux.
When referencing command-line alternatives, mention both PowerShell and Azure CLI, and provide links/examples for each.
Ensure that any references to tools or scripts are not Windows-specific unless absolutely necessary, and always provide Linux equivalents where possible.
Consider a section or note explicitly stating that the steps can be performed from any OS using the Azure portal or Azure CLI.

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 before Linux in both the main connection table and the 'Next steps' section. There are also missing explicit Linux command examples or screenshots in the main body, with more detailed step references for Windows clients. Linux tools and workflows are mentioned, but not as prominently or with as much detail as Windows equivalents.

Recommendations:

Present Linux and Windows examples side-by-side or alternate their order in tables and 'Next steps' sections.
Include explicit Linux command-line examples and screenshots in the main documentation body, not just as links.
Ensure that Linux-native tools (such as OpenSSH) are discussed with the same depth and clarity as Windows tools.
Add a section or callout for macOS users if relevant, to further improve cross-platform parity.
Review linked pages to ensure Linux instructions are as comprehensive and accessible as Windows instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell instructions for verifying the deployment, but the PowerShell examples are included as a primary alternative to the CLI, which is cross-platform. There are no Linux-specific shell examples (e.g., bash), and PowerShell is traditionally associated with Windows, though it is now cross-platform. The order of presentation (CLI first, then PowerShell) is reasonable, but the inclusion of PowerShell as the only alternative may suggest a slight Windows bias, especially since no explicit Linux shell or macOS Terminal instructions are given.

Recommendations:

Add explicit bash shell examples for Linux/macOS users, especially for common verification and scripting steps.
Clarify that Azure CLI commands work on all platforms, and consider adding a note about running them in bash or zsh.
If PowerShell is included, mention that it is available cross-platform, or provide a link to installation instructions for Linux/macOS.
Consider including a table or section summarizing command usage across Windows (PowerShell, CMD), Linux (bash), and macOS (zsh, bash) to improve parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by only providing 'Next steps' links for creating and connecting to Windows virtual machines, with no mention or guidance for Linux VMs. There are no Linux-specific examples or references, and the workflow implicitly assumes a Windows-centric use case.

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 examples or references for connecting to Linux VMs via Bastion, not just Windows (RDP) scenarios.
Ensure that any screenshots or walkthroughs that are OS-specific are balanced with both Windows and Linux examples.
Review the documentation for any implicit assumptions that the user is deploying Windows VMs and update language to be OS-neutral where possible.

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 linking to equivalent Linux VM creation or SSH connection documentation. There are no Linux-specific examples or references, which may lead Linux users to feel unsupported or overlooked.

Recommendations:

Include links to both Windows and Linux VM creation guides (e.g., /azure/virtual-machines/linux/quick-create-portal).
Provide examples or links for connecting to Linux VMs via SSH using Azure Bastion (e.g., bastion-connect-vm-ssh-linux.md).
Ensure that instructions and references are platform-neutral or explicitly cover both Windows and Linux scenarios.
Where possible, mention both RDP (for Windows) and SSH (for Linux) in connection steps and overviews.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page for configuring Bastion session recording is platform-neutral in its instructions, focusing on Azure Portal UI steps and storage configuration. However, it implicitly exhibits 'missing_linux_example' and 'windows_first' bias by not mentioning or providing any Linux-specific guidance or CLI examples, nor does it address Linux users' needs for automation or scripting (e.g., via Azure CLI, Bash, or PowerShell). The instructions and screenshots are tailored to the Azure Portal, which is commonly used by Windows administrators, and there is no mention of alternative methods or considerations for Linux environments.

Recommendations:

Add equivalent instructions for configuring Bastion session recording using Azure CLI and/or Azure PowerShell, and present both methods side by side.
Include Linux-specific examples for generating SAS tokens (e.g., using az storage commands in Bash).
Explicitly mention that the steps are applicable regardless of the OS, or clarify any OS-specific differences if they exist.
Provide automation scripts or command-line alternatives for common tasks (e.g., creating storage accounts, containers, and SAS tokens) to support Linux and cross-platform users.
Ensure that any screenshots or UI references are supplemented with text-based instructions for users who may not use the Azure Portal.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by referencing only Windows-specific instructions for the copy/paste feature ("Copy and paste - Windows VMs") without mentioning Linux VMs or providing equivalent guidance for Linux users. There is no explicit mention of Linux tools, workflows, or examples, and Windows is prioritized in the only detailed feature link.

Recommendations:

Add equivalent documentation and links for Linux VM scenarios, such as 'Copy and paste - Linux VMs', ensuring parity in feature explanation.
Where features are OS-agnostic, clarify that instructions apply to both Windows and Linux, or provide OS-specific sections/examples.
Review all referenced articles (e.g., for file transfer, audio) to ensure Linux workflows are included and linked from this page.
Avoid using Windows as the default or only example; present both Windows and Linux options side by side where relevant.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page focuses on conceptual information about Azure Batch and Storage accounts, but where it mentions programmatic creation and management, it only references the Azure portal and the Batch Management .NET library—both of which are more commonly associated with Windows environments. There are no examples or mentions of Linux-friendly tools (such as Azure CLI, Bash, or Python SDK), nor are cross-platform command-line options presented. This creates a subtle Windows-first bias and omits Linux parity in tooling guidance.

Recommendations:

Include examples and references for creating and managing Batch accounts using the Azure CLI, which is cross-platform and widely used on Linux.
Mention and link to documentation for other SDKs (such as Python, Java, or Node.js) that are commonly used in Linux environments.
When listing programmatic options, present cross-platform tools (like Azure CLI) before or alongside Windows-centric tools (like .NET library).
Add explicit Linux/Bash command-line examples where relevant, especially for common tasks like associating storage accounts.
Review and update the 'Next steps' section to include links to cross-platform management options, not just the portal and .NET.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page lacks Linux-specific examples and mentions a Windows command-line pattern before any mention of Linux equivalents. There are no Linux or cross-platform command-line examples, and the only explicit example for running a custom script refers to a Windows node and Windows executables.

Recommendations:

Add equivalent Linux/bash examples wherever a Windows command-line or executable is referenced (e.g., show both 'doMyWork.exe && uploadMyFilesToSql.exe' and './doMyWork.sh && ./uploadMyFilesToSql.sh').
Explicitly mention that custom file movement solutions can be implemented on both Windows and Linux nodes, and provide guidance for both.
Include references or links to cross-platform tools and scripting practices, not just .NET/C# libraries.
Ensure that examples and recommendations are presented in a platform-neutral manner, or that both Windows and Linux approaches are given equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to move an Azure Batch account using the Azure portal and ARM templates, with all instructions and UI references tailored to the Azure portal experience. There are no command-line examples (such as Azure CLI, PowerShell, or Bash scripts), and no mention of Linux or cross-platform tooling. The steps and screenshots implicitly assume a Windows-centric workflow, as the Azure portal is often associated with Windows users, and there is no guidance for users who prefer or require command-line or automation approaches common on Linux.

Recommendations:

Add equivalent instructions for moving a Batch account using the Azure CLI, which is cross-platform and widely used on Linux.
Include PowerShell examples for Windows users, but ensure CLI/Bash examples are given equal prominence.
Explicitly mention that the Azure portal is accessible from any OS, but provide alternative workflows for users who prefer not to use the portal.
Provide downloadable sample scripts (Bash, CLI, PowerShell) for exporting, modifying, and deploying ARM templates.
Ensure that any references to tools or workflows are not Windows-specific, or provide Linux/macOS alternatives where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally maintains good cross-platform parity, especially in the Python section, where both Windows and Linux commands are provided side-by-side. However, there is a subtle 'windows_first' bias in the ordering of examples (Windows commands are listed before Linux), and the documentation consistently references Windows-centric tools such as Docker Desktop, which is less common on Linux. There are no PowerShell-only examples, and Linux instructions are present where relevant.

Recommendations:

When presenting platform-specific commands, alternate the order (e.g., show Linux first in some sections) or present both together in a neutral way.
Where Docker Desktop is mentioned as a prerequisite, clarify that Linux users can use the standard Docker Engine and provide a link to Linux installation instructions.
Review other tool references (such as Azure CLI) to ensure Linux compatibility is explicitly stated or linked.
Continue providing both Windows and Linux command examples, and consider adding macOS instructions where applicable.
If possible, use platform-agnostic command blocks or tabs to avoid implying a default platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page generally aims for cross-platform parity by referencing the Azure CLI and mentioning support for Windows, Mac, and Linux. However, in the file transfer section, all example paths use Windows-style paths (e.g., c:\source_videos\*.mp4), and there are no equivalent Linux/macOS path examples. This presents a subtle 'windows_first' and 'missing_linux_example' bias, as Linux users may not immediately recognize how to adapt the commands for their environment.

Recommendations:

For every CLI example that uses a Windows-style path, provide an equivalent Linux/macOS example (e.g., /home/user/source_videos/*.mp4).
Explicitly mention that the Azure CLI commands work on all supported platforms and that file paths should be adapted to the user's OS.
Where possible, use OS-agnostic placeholder paths in examples, or provide both Windows and Linux/macOS variants side by side.
Add a note or callout reminding users to adjust file paths for their operating system.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page provides detailed authentication steps and code samples for .NET and Python, but all portal navigation and setup instructions assume use of the Azure Portal GUI, without mention of CLI or scripting alternatives. There are no examples using Bash, Azure CLI, or Linux-native tools, and no guidance for users working in non-Windows environments. The .NET code samples implicitly target Windows users, and the Python example, while cross-platform, does not address Linux-specific setup or authentication nuances. There are no PowerShell-specific examples, but the absence of Linux/CLI parity and the focus on GUI steps indicate a Windows-first, GUI-centric bias.

Recommendations:

Add equivalent instructions for registering applications, assigning permissions, and managing secrets using the Azure CLI (az) and/or Azure PowerShell, and present these before or alongside GUI steps.
Include Bash or shell script examples for authentication flows, especially for unattended/service principal scenarios.
Explicitly mention that the Python code is cross-platform and provide any Linux-specific notes (e.g., environment variable setup, dependency installation).
Provide guidance for headless or non-GUI environments (common in Linux), such as using device code authentication or service principal flows via CLI.
Where possible, balance the order of presentation so that CLI/Linux-native approaches are not always secondary to GUI/Windows-centric instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation generally maintains platform neutrality but exhibits subtle Windows bias by listing the Windows documentation link before Linux in the FAQ and not providing concrete, step-by-step Linux command examples for certificate handling. Linux-specific guidance is less detailed, and practical examples for Linux users (such as shell commands or scripts) are missing.

Recommendations:

When referencing documentation for both Windows and Linux, alternate the order or present them together (e.g., 'See the documentation for Windows and Linux').
Provide explicit, step-by-step examples for Linux users, such as sample shell commands for copying certificates, adjusting permissions, or accessing Key Vault from a Linux Batch pool.
Ensure that all instructions and examples are equally detailed for both platforms, including code snippets or configuration samples for Linux where relevant.
Highlight any platform-specific considerations in parallel, rather than focusing on one OS before the other.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exclusively provides examples and code samples using the Batch .NET SDK in C# and references to C# sample projects. There are no examples or code snippets for Linux-oriented tools (such as Azure CLI, Bash, Python SDK, or REST via curl), nor are there references to cross-platform scripting or command-line usage. The documentation assumes a Windows/.NET development environment, which may disadvantage Linux or cross-platform users.

Recommendations:

Add equivalent code samples using the Azure CLI to demonstrate efficient list queries for Batch resources, including filter, select, and expand usage.
Provide examples using the Python SDK (azure-batch) to illustrate how to construct efficient queries in a cross-platform language.
Include REST API usage examples with curl or HTTPie, showing how to construct filter, select, and expand query strings.
Reference and link to sample projects or scripts that are cross-platform (e.g., Python, Bash) in addition to the C#/.NET samples.
Explicitly mention that the concepts apply to all platforms and provide guidance for users on Linux or macOS.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exclusively provides .NET (C#) code samples and instructions, which are typically associated with Windows development environments. There is no mention of Linux or cross-platform considerations, nor are there any examples or notes about running the .NET library or code on Linux systems. The only sample project referenced is in C#, and there are no alternative language or platform examples. This creates a subtle Windows bias by omission, as it assumes a Windows/.NET-centric development context and does not address Linux users or cross-platform usage.

Recommendations:

Explicitly state that the Batch Management .NET library and its code samples are cross-platform and can be used on Linux and macOS as well as Windows, especially since .NET Core/.NET 5+ is supported on these platforms.
Provide instructions or notes for setting up the development environment on Linux (e.g., installing .NET SDK, using VS Code or other editors, running the code from the terminal).
Include at least one example of running the code or configuring authentication on Linux (e.g., using environment variables for DefaultAzureCredential).
Mention any Linux-specific considerations or troubleshooting tips, if applicable.
Reference or link to equivalent documentation or samples in other languages that are popular on Linux (e.g., Python, Java), or at least mention their existence in the 'Next steps' section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_heavy

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows-related information and terminology. The 'cloudServiceConfiguration' section is exclusively Windows-focused, referencing only Windows Server OS families. The documentation provides more detail and explicit references for Windows (e.g., Windows Server versions, Windows-specific configuration), while Linux is only mentioned in passing (e.g., in a link to VM sizes and a note that 'windowsConfiguration' must not be set for Linux images). There are no Linux-specific configuration examples or details.

Recommendations:

Add a dedicated section for Linux configuration, similar to the 'windowsConfiguration' section, describing relevant Linux settings (e.g., SSH configuration, user setup, extensions).
Provide explicit Linux OS family/version examples and references, not just Windows Server versions.
Ensure that Linux and Windows VM size links are presented together and with equal prominence.
Include example JSON snippets for both Windows and Linux pool configurations.
Clarify in the documentation when a property is Linux-specific, Windows-specific, or applicable to both, to avoid implicit Windows-first assumptions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias by mentioning Windows-specific configuration (automatic updates) without providing equivalent information for Linux pools. There are no OS-specific command-line examples, but the only explicit OS distinction is for Windows, and Linux parity is not addressed in those sections.

Recommendations:

Where Windows-specific settings are discussed (e.g., enableAutomaticUpdates), provide equivalent information for Linux pools, such as how updates are handled or configured on Linux nodes.
Explicitly mention differences in node management, error states, or troubleshooting steps for Linux pools where applicable.
If there are OS-specific behaviors (such as log file locations, update mechanisms, or disk management), include parallel guidance for both Windows and Linux.
Consider adding examples or notes that clarify when instructions or recommendations apply to all OS types versus only Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both PowerShell and Azure CLI commands for listing VM sizes and images, but PowerShell (a Windows-centric tool) is consistently mentioned first in all lists and examples. There are no Linux-specific shell examples (e.g., Bash), and the documentation does not mention or demonstrate Linux-native tools or patterns, despite Azure CLI being cross-platform. This ordering and tool selection subtly prioritize Windows users and workflows.

Recommendations:

Alternate the order of PowerShell and Azure CLI in lists and examples, or list Azure CLI first to reflect its cross-platform nature.
Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
Where possible, include Linux-native command-line patterns (e.g., Bash scripting) alongside PowerShell examples.
Add a note clarifying that PowerShell Core is available cross-platform, but that Azure CLI is the recommended tool for Linux users.
Review other documentation pages for similar ordering and tool selection to ensure consistent cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page does not provide explicit examples or instructions that are Windows-specific, but it does exhibit subtle Windows bias by referencing the Batch .NET client library before Python in the 'Next steps' section. There are no Linux-specific examples, tools, or workflows mentioned, and the documentation does not clarify cross-platform considerations or provide parity for Linux users.

Recommendations:

Present cross-platform SDKs and tools in a neutral or rotating order (e.g., list Python and .NET together, or alternate which is mentioned first).
Explicitly mention that Batch supports both Windows and Linux compute nodes, and provide links to documentation or quickstarts for both platforms.
Include examples or references for Linux users, such as Bash scripts or Linux command-line tools, where appropriate.
Highlight any platform-specific considerations (e.g., differences in application packaging or node setup between Windows and Linux).
Ensure that all referenced tools (such as Batch Explorer) are clearly marked as cross-platform or provide alternatives if they are Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation generally maintains OS neutrality, but in the 'Connect to compute nodes' section, Windows (RDP) is mentioned before Linux (SSH), and no concrete command-line examples are provided for either OS. In the troubleshooting section, instructions reference examining 'event logs' without clarifying this is a Windows-specific tool, and there are no Linux log equivalents or examples. There are no PowerShell-heavy or Windows-only tool references, but Linux-specific troubleshooting steps and examples are missing.

Recommendations:

When describing remote connection methods, present Linux (SSH) and Windows (RDP) options in parallel, or alternate their order in different sections.
Provide explicit examples for both Windows (e.g., using RDP) and Linux (e.g., using SSH) for connecting to nodes, including sample commands.
In troubleshooting sections, mention both Windows event logs and Linux log files (e.g., /var/log/syslog, /var/log/messages) for parity.
Where possible, include code snippets or command-line examples for both platforms (e.g., using SSH to connect to Linux nodes, or using Windows Remote Desktop for Windows nodes).
Clarify when instructions or tools are OS-specific, and provide equivalent guidance for the other OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally maintains cross-platform language, but there are subtle signs of Windows bias. In the section on specifying the command line for tasks, the Windows example (cmd.exe) is listed before the Linux example (/bin/sh). Additionally, the 'robocopy' tool (Windows-specific) is mentioned as an example for copying files in a start task, without mentioning a Linux equivalent like 'cp' or 'rsync'. No Linux-specific tools are referenced in parallel, and the examples and tool mentions may lead Linux users to feel less directly supported.

Recommendations:

When providing command line examples, alternate the order or present Linux and Windows examples side by side, or even lead with Linux examples where appropriate.
When referencing platform-specific tools (e.g., 'robocopy'), also mention Linux equivalents such as 'cp' or 'rsync' to ensure parity.
Explicitly state that examples are provided for both Windows and Linux, and ensure that for every Windows-specific example or tool, a Linux counterpart is included.
Consider including a table or section summarizing common commands and tools for both platforms in the context of Azure Batch tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents PowerShell examples before Azure CLI, which may suggest a Windows-first perspective. The PowerShell section is detailed and uses Windows-centric tooling, while the CLI section, though present, comes after. There are no explicit Linux-only tools or shell patterns, but the ordering and emphasis could be perceived as favoring Windows users.

Recommendations:

Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows.
Include bash-specific notes or examples (e.g., using export, or referencing Linux shell conventions) to reinforce Linux parity.
If possible, add a short section or note about using these commands in Linux environments, including any prerequisites or differences.

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 of examples and references. Specifically, in the section on obtaining managed identity tokens within Batch nodes, the PowerShell (Windows) example is presented before the Bash (Linux) example. Additionally, the reference link for the Azure Instance Metadata Service points to the Windows-specific documentation. However, both Windows and Linux examples are present, and the overall content does not omit Linux instructions or tools.

Recommendations:

Present Linux and Windows examples in parallel or alternate the order to avoid always listing Windows first.
Use neutral or combined documentation links (e.g., a general Instance Metadata Service page, or both Windows and Linux links).
Ensure that any code samples, tips, or references that are platform-specific are clearly labeled and that Linux is given equal prominence.
Consider adding explicit notes about cross-platform support where relevant, to reassure users of Linux parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides step-by-step instructions for associating an Azure Batch account with a network security perimeter using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, which can be interpreted as a Windows-first ordering. The PowerShell section is detailed and uses Windows-centric tooling, which may be less familiar or accessible to Linux/macOS users. However, the inclusion of Azure CLI instructions does provide cross-platform coverage, as Azure CLI is available on all major operating systems. There are no Linux-specific shell (e.g., Bash) examples or explicit mention of Linux tools, but the CLI coverage partially mitigates this.

Recommendations:

Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more inclusive for Linux/macOS users.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to encourage non-Windows users.
Optionally, include Bash script examples or notes for Linux users, especially for automation scenarios.
Consider providing parity in troubleshooting or environment setup notes for both Windows (PowerShell) and Linux (Bash/CLI) environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation primarily describes deployment using the Azure Portal and briefly mentions Azure PowerShell, Azure CLI, and REST API as alternatives. However, it links only to the PowerShell deployment guide and does not provide direct examples or links for Linux users (e.g., Bash/CLI instructions). The order of mention and linking prioritizes Windows-centric tools, and there are no Linux-specific examples or parity in guidance.

Recommendations:

Add explicit Azure CLI (Bash) deployment instructions or links alongside PowerShell, ensuring both Windows and Linux users are equally supported.
When referencing alternative deployment methods, list Azure CLI before or alongside PowerShell, not after.
Provide example commands for both PowerShell and Azure CLI in the documentation, or link to both sets of instructions.
Include a note clarifying that the Azure CLI is cross-platform and suitable for Linux, macOS, and Windows users.
Ensure that all referenced guides (such as 'Deploy templates') include both PowerShell and CLI tabs/examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally maintains cross-platform neutrality, but in the troubleshooting section, the Windows PowerShell command (Test-TcpConnection) is listed before the Linux equivalent (nc), and the Windows command is labeled with a platform-specific comment. This ordering and explicit mention of PowerShell can be interpreted as a subtle Windows-first and PowerShell-heavy bias. No other examples, tools, or instructions are Windows-specific, and Linux is mentioned where relevant (e.g., Ubuntu image in REST example).

Recommendations:

Present Linux and Windows command-line examples in parallel or alternate the order (e.g., show Linux first in some sections).
Use neutral phrasing such as 'On Windows, use...' and 'On Linux, use...' instead of always listing Windows first.
Where possible, provide cross-platform commands or scripts (e.g., using Azure CLI, which is available on both platforms) as primary examples.
Ensure that any screenshots or UI references are not Windows-centric unless the feature is truly Windows-only.
Review other sections for subtle ordering or terminology that may imply Windows is the default or preferred platform.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio Code (VS Code) and its GUI for tasks such as opening terminals, generating deployment scripts, and managing files, without mentioning or providing examples for Linux or macOS environments. All command-line instructions assume a generic 'command prompt' but do not clarify or show examples for Bash or other Unix shells. There are no references to Linux-specific tools, shell commands, or alternative editors, and screenshots and instructions are tailored to the VS Code/Windows experience.

Recommendations:

Explicitly state that the instructions apply to Windows, Linux, and macOS, and clarify any differences in steps or UI.
Provide alternative instructions or notes for Linux/macOS users, such as using Bash instead of 'command prompt', and clarify how to open terminals in those environments.
Show examples of Git commands in both Windows (cmd/PowerShell) and Bash syntax, noting any differences in path formats.
Mention that Visual Studio Code is cross-platform, and provide links or notes for installing and using it on Linux/macOS.
Include screenshots or descriptions that reflect Linux/macOS environments where appropriate.
If any steps require Windows-only tools or features, clearly note this and suggest alternatives for Linux/macOS users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses the Azure Portal (web UI) for instructions and does not provide any command-line examples. While this avoids explicit Windows-specific tools like PowerShell, it also omits CLI-based workflows that are common on Linux and cross-platform environments. The lack of Azure CLI or Bash examples means Linux users do not see parity in automation or scripting approaches. Additionally, the documentation implicitly assumes a Windows-first perspective by not mentioning or linking to CLI alternatives.

Recommendations:

Add equivalent Azure CLI examples for all major steps (creating the CDN profile, endpoint, and resource cleanup), using Bash syntax.
Explicitly mention that the steps can be performed using Azure CLI or PowerShell, and provide links to relevant documentation for both.
Ensure that any future updates include both portal and CLI (cross-platform) instructions side by side.
Consider including a table or section that compares how to perform the tasks in the Portal, Azure CLI, and PowerShell, making it clear that all platforms are supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation shows a mild Windows bias by recommending Visual Studio Code (a Microsoft product, though cross-platform) as the editor, referencing Visual Studio Code's launch.json for debugging, and mentioning PowerShell as an additional management tool in the 'Next Steps' section. There are no explicit Linux or macOS-specific instructions, nor are there examples of running the code or setting up debugging on Linux/macOS. However, the main code and npm commands are cross-platform, and there are no PowerShell-heavy or Windows-only command-line examples.

Recommendations:

Explicitly mention that all steps and tools (npm, Node.js, editors) work on Linux and macOS as well as Windows.
Provide alternative instructions or notes for setting up command-line parameters in popular Linux/macOS editors or debuggers (e.g., JetBrains WebStorm, VS Code on Linux, or command-line usage).
In the 'Next Steps' section, balance the mention of PowerShell with links to equivalent Azure CLI documentation, which is cross-platform.
Where screenshots or instructions reference Visual Studio Code, clarify that it is available on all major OSes, or provide alternative examples for other environments.
Consider including a brief section or note on running the Node.js application from a Linux/macOS terminal to reinforce cross-platform support.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page presents both Bash and PowerShell as options in Azure Cloud Shell, but there is a subtle Windows bias. PowerShell and Azure PowerShell are mentioned alongside or before Bash and Azure CLI in several sections, and links to Azure PowerShell documentation are given equal prominence to Azure CLI. The integrated editor is described in the context of Azure CLI or Azure PowerShell, with no explicit mention of Bash scripting or Linux tooling. There are no explicit Linux command examples or references to Linux-specific tools, though it is noted that user permissions are those of a regular Linux user.

Recommendations:

Ensure that Bash and Azure CLI are mentioned before or alongside PowerShell in all relevant sections to avoid a 'Windows-first' impression.
Include explicit references to Bash scripting and Linux command-line tools in the description of the Cloud Shell environment and editor.
Provide links to Bash scripting or Linux command-line documentation, not just Azure CLI and PowerShell.
When listing access points or features, alternate the order of Bash/Azure CLI and PowerShell to ensure parity.
Add examples or references that highlight Linux tooling or workflows, such as using common Linux utilities within Cloud Shell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation shows a mild Windows bias by consistently listing Azure PowerShell updates alongside Azure CLI updates, sometimes mentioning PowerShell first or with more detail. The link for 'Get started with Azure Cloud Shell ephemeral sessions' defaults to the PowerShell tab, and some references (such as release notes) link directly to PowerShell-specific pages. However, the content overall is fairly cross-platform, with explicit mention of Azure Linux and Linux-specific tools, and there are no exclusive Windows-only tools or examples.

Recommendations:

When referencing features or tools available in both Bash and PowerShell, alternate the order in which they are mentioned, or mention both equally.
Provide links to both Bash and PowerShell documentation/tabs where possible, or use a neutral landing page.
Ensure that examples, instructions, and references are not PowerShell-specific unless the feature is exclusive to PowerShell.
Highlight Linux-specific changes or tools with the same prominence as Windows/PowerShell updates.
In link references, avoid defaulting to PowerShell tabs unless contextually appropriate; consider using a selector or neutral default.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exhibits mild Windows bias. References to Windows-specific technologies (such as TPM and Secure Boot) link to Microsoft/Windows documentation, and the Trusted Platform Module (TPM) section links exclusively to Windows resources. In the OS support table, while Linux options are listed first, Windows versions are described in greater detail and with more granularity. Some feature limitations reference Windows-centric features (e.g., Live Migration, Dynamic Memory) without Linux equivalents or context.

Recommendations:

Provide equivalent Linux documentation links for technologies like TPM and Secure Boot (e.g., link to Linux TPM and Secure Boot documentation alongside Windows links).
When mentioning features like Live Migration or Dynamic Memory, clarify if there are Linux equivalents or note their absence for parity.
Ensure that Linux and Windows OS support are described with equal granularity and detail in tables and lists.
Where possible, include Linux-specific examples, tools, or references in addition to Windows ones, especially in sections discussing security technologies.
Review all external documentation links to ensure both Linux and Windows users are equally supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by referencing Windows-specific scenarios (such as creating images from Windows confidential VMs) before mentioning Linux equivalents, and by not providing explicit Linux-focused examples or guidance. While there are some links to Linux generalization steps, the overall flow and examples are not balanced between Windows and Linux, and Linux-specific considerations are not highlighted.

Recommendations:

Add explicit Linux-focused examples and scenarios alongside Windows examples, especially when discussing image creation and generalization.
Ensure that references to generalization steps for both Linux and Windows are given equal prominence and are mentioned together, rather than Windows first.
Include notes or sections that address Linux-specific requirements or caveats for confidential VMs, such as supported distributions, kernel versions, or configuration steps.
Where possible, provide parity in screenshots or step-by-step instructions for both Windows and Linux VM images.
Review the order of presentation to avoid consistently mentioning Windows before Linux, and strive for a neutral or alternating order.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation generally maintains parity between Windows and Linux in terms of supported images and references. However, there is a subtle 'windows_first' bias: in the ARM template deployment section, the link for further information points to a Windows-specific template description page, and the Windows image is listed first in the example image references. There are no explicit Linux command-line examples (e.g., bash), and the Azure CLI example uses PowerShell-style backticks for line continuation, which may confuse Linux users. No Linux-specific deployment patterns or tools are mentioned.

Recommendations:

Provide links to both Windows and Linux ARM template documentation, or use a neutral, combined page.
List Linux and Windows images in a neutral or alternating order, or clarify that the order is not significant.
Use bash-style line continuation (backslash) in Azure CLI examples or provide both PowerShell and bash variants.
Explicitly mention Linux deployment considerations or tools where relevant, ensuring Linux users are equally supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page predominantly features .NET/ASP.NET Core and Orleans samples, which are technologies most commonly associated with Windows development. The majority of the listed samples focus on Microsoft-centric stacks, with only a few Java and Drupal examples representing more cross-platform or Linux-native technologies. There are no explicit Linux or Linux tool-specific examples, and the ordering and selection of samples suggest a Windows/.NET-first perspective.

Recommendations:

Add more samples featuring Linux-native technologies (e.g., Node.js, Python, Go, PHP) deployed to Azure Container Apps.
Include examples that use Linux command-line tools and scripting (e.g., Bash, shell scripts) for deployment and management.
Ensure parity in documentation by providing equivalent walkthroughs for both Windows/.NET and Linux/open-source stacks.
Highlight cross-platform deployment strategies and tools, not just those familiar to Windows users.
Consider reordering the sample list to alternate between Windows-centric and Linux-centric technologies, or group by language/platform.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias primarily through exclusive references to the Azure portal (a web UI, but often associated with Windows-centric workflows) and the absence of Linux-specific instructions or command-line examples. The only development tool mentioned for local workflow creation is Visual Studio Code, which is cross-platform, but there are no references to Linux-native tools, shell commands, or CLI-based approaches. Additionally, in the connector technical reference, App Service Environment v3 is specified as 'Windows plans only' without mention of Linux plans or parity.

Recommendations:

Include explicit instructions and examples for using the Azure CLI and/or Azure PowerShell on Linux and macOS, especially for common tasks like retrieving storage account keys, connection strings, and managing resources.
Clarify whether all features and connectors are available on Linux-based App Service plans, and provide guidance for Linux users if there are differences.
Add references to Linux-native tools (e.g., az CLI, bash scripts) for managing Azure resources, alongside or instead of Azure portal steps.
Where screenshots are used, consider including examples from Linux environments or terminal-based workflows.
Explicitly state OS requirements or limitations for features that are Windows-only, and provide alternatives or workarounds for Linux users where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by referencing 'IBM Informix for Windows running in Azure virtualization' as the primary cloud-based example and by listing 'Windows (kerberos)' as an authentication type without mentioning Linux equivalents. There is no explicit Linux example or mention of Linux authentication mechanisms, and the documentation does not clarify cross-platform compatibility or provide parity in examples for Linux-based Informix deployments.

Recommendations:

Explicitly mention support for Linux-based Informix servers, both on-premises and in the cloud.
Provide example connection strings and scenarios for Informix running on Linux, not just Windows.
Clarify authentication options for Linux deployments (e.g., PAM, LDAP, or other mechanisms) alongside Windows (kerberos).
Ensure that screenshots and example values do not imply Windows-only environments (e.g., use generic hostnames or include Linux hostnames).
Add a note or section about cross-platform compatibility, including any differences or considerations for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by requiring the use of the 3270 Design Tool, which is dependent on Microsoft .NET Framework 4.8 (Windows-only), and by not mentioning or providing alternatives for Linux users. There are no Linux-compatible tools or instructions, nor are there any examples or guidance for Linux environments.

Recommendations:

Provide information about the platform compatibility of the 3270 Design Tool. If it is Windows-only, state this explicitly and suggest workarounds for Linux users (e.g., using Wine, or running in a Windows VM).
If possible, offer or reference a cross-platform or Linux-native tool for generating HIDX files.
Include explicit instructions or examples for Linux users, such as how to upload files to Azure from Linux (e.g., using Azure CLI or azcopy), and clarify that the Azure portal is web-based and accessible from any OS.
Mention any limitations or requirements for Linux users upfront in the prerequisites section.
If the connector or related tools are only supported on Windows-based App Service plans, clarify this and provide guidance for Linux-based plans or environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page provides instructions primarily through the Azure Portal UI and does not include any command-line examples. There are no references to Windows-specific tools or PowerShell, but there is also a lack of parity for Linux users: no CLI (Azure CLI, Bash) examples are provided, which are commonly used on Linux and cross-platform environments. The absence of CLI instructions may implicitly favor Windows users, who are more likely to use the portal, and does not address the needs of Linux or automation-focused users.

Recommendations:

Add Azure CLI examples for all configuration steps, including registering the GitHub app and configuring authentication providers.
Include Bash script snippets for secret management and app configuration.
Explicitly mention that all steps can be performed via CLI on Linux, macOS, or Windows, and provide links to relevant CLI documentation.
Ensure that any future troubleshooting or advanced configuration sections include both portal and CLI/Bash instructions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) and the HIS Designer for Logic Apps, which are Windows-only tools. The only prerequisite for the HIS Designer is Microsoft .NET Framework 4.8, which is not natively available on Linux. There are no examples or instructions for Linux or cross-platform environments, nor are alternative tools or methods mentioned for non-Windows users.

Recommendations:

Provide information on whether the HIS Designer for Logic Apps can be used on Linux (e.g., via Mono, .NET Core, or Wine), or explicitly state if it is Windows-only.
If possible, offer alternative methods or tools for generating the required HIDX metadata file on Linux or macOS.
Include examples or workflow steps that can be performed from Linux environments, or clarify any platform limitations.
Mention any future plans or workarounds for non-Windows users, such as containerized versions of the HIS Designer or REST APIs for metadata generation.
Clearly indicate in the prerequisites section that the current tooling is Windows-specific, and provide guidance for users on other platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Azure CLI (Bash) and PowerShell examples for all steps, but does not include any Linux-specific shell examples (such as plain Bash or zsh), nor does it mention Linux tooling or patterns. PowerShell is given equal prominence to Azure CLI, which is more common on Windows, and the PowerShell examples use Windows-style variable syntax. In some cases, PowerShell examples are shown before or alongside CLI, but there is no explicit Linux-first approach. There are no examples or notes for Linux-specific environments, nor any mention of WSL or native Linux shells.

Recommendations:

Add explicit Bash (Linux/macOS) examples where relevant, especially for environment variable syntax and command usage.
Clarify that Azure CLI examples are intended for Bash/zsh shells on Linux/macOS, and PowerShell examples are for Windows users.
Consider providing a Linux/macOS tab (with Bash syntax) in addition to Azure CLI and PowerShell, or clarify that the Azure CLI tab uses Bash.
Include notes on any differences in command output or file paths (e.g., kubeconfig location) between Windows and Linux.
Where PowerShell is used, ensure it is not presented as the default or primary method unless justified by audience data.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and PowerShell examples for all command-line steps, but in several key sections, the PowerShell (Windows) workflow is more detailed and prominent. For example, the deployment of the frontend app is described with a simple Bash command, but the PowerShell section includes extensive object creation and scripting, which may suggest a Windows-centric workflow. Additionally, in some places, PowerShell examples or explanations are given after Bash, but with more detail, indicating a possible subtle 'windows_first' or 'windows_heavy' bias.

Recommendations:

Ensure parity in explanation depth and workflow between Bash and PowerShell sections. If the PowerShell workflow requires more steps, consider providing equivalent Bash scripting for advanced scenarios.
Where possible, avoid making the PowerShell workflow appear as the 'default' or more complete path. If additional steps are needed for PowerShell, clarify why and provide Bash equivalents.
Consider including a short explanation at the start that both Bash (Linux/macOS) and PowerShell (Windows) are equally supported, and that users should follow the tab that matches their environment.
If advanced object-based scripting is shown for PowerShell, provide a Bash script or reference for users who want to automate similar steps on Linux.
Review the order and prominence of examples to ensure neither platform is implicitly prioritized.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both PowerShell and curl examples for invoking HTTP endpoints and viewing logs, but PowerShell examples are consistently presented first. There are no Linux-specific shell or tool examples beyond curl, and the use of PowerShell may suggest a Windows-centric workflow. However, the main deployment and setup steps use Azure CLI, which is cross-platform.

Recommendations:

Alternate the order of PowerShell and curl examples, or present curl (Linux/macOS) examples first to avoid implicit Windows prioritization.
Explicitly mention that curl commands are suitable for Linux/macOS users and PowerShell for Windows users.
Consider adding bash script examples or referencing Linux-native tools where appropriate.
Clarify in the prerequisites or relevant sections that all steps are cross-platform unless otherwise noted.
If PowerShell-specific features are used, provide equivalent bash or shell script alternatives.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exhibits a Windows bias by exclusively referencing Hyper-V, a Windows-specific virtualization technology, as the foundation for session isolation. There is no mention of Linux-based isolation technologies (such as KVM, gVisor, or Kata Containers), nor is there any discussion of how sessions operate or are isolated on non-Windows platforms. The documentation also links to Windows Server Hyper-V documentation, reinforcing the Windows-centric perspective.

Recommendations:

Include information on whether Linux-based isolation technologies (e.g., KVM, gVisor, Kata Containers) are used or supported for session isolation, especially since Azure Container Apps can run Linux containers.
Provide links to documentation for Linux-based sandboxing or isolation technologies if applicable.
Clarify if Hyper-V is used for all session types regardless of the underlying OS, or if different technologies are used for Linux containers.
Ensure that any platform-specific details (such as isolation mechanisms) are presented in a cross-platform manner, or clearly state any platform limitations or differences.
If only Hyper-V is supported, explicitly state this and provide guidance for Linux users regarding compatibility or alternatives.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation does not provide any command-line troubleshooting examples, but all diagnostic instructions are given in the context of the Azure Portal UI, which is platform-agnostic. However, there is a notable absence of CLI-based troubleshooting steps (such as using Azure CLI, Bash, or PowerShell), and no mention of Linux-native tools or workflows. This omission may disadvantage Linux users who typically rely on command-line tools for container diagnostics. The documentation also does not mention Windows-specific tools, but the lack of Linux examples still constitutes a subtle bias.

Recommendations:

Add troubleshooting steps using Azure CLI commands that can be run from Bash or PowerShell, ensuring parity for both Linux and Windows users.
Include examples of how to access container logs and exit codes using cross-platform tools (e.g., az containerapp revision list, az containerapp logs).
Mention Linux-native diagnostic tools (such as journalctl, docker logs, or kubectl logs if relevant) where appropriate.
Explicitly state that the Azure Portal steps are platform-independent, and provide alternative CLI-based instructions for users who prefer command-line interfaces.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page lists several cluster templates, and among them, the Microsoft HPC Pack (a Windows-specific job scheduler) is featured prominently with a direct link to PowerShell documentation. This is the only template in the table that links to a Windows-specific technology and documentation, while the others are cross-platform or Linux-centric. The HPC Pack entry is also placed before several Linux-native schedulers, which may suggest a Windows-first bias.

Recommendations:

Ensure that all scheduler templates (Windows and Linux) are presented with equal prominence and in a neutral order (e.g., alphabetical or by popularity).
Avoid linking to Windows/PowerShell documentation unless equivalent Linux documentation is also provided.
If referencing Windows-specific tools like HPC Pack, provide context about platform compatibility and offer Linux alternatives or equivalents in the same section.
Consider adding explicit Linux usage examples or links for each template, especially where Windows tools are mentioned.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page shows 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 examples. While the table lists both Linux and Windows images, the configuration snippets and guidance focus exclusively on Windows, with no Linux or cross-platform parity in the examples.

Recommendations:

Provide Linux-based examples alongside Windows examples for specifying images using ImageName, URN, and labels (e.g., use 'cycle.image.ubuntu22' and 'Canonical:0001-com-ubuntu-server-focal:20_04-lts:latest').
Alternate the order of examples or present both Windows and Linux examples together to avoid implicit prioritization.
Include a note or section explicitly addressing Linux image usage and any platform-specific considerations.
Ensure that all configuration snippets and usage instructions demonstrate both Windows and Linux scenarios for parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively provides troubleshooting steps and examples for SQL Server (a Microsoft/Windows-centric database) using T-SQL queries and stored procedures. There are no examples or guidance for Linux-based or open-source databases, nor any mention of Linux command-line tools or environments. The focus on SQL Server and absence of cross-platform parity constitutes a Windows bias.

Recommendations:

Include troubleshooting steps and examples for popular Linux/open-source databases that support CDC, such as PostgreSQL or MySQL, where applicable.
Provide equivalent command-line examples for Linux environments (e.g., using psql or mysql CLI tools) if CDC is supported.
Mention any platform-specific limitations or differences explicitly, and offer guidance for users running Azure Data Factory with non-Windows sources.
If SQL Server is the only supported source, clarify this early in the documentation and provide links or notes for Linux users seeking CDC solutions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by referencing Windows-specific tools (SQL Server Management Studio) for database operations and omitting Linux-friendly alternatives. There are no explicit PowerShell or command-line examples, but the only tool mentioned for SQL interaction is SSMS, which is primarily a Windows application. No Linux or cross-platform alternatives (such as Azure Data Studio, sqlcmd, or CLI tools) are suggested, and no Linux-specific instructions are provided.

Recommendations:

Mention and provide examples using cross-platform tools such as Azure Data Studio or sqlcmd for database operations, alongside SQL Server Management Studio.
Explicitly state that users can perform SQL commands from any OS using Azure Data Studio, sqlcmd, or the Azure Portal's Query Editor.
Where GUI instructions are given (e.g., 'right-click the database'), provide equivalent command-line or cross-platform steps.
Add a note clarifying that all steps can be performed from Linux, macOS, or Windows, and link to relevant cross-platform tool documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation references PowerShell and the SDK as methods for managing Data Factory resources, but does not mention or provide examples for equivalent Linux-native tools (such as Azure CLI or Bash scripting). There are no Linux-specific instructions or examples, and PowerShell is implicitly prioritized as the non-portal automation method.

Recommendations:

Explicitly mention Azure CLI as an alternative to PowerShell for managing Data Factory resources, and provide equivalent CLI command examples.
Include Bash scripting examples where automation is discussed, especially for Linux users.
Ensure that references to automation tools do not assume a Windows environment; mention both PowerShell and CLI equally and in parallel.
Where SDKs are mentioned, clarify that they are cross-platform and provide links or examples for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently presents Windows-focused examples and reference architectures, particularly in the 'Virtual machine (Windows/Linux) workloads' section. While the section heading mentions both Windows and Linux, all detailed examples, diagrams, and links are specific to Windows (e.g., 'Windows N-tier application on Azure'). There are no Linux-specific reference architectures, diagrams, or links provided, and Linux is not equally represented in the scenarios or guidance.

Recommendations:

Add parallel Linux-specific reference architectures and diagrams, such as 'Linux N-tier application on Azure', with equivalent depth and detail.
Include links to Linux-focused Azure architecture documentation where available.
Ensure that examples and best practices are presented for both Windows and Linux workloads, or use neutral, OS-agnostic language and diagrams where possible.
Where both Windows and Linux are supported, explicitly mention and illustrate both, rather than only referencing Windows.
Review and update headings and content to avoid implying parity where it does not exist (e.g., do not mention 'Windows/Linux' if only Windows is detailed).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by explicitly stating that the connector supports only Windows versions for the self-hosted integration runtime, and by linking to Windows-specific prerequisites. There are no Linux examples or mention of Linux support for the self-hosted integration runtime, and no Linux command-line or configuration guidance is provided.

Recommendations:

Clearly state whether Linux is supported or not for the self-hosted integration runtime in this scenario. If Linux is not supported, explain the limitation and provide a roadmap or alternatives if possible.
If Linux support is available or planned, provide equivalent Linux instructions, including prerequisites, installation, and configuration steps.
Include Linux-specific examples or notes where relevant, such as environment setup, service management, and troubleshooting.
Avoid language that implies Windows is the only or default platform unless it is a technical requirement, and make this explicit to avoid confusion.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation references and highlights the Execute SSIS Package activity, which is a Windows-centric technology, alongside more cross-platform Data Factory activities. There is a notable emphasis on SSIS (a Windows-only tool), including screenshots and step-by-step lineage instructions, without mentioning Linux alternatives or clarifying platform support. The documentation does not provide Linux-specific examples or guidance, and the order of presentation places the Windows-only SSIS activity on equal footing with cross-platform activities.

Recommendations:

Clearly indicate that SSIS is a Windows-only technology and specify any platform limitations.
Provide examples or mention of Linux-compatible activities or tools within Data Factory, if available.
If possible, include Linux-specific guidance or alternatives for users who do not have access to SSIS.
Reorder examples to present cross-platform activities (Copy, Data Flow) before Windows-only activities (SSIS), and clarify platform compatibility in each section.
Add a note in the prerequisites or relevant sections about platform support for each activity type.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias primarily by referencing Windows-specific tooling (Dynamics XRM tooling for Windows client applications) and omitting any mention of Linux or cross-platform alternatives. There are no PowerShell or CMD examples, but the only referenced SDK/tooling is Windows-centric. No Linux-specific instructions, tools, or parity notes are provided, and the documentation does not clarify cross-platform support or limitations.

Recommendations:

Explicitly state whether the Dynamics XRM tooling and connector are supported on Linux or cross-platform environments, or provide alternatives if available.
If there are Linux-compatible SDKs, CLIs, or APIs for interacting with Dynamics 365/Dataverse, include references and examples.
Add a section or note clarifying any platform dependencies or limitations, especially for users deploying self-hosted integration runtimes or custom connectors on Linux.
If only Windows is supported for certain features, clearly document this and suggest workarounds or roadmap for Linux support.
Where possible, provide parity in examples and tooling references for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exhibits a mild Windows bias, primarily in the authentication and certificate management sections. Windows-specific tools (e.g., MMC, certificate store instructions) are referenced exclusively for managing client certificates on self-hosted Integration Runtime. Additionally, Windows authentication is listed alongside other authentication types, but there is no mention of Linux equivalents or instructions for Linux environments. In the 'TIP' for testing HTTP requests, only Windows-centric tools (Visual Studio, PowerShell) are mentioned, with no Linux alternatives like curl or wget.

Recommendations:

Add Linux-equivalent tools and instructions wherever Windows tools are mentioned. For example, suggest using 'curl' or 'wget' for testing HTTP endpoints, alongside PowerShell and Visual Studio.
Provide guidance for managing client certificates on Linux-based self-hosted Integration Runtime machines, including certificate storage locations and permission management.
Clarify whether Windows authentication is supported only on Windows-based Integration Runtime, and if so, explicitly state this and suggest alternatives for Linux environments.
Ensure that examples and troubleshooting steps are platform-neutral or provide both Windows and Linux variants where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by referencing Windows versions as prerequisites for the self-hosted integration runtime, without mentioning Linux support or alternatives. There are no Linux-specific instructions, examples, or clarifications, and the only OS mentioned is Windows. No PowerShell or Windows command-line examples are present, but the lack of Linux parity in prerequisites and examples is notable.

Recommendations:

Explicitly state whether the self-hosted integration runtime supports Linux, and provide installation instructions for Linux if available.
If Linux is not supported, clearly mention this limitation to set user expectations.
Include Linux-specific examples or notes where relevant, such as environment setup, configuration, or troubleshooting.
Where OS-specific requirements are listed, present both Windows and Linux options (if supported), or clarify support status for each.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references a pattern for sharing SelfHosted Integration Runtime that is published specifically for PowerShell, which is a Windows-centric tool. There are no equivalent examples or references for Linux or cross-platform command-line tools. Additionally, there are no command-line examples at all (neither Windows nor Linux), but the only tool-specific link is to a PowerShell-based guide.

Recommendations:

Provide equivalent documentation or examples for Linux users, such as using Azure CLI or Bash scripts for cloning or sharing SelfHosted Integration Runtime.
When referencing patterns or guides, include both PowerShell and Azure CLI (or REST API) versions, and mention them together or in a platform-neutral order.
Explicitly state if certain operations can be performed using cross-platform tools, and provide links or examples for those tools.
Avoid referencing only Windows-specific tools (like PowerShell) without mentioning alternatives for other platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation assumes the use of Windows environments by referencing tools and patterns specific to Windows, such as the Integration Runtime Configuration Manager and ODBC DSN setup, without mentioning Linux equivalents or providing Linux-specific guidance. There are no examples or troubleshooting steps for Linux-based Integration Runtime hosts.

Recommendations:

Add explicit instructions for installing and configuring 64-bit ODBC drivers on Linux-based Integration Runtime hosts, including common distributions and package managers.
Document how to set up and reference ODBC DSNs on Linux (e.g., editing /etc/odbc.ini and /etc/odbcinst.ini), and provide example connection strings for Linux.
Clarify whether the Integration Runtime Configuration Manager is available on Linux, and if not, provide alternative troubleshooting steps for Linux environments (such as using command-line tools like isql or unixODBC diagnostics).
Include screenshots or terminal examples for Linux where UI or tool usage is described.
Explicitly state OS requirements and limitations for self-hosted Integration Runtime, and link to cross-platform setup guides if available.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by requiring the installation of the SAP .NET Connector 3.0, which is only available for Windows, as a prerequisite for using the SAP BW Open Hub connector. There are no instructions or examples for Linux environments, nor are alternative cross-platform connectors mentioned. The documentation assumes the use of Windows-based Self-hosted Integration Runtime and does not address Linux users or provide parity guidance.

Recommendations:

Explicitly state the platform requirements and limitations (e.g., that the SAP .NET Connector 3.0 is Windows-only) at the beginning of the prerequisites section.
If Linux is not supported, clearly mention this and, if possible, provide a roadmap or alternatives for Linux users.
If any cross-platform or Linux-compatible SAP connectors exist (such as SAP Java Connector or ODBC/JDBC options), mention them and provide guidance or links.
Provide example setups or troubleshooting notes for Linux users, or direct them to relevant resources if support is limited.
Consider advocating for or documenting any future plans for Linux support in the Self-hosted Integration Runtime or SAP connector stack.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in the troubleshooting and prerequisites sections, where it instructs users to place SAP NetWeaver RFC SDK libraries in the %windir%\system32 folder—a Windows-specific path. There are no equivalent instructions or examples for Linux-based Self-hosted Integration Runtime setups, nor is there mention of Linux library paths or troubleshooting steps. All examples and configuration steps are platform-agnostic JSON or UI-based, but the only OS-specific guidance is for Windows.

Recommendations:

Add explicit instructions for installing and configuring the SAP NetWeaver RFC SDK libraries on Linux-based Self-hosted Integration Runtime machines, including typical library paths (e.g., /usr/lib, /opt/sap, etc.).
Include troubleshooting tips for Linux environments, such as checking LD_LIBRARY_PATH and file permissions.
Mention both Windows and Linux in all OS-specific guidance, or clarify when instructions are Windows-only.
Provide example commands or steps for both Windows and Linux wherever file placement or environment configuration is discussed.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias towards Windows environments by requiring the SAP Connector for Microsoft .NET (a Windows-only component) as a prerequisite for the self-hosted integration runtime. There are no instructions, examples, or guidance for Linux-based integration runtimes or SAP connectors. All setup steps, tooling, and screenshots implicitly assume a Windows environment, and there is no mention of Linux compatibility or alternatives.

Recommendations:

Explicitly state whether Linux-based self-hosted integration runtimes are supported or not for SAP table integration. If not supported, clarify this limitation early in the prerequisites section.
If Linux support is possible (e.g., via Java connectors or other cross-platform SAP libraries), provide equivalent setup instructions and examples for Linux environments.
Include a table or section comparing Windows and Linux support for SAP connectors, listing any differences in prerequisites, setup, or functionality.
Where screenshots or instructions are Windows-specific, add notes or alternative steps for Linux users (if applicable).
If only Windows is supported, suggest workarounds for Linux users, such as running the integration runtime in a Windows VM or container.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references Windows support explicitly for the self-hosted integration runtime and does not mention Linux support or provide Linux-specific instructions or examples. There are no Linux equivalents or parity information, and no examples or guidance for Linux-based environments.

Recommendations:

Explicitly state whether Linux is supported for the self-hosted integration runtime and, if so, provide instructions or a link to Linux setup documentation.
If Linux is not supported, clearly mention this limitation to inform users.
Include Linux-specific examples or notes where relevant, especially in sections discussing prerequisites or environment setup.
Ensure parity in tool and platform references by mentioning both Windows and Linux where applicable.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation consistently references the Azure portal, PowerShell, and SDKs for managing credentials, but does not provide any explicit Linux or cross-platform CLI (e.g., Azure CLI) examples. PowerShell is mentioned as a scripting option, but there is no mention or example of using Bash, Azure CLI, or Linux-native tools. This creates a bias toward Windows-centric tools and workflows.

Recommendations:

Include Azure CLI (az) command examples for all credential management tasks, as Azure CLI is cross-platform and widely used on Linux.
When listing scripting options, mention Azure CLI and Bash scripts alongside PowerShell and SDKs.
Add screenshots or step-by-step instructions for performing tasks using Azure CLI in addition to the Azure portal and PowerShell.
Explicitly state that all operations can be performed from Linux/macOS environments using Azure CLI, and provide links to relevant documentation.
Ensure that REST API examples include curl or httpie commands, which are common on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing only Windows-based virtual machine examples (specifically referencing 'Windows Server 2019 Datacenter - Gen1') for deploying the self-hosted integration runtime (IR). There are no instructions or examples for deploying the self-hosted IR on Linux-based virtual machines, nor are Linux images mentioned as options. The documentation also omits any Linux-specific configuration or troubleshooting guidance.

Recommendations:

Add parallel instructions and examples for deploying the self-hosted IR on supported Linux distributions, including recommended Linux VM images.
Explicitly mention that the self-hosted IR can be installed on both Windows and Linux, if supported, and provide links to relevant installation guides for each OS.
Include Linux-specific configuration steps, such as firewall rules, DNS setup, and package dependencies, where applicable.
Ensure screenshots and UI walkthroughs are not Windows-centric, or provide Linux equivalents where the experience differs.
Review all sections for implicit assumptions of a Windows environment and clarify cross-platform support where relevant.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references the XrmToolBox, a Windows-only tool, as a troubleshooting step in multiple places. There are no Linux or cross-platform alternatives mentioned, nor are there command-line or PowerShell examples, but the exclusive mention of a Windows GUI tool introduces a Windows bias. No Linux-specific guidance or parity is provided.

Recommendations:

Where XrmToolBox is recommended, also mention cross-platform alternatives or clarify if none exist.
If possible, provide equivalent troubleshooting steps using REST APIs, CLI tools, or scripts that are platform-agnostic.
Explicitly state the platform requirements for XrmToolBox and suggest workarounds for Linux/macOS users, such as using Wine, or recommend alternative approaches.
Consider including examples or links for troubleshooting Dynamics 365 connectivity and data issues using PowerShell (cross-platform), Azure CLI, or REST API calls.
Audit the documentation for other implicit Windows dependencies and add Linux/macOS guidance where feasible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by exclusively describing role assignment and management via the Azure Portal UI, which is most commonly accessed and documented in a Windows context. There are no CLI, PowerShell, or command-line examples (which could be cross-platform), nor are there Linux-specific instructions or examples for authentication, token acquisition, or role assignment. The absence of CLI or Linux-native tooling examples may disadvantage Linux users or those automating tasks outside the Azure Portal.

Recommendations:

Add Azure CLI examples for assigning roles (e.g., using `az role assignment create`) alongside or before portal instructions to ensure parity for Linux and automation users.
Include sample commands for obtaining Microsoft Entra JWT tokens using cross-platform tools such as curl, Azure CLI, or relevant SDKs in Python or Bash.
Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide links to CLI documentation.
Where possible, provide both portal and command-line instructions, and avoid assuming the user is operating in a Windows environment.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is generally platform-neutral, as it describes data flow functions in Azure Data Factory and Synapse Analytics, which are cloud-based and not OS-specific. However, there are a few instances where Windows-specific terminology or encodings are mentioned (e.g., 'Windows-1252' encoding in examples for fromBase64 and toBase64), and Windows time zones (e.g., 'PST') are listed before IANA/Olson equivalents. There are no PowerShell-heavy examples, nor are there Windows command-line tools or patterns. Linux-specific encodings, locales, or time zones are not mentioned, and Linux-first terminology is not used.

Recommendations:

When providing examples of character encodings (e.g., in fromBase64, toBase64), include both Windows-specific (e.g., 'Windows-1252') and common Linux/UNIX encodings (e.g., 'UTF-8', 'ISO-8859-1') to demonstrate parity.
When listing time zones, prefer IANA/Olson time zone names (e.g., 'America/New_York', 'Europe/Berlin') and mention Windows time zone abbreviations only as secondary options.
If referencing locale or encoding, clarify that the functions are not limited to Windows environments and work equally on Linux-based integration runtimes.
Consider adding a note or example that demonstrates the use of these functions in a Linux context, especially where encoding or locale is relevant.
Review all examples and terminology to ensure that neither Windows nor Linux is implicitly prioritized, and that documentation is inclusive of both environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing PowerShell and Azure CLI for enabling Key Vault properties but does not provide any command-line examples for either platform. The UI walkthroughs and screenshots are exclusively from the Azure Portal, which is platform-agnostic but often more familiar to Windows users. There are no Linux-specific instructions, shell commands, or mentions of Linux tooling. The ordering of PowerShell before Azure CLI in the prerequisites section also subtly prioritizes Windows tooling.

Recommendations:

Provide explicit command-line examples for both PowerShell (Windows) and Bash (Linux) when describing how to enable Key Vault properties such as Soft Delete and Do Not Purge.
Include Azure CLI examples using Bash syntax, and clarify that Azure CLI is cross-platform.
When listing options for configuration, alternate the order (e.g., mention Azure CLI before PowerShell in some sections) or present them in parallel to avoid implicit prioritization.
Add a section or callout for Linux/macOS users, highlighting any differences or confirming that all steps are cross-platform.
Where possible, include screenshots or terminal output from both Windows and Linux environments to reinforce parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation assumes the use of Self-Hosted Integration Runtime (SHIR), which is only available for Windows, and provides no mention of Linux support or alternatives. There are no Linux-specific instructions, examples, or troubleshooting steps, and the guidance implicitly assumes a Windows environment for driver installation and runtime hosting.

Recommendations:

Explicitly state that SHIR is only supported on Windows, and if possible, provide guidance or links for Linux users (e.g., Azure IR or other alternatives).
Add a section clarifying platform support and any workarounds for Linux environments.
If Linux support is planned or available via other runtimes, include parallel instructions or examples for Linux.
Mention any limitations or considerations for non-Windows users early in the documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively references the Microsoft Integration Runtime Configuration Manager, a Windows-only GUI tool, for sending logs. There are no instructions or examples for performing the same task on Linux systems, nor is there any mention of Linux command-line alternatives or parity.

Recommendations:

Provide equivalent instructions for Linux environments, such as using command-line tools or scripts to collect and send logs.
Explicitly state platform requirements or limitations if the feature is only available on Windows, and suggest workarounds for Linux users.
Include screenshots or examples for both Windows and Linux where applicable.
Mention whether the self-hosted integration runtime supports Linux, and if so, document the log collection process for Linux deployments.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation assumes the Self-hosted Integration Runtime (SHIR) is running on a machine where a user can open a browser and visit a website (whatismyipaddress.com) to determine the outbound IP. This is a Windows-centric approach, as SHIR is often run on Windows, and no Linux-specific instructions or command-line alternatives are provided. There are no Linux or cross-platform command-line examples for retrieving the IP address, and the workaround does not consider headless or Linux environments.

Recommendations:

Provide Linux-specific instructions for retrieving the outbound IP address, such as using curl or wget from the command line (e.g., curl ifconfig.me).
Clarify whether SHIR is supported on Linux, and if so, include parity in troubleshooting steps and examples.
Offer command-line alternatives for environments where a browser is not available, benefiting both Windows Server Core and Linux users.
Review other workarounds and instructions to ensure they are not implicitly assuming a Windows GUI environment.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows by exclusively referencing Windows-centric tools and concepts such as SQL Server Management Studio (SSMS), SQL Server Agent jobs, and Windows Firewall. There are no examples or mentions of Linux-based tools, command-line utilities, or cross-platform alternatives for managing or deploying SSIS packages. Additionally, PowerShell is referenced as a method for configuring certain Azure features, with no mention of Bash, Azure CLI, or other Linux-native approaches.

Recommendations:

Include examples using Azure CLI and Bash scripts for provisioning and managing Azure-SSIS IR and related resources, alongside or instead of PowerShell.
Mention cross-platform tools (such as Azure Data Studio) in addition to SSMS for managing SQL Managed Instance and SSISDB.
Clarify that SSIS package deployment and management can be performed from non-Windows environments, if supported, and provide relevant instructions.
When referencing firewall or network configuration, provide guidance for both Windows Firewall and Linux iptables/ufw where applicable.
Explicitly state platform requirements and offer parity in instructions for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation assumes the use of the SAP .NET Connector 3.0, which is only available for Windows, and requires installation on the same machine as the self-hosted integration runtime. There are no instructions or examples for Linux environments, nor is there mention of alternatives for non-Windows users. All setup steps and screenshots implicitly target Windows users.

Recommendations:

Explicitly state that the SAP .NET Connector 3.0 and self-hosted integration runtime are Windows-only, and clarify platform requirements early in the prerequisites.
If possible, provide guidance or alternatives for Linux environments, such as using the ODBC connector or other cross-platform integration runtimes.
Include a section addressing what Linux or macOS users should do, or link to relevant documentation for non-Windows data integration scenarios.
If no Linux support exists, clearly document this limitation to set user expectations.
Consider adding a feature request or roadmap note if Linux support is planned for the future.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides a command example using the ARMClient tool, which is a Windows-centric utility, and does not mention or provide equivalent instructions for Linux or cross-platform alternatives. There are no Linux shell or CLI examples, nor is there guidance for users on non-Windows systems.

Recommendations:

Provide equivalent instructions using Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
Explicitly mention whether ARMClient is available for Linux/macOS, and if not, suggest alternatives.
Add bash or shell command examples alongside PowerShell/Windows-specific ones.
Clarify any OS-specific requirements or differences in the installation and usage of required tools.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates Windows bias by mentioning the use of the Windows-specific tool 'Robocopy' for applying ACLs to exported Azure Files data, without providing a Linux equivalent or alternative. Additionally, there are no Linux-specific tools, commands, or examples provided for exporting data or handling ACLs, and the only script referenced is a PowerShell (.ps1) script, which is native to Windows. There are no explicit Linux examples or references to Linux-native tools for data copy or ACL management.

Recommendations:

Provide Linux-equivalent tools and examples for applying ACLs to exported Azure Files data, such as using 'rsync', 'setfacl', or 'getfacl'.
Mention and provide sample commands for Linux file copy and ACL preservation, alongside or in place of the Robocopy recommendation.
Offer cross-platform scripts (e.g., Bash or Python) for generating XML files, or clarify if the PowerShell script can be run on Linux (e.g., with PowerShell Core), and provide instructions for doing so.
Include a section or note explicitly addressing Linux and macOS users, outlining supported workflows and any OS-specific considerations.
Ensure parity in documentation by listing both Windows and Linux approaches wherever OS-specific tools or commands are referenced.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively providing SQL Server and Azure SQL Database examples for the control table, without mentioning or providing examples for Linux-based databases or environments. There are no examples or instructions for creating the control table in Oracle, Netezza, or Teradata, which are commonly run on Linux/UNIX systems. The workflow and screenshots also implicitly assume a Windows-centric environment.

Recommendations:

Add examples for creating the control table in Oracle, Netezza, and Teradata, including relevant SQL syntax and notes about platform-specific differences.
Explicitly mention that the process applies to both Windows and Linux-based database systems, and provide guidance for users working in Linux environments.
Include screenshots or instructions that are not specific to Windows tools or interfaces, or provide Linux/UNIX equivalents where applicable.
Clarify any platform-specific prerequisites or steps, such as connection setup or authentication, for Linux-hosted databases.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively uses Azure SQL Database and T-SQL (SQL Server) for control tables and stored procedures, with no mention of Linux-friendly or cross-platform alternatives such as PostgreSQL, MySQL, or open-source database engines. All example code is in T-SQL, which is most commonly associated with Windows environments. There are no examples or guidance for users who may wish to use Linux-based databases or tools.

Recommendations:

Provide alternative examples using open-source databases such as PostgreSQL or MySQL, including equivalent table and stored procedure creation scripts.
Clarify whether Azure Data Factory supports control tables and stored procedures in non-SQL Server databases, and provide guidance for those scenarios.
Include a note or section on how to adapt the templates for users who do not use Azure SQL Database, especially those on Linux-based platforms.
If possible, provide shell (bash) or cross-platform command-line examples for interacting with the control tables, not just T-SQL.
Mention any limitations or requirements for using non-Windows, non-SQL Server environments with these templates.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation shows mild Windows bias in its references to encoding names and Java runtime detection. Encoding examples reference Windows code pages (e.g., 'windows-1250'), and the process for locating Java on Self-hosted Integration Runtime checks the Windows registry first before using the cross-platform JAVA_HOME environment variable. There are no explicit Linux/POSIX shell or tool examples, and the documentation does not mention Linux-specific patterns or alternatives.

Recommendations:

When referencing encoding names, provide both Windows and common Linux/Unix encoding names (e.g., 'windows-1250' and 'ISO-8859-2').
In instructions for Java runtime detection, clarify that JAVA_HOME is the standard on Linux/macOS and that the registry check is Windows-specific.
Where file paths or environment variables are mentioned, show both Windows and Linux/macOS syntax (e.g., C:\path vs /path).
If referencing external tools or APIs (such as .NET encoding names), note Linux/Unix equivalents or cross-platform considerations.
Add examples or notes for Linux users where relevant, especially in sections discussing system configuration or environment variables.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias, primarily through its use of Windows-style path separators (e.g., 'scripts\kona\SearchLogProcessing.txt') in JSON examples and U-SQL script references. There are no explicit Linux or cross-platform examples, and no mention of Linux/Unix path conventions. While the documentation does not reference Windows-specific tools or PowerShell, the implicit assumption of Windows paths may confuse or inconvenience Linux users.

Recommendations:

Provide examples using both Windows (\) and Linux (/) path separators, or use forward slashes (/) which are supported on both platforms in Azure Data Lake.
Add a note clarifying that both path styles are supported, and recommend using forward slashes for cross-platform compatibility.
Explicitly mention that the examples are platform-agnostic, or provide a section on cross-platform considerations.
Review all code snippets and UI screenshots to ensure they do not reinforce a Windows-only workflow.
If relevant, include CLI or scripting examples (such as Azure CLI or Bash) alongside any UI or JSON examples.

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' executables (e.g., 'MyMapper.exe', 'MyReducer.exe') in both the JSON sample and file paths. There are no examples or mentions of Linux/Unix-style scripts (e.g., Python, Bash, or shell scripts), which are more common in Hadoop Streaming scenarios. The documentation implicitly assumes Windows tools and omits Linux equivalents.

Recommendations:

Provide parallel examples using Linux/Unix-style scripts (e.g., 'MyMapper.py', 'MyReducer.sh') in the JSON sample and file paths.
Explicitly mention that both Windows executables and Linux scripts are supported, and clarify any platform-specific considerations.
Include a section or note on how to prepare and upload Linux-based mapper and reducer scripts to Azure Storage.
Balance the documentation by showing both Windows and Linux usage patterns, especially in code and configuration samples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on SQL Server, Azure SQL Database, and Synapse Analytics, with instructions and examples tailored to these Microsoft-centric technologies. There is no mention of Linux-based SQL Server deployments, nor are there examples or guidance for using the Stored Procedure activity with open-source or non-Microsoft databases. Additionally, the prerequisite tutorial referenced is 'tutorial-transform-data-spark-powershell.md', which suggests a Windows/PowerShell-centric approach, with no alternative for Linux users.

Recommendations:

Include explicit mention and examples for using SQL Server on Linux, clarifying any differences in integration runtime setup or connectivity.
Provide alternative tutorials or references for Linux users, such as using Bash or Azure CLI instead of PowerShell.
Expand the scope to mention and, where possible, provide examples for invoking stored procedures in other supported databases (e.g., PostgreSQL, MySQL) if applicable.
Ensure that references to tools, scripts, or runtimes are cross-platform, or provide platform-specific instructions where differences exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by referencing Windows-specific tools and workflows (such as Notepad) and omitting Linux/macOS equivalents. The instructions for creating files and interacting with Azure Storage do not provide cross-platform alternatives or mention command-line options suitable for Linux users. The tutorial assumes a GUI workflow and does not address Linux-native tools or scripting approaches.

Recommendations:

When instructing users to create a text file (e.g., input.txt), mention cross-platform editors such as nano, vim, or provide a generic instruction like 'use your preferred text editor' with examples for both Windows (Notepad) and Linux/macOS (nano, vim, etc.).
For uploading files to Azure Blob Storage, in addition to Azure Storage Explorer (a GUI tool), provide CLI alternatives such as using the Azure CLI (az storage blob upload) or AzCopy, with example commands for both Windows and Linux/macOS.
Avoid referencing only Windows-specific tools in step-by-step instructions. Where browser support is mentioned, clarify that the Azure Portal is accessible from supported browsers on any OS.
Add a note or section on how to perform the same steps using command-line tools or scripts, which are often preferred by Linux users.
Ensure that all screenshots and instructions are either OS-agnostic or, where necessary, provide parallel instructions for Linux/macOS environments.

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 comes after the Bash example. Throughout the document, all portal-based instructions and screenshots are platform-agnostic, but there is a subtle Windows bias in the inclusion and detail of the PowerShell example. There are no Linux-specific tools or CLI-based alternatives for steps that could be performed outside the portal, and the PowerShell example may implicitly prioritize Windows users.

Recommendations:

Ensure that Bash and PowerShell examples are equally detailed and placed in parallel, not with one prioritized over the other.
Consider adding Azure CLI examples for steps like app registration, role assignment, and resource creation, which would benefit Linux and cross-platform users.
Explicitly mention that all steps can be performed on any OS using the Azure CLI or REST APIs, not just via the Azure Portal or PowerShell.
Where possible, provide Linux-specific troubleshooting tips or notes, especially for authentication and token generation.
Review screenshots and instructions to ensure they do not assume a Windows environment (e.g., avoid referencing Windows-specific UI elements or terminology).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by instructing users to use Notepad to create a text file, without mentioning cross-platform alternatives. No Linux- or macOS-specific instructions or examples are provided for file creation or tooling. All other steps are performed in the Azure Portal UI, which is cross-platform, but the initial file creation step assumes a Windows environment.

Recommendations:

When instructing users to create a text file, mention cross-platform editors (e.g., 'Use Notepad (Windows), TextEdit (macOS), or nano/vi (Linux) to create emp.txt').
Explicitly state that the Azure Portal and Azure Storage Explorer are available on Windows, macOS, and Linux.
Wherever local tools are referenced, provide alternatives or clarify that the instructions apply to all major operating systems.
Consider including a note or section for Linux/macOS users to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation shows subtle Windows bias by referencing Notepad as the default text editor for preparing the input file, without mentioning Linux or cross-platform alternatives. There are no explicit Linux or macOS instructions or examples for creating and uploading files, and no mention of common Linux tools or workflows. The rest of the tutorial is platform-neutral, focusing on the Azure portal UI.

Recommendations:

When instructing users to create a text file, mention cross-platform editors (e.g., 'use Notepad (Windows), TextEdit (macOS), or nano/vi (Linux)').
Provide command-line examples for creating the input file using echo/cat (Linux/macOS) and PowerShell (Windows), so users on all platforms have clear guidance.
When suggesting upload tools, mention cross-platform CLI tools like 'azcopy' or 'Azure CLI', and provide example commands for uploading the file from Linux/macOS terminals.
Add a note clarifying that all steps can be performed from any OS using the Azure portal, and link to documentation for cross-platform Azure tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on configuring Azure-SSIS IR using the Azure Portal and ADF UI, which are web-based and platform-agnostic, but does not provide any command-line examples or alternative approaches for Linux users. There is a reference to a separate PowerShell-based guide in the 'Related content', but no mention of Linux CLI tools (such as Azure CLI or Bash scripts), nor are any Linux-specific workflows or considerations discussed. All instructions and screenshots assume a GUI workflow, which is more common in Windows-centric documentation.

Recommendations:

Add equivalent instructions for configuring Azure-SSIS IR to join a virtual network using Azure CLI commands, which are cross-platform and commonly used on Linux.
Include references to Bash scripting or automation for Linux users, in addition to the PowerShell guide already referenced.
Explicitly state that the Azure Portal and ADF UI are accessible from any OS with a supported browser, and clarify any OS-specific requirements if they exist.
Where possible, provide side-by-side examples for both PowerShell (Windows) and Azure CLI (Linux/macOS) in relevant sections.
Mention and link to documentation on using Azure CLI for network and resource configuration, to ensure Linux users have clear guidance.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page provides code examples and workflows primarily using the .NET SDK (C#) and references Visual Studio Code for authoring, but does not include any Linux- or cross-platform-specific command-line examples (such as Bash, curl, or jq), nor does it mention Linux tools or workflows. REST API and Azure CLI are mentioned, but no concrete Linux shell examples are provided. There is an implicit Windows-first bias due to the focus on .NET/C# and lack of parity for Linux users.

Recommendations:

Add explicit Linux shell (Bash) examples for REST API usage, such as using curl to upload, retrieve, and delete models.
Include Azure CLI command examples for all major operations (upload, retrieve, delete models), and clarify that Azure CLI is cross-platform.
Where SDK examples are given in C#, provide equivalent examples in Python (which is widely used on Linux) or JavaScript.
Mention and demonstrate how to use common Linux tools (e.g., jq for JSON manipulation) in relevant workflows.
Ensure that any references to Visual Studio Code highlight its cross-platform nature and suggest alternative editors for Linux where appropriate.
If PowerShell or Windows-specific tools are referenced elsewhere, provide Linux alternatives or note their equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by listing Hyper-V (a Windows virtualization platform) before VMware ESXi and omitting any mention of Linux-based virtualization platforms (such as KVM or Xen). There are no Linux-specific examples, tools, or instructions provided, and the documentation does not clarify support for Linux hosts or clients beyond referencing included files. This may leave Linux users uncertain about compatibility and best practices.

Recommendations:

Explicitly mention support (or lack thereof) for Linux-based virtualization platforms such as KVM, Xen, or Proxmox, and provide relevant instructions if supported.
Include examples or notes for Linux client connectivity, such as mounting SMB shares from Linux systems or configuring firewall rules using common Linux tools (e.g., iptables, firewalld, ufw).
Balance the order of platform presentation (e.g., list VMware and Hyper-V together, or in alphabetical order) to avoid implicit prioritization of Windows solutions.
Provide parity in troubleshooting and configuration guidance for both Windows and Linux environments.
Clarify in the documentation whether Linux hosts can be used for the Data Box Gateway virtual device, and if not, state this explicitly to avoid ambiguity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias. While it mentions both Windows and Linux as supported OS types for VM images, it provides a prerequisite link that points to a Windows-specific tab (azcopy instructions), and does not provide any Linux-specific examples or guidance. There are no command-line examples (PowerShell, Bash, etc.), but where OS is mentioned, Windows is listed first. The documentation does not mention Linux tools or workflows, nor does it provide parity in example coverage for Linux users.

Recommendations:

Ensure that prerequisite links and referenced guides provide both Windows and Linux instructions, or default to a neutral landing page.
Where OS types are listed (e.g., 'Specify the OS associated with the image in your Storage account, either Windows or Linux'), alternate the order or explicitly state that both are equally supported.
Add explicit Linux examples or screenshots where relevant, especially for steps involving uploading VHDs or interacting with Azure tools.
If command-line tools are referenced (such as AzCopy), provide both Windows and Linux usage examples.
Review linked documentation (e.g., 'Upload a VHD image in your Azure Storage account') to ensure Linux parity and cross-link to Linux-specific instructions if available.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page provides only .NET/C# code examples and project setup instructions that are tailored to Windows-centric workflows (e.g., Visual Studio, right-click 'Save as', and 'console app project'). There are no Linux-specific instructions, CLI, or cross-platform code samples. The guidance for downloading files and setting up projects assumes a Windows environment and omits Linux or macOS equivalents.

Recommendations:

Include equivalent instructions for Linux and macOS users, such as using 'curl' or 'wget' to download files instead of browser-based 'right-click Save as'.
Provide setup and run instructions for common Linux editors (e.g., VS Code, JetBrains Rider) and command-line workflows (e.g., 'dotnet new console' from the terminal).
Add CLI-based examples (e.g., using Azure CLI or REST API with curl) for managing digital twins, alongside the .NET SDK examples.
Clarify that the .NET SDK and code samples are cross-platform, and explicitly mention how to run them on Linux and macOS.
Where possible, provide code snippets in additional languages (such as Python or JavaScript) that are popular in Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-style drive letters (e.g., D:\, E:\) and file paths, and by using a PowerShell script file (.ps1) as an example. There are no Linux or cross-platform examples, nor is there mention of Linux file systems, mount points, or shell commands. This may make it less accessible or relatable for Linux users.

Recommendations:

Include Linux-equivalent file path examples (e.g., /mnt/databoxdiskimport/logs) alongside Windows paths.
Provide sample error logs or scenarios using Linux file types and paths.
Mention how to access the log files on Linux systems, including typical mount points and commands.
Reference both Windows and Linux shell commands for viewing or copying log files (e.g., 'type' vs. 'cat').
Clarify that the validation tool and logs are cross-platform (if applicable), and provide any Linux-specific guidance if needed.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows environments by exclusively referencing Microsoft Azure Storage Explorer (a GUI tool primarily distributed for Windows, though available on other platforms) and portal-based verification steps, with no mention of Linux command-line tools or workflows. There are no examples or instructions for verifying data upload using Linux-native tools (such as Azure CLI, azcopy, or standard shell commands), nor are there any references to Linux or cross-platform verification methods.

Recommendations:

Add examples for verifying data upload using Azure CLI commands (e.g., az storage blob list) that work on Linux, macOS, and Windows.
Include instructions for using azcopy (a cross-platform tool) to list and verify blobs/files in the storage account.
Mention and provide examples for using standard Linux shell commands in conjunction with Azure CLI for data verification.
Explicitly state that the verification steps can be performed from any OS, and provide parity in instructions for both GUI (Storage Explorer) and CLI (Azure CLI/azcopy) approaches.
If screenshots are provided for GUI tools, consider also providing terminal output examples for CLI tools.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a subtle Windows bias by referencing BitLocker (a Windows-specific encryption tool) as the default for software-encrypted disks, and by mentioning BitLocker-encrypted disks before describing hardware-encrypted disks that are suitable for Linux. There are no explicit Linux command examples or Linux-specific workflows, and the only mention of Linux is in the context of hardware-encrypted disks being 'well suited' for Linux systems. No Linux tools or patterns are described.

Recommendations:

Provide explicit examples or references for both Windows and Linux workflows, including how to unlock and mount disks on Linux systems.
Mention Linux-compatible encryption and disk management tools (e.g., cryptsetup, udisks) alongside BitLocker.
Ensure that Linux use cases and instructions appear with equal prominence and detail as Windows equivalents.
Include a section or quickstart guide specifically for Linux users, detailing the steps and tools required for data transfer.
Clarify any limitations or differences in experience between Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing BitLocker (a Windows-specific encryption tool) as the sole example of disk encryption, without mentioning or providing alternatives for Linux environments. There are no examples or guidance for Linux users regarding disk unlocking, encryption, or usage, and no mention of cross-platform compatibility for the unlock tool.

Recommendations:

Include information about Linux compatibility for the Data Box Disk unlock tool, and provide instructions or references for Linux users.
Mention or provide examples of how Linux users can interact with encrypted disks, including any required tools or steps.
If BitLocker is the only supported encryption method, explicitly state this and clarify any limitations for non-Windows users.
Add a section or note addressing cross-platform usage, including any differences or additional steps required on Linux or macOS.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references client-side tools such as Azure PowerShell and Data Lake Tools for Visual Studio, both of which are Windows-centric. There are no examples or mentions of Linux-native tools or command-line usage (e.g., curl, wget, or Linux shell scripts) for interacting with WebHCat. The documentation does not provide parity for Linux users in terms of tooling or usage patterns.

Recommendations:

Include examples of using Linux-native tools (such as curl or wget) to interact with the WebHCat REST API.
Mention cross-platform or Linux-friendly clients (e.g., Azure CLI, Python scripts) alongside Windows tools.
Provide sample commands or scripts for common troubleshooting steps that can be run on Linux or macOS terminals.
Ensure that references to client-side tools are balanced, listing cross-platform or Linux tools before or alongside Windows-specific ones.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by listing Windows as the only supported development environment in the prerequisites, providing download links specifically for Windows versions of tools (e.g., Azure CLI, Docker CE), and referencing Visual Studio Code as the primary editor without mentioning Linux alternatives or instructions. There are no Linux-specific setup steps or examples, despite the initial note recommending Linux VMs for IoT Edge deployment. The instructions and screenshots assume a Windows client, and there is no guidance for users developing from a Linux or macOS environment.

Recommendations:

Add a parallel set of prerequisites and instructions for Linux (and optionally macOS) users, including installation commands for Azure CLI, Docker, and VS Code on those platforms.
Provide download links for cross-platform versions of required tools (e.g., Azure CLI for Linux, Docker for Linux).
Include terminal commands and screenshots from Linux environments where applicable.
Explicitly state that the development steps can be performed on Linux and provide any necessary adjustments (e.g., file paths, environment variable syntax).
If certain steps are Windows-only, clearly indicate this and provide Linux alternatives or workarounds.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes operations using the Azure Portal UI, with no mention of command-line or scripting alternatives. There are no examples or instructions for performing tasks via CLI tools such as Azure CLI, PowerShell, or Bash scripts. While this avoids explicit Windows-only tools, it implicitly prioritizes GUI workflows, which are more familiar to Windows users. There is also no mention of Linux or cross-platform command-line options, resulting in a lack of Linux parity.

Recommendations:

Add Azure CLI command examples for all key operations (e.g., creating key vaults, viewing secrets, managing access policies, recovering key vaults).
Where applicable, provide both Azure CLI and PowerShell examples, and present Azure CLI (cross-platform) examples before PowerShell.
Include notes or sections on how to perform these tasks from Linux/macOS environments, emphasizing cross-platform compatibility.
Reference relevant documentation for scripting and automation, not just portal-based workflows.
Explicitly state that all operations can be performed from any OS using the Azure CLI, and provide links to installation and usage guides.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation focuses exclusively on the .NET parser library and provides only C# code examples, which are most commonly associated with Windows development environments. There are no examples or guidance for using the parser library on Linux or with non-Windows tools, nor is there mention of cross-platform usage or alternative languages/environments.

Recommendations:

Include explicit instructions or notes on using the .NET parser library on Linux (e.g., with .NET Core/.NET 6+), including any prerequisites or differences.
Provide code examples or command-line snippets for running the parser on Linux (e.g., using dotnet CLI on Ubuntu).
Mention that the .NET parser library is cross-platform and can be used on Linux and macOS as well as Windows.
If possible, add examples in other languages supported by Azure Digital Twins (such as Python or JavaScript) to broaden platform inclusivity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page primarily provides query language examples and C#/.NET SDK usage, with no explicit examples or instructions for Linux users or non-Windows environments. The only shell-related tip references 'Cloud Shell' without clarifying platform, and the SDK example is exclusively in C#. There are no Linux/Unix shell, Python, or cross-platform SDK examples, nor is there mention of Linux-specific tools or workflows.

Recommendations:

Add examples using cross-platform SDKs, such as Python or JavaScript, to demonstrate query execution from non-Windows environments.
Clarify whether 'Cloud Shell' refers to Azure Cloud Shell (which is cross-platform) and provide equivalent command-line examples for both Windows (PowerShell) and Linux (Bash).
Include REST API call examples using curl or HTTPie, which are common on Linux and macOS.
Explicitly mention that the SDKs and APIs can be used from Linux, and provide at least one end-to-end example from a Linux environment.
Balance the order of examples so that Windows-specific tools or languages are not always presented first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by referencing 'File Explorer' as the default method for connecting to shares, without providing equivalent Linux instructions or examples. While there is a mention of using 'rsync' for copying files to NFS shares (which is Linux-friendly), the step-by-step instructions and screenshots focus on Windows tools and workflows, and there are no explicit Linux file manager or command-line mounting examples. This may leave Linux users without clear guidance for performing the same tasks.

Recommendations:

Provide explicit Linux instructions for connecting to Edge shares, such as using the 'mount' command or a Linux file manager (e.g., Nautilus, Dolphin).
Include Linux command-line examples for mounting SMB/CIFS and NFS shares (e.g., 'mount -t cifs ...' or 'mount -t nfs ...').
Add screenshots or terminal output from a Linux environment to illustrate the process for Linux users.
When referencing tools like 'File Explorer', also mention Linux equivalents (e.g., 'File Explorer (Windows) or your preferred Linux file manager').
Ensure parity in all verification steps by providing both Windows and Linux approaches side by side.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page does not provide any OS-specific command-line examples, but it does reference a PowerShell module (Az.KeyVault) for key recovery without mentioning Linux/CLI alternatives. There are no explicit Linux or cross-platform command-line instructions, and the only tool referenced is Windows-centric.

Recommendations:

Wherever PowerShell modules or commands are referenced (e.g., Undo-AzKeyVaultKeyRemoval), provide equivalent Azure CLI commands for Linux/macOS users, such as 'az keyvault key recover'.
Explicitly mention that all Azure portal steps are OS-agnostic, but for command-line operations, provide both PowerShell and Azure CLI (bash) examples.
Add a section or note clarifying how Linux users can perform key vault recovery and related operations, referencing official Azure CLI documentation.
Review all troubleshooting steps to ensure parity between Windows and Linux tooling, especially for scripting and automation scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure PowerShell and Azure CLI examples for managing resources, but consistently presents PowerShell (a Windows-centric tool) before CLI in all code tabs and output sections. There are no Linux-specific instructions, nor is there mention of running CLI commands in a native Linux shell, though Azure CLI is cross-platform. The documentation implicitly prioritizes Windows/PowerShell workflows.

Recommendations:

Alternate the order of PowerShell and CLI tabs, or present CLI examples first to avoid implicit prioritization of Windows tools.
Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide example shell prompts (e.g., bash) for Linux users.
Add a brief section or note highlighting cross-platform support and how to use Azure CLI in native Linux environments.
Where possible, include screenshots or instructions that reflect both Windows and Linux environments (e.g., terminal screenshots, shell prompts).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. While it claims support for both Windows and Linux VMs, it consistently references Windows first (e.g., 'Windows or Linux VHD', 'Prepare a generalized image from a Windows VHD'), and provides a direct link only for preparing a Windows VHD image, with no equivalent link or instructions for preparing a Linux VHD. There are no explicit Linux-specific walkthroughs or examples for VHD preparation, and the only Linux-specific guidance is deferred to an included file for connecting to a Linux VM, rather than being present in the main flow. The documentation does not provide Linux-first or Linux-equal examples for key steps such as VHD preparation.

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 both Windows and Linux, alternate the order or explicitly state that both are equally supported.
Provide Linux-specific screenshots or walkthroughs where applicable, especially for steps that may differ between OS types.
Ensure that all references to external guides (e.g., for VHD preparation) are present for both Windows and Linux.
Consider including a table or matrix summarizing differences or requirements for both Windows and Linux VM deployment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation lists Windows Server OS support before Linux, and provides more detail for Windows (two versions) than for Linux (one version). There are no Linux command-line examples or Linux-specific deployment instructions, and troubleshooting or manual installation steps for Linux are only referenced via external links. No PowerShell commands are present, but the overall pattern prioritizes Windows and omits Linux parity in examples and guidance.

Recommendations:

List supported Linux distributions and versions with the same level of detail as Windows, and consider listing Linux first or in parallel.
Provide explicit Linux deployment and management examples, such as using Azure CLI or SSH, alongside any Windows/PowerShell instructions.
Include troubleshooting steps and manual installation instructions for Linux directly in the documentation, not just as external links.
Ensure all features, such as GPU extension installation and management, are documented for both Windows and Linux with equal clarity and depth.
Add examples for common Linux distributions (e.g., Ubuntu 20.04, CentOS) if supported, or clarify support roadmap.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page for Azure Stack Edge Pro with GPU demonstrates a mild Windows bias. It references BitLocker for encryption, which is a Windows-specific technology, and does not mention Linux-native encryption alternatives. There are no explicit Linux command-line or tool examples, nor is there mention of Linux-specific management or configuration options. The documentation also omits Linux administration patterns or tools, and does not provide parity in examples or tool references for Linux users.

Recommendations:

When mentioning BitLocker for encryption, also reference Linux-compatible encryption solutions (e.g., LUKS/dm-crypt) and clarify if/how they can be used with the device.
Include Linux-specific examples or instructions for common administrative tasks, such as device configuration, diagnostics, and data transfer.
If the device supports Linux-based management or scripting (e.g., via SSH, bash scripts), provide examples alongside any Windows or PowerShell instructions.
Explicitly state the compatibility and support for Linux clients and tools (e.g., NFS, SMB mounting from Linux, REST API usage with curl or wget).
Ensure parity in documentation by providing both Windows and Linux perspectives for all relevant features and workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation shows a Windows-first bias, particularly in the 'Protect files and folders on VMs' section, where the Microsoft Azure Recovery Services (MARS) agent is listed as a backup solution only for Windows, with no equivalent Microsoft solution mentioned for Linux. Third-party solutions are listed for both Windows and Linux, but no first-party (Microsoft) Linux backup solution is referenced. There are no OS-specific command examples, but the ordering and solution coverage favor Windows.

Recommendations:

Include information about Microsoft-supported Linux backup solutions, if available, such as Azure Backup for Linux VMs.
If no first-party Linux solution exists, explicitly state this and provide guidance or best practices for Linux VM backup.
Ensure parity in documentation by listing Linux options alongside Windows options, not after.
Where possible, provide Linux-specific examples or references, especially in sections where only Windows solutions are detailed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias: in the 'Restore VM files and folders' section, the only Microsoft-native backup solution (MARS agent for Azure Backup) is listed as supporting Windows only, and is presented first in the table, while Linux support is only mentioned for third-party solutions. There are no explicit Linux-specific instructions or examples, and no parity for Linux-native backup/restore tools or guidance. The rest of the documentation avoids OS-specific instructions, but the backup/restore guidance is Windows-centric.

Recommendations:

Include Linux-native backup/restore solutions (such as Azure Backup for Linux VMs, or instructions for using rsync, tar, or other common Linux tools) where appropriate.
Provide explicit Linux examples or instructions alongside Windows ones, especially in sections discussing VM backup and restore.
If Microsoft-native solutions for Linux are unavailable, clearly state this and suggest best-practice alternatives for Linux users.
Reorder or clarify tables to avoid listing Windows-only solutions first, or group by OS for clarity.
Ensure parity in guidance for both Windows and Linux environments throughout the documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes GUI-based steps using the Azure Portal, with no mention of command-line alternatives. There are no examples or instructions for performing these operations via CLI tools (such as Azure CLI, PowerShell, or Bash), nor is there any discussion of Linux-based workflows. This implicitly prioritizes Windows/GUI users and omits Linux or cross-platform command-line users.

Recommendations:

Add instructions for performing device reset and certificate download using Azure CLI, including example commands for both Windows (PowerShell) and Linux (Bash) environments.
Explicitly mention and provide parity for command-line workflows, ensuring that Linux users can follow the same procedures without relying on the Azure Portal GUI.
Include references to relevant CLI documentation and clarify any platform-specific requirements or differences.
Where screenshots are used, consider adding CLI output examples for cross-platform clarity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing 'File Explorer' as the method to connect to Edge shares, without providing equivalent instructions or examples for Linux users (e.g., using the mount command or Linux file managers). There are no explicit Linux command-line examples for accessing shares, and the only command-line example given (rsync) is for copying files, not for mounting or browsing shares. The documentation also mentions Storage Explorer, which is available cross-platform, but does not clarify usage on Linux. While the IoT Edge runtime is stated to be Linux-based, the operational instructions assume a Windows environment.

Recommendations:

Provide Linux-specific instructions for connecting to Edge shares, such as using the 'mount' command for SMB/NFS or using Linux file managers (e.g., Nautilus, Dolphin).
Include screenshots or terminal commands for Linux environments alongside Windows examples.
Clarify that 'File Explorer' refers to Windows and suggest Linux alternatives.
Explicitly mention that Storage Explorer is available on Linux and provide installation or usage notes if needed.
Ensure that all operational steps (e.g., verifying data transfer, browsing shares) have both Windows and Linux workflows documented.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias in the certificate generation section, where instructions and context are tailored to Windows users (e.g., opening a command prompt in %USERPROFILE%), and there are no equivalent Linux or macOS instructions or examples. The rest of the guide is platform-neutral, especially when using the cross-platform MQTTX app, but the initial setup lacks Linux parity.

Recommendations:

Provide explicit Linux and macOS instructions for installing and using the step CLI, including example terminal commands for common distributions (e.g., apt, yum, brew).
Replace or supplement the '%USERPROFILE%' and 'command prompt' references with platform-agnostic or platform-specific alternatives (e.g., '~' for Linux/macOS, and mention Terminal for non-Windows users).
Add notes or callouts clarifying any platform-specific differences in file paths or environment variables.
Wherever commands are shown, provide both Windows (PowerShell/cmd) and Linux/macOS (bash) equivalents, especially for certificate generation and file path references.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references BitLocker, a Windows-specific disk encryption technology, as the mechanism for protecting data and system volumes. There are no mentions of Linux-based encryption tools or recovery processes, nor are there examples or instructions for Linux users. The documentation assumes familiarity with Windows tooling and does not provide Linux parity.

Recommendations:

Include information about how Linux users can interact with or recover encrypted disks, if supported.
Clarify whether BitLocker is the only supported encryption method, and if so, note any limitations for Linux environments.
If the device can be managed or recovered from Linux, provide equivalent Linux command-line examples and tooling references (e.g., using cryptsetup or dislocker for BitLocker volumes).
Explicitly state OS requirements or limitations for device management and recovery.
Consider mentioning or linking to documentation for cross-platform access or recovery scenarios.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exhibits mild Windows bias by referencing BitLocker (a Windows-specific encryption tool) as the example for local data encryption and linking to a VPN configuration guide that is specifically for PowerShell. There are no explicit Linux examples or tools mentioned, and Windows tools are referenced first or exclusively in relevant sections.

Recommendations:

When mentioning BitLocker for local encryption, also reference Linux-native encryption solutions (e.g., LUKS/dm-crypt) and provide links to relevant documentation.
If providing a VPN configuration guide for PowerShell, also provide equivalent instructions for configuring VPN using common Linux tools (e.g., strongSwan, OpenVPN) and link to those guides.
Wherever possible, clarify that supported protocols (e.g., SMB, NFS) are cross-platform and provide example usage or configuration steps for both Windows and Linux clients.
Review linked guides (such as system requirements and management tasks) to ensure Linux users are not left out and that parity is maintained in all operational documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation does not provide any OS-specific examples or instructions, but it implicitly assumes a Windows-centric environment by referencing Azure portal workflows and tools (such as Key Vault) that are typically accessed via the web UI or Azure CLI/PowerShell. There are no explicit Linux or cross-platform command-line examples, nor any mention of Linux-specific considerations or tools.

Recommendations:

Include explicit instructions or examples for both Windows and Linux environments, especially for steps that could be performed via command line (e.g., using Azure CLI on Linux to generate activation keys).
Mention cross-platform tools (such as Azure CLI) and provide equivalent command-line snippets for Linux users.
Clarify when steps are performed in the browser (OS-agnostic) versus when OS-specific tools or commands are required.
Add a section or note highlighting that all steps can be performed from any OS with browser access, and provide links to Azure CLI documentation for Linux/macOS users if applicable.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias in the storage specifications section, where 'Storage Spaces Direct with mirroring' (a Windows Server technology) is referenced as the RAID configuration for all models. There is no mention of Linux-based RAID or storage solutions, nor are Linux equivalents or compatibility discussed. No Linux-specific examples, tools, or patterns are provided anywhere in the document.

Recommendations:

Include information on whether Linux-based RAID or storage management solutions (such as mdadm, LVM, or ZFS) are supported or compatible with the device.
If the device is intended to be used exclusively with Windows technologies, explicitly state this to set user expectations.
If Linux is supported, provide equivalent documentation or references for Linux storage configuration and management.
Consider adding a section or note about cross-platform compatibility, especially for users who may wish to integrate the device into heterogeneous environments.
Where Windows-specific tools or technologies are referenced, offer Linux alternatives or clarify the scope of support.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation does not provide any OS-specific command-line examples, but it implicitly assumes the use of Azure Portal and Azure tools, which are cross-platform. However, there is a lack of explicit Linux or cross-platform CLI/PowerShell/Bash examples for configuring VPNs, route tables, or firewalls. There are also no references to Linux-native tools or workflows, which may leave Linux users without clear guidance.

Recommendations:

Include explicit examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) when describing steps such as updating route tables, configuring VPNs, or modifying firewall rules.
Reference Linux-native tools (such as iptables, nftables, or UFW) when discussing firewall configuration, and provide sample commands.
Clarify whether steps are to be performed in the Azure Portal, via Azure CLI, or with OS-native tools, and provide parity in instructions for both Windows and Linux environments.
Add a section or callouts for Linux users, highlighting any differences or additional steps required for common Linux distributions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing BitLocker (a Windows-specific encryption tool) as the default and only mentioned method for encryption-at-rest. There are no references to Linux-based tools or workflows, nor are there examples or instructions for users managing certificates or encryption from Linux environments. The documentation assumes a Windows-centric approach, especially in the encryption section, and does not provide parity for Linux users.

Recommendations:

Include alternative instructions or notes for Linux users, such as how to manage certificates or interact with the device from Linux-based systems.
Mention and, if possible, support Linux-native encryption solutions or clarify if BitLocker is the only supported method.
Provide example commands or workflows for certificate management using Linux tools (e.g., OpenSSL) alongside any Windows-specific instructions.
Explicitly state OS requirements or limitations if certain features (like BitLocker) are Windows-only, and suggest workarounds or alternatives for Linux environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references BitLocker and a VPN configuration guide specifically for PowerShell, both of which are Windows-centric tools and workflows. There are no Linux equivalents or examples provided for local encryption or VPN configuration, and no mention of Linux command-line or tooling options. This suggests a bias towards Windows environments and tools, with missing parity for Linux users.

Recommendations:

Include instructions for configuring local encryption using Linux-native tools (e.g., LUKS/dm-crypt) alongside BitLocker.
Provide VPN configuration steps for Linux environments, including relevant commands and supported clients.
Ensure that any PowerShell or Windows-specific guides are matched with equivalent Linux examples or references.
Explicitly state cross-platform support and provide links or documentation for both Windows and Linux wherever device management or configuration is discussed.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides detailed, step-by-step instructions for importing certificates on Windows clients, including screenshots and wizard guidance, but does not mention or provide any instructions for Linux or macOS clients. This omission suggests a Windows-centric approach, potentially leaving Linux users without guidance for equivalent tasks.

Recommendations:

Add a section with instructions for importing certificates on Linux clients, including common distributions (e.g., Ubuntu, CentOS) and relevant commands (such as using 'update-ca-certificates' or 'trust anchor').
Include guidance for macOS users, describing how to import certificates into the system keychain.
Where possible, present platform-agnostic steps first, then provide platform-specific instructions for Windows, Linux, and macOS in parallel or clearly marked subsections.
Explicitly state that the process applies to multiple operating systems and link to official documentation for certificate management on each platform.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation primarily uses Azure CLI examples, which are cross-platform, but includes a parameter example using PowerShell variable assignment ($params = ...), which is not valid in Bash or other Unix shells. There are no equivalent Linux/Bash examples for passing parameters, and the only variable assignment shown is in PowerShell syntax. This may confuse Linux or macOS users.

Recommendations:

Provide both PowerShell and Bash examples for variable assignment and parameter passing, e.g., show how to assign and use parameters in Bash: params='{ "name": "firstMsi", "location": "northeurope" }' and then use --parameters "$params".
Explicitly note that the Azure CLI commands work on Windows, Linux, and macOS, and clarify any OS-specific syntax differences.
Where variable assignment or scripting is shown, always provide both Windows (PowerShell) and Linux/macOS (Bash) variants side by side.
Review for any other subtle Windows-centric patterns (such as path separators or environment variable syntax) and ensure parity in examples.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation for Microsoft Dev Box demonstrates a Windows bias by only mentioning support for Windows 10 and Windows 11 client editions in dev box definitions, with no reference to Linux or other operating systems. There are no examples or mentions of Linux-based development environments, tools, or workflows. The documentation implicitly assumes Windows as the default and only supported platform.

Recommendations:

Explicitly state whether Linux-based dev boxes are supported or not. If not, clarify this limitation for users.
If Linux support is available or planned, include examples and instructions for creating and managing Linux dev boxes, including references to Linux images in Azure Marketplace.
Provide parity in documentation by mentioning Linux development scenarios, tools, and workflows alongside Windows equivalents.
Include guidance for mixed-platform teams, such as how to manage both Windows and Linux dev boxes within the same dev center or project.
If only Windows is supported, add a section explaining the roadmap or alternatives for Linux developers.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented around the Azure portal UI and Microsoft-specific identity solutions (Microsoft Entra, Active Directory), with references to Windows-centric network requirements and no mention of Linux tools, CLI, or cross-platform automation. There are no examples or instructions for Linux users or those preferring command-line interfaces (e.g., Azure CLI, PowerShell Core, Bash).

Recommendations:

Provide equivalent instructions using Azure CLI commands, which are cross-platform and can be run on Linux, macOS, and Windows.
Include examples for managing network connections using command-line tools (e.g., az network vnet create) in addition to the Azure portal UI.
Explicitly mention that the steps can be performed from any OS using the Azure CLI or REST API, and provide links to relevant documentation.
Clarify that Microsoft Entra and Active Directory are identity solutions that can be integrated with Linux-based environments, and provide guidance or references for Linux administrators.
Add troubleshooting or configuration notes relevant to Linux-based firewalls or network security tools, not just Microsoft Defender or Windows-centric solutions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by exclusively referencing Windows-based images (e.g., Windows 11 Enterprise, Visual Studio on Windows) and not mentioning Linux or other operating systems as options for dev box definitions. All example images and recommendations are Windows-centric, and there are no examples or guidance for using Linux images or configuring dev boxes for Linux development.

Recommendations:

Explicitly mention support for Linux images if available, or clarify if only Windows images are supported.
Provide examples of creating dev box definitions using popular Linux distributions (e.g., Ubuntu, CentOS) from the Azure Marketplace or custom images.
Include guidance or screenshots for selecting Linux images in the Azure portal, if supported.
Balance recommendations by suggesting Linux-based images for relevant development scenarios, not just Windows/Visual Studio.
If Linux is not supported, clearly state this limitation early in the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes managing Dev Box pools via the Azure portal UI, with no mention of command-line tools, scripts, or automation options. There are no examples or references to PowerShell, Windows tools, or Windows-specific patterns, but there is also a complete absence of Linux CLI, Bash, or cross-platform automation examples. The documentation implicitly assumes a graphical, portal-based workflow, which is more common in Windows-centric environments, and does not address Linux users or those preferring CLI-based management.

Recommendations:

Add equivalent instructions for managing Dev Box pools using Azure CLI (az), which is cross-platform and works on Linux, macOS, and Windows.
Provide Bash script examples for common tasks (create, update, delete pools) to support Linux users.
Explicitly mention that all portal-based actions can also be performed via CLI or REST API, and link to relevant documentation.
Ensure screenshots and UI references are supplemented with CLI command blocks for parity.
If PowerShell examples are added in the future, ensure Bash/Azure CLI equivalents are provided alongside.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing 'Windows Plan' as the default for Logic Apps and focusing on Office 365 Outlook integration for notifications, with no mention of Linux or cross-platform alternatives. There are no CLI, PowerShell, or Bash examples, but the only platform-specific reference is to Windows plans and Microsoft-centric tools, with no Linux or open-source equivalents discussed.

Recommendations:

Clarify whether the 'Windows Plan' is required for Logic Apps or if Linux-based plans are available and supported. If so, provide guidance for both.
Include examples or notes for integrating with non-Microsoft email clients (e.g., Gmail, SendGrid) for notifications, to support users on Linux or non-Windows platforms.
If possible, provide Azure CLI or REST API instructions for configuring autoshutdown, as these are cross-platform and can be used from Linux, macOS, or Windows.
Review screenshots and instructions to ensure they are not Windows-specific, or add notes/screenshots for Linux users where the experience may differ.
Explicitly state that the Azure portal and Logic Apps are accessible from any OS/browser, to reassure Linux and macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively references the Azure portal UI for managing Dev Box dev centers, with no mention of command-line tools or automation options. There are no examples or instructions for managing dev centers using cross-platform tools such as Azure CLI, and there is no mention of Linux or macOS environments. This implicitly prioritizes Windows-centric workflows, as the Azure portal experience is most commonly associated with Windows users, and omits guidance for users who prefer or require Linux-based tooling.

Recommendations:

Add equivalent instructions for managing dev centers using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
Include example commands for common tasks (create, delete, assign permissions) using Azure CLI or Azure PowerShell, and clarify which tools are available on which platforms.
Explicitly mention that the Azure portal can be accessed from any modern browser on any OS, to avoid the impression of Windows exclusivity.
Where screenshots or UI steps are shown, consider supplementing with terminal-based examples for parity.
If there are any limitations or differences in experience for Linux/macOS users, document them clearly.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page consistently references the Azure portal and REST APIs for managing personal data in Azure Digital Twins, but does not provide any platform-specific command-line examples. However, the Azure portal is a web-based tool often associated with Windows-centric workflows, and there are no examples or mentions of Linux-native tools, CLI commands, or cross-platform automation (e.g., Azure CLI, Bash scripts). This may implicitly favor Windows users or those familiar with the Azure portal, while omitting guidance for Linux users or those preferring command-line interfaces.

Recommendations:

Include examples using Azure CLI commands for identifying, exporting, and deleting personal data, as Azure CLI is cross-platform and widely used on Linux.
Provide Bash script snippets for common tasks, or reference automation via shell scripting.
Explicitly mention that the REST APIs can be accessed using tools like curl or httpie, and provide example commands.
Clarify that the Azure portal is web-based and accessible from any OS, but supplement with CLI and scripting alternatives for Linux users.
Add a section or callout highlighting cross-platform tooling and automation options.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to configure disk encryption using the Azure Portal UI, with terminology and navigation patterns that are most familiar to Windows users. There are no examples or instructions for performing these tasks using command-line tools such as Azure CLI, PowerShell, or Bash scripts, nor is there any mention of Linux-specific workflows or considerations. This may disadvantage Linux users or those who prefer automation and cross-platform scripting.

Recommendations:

Add step-by-step instructions for configuring disk encryption using Azure CLI, which is cross-platform and widely used by both Windows and Linux users.
Include PowerShell examples for users who prefer scripting, but ensure parity by providing equivalent Bash/Azure CLI commands.
Mention and link to relevant documentation for automating these tasks on Linux systems, such as using ARM templates or REST APIs.
Clarify that the Azure Portal UI is platform-agnostic, but explicitly state that all steps can be performed from any OS with a supported browser.
Provide troubleshooting or validation steps that can be performed from both Windows and Linux VMs (e.g., using OS-native commands to check disk encryption status).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation references Azure PowerShell before Azure CLI when describing deployment commands, and it mentions the Visual Studio Azure Resource Group project template as a related tool, which is primarily a Windows-centric development environment. There are no explicit Linux or cross-platform examples or tool recommendations, and the documentation does not mention Linux-specific workflows or editors.

Recommendations:

List Azure CLI before Azure PowerShell when describing deployment commands, as Azure CLI is cross-platform.
Include explicit Linux/macOS command-line examples for deploying templates, such as bash scripts or CLI usage.
Mention cross-platform editors and tools (e.g., VS Code, Git) alongside or instead of Visual Studio.
Add a section or note highlighting that all steps can be performed from Linux/macOS environments using Azure CLI and other cross-platform tools.
Provide links to documentation or tutorials that use Linux/macOS environments for ARM template deployment.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The tutorial uses generic 'command window' language and presents all command-line examples in a way that works on both Windows and Linux (e.g., 'dotnet' commands). However, it implicitly assumes a Windows-first perspective by referencing Visual Studio-specific tips and not mentioning Linux-specific editors or shell environments. There are no explicit Linux or macOS examples, nor are there any references to common Linux tools or editors. The only editor called out by name is Visual Studio, and the only tip for file management is specific to Visual Studio, which is primarily a Windows tool. There are no explicit PowerShell or Windows command prompt commands, but the lack of Linux-specific guidance or parity tips is a subtle bias.

Recommendations:

Include explicit references to Linux and macOS environments, such as mentioning common editors (e.g., VS Code, Vim, nano) and shell environments (e.g., Bash, Zsh).
Provide Linux/macOS-specific tips where appropriate, such as how to copy files or set file properties using common Linux tools.
When giving Visual Studio-specific tips, also provide equivalent instructions for cross-platform editors like VS Code or JetBrains Rider.
Clarify that all 'dotnet' CLI commands work on Linux, macOS, and Windows, and show example terminal prompts for each platform where relevant.
Add a section or callout confirming that the tutorial has been tested on Linux and macOS, and note any platform-specific caveats.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page provides only Windows-based examples for connecting an environment to a lab's VNet in Azure DevTest Labs. The sample ARM template exclusively references Windows Server images and does not mention or provide examples for Linux-based environments. There are no Linux OS options, publishers, or offers in the template, and no guidance is given for Linux users.

Recommendations:

Add Linux OS options (such as Ubuntu, CentOS, or other popular distributions) to the ARM template parameters and variables.
Include a Linux-based example in the documentation, showing how to deploy a Linux VM connected to the lab VNet.
Mention both Windows and Linux use cases in the scenario description to ensure parity.
Provide guidance or links for Linux-specific configuration or troubleshooting steps where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation presents Windows connection methods (RDP) before Linux methods (SSH/CLI) and refers to Windows-specific tools (RDP) by name, while Linux connection options are mentioned second and less prominently. There are no explicit command-line examples for either OS, but the ordering and naming favor Windows.

Recommendations:

Present Linux and Windows connection options in parallel or in a neutral order (e.g., 'For Windows VMs, use RDP; for Linux VMs, use SSH or Azure CLI').
Provide explicit examples or links for both Windows and Linux connection methods with equal prominence.
Avoid listing Windows tools or patterns before Linux equivalents unless there is a technical reason.
Consider including screenshots or instructions for both OS types side by side where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses on troubleshooting remote desktop connection issues, specifically referencing Windows-based VMs and RDP. There is no mention of Linux VMs, SSH, or Linux-specific troubleshooting scenarios, which may lead users to believe the redeploy feature is only relevant for Windows VMs.

Recommendations:

Include examples or scenarios for Linux VMs, such as troubleshooting SSH connectivity issues.
Clarify that the redeploy feature applies to both Windows and Linux VMs, if applicable.
Mention Linux-specific remote access methods (e.g., SSH) alongside RDP.
Add a note or section addressing common Linux VM redeployment use cases.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias by presenting the Windows VM creation example before the Linux example, and by referencing Windows-specific images and artifacts first. While both Windows and Linux scenarios are covered, Windows is consistently mentioned or exemplified before Linux, and Windows tools (such as Remote Desktop) are referenced alongside SSH, sometimes with more prominence.

Recommendations:

Alternate the order of examples so that Linux-based VM creation is shown before or alongside Windows-based examples.
Ensure parity in artifact examples by including both Windows and Linux artifacts in sample outputs and JSON snippets.
When referencing connection methods, present SSH (Linux) and RDP (Windows) in parallel, giving neither undue prominence.
Where possible, use neutral or cross-platform examples (e.g., generic images, admin credentials) unless a specific OS is being demonstrated.
Explicitly mention that all commands and procedures apply equally to both Windows and Linux VMs, and provide links to both Linux and Windows connection guides.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing command-line testing instructions only for Windows (using 'command prompt' and 'nslookup'), without mentioning or illustrating equivalent steps for Linux or macOS users. There are no Linux shell or cross-platform examples, and the only non-portal automation reference is to Azure PowerShell, with no mention of Azure CLI or other cross-platform tools.

Recommendations:

Include Linux/macOS instructions for testing DNS delegation, such as using 'dig' or 'nslookup' from a Unix shell.
When referencing command-line tools, specify both Windows (Command Prompt/PowerShell) and Linux/macOS equivalents.
Mention and provide examples using Azure CLI for subdomain delegation, as it is cross-platform.
Avoid phrases like 'Open a command prompt' without also mentioning 'Open a terminal' for Linux/macOS users.
Add screenshots or code snippets that reflect both Windows and Linux environments where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias toward Windows by exclusively using Windows as the operating system in all examples for App Service plans and web apps. There are no examples or guidance for Linux-based App Service plans or web apps, nor is there any mention of Linux runtimes or deployment patterns. This may lead Linux users to believe that the process is Windows-specific or that Linux is not supported.

Recommendations:

Provide parallel examples using Linux as the operating system in the App Service plan and web app creation steps.
Include at least one Linux runtime (such as Node.js, Python, or .NET Core on Linux) in the web app configuration tables.
Add a note clarifying that both Windows and Linux App Service plans are supported, and link to relevant documentation for Linux deployments.
Ensure that instructions and screenshots (if any) are not Windows-specific and are applicable to both platforms.
Explicitly mention any differences or considerations when using Linux-based App Service plans with Traffic Manager and Azure DNS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing only a Windows Server 2019 Datacenter example when adding a VM to the lab, without mentioning or illustrating how to create a Linux-based VM. There are no Linux-specific instructions, screenshots, or references to Linux images, tools, or patterns. The documentation implicitly assumes Windows as the default, which may mislead or disadvantage users seeking to deploy Linux environments.

Recommendations:

Include parallel instructions and screenshots for creating a Linux VM (e.g., Ubuntu, CentOS) in the 'Add a VM to the lab' section.
Explicitly mention that both Windows and Linux images are supported, and provide guidance on selecting a Linux base image.
Add notes or tips about Linux-specific configuration options (e.g., SSH key authentication, default usernames, artifact installation differences).
Where possible, use neutral language and examples that apply to both Windows and Linux, or provide side-by-side examples.
Reference documentation or quickstarts for deploying Linux VMs in DevTest Labs.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation focuses exclusively on .NET Core and ASP.NET Core examples, which are traditionally associated with Windows environments, and does not provide any Linux-specific examples or mention Linux-based tools or patterns. There are no references to Linux shell scripts, Bash, or Linux VM configurations, nor are there any screenshots or instructions that address Linux users. The documentation implicitly assumes a Windows-centric workflow by defaulting to technologies and templates commonly used in Windows environments.

Recommendations:

Include parallel examples for Linux-based web apps (e.g., Node.js, Python, or Java on Linux App Service) alongside .NET Core examples.
Demonstrate how to configure and deploy to Linux VMs or Linux-based environments in DevTest Labs.
Add sample pipeline YAML or task configurations that use Bash scripts or Linux shell commands.
Explicitly mention that DevTest Labs and Azure Pipelines support both Windows and Linux environments, and provide links or references to Linux-specific documentation.
Show screenshots or UI flows that include Linux options (e.g., selecting Ubuntu or other Linux images in DevTest Labs).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently uses the nslookup tool for DNS validation, with screenshots and references that appear to be from Windows Command Prompt. There are no examples or screenshots for Linux or macOS users, nor are alternative tools (like dig) mentioned. This presents a subtle Windows-first and Windows-only bias, as it assumes the reader is using a Windows environment for DNS troubleshooting.

Recommendations:

Include Linux/macOS equivalents for DNS validation, such as using the dig command (e.g., dig <domain>) alongside nslookup.
Provide screenshots or terminal output examples from Linux/macOS environments in addition to Windows Command Prompt.
Explicitly mention that nslookup is available on multiple platforms, but also suggest dig as a common alternative on Unix-like systems.
Wherever command-line validation is shown, provide both Windows and Linux/macOS command syntax and expected output.
Consider a short section or callout box summarizing DNS troubleshooting commands for different operating systems.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides only .NET (C#) code samples and instructions, which are most commonly associated with Windows development environments. There are no examples or setup instructions for Linux or cross-platform development environments, and all package management and project setup guidance is tailored to Visual Studio or the dotnet CLI, both of which are Windows-centric or at least Windows-first in their documentation and usage patterns. No Linux-specific tools, shell commands, or environment setup instructions are provided.

Recommendations:

Add equivalent code samples for other supported languages (e.g., Python, Java, JavaScript) and show how to authenticate using Azure.Identity in those languages.
Include instructions for setting up projects and installing dependencies using cross-platform tools (e.g., pip for Python, npm for JavaScript, Maven/Gradle for Java).
Provide examples of environment variable configuration and credential management for Linux/macOS shells (e.g., bash, zsh), not just Windows/Visual Studio.
Explicitly mention that the authentication approaches work on Linux and macOS, and provide any necessary platform-specific notes.
Where referencing command-line tools, include both Windows (dotnet CLI, PowerShell) and Linux/macOS (bash, sh) equivalents.

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, and no explicit Linux/bash-specific instructions or examples are provided. The CLI example is cross-platform, but the inclusion of PowerShell (which is traditionally associated with Windows) without a corresponding bash or Linux shell example may suggest a slight Windows bias. There are no references to Windows-only tools, but the documentation does not explicitly address Linux users or provide Linux-specific guidance.

Recommendations:

Clarify that the Azure CLI example works on Linux, macOS, and Windows, and consider labeling it as 'Bash/CLI' or 'Linux/macOS/Windows CLI' to highlight cross-platform compatibility.
If possible, provide a bash-specific example or note that the CLI commands can be run in a Linux shell.
Consider adding a note for Linux users about installing and using the Azure CLI, or linking to relevant documentation.
If PowerShell is included, consider also including bash or shell script examples to ensure parity for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on creating and managing Windows virtual machines, with no mention of Linux VM options or examples. All VM-related steps and outputs are Windows-specific, and there is no guidance for users who may want to deploy Linux VMs. While both Azure CLI and PowerShell are provided for verification, the overall workflow and resource creation are Windows-centric.

Recommendations:

Include parallel instructions and Terraform code samples for deploying Linux virtual machines alongside Windows VMs.
Update the checklist and summary to mention both Windows and Linux VM creation, or provide an explicit choice.
Add example outputs and troubleshooting notes relevant to Linux VMs.
Ensure that any referenced scripts, variables, or admin credential outputs are equally applicable to Linux (e.g., SSH keys instead of only passwords).
Consider providing a toggle or tabs for Windows and Linux VM scenarios throughout the guide.

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 section is included immediately after the CLI section, and both use Windows-centric scripting syntax. There are no explicit Linux shell (bash) examples, and the PowerShell tab is presented as an alternative rather than providing parity with Linux-native tools or workflows. The use of PowerShell and CLI together may implicitly favor Windows users, as PowerShell is primarily a Windows tool, though now cross-platform.

Recommendations:

Add explicit Bash/Linux shell examples for all verification steps, especially for users running Terraform and Azure CLI on Linux or macOS.
Clarify that Azure CLI commands can be run on any platform, and provide example shell commands for Linux/macOS (e.g., using export instead of $var=).
If PowerShell is included, ensure that Bash examples are given equal prominence and are presented before or alongside PowerShell examples.
Mention that PowerShell Core is cross-platform, but provide clear guidance for Linux/macOS users who may not use PowerShell.
Consider adding a table or tabbed interface that includes Bash, PowerShell, and Azure CLI examples for each step.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a bias towards Windows by exclusively referencing the Azure Portal (a web GUI) and not providing any command-line examples. There are no examples using cross-platform tools such as Azure CLI, Azure PowerShell, or REST APIs, which are commonly used on Linux and macOS. The documentation implicitly assumes a GUI/Windows-centric workflow, omitting Linux-friendly automation or scripting options.

Recommendations:

Add step-by-step instructions using Azure CLI for all key management and configuration tasks, as Azure CLI is cross-platform and widely used on Linux.
Include PowerShell examples as an alternative, but ensure CLI examples are presented first or alongside PowerShell to avoid Windows-first bias.
Provide REST API examples for advanced users who may want to automate these tasks from any OS.
Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and provide links to relevant CLI or API documentation.
Where screenshots are used, consider including terminal output or code snippets to complement GUI steps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation consistently presents Azure PowerShell examples before Azure CLI examples, and all PowerShell code is shown using Windows PowerShell syntax. There are no explicit Linux shell or Bash examples, and the PowerShell approach is highlighted as a primary method throughout. This ordering and emphasis may give the impression that Windows or PowerShell is the preferred or default environment for managing Azure DNS, which can be unwelcoming or confusing for Linux users.

Recommendations:

Present Azure CLI examples before or alongside PowerShell examples, 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 Bash shell context where appropriate.
Add example command lines using Bash or other common Linux shells, especially for tasks like scripting or automation.
Clarify that PowerShell is available cross-platform, but provide guidance for Linux users who may not have PowerShell installed by default.
Review screenshots and UI instructions to ensure they are not Windows-specific where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section, which subtly prioritizes Windows-centric tooling. There are no Linux-specific examples or explicit mention of Linux tools, and the only command-line examples referenced are PowerShell and CLI, with PowerShell listed first.

Recommendations:

Present Azure CLI before Azure PowerShell in example links and instructions, as CLI is cross-platform and more familiar to Linux users.
Include explicit Linux usage examples or screenshots where relevant, such as showing CLI commands being run in a Bash shell.
Mention that both Azure CLI and PowerShell are available on multiple platforms, and provide parity in documentation for both.
If possible, add a section or note for Linux administrators, highlighting any differences or tips for using the autoregistration feature from Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

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 or PowerShell). While this avoids explicit Windows-only tooling, it implicitly favors Windows users by omitting Linux-friendly CLI workflows, which are common in Linux environments and automation. There is also no mention of how to perform these tasks via command line, which is often preferred by Linux users.

Recommendations:

Add Azure CLI examples for all major steps (e.g., creating the resource group, deploying the AKS cluster, cleaning up resources).
If PowerShell examples are added, ensure Azure CLI (cross-platform) examples are provided first or alongside.
Explicitly mention that the Azure CLI can be used on Windows, Linux, and macOS, and provide installation links.
Include a section or links for automating these tasks via scripts for both Linux and Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section and referencing PowerShell as a primary tool. While the main content is platform-neutral and does mention Azure CLI, there are no Linux- or Bash-specific examples or explicit parity in tool recommendations. The documentation avoids exclusive mention of Windows tools, but the ordering and emphasis subtly prioritize Windows/PowerShell users.

Recommendations:

Ensure that Azure CLI (which is cross-platform) is mentioned before or alongside Azure PowerShell in all tool lists and 'Next steps' sections.
Explicitly state that Azure CLI commands can be run on Linux, macOS, and Windows to reinforce cross-platform support.
Where possible, provide example commands for both Azure PowerShell and Azure CLI (or Bash scripts) to demonstrate parity.
Include references or links to Linux-specific guidance or troubleshooting if relevant.
Review all documentation for consistent ordering and equal emphasis of cross-platform tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page references Azure PowerShell before Azure CLI in the 'Next steps' section, which may suggest a Windows-first or PowerShell-heavy approach. While both PowerShell and CLI are mentioned, the ordering may subtly prioritize Windows tooling. There are no explicit Linux or cross-platform examples, and no mention of Linux-specific tools or workflows.

Recommendations:

Present Azure CLI before or alongside Azure PowerShell in all lists and examples, as CLI is cross-platform and more familiar to Linux users.
Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS to reinforce cross-platform parity.
Add Linux-specific or cross-platform command examples where appropriate, or clarify that the instructions apply equally to Linux environments.
Avoid ordering that consistently places Windows/PowerShell tools before Linux/CLI equivalents.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page does not provide any OS-specific command-line examples, but in the 'Next steps' section, it only references Azure PowerShell and the Azure portal for creating a DNS Private Resolver. There is no mention of Azure CLI (which is cross-platform and commonly used on Linux/macOS), nor are there any Linux-specific tools or workflows discussed. This subtly prioritizes Windows-centric tools and patterns, and omits Linux parity in guidance.

Recommendations:

Add Azure CLI instructions and links alongside Azure PowerShell and portal guidance, as Azure CLI is cross-platform and widely used on Linux.
Wherever command-line examples are referenced, ensure both PowerShell and CLI (bash) examples are provided, or at least link to both.
Explicitly mention that the Azure DNS Private Resolver can be managed from Linux, macOS, and Windows environments, and provide links to relevant documentation for each.
If referencing scripts or automation, include bash/shell script examples in addition to PowerShell.
Review screenshots and UI guidance to ensure they are not Windows-specific, or provide equivalent Linux/macOS context where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively uses Windows Server for the virtual machine example, including instructions for installing IIS via the Windows GUI and connecting via RDP. There are no examples or instructions for creating or configuring a Linux-based VM, nor for installing a web server (such as Apache or Nginx) on Linux. All screenshots and step-by-step instructions assume a Windows environment, and no Linux alternatives are mentioned.

Recommendations:

Add parallel instructions for creating a Linux virtual machine (e.g., Ubuntu or CentOS) in Azure.
Provide steps for installing a web server (such as Apache or Nginx) on the Linux VM, including relevant command-line examples.
Include screenshots or terminal output relevant to Linux environments.
Mention both RDP (for Windows) and SSH (for Linux) as connection methods, with instructions for each.
Where possible, use neutral language (e.g., 'web server VM') and clarify that either Windows or Linux can be used.
Consider providing a table or toggle for users to select their preferred OS (Windows or Linux) for the tutorial steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by only providing instructions and examples using the Azure Portal (a web UI) and the nslookup command from a generic 'command prompt' without specifying or illustrating Linux or cross-platform alternatives. The testing step assumes the use of nslookup from a Windows command prompt, with no mention of Linux shells, tools like dig, or cross-platform command syntax. There are no CLI (az cli, PowerShell, or bash) examples, and no explicit Linux guidance is provided.

Recommendations:

Include explicit instructions for verifying DNS records from Linux/macOS terminals, such as using dig (e.g., `dig test.contoso.com`) in addition to nslookup.
Clarify that nslookup is available on both Windows and Linux, or provide installation instructions for Linux users if needed.
Where 'command prompt' is mentioned, specify that these steps can be performed from Windows Command Prompt, PowerShell, or Linux/macOS terminal.
Consider adding Azure CLI (az cli) examples for creating and managing DNS records, which are cross-platform.
Add a note or section for Linux/macOS users to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias towards Windows environments by focusing exclusively on GUI tools (Postman desktop app) and Python-based utilities (sdutil) without providing explicit Linux command-line examples or mentioning Linux-native tools. The instructions assume the use of desktop applications and do not address Linux-specific installation or usage considerations. There is no mention of Linux package managers, shell commands, or alternative workflows that are common in Linux environments.

Recommendations:

Provide explicit Linux command-line examples for each step, such as using curl or wget for API calls and file uploads.
Include instructions for installing and running Postman and sdutil on Linux, including any dependencies or package manager commands (e.g., apt, yum, snap).
Mention and demonstrate how to use native Linux tools (e.g., curl, jq) as alternatives to Postman for API interactions.
Clarify that sdutil and Postman are cross-platform, and provide troubleshooting tips for Linux users (e.g., permissions, environment variables).
Add a section or callouts for Linux users, highlighting any differences or additional steps required on Linux systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides deployment instructions for Azure Kubernetes Service (AKS) and Windows, but does not mention or provide instructions for deploying the GCZ service on Linux (outside of AKS). The 'Windows' deployment option is presented as the only non-AKS alternative, with no equivalent Linux instructions for development or testing environments. This creates a Windows-first impression and omits Linux users who may wish to deploy locally or outside Kubernetes.

Recommendations:

Add a section or pivot for deploying the GCZ service on Linux (e.g., Ubuntu), including step-by-step instructions or a link to a Linux deployment guide.
Wherever a 'Windows' deployment is mentioned, also mention 'Linux' as a supported platform if possible, or clarify platform limitations.
If there are scripts or tools provided for Windows (e.g., PowerShell), provide equivalent Bash or shell scripts for Linux users.
Explicitly state platform support and any limitations for each deployment option to help users on all major operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows tools (Postman desktop app) and providing screenshots and instructions that assume a Windows environment. There are no explicit Linux-specific instructions, examples, or screenshots, and setup steps for tools like Postman and sdutil do not address Linux installation or usage. The documentation does not mention or show parity for Linux users, such as using Postman on Linux, or provide Linux command-line alternatives or troubleshooting.

Recommendations:

Include explicit instructions and screenshots for installing and using Postman on Linux, or clarify that Postman is cross-platform.
Provide Linux-specific setup notes for sdutil, including installation steps and any OS-specific dependencies.
When referencing tools, avoid language that implies Windows is the default (e.g., 'Download and install the Postman desktop app' could be 'Download and install the Postman desktop app for your OS').
Add troubleshooting tips or notes for common Linux issues (e.g., permissions, Python environment setup for sdutil).
Where screenshots are shown, consider including at least one from a Linux environment or clarify that the UI is the same across platforms.
Explicitly state that all command-line examples (bash scripts, sdutil commands) are valid on Linux and provide any necessary adjustments for Windows users if needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples, but consistently lists PowerShell examples immediately after CLI, and in some sections, PowerShell is given equal or more detailed coverage. There are no explicit Linux-specific examples or mentions of Linux-native tools (e.g., curl, jq) outside of the CLI section, and the PowerShell examples are more verbose and detailed. The use of Azure Cloud Shell is mentioned, but it defaults to both Bash and PowerShell without highlighting Linux workflows. There is no explicit bias in tool availability, but the structure and example order subtly favor Windows/PowerShell users.

Recommendations:

Add explicit Linux/Bash-native examples (e.g., using curl, jq, or bash scripting) outside of just Azure CLI.
In sections where both PowerShell and CLI are shown, alternate the order or clarify that CLI is cross-platform and preferred for Linux/Mac users.
Highlight that Azure CLI commands are fully supported on Linux and Mac, and provide troubleshooting tips for common Linux environments.
Where Cloud Shell is mentioned, clarify that Bash is the default for Linux users and show Bash-specific workflows.
Consider adding a 'Linux' or 'macOS' tab in code examples to show parity and avoid the impression of Windows/PowerShell primacy.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes GUI-based steps using the Azure Portal and does not provide any command-line examples for enabling diagnostic settings or downloading logs. There are no references to Windows-specific tools (such as PowerShell), but the instructions implicitly assume use of the Azure Portal, which is most commonly accessed from Windows environments. There are no CLI (az), PowerShell, or Linux shell examples, nor is there mention of how to perform these tasks from Linux or cross-platform environments.

Recommendations:

Add equivalent command-line instructions using Azure CLI (az), which is cross-platform and works on Linux, macOS, and Windows.
Include examples for downloading logs using az storage blob commands or other cross-platform tools (e.g., curl, wget, or Azure Storage Explorer).
Explicitly mention that all steps can be performed from any OS, and provide links to CLI documentation for users who prefer or require non-GUI workflows.
If PowerShell examples are added, ensure that Bash/Linux shell equivalents are also provided.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation consistently instructs users to run commands in 'Azure Cloud Shell', which by default is a Bash environment but is tightly integrated with Azure and often associated with Windows-centric workflows. There are no explicit PowerShell or Windows command examples, but the documentation does not mention or provide guidance for running these commands in a generic Linux/macOS terminal or on-premises shell. The screenshots and instructions focus exclusively on Azure/Microsoft tools and environments, with no mention of Linux-native authentication or CLI workflows outside of Azure's ecosystem.

Recommendations:

Explicitly state that the curl commands can be run from any Bash-compatible shell on Linux, macOS, or Windows (with WSL or Git Bash), not just Azure Cloud Shell.
Provide examples or notes for running the commands in native Linux/macOS terminals, including any prerequisites (e.g., curl installation, environment variable setup).
If authentication steps differ for Linux/macOS (e.g., using Azure CLI on Linux), include those instructions or references.
Avoid implying that Azure Cloud Shell is the only or primary environment for these operations; mention alternatives such as local terminals.
If screenshots are necessary, consider including examples from both Windows and Linux environments to demonstrate cross-platform compatibility.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation introduces the tutorial as using PowerShell to work with Reservoir DDMS APIs, suggesting a Windows-first approach. However, all provided command-line examples use Bash and Docker, which are cross-platform, but the initial framing may mislead Linux or Mac users into thinking the tutorial is Windows-centric.

Recommendations:

Remove or generalize the reference to PowerShell in the introduction. Instead, state that the tutorial uses cross-platform command-line tools.
Explicitly mention that the Bash and Docker commands work on Linux, macOS, and Windows (with WSL or compatible terminals).
If there are any platform-specific steps (such as Docker Desktop installation), provide links or notes for both Windows and Linux/macOS users.
Consider providing PowerShell equivalents only if there are Windows-specific nuances, otherwise keep examples in Bash for maximum portability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively references Visual Studio Code and Azure portal workflows without specifying or providing parity for Linux environments. All instructions assume the use of VS Code and Azure tools, which are cross-platform, but there is no mention of Linux-specific considerations, CLI alternatives, or examples for Linux users. There are no PowerShell-specific commands, but the lack of explicit Linux examples or terminal/CLI instructions constitutes a subtle Windows-first bias.

Recommendations:

Include explicit instructions or notes for Linux users, such as verifying that all steps work identically on Linux.
Provide Azure CLI commands as alternatives to portal-based steps, especially for creating and deploying Azure Functions.
Mention any Linux-specific prerequisites or troubleshooting tips (e.g., Node.js installation, VS Code extensions).
Add screenshots or terminal examples from Linux environments where applicable.
Clarify that the process is cross-platform and highlight any differences, if any, for Linux or macOS users.

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 (a web-based GUI) and Visual Studio Code for setup and deployment, without providing any command-line examples (such as Azure CLI or PowerShell) or Linux-specific instructions. There are no explicit Linux or cross-platform terminal commands, and all configuration steps are described via GUI navigation, which is more familiar to Windows users. There is also an assumption that users will use the clipboard and GUI-based workflows, which are more common in Windows environments.

Recommendations:

Add equivalent instructions using Azure CLI for all major steps (function creation, configuration, deployment, event subscription), including sample commands.
Provide examples for deploying and configuring Azure Functions from Linux/macOS terminals.
Include notes or links for users who prefer command-line or automation approaches, highlighting cross-platform compatibility.
Clarify that Visual Studio Code and Azure CLI are available on Linux and macOS, and provide any necessary setup links.
Offer alternative instructions for copying connection strings and managing secrets using environment variables or CLI tools, not just GUI/clipboard methods.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by referencing Windows-specific resources first (e.g., linking to configuring managed identities on a Windows VM) and omitting explicit Linux or cross-platform examples. There are no PowerShell-heavy sections or exclusive use of Windows tools, but the absence of Linux/Unix-specific instructions or examples may hinder parity for non-Windows users.

Recommendations:

When referencing enabling managed identities, provide links and instructions for both Windows and Linux VMs (e.g., link to both Windows and Linux VM managed identity guides).
Include explicit examples or notes for Linux environments, especially in sections discussing enabling managed identities or configuring environment variables.
If providing code snippets that set environment variables (e.g., using Environment.SetEnvironmentVariable in C#), add equivalent shell commands for Linux/macOS (e.g., export AZURE_CLIENT_ID=...).
Ensure that all Azure portal instructions are clearly marked as cross-platform, and where CLI or scripting is involved, provide both PowerShell and Bash/Azure CLI equivalents.
Review all links and references to ensure Linux and cross-platform documentation is equally discoverable and prioritized alongside Windows resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation primarily describes deployment using the Azure Portal and references PowerShell in the context of alternative deployment methods, but does not provide explicit examples or instructions for Linux users (e.g., Azure CLI or Bash). The only alternative method directly linked is PowerShell, and there are no Linux-specific tools or command-line examples provided.

Recommendations:

Add explicit Azure CLI (cross-platform) deployment instructions alongside or before PowerShell references.
Provide Bash shell command examples for uploading files to Blob storage (e.g., using az storage blob upload or curl), not just portal-based instructions.
When listing deployment methods, mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
Include notes or links to Linux/macOS-specific guidance where relevant, especially for command-line operations.
Ensure that all referenced documentation (such as 'Deploy templates') includes parity between PowerShell and CLI/Bash examples.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is primarily focused on Linux (Ubuntu) scripting and usage, with all code examples and best practices centered on Bash and Linux tools. However, there is a subtle Windows bias in the way that Windows-based tools (Azure PowerShell, .NET SDK) are listed as primary methods for applying script actions, and in the troubleshooting section, where the root cause of common errors is attributed to authoring scripts on Windows. The documentation does not provide Linux CLI (az CLI) examples for managing script actions, and Windows-centric tools are often mentioned before Linux equivalents.

Recommendations:

Add examples and instructions for using the Azure CLI (az CLI), which is cross-platform and preferred by many Linux users, for applying script actions.
When listing methods for applying script actions, mention cross-platform tools (like Azure CLI) before or alongside Windows-specific tools (PowerShell, .NET SDK).
In troubleshooting sections, provide guidance for both Windows and Linux users, such as how to convert line endings on both platforms.
Where possible, avoid assuming scripts are authored on Windows; instead, provide neutral language that addresses both Windows and Linux development environments.
Include links to Linux-native tools and documentation for managing HDInsight clusters, not just PowerShell or .NET SDK references.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias primarily in the application development and event processing sections. While the Azure CLI and curl commands are cross-platform, the only example for building a listener application is for C# using Visual Studio on Windows, with explicit instructions to use Visual Studio 2019 or later. There are no equivalent instructions or examples for Linux or macOS users, nor are alternative languages or tools highlighted for non-Windows environments.

Recommendations:

Add explicit instructions and examples for building and running the listener application on Linux and macOS, including how to use .NET Core/SDK and cross-platform editors like VS Code.
Provide alternative sample applications in additional languages (e.g., Python, Node.js) that are commonly used on Linux.
Clarify that Visual Studio is not required and that .NET projects can be built and run using the dotnet CLI on any OS.
Include links to cross-platform setup guides for .NET and other supported languages.
Where possible, mention Linux and macOS as supported environments in the prerequisites and throughout the tutorial.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to enable managed identity for an Azure Event Grid partner topic using the Azure portal, a web-based interface accessible from any OS. However, it omits any command-line examples (such as Azure CLI or Azure PowerShell), and does not mention Linux-specific workflows or tools. While not overtly Windows-specific, the lack of CLI examples (which are often more relevant to Linux users) and the focus on graphical interface workflows can be considered a subtle 'Windows-first' or 'GUI-first' bias.

Recommendations:

Add Azure CLI examples for assigning system-assigned and user-assigned managed identities, as Azure CLI is cross-platform and widely used on Linux.
If relevant, provide Azure PowerShell examples as well, but ensure CLI examples are presented first or alongside PowerShell.
Explicitly mention that the Azure portal is accessible from any OS to clarify cross-platform compatibility.
Include a section or links for automating these tasks via scripts, which is common in Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exclusively uses PowerShell-based runbooks and AzureRM modules, which are Windows-centric. There are no examples or guidance for using Python or other cross-platform scripting languages in Azure Automation, nor any mention of Linux-specific considerations or alternatives. All code snippets and automation steps assume a Windows/PowerShell environment.

Recommendations:

Provide equivalent examples using Python runbooks, which are supported in Azure Automation and are cross-platform.
Include notes or sections on how to adapt the automation for Linux VMs, such as using Azure CLI or Bash scripts.
Mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical) and link to relevant documentation for non-Windows users.
Add guidance or links for users who manage Linux VMs, including tagging and automation best practices for Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes how to enable managed identity for an Event Grid namespace using the Azure portal, which is a graphical interface commonly associated with Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux or cross-platform tooling. This approach implicitly favors Windows users and those comfortable with GUI workflows, while omitting guidance for Linux users or those who prefer automation and scripting.

Recommendations:

Add step-by-step instructions for enabling managed identity using the Azure CLI, which is cross-platform and widely used on Linux.
Include equivalent examples using Azure PowerShell for parity, but ensure CLI examples are presented first or alongside PowerShell.
Explicitly mention that the Azure portal is accessible from any OS, but also provide non-GUI alternatives for users on Linux or those automating deployments.
Where possible, provide Bash script snippets for common tasks to support Linux users.
Review all images and instructions to ensure they are not specific to Windows-only UI conventions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is largely platform-neutral, focusing on event schemas and JSON payloads. However, there is a subtle Windows bias in the example event payloads: the 'useragent' field in the image pushed event contains 'os/windows' and 'Docker-Client/18.03.0-ce (windows)', which may suggest Windows as the default or primary environment. No explicit Linux or cross-platform user agents are shown, and no Linux-specific examples or tools are mentioned. There are no PowerShell or Windows command-line examples, but the only concrete client environment shown is Windows.

Recommendations:

Provide example event payloads that include both Windows and Linux user agents in the 'useragent' field to illustrate cross-platform usage.
Explicitly mention that Azure Container Registry and Event Grid are cross-platform and can be used from Linux, macOS, and Windows.
If referencing client tools (e.g., Docker), show example user agents or commands from both Windows and Linux environments.
Ensure that any future command-line or code examples are provided for both Windows (PowerShell/CMD) and Linux (Bash) where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation presents Azure PowerShell instructions before Azure CLI, which may suggest a Windows-first approach. PowerShell is typically associated with Windows environments, while Azure CLI is cross-platform and more commonly used on Linux and macOS. No Linux-specific examples or terminal screenshots are provided, and there is no mention of Bash or shell scripting, which are common on Linux.

Recommendations:

Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more inclusive for Linux users.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and consider including a Bash example or terminal screenshot.
Add a note or section highlighting Linux/macOS compatibility and any prerequisites for those platforms.
If possible, provide troubleshooting tips or environment setup guidance for Linux users.

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 preference for Windows tooling. There is no explicit mention of Linux or Bash examples, and the only command-line sample linked is for Azure CLI, which is cross-platform but is listed after PowerShell.

Recommendations:

List Azure CLI (cross-platform) samples before PowerShell samples to avoid implying a Windows-first approach.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
Add Bash or shell script examples where appropriate to ensure Linux users are equally supported.
Include a note or section highlighting Linux/macOS compatibility and usage patterns.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates subtle Windows bias by referencing Azure portal workflows and domain names with a strong Windows association (e.g., *.servicebus.windows.net) and by omitting any Linux-specific or cross-platform command-line examples. There are no CLI or shell commands (such as Azure CLI or Bash), and all instructions assume use of the Azure portal, which is more familiar to Windows users. There are no references to Linux tools, nor are there any examples for Linux environments.

Recommendations:

Include Azure CLI and Bash command-line examples for creating namespaces, event hubs, and retrieving connection strings, alongside or before portal instructions.
Mention Linux and macOS compatibility explicitly, and provide sample commands for those environments.
When referencing domain names, clarify that the instructions apply equally to Linux and macOS users.
Add verification steps using cross-platform tools (e.g., kafkacat, curl, or Azure CLI) instead of relying solely on the Azure portal.
Ensure screenshots and walkthroughs are not portal-exclusive; include terminal-based alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing Windows-specific resources (such as enabling managed identities on Azure VMs via a Windows-focused link) and providing only .NET/C# (commonly associated with Windows development) sample code. There are no explicit Linux or cross-platform command-line examples, nor are there instructions for enabling managed identities on Linux VMs or using Linux-native tools. The primary sample application is an ASP.NET Core web app, and while Java and Kafka samples are mentioned, they are only linked and not described in the main flow.

Recommendations:

Include explicit instructions and links for enabling managed identities on Linux VMs, not just Windows VMs.
Provide sample code and walkthroughs for Linux-based environments, such as using Python or Java on Linux VMs or containers.
Add command-line examples using Azure CLI (which is cross-platform) for key steps like enabling managed identities and assigning roles.
Ensure that references to sample applications and code are balanced between Windows and Linux (e.g., include both .NET and Python/Java samples in the main text, not just in links).
Mention Linux and cross-platform scenarios early in the documentation to signal parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates mild Windows bias by referencing Windows-centric tools and patterns first. For example, the use of 'nslookup' is illustrated with a Windows-specific namespace ('ns.servicebus.windows.net'), and the documentation refers to checking properties in the portal, Azure CLI, or PowerShell, listing PowerShell explicitly but not mentioning Linux shells or tools. There are no explicit Linux or cross-platform command examples, and no mention of Linux-specific tools or instructions.

Recommendations:

Provide command examples for both Windows (PowerShell/CMD) and Linux (Bash) environments when referencing tools like 'nslookup' or Azure CLI.
When mentioning Azure CLI or scripting, clarify that it is cross-platform and provide example commands for both Windows and Linux shells.
Avoid using Windows-specific namespaces or examples exclusively; include generic or Linux-relevant examples as well.
Explicitly mention Linux and macOS compatibility where applicable, especially for management tools and command-line operations.
Consider adding a section or callout noting that all features and management operations are supported on Linux, and provide links to Linux-specific documentation if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by referencing .NET and C# code exclusively for all code examples, and by mentioning Windows-centric tools (such as DnsClient.NET) without Linux or cross-platform alternatives. There are no PowerShell-specific examples, but the lack of Linux or open-source tool examples (e.g., dig, nslookup, or Linux SDKs) and the absence of code samples in languages commonly used on Linux (such as Python or Java) indicate a lack of Linux parity.

Recommendations:

Provide equivalent code samples in cross-platform languages such as Python, Java, or Node.js, especially for event processing and DNS queries.
When referencing DNS client libraries, mention and provide examples for Linux-friendly tools (e.g., dig, nslookup) and libraries (e.g., dnspython for Python, or Java DNS libraries).
Explicitly state that the guidance and code samples are cross-platform where applicable, and note any platform-specific limitations.
Include instructions or references for setting up and running the provided samples on Linux environments.
Balance the documentation by alternating or combining Windows and Linux examples, ensuring both audiences are equally served.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is focused exclusively on .NET Framework APIs and exception handling, which are primarily associated with Windows environments. There are no examples, notes, or references to Linux-specific usage, cross-platform .NET Core/.NET 5+ considerations, or command-line tools/environments outside of Windows. The documentation implicitly assumes a Windows-first context by referencing only Windows-centric APIs and tools, and by omitting any mention of Linux or cross-platform scenarios.

Recommendations:

Include notes or sections clarifying cross-platform support, especially for .NET Core/.NET 5+ users on Linux and macOS.
Add examples or references for handling exceptions in cross-platform environments, including any differences in behavior or configuration on Linux.
Mention any relevant Linux troubleshooting steps, such as checking systemd logs, network configuration, or environment-specific issues that may affect Event Hubs connectivity.
If applicable, provide parity in documentation for command-line tools (e.g., Azure CLI, Bash scripts) that are commonly used on Linux, not just Windows or PowerShell.
Explicitly state when guidance is Windows-specific, and provide equivalent guidance for Linux where differences exist.

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 SDKs, which are more commonly associated with Windows environments. There are no explicit examples or instructions for Linux users, such as command-line (CLI), Bash, or cross-platform SDKs (like Python or Java). The only SDK reference is for .NET, and the only example link is for .NET, omitting Linux-prevalent languages and tools.

Recommendations:

Include examples and links for cross-platform SDKs such as Python, Java, or Node.js, which are widely used on Linux.
Provide instructions for configuring Event Hubs using the Azure CLI or Azure PowerShell (with clear cross-platform notes), not just the Azure portal.
Add a section or note explicitly addressing Linux users, including any relevant differences or considerations.
Reference SDK documentation for multiple languages, not just .NET, to ensure parity for Linux and non-Windows developers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently refers to 'command prompt' and recommends Visual Studio Code, both of which are more closely associated with Windows environments. There are no explicit Linux or macOS terminal instructions, nor are there any bash- or shell-specific notes. All command-line instructions are generic and do not clarify cross-platform differences, potentially leading Linux users to assume Windows-centric defaults. No PowerShell-specific commands are present, but the lack of Linux-specific context or examples is a subtle form of bias.

Recommendations:

Explicitly mention that all command-line instructions work in Linux/macOS terminals as well as Windows command prompt.
Where 'command prompt' is mentioned, add 'or terminal (Linux/macOS)' to clarify cross-platform applicability.
Provide at least one example of running commands in a Linux/macOS terminal, such as using bash.
When recommending editors, mention popular Linux/macOS editors (e.g., PyCharm, Sublime Text, vim) alongside Visual Studio Code.
If there are any platform-specific considerations (e.g., differences in environment variable syntax, package installation, or permissions), call them out in notes or tips.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by instructing users to create a Windows virtual machine as a prerequisite, without mentioning Linux alternatives or providing Linux-specific instructions. All setup and configuration steps assume a Windows environment, and there are no examples or guidance for users on Linux systems.

Recommendations:

Include instructions for creating and configuring a Linux virtual machine as an alternative to Windows.
Provide Linux-specific guidance for installing prerequisites such as JDK, Maven, and Git (e.g., using apt, yum, or other package managers).
Ensure that all command-line instructions are cross-platform or provide both Windows and Linux command examples where differences exist.
Mention that the Kafka client code and Event Hubs integration are platform-agnostic, and clarify any OS-specific steps.
Update screenshots and portal instructions to indicate that managed identities and role assignments apply to both Windows and Linux VMs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page exhibits a mild Windows bias, primarily by listing .NET (a Microsoft/Windows-centric technology) SDKs and tools first in all tables and sections, and by providing extra detail and historical context for .NET/Windows libraries. There is also mention of 'WindowsAzure.Messaging' and .NET Framework-specific packages, which are Windows-specific tools. However, there are no explicit PowerShell examples or exclusive Windows command-line instructions, and Linux/Java/Python/JavaScript/Go SDKs are also documented with parity in the main tables.

Recommendations:

Reorder SDK tables or alternate the order of language listings to avoid always placing .NET/.NET Framework first.
Provide equivalent historical and technical context for non-Windows SDKs (e.g., Java, Python) in their own sections, not just for .NET.
Clarify cross-platform compatibility for all SDKs, especially for .NET Standard libraries, and explicitly mention Linux/Mac support where applicable.
Avoid using Windows-specific package names (like 'WindowsAzure.Messaging') in section headers or summaries unless absolutely necessary, and always provide cross-platform alternatives.
Consider adding a brief statement at the top clarifying that all major SDKs are cross-platform unless otherwise noted.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page shows a Windows bias by using Windows-specific device IDs (e.g., 'Windows109') in all JSON examples and not providing any Linux-based examples or references. There are no explicit Linux commands, device names, or screenshots, and the only sample module client code references .NET (commonly associated with Windows, though cross-platform). No mention is made of Linux tools, patterns, or device names, and the examples and walkthroughs implicitly assume a Windows environment.

Recommendations:

Include examples with Linux-based device IDs (e.g., 'Ubuntu2004', 'raspberrypi', etc.) alongside or instead of Windows IDs in JSON samples.
Explicitly mention that the instructions and tools (Azure CLI, VS Code, Azure Portal) are cross-platform and work on Linux, macOS, and Windows.
Add screenshots or terminal snippets from Linux environments where appropriate.
If referencing code samples, consider including examples in Python or Node.js (popular on Linux) in addition to .NET.
Clarify that the steps and troubleshooting guidance apply equally to Linux-based IoT Edge devices.
Where possible, provide Linux-specific troubleshooting tips or notes (e.g., file paths, service management commands).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and PowerShell examples for configuring Azure Firewall DNS settings, but the PowerShell examples are prominent and detailed, reflecting a bias toward Windows-centric tooling. There are no Linux-specific command-line examples (such as Bash scripts or Linux-native tools), and PowerShell is presented as an equal alternative to CLI, despite being primarily a Windows tool. The documentation does not mention or address Linux-specific considerations or workflows, and the ordering of examples sometimes places PowerShell before or at parity with CLI, which may not reflect the cross-platform user base.

Recommendations:

Add explicit Bash shell examples for all CLI commands, demonstrating usage in a typical Linux environment.
Clarify that Azure CLI is cross-platform and can be used on Windows, macOS, and Linux, while PowerShell is primarily for Windows users (unless using PowerShell Core).
Consider providing Linux-specific notes or troubleshooting tips, such as how to restart network services on Linux VMs after DNS changes.
Where possible, lead with CLI/Bash examples before PowerShell, as CLI is more universally accessible across platforms.
Include references or links to Linux administration documentation for related tasks (e.g., updating DNS settings on Linux VMs).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell as a prerequisite for local command-line configuration, without mentioning Azure CLI or Bash alternatives. The only command-line tool referenced is Azure PowerShell, which is most commonly associated with Windows environments. No Linux-specific tools, shell instructions, or parity examples are provided. However, the main configuration flow is via the Azure portal, which is cross-platform.

Recommendations:

Mention Azure CLI as an alternative to Azure PowerShell for users on Linux or macOS.
Provide equivalent Azure CLI commands or instructions for all PowerShell references.
Update the 'Before you begin' section to include both Azure PowerShell and Azure CLI as supported local tools.
Clarify that the Azure portal is accessible from any OS, and provide links to cross-platform command-line documentation.
If screenshots or examples reference Windows-specific UI or paths, consider including notes or images from Linux/macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by linking only to guidance for configuring DSCP markings on Windows 10 clients, with no mention of Linux or cross-platform configuration steps. There are no examples or references for Linux tools or methods to set QoS/DSCP markings, which may leave Linux administrators without clear guidance.

Recommendations:

Include references or links to documentation on configuring DSCP markings and QoS policies on Linux systems (e.g., using iptables, tc, or systemd-networkd).
Provide example commands or configuration snippets for both Windows and Linux platforms.
Explicitly mention that the guidance applies to both Windows and Linux clients, and clarify any platform-specific differences.
Add a section or note addressing how to achieve equivalent QoS configuration on Linux endpoints.

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 Linux equivalents or instructions, and the only OS context given is Windows, which may lead users to believe that Linux is unsupported or less suitable for this scenario.

Recommendations:

Include examples and instructions for deploying and testing with Linux virtual machines (e.g., Ubuntu, CentOS) alongside or instead of Windows VMs.
Explicitly mention that the scenario works with both Windows and Linux VMs, and provide sample Terraform code for azurerm_linux_virtual_machine.
If remote connectivity or testing steps are described (e.g., using RDP for Windows), also describe SSH access for Linux VMs.
Ensure that any firewall rule testing steps include Linux command-line examples (e.g., using curl or wget) in addition to Windows-based methods.
Review the documentation for any other implicit Windows assumptions and clarify cross-platform compatibility where applicable.

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 clarifying platform parity or mentioning cross-platform PowerShell Core. There are no Linux- or macOS-specific instructions, nor is there any mention of Bash scripting or other Linux-native tools.

Recommendations:

Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
Mention that PowerShell Core is available cross-platform, or clarify if the instructions are specific to Windows PowerShell.
Consider providing Bash script examples or explicitly stating that the CLI commands work in Bash on Linux/macOS.
If referencing PowerShell, note its cross-platform availability and provide installation links for non-Windows users.
Add a note or section for Linux/macOS users to ensure they feel equally supported.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes configuration using the Azure Portal GUI and does not provide any command-line examples. There is no mention of PowerShell, Azure CLI, or any OS-specific tools, but all instructions assume a graphical, browser-based workflow. This approach implicitly favors Windows environments, as Windows users are more likely to use the Azure Portal, while Linux users often prefer or require CLI-based instructions. There are no examples or references for Linux-native workflows (such as Azure CLI commands), nor is there any parity for headless or scriptable environments.

Recommendations:

Add Azure CLI command examples for enabling/disabling rate limiting, as Azure CLI is cross-platform and widely used on Linux.
If PowerShell examples are added, ensure Azure CLI equivalents are always provided and presented first or side-by-side.
Explicitly mention that all steps can be performed via the Azure CLI or REST API, and provide links or examples for those methods.
Include a section or callout for users who prefer command-line or automated/scripted workflows, referencing both Windows and Linux environments.
Review screenshots and instructions to ensure they do not assume a Windows-only experience (e.g., avoid referencing Windows-specific UI elements or terminology).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The tutorial exclusively uses Windows Server virtual machines and only demonstrates remote desktop (RDP) and Internet Explorer for connectivity and testing. There are no Linux VM deployment steps, nor are there examples for SSH access or Linux-based testing. The documentation assumes a Windows-centric workflow throughout, omitting Linux alternatives.

Recommendations:

Include parallel instructions for deploying a Linux VM (e.g., Ubuntu) alongside the Windows VM steps.
Provide examples for connecting to Linux VMs using SSH, and for testing firewall rules with Linux tools (e.g., curl, wget, or a browser like Firefox).
When demonstrating firewall rules, show both RDP (for Windows) and SSH (for Linux) DNAT/network rules.
In testing sections, include Linux-based connectivity tests (e.g., SSH from one Linux VM to another, or browsing with a Linux browser).
Use neutral language and ordering (e.g., 'Windows or Linux VM') to avoid implying Windows is the default or only supported platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively uses Windows Server as the example OS for the workload VM, with no mention of Linux alternatives or instructions. The testing section assumes the use of Remote Desktop and Internet Explorer, both Windows-specific tools, and does not provide Linux equivalents or guidance. While the Azure portal is cross-platform, the step-by-step instructions and validation steps are Windows-centric.

Recommendations:

Provide parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the workload subnet, including example settings.
Include guidance for connecting to the Linux VM (e.g., using SSH) and testing outbound connectivity (e.g., using curl or wget to access allowed FQDNs).
In the firewall DNAT rule section, mention SSH (port 22) as an alternative to RDP (port 3389) for Linux VMs.
In the testing section, add Linux-specific examples for verifying DNS and HTTP/HTTPS access (e.g., using dig, nslookup, curl, or wget).
Explicitly state that the procedure is applicable to both Windows and Linux VMs, and provide links to relevant Azure Linux VM documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively deploying Windows Server virtual machines in the Terraform example and referring only to Windows VMs throughout. There are no examples or mentions of deploying Linux VMs, nor are there instructions or notes for users who may wish to use Linux servers instead. This may give the impression that only Windows is supported or recommended in this scenario.

Recommendations:

Include parallel examples or instructions for deploying Linux virtual machines using azurerm_linux_virtual_machine alongside the Windows VM steps.
Update the narrative to mention that either Windows or Linux VMs can be used, and provide guidance or code samples for both.
Where VM credentials or configuration are discussed (such as random_password for Windows), add equivalent Linux-focused steps (e.g., SSH key generation).
Ensure that any troubleshooting or verification steps are not specific to Windows and clarify cross-platform applicability.
Consider rephrasing the description and checklist to refer to 'virtual machines' generically, or explicitly state that both Windows and Linux are supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides a PowerShell example (Remove-AzResourceGroup) for resource cleanup but does not offer equivalent CLI or Bash commands for Linux/macOS users. No Linux-specific or cross-platform command-line instructions are given, despite the ARM template including a Linux jumpbox.

Recommendations:

Add Azure CLI and/or Bash examples for resource group deletion (e.g., az group delete --name <your resource group name>).
Wherever PowerShell is used, provide equivalent cross-platform commands or clearly indicate alternatives for Linux/macOS users.
Consider including a table or section summarizing common operations (deploy, delete, review) with both PowerShell and Azure CLI/Bash commands.
Review other steps for implicit Windows assumptions and clarify that all steps can be performed from any OS using the Azure CLI or portal.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by focusing exclusively on deploying and accessing Windows Server virtual machines (with RDP), without mentioning or providing examples for Linux VMs or SSH access. The only VM example is Windows, and the NAT rules are described as enabling RDP to Windows Server 2019 VMs. There are no Linux VM deployment steps or verification instructions for Linux users.

Recommendations:

Include parallel examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine) alongside the Windows VM steps.
Describe how to configure NAT rules for SSH access to Linux VMs, in addition to RDP for Windows.
In the checklist and resource creation steps, mention both Windows and Linux VM options, or provide a choice.
In the verification section, add instructions for verifying access to Linux VMs (e.g., using SSH) as well as Windows VMs.
Reference documentation for both Windows and Linux VM management in Azure, not just Windows/PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on Windows-based virtual desktop infrastructure, specifically Azure Virtual Desktop (which is Windows-centric), and does not mention or provide guidance for Linux-based virtual desktop solutions or clients. All examples and descriptions assume a Windows environment, with no reference to Linux equivalents or cross-platform scenarios.

Recommendations:

Include references to Linux-based virtual desktop solutions that can be protected by Azure Firewall, such as Linux VDI or third-party Linux desktop virtualization tools.
Provide examples or guidance for securing outbound/inbound connections for Linux virtual machines or Linux-based remote desktop clients.
Mention that Azure Firewall can protect both Windows and Linux workloads, and provide parity in documentation for both operating systems.
If possible, add links or references to documentation on securing Linux remote work environments with Azure Firewall.

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 and providing only instructions for connecting via Remote Desktop (RDP) and using Microsoft Edge. There are no examples or guidance for deploying or testing with a Linux VM, nor are there instructions for connecting via SSH or using Linux-based tools to test firewall rules.

Recommendations:

Add parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet, including appropriate configuration steps.
Include examples for connecting to the Linux VM using SSH, and provide Linux-based testing steps (e.g., using curl or wget to test outbound access, dig or nslookup for DNS testing).
When describing the test phase, offer both Windows (RDP, Edge) and Linux (SSH, browser or command-line tools) options.
Consider mentioning both Windows and Linux options side-by-side throughout the tutorial, rather than only referencing Windows tools and patterns.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively demonstrates deploying and testing Azure Firewall using a Windows Server virtual machine, with no mention or example of Linux-based VMs. The test instructions (e.g., using Remote Desktop and Internet Explorer) are Windows-specific, and there are no Linux alternatives or parity in the walkthrough. The only OS option presented for the test VM is Windows, and the testing steps assume a Windows environment.

Recommendations:

Add parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the test subnet, including example configuration values.
Include Linux-specific testing steps, such as connecting via SSH and using a browser like Firefox or Chrome to test outbound access.
Provide guidance on configuring DNS settings for Linux VMs (e.g., editing /etc/resolv.conf or using cloud-init).
Wherever possible, present both Windows and Linux options side-by-side, or at least mention Linux as an alternative.
Avoid assuming the use of Windows-only tools (e.g., Remote Desktop, Internet Explorer) in testing steps; suggest cross-platform or Linux-native alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The tutorial exclusively uses a Windows Server virtual machine as the workload example and instructs users to test connectivity using Remote Desktop (RDP), which is a Windows-centric protocol. There are no Linux VM deployment instructions or SSH-based testing examples, and the only OS option explicitly mentioned is Windows Server. This creates a Windows-first impression and omits Linux parity in both deployment and testing steps.

Recommendations:

Add parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet, including specifying username, authentication, and any required inbound ports (e.g., 22 for SSH).
Include testing steps for Linux VMs, such as connecting via SSH to the firewall public IP address and verifying access to the Linux VM.
When listing OS choices for the VM, mention both Windows and Linux options, or provide a choice step.
If using RDP as an example, also provide an SSH example for Linux, including the necessary DNAT rule for port 22.
Ensure that screenshots or UI steps do not assume only Windows Server images are being used.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively uses Windows Server as the example workload VM and only demonstrates testing via Remote Desktop (RDP) to port 3389, which is specific to Windows environments. There are no Linux VM deployment instructions, nor are there examples for Linux-based access (such as SSH on port 22). This presents a Windows-first bias and omits Linux parity in both deployment and testing steps.

Recommendations:

Include parallel instructions for deploying a Linux VM (e.g., Ubuntu Server) in the 'Create a virtual machine' section.
Provide an example NAT rule for SSH (port 22) to a Linux VM, alongside the RDP example.
In the 'Test the firewall' section, add steps for connecting via SSH to the Linux VM using its public IP and port 22.
When referencing operating system-specific steps, present both Windows and Linux options, or clarify that the process is OS-agnostic where possible.
Consider mentioning cross-platform remote access tools or protocols, or provide a note about how to adapt the instructions for Linux workloads.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The tutorial exclusively uses Windows Server as the example operating system for the workload VM, with no mention of Linux alternatives or instructions. The testing steps assume the use of Remote Desktop and Internet Explorer, both Windows-specific tools, and there are no Linux command-line or desktop environment equivalents provided. The only alternative workflow mentioned is Azure PowerShell, with no reference to Azure CLI or Bash scripting.

Recommendations:

Include parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu Server) alongside the Windows Server example.
Provide Linux-compatible testing steps, such as using SSH for remote access and browsers like Firefox or Chrome for validation.
Reference Azure CLI and Bash scripting alternatives for users who prefer or require non-Windows environments.
Explicitly mention that the tutorial is applicable to both Windows and Linux VMs, and provide guidance for both where steps differ.
When suggesting remote access, offer both RDP (for Windows) and SSH (for Linux) instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation does not explicitly mention or provide examples for Linux or macOS environments. All command-line instructions (such as checking Python version and using az login) are given in a generic way, but there is no guidance on platform-specific considerations. The lack of Linux-specific notes or examples, especially for common issues like Python environment setup, file permissions, or Azure CLI installation on Linux, may make the documentation feel Windows-centric by omission.

Recommendations:

Add explicit notes or examples for Linux and macOS users, such as verifying Python installation (e.g., python3 --version), and using pip3 if needed.
Include platform-specific guidance for installing the Azure CLI on Linux and macOS, with links to official installation instructions.
Mention any differences in file path conventions or permissions that may affect Linux/macOS users.
Provide troubleshooting tips for common issues encountered on Linux, such as missing dependencies or permission errors.
Ensure that all command-line examples are cross-platform or provide alternatives for each major OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by only providing examples for deploying App Services using the Windows operating system. The 'Operating System' field is set to 'Windows' by default, and there are no instructions or examples for deploying on Linux, which is a common and supported scenario for Azure App Services. No Linux-specific guidance, screenshots, or parity notes are included.

Recommendations:

Add parallel instructions and screenshots for deploying App Services on Linux (e.g., by selecting 'Linux' in the 'Operating System' field and choosing a Linux-compatible runtime stack).
Include a note or section explaining that both Windows and Linux are supported for App Services, and highlight any differences in configuration or available features.
Provide example configurations for both Windows and Linux, possibly using tabs or side-by-side comparisons.
Ensure that terminology and steps are inclusive of both platforms (e.g., refer to 'App Service plan' rather than 'Windows Plan' when possible, or clarify the difference).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exhibits mild Windows bias by referencing the Windows-style environment variable (%HADOOP_HOME%) in the file path for core-site.xml, and by using Windows path notation. There are no explicit Linux or cross-platform examples, and the only file path example uses Windows conventions. However, there are no command-line examples (PowerShell or otherwise), and most of the content is platform-neutral.

Recommendations:

When referencing file paths, provide both Windows and Linux/macOS formats (e.g., %HADOOP_HOME%/conf/core-site.xml and $HADOOP_HOME/conf/core-site.xml).
Clarify that the location of configuration files applies to both Windows and Linux-based HDInsight clusters, or specify if it is Windows-only.
If including environment variable references, use cross-platform notation or mention both (%VAR% for Windows, $VAR for Linux/macOS).
Add Linux/macOS-specific notes or examples where relevant, especially if there are differences in file paths or commands.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides a quickstart for creating an Azure Front Door using Terraform, but it only demonstrates the creation of an App Service app using the azurerm_windows_web_app resource. There are no examples or mentions of Linux-based App Service equivalents (such as azurerm_linux_web_app), nor are there instructions or notes for users deploying on Linux. This omission may lead users to assume that only Windows-based web apps are supported or recommended.

Recommendations:

Include parallel examples or instructions for creating an App Service app using azurerm_linux_web_app, or at least mention that Linux is supported and link to relevant documentation.
Add a note clarifying that both Windows and Linux App Service plans are supported, with guidance on how to choose between them.
Where possible, provide code samples or references for both Windows and Linux scenarios to ensure parity.
Review any referenced sample code to ensure Linux examples are present and easy to find.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure PowerShell and Azure CLI examples for network resource queries, but PowerShell examples are consistently presented first. There are no Linux-specific shell examples (e.g., Bash with Azure CLI), and the use of PowerShell as the primary scripting language may implicitly favor Windows users. However, Azure CLI commands are included, which are cross-platform, mitigating some bias. No Windows-only tools or patterns are mentioned, but the ordering and scripting language preference suggest a mild Windows-first bias.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (which is cross-platform) first to better support Linux users.
Explicitly note that Azure CLI commands can be run in Bash on Linux/macOS, and provide example shell prompts (e.g., $ for Bash, PS> for PowerShell) to clarify context.
Where possible, include Bash script snippets for common tasks, especially in sections where PowerShell scripting is shown.
Add a brief section or note highlighting that all Azure CLI commands are fully supported on Linux, macOS, and Windows.
Review linked documents to ensure Linux parity in examples and instructions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page lists several development tools, including Visual Studio, IntelliJ, Eclipse, and VS Code, with a specific mention of 'HDInsight Visual Studio tool'—a Windows-only IDE—alongside cross-platform tools. The ordering of tools in the 'Tools' section places Visual Studio last, but its inclusion without a Linux equivalent (e.g., no mention of Linux-specific editors or command-line tools) introduces a subtle Windows bias. There are no explicit PowerShell or Windows command examples, but the presence of Visual Studio as a recommended tool and the lack of parity for Linux-native tooling or workflows suggest a mild Windows-first perspective.

Recommendations:

Add explicit mention of Linux-compatible development tools and workflows, such as command-line interfaces, Emacs, or Linux-specific editors.
Clarify which tools are cross-platform and which are Windows-only (e.g., note that Visual Studio is Windows-only, while VS Code, IntelliJ, and Eclipse are cross-platform).
Provide Linux-specific troubleshooting examples or links alongside any Windows-specific tools or instructions.
Consider reordering the 'Tools' list to lead with cross-platform options or group by platform compatibility.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both PowerShell and Azure CLI instructions, but PowerShell (a Windows-centric tool) is consistently presented first in all code tabs and explanations. The narrative and guidance around using PowerShell (including Cloud Shell and local installation) is more detailed and prominent than for Azure CLI. There are no explicit Linux-only examples or references to Linux-native tools, and the documentation assumes familiarity with PowerShell patterns.

Recommendations:

Alternate the order of PowerShell and Azure CLI tabs, or present Azure CLI first to avoid implicit prioritization of Windows tooling.
Ensure that explanations and guidance for Azure CLI are as detailed as those for PowerShell, including instructions for both Windows and Linux environments.
Explicitly mention that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
Where possible, provide bash shell examples or reference Linux-native workflows for common tasks (e.g., DNS configuration, certificate management).
Add a note or section highlighting that all steps can be performed from Linux or macOS using Azure CLI, and provide troubleshooting tips for those environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents a clear Windows-first bias by listing the Azure Portal (GUI) and PowerShell methods before the Azure CLI approach. The PowerShell section is detailed and assumes the use of PowerShell or Azure Cloud Shell, which is more familiar to Windows users. While a CLI section is present (which is cross-platform), it is placed after the PowerShell section, and there are no explicit Linux- or Bash-specific examples or troubleshooting notes. No Linux-specific tools or workflows are highlighted.

Recommendations:

Reorder the technical pivots so that Azure CLI (which is cross-platform and preferred by many Linux users) appears before PowerShell, or at least give them equal prominence.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific notes or troubleshooting tips where relevant.
Where PowerShell is referenced, also mention that Azure Cloud Shell supports Bash, and provide equivalent Bash/CLI snippets for any PowerShell-specific logic.
In the prerequisites and tool installation sections, include instructions for installing Azure CLI and PowerShell on Linux, and clarify that both are supported.
Add a note in the introduction or prerequisites highlighting that all workflows can be completed from Linux, macOS, or Windows, and link to platform-specific setup guides.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples for either Windows (PowerShell, Command Prompt) or Linux (Bash, CLI). However, the absence of CLI examples (such as Azure CLI commands) means Linux users do not see parity or explicit guidance for non-Windows environments. Additionally, the documentation refers to the Azure Portal, which is platform-agnostic but often associated with Windows-centric workflows in Azure documentation. There are no explicit Windows-only tools or commands, but the lack of Linux/CLI examples is a notable omission.

Recommendations:

Add Azure CLI examples for all major steps (creating storage accounts, configuring Front Door, purging cache, etc.), as Azure CLI is cross-platform and widely used on Linux.
Where possible, provide both portal and CLI instructions side-by-side, or link to CLI documentation for each step.
Explicitly mention that all steps can be performed from any OS via the Azure Portal, but highlight CLI alternatives for automation and scripting.
If PowerShell examples are ever added, ensure Bash/Azure CLI equivalents are also provided.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively describes configuration steps using the Azure Portal GUI and does not provide any command-line examples. There is no mention of cross-platform CLI tools (such as Azure CLI or Azure PowerShell), nor are there any Linux-specific instructions or examples. The absence of CLI examples implicitly favors Windows users, as the Azure Portal experience is often more closely associated with Windows environments, and omits parity for Linux or automation-focused users.

Recommendations:

Add Azure CLI examples for all configuration steps, including enabling managed identity and assigning Key Vault permissions. Azure CLI is cross-platform and works on Linux, macOS, and Windows.
Where relevant, provide Azure PowerShell examples as well, but ensure Azure CLI is presented first or alongside PowerShell to avoid Windows-first bias.
Explicitly mention that all steps can be performed using CLI tools on any platform, and link to relevant CLI documentation.
Include a section or callout for automation and scripting, highlighting how these tasks can be performed non-interactively (e.g., in CI/CD pipelines or on Linux servers).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page provides only portal-based (GUI) instructions and screenshots, with no command-line examples for either Windows (PowerShell) or Linux (CLI). However, there is an implicit Windows bias because Azure documentation often defaults to PowerShell or Windows-centric tools when command-line examples are provided, and this page does not make any effort to include or mention Linux CLI (Azure CLI) equivalents. Additionally, the terminology and workflow are oriented around the Azure Portal, which is more familiar to Windows users, and there is no mention of how to perform these tasks using cross-platform tools.

Recommendations:

Add Azure CLI (az) command-line examples for all major steps, such as enabling managed identities, assigning roles, and associating identities with origin groups.
Explicitly mention that all steps can be performed using Azure CLI on Linux, macOS, or Windows, and provide links to relevant CLI documentation.
If PowerShell examples are added in the future, ensure that Azure CLI equivalents are provided alongside them.
Include a section or callout for users who prefer automation or scripting, referencing both PowerShell and Azure CLI.
Review terminology and instructions to ensure they are platform-neutral and do not assume use of the Azure Portal or a Windows environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides configuration examples for multiple origin types, but the IIS (Windows) example is presented before the AKS NGINX (Linux) example. Additionally, the IIS example is detailed and uses Windows-specific configuration (web.config), while there is no equivalent example for generic Linux web servers (e.g., Apache, NGINX outside AKS). This ordering and tool selection may suggest a slight Windows bias.

Recommendations:

Reorder the example sections so that Linux-based origins (e.g., AKS NGINX, generic NGINX, Apache) are presented before or alongside Windows/IIS examples.
Add configuration examples for common Linux web servers such as Apache and standalone NGINX (not just AKS ingress), showing how to filter the X-Azure-FDID header.
Ensure that for every Windows-specific example, there is a Linux equivalent, and that both are equally detailed.
Explicitly mention cross-platform applicability and provide links or references to Linux documentation where relevant.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides detailed instructions and screenshots for capturing the Reference String using the Microsoft Edge browser and its developer tools, which are primarily associated with Windows environments. There are no examples or instructions for capturing the Reference String using tools or browsers commonly used on Linux (such as curl, wget, Firefox, or Chrome on Linux), nor are there command-line examples that would be cross-platform. The only method described is Windows-centric, and it is presented as the default/primary approach.

Recommendations:

Add instructions and examples for capturing the Reference String using cross-platform command-line tools such as curl or wget, which are available on both Linux and Windows.
Include a browser-agnostic section or provide examples for other browsers (e.g., Firefox, Chrome) and clarify that the process is similar across platforms.
Explicitly mention that the Reference String can be obtained on any OS and provide at least one Linux-specific example (e.g., using curl in a Linux terminal to view response headers).
Consider reordering the examples or providing a tabbed interface for different operating systems (Windows, Linux, macOS) to ensure parity and avoid the perception of Windows-first bias.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references Windows-specific tools (Fiddler) and does not provide Linux-equivalent examples or mention Linux tools for troubleshooting. While one example uses OpenSSL (a cross-platform tool), there is a lack of parity in suggesting or demonstrating Linux-native approaches or alternatives where relevant.

Recommendations:

When suggesting Fiddler, also mention Linux-compatible alternatives such as mitmproxy, curl, or tcpdump, and provide example commands.
Where browser developer tools are mentioned, clarify that these are available on all major platforms.
For all troubleshooting steps involving command-line tools, provide both Windows (PowerShell/CMD) and Linux (bash) example commands where applicable.
Explicitly state that OpenSSL commands work on both Windows and Linux, and provide installation guidance if needed.
Review the documentation for any other implicit Windows-first assumptions and ensure Linux users are equally supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The tutorial demonstrates a bias toward Windows by exclusively using Windows Server as the VM image and only providing instructions for connecting via RDP. There are no Linux VM creation steps, nor are there SSH or Linux-specific instructions. This may lead Linux users to feel unsupported or unclear about how to follow the tutorial with Linux VMs.

Recommendations:

Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
Include steps for connecting to a Linux VM using SSH, in addition to the RDP instructions for Windows.
Show how to verify network connectivity from a Linux VM (e.g., using curl or wget to access www.bing.com).
Clarify in the prerequisites or introduction that the tutorial applies to both Windows and Linux VMs, and link to both sets of instructions.
Where possible, use neutral terms (e.g., 'connect to your VM') and provide both RDP (Windows) and SSH (Linux) options.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page is largely neutral and platform-agnostic in its main content, focusing on open-source component versions. However, in the 'Next steps' section, a link specifically highlights working with HDInsight from a Windows PC and references Windows tools, without an equivalent mention or link for Linux or cross-platform tools. This suggests a subtle Windows-first and Windows-tools bias.

Recommendations:

Add a parallel link in the 'Next steps' section for working with HDInsight from Linux or macOS, or a general cross-platform guide.
Ensure that references to client tools or setup guides include both Windows and Linux (and optionally macOS) instructions, or clearly indicate cross-platform compatibility.
Review other related documentation to ensure Linux users are equally supported and not required to infer steps from Windows-specific guides.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page lists a 'Work in Apache Hadoop on HDInsight from a Windows PC' link in the 'Next steps' section, highlighting Windows tooling. There is no equivalent Linux-specific guidance linked, and the Windows PC workflow is mentioned before any Linux alternatives, indicating a subtle Windows-first bias.

Recommendations:

Add a parallel link or section for 'Work in Apache Hadoop on HDInsight from a Linux PC' to provide Linux users with equivalent guidance.
Ensure that Linux tools and workflows are mentioned alongside Windows options, not just in secondary documentation.
Review cross-references and 'Next steps' to balance platform-specific guidance, so Linux users are not left out or made to feel like a secondary audience.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page exhibits mild Windows bias, particularly in the 'Next steps' section where the Windows PC tooling guide is listed before any Linux-specific guidance. Additionally, there is a direct link to 'Work in Apache Hadoop on HDInsight from a Windows PC', but no equivalent Linux-focused resource is mentioned. The main content does not provide OS-specific examples, but the navigation and resource emphasis favor Windows.

Recommendations:

Add a parallel link in the 'Next steps' section for working with Apache Hadoop on HDInsight from a Linux or macOS environment.
Ensure that any tooling or workflow documentation for Windows is matched with Linux (and optionally macOS) equivalents.
Review the order of links in 'Next steps' to avoid consistently listing Windows resources before Linux ones.
Consider including a brief section or note clarifying cross-platform support and linking to platform-agnostic or platform-specific guides as appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash (with jq) and PowerShell examples for retrieving host names via the Ambari REST API. However, the PowerShell example is more detailed, including credential prompts, and is presented immediately after the Bash example. There is a slight bias in that the PowerShell example uses Windows-specific cmdlets and patterns, and the Bash example does not include instructions for Windows users who may use WSL or Git Bash. The documentation does not mention Linux tools or environments explicitly, nor does it provide troubleshooting or installation guidance for jq on Linux.

Recommendations:

Ensure that both Bash and PowerShell examples are equally detailed and cover authentication and output parsing.
Explicitly mention that the Bash example works on Linux, macOS, and Windows (with WSL or Git Bash), and provide installation instructions for jq.
Consider presenting the Bash (Linux/macOS) example first, or clarify that both are supported equally.
Add troubleshooting tips for common issues on both Linux and Windows platforms.
Where possible, provide parity in explanation and context for both operating systems, including any OS-specific caveats.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides host information retrieval commands specifically for Windows command prompt, with explicit references to Windows paths and tools (e.g., C:\HDI\jq-win64.exe), and notes that 'slight variations will be needed for other environments' without providing Linux/macOS equivalents. No Linux or cross-platform example is given for this step, which may hinder users on non-Windows systems.

Recommendations:

Provide equivalent Linux/macOS command examples for retrieving Kafka ZooKeeper and broker hosts, using standard Unix shell syntax and typical jq installation paths (e.g., /usr/bin/jq).
Clearly label both Windows and Linux/macOS command blocks, so users can easily find the instructions relevant to their environment.
Avoid referencing only Windows-specific paths (such as C:\HDI\jq-win64.exe); instead, use environment variables or note typical installation locations for different platforms.
Where possible, use cross-platform command syntax or provide guidance on adapting commands for different shells (cmd, PowerShell, Bash, etc.).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page is largely neutral and focused on HDInsight versions and support policies, with most technical details referencing Ubuntu as the cluster OS. However, in the 'Next steps' section, the link 'Work in Apache Hadoop on HDInsight from a Windows PC' is called out specifically, while no equivalent Linux or cross-platform guidance is highlighted. Additionally, in the introduction, deployment methods are listed as 'Azure portal and other deployment methods like PowerShell, CLI and the .NET SDK', with PowerShell (a Windows-centric tool) mentioned before the cross-platform CLI, which may suggest a subtle Windows-first bias.

Recommendations:

Add a 'Work in Apache Hadoop on HDInsight from a Linux PC' or 'Work in Apache Hadoop on HDInsight from macOS/Linux' link in the 'Next steps' section to provide parity for non-Windows users.
When listing deployment methods, mention cross-platform tools (such as Azure CLI) before or alongside PowerShell to avoid implying a Windows-first workflow.
If there are any platform-specific tools or guides, ensure that both Windows and Linux (and optionally macOS) equivalents are referenced and linked with equal prominence.
Consider a general 'Accessing HDInsight from your local machine' guide that covers Windows, Linux, and macOS, rather than platform-specific links.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both Azure PowerShell and Azure CLI examples for network security group configuration, but consistently lists PowerShell (a Windows-centric tool) before CLI. The most detailed, step-by-step example is given in PowerShell, with CLI following. There are no Linux shell (bash) script examples for Azure CLI, and no explicit mention of using CLI on Linux, though CLI is cross-platform. However, the DNS configuration section is Linux-focused, and the 'Test your settings' section recommends using a Linux VM, partially balancing the bias.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present CLI first to avoid implicit Windows-first bias.
Explicitly state that Azure CLI commands can be run on Linux, macOS, and Windows, and provide bash shell script examples where appropriate.
Add a short section or callout for Linux users, highlighting that all CLI steps are fully supported on Linux.
Where possible, provide bash script blocks for Azure CLI steps to demonstrate parity and usability for Linux users.
Consider including a table or quick reference comparing PowerShell and CLI commands, clarifying platform compatibility.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias towards Windows/Azure-centric tooling and patterns. It exclusively references Azure SQL Database (a Microsoft-managed service) as the only supported external database for Ambari, with no mention of Linux-native or open-source alternatives (such as PostgreSQL or MySQL). All command-line examples use Azure CLI, which, while cross-platform, is tightly coupled with Azure's ecosystem. There are no examples or guidance for Linux-native database management, nor are there references to Linux tools or shell commands for database setup or connectivity.

Recommendations:

Include examples or guidance for using open-source, Linux-native databases (such as PostgreSQL or MySQL) as external Ambari databases, if supported.
Provide Linux shell (bash) command examples for database setup, user creation, and permission granting, alongside or instead of SQL Server-specific commands.
Clarify whether only Azure SQL Database is supported, or if other database engines can be used, and document their setup if possible.
Add references to Linux-native tools (e.g., psql, mysql CLI) for database management tasks.
Ensure parity in instructions and examples for both Windows and Linux users, especially for database provisioning and connectivity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias, primarily by using Windows-style paths (e.g., C:\HD\HDexample) in all file and folder examples, and not providing equivalent Linux/macOS examples. There are no explicit Linux command-line or file path examples, and the only Linux-specific mention is a note about installing xclip for copy-table data. The documentation assumes a Windows environment for directory navigation and file creation, which can be confusing for Linux/macOS users.

Recommendations:

Provide parallel Linux/macOS examples for file paths (e.g., use /home/user/HDexample alongside C:\HD\HDexample).
When giving instructions for opening folders or creating files, include both Windows and Linux/macOS navigation steps.
Explicitly mention that all steps apply to Linux/macOS unless otherwise noted, and highlight any differences.
Include screenshots or terminal snippets from Linux/macOS environments where relevant.
Add a section or callouts for common Linux/macOS issues or prerequisites (e.g., permissions, Mono installation, xclip usage).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page focuses exclusively on .NET samples for Azure HDInsight, which are typically associated with Windows development environments (e.g., Visual Studio). There are no examples or guidance for Linux users or alternative development environments. The only prerequisite and tooling mentioned is the Azure HDInsight SDK for .NET, and Visual Studio subscriber benefits are highlighted, reinforcing a Windows-centric approach.

Recommendations:

Include instructions for setting up and using the .NET SDK on Linux and macOS, such as using VS Code or JetBrains Rider.
Provide examples of running the .NET samples using cross-platform .NET CLI commands, not just Visual Studio.
Mention alternative editors and tools that are available on Linux (e.g., VS Code, command-line tools).
Add a note clarifying that .NET Core/.NET 5+ is cross-platform and can be used on Linux and macOS.
Where Visual Studio is mentioned, also mention equivalent Linux-friendly workflows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides examples and instructions for both Azure PowerShell and Azure CLI, but PowerShell is consistently presented before CLI, and PowerShell examples are more detailed and prominent. There are multiple references to PowerShell-specific cmdlets and scripts, with CLI examples and commands appearing later or with less emphasis. There is no explicit Windows-only tooling, but the ordering and depth of PowerShell coverage suggest a subtle Windows-first bias.

Recommendations:

Present Azure CLI and PowerShell examples in parallel or alternate their order to avoid implying preference.
Ensure that CLI examples are as detailed and comprehensive as PowerShell examples, including output samples and step-by-step instructions.
Add explicit notes that PowerShell can be used cross-platform, but highlight that Azure CLI is often preferred on Linux/macOS.
Where possible, provide Bash shell script snippets for common tasks, especially in sections focused on Linux-based clusters.
Review and balance the depth of coverage for PowerShell and CLI to ensure Linux users are equally supported.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides a balanced overview of SSH usage across platforms, but there is a subtle Windows bias in the ordering and emphasis of SSH client options. Windows-specific tools and installation instructions are given more detailed attention, and Windows alternatives (including graphical clients) are listed before or with more explanation than their Linux equivalents. However, Linux/Unix commands and patterns are present throughout, and most command-line examples use standard ssh/scp syntax applicable to all platforms.

Recommendations:

When listing SSH clients, mention Linux/Unix/macOS built-in support first, as these platforms natively include SSH tools, then describe Windows options.
Provide equal detail for Linux/Unix/macOS SSH client usage and configuration, not just for Windows installation.
Include explicit Linux/Unix/macOS command-line examples where possible, especially for tasks like SSH key generation, agent forwarding, and file copying.
When referencing graphical SSH clients, note that such tools are available on Linux/macOS as well (e.g., GNOME Terminal, Konsole, or FileZilla for SCP/SFTP).
Ensure that any PowerShell or Windows-specific instructions are accompanied by equivalent Linux/Unix/macOS instructions, or clearly state when a step is platform-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure PowerShell and Azure CLI examples for enabling and managing Azure Monitor logs on HDInsight clusters. However, PowerShell (a Windows-centric tool) is consistently presented before Azure CLI (which is more cross-platform and Linux-friendly) in all code example sections. There are no explicit Linux shell or OS-specific instructions, but the ordering and emphasis on PowerShell may suggest a Windows-first approach. No exclusive use of Windows tools or missing Linux examples were found, as Azure CLI is included throughout.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect the prevalence of Linux-based HDInsight clusters.
Explicitly state that Azure CLI commands work natively on Linux, macOS, and Windows, and that PowerShell is available cross-platform but is traditionally associated with Windows.
Where relevant, add notes or examples for running commands in a Linux shell environment (e.g., bash), especially for common operational tasks.
Consider including a short section on choosing between PowerShell and Azure CLI, highlighting cross-platform compatibility.
Ensure that any OS-specific prerequisites or behaviors (such as file paths, permissions, or agent installation) are documented for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a bias towards Windows/Azure-centric tooling by exclusively referencing Azure SQL Database as the external metastore option, with no mention of open-source or Linux-native alternatives (such as MySQL, PostgreSQL, or MariaDB, which are supported by Apache Hive and Oozie). All configuration steps, screenshots, and instructions are based on the Azure Portal and Azure SQL Database, with no examples or guidance for users who may wish to use non-Microsoft databases or command-line (Linux) tools. There are no PowerShell or Windows command-line examples, but the absence of Linux-native options and the exclusive focus on Azure SQL Database constitutes a form of Windows/Microsoft ecosystem bias.

Recommendations:

Document how to use open-source databases (e.g., MySQL, PostgreSQL, MariaDB) as external metastores for Hive, Oozie, and Ambari, including any limitations or support caveats in HDInsight.
Provide example configuration steps for setting up and connecting to non-Azure SQL Database metastores, including Linux command-line (e.g., mysql, psql) instructions.
Include guidance for configuring firewall/network access for non-Azure databases, possibly running on Linux VMs or on-premises.
Add troubleshooting and backup/restore instructions for open-source database metastores.
Clarify in the documentation whether only Azure SQL Database is supported, or if other databases are possible, and if so, provide parity in documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on using the Azure Portal UI and SQL query editor for configuring Managed Identity authentication, without providing any command-line examples or guidance for Linux users (e.g., Azure CLI, Bash scripting). There is no mention of PowerShell, but the absence of Linux/CLI alternatives and the reliance on portal screenshots and SQL commands may disadvantage users working in Linux-first or automated/scripted environments.

Recommendations:

Add step-by-step instructions for configuring Managed Identity authentication using the Azure CLI, including relevant Bash commands.
Provide examples for automating the process (e.g., using Azure CLI scripts) suitable for Linux environments.
Clarify that the process can be performed from any OS, and explicitly mention Linux compatibility where relevant.
Include references or links to cross-platform tools and documentation (e.g., Azure CLI, az sql commands) alongside portal-based instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation is generally cross-platform, using Azure CLI and bash-style syntax, which is compatible with both Linux and Windows. However, there is a subtle Windows bias: the note about running scripts in Visual Studio Code and PowerShell appears early, and PowerShell-specific advice (adding the $ symbol for variables) is given without any equivalent Linux shell notes. No Linux-specific tools or environments are mentioned, and the only environment-specific advice is for Windows/PowerShell users.

Recommendations:

Include explicit notes or examples for running the scripts in Linux/macOS shells (e.g., bash, zsh), such as variable syntax differences or environment setup.
Mention that the CLI commands work natively in Linux/macOS terminals, not just in PowerShell or Visual Studio Code.
Provide a brief section or note on how to adapt the scripts for PowerShell (e.g., variable assignment differences), rather than implying PowerShell is the default.
Balance environment references by mentioning both Windows and Linux/macOS editors (e.g., Visual Studio Code, GNOME Terminal, Terminal.app) where scripts can be run.
If referencing Visual Studio Code, clarify that it is cross-platform and not exclusive to Windows.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates bias by omitting Linux-specific examples and tools. All example steps focus on using the Azure Portal and Bastion, which are often associated with RDP (a Windows protocol) and do not mention SSH or Linux command-line workflows. There are no Linux-specific instructions or references to common Linux administration patterns (e.g., using SSH, CLI tools, or Linux firewall configuration).

Recommendations:

Add example steps for connecting to Linux VMs using SSH via Azure Bastion, including both portal and CLI workflows.
Include references to Linux-native tools and patterns (e.g., iptables, firewalld, or ufw for network rules).
Provide parity in examples by showing both Windows (RDP) and Linux (SSH) connection scenarios.
Mention Azure CLI and Azure PowerShell equally, and provide command-line examples for both platforms.
Clarify that Bastion supports both RDP (Windows) and SSH (Linux), and show how to use each.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page focuses exclusively on Azure Portal GUI steps and general Azure concepts, without providing any command-line examples. There are no references to Linux tools, CLI commands, or cross-platform automation methods. The absence of Linux (or even Azure CLI) examples, while describing storage setup and management, results in a bias toward Windows-centric workflows, as the Azure Portal is often more familiar to Windows users and less scriptable for Linux automation.

Recommendations:

Add Azure CLI and PowerShell command examples for all major storage setup and configuration steps, ensuring parity between Windows and Linux environments.
Include sample scripts for storage account creation, access control configuration, and encryption verification using both Azure CLI (cross-platform) and PowerShell.
Mention and link to documentation for automating storage setup from Linux shells, not just the Azure Portal.
Explicitly state that all steps can be performed from Linux, macOS, and Windows using the Azure CLI, and provide equivalent instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on Azure-native monitoring tools and workflows, with all step-by-step instructions and UI navigation based on the Azure Portal (a web interface, but often associated with Windows-centric workflows). There are no explicit Windows-only tools or PowerShell examples, but there is also a lack of Linux-specific examples, CLI alternatives, or mention of common open-source monitoring tools outside the Azure ecosystem. The only script example is a Bash script using the Azure CLI, but it is tightly coupled to Azure resources and does not demonstrate Linux-native monitoring practices or integration with non-Azure environments. There is no mention of Linux logging/monitoring tools (e.g., syslog, collectd, Nagios, etc.), nor are there instructions for configuring monitoring on Linux VMs outside of the Azure context.

Recommendations:

Provide parallel examples for both Azure Portal (GUI) and Azure CLI for all setup steps, making it clear that CLI commands work cross-platform (including Linux).
Include examples or references for integrating Azure Monitor, Grafana, and Prometheus with Linux-native monitoring/logging tools (e.g., syslog, collectd, journald, or node_exporter).
Explicitly mention how to configure monitoring agents or exporters on Linux HPC nodes, including installation and configuration steps.
Add a section or examples for monitoring on-premises or hybrid Linux clusters, not just Azure-native resources.
Reference or link to documentation for open-source monitoring tools commonly used in Linux HPC environments, and describe how they can be integrated with Azure monitoring solutions.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page discusses storage migration in HPC environments with a focus on Azure but does not provide any explicit examples or tool references for either Windows or Linux. However, the absence of Linux-specific tools, commands, or examples (such as rsync, scp, or Linux CLI patterns) and the mention of SMB (a Windows-centric protocol) before NFS (a Linux/UNIX-centric protocol) suggest a subtle Windows-first and missing Linux example bias.

Recommendations:

Include explicit Linux-based migration tool examples (e.g., rsync, scp, lftp) alongside any Windows tools.
Provide sample commands or scripts for both Linux (bash) and Windows (PowerShell) environments in quick start sections.
When mentioning protocols, present NFS and SMB in a neutral or alternating order, or explain their relevance to both Linux and Windows environments.
Reference Linux-native automation tools (e.g., Ansible, shell scripts) alongside Terraform and Bicep.
Ensure that best practices and quick start guides address both Linux and Windows use cases equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation presents Active Directory (a Windows-centric directory service) as the first and most detailed option for configuring directory services, with Linux/UNIX options (flat file and LDAP) described afterward. The AD section is more prominent and detailed, and there is no mention of Linux-native tools or examples beyond referencing /etc/passwd and /etc/group files. There are no command-line examples for Linux or Windows, but the ordering and focus suggest a Windows/AD bias.

Recommendations:

Reorder the directory service options to avoid always listing Active Directory first; consider listing LDAP or flat file first, or presenting all options equally.
Expand the flat file and LDAP sections with more detailed configuration steps and troubleshooting tips, matching the depth of the Active Directory section.
Include example commands or scripts for generating and securely transferring /etc/passwd and /etc/group files from Linux systems.
Mention common Linux directory service tools (such as sssd, nsswitch.conf, or openldap) where relevant.
Clarify that both Windows (AD) and Linux/UNIX (flat file, LDAP) directory services are fully supported and provide guidance for mixed environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by exclusively referencing the default NTP server as time.windows.com and using its IP address in firewall rules, without mentioning common Linux/Unix NTP servers (e.g., pool.ntp.org). The instructions for DNS and network configuration are platform-neutral, and all command-line examples use Bash/Linux tools. However, the NTP section's focus on a Windows-centric server and terminology (time.windows.com) may mislead or inconvenience Linux users who typically use other NTP sources.

Recommendations:

Mention alternative NTP servers commonly used in Linux environments (e.g., pool.ntp.org) alongside time.windows.com.
Provide example firewall rules for both time.windows.com and pool.ntp.org, or explain how to substitute the NTP server address as appropriate for the user's environment.
Clarify that the choice of NTP server is flexible and not limited to Windows infrastructure.
Continue to provide Bash/Linux command-line examples, and ensure parity if any PowerShell or Windows-specific commands are added in the future.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes how to create and manage integration environments using the Azure Portal, a web-based GUI. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there any references to Linux-native tools or workflows. This approach implicitly favors Windows users, who are more likely to use GUI-based workflows, and omits parity for users who prefer or require command-line or scriptable solutions, which are common in Linux environments.

Recommendations:

Add step-by-step instructions for creating and managing integration environments using the Azure CLI, which is cross-platform and widely used on Linux.
Include equivalent examples using Azure PowerShell for users who prefer scripting, but ensure Azure CLI examples are presented first or alongside PowerShell.
Provide sample Bash scripts for automating environment creation, demonstrating Linux-friendly automation.
Explicitly mention that all steps can be performed on any OS via the Azure Portal, but highlight and document command-line alternatives for Linux users.
Ensure screenshots and terminology are not exclusively tied to Windows (e.g., avoid referencing only Windows file paths or UI conventions).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes how to associate an ASN with an Azure subscription using the Azure portal, with all instructions and screenshots based on the web interface. There are no command-line examples provided for any platform (Windows, Linux, or macOS), but there is an implicit Windows bias as Azure documentation often defaults to Windows-centric tools or workflows. The absence of any mention of cross-platform command-line tools (such as Azure CLI or Azure PowerShell) or Linux-specific guidance means Linux users are not directly supported in this workflow.

Recommendations:

Add step-by-step instructions for associating an ASN using the Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
Include example commands for both Azure CLI and Azure PowerShell (if relevant), and present Azure CLI examples first or alongside PowerShell to ensure Linux parity.
Explicitly mention that the Azure portal is web-based and platform-agnostic, but also provide links or references to command-line alternatives for users who prefer or require automation or non-GUI workflows.
Where screenshots are used, clarify that the portal experience is the same across operating systems, and consider including terminal screenshots for CLI workflows.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation refers to associating Peer ASN using a guide specifically named 'howto-subscription-association-powershell.md', indicating reliance on PowerShell (a Windows-centric tool) for this operation. There are no equivalent instructions or references for Linux or cross-platform tools (such as Azure CLI or REST API), nor are Linux-specific examples provided.

Recommendations:

Provide equivalent instructions for associating Peer ASN using Azure CLI, which is cross-platform and widely used on Linux.
Include references or links to documentation for performing the same tasks via REST API or Azure Portal, both of which are platform-agnostic.
Ensure that all step-by-step guides and code examples are available for both Windows (PowerShell) and Linux (Azure CLI, Bash) users.
Explicitly mention the availability of cross-platform tools and recommend them where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides cross-platform examples for generating derived device keys (Azure CLI, Windows/PowerShell, Linux/openssl, C#), but the Windows/PowerShell example is presented before the Linux/openssl example. Additionally, the Windows/PowerShell example is more detailed and uses native Windows tools, which may give the impression of a slight preference for Windows environments.

Recommendations:

Present Linux and Windows examples in parallel or alternate their order in different sections to avoid always listing Windows first.
Ensure that Linux examples are as detailed and accessible as their Windows counterparts.
Explicitly state at the beginning of the example section that all major platforms are supported and that equivalent tooling is available.
Consider including a Bash example for macOS, or clarify that the Linux example applies to macOS as well.
Where possible, provide platform-agnostic code (e.g., Python) to further improve parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes configuration steps using the Azure portal (a web GUI), without providing any command-line examples or automation options. There are no references to CLI tools (such as Azure CLI or PowerShell), but also no Linux-specific guidance or parity. The FAQ explicitly states that there is no API support and that configuration can only be done via the Azure portal, which may disadvantage users who prefer or require CLI/automation, especially on Linux systems. There are no PowerShell-specific examples, but the lack of Linux/CLI parity is a notable bias.

Recommendations:

Add equivalent instructions for performing these tasks using the Azure CLI (az), which is cross-platform and widely used on Linux.
Where possible, provide REST API examples or scripts (even if limited), or clarify roadmap for API/CLI support.
Explicitly mention that the Azure portal is web-based and accessible from any OS, but highlight any limitations for Linux users if present.
If PowerShell or Windows tools are not required, clarify this to reassure Linux users.
Monitor for future CLI/API support and update documentation to include Linux-friendly automation options as soon as available.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a bias toward Windows by exclusively referencing the Azure portal (a web-based GUI) for all configuration steps, with no mention of command-line alternatives such as Azure CLI, PowerShell, or REST API. There are no Linux-specific instructions or examples, and the only configuration method mentioned is the Azure portal, which is commonly associated with Windows-centric workflows. Additionally, the FAQ explicitly states that there is currently no API support and that configuration can only be performed via the Azure portal, further limiting options for Linux or automation-focused users.

Recommendations:

Add step-by-step instructions for performing all configuration tasks using Azure CLI, which is cross-platform and widely used on Linux.
If possible, provide REST API examples for automation and parity with non-GUI workflows.
Include PowerShell examples only if they are complemented by equivalent Azure CLI or REST API instructions.
Clarify any platform dependencies for the Azure portal, and ensure that Linux users are not disadvantaged.
Update the FAQ and main content when API or CLI support becomes available, to encourage automation and cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally maintains a cross-platform tone, but in the 'Encryption at rest' section, Windows BitLocker is specifically recommended for Windows, while Linux is mentioned only generically ('Linux has several options for encryption at rest'). No specific Linux tools or examples are provided, and the Windows tool is mentioned by name and linked, giving Windows users a clearer path.

Recommendations:

List specific Linux encryption tools (e.g., LUKS, dm-crypt, eCryptfs) alongside BitLocker, and provide links to their documentation.
Present Linux and Windows options in parallel structure, e.g., 'For Linux, consider [LUKS](https://gitlab.com/cryptsetup/cryptsetup), [dm-crypt](https://wiki.archlinux.org/title/Dm-crypt), or [eCryptfs](https://wiki.archlinux.org/title/Ecryptfs). For Windows, [BitLocker](https://docs.microsoft.com/windows/security/operating-system-security/data-protection/bitlocker) is recommended.'
Where possible, provide example commands or configuration snippets for both Linux and Windows to ensure parity.
Review other sections for opportunities to add Linux-specific guidance or examples, even if only brief, to reinforce cross-platform support.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references a PowerShell function (Get-AduFileHashes in AduUpdate.psm1) as the example for calculating file hashes, but does not provide equivalent Linux or cross-platform command-line examples. No Linux-native tools or scripts are mentioned, and the only tooling guidance is specific to Windows/PowerShell.

Recommendations:

Provide equivalent Linux and cross-platform examples for calculating file hashes, such as using 'sha256sum' or 'openssl dgst -sha256' in Bash.
Mention or link to Linux shell scripts or commands that can generate the required base64-encoded SHA-256 hash.
If referencing a PowerShell script, clarify whether it is cross-platform (PowerShell Core) or Windows-only, and provide alternatives for other platforms.
Ensure that all tooling references are accompanied by platform-agnostic or platform-specific alternatives as appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally aims for cross-platform parity by using cURL, Bash, and Python examples, and explicitly mentions both Linux and Windows environments. However, there is a subtle Windows bias: Windows is mentioned first in environment setup instructions, and Windows-specific tooling (Git Bash) is emphasized for Windows users, with no mention of native Windows command prompts or PowerShell. There are no PowerShell-specific examples, but the guidance for Windows users is to use Git Bash, a third-party tool, rather than native Windows shells. Linux/WSL users are simply told to use Bash, which is native. There are no missing Linux examples or exclusive use of Windows tools, but the documentation does not mention or provide parity for native Windows shells (e.g., Command Prompt or PowerShell), which could be seen as a gap.

Recommendations:

Explicitly provide instructions or notes for users who may want to use native Windows shells (Command Prompt or PowerShell), or clarify why Git Bash is preferred.
Where possible, include PowerShell or Command Prompt equivalents for Bash/cURL commands, or link to documentation that explains how to run these commands in those environments.
Consider mentioning Linux/WSL first in environment setup sections, or alternate the order to avoid the appearance of Windows-first bias.
If recommending third-party tools (like Git Bash) for Windows, provide similar recommendations for Linux users if any non-native tools are required, or clarify that Bash is native on Linux.
Add a brief section explaining cross-platform considerations, including any limitations or differences when running commands on Windows vs. Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page provides instructions primarily through the Azure portal UI and mentions PowerShell as a management option, but does not provide any command-line examples for either Windows (PowerShell) or Linux (Bash/CLI). However, when discussing alternatives to the portal, it lists 'Azure CLI, PowerShell, or service APIs', with PowerShell mentioned before Linux-native tools. There are no explicit Linux/Bash examples or references to Linux-specific tools, which may make Linux users feel less directly supported.

Recommendations:

Provide explicit command-line examples for both Azure CLI (cross-platform) and PowerShell when mentioning alternatives to the portal.
When listing management options, mention Azure CLI before or alongside PowerShell to emphasize cross-platform parity.
Include sample commands for common tasks (such as enabling/disabling public network access) using both Azure CLI and PowerShell.
Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide installation links for each platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by consistently mentioning Windows and its tools (specifically Git Bash and winpty) before Linux/WSL equivalents, and by providing Windows-specific instructions and caveats (such as the need for an extra slash in certificate subjects and the use of winpty for openssl). While Linux/WSL instructions are present and parity is generally maintained, Windows is prioritized in ordering and tool recommendations.

Recommendations:

Alternate the order in which Windows and Linux/WSL instructions are presented, or present Linux first in some sections to balance perceived priority.
When introducing prerequisites and command-line environments, mention Bash on Linux/WSL first, then Git Bash for Windows, to avoid defaulting to Windows-centric language.
Clarify that winpty and the extra slash in certificate subjects are only needed for Git Bash on Windows, and consider grouping these as footnotes or callouts rather than leading the main instructions.
Where possible, provide a unified command example and only note platform-specific differences as exceptions, rather than separate primary/secondary tabs.
Explicitly state that all examples are cross-platform unless otherwise noted, and highlight any differences in a neutral, non-prioritized way.

Create pull request

Bias Types:

⚠️ bash_first

⚠️ windows_shell_note

Summary:

The documentation primarily uses Bash syntax for variable assignment and command examples, with a note indicating that users on Windows CMD or PowerShell should adapt the commands. However, no explicit Windows CMD or PowerShell examples are provided, and Bash is presented as the default environment. There is no exclusive use of Windows tools or patterns, but Linux/Bash is favored in the examples.

Recommendations:

Provide equivalent command examples for Windows CMD and PowerShell alongside the Bash examples, especially for variable assignment and usage.
Include a table or section summarizing syntax differences for key commands (e.g., variable assignment, echoing variables) across Bash, CMD, and PowerShell.
Explicitly mention that the Azure CLI works cross-platform and link to official guidance on using it in different shells.
Consider alternating the order of examples or providing tabs for Bash, CMD, and PowerShell to ensure parity and clarity for all users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a 'Windows-first' bias by exclusively referencing the Azure portal UI for configuration steps and mentioning PowerShell as a management option before the Azure CLI. There are no explicit Linux-specific instructions or CLI examples, and all screenshots and step-by-step guides are based on the Azure portal, which is platform-agnostic but often more familiar to Windows users. Additionally, there are no command-line examples (neither PowerShell nor Bash/CLI), and Linux tooling or workflows are not discussed.

Recommendations:

Add explicit Azure CLI (bash) examples for all configuration steps, especially for setting up private endpoints and managing enrollments.
When listing management options, mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
Include at least one example using Linux-native tools or workflows (e.g., bash scripts, curl, jq) for interacting with DPS and private endpoints.
Provide screenshots or terminal output from cross-platform tools (CLI) in addition to or instead of Azure portal UI.
Clarify that all instructions are cross-platform where possible, and highlight any steps that are platform-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation references both Windows and Linux platforms in the module.json example, but the only explicit platform example with an OS name is 'windows-amd64', while Linux platforms are referenced generically by architecture (e.g., 'amd64', 'arm32v7'). There are no explicit Linux-specific instructions, tools, or examples, and the text mentions Visual Studio and Visual Studio Code (which are available on both platforms, but VS is primarily associated with Windows). There are no PowerShell or Windows-only tool references, but the lack of explicit Linux parity in naming and examples suggests a mild Windows-first bias.

Recommendations:

Add explicit Linux platform keys in the example (e.g., 'linux-amd64') to match the specificity of 'windows-amd64'.
Include a Linux-specific example or scenario, such as referencing a Dockerfile.linux-amd64.
Clarify in the text that the generic architecture keys (e.g., 'amd64') refer to Linux by default, or provide a table mapping platform keys to OS/architecture combinations.
Mention Linux development tools or workflows alongside Visual Studio, such as using VS Code on Linux or command-line Docker builds.
Ensure that any future examples or instructions provide parity for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is generally cross-platform but exhibits subtle Windows bias: Windows devices are mentioned before Linux devices in some places, and there are no explicit Linux-specific command-line examples or instructions. The tutorial assumes use of Visual Studio Code (which is cross-platform), but does not provide any Linux terminal or shell-specific guidance, nor does it mention or show Linux-native tools or patterns. All steps are described in a way that is platform-agnostic, but the lack of explicit Linux examples or troubleshooting tips may disadvantage Linux users.

Recommendations:

When listing device setup options, mention Linux before Windows or give them equal prominence.
Provide explicit Linux shell/terminal command examples where relevant (e.g., for Docker commands, file navigation, permissions).
Include troubleshooting tips or notes for common Linux-specific issues (e.g., Docker permissions, file paths, case sensitivity).
Reference Linux-native tools or patterns where appropriate (e.g., using bash scripts for automation, systemd for service management).
Add screenshots or terminal output examples from Linux environments, not just generic or Windows-centric visuals.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation is generally cross-platform and uses Azure CLI with Bash as the primary environment. However, there is a subtle Windows-first bias: PowerShell is mentioned as an alternative for line continuation syntax, and escaping JSON characters in PowerShell is specifically called out, while Linux/Bash is treated as the default. There are no explicit Linux examples missing, but the documentation assumes familiarity with PowerShell for Windows users and provides tips for them, which is a mild form of Windows-centric bias.

Recommendations:

Provide explicit Linux/Bash and Windows/PowerShell command examples side by side where syntax differs, rather than only mentioning PowerShell as an aside.
Include a table or section summarizing differences in command syntax and escaping for Bash vs. PowerShell, rather than only referencing PowerShell in tips.
Ensure that any tips or troubleshooting steps are equally detailed for both Linux and Windows environments.
Where possible, add examples or notes for MacOS users if there are any platform-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation is generally Linux-focused for device configuration and usage, but there are subtle signs of Windows bias. Specifically, directory and output examples use Windows paths (e.g., 'C:\nested-edge\output'), and the documentation references the Azure portal's Windows VM instructions for opening ports. These Windows elements appear before or instead of equivalent Linux examples, despite the main tutorial targeting Linux devices.

Recommendations:

Provide output directory examples using both Windows (C:\...) and Linux (~/...) paths, or default to Linux paths since the tutorial is Linux-focused.
When referencing Azure portal documentation for opening ports, link to both Windows and Linux VM guides, or use the cross-platform documentation.
Include example commands and outputs for both Windows and Linux environments where relevant, especially in sections that show file system interactions or command-line outputs.
Ensure that any screenshots or code snippets that show file paths or shell prompts are representative of the target OS (Linux in this case), or provide both variants.
Review the documentation for any other subtle Windows-first language or assumptions and adjust to be OS-neutral or Linux-first, given the tutorial's prerequisites.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation focuses on discovery methods in Azure Migrate but does not provide explicit examples or guidance for Linux environments. The guidance sections reference VMware and Hyper-V (the latter being Windows-centric) before mentioning 'physical & public Cloud servers,' which could include Linux but is not stated. There are no Linux-specific tools, commands, or scenarios discussed, and no mention of Linux workloads or discovery nuances.

Recommendations:

Include explicit references to Linux environments in the guidance sections, such as 'For Linux-based physical servers, follow these steps...'.
Provide examples or notes on discovering Linux workloads (e.g., Apache, NGINX, PostgreSQL) alongside the existing SQL Server and ASP.NET examples.
Clarify that the 'physical stack of appliance' supports Linux servers and describe any Linux-specific prerequisites or considerations.
Add Linux-specific discovery and migration scenarios, including any required agents or tools.
Ensure parity in workload lists by mentioning both Windows and Linux application types where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates a mild Windows bias by referencing PowerShell syntax and usage before mentioning Linux/Bash alternatives, and by providing tips that prioritize PowerShell users. However, the main command-line examples use Azure CLI with Bash syntax, and there are no exclusive Windows-only tools or missing Linux examples. The documentation does not provide Linux-specific troubleshooting or examples beyond Bash, and it assumes familiarity with Azure Portal (which is cross-platform but often associated with Windows environments).

Recommendations:

Provide explicit Linux command-line examples where relevant, especially for file path manipulations or troubleshooting.
Include notes or sections for common Linux shell environments (e.g., zsh, fish) if command syntax may differ.
Balance PowerShell tips with equivalent Bash/Linux shell tips, and avoid placing Windows/PowerShell guidance before Linux/Bash guidance unless usage data supports it.
Add troubleshooting steps or examples for both Windows and Linux environments, especially for device-side configuration and log file access.
Clarify that Azure Portal and Azure CLI are cross-platform, and provide links to Linux-specific installation or usage guides where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation is primarily focused on Linux (Ubuntu) for the device setup and update process, providing detailed shell (bash) commands and Linux-specific instructions. However, there is a notable instance where PowerShell is referenced as the default tool for copying files to the VM (using scp), and the instructions assume the user is running PowerShell on their computer. There are no explicit Linux desktop or cross-platform alternatives mentioned for this step, and the only desktop-side example is Windows-centric. No Windows-only tools or patterns dominate, but the assumption of PowerShell as the user's shell introduces a subtle Windows-first bias.

Recommendations:

Provide explicit cross-platform instructions for file transfer (e.g., mention using scp from Linux/macOS terminal, or alternatives like WinSCP for Windows).
Avoid assuming PowerShell as the default shell; instead, offer both Windows (PowerShell/CMD) and Linux/macOS (terminal/bash) command examples where relevant.
Where desktop-side actions are required, clarify that the steps apply to all platforms, or provide platform-specific alternatives.
Consider including a note or table summarizing equivalent commands/tools for Windows, Linux, and macOS users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation generally maintains cross-platform parity, especially in the Azure CLI section, which explicitly references Bash and provides guidance for PowerShell users. However, there is a subtle Windows bias in the 'Import using the Device Update APIs' section, where PowerShell modules are mentioned as a sample method, and PowerShell is listed first among supported platforms. Additionally, in the 'Prerequisites' and 'Portal' sections, there is a slight preference for Microsoft Edge (a Windows-centric browser), and Windows-style screenshots are used throughout.

Recommendations:

When mentioning PowerShell modules, also highlight equivalent Linux/macOS scripting options or provide Bash/Python script samples for parity.
In the API/programmatic section, list cross-platform SDKs and tools before or alongside PowerShell, and clarify that PowerShell is available on Linux/macOS as well as Windows.
Where browser support is mentioned, list browsers in alphabetical order or mention Chrome/Firefox/Safari alongside Edge to avoid Windows-first perception.
Consider including at least one screenshot or example from a Linux environment (e.g., Azure CLI in a Linux terminal) to visually reinforce cross-platform support.
Explicitly state that all CLI and API methods are supported equally on Linux, macOS, and Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation references the Windows Update platform as the foundation for Device Update, highlighting its reliability and global scale. This mention appears before any Linux-specific update frameworks or tools are discussed. While the document does mention Linux support, Yocto images, and open-source agent extensibility, it does not provide Linux-first or Linux-equal examples, nor does it mention Linux update tools (e.g., apt, rpm, swupd) as foundational. There are no explicit PowerShell or Windows command examples, but the underlying bias is present in the framing and tool references.

Recommendations:

Acknowledge and briefly describe Linux-native update mechanisms (e.g., apt, rpm, swupd) and how Device Update integrates with or differs from them.
Balance the mention of Windows Update platform by also referencing established Linux update frameworks or open-source OTA solutions.
Provide explicit Linux command-line examples or references where relevant, especially in sections discussing agent integration and update workflows.
Ensure that Linux and Windows are presented with parity in foundational technology references, not just in agent support.
Consider adding a section or callout highlighting Linux-first workflows or best practices for Device Update integration.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by referencing Windows-specific scenarios (such as end of support for Windows OS and SQL versions) and omitting explicit mention or examples for Linux workloads, tools, or migration considerations. There are no Linux-specific migration examples, nor are Linux tools or patterns discussed. The migration strategies and cost analyses are described in a way that implicitly assumes Windows-centric environments, with no parity for Linux-specific scenarios.

Recommendations:

Explicitly mention both Windows and Linux workloads throughout the documentation, including in feature descriptions and migration strategies.
Provide examples or notes for Linux server discovery, assessment, and migration, including any differences in process or tooling.
Highlight cost and modernization considerations for Linux workloads (e.g., migration to Azure Linux VMs, Azure Container Instances, or AKS for Linux).
Reference end-of-support scenarios for popular Linux distributions alongside Windows, where relevant.
Ensure screenshots and UI references show a mix of Windows and Linux workloads to reinforce cross-platform support.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides only Windows-based examples for virtual machine images (specifically 'Windows Server 2022 Datacenter') and does not mention or demonstrate Linux-based alternatives. There are no examples, screenshots, or instructions for creating or using Linux VMs, nor are Linux-specific considerations or options discussed. This presents a Windows-first bias and omits Linux parity in the tutorial workflow.

Recommendations:

Include Linux-based virtual machine image options (e.g., Ubuntu, CentOS) alongside Windows in the 'Create a new lab' section.
Provide example walkthroughs and screenshots for creating a lab using a Linux VM image.
Mention any Linux-specific configuration steps or differences, such as SSH key setup or default credentials.
Ensure troubleshooting and next steps sections address both Windows and Linux VM scenarios.
Clarify that both Windows and Linux VMs are supported by Azure Lab Services, and link to relevant documentation for each.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation references Azure PowerShell as a configuration method alongside Azure CLI and the Azure portal, which can indicate a Windows bias, especially since PowerShell is traditionally associated with Windows environments. Additionally, the order of listing (portal, CLI, PowerShell) puts PowerShell before any mention of Linux-native tools or workflows. There are no explicit Linux-only examples or mentions of Linux-specific tools, and no indication that the examples or instructions are cross-platform.

Recommendations:

Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
If referencing PowerShell, note that PowerShell Core is also available on Linux and macOS, or provide equivalent Bash shell commands where appropriate.
Add explicit Linux/macOS instructions or examples, especially for command-line configuration steps.
Consider reordering the configuration methods to list the Azure CLI before PowerShell, as CLI is more commonly used in Linux environments.
Where possible, include notes or callouts about cross-platform compatibility for all tools and SDKs mentioned.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows 11 Pro as the virtual machine image in the example, and by only describing remote desktop (RDP) connections, which are primarily associated with Windows environments. There are no examples or instructions for creating labs with Linux VM images, nor are there any Linux-specific configuration or connection instructions. The documentation does not mention or show parity for Linux users or scenarios.

Recommendations:

Provide examples that use both Windows and Linux VM images when creating a lab, or explicitly mention that Linux images are supported.
Include instructions or screenshots for connecting to Linux-based lab VMs, such as using SSH, in addition to RDP for Windows.
When listing software installation examples, include popular Linux tools or editors (e.g., VS Code, vim, gcc) and show how to install them on Linux.
Clarify in the prerequisites or relevant sections that both Windows and Linux environments are supported, and link to documentation for both.
Ensure that any step or screenshot that is OS-specific is accompanied by a Linux equivalent, or at least a note about Linux usage.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and PowerShell examples for deploying Resource Manager templates, but PowerShell is given equal prominence to CLI, and Windows-style file paths (e.g., my\path\to\template.json) are used in examples. There are no explicit Linux shell or Bash-specific examples, and PowerShell is highlighted as a primary method alongside CLI, which may indicate a slight Windows bias. However, the use of Azure CLI, which is cross-platform, helps mitigate this bias.

Recommendations:

Use POSIX-style (Linux/macOS) file paths (e.g., my/path/to/template.json) in CLI examples, or provide both Windows and Linux path variants.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
If PowerShell is shown, consider also showing Bash or sh equivalents for common tasks, especially for scripting or automation.
Clarify in the prerequisites or deployment sections that all steps can be performed on Linux, macOS, or Windows, and link to platform-specific setup guides if needed.
Where file uploads or downloads are discussed (e.g., in Azure Cloud Shell), mention any differences in file navigation or commands between Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation references Windows-specific tools (PowerShell) alongside cross-platform options (Azure CLI and portal), but lists PowerShell before mentioning management APIs. There are no explicit Linux or Bash examples, and no mention of Linux-specific tools or shell environments. The documentation does not provide parity in example commands or tooling guidance for Linux users, potentially making it less approachable for non-Windows users.

Recommendations:

When listing configuration options, mention cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell), or group them together without preference.
Explicitly state that Azure CLI and the portal are cross-platform and suitable for Linux, macOS, and Windows.
Provide example commands for both Azure CLI (Bash/shell) and PowerShell where appropriate.
Include a note or section highlighting Linux compatibility and any Linux-specific considerations.
Ensure parity in code snippets and walkthroughs for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation assumes a Windows development environment throughout, with all command-line examples (e.g., setting environment variables, running commands) shown only in Windows CMD syntax. There are no explicit Linux or cross-platform shell equivalents provided for key steps such as setting environment variables or running the app. The instructions and screenshots reference Windows tools and patterns first, and do not offer parity for Linux or macOS users.

Recommendations:

For every command-line example (e.g., setting environment variables, running npm commands, git commands), provide both Windows CMD and Linux/macOS (bash/zsh) equivalents, clearly labeled.
In the 'Configure environment variables' section, add Linux/macOS export commands (e.g., export IotHubConnectionString=...) alongside the Windows set commands.
When referencing file navigation or editors, use neutral language (e.g., 'your preferred editor') and avoid screenshots or instructions that are Windows-specific unless alternatives are also shown.
Where App Service plans are discussed, give equal prominence to Linux hosting options, not just mentioning them as an aside.
Add a note or table at the start of the tutorial summarizing which commands to use for Windows vs. Linux/macOS.
Include troubleshooting steps relevant to Linux/macOS environments (e.g., checking environment variables, npm/node issues on Unix-like systems).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily describes Azure IoT Hub monitoring using the Azure portal and platform-agnostic tools (Kusto queries, Log Analytics, Event Grid), with no explicit command-line examples. However, in the 'SDK version in IoT Hub logs' section, all sample SDK version strings shown are from Windows environments (e.g., 'Windows_NT', 'Microsoft Windows'), and no Linux or macOS examples are provided. There are no PowerShell or Windows-specific tool instructions, but the absence of Linux/macOS examples and the exclusive use of Windows in SDK version samples indicate a subtle Windows-first bias.

Recommendations:

Include SDK version log examples from Linux and macOS environments (e.g., show sample sdkVersion strings from devices running on Ubuntu, Debian, or macOS).
When showing sample log outputs or properties, provide a mix of OS platforms to reflect cross-platform usage.
If referencing tutorials or external samples (such as Event Hubs client samples), ensure that links or instructions are available for both Windows and Linux environments.
Explicitly mention that the monitoring and logging features are platform-agnostic, and provide guidance or screenshots from non-Windows environments where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally maintains cross-platform parity by focusing on the Azure CLI and Cloud Shell, which are available on both Windows and Linux. However, there are subtle signs of Windows bias: Windows tools (e.g., Windows Terminal) are mentioned before Linux equivalents, and PowerShell is given special attention, including dedicated notes and command variants, while Linux shells are not similarly highlighted. There are no Linux-specific examples or troubleshooting notes, and the documentation does not mention Linux terminals or tools by name.

Recommendations:

When referencing local CLI usage, mention both Windows Terminal and common Linux terminals (e.g., GNOME Terminal, Konsole, xterm) to reinforce cross-platform support.
Provide equal attention to Bash and PowerShell, including troubleshooting notes or command variants for Bash where relevant (not just PowerShell).
Add explicit statements or notes confirming that all examples work identically on Linux, macOS, and Windows, or highlight any differences.
Include screenshots or references to Linux environments where possible, not just Windows-based visuals.
If mentioning PowerShell-specific syntax (e.g., JSON escaping), consider also noting any Bash-specific tips or common issues.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation is generally cross-platform and uses OpenSSL (a cross-platform tool) and Bash shell commands for most certificate operations, which is favorable for Linux users. However, in the 'Verify certificate manually after upload' section, the PowerShell script option is listed first, and the Bash script is mentioned second. This ordering, along with explicit mention of PowerShell, subtly prioritizes Windows workflows. There is also a reference to a PowerShell script 'supplied by Microsoft' without a corresponding mention of a native Linux tool or parity in script support.

Recommendations:

List Bash/Linux examples before or alongside PowerShell/Windows examples to avoid implying Windows is the primary or preferred platform.
Ensure that any scripts or tools supplied by Microsoft for Windows (e.g., PowerShell scripts) have equivalent, well-documented Linux/Bash versions, and mention them equally.
Explicitly state that all steps can be performed on both Windows and Linux, and clarify any platform-specific requirements.
Where possible, provide cross-platform scripts (e.g., in Python or as Docker containers) to further reduce platform bias.
Review future documentation to ensure that Windows-specific tools or workflows are not given priority unless there is a technical reason.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows by exclusively referencing Fiddler (a Windows-centric tool) for web debugging in the template testing section, and by not mentioning or providing examples for Linux-compatible alternatives. There are no PowerShell or Windows command-line examples, but the only explicit tooling guidance is Windows-focused. No Linux tools or cross-platform alternatives are suggested, and no Linux-specific instructions or screenshots are provided.

Recommendations:

Mention and provide examples for Linux-compatible web debugging tools, such as mitmproxy or Charles Proxy, alongside Fiddler.
Include instructions or example scripts for using these alternative tools to test templates, ensuring parity for Linux and macOS users.
Add a note clarifying that Fiddler is just one option, and that any web debugging tool capable of request interception and modification can be used.
Wherever screenshots or step-by-step instructions are given for a tool, consider providing equivalent guidance for a popular Linux alternative.
Review other sections for implicit assumptions about the user's OS (e.g., file paths, browser recommendations) and clarify cross-platform compatibility where relevant.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides instructions for using the Azure Portal (web-based, cross-platform) and Azure CLI (cross-platform), but the only code sample for simulating device messages is a .NET console application (SimulatedDevice), which is Windows-centric by default. There are no examples or guidance for running the simulated device on Linux or using other common cross-platform languages/tools (such as Python). The documentation also references editing and running a C# file (Program.cs), which assumes a Windows development environment or familiarity with .NET tooling.

Recommendations:

Provide alternative simulated device code samples in a cross-platform language such as Python or Node.js, and include instructions for running them on Linux.
Explicitly mention that the .NET sample can be run on Linux using .NET Core, and provide installation instructions or a link.
Add a note or section for Linux/macOS users, clarifying any differences or prerequisites for running the sample code.
Consider including Bash shell examples alongside Azure CLI commands, especially for variable setting and environment preparation.
Reference or link to official cross-platform SDKs and samples for Azure IoT Hub, highlighting their compatibility with Linux.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a bias towards Windows by only providing .NET (C#) sample code, which is most commonly associated with Windows environments, and by referencing Azure IoT Explorer, a GUI tool that is only officially available for Windows and Mac. There are no Linux-specific code samples, nor are there instructions for sending device telemetry using cross-platform or Linux-native tools (such as Python, Node.js, or command-line utilities like mosquitto_pub). The tutorial assumes the user is comfortable with .NET and does not mention or link to equivalent SDKs or instructions for Linux users.

Recommendations:

Provide sample code and instructions using cross-platform SDKs, such as Python or Node.js, which are popular and well-supported on Linux.
Include explicit instructions or examples for sending device telemetry using command-line tools available on Linux (e.g., mosquitto_pub for MQTT).
Mention and link to the Azure IoT SDKs for other languages (Python, JavaScript, Java, C) and show how to run the sample on Linux.
Clarify the availability of Azure IoT Explorer on Linux, and if not available, suggest alternative methods (such as using the Azure CLI or other open-source tools) for monitoring device messages.
Add a note in the prerequisites and sample code sections that the tutorial is cross-platform, and provide any necessary Linux-specific setup steps (e.g., installing .NET Core on Linux, or using a different SDK).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by consistently referencing Windows-specific tools and workflows before their Linux equivalents. For example, it recommends using Git Bash (a Windows tool) to access OpenSSL, and provides Windows-specific instructions and notes before Linux ones. The documentation assumes a Windows environment in several prerequisite and setup steps, and only later provides Linux alternatives. However, both Windows and Linux command examples are ultimately provided, and OpenSSL (a cross-platform tool) is used throughout.

Recommendations:

Present Linux and Windows instructions in parallel or in a neutral order, rather than listing Windows first.
In the prerequisites, clarify that OpenSSL and Git are available natively on Linux/macOS, and that Git Bash is primarily needed for Windows users.
Avoid assuming the use of Git Bash for all users; suggest native terminals for Linux/macOS.
Explicitly mention macOS support and provide corresponding instructions where applicable.
Where possible, use cross-platform language and tools, and avoid Windows-centric terminology unless necessary.
In notes and recommendations, avoid defaulting to Windows-specific advice (e.g., 'unless you're familiar with OpenSSL and it's already installed on your Windows machine...'). Instead, provide equivalent guidance for all platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page for Azure IoT explorer subtly favors Windows by mentioning Windows-specific launch instructions (e.g., launching from the Start menu) without providing equivalent details for Linux or macOS. There are no explicit Linux or macOS installation or usage examples, nor are there references to platform-specific behaviors or troubleshooting for non-Windows users.

Recommendations:

Add explicit installation and launch instructions for Linux and macOS platforms, including how to run the application from the terminal or application menu.
Include screenshots or examples from Linux and macOS environments to demonstrate parity.
Mention any platform-specific prerequisites or troubleshooting steps for Linux/macOS users.
Ensure that all steps and features described are clearly applicable to all supported platforms, or note any differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias, primarily by referencing the Az PowerShell module as the only command-line SDK example and listing it before mentioning .NET and Python SDKs. There are no explicit Linux CLI (e.g., Azure CLI) examples or references, and no mention of Linux-specific tools or workflows. While the page does mention improved auto-shutdown for both Windows and Linux, the SDK/tooling focus is Windows-centric.

Recommendations:

Include Azure CLI examples alongside or before PowerShell examples when discussing SDKs or automation.
Explicitly mention Linux compatibility and provide Linux command-line usage patterns where relevant.
Reference cross-platform tools (e.g., Azure CLI) in addition to Windows-centric tools (e.g., PowerShell).
Ensure that any SDK or automation guidance is not presented as PowerShell-first; consider listing Python, .NET, and CLI options equally.
Add links or notes about managing Azure Lab Services from Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally presents Windows tools and workflows before Linux equivalents, particularly in the section about creating VHDs, where Windows Hyper-V is mentioned as the default tool for both Windows and Linux images. There is a notable absence of Linux-native tooling (such as KVM, qemu-img, or VirtualBox) for creating VHDs, and the only example of on-premises image creation references Windows Hyper-V. While both Windows and Linux are acknowledged throughout, Windows-centric tools and patterns are prioritized or exclusively mentioned in some key steps.

Recommendations:

When describing how to create VHDs for custom images, include Linux-native tools such as KVM, qemu-img, or VirtualBox alongside Hyper-V, with links to relevant documentation.
Where steps differ for Windows and Linux, provide parallel, side-by-side instructions or clearly separate sections for each OS.
Avoid presenting Windows tools as the default or only option for cross-platform workflows; instead, introduce both Windows and Linux options together.
Consider adding a summary table or matrix showing supported tools and workflows for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page, while focused on Linux custom images, presents Windows-centric links and examples first when describing how to create an Azure VM. Specifically, the instructions for creating a VM reference Windows portal, PowerShell, and CLI documentation before any Linux-specific equivalents, and do not provide direct Linux-focused examples or links. This may confuse or inconvenience Linux users and gives the impression of a Windows-first approach.

Recommendations:

Provide Linux-specific links and examples alongside or before Windows options when describing how to create an Azure VM (e.g., link to /azure/virtual-machines/linux/quick-create-portal and /azure/virtual-machines/linux/quick-create-cli).
Ensure that all example commands, scripts, and references are either Linux-specific or presented in both Windows and Linux variants.
Review the documentation for any other Windows-centric language or assumptions and revise to ensure Linux users are equally supported.
Consider adding a dedicated section or callout for Linux users to clarify any differences in process or tooling.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell and Az.LabServices cmdlets as next steps, without mentioning equivalent CLI or Linux-native tools. While the main content is cross-platform Python, the only administrative tooling highlighted is PowerShell, which is traditionally associated with Windows environments.

Recommendations:

Include references to Azure CLI (az labservices) commands as alternatives to PowerShell cmdlets for managing lab plans and resources.
Explicitly state that the Python code examples are cross-platform and can be run on Linux, macOS, and Windows.
Provide links to documentation for both Azure CLI and PowerShell, ensuring Linux users are equally supported.
If mentioning PowerShell, clarify that PowerShell Core is available cross-platform, or provide Bash/CLI equivalents where possible.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a mild Windows bias by exclusively referencing Microsoft-centric tools and ecosystems (e.g., Microsoft Excel for CSV editing, Microsoft Entra, Teams, and Office 365) and by mentioning Microsoft tools before any alternatives. There are no explicit Linux or cross-platform command-line examples, and the workflow assumes use of Microsoft products. However, there are no PowerShell-specific instructions or CLI commands, and the process is largely web-based, which mitigates some potential bias.

Recommendations:

When mentioning CSV file creation, suggest cross-platform tools such as LibreOffice Calc, Google Sheets, or command-line utilities (e.g., awk, sed) alongside Microsoft Excel.
Clarify that any text editor (including Linux-based editors like nano, vim, or gedit) can be used to create or edit CSV files.
If possible, provide CLI or script-based examples for user management that work on both Windows and Linux (e.g., using Azure CLI or REST API).
Explicitly state that the Azure Lab Services website and its features are accessible from any modern browser on any OS.
Include references or links to documentation for Linux/macOS users where relevant, especially for tasks like CSV manipulation or email sending.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page consistently refers to Windows-specific disk naming conventions (C: and D: drives) when describing OS and temporary disks, without mentioning Linux equivalents (such as / or /mnt). There are no Linux-specific examples or terminology, and no mention of Linux command-line tools or patterns. The only command-line automation examples provided are via PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling.

Recommendations:

Include Linux disk naming conventions (e.g., '/' for OS disk, '/mnt' or '/mnt/resource' for temporary disk) alongside Windows examples when discussing disk persistence.
Provide Linux-specific or cross-platform examples for command-line automation, such as using Azure CLI or Bash scripts, in addition to PowerShell.
Explicitly state that the instructions apply to both Windows and Linux VMs, and clarify any differences in behavior or terminology.
Where screenshots or UI references use Windows-centric language, consider adding notes or alternative screenshots for Linux users if the experience differs.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by presenting environment-specific instructions (such as checking pip installation) that mention Windows and Mac, but do not reference Linux explicitly. Additionally, there are no Linux-specific examples or terminal commands, and the order of instructions and terminology often assumes a Windows or Mac environment. While the Azure CLI is cross-platform, the lack of explicit Linux guidance or examples may make Linux users feel less directly supported.

Recommendations:

Include explicit Linux instructions and examples alongside Windows and Mac, especially in sections about checking pip installation and running CLI commands.
Add Linux-specific terminal commands and troubleshooting steps where relevant (e.g., using apt, yum, or other package managers for pip installation).
When referencing command prompts or terminals, clarify that the instructions apply to all platforms, or provide separate tabs/sections for Windows, Mac, and Linux.
Review all environment setup steps to ensure Linux users are not required to infer steps from Windows/Mac instructions.
Consider adding a table or section summarizing platform-specific setup steps for Windows, Mac, and Linux.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page does not provide explicit Windows-only examples or mention Windows-specific tools directly. However, there is a subtle bias in the examples and tooling recommendations: all code samples and GitHub references use C#/.NET (e.g., ASP.NET, Swashbuckle, TRex), which are traditionally more common in Windows environments. There are no Linux-specific examples, nor are there references to Linux-native frameworks, deployment patterns, or tools. The focus on Azure App Service and .NET-centric tools may implicitly favor Windows developers, even though cross-platform support exists.

Recommendations:

Include example implementations using popular Linux-first stacks (e.g., Flask for Python, Express for Node.js, Spring Boot for Java) alongside .NET examples.
Reference Linux-native tools for OpenAPI/Swagger generation (e.g., Swagger CLI, openapi-generator) in addition to Swashbuckle and TRex.
Add deployment guidance for Linux-based hosting environments (e.g., Azure App Service for Linux, Docker containers, or Azure Functions on Linux).
Ensure that code samples and GitHub references include at least one non-.NET, non-Windows-centric example.
Explicitly state that all patterns and recommendations apply equally to Linux-hosted APIs and provide links to relevant Linux documentation where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing 'App Service Environment v3 (Windows plans only)' as the only supported environment for Standard logic apps, and by exclusively using the Azure portal (a web-based GUI) for all examples and instructions. There are no references to Linux-specific environments, tools, or command-line alternatives (such as Azure CLI, PowerShell, or Bash scripts), nor are there any examples or guidance for Linux users. The documentation assumes users are working in environments compatible with Windows plans and the Azure portal, potentially excluding Linux-native workflows or automation.

Recommendations:

Clarify support for Linux-based App Service plans for Standard logic apps, or explicitly state if only Windows plans are supported.
Provide equivalent instructions and examples for Linux users, such as using Azure CLI or ARM templates, in addition to Azure portal steps.
Include notes or sections on how to perform relevant tasks (such as uploading schemas, configuring agreements, or managing resources) using cross-platform tools.
If certain features are Windows-only, clearly indicate this and suggest alternative approaches for Linux users where possible.
Add references to automation and scripting options (e.g., Bash, Azure CLI) for users who prefer or require non-GUI workflows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments by exclusively referencing the Azure portal and KuduPlus (with CMD shell) for file editing and configuration, which are Windows-centric tools. There are no examples or instructions for performing equivalent tasks using Linux tools, CLI, or cross-platform approaches. The use of 'CMD' in KuduPlus and the absence of Linux shell or Azure CLI/PowerShell alternatives further reinforce this bias.

Recommendations:

Provide alternative instructions for editing files and configuring settings using cross-platform tools such as Azure CLI, Azure Cloud Shell (Bash), or direct SSH access.
Include examples for managing the host.json file using Linux shell commands (e.g., nano, vi, or echo/cat for editing JSON files).
Mention that KuduPlus offers both CMD and Bash shells, and show how to use the Bash shell for Linux users.
Where possible, add Azure CLI commands for enabling Health Check and updating configuration, so users on any OS can follow along.
Ensure screenshots and step-by-step instructions are not limited to Windows interfaces or terminology.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently lists the Azure portal, Azure PowerShell, Azure CLI, and REST API as migration options, but always mentions Azure PowerShell (a Windows-centric tool) before Azure CLI (cross-platform). No explicit examples or command snippets are provided for either PowerShell or CLI, but the ordering may suggest a Windows-first approach. There are no Linux-specific instructions, examples, or references, and Visual Studio (primarily a Windows IDE) is mentioned for template management, with no mention of cross-platform alternatives like VS Code.

Recommendations:

Alternate the order of Azure PowerShell and Azure CLI when listing options, or list Azure CLI first to reflect its cross-platform nature.
Provide explicit example commands for both Azure PowerShell and Azure CLI, ensuring parity and clarity for Linux users.
Mention and provide instructions for using Visual Studio Code (VS Code) as a cross-platform alternative to Visual Studio for managing and deploying ARM templates.
Add notes or sections highlighting any platform-specific considerations, especially for Linux/macOS users.
Ensure that any references to tools or workflows (such as exporting templates) include cross-platform options and not just Windows-centric tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page exhibits a mild Windows bias by referencing 'Windows plan' multiple times and only mentioning Windows-based hosting options when discussing zone redundancy. There are no Linux-specific examples, nor is there mention of Linux-based plans or parity in the creation process. The screenshots and instructions focus solely on the Azure portal experience, which is platform-agnostic, but the explicit references to 'Windows plan' without mention of Linux equivalents suggest a Windows-first perspective.

Recommendations:

Explicitly mention both Windows and Linux hosting options where applicable, such as 'Windows or Linux plan' instead of just 'Windows plan'.
Clarify whether zone redundancy is supported for both Windows and Linux plans, and provide guidance for both.
If there are differences in enabling zone redundancy for Linux-based logic apps, include those steps or note any limitations.
Add examples or notes for users deploying logic apps on Linux-based App Service plans.
Review screenshots and instructions to ensure they are not implicitly favoring Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias, most notably by referencing 'Azure App Service Environment v3 (Windows plans only)' multiple times before mentioning any cross-platform or Linux options. There is also a lack of explicit mention of Linux-based hosting or development environments, and no Linux-specific tools or instructions are provided. However, the documentation does not rely heavily on PowerShell or Windows-only CLI tools, and most instructions are platform-agnostic (Azure Portal, VS Code, Azure CLI).

Recommendations:

Explicitly mention Linux-based hosting options (such as Linux App Service plans) where applicable, or clarify if they are not supported.
If certain features are Windows-only (e.g., ASE v3), provide equivalent Linux options or clearly state the limitation.
Include examples or notes for Linux users, such as using Bash with Azure CLI, or developing on Linux-based VS Code.
Where documentation references 'Windows plans only', consider adding a parallel statement about Linux support or lack thereof.
Ensure parity in tool recommendations (e.g., if Azure PowerShell is mentioned, also mention Bash/Azure CLI for Linux).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ macos_first

Summary:

The documentation provides explicit instructions for macOS but does not mention or provide examples for Linux or Windows. There is a notable absence of Linux-specific guidance, which may hinder Linux users. No Windows or PowerShell-specific tools or patterns are present, nor is there a 'Windows-first' ordering, but the omission of Linux examples is a bias.

Recommendations:

Add a dedicated section or include instructions for Linux users, ensuring parity with the macOS instructions.
If the steps are identical for Linux and macOS, clarify this explicitly to reassure Linux users.
Consider providing Windows instructions if relevant, or state clearly if the process is not supported or differs on Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation shows mild Windows bias by using the 'del-cli' tool in the npm build script, which is a Windows-centric utility for deleting files/folders. While the rest of the instructions and shell commands are Unix-like (bash), the inclusion of 'del-cli' and the lack of explicit Linux/macOS alternatives or notes may cause confusion or friction for non-Windows users. However, the majority of the examples use bash syntax and Linux-style paths, and there are no PowerShell examples or exclusive references to Windows-only tools beyond 'del-cli'.

Recommendations:

Replace 'del-cli' with a cross-platform alternative such as 'rimraf' in the npm build script, or provide separate instructions/scripts for Windows and Linux/macOS environments.
Explicitly mention that the build instructions and shell commands are intended for Unix-like systems, and provide Windows (cmd/PowerShell) equivalents where appropriate.
Audit all CLI tool usage in scripts for cross-platform compatibility and document any OS-specific requirements or alternatives.
Add a note in the prerequisites or build section clarifying any differences in commands or tools between Windows and Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation shows subtle Windows bias: file paths in the Azure CLI example use Windows-style (c:/certs/...), and there are no Linux path examples or notes for Linux users. While OpenSSL is mentioned as required for both Windows and Linux, the CLI usage examples only reflect Windows conventions.

Recommendations:

Provide both Windows and Linux file path examples in CLI commands (e.g., 'c:/certs/member0_cert.pem' and '/home/user/certs/member0_cert.pem').
Add a note clarifying that file paths should be adapted for the user's OS.
Explicitly mention that all CLI commands work on both Windows and Linux, and provide OS-agnostic or dual examples where file paths are shown.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation mentions both Windows and Linux in the prerequisites for OpenSSL, but does not provide any explicit Linux-specific instructions or examples in the visible content. There is a section for Mac instructions, but no equivalent for Linux. The ordering of 'Windows or Linux' in the prerequisites may also subtly prioritize Windows.

Recommendations:

Add explicit Linux instructions or examples alongside the Mac instructions, especially for command-line operations or environment setup.
Ensure that any included snippets or referenced files (such as 'service-identity.md' or 'deploy-update-application.md') contain Linux-specific guidance if they contain platform-specific steps.
Consider reordering mentions to 'Linux or Windows' or simply 'Windows, Linux, or Mac' to avoid subtle prioritization.
If there are any scripts or commands, provide both Windows (PowerShell/CMD) and Linux (bash) variants.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by exclusively referencing the Azure portal (a web UI) and Azure CLI, with no mention of Linux-specific tools or workflows. While the CLI and curl examples are cross-platform, the absence of Linux shell-specific guidance or alternative Linux-native tools (such as bash scripting or environment variable handling) may disadvantage Linux users. There are no PowerShell-specific commands, but the overall workflow assumes familiarity with Azure's web and CLI tools, which are more commonly used in Windows-centric environments.

Recommendations:

Explicitly state that the Azure CLI and curl commands work on Linux, macOS, and Windows, and provide any necessary installation instructions for Linux users.
Include Linux shell scripting examples for automating token retrieval and API calls (e.g., using bash scripts or environment variables).
Mention how to install and use Azure CLI on Linux, including package manager commands (e.g., apt, yum).
If referencing the Azure portal, clarify that it is a web-based interface accessible from any OS.
Add troubleshooting tips for common Linux-specific issues (e.g., permissions, environment setup).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Azure portal and Microsoft Entra (formerly Azure AD) workflows, with all instructions and screenshots based on the Azure web UI. There are no references to command-line tools, scripting, or cross-platform methods (such as CLI, REST API, or Terraform), and no mention of Linux or non-Windows environments. This creates an implicit Windows/Microsoft ecosystem bias, as users on Linux or those preferring automation/scripting are not provided with equivalent guidance.

Recommendations:

Include CLI-based instructions (e.g., using Azure CLI or PowerShell) alongside portal steps, and ensure Azure CLI examples are provided before or alongside PowerShell.
Add REST API or Terraform examples for automating Grafana Team Sync configuration, which are platform-agnostic and suitable for Linux users.
Explicitly mention that all steps can be performed from any OS with a web browser, and clarify any OS-specific requirements if present.
Provide links or references to documentation on managing Microsoft Entra groups and Azure Managed Grafana from Linux environments.
If possible, include a section on integrating with non-Microsoft identity providers or open-source alternatives for broader applicability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently references Windows-centric virtualization platforms (VMware, Hyper-V) and Windows-based workloads (SQL Server, IIS/ASP.NET) without providing equivalent examples or guidance for Linux-based environments, workloads, or tools. There are no explicit Linux migration scenarios, tools, or troubleshooting steps, and Linux is not mentioned as a source OS or workload type, leading to a Windows-first and missing-Linux-example bias.

Recommendations:

Include explicit references to Linux servers as supported source environments in assessment scenarios.
Add examples and troubleshooting steps for common Linux workloads (e.g., Apache, MySQL, PostgreSQL) in addition to Windows workloads (IIS, SQL Server).
Mention Linux-specific considerations for performance data collection, such as required agents, permissions, or counters.
Provide parity in documentation for Linux-based discovery, assessment, and migration, including links to relevant tutorials.
Clarify that Azure Migrate supports both Windows and Linux servers, and provide guidance for mixed-environment assessments.
Where agent or appliance installation is discussed, include Linux installation/requirements alongside Windows.
Add FAQs or sections addressing common Linux migration blockers and how Azure Migrate handles them.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page for Azure Logic Apps and Power Automate expression functions shows evidence of Windows bias. Specifically, references to time zone names and date/time formatting consistently point to Microsoft Windows resources (e.g., 'Microsoft Windows Default Time Zones', .NET date/time format strings), and no mention is made of Linux or IANA time zone standards. The documentation relies on .NET conventions and Windows-centric resources, which may not be familiar or directly applicable to Linux users. There are no PowerShell-specific examples, but Windows tools and patterns are referenced exclusively or before any cross-platform alternatives.

Recommendations:

Where time zone names are referenced, also provide IANA/Olson time zone equivalents or clarify how to map between Windows and IANA time zones.
When referencing date/time format strings, note that these are .NET-specific and provide links or mappings to equivalent POSIX/strftime formats where possible.
Add a note clarifying that the underlying implementation is based on .NET, which may use Windows conventions, but provide guidance for Linux users on how to adapt or interpret these values.
Where external resources are linked (e.g., Microsoft Windows Default Time Zones), also link to cross-platform resources or explain any differences.
Explicitly state any platform dependencies or limitations, and provide examples or explanations relevant to Linux environments if applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page provides detailed steps for migrating VMware servers to Azure using Private Link, but it implicitly assumes the Azure Migrate appliance is a Windows-based VM. There are no explicit Linux-specific instructions, examples, or troubleshooting steps. The only OS-specific mention is in the Azure Hybrid Benefit section, which refers to Windows Server. There are references to editing the 'hosts file' and running commands from 'the on-premises server hosting the Migrate appliance,' but no cross-platform (Linux) guidance is provided. No PowerShell or Windows tool commands are shown, but the lack of Linux parity is notable.

Recommendations:

Explicitly state whether the Azure Migrate appliance can be deployed on Linux, and if so, provide Linux-specific setup and troubleshooting instructions.
When referencing editing the hosts file or verifying DNS resolution, include both Windows and Linux command examples (e.g., 'notepad C:\Windows\System32\drivers\etc\hosts' vs. 'sudo nano /etc/hosts'; 'nslookup' or 'dig' on Linux).
In sections discussing Azure Hybrid Benefit, clarify applicability for Linux VMs (e.g., mention Azure Hybrid Benefit is only for Windows Server, and note any Linux migration licensing considerations).
Add troubleshooting steps and connectivity verification commands for both Windows and Linux environments.
If the Azure Migrate appliance is Windows-only, state this clearly at the beginning of the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by referencing Windows Server as the only example of an unsupported OS and omitting any mention of Linux distributions or their compatibility. There are no Linux-specific examples, scenarios, or troubleshooting notes, and the language assumes Windows workloads by default.

Recommendations:

Include explicit examples and scenarios for both Windows and Linux servers throughout the documentation, such as referencing unsupported Linux distributions or kernel versions in the 'Conditionally ready for Azure' section.
Add a table or list of supported and unsupported operating systems, including major Linux distributions (e.g., Ubuntu, CentOS, Red Hat, SUSE) and their versions.
Provide Linux-specific remediation guidance and considerations, especially where Azure VM features (like Trusted Launch) have different requirements or support levels for Linux.
Ensure that all sections discussing readiness, sizing, and security explicitly mention Linux alongside Windows, and clarify any differences in assessment or migration processes.
Where examples are given (for instance, in CSV import or performance data), include Linux server names or properties to illustrate parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently refers to SQL Server migration scenarios and readiness in the context of 'SQL Server on Azure VM', 'Azure SQL Managed Instance', and 'Azure SQL Database', but does not mention or provide examples for SQL Server running on Linux or migration from Linux-based SQL Server deployments. There are no references to Linux-specific considerations, tools, or patterns, nor are there any examples or instructions that address Linux environments. The documentation implicitly assumes a Windows-based SQL Server source environment.

Recommendations:

Explicitly mention that SQL Server can run on both Windows and Linux, and clarify whether the assessment supports both platforms.
Add examples or notes for users migrating SQL Server from Linux environments, including any differences in assessment, readiness, or migration steps.
Include references to Linux-specific tools or commands where relevant (e.g., bash scripts, Linux authentication, file paths).
If there are limitations or differences for Linux-based SQL Server migrations, document them clearly.
Ensure screenshots and UI references do not assume only Windows-based SQL Server sources.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references the SQL Server Migration Assistant for MySQL, which is a Windows-only tool, without mentioning Linux alternatives or providing Linux-based migration examples. There are no explicit Linux command-line or tool examples, and the documentation does not address cross-platform migration tooling parity.

Recommendations:

Include Linux-compatible migration tools (such as MySQL Workbench, pg_dump/pg_restore, or open-source migration frameworks) alongside or in place of Windows-only tools like SQL Server Migration Assistant.
Provide example migration workflows or commands for both Windows (PowerShell, SSMA) and Linux (Bash, native CLI tools).
Explicitly state platform compatibility for each tool or guide, and link to Linux-specific documentation where available.
Consider adding a section or table comparing migration tooling options for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is focused exclusively on assessing Hyper-V VMs for migration to Azure, implicitly targeting Windows-centric environments. There are no Linux-specific examples, tools, or considerations provided, and the workflow assumes a Windows/Hyper-V context throughout. While there is a brief mention of Enterprise Linux subscriptions (RHEL and SLES) in the context of Azure Hybrid Benefit, there are no instructions or examples tailored for Linux VMs or administrators.

Recommendations:

Include explicit instructions or examples for assessing Linux VMs running on Hyper-V, highlighting any differences or additional considerations.
Mention Linux-specific licensing and migration considerations earlier and more prominently, not just in the context of Azure Hybrid Benefit.
Provide parity in examples, such as screenshots or command-line steps, that show both Windows and Linux VM scenarios.
Clarify in the prerequisites or introduction that the process applies to both Windows and Linux VMs, and link to Linux-specific guidance if available.
If any steps differ for Linux VMs (e.g., agent installation, performance data collection), document those differences clearly.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides parallel mention of ASP.NET/IIS (Windows) and Java/Tomcat (Linux/Java) web apps, but the actual step-by-step examples and screenshots are generic and do not show any Linux-specific tools, commands, or patterns. There is no explicit demonstration of Linux-based web app assessment workflows, and the documentation does not mention or show Linux-native environments, tools, or shell commands. The structure and terminology (e.g., 'Servers', 'Appliance') are platform-neutral, but the lack of Linux-specific examples or references constitutes a subtle Windows-first and missing Linux example bias.

Recommendations:

Add explicit step-by-step examples for assessing Linux-based web apps (e.g., Node.js, PHP, Python on Apache/Nginx) in addition to Java/Tomcat.
Include screenshots and walkthroughs that show Linux server environments and Linux-native tools (e.g., bash commands, Linux file paths).
Mention and demonstrate the assessment of web apps running on popular Linux web servers (Apache, Nginx) and frameworks.
Ensure parity in the depth and clarity of instructions for both Windows (IIS/ASP.NET) and Linux (Tomcat/Apache/Nginx) scenarios.
Where platform-specific steps differ (e.g., agent installation, prerequisites), provide clear, side-by-side instructions for both Windows and Linux.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page for Azure NAT Gateway is generally platform-neutral, focusing on conceptual overviews and Azure-specific features. However, there is a subtle Windows bias in the 'NAT gateway and basic resources' section, where the only example for upgrading a basic load balancer to standard references a PowerShell-based process. No equivalent Linux/CLI or cross-platform example is provided, and the PowerShell reference appears before any mention of portal-based or CLI-based upgrades.

Recommendations:

Provide equivalent Azure CLI (cross-platform) commands alongside PowerShell examples for resource upgrades and management tasks.
When referencing upgrade or management procedures, list Azure Portal and Azure CLI methods before or alongside PowerShell to avoid implying Windows/PowerShell primacy.
Ensure that all procedural links and examples are available for both Windows (PowerShell) and Linux/macOS (Azure CLI, Bash) users.
Add explicit notes or sections for Linux/macOS users where relevant, especially for command-line operations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by explicitly requiring Windows PowerShell 4.0 on the source servers for migration and makes no mention of Linux-based alternatives or scenarios. There are no examples or instructions for migrating from Linux-based web servers, nor is there guidance for users running ASP.NET Core apps on Linux. The documentation assumes a Windows/IIS environment throughout.

Recommendations:

Clarify whether Linux-based ASP.NET (Core) web apps are supported for migration using Azure Migrate, and if so, provide equivalent instructions or note any limitations.
If Linux is not supported, explicitly state this in the prerequisites to set expectations for users.
If Linux is supported, include examples or steps for Linux environments (e.g., using Bash, SSH, or Linux-native tools) alongside Windows/PowerShell instructions.
Mention any Linux-specific requirements or tools (such as minimum supported distributions, required packages, or migration agents) if applicable.
Ensure parity in post-migration steps by referencing Linux-specific configuration or troubleshooting resources where relevant.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes how to deploy and configure a NAT gateway using the Azure Portal GUI, without providing any command-line examples. There are no references to PowerShell or Windows-specific tools, but there is also a lack of Azure CLI (cross-platform) or Bash/Linux shell examples. This omission can be seen as a subtle Windows bias, as Azure Portal workflows are often more familiar to Windows users, and the absence of CLI or script-based instructions may disadvantage Linux users or those automating deployments.

Recommendations:

Add Azure CLI examples for each step, demonstrating how to create and configure a NAT gateway and associate resources using cross-platform commands.
Include Bash script snippets for automating the process, making the documentation more accessible to Linux users.
Explicitly mention that the steps can be performed via Azure CLI or ARM templates, and provide links or references to relevant documentation.
Ensure parity by presenting both Portal and CLI/script-based instructions side by side, or clearly indicating alternative methods for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation generally maintains OS neutrality but exhibits subtle Windows bias in the order of references and lack of Linux-specific examples. In the 'Monitoring connectivity from Azure virtual machines and virtual machine scale sets' section, the link to 'Manage Network Watcher extension for Windows' is listed before the Linux equivalent, and there are no explicit Linux or cross-platform command-line examples (e.g., Bash, Azure CLI) in the 'Create a connection monitor' section, where only Azure PowerShell is mentioned as a programmatic method. This may give the impression that Windows or PowerShell is the primary or preferred environment.

Recommendations:

When listing OS-specific instructions or links, alternate the order or list Linux first in some sections to avoid implicit prioritization.
Provide explicit Linux/Bash/Azure CLI examples alongside or before PowerShell examples when describing command-line or automation workflows.
Mention cross-platform tools (such as Azure CLI or ARM templates) equally or before Windows-specific tools like PowerShell.
Add a table or section summarizing parity between Windows and Linux for agent installation, troubleshooting, and automation.
Ensure that all references to monitoring agents, troubleshooting steps, and automation methods clearly state support for both Windows and Linux, and provide parallel examples where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently uses Windows-centric examples, particularly by focusing on RDP (port 3389) connectivity, which is specific to Windows environments. There are no equivalent Linux scenarios (such as SSH on port 22) provided. The troubleshooting steps and sample outputs are all based on RDP, and solutions reference enabling RDP or related Windows firewall/security group rules. While the documentation does mention Linux in the context of installing the Network Watcher agent, it does not provide Linux-specific connectivity tests or troubleshooting examples.

Recommendations:

Include Linux-centric connectivity scenarios, such as testing SSH (port 22) between virtual machines, alongside or instead of RDP examples.
For each troubleshooting example, provide parallel steps and outputs for both RDP (Windows) and SSH (Linux) to ensure parity.
In solution sections, mention updating firewall rules for SSH on Linux (e.g., opening port 22) as well as RDP for Windows.
Where operating system configuration is referenced, provide guidance for both Windows (enabling RDP) and Linux (enabling SSH, checking sshd status, etc.).
Ensure that screenshots and sample outputs reflect both Windows and Linux use cases where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a 'windows_first' bias by exclusively using Windows Server images and Windows-centric terminology in all virtual machine creation steps, both in the Azure Portal and command-line examples. There are no examples or instructions for deploying or managing Linux-based virtual machines, nor is there any mention of Linux-specific considerations or differences. This may lead Linux users to feel unsupported or uncertain about following the guide for their scenarios.

Recommendations:

Add parallel Linux examples for all VM creation steps, both in the Portal and CLI/PowerShell sections (e.g., show how to select Ubuntu or another popular Linux image).
In the Portal instructions, include a step or note showing how to select a Linux image and set up SSH authentication.
In PowerShell and Azure CLI examples, provide Linux image references (e.g., 'Canonical:UbuntuServer:20_04-lts:latest') and show how to configure Linux-specific parameters such as SSH keys.
Where administrator credentials are discussed, mention SSH keys for Linux and provide guidance for secure setup.
Add a note clarifying that the NSG diagnostics and other procedures are applicable to both Windows and Linux VMs, and highlight any OS-specific considerations if relevant.
Ensure screenshots and example outputs are not exclusively Windows-centric, or provide Linux equivalents where possible.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples or tooling, but it also does not mention or demonstrate how to generate or use SAS tokens via command-line tools or scripts. There are no references to Windows tools (such as PowerShell or Azure CLI on Windows), nor are there any Linux/Unix-specific examples. However, the absence of any command-line or scripting examples means Linux users are not shown parity in how to interact with SAS tokens, which is a subtle form of bias by omission.

Recommendations:

Add examples showing how to generate SAS tokens using both Azure CLI (cross-platform) and PowerShell, ensuring both are presented equally.
Include sample commands for accessing blobs with SAS tokens using curl (Linux/Unix) and Invoke-WebRequest (PowerShell/Windows).
Explicitly mention that all steps can be performed on both Windows and Linux, and provide links to relevant cross-platform tooling.
If screenshots or UI steps are included, clarify that the Azure Portal is accessible from any OS.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides both Linux/macOS and Windows instructions for setting environment variables, but the Windows example is presented after the Linux/macOS example. There is no exclusive use of Windows tools, nor are there missing Linux examples or PowerShell-heavy instructions. The documentation is generally cross-platform, but the ordering of examples could be considered a subtle form of bias if consistency across Microsoft documentation is considered.

Recommendations:

Present both Linux/macOS and Windows instructions side-by-side or in a tabbed interface, ensuring equal prominence.
Consider alternating the order of platform examples in different sections, or default to alphabetical order (Linux, macOS, Windows) to avoid implicit prioritization.
Explicitly state that the tool is cross-platform and works identically on all supported operating systems.
If possible, provide PowerShell examples for Windows users in addition to CMD, as PowerShell is increasingly common.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively provides C#/.NET code samples and does not mention or provide any platform-specific instructions, but all examples implicitly assume a Windows/.NET development environment. There are no Linux-specific instructions, examples, or references to cross-platform usage, which may leave Linux developers without guidance on how to use Azure Relay in their environment.

Recommendations:

Explicitly state that the .NET Standard APIs and code samples are cross-platform and can be used on Linux, macOS, and Windows.
Include instructions or notes on how to run the provided .NET code samples on Linux (e.g., using .NET Core/SDK on Linux).
If there are any platform-specific considerations (such as firewall configuration, dependencies, or environment variables), document these for Linux users.
Provide example commands for building and running the code on Linux (e.g., using 'dotnet build' and 'dotnet run' in a terminal).
Link to official Microsoft documentation on installing .NET on Linux.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions for cabling and network configuration of Azure Data Box, but all examples for setting static IP addresses and configuring network adapters are generic and do not specify commands or steps for either Windows or Linux. However, the language and phrasing (e.g., 'Configure the Ethernet adapter of the laptop you're using') implicitly assumes a Windows environment, and there are no explicit Linux (or macOS) configuration examples or references. There are also no mentions of Linux-specific tools or commands for network configuration.

Recommendations:

Add explicit examples for both Windows and Linux environments when configuring network adapters, such as using 'Control Panel > Network and Sharing Center' for Windows and 'nmcli' or 'ifconfig' commands for Linux.
Include screenshots or command-line snippets for both operating systems to guide users through setting static IP addresses.
Mention Linux as a supported environment in the configuration steps, not just in the prerequisites.
If possible, provide a table or section summarizing network configuration steps for Windows, Linux, and macOS.
Clarify that the instructions apply to all supported operating systems, and link to OS-specific network configuration guides.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on using the Azure Portal and ARM templates for deploying an Azure Migrate project, 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 provided, and no Linux-specific instructions or considerations are mentioned.

Recommendations:

Add Azure CLI examples for deploying the ARM template, which are cross-platform and work on Linux, macOS, and Windows.
Include Bash shell commands for users who prefer scripting on Linux.
Explicitly mention that the ARM template can be deployed using Azure CLI or PowerShell, and provide both sets of instructions.
Ensure screenshots and instructions are not portal-only; provide equivalent command-line steps.
Highlight any platform-specific considerations if they exist (e.g., authentication differences between Windows and Linux environments).

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation exhibits a subtle Windows bias by referencing 'App Service Environment v3 (Windows plans only)' when describing the Standard environment, without mentioning Linux equivalents or clarifying Linux support. There are no explicit Windows-only tools, PowerShell commands, or examples, but the documentation does not address Linux scenarios or provide parity in platform references.

Recommendations:

Clarify whether Standard Logic Apps are supported on Linux plans, and if so, provide equivalent instructions or notes for Linux users.
If certain features are Windows-only (such as App Service Environment v3), explicitly state this and provide guidance or alternatives for Linux users.
Review all platform-specific references to ensure both Windows and Linux users are equally informed about compatibility and deployment options.
Include a section or note addressing cross-platform considerations, especially for users deploying Logic Apps in different environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides both Bash (Linux/macOS) and Azure PowerShell (Windows) examples for verifying the results, but the Bash example is presented first. There are no exclusive references to Windows tools or patterns, and Linux examples are not missing. No evidence of PowerShell-heavy bias or exclusive use of Windows tools was found.

Recommendations:

Maintain parity by continuing to provide both Bash and PowerShell examples for all command-line steps.
Explicitly mention that Bash commands work on Linux and macOS, and that PowerShell is for Windows, to help users choose the right tab.
Consider including a note about using the Azure CLI in Windows environments (e.g., via WSL or native CLI) to further support cross-platform users.
Ensure that any referenced scripts or code samples are tested on both Linux and Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides platform-specific instructions for generating a development signature hash, listing the Windows command first and labeling the next as 'For iOS' (though it is actually the Unix/Linux equivalent). No explicit Linux example is given, and the Windows command is prioritized, which may imply a Windows-first bias.

Recommendations:

Label the Unix command as 'For Linux/macOS' instead of 'For iOS', since the command is for the shell and applies to both Linux and macOS environments.
Present both Windows and Linux/macOS commands together, or list Linux/macOS first or equally, to avoid implying Windows is the default or primary environment.
Explicitly mention Linux as a supported development environment in the relevant sections.
Consider providing a table or side-by-side code blocks for Windows and Linux/macOS commands for parity and clarity.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples, scripts, or tooling, but also does not mention or demonstrate how to perform the described operations (such as calling Microsoft Graph API) from any platform, including Windows or Linux. There is an implicit bias in that no cross-platform command-line or scripting examples (such as curl, bash, PowerShell, or CLI tools) are provided, which may leave Linux users without clear guidance.

Recommendations:

Add explicit examples for calling the Microsoft Graph API using cross-platform tools such as curl or HTTPie, which work on both Linux and Windows.
If scripting examples are provided in the future, ensure both PowerShell (Windows) and bash (Linux/macOS) examples are included.
Mention and link to platform-agnostic tools (e.g., Azure CLI, Microsoft Graph CLI) where possible.
Clarify that the described API operations can be performed from any OS, and provide sample commands for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation presents both Windows and Linux default values in a configuration table, but consistently lists Windows first. There are no explicit Windows-only tools, commands, or examples, and all configuration examples use the cross-platform Azure CLI. However, the ordering of Windows before Linux in the table and in the note about unsupported features ("App Service on Windows does not support DNS resolution over TCP") subtly prioritizes Windows. There are no missing Linux examples, but Linux is always mentioned second.

Recommendations:

Alternate the order of Windows and Linux in tables and explanations, or use alphabetical order (Linux, Windows) to avoid implicit prioritization.
Where possible, provide parity in notes and limitations (e.g., if a limitation is Windows-only, clarify if Linux has similar or different behavior).
Explicitly state that all CLI examples are cross-platform to reinforce parity.
Consider adding a brief section summarizing any platform-specific differences, rather than embedding Windows-first details throughout.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively uses Azure CLI commands and does not provide any OS-specific shell examples (such as PowerShell or Bash). However, there are no explicit Windows tools, PowerShell scripts, or references to Windows-specific patterns. The Azure CLI is cross-platform, but there are no Linux/Bash-specific examples or notes, nor are there any references to Linux tools or workflows. The documentation is neutral in tone but lacks explicit Linux parity in examples or troubleshooting steps.

Recommendations:

Add explicit Bash shell examples where relevant, especially for common Linux workflows.
Include notes or troubleshooting tips for Linux environments, such as DNS resolution or file-based configuration nuances.
If referencing command-line tools, clarify their cross-platform compatibility and provide alternative commands for PowerShell (Windows) and Bash (Linux/macOS) where differences exist.
Mention any OS-specific considerations (e.g., file paths, environment variables) that may affect Linux users.
Ensure that any referenced quickstarts or tutorials include both Windows and Linux setup instructions where applicable.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation lists Windows-specific tools (Azure PowerShell, Azure portal) before Linux-friendly options (Azure CLI) when describing how to create an Azure Kubernetes cluster. However, the main deployment instructions use cross-platform tools (kubectl) and do not otherwise show a Windows or PowerShell bias. There are no missing Linux examples, and no exclusive use of Windows tools or patterns in the main workflow.

Recommendations:

List Azure CLI (which is cross-platform and preferred in Linux environments) before Azure PowerShell and Azure portal in the prerequisites.
Explicitly mention that all kubectl commands work identically on Windows, Linux, and macOS.
If possible, provide links or notes for Linux/macOS users regarding installation of required tools (kubectl, Azure CLI).
Ensure that any referenced scripts or commands are not PowerShell-specific, and clarify when a command is platform-agnostic.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any OS-specific examples or commands, but all configuration steps are described exclusively through the Azure Portal UI. There are no CLI, PowerShell, or Linux shell examples, which may disadvantage users who prefer or require command-line automation, especially on Linux. The absence of CLI or Linux-native instructions constitutes a subtle bias by omission.

Recommendations:

Add Azure CLI examples for all configuration steps, as the Azure CLI is cross-platform and widely used on Linux.
If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are provided.
Explicitly mention that all steps can be performed via the Azure CLI or ARM templates, and link to relevant documentation.
Include sample commands for subnet delegation, resource provider registration, and network integration using both Azure CLI and PowerShell, with Linux/Bash examples shown first or equally.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation demonstrates a subtle Windows bias by listing the Windows hosts file path before the Linux/macOS equivalent when describing how to update the hosts file for DNS testing. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present, but the ordering suggests a preference for Windows environments.

Recommendations:

List both Windows and Linux/macOS hosts file paths together, or alternate the order in which they are presented to avoid implying a preference.
Wherever possible, provide explicit examples or screenshots for both Windows and Linux environments.
Review the documentation for other subtle ordering or phrasing that may suggest Windows is the primary or default platform.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page provides step-by-step instructions for configuring Azure API Management private endpoints, but it lacks any OS-specific bias such as Windows/Powershell-heavy examples or exclusive mention of Windows tools. The only command-line example is an Azure CLI command, which is cross-platform. However, in the 'Test in virtual network' section, the only DNS lookup example given is with nslookup, and there is no mention of Linux/Unix alternatives such as dig. There are no references to Windows-specific tools, Powershell, or patterns, and the Azure portal instructions are OS-agnostic.

Recommendations:

Add Linux/Unix command examples alongside nslookup, such as 'dig my-apim-service.privatelink.azure-api.net', to ensure parity for users on non-Windows systems.
When suggesting utilities, mention both 'nslookup' and 'dig' as options for DNS lookups.
Explicitly state that Azure CLI commands work on Windows, Linux, and macOS to reinforce cross-platform support.
Continue to avoid Windows/Powershell-specific instructions unless parity is provided for other platforms.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally maintains cross-platform neutrality, but in the section describing hosts file editing for DNS testing, the Windows path (%SystemDrive%\drivers\etc\hosts) is mentioned before the Linux/macOS path (/etc/hosts). No command-line examples are given, and no Windows-specific tools or PowerShell commands are used elsewhere.

Recommendations:

When mentioning file paths for cross-platform features (like the hosts file), list Linux/macOS paths first or present them in parallel (e.g., 'on Linux/macOS: /etc/hosts; on Windows: %SystemDrive%\drivers\etc\hosts').
If providing examples or screenshots, ensure parity by including both Windows and Linux equivalents where appropriate.
Continue to avoid platform-specific tooling or commands unless absolutely necessary, and always provide alternatives for other platforms.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation presents Windows examples and instructions before Linux equivalents, as seen in the ordering of the code and container pivots. While Linux content is present, the structure prioritizes Windows, which may suggest a subtle bias towards Windows users.

Recommendations:

Alternate the order of platform pivots or present Linux and Windows examples side-by-side to ensure equal visibility.
Explicitly mention that both Windows and Linux are supported at the top of the page.
Consider a neutral introduction or overview before diving into platform-specific instructions.
Ensure that Linux instructions are as detailed and prominent as Windows instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific command-line examples or instructions, but it does reference ASP.NET Core for URL rewriting as the only concrete application-level workaround for root domain mapping. This implicitly assumes a Windows/.NET stack and does not mention equivalent solutions for Linux-based stacks (e.g., Nginx, Apache). There are no explicit PowerShell, Windows tools, or Windows-first ordering, but the lack of Linux/OSS examples is a subtle bias.

Recommendations:

When suggesting application-level URL redirects, include examples for popular Linux-based web servers such as Nginx and Apache, alongside the ASP.NET Core example.
Explicitly mention that the workaround for root domains can be implemented in any web framework or server, and provide links or references to documentation for common Linux stacks.
If referencing application-level configuration, provide parity by showing both Windows/.NET and Linux/OSS approaches.
Consider adding a note that the Azure portal and DNS changes are platform-agnostic, to reassure Linux users.

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; it is largely platform-neutral. However, in the section about SSH key authentication, the only help link provided is 'How to create and use SSH keys' with a URL ending in '/linux/ssh-from-windows', which specifically targets Windows users connecting to Linux VMs. There are no Linux or macOS-specific instructions or links, and no mention of Linux-native tools or workflows. No PowerShell, Windows command prompt, or Windows-specific tools are referenced, but Linux parity is not fully addressed.

Recommendations:

Provide links to SSH key creation and usage guides for Linux and macOS users, not just Windows.
Explicitly mention that the deployment process is platform-agnostic and can be performed from any OS with a web browser.
If command-line or scripting examples are added in the future, ensure both Windows (PowerShell/CMD) and Linux/macOS (bash/ssh) examples are included.
Clarify that the Azure Portal and deployment wizard are accessible from any modern operating system.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples, but it also does not mention or demonstrate any Linux-specific tools, commands, or workflows. While the content is generally platform-neutral, there is a missed opportunity to address Linux users explicitly, especially given the 'linux-related-content' tag. There are no Windows-specific commands or tools, but the lack of Linux-specific guidance or troubleshooting constitutes a subtle bias by omission.

Recommendations:

Add explicit notes or examples for both Windows and Linux App Service environments, clarifying any differences in behavior or UI.
Include troubleshooting steps or caveats for Linux-based App Service plans, such as file system case sensitivity, file permissions, or differences in error handling.
If the UI or features differ between Windows and Linux App Service, provide screenshots or callouts for each.
Mention any Linux-specific limitations or configuration steps, if applicable.
Ensure that the FAQ and instructions address both Windows and Linux scenarios where relevant.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation presents the Windows (SMB) connection instructions before the Linux (NFS) instructions, but both platforms are covered with equivalent detail and examples. There are no missing Linux examples or exclusive use of Windows tools.

Recommendations:

Alternate the order of SMB (Windows) and NFS (Linux) sections, or present them in parallel to avoid implicit prioritization.
Explicitly state that both Windows and Linux are supported at the beginning of the 'Connect to the share' section.
Ensure parity in troubleshooting tips and caveats for both platforms, if applicable.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page generally avoids OS-specific tooling or examples, but in the 'Next steps' section, instructions for creating an application gateway are listed in the order: Azure Portal, Azure PowerShell, and then Azure CLI. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform. Listing PowerShell before CLI may subtly prioritize Windows users.

Recommendations:

List Azure CLI instructions before or alongside PowerShell to reflect its cross-platform nature and promote parity for Linux and macOS users.
Explicitly mention that both Azure CLI and PowerShell are supported on multiple platforms, if true, to avoid the impression of Windows preference.
Wherever possible, provide parallel examples for both PowerShell and CLI in procedural documentation.
Review other documentation pages for similar ordering or tool prioritization to ensure consistent cross-platform inclusivity.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide explicit examples or instructions for Linux users. While it mentions uploading executables or scripts in a .zip file, it does not clarify support for Linux-specific script types (e.g., Bash, Python) or provide Linux-oriented examples. There is no mention of Linux command-line tools, nor are there instructions for deploying or managing WebJobs from a Linux environment. The documentation is neutral in tone but implicitly assumes a Windows-centric workflow by omitting Linux-specific guidance.

Recommendations:

Explicitly list and provide examples for Linux-compatible script types (e.g., .sh, Python) in the 'Supported file types' section.
Add a section or examples showing how to create, deploy, and manage WebJobs using Linux command-line tools (e.g., Azure CLI on Linux, Bash scripts).
Clarify any differences in behavior or requirements when running WebJobs on Linux App Service plans versus Windows.
Include screenshots or terminal output from Linux environments where relevant.
Mention any prerequisites or considerations for Linux users, such as file permissions or shebang lines in scripts.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific troubleshooting commands or examples, but it does mention exporting the TLS/SSL certificate using a browser without specifying any platform. However, there are no explicit instructions or examples for Linux users (e.g., using OpenSSL or command-line tools), which may leave Linux administrators without clear guidance.

Recommendations:

Add step-by-step instructions for exporting the ILB certificate using common Linux tools such as OpenSSL.
Provide both Windows (e.g., using MMC or browser) and Linux (e.g., using curl or OpenSSL) methods for retrieving and exporting certificates.
Explicitly mention that the browser export method works on all platforms, or clarify any platform-specific steps if necessary.
Include command-line examples for both Windows (PowerShell) and Linux (bash) where relevant, to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation references both PowerShell and Azure CLI for listing SSL certificates, but it mentions the PowerShell command before the Azure CLI command. No Linux-specific tools or examples are provided, but the CLI example is cross-platform. There are no exclusive Windows tools or patterns, and the rest of the documentation is portal-focused and platform-neutral.

Recommendations:

When listing command-line examples, alternate the order or explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
Consider providing a Linux shell example (e.g., Bash) for Azure CLI usage to reinforce cross-platform applicability.
Add a brief note clarifying that PowerShell is available on Linux and macOS as well, or link to installation instructions for non-Windows users.
Ensure that any future command-line or scripting examples are balanced between platforms, or use Azure CLI as the default for cross-platform parity.

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. There is no explicit Windows bias, but the absence of concrete examples (such as using Powershell, Windows tools, or Linux shell commands) means Linux parity is not addressed. If future updates add examples, care should be taken to include both Windows and Linux instructions.

Recommendations:

When adding practical configuration steps, provide both Windows (e.g., Powershell, CMD) and Linux (e.g., Bash, systemd) examples for setting headers and configuring backend servers.
Include sample commands for setting HTTP headers in both Windows (IIS, Powershell) and Linux (Apache, Nginx, curl) environments.
If referencing tools or logs, mention both Windows and Linux equivalents (e.g., Event Viewer and journalctl, or IIS logs and Apache/Nginx logs).
Ensure that any troubleshooting or monitoring steps are cross-platform.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions only for disabling Azure Automanage via the Azure Portal, with no mention of command-line methods (such as PowerShell, Azure CLI, or Bash). However, there is no explicit Windows bias in the form of PowerShell-heavy examples, Windows-first ordering, or exclusive mention of Windows tools. The main bias is the lack of parity for users who prefer or require CLI-based workflows, which are especially common on Linux.

Recommendations:

Add instructions for disabling Automanage using the Azure CLI, which is cross-platform and widely used on Linux.
If PowerShell examples are added, ensure equivalent Bash/Azure CLI examples are provided.
Explicitly mention that the portal method works for both Windows and Linux VMs, or clarify any differences if they exist.
Include links to relevant CLI documentation for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation lists Windows Server before Linux in the prerequisites and in the links to further documentation, suggesting a subtle 'windows_first' bias. However, there are no explicit examples, commands, or tools shown that are Windows-specific, and Linux is mentioned as supported throughout. No PowerShell-heavy content or exclusive Windows tooling is present.

Recommendations:

Alternate the order of Windows and Linux mentions or list them alphabetically to avoid implicit prioritization.
Ensure that Linux and Windows documentation links are presented with equal prominence.
Consider including a brief example or mention of both Windows and Linux onboarding flows, even if only at a high level, to reinforce parity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning the equivalent command for macOS/Linux. All other code and instructions are cross-platform and do not show a strong Windows or PowerShell bias.

Recommendations:

Present environment variable setup commands for all platforms together, or alternate the order (e.g., show Linux/macOS first in some sections).
Consider using a table or tabbed code blocks to make platform parity more visually clear.
Explicitly state that all code examples are cross-platform unless otherwise noted, to reassure non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

Summary:

The documentation provides language-specific examples for C#, JavaScript, PowerShell, Python, and Java. While most examples are language-focused and cross-platform, the inclusion of PowerShell as a primary language (alongside Python and JavaScript) may indicate a slight Windows bias, as PowerShell is traditionally associated with Windows environments, although it is now cross-platform. However, there are no explicit Windows-only tools, Windows-first ordering, or missing Linux examples. No Windows-specific commands, paths, or tools are mentioned, and all code samples are language-agnostic or cross-platform.

Recommendations:

Clarify that PowerShell examples are intended to be cross-platform (PowerShell Core), not Windows PowerShell, to avoid confusion.
Consider including bash or shell script examples for Linux users, especially if scripting is relevant for operational tasks.
Explicitly state in the introduction or relevant sections that all examples are intended to work on both Windows and Linux, unless otherwise noted.
If any operational steps (such as local development, deployment, or troubleshooting) are added in the future, ensure both Windows and Linux command-line instructions are provided.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively describes Azure App Configuration recovery operations using the Azure Portal UI, with no mention of command-line tools or automation. There are no examples or instructions for performing these tasks via CLI, PowerShell, or scripting, and thus no Linux (or cross-platform) parity is demonstrated. This omission implicitly favors GUI-based workflows, which are more common on Windows, and neglects users who prefer or require command-line or automated solutions, especially on Linux or macOS.

Recommendations:

Add equivalent instructions and examples for performing all recovery, purge, and configuration operations using the Azure CLI (az appconfig commands), which is cross-platform.
If PowerShell examples are added, ensure to also provide Azure CLI examples for Linux/macOS users.
Explicitly mention that all operations can be performed via CLI and provide links to relevant CLI documentation.
Consider including bash script snippets for common automation scenarios.
Clarify any differences or limitations between portal, CLI, and PowerShell approaches.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of command-line instructions or tool references; all shell commands use the cross-platform 'dotnet' CLI and .NET Secret Manager, which are available on both Windows and Linux. However, there is a subtle bias in that there are no explicit Linux/macOS-specific instructions, troubleshooting notes, or terminal output examples, which may leave Linux users uncertain about environment-specific differences or requirements.

Recommendations:

Explicitly mention that all dotnet CLI and Secret Manager commands work on Linux/macOS as well as Windows.
Add a note or section confirming cross-platform compatibility, and provide any Linux/macOS-specific prerequisites (such as ensuring the dotnet CLI is in PATH, or how to install it on Linux).
Include screenshots or terminal output examples from Linux/macOS environments alongside or in place of Windows examples, where relevant.
If there are any known differences in behavior or setup steps for Linux/macOS (such as file permissions or environment variable handling), document these explicitly.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning the equivalent command for macOS/Linux. All other code and instructions are cross-platform and Python-centric, with no exclusive use of Windows tools or missing Linux examples.

Recommendations:

Present environment variable setup commands for all platforms together, or list Linux/macOS first to avoid implicit prioritization of Windows.
Consider using a tabbed or side-by-side format for platform-specific commands to give equal prominence to Windows, macOS, and Linux.
Review future documentation to ensure that Linux/macOS instructions are not always listed after Windows/PowerShell, especially for common developer workflows.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation demonstrates a mild 'windows_first' bias: in the 'Prerequisites' section, installation instructions for Node.js reference Windows and WSL before Linux, and in the environment variable setup, Windows command prompt and PowerShell instructions are presented before macOS/Linux equivalents. However, Linux/macOS instructions are present throughout, and no examples or tools are exclusive to Windows.

Recommendations:

Present environment variable setup instructions for all platforms in parallel (e.g., in a table or side-by-side tabs), or rotate the order so Linux/macOS is sometimes listed first.
In the 'Prerequisites' section, provide direct Linux/macOS installation guidance or links alongside Windows, not just after.
Ensure that any future troubleshooting or advanced sections do not default to Windows-only tools or patterns.
Consider using neutral, cross-platform language and examples where possible (e.g., 'terminal' instead of 'command prompt').

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally maintains cross-platform parity, providing instructions and code samples that are equally applicable to Windows, macOS, and Linux. However, in the 'Prerequisites' section, the link for installing Node.js prioritizes Windows-specific instructions ('installing Node.js either directly on Windows or using the Windows Subsystem for Linux (WSL)'), which places Windows before Linux or macOS. In the environment variable configuration section, all three platforms (Windows Command Prompt, PowerShell, macOS/Linux) are covered equally and in parallel, with no platform unduly prioritized. No PowerShell-heavy content, missing Linux examples, or exclusive use of Windows tools is present.

Recommendations:

In the 'Prerequisites' section, provide a more balanced link or sentence for Node.js installation, such as: 'For information about installing Node.js on Windows, macOS, or Linux, see [Get started with Node.js](/windows/dev-environment/javascript/nodejs-overview)'.
If linking to platform-specific guides, consider listing Linux and macOS before or alongside Windows, or provide a neutral landing page that covers all platforms equally.
Continue to ensure that all command-line instructions and code samples are provided for all major platforms in parallel, as is done in the environment variable configuration section.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation demonstrates a subtle Windows bias in its references to Azure VMSS (Virtual Machine Scale Sets) and managed identities. Specifically, links and instructions for enabling managed identities and assigning roles reference Windows VMSS documentation and URLs, even though AKS clusters can run on Linux VMSS as well. No explicit PowerShell or Windows-only command-line examples are present, and all CLI and YAML examples are cross-platform. However, the documentation consistently references Windows VMSS in authentication scenarios, which may confuse or exclude Linux VMSS users.

Recommendations:

Wherever managed identity or VMSS is referenced, provide links and instructions for both Windows and Linux VMSS. For example, link to both Windows and Linux quickstarts for enabling managed identity.
Clarify in the authentication sections that the instructions apply to both Windows and Linux VMSS, or specify any differences if they exist.
Audit all links to Azure documentation to ensure they are not Windows-specific unless required. If both OSes are supported, use generic or dual links.
Explicitly state that AKS clusters typically run on Linux VMSS and provide Linux-centric examples or notes where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

Summary:

The documentation provides language-specific examples for C#, Java, JavaScript, TypeScript, PowerShell, and Python. While there is no overt Windows bias in the form of Windows-only tools or commands, the inclusion of PowerShell as a primary example language (with detailed configuration and code samples) can be seen as a subtle Windows bias, since PowerShell is most commonly associated with Windows environments. However, there are no missing Linux examples, and no Windows-specific tools or patterns are mentioned exclusively or prioritized before Linux equivalents.

Recommendations:

Clarify that PowerShell examples are cross-platform, as PowerShell Core runs on Linux and macOS as well as Windows.
Consider adding Bash or shell script examples if relevant for parity with PowerShell, especially in sections where scripting is demonstrated.
Explicitly mention that all code samples are platform-agnostic unless otherwise noted, to reassure Linux users.
If any setup, deployment, or CLI instructions are added in the future, ensure both Windows (PowerShell/CMD) and Linux (Bash) equivalents are provided.

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. However, there is a lack of parity for PowerShell: while a placeholder for PowerShell examples is present, no actual PowerShell (or platform-specific) samples are provided. There are no references to Windows-only tools, nor are Windows-specific instructions or patterns prioritized over Linux equivalents. All code samples are cross-platform (C#, JavaScript, Python), and there is no mention of Windows-specific behaviors or requirements. However, the absence of any Linux- or bash-specific examples or notes, especially in sections where PowerShell is mentioned, may leave Linux users underserved.

Recommendations:

If PowerShell samples are to be included, ensure equivalent bash or shell script examples are also provided for Linux users.
Explicitly state that all code samples are cross-platform unless otherwise noted.
If any platform-specific setup or troubleshooting is required (e.g., for local development), provide both Windows and Linux instructions.
When mentioning PowerShell, clarify its cross-platform availability or provide alternatives for Linux (such as bash).
Consider adding a section or note on running these samples on Linux/macOS, including any necessary environment setup or differences.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides code examples for C# and JavaScript, but for Python and PowerShell, it states that complete samples are pending. There are no explicit Windows-specific tools, commands, or PowerShell-heavy content, nor is there a 'Windows-first' ordering. However, the lack of Linux-oriented or cross-platform examples (especially for Python, which is popular on Linux) indicates a bias by omission.

Recommendations:

Add complete Python and PowerShell code samples to achieve parity with C# and JavaScript.
Ensure that any future troubleshooting or setup instructions include both Windows and Linux command-line examples (e.g., Bash and PowerShell).
Explicitly mention cross-platform compatibility where relevant, and avoid assuming a Windows environment.
If referencing configuration files or environment variables, provide examples for both Windows (e.g., %ENV_VAR%) and Linux/macOS (e.g., $ENV_VAR) syntax.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation exhibits mild Windows bias by mentioning Windows-specific Docker configuration before Linux, specifically noting that 'On Windows, Docker must also be configured to support Linux containers.' Additionally, PowerShell and Windows tools are referenced as automation options before Azure CLI, and there is an implicit assumption of familiarity with Windows conventions (e.g., line continuation character guidance). However, the majority of examples and commands are cross-platform (bash/curl/Docker), and Linux is not excluded from any instructions.

Recommendations:

Explicitly provide Linux-specific guidance alongside Windows notes, such as clarifying Docker installation and configuration steps for both platforms.
When mentioning automation options, list cross-platform tools (e.g., Azure CLI, bash scripts) before or alongside Windows-specific tools like PowerShell.
Where line continuation characters are discussed, provide both Windows (^) and Linux (\) examples, or link to platform-specific documentation.
Consider adding a short section or callout confirming that all commands are intended to work on both Linux and Windows (with Docker configured for Linux containers), and provide troubleshooting tips for both environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples or instructions, but it also omits any mention of Linux or cross-platform considerations. There are no explicit Windows or PowerShell examples, but the lack of Linux-specific guidance or parity checks could be seen as a subtle bias by omission.

Recommendations:

Add explicit instructions or examples for both Windows and Linux environments when discussing OS-level checks.
Mention common tools for both platforms (e.g., PowerShell for Windows, Bash/SSH for Linux) when suggesting how to perform connectivity or health checks.
Include sample commands or scripts for verifying server health, LUN accuracy, and configuration checks on both Windows and Linux.
Clarify that the guidance applies to both Windows and Linux Azure Large Instances, or specify any differences in procedures.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides HTTP request examples for querying datasets using the Web Feature Service but does not include any platform-specific command-line examples (such as curl, PowerShell, or CLI). However, it also does not provide Linux/Unix-specific examples or mention Linux tools, which may leave Linux users without clear guidance on how to perform these actions from their environment.

Recommendations:

Add example commands using curl (commonly available on Linux, macOS, and Windows) to demonstrate how to make the HTTP GET requests.
If providing platform-specific instructions, ensure parity by including both PowerShell (for Windows) and shell/curl (for Linux/macOS) examples.
Explicitly mention that the HTTP requests can be made from any platform using standard tools, and provide links or references to cross-platform tools where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally avoids OS-specific bias except in the 'Verify a custom domain' section, where the PowerShell (Windows) example is presented before the Bash (Linux/macOS) example. No other sections show Windows-specific tools, commands, or patterns, and Linux is explicitly mentioned in the DNS lookup example. There are no missing Linux examples or exclusive use of Windows tools.

Recommendations:

Present Bash (Linux/macOS) and PowerShell (Windows) examples in parallel tabs or alternate which comes first to avoid implicit prioritization.
In the 'Verify a custom domain' section, consider listing Bash first or side-by-side with PowerShell to ensure parity.
Continue to avoid OS-specific tooling unless necessary, and always provide equivalent examples for both Windows and Linux environments.
Explicitly mention that both Windows and Linux users are supported where relevant, to reinforce cross-platform inclusivity.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page provides only Azure Portal (GUI) instructions for subnet delegation and does not include any command-line examples. There is no mention of Windows-specific tools, but the absence of CLI (such as Azure CLI or PowerShell) examples means Linux users do not have parity, as they often rely on CLI tools for automation and scripting.

Recommendations:

Add Azure CLI examples for creating and delegating a subnet to Azure NetApp Files, as Azure CLI is cross-platform and widely used on Linux.
If including PowerShell examples, ensure they are presented alongside Azure CLI examples, not before them.
Explicitly mention that the steps can be performed using either the Azure Portal, Azure CLI, or PowerShell, and provide links or references to relevant CLI documentation.
Consider including sample scripts for both Azure CLI and PowerShell to cover both Linux and Windows users.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally avoids overt Windows bias, providing platform-neutral descriptions. However, in the 'Capacity utilization monitoring' section, it states: 'You can check the used and available capacity of a volume by using Windows or Linux clients.' The order of mention ('Windows or Linux') subtly prioritizes Windows, which is a minor instance of 'windows_first' bias. No explicit PowerShell-heavy examples, exclusive Windows tools, or missing Linux examples are present.

Recommendations:

When listing platforms, alternate or alphabetize (e.g., 'Linux or Windows clients') to avoid implicit prioritization.
Where possible, provide example commands for both Windows (e.g., PowerShell) and Linux (e.g., Bash) to ensure parity.
Explicitly mention cross-platform tools or interfaces (such as Azure CLI) and provide usage examples for both environments.
Review other documentation pages linked from this one to ensure that any referenced guides do not exhibit stronger Windows bias.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only portal-based (GUI) instructions and does not include any command-line examples for managing tags or billing data. There are no examples using PowerShell, Azure CLI, or other tools. However, the absence of Azure CLI (cross-platform) or Linux-specific instructions means Linux users do not have parity with potential Windows users who might expect PowerShell or CLI options.

Recommendations:

Add Azure CLI examples for adding, editing, and viewing tags on capacity pools, as Azure CLI is cross-platform and widely used on Linux.
Include instructions for downloading and processing billing/tag data using command-line tools (e.g., az costmanagement, curl, jq) suitable for Linux environments.
If PowerShell examples are added in the future, ensure equivalent Azure CLI or Bash examples are provided alongside.
Explicitly mention that all portal-based steps are platform-agnostic, but provide links or references to CLI documentation for users who prefer or require command-line automation.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation exhibits a subtle Windows bias by referencing the 'default Windows plan' (Workflow Standard WS1) as the primary hosting option for Azure Logic Apps, including its Windows-centric specifications (ACU, memory, vCPU). There are no explicit PowerShell commands, Windows-only tools, or examples, but the mention of the Windows plan occurs without mention of Linux-based hosting options or parity.

Recommendations:

Explicitly mention both Windows and Linux hosting plans for Azure Logic Apps, including their specifications and suitability for this workflow.
Provide guidance or notes for users who may wish to use a Linux-based Logic App plan, including any differences in configuration or compatibility.
Ensure that any default plan references are neutral or provide equal visibility to Linux options.
If there are platform-specific considerations (e.g., certificate handling, environment variables), document these for both Windows and Linux hosting environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation presents both Windows and Linux command examples for activating the environment, but the Windows-based example is listed first. There is no exclusive use of Windows tools or missing Linux examples, but the ordering suggests a subtle preference for Windows.

Recommendations:

Alternate the order of Windows and Linux examples in different sections, or present them side-by-side to avoid implying preference.
Explicitly state that both Windows and Linux are equally supported.
Where possible, provide combined or OS-agnostic instructions before OS-specific commands.
Ensure parity in troubleshooting and tool references for both platforms.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific command-line examples, but it implicitly assumes the use of generic DNS server management without mentioning any tools or commands for either Windows or Linux. However, when discussing conditional forwarders, it refers to 'your on-premises DNS server' without specifying whether this is Windows DNS, BIND, or another platform, and does not provide any Linux/BIND examples or guidance. This omission can be considered a 'missing_linux_example' bias, as Windows DNS is often the default assumption in enterprise environments, and Linux/BIND users are left without parity guidance.

Recommendations:

Explicitly mention both Windows DNS Server and Linux/BIND as supported DNS server options for on-premises environments.
Provide example steps or links for configuring conditional forwarders in both Windows DNS Server (via GUI or PowerShell) and Linux/BIND (editing named.conf).
Clarify that the Azure DNS Private Resolver can be integrated with both Windows and Linux DNS infrastructures.
Where DNS server configuration is referenced, include brief sample configuration snippets for both platforms, or link to relevant Microsoft and BIND documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples, commands, or tooling, but it also does not include any practical configuration steps (such as CLI commands or scripts) at all. As a result, there is no explicit Windows bias, but there is a lack of parity in that no Linux (or Windows) command-line or configuration examples are given, which could disadvantage Linux users if future updates add only Windows/Powershell examples.

Recommendations:

When adding practical configuration steps, ensure that both Azure CLI (cross-platform) and PowerShell examples are provided.
If referencing tools for connectivity testing or troubleshooting, include both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash, curl, ip, traceroute) equivalents.
Explicitly mention that the steps are platform-agnostic where possible, or clarify any OS-specific requirements.
Consider including sample scripts or commands for both Linux and Windows environments when demonstrating network configuration or verification.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples, scripts, or command-line instructions. All configuration steps are described as GUI operations within the Azure portal, and there are no references to Windows, PowerShell, or Windows-specific tools. However, the guide also omits any mention of Linux or cross-platform command-line approaches, such as Azure CLI or REST API usage. This lack of parity may disadvantage users who prefer or require automation or non-GUI workflows, which are common in Linux environments.

Recommendations:

Add Azure CLI examples for creating ExpressRoute authorizations and peering, as the CLI is cross-platform and widely used in Linux environments.
Include REST API sample calls for each major step, allowing users to automate the process regardless of their OS.
Explicitly mention that all steps can be completed via the Azure portal, PowerShell, or Azure CLI, and provide links to relevant CLI and PowerShell documentation.
Where screenshots or instructions reference the Azure portal, consider adding equivalent command-line instructions for parity.
Clarify that no OS-specific tools are required, and highlight cross-platform options for managing ExpressRoute and Azure VMware Solution resources.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides configuration instructions exclusively via the Azure Portal (web UI) and Bicep templates, with no command-line examples for either Windows (e.g., PowerShell, Command Prompt) or Linux (e.g., Bash, Azure CLI). However, the absence of any CLI-based instructions or examples (such as Azure CLI commands) constitutes a bias of omission, as Linux users typically rely on CLI tools for automation and scripting. This results in a lack of parity for Linux users who may prefer or require command-line instructions.

Recommendations:

Add Azure CLI examples for each configuration scenario (public network access, default action, request type rules, IP rules), as Azure CLI is cross-platform and widely used on Linux.
Where possible, provide Bash shell scripts or command snippets to demonstrate automation workflows.
Explicitly mention that all instructions are applicable to both Windows and Linux when using the Azure Portal or Bicep, but highlight CLI alternatives for Linux users.
Consider including PowerShell examples for Windows users only if Azure CLI is also provided for Linux users, ensuring parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only Azure CLI and Azure Portal instructions, with no explicit Windows or PowerShell bias. However, it lacks any Linux-specific examples or terminal/shell guidance, which may disadvantage Linux users who commonly manage AKS clusters. The 'Next steps' section links to a PowerShell guide but does not mention Bash or Linux shell equivalents.

Recommendations:

Add explicit Linux/Bash shell examples where relevant, especially for Azure CLI commands (e.g., show both Windows CMD/PowerShell and Bash syntax for environment variables, command substitution, etc.).
Clarify that Azure CLI commands are cross-platform and provide notes or tips for Linux/macOS users (e.g., differences in command substitution: $(...) vs %...%).
Include links to Linux/Bash-specific AKS backup documentation in the 'Next steps' section, or clarify that the Azure CLI instructions are suitable for Linux/macOS.
If any scripts or automation are referenced, provide both PowerShell and Bash versions.
Explicitly state platform compatibility at the start of the article to reassure non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation is largely cross-platform, using Azure CLI commands and Bash variable syntax, which are compatible with both Windows and Linux. However, there is one instance where a Windows-specific file path ('.\OSSBkpInstance.JSON') is used in a command example, which may confuse Linux users who expect './OSSBkpInstance.JSON'. No PowerShell-specific commands or Windows-only tools are present, but the single use of a Windows path separator suggests a subtle 'windows_first' bias.

Recommendations:

Replace Windows-style file paths (e.g., '.\OSSBkpInstance.JSON') with POSIX-style paths (e.g., './OSSBkpInstance.JSON'), or provide both variants to accommodate both Windows and Linux users.
Explicitly state that the Azure CLI commands work on both Windows and Linux, and clarify any platform-specific differences in file paths or environment variable syntax.
Where file paths or shell syntax are shown, consider using cross-platform conventions or add notes for both environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page does not show overt Windows bias in terms of examples or tools (e.g., no PowerShell, CMD, or Windows-specific tooling is present). However, there is a subtle bias in the use of 'Pacific Standard Time' as the default time zone in several example request bodies, and in the ordering of examples (e.g., Azure VM, SQL in Azure VM, SAP HANA in Azure VM) which are most commonly associated with Windows workloads. There are no explicit Linux or cross-platform command-line examples, but since the page is focused on REST API usage, this is less critical. No Linux-specific examples or references are missing, but the use of a Windows-centric time zone as a default may suggest a slight Windows-first orientation.

Recommendations:

Use 'UTC' as the default time zone in all examples to avoid regional or OS-specific bias.
Explicitly mention that the REST API is platform-agnostic and can be used from any OS or environment.
If possible, provide example REST API invocations using common cross-platform tools (e.g., curl, HTTPie) to reinforce platform neutrality.
Consider including a note or example for Linux administrators, especially if there are any platform-specific considerations for time zones or date formats.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally maintains platform neutrality, but in the 'Install the VM agent' section, instructions for Windows are presented before Linux. Both platforms are covered with similar detail, and no exclusive use of Windows tools, PowerShell, or missing Linux examples are observed elsewhere in the document.

Recommendations:

Present Linux and Windows instructions in parallel columns or in the order most relevant to the audience, or alternate which platform appears first in different sections.
Ensure that any command-line or scripting examples (if added in the future) include both Windows (PowerShell/Command Prompt) and Linux (Bash/CLI) equivalents.
Continue to avoid exclusive references to Windows tools or patterns unless there is no Linux equivalent, and always provide Linux alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_tools

Summary:

The documentation is largely platform-neutral, focusing on REST API usage and JSON payloads. However, there is a subtle Windows bias in the mention of the 'default PowerShell object' for PostgreSQL - Flexible servers, implying PowerShell as a reference implementation or default tool. There are no explicit Linux or cross-platform CLI examples, and no mention of Linux-native tools or shell environments.

Recommendations:

Remove or rephrase references to 'default PowerShell object' to avoid implying PowerShell is the primary or only supported tool.
Add equivalent examples or references for Linux users, such as using curl or HTTPie to make REST API calls.
Explicitly mention that the REST API can be used from any platform, and provide sample commands for both Windows (PowerShell) and Linux/macOS (bash/curl).
If referencing scripting or automation, provide both PowerShell and bash script snippets where relevant.

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 show any examples for Linux users, despite SGX enclaves being commonly used on Linux. There is no explicit Windows bias, but the absence of Linux-specific guidance or parity examples is a notable omission.

Recommendations:

Include explicit examples or references for both Windows and Linux environments, especially for common developer tasks such as running attestation commands or setting up the environment.
Clarify whether the attestation process or sample code is platform-agnostic, or provide separate instructions for each supported OS.
Link to or provide sample scripts for Linux (bash) as well as Windows (PowerShell), if applicable.
Mention any platform-specific prerequisites or differences in the attestation process for Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page exclusively describes how to audit and enforce backup for Managed Disks using the Azure Portal UI, without providing any command-line examples. There is no mention of PowerShell, Windows tools, or Windows-specific patterns, but there is also a lack of parity for Linux users, as no Azure CLI or Bash examples are provided. This omission can disadvantage users who prefer or require command-line automation, especially on Linux or cross-platform environments.

Recommendations:

Add Azure CLI examples for assigning and managing Azure Policies related to Managed Disks backup, ensuring that Linux and cross-platform users can follow along without relying on the Azure Portal.
Include Bash script snippets for common policy assignment and remediation tasks.
Explicitly mention that all steps can be performed via Azure CLI or ARM templates, and provide links or examples.
Ensure that screenshots and instructions are balanced between portal and command-line approaches to support both Windows and Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not explicitly show Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-first patterns. However, it lacks any platform-specific examples or guidance, and does not provide Linux-specific instructions or examples for handling linked Resource Manager templates in CI/CD pipelines. This absence can be considered a subtle bias, as it assumes platform neutrality but does not confirm Linux parity or address potential differences in scripting, tooling, or environment setup.

Recommendations:

Add explicit examples for both Windows (e.g., PowerShell, Azure CLI on Windows) and Linux (e.g., Bash, Azure CLI on Linux) for uploading linked templates and managing SAS tokens.
Include notes or sections on any platform-specific considerations (such as file path formats, environment variable handling, or script execution differences) that may affect Linux users.
Provide sample scripts or commands for common Linux CI/CD environments (e.g., Azure Pipelines with Ubuntu agents, GitHub Actions runners on Linux) to demonstrate parity.
Clarify that the instructions are platform-agnostic if that is the case, or explicitly state any limitations or differences for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation is largely cross-platform, focusing on Azure CLI commands, which are available on both Windows and Linux. However, there is a subtle Windows bias in one example output, where the command prompt path (C:\Users\testuser\Downloads\CLIForAFS\azure-cli>) is shown, suggesting a Windows environment. No PowerShell-specific commands or Windows-only tools are used, and all command examples are in Azure CLI syntax. There are no missing Linux examples, but the presence of a Windows file path in an example may make Linux users feel less directly addressed.

Recommendations:

Replace or supplement Windows-style command prompt paths (e.g., C:\Users\...) in example outputs with generic or Linux-style paths (e.g., /home/user/...), or use a neutral prompt (e.g., $ or azcli>) to reinforce cross-platform applicability.
Add a brief note at the start clarifying that all Azure CLI commands work identically on Windows, Linux, and macOS.
Where file paths are referenced (such as for JSON policy files), provide both Windows and Linux path examples, or use relative paths.
Avoid including OS-specific shell prompts or environment details in outputs unless demonstrating OS-specific behavior.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively uses Azure Portal (GUI) instructions and screenshots, with no command-line examples provided for either Windows (PowerShell/Command Prompt) or Linux (Bash/CLI). However, there is an implicit bias due to the absence of any Linux-specific guidance or CLI-based workflows, which are commonly preferred by Linux users and administrators. There are no references to Windows tools, but the lack of parity for Linux command-line usage is a notable gap.

Recommendations:

Add Azure CLI examples for each major step, as the Azure CLI is cross-platform and widely used by Linux administrators.
If PowerShell examples are provided in the future, ensure equivalent Bash/Azure CLI examples are included and presented with equal prominence.
Explicitly mention that all steps can be performed via the Azure CLI or provide links to relevant CLI documentation.
Include notes or sections addressing automation and scripting for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides both Windows and Linux VM quickstart links and mentions both RDP (Windows) and SSH (Linux) ports, but in the prerequisites, the Windows VM creation link is listed before the Linux VM link. There are no command-line (PowerShell or Bash) examples at all, and no Windows-specific tools or patterns are emphasized. The overall structure is neutral, but the ordering of Windows before Linux in the prerequisites is a subtle 'windows_first' bias.

Recommendations:

List Linux and Windows VM creation links in alternating order across documentation, or list Linux first in some instances to balance exposure.
Explicitly state that the steps apply equally to both Windows and Linux VMs where relevant.
If providing future examples or screenshots, ensure parity by including both Windows and Linux scenarios.
Consider adding a note or section clarifying that Bastion supports both SSH (Linux) and RDP (Windows) equally, with links to connection guides for both.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any command-line examples or tooling instructions for rotating Batch account keys, nor does it mention any platform-specific tools. However, it also does not provide any examples for Linux or cross-platform command-line usage, such as Azure CLI or Bash, which are commonly used on Linux. The only method described is via the Azure portal, which is platform-agnostic, but the absence of CLI or script-based examples may disadvantage Linux users who prefer or require automation.

Recommendations:

Add Azure CLI examples for rotating Batch account keys, as the CLI is cross-platform and widely used on Linux.
Include PowerShell examples only if paired with equivalent Bash or CLI examples.
Explicitly mention that the Azure portal method works on all platforms, but provide automation options for users who do not use a GUI.
Consider adding a section on scripting key rotation for CI/CD pipelines, with both Linux (Bash/CLI) and Windows (PowerShell) examples.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation claims to cover both Linux and Windows pools but does not provide any concrete examples or instructions for either platform. However, it notably lacks any Linux-specific guidance or examples for mounting Azure file shares, which is a common area where Windows/PowerShell examples are often prioritized or exclusively provided.

Recommendations:

Add explicit, step-by-step instructions for mounting Azure file shares on Linux Batch pool nodes, including example commands (e.g., using mount.cifs or SMB utilities).
Ensure parity by providing both Linux (bash/CLI) and Windows (PowerShell/GUI) examples side by side.
Reference Linux-specific troubleshooting and best practices for Azure Files (e.g., required packages, handling credentials securely).
Clearly indicate in each section which instructions apply to Linux, Windows, or both.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only C# code examples and general Azure Batch concepts, with no mention of Windows-specific tools or patterns. However, it lacks any Linux- or cross-platform-specific examples, shell commands, or references to Linux environments, which may make it less accessible to users working in Linux or non-Windows environments.

Recommendations:

Add equivalent Linux shell (bash) or Python examples for creating and using resource files, especially for common scenarios like downloading files from Azure Storage.
Include notes or sections on how resource files are handled on Linux Batch nodes, such as file permissions, path conventions, or troubleshooting tips.
Reference cross-platform tools (e.g., az CLI, curl, wget) alongside or instead of Windows-centric tools.
Explicitly state that the examples are cross-platform where applicable, or provide guidance for both Windows and Linux users.
If PowerShell or Windows command-line examples are added in the future, ensure Linux equivalents are provided in parallel.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or tooling instructions, but it also does not include any Linux-specific guidance or examples. There are no explicit Windows or PowerShell commands, but the absence of any example commands or scripts (for either Windows or Linux) means Linux users are not directly supported with parity.

Recommendations:

Add example commands for retrieving the POP IP list using common Linux tools (e.g., curl, wget, jq) to demonstrate how to automate the retrieval process.
If providing example scripts, ensure both Windows (PowerShell) and Linux (bash) versions are included.
Mention cross-platform tools and approaches where possible, such as REST API calls using platform-agnostic methods.
Clarify that the instructions apply equally to both Windows and Linux environments, or specify any differences if they exist.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page only describes how to purge an Azure CDN endpoint using the Azure Portal (web UI) and does not provide any command-line examples. There is no mention of PowerShell, Windows tools, or Windows-specific patterns, but there is also a lack of parity for Linux users, as there are no CLI (Azure CLI, Bash, etc.) or REST API command examples that could be run on Linux or cross-platform environments. The only programmatic reference is a link to the REST API documentation in the 'Next steps' section, without any example provided.

Recommendations:

Add Azure CLI examples for purging a CDN endpoint, as the Azure CLI is cross-platform and works on Linux, macOS, and Windows.
Provide REST API usage examples (e.g., using curl or HTTPie) to demonstrate how to purge a CDN endpoint programmatically from any OS.
If PowerShell or Windows-specific tools are ever referenced, ensure equivalent Bash or shell examples are provided.
Explicitly mention that the Azure Portal method is OS-agnostic, but highlight CLI and API options for automation and scripting on Linux.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally avoids platform-specific bias, as it focuses on the Azure Cloud Shell interface, which is cross-platform. However, in the 'Copy and paste' section, Windows instructions are listed first, followed by macOS and Linux. No PowerShell-specific bias or exclusive mention of Windows tools is present, and Linux instructions are included where relevant.

Recommendations:

List copy/paste instructions in a neutral or alphabetical order (e.g., Linux, macOS, Windows) to avoid the perception of Windows-first bias.
Where platform-specific shortcuts or behaviors are mentioned, ensure equal prominence and detail for Linux and macOS.
Continue to avoid exclusive references to Windows tools or patterns, and ensure all examples and instructions are equally applicable to Bash/Linux and PowerShell/Windows environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific troubleshooting commands, examples, or tools. However, it also omits any mention of Linux-specific tools or command-line instructions, which may be relevant since containers often run on Linux. The absence of both Windows and Linux examples means there is no explicit Windows bias, but the lack of Linux parity (e.g., shell commands, log file locations) is a missed opportunity.

Recommendations:

Add example troubleshooting steps using common Linux commands (e.g., checking mount points with 'mount' or 'df', inspecting logs with 'cat /var/log/syslog', etc.).
Include references to both Linux and Windows environments if relevant, clarifying any OS-specific behaviors or error messages.
Provide sample error messages or diagnostic outputs from both Linux-based and Windows-based containers, if supported.
Mention where to find logs or diagnostic information inside the container for both Linux and Windows containers.

Create pull request

Bias Types:

⚠️ powershell_heavy

Summary:

The documentation page is generally neutral and cross-platform, focusing on Azure Logic Apps built-in connectors without favoring Windows or Linux. However, in the 'Run code from workflows' section, PowerShell script execution is specifically called out as a supported option (alongside JavaScript and C#), which may indicate a slight Windows bias, as PowerShell is more commonly associated with Windows environments. There are no explicit Windows-only tools, examples, or patterns, and Linux equivalents are not omitted, but the mention of PowerShell without a corresponding Bash or Linux shell scripting example could be seen as a minor bias.

Recommendations:

Add examples or documentation for running Bash or other Linux shell scripts as inline code or via connectors, if supported.
Clarify whether PowerShell script execution is cross-platform (i.e., works with PowerShell Core on Linux) or Windows-only.
If only PowerShell is supported for scripting, consider explaining the rationale and providing guidance for Linux users.
Ensure that any scripting or code execution features highlight both Windows and Linux options where possible, or explicitly state platform limitations.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation uses Azure CLI examples throughout, which are generally cross-platform. However, there is a subtle Windows bias in the Bicep deployment section: the CLI example for deploying the Bicep file uses PowerShell-style backticks (`) for line continuation, which is specific to Windows/PowerShell. No equivalent Bash (Linux/macOS) example is provided. Additionally, references to 'cmdlets from the Az.App module in PowerShell' are mentioned before CLI commands, and there is no explicit mention of Linux shell usage or examples.

Recommendations:

For all CLI command examples, provide both Bash (\) and PowerShell (`) line continuation variants, or use single-line commands to avoid platform-specific syntax.
When mentioning PowerShell modules or cmdlets, also mention Bash/Azure CLI equivalents, and clarify which environments each applies to.
Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary notes for cross-platform usage.
Where environment variables are set, clarify syntax differences (e.g., $VAR for Bash, $env:VAR for PowerShell) if relevant.
Consider adding a 'Platform differences' note or section to highlight any OS-specific considerations.

Create pull request

Bias Types:

⚠️ windows_tools

Summary:

The documentation is generally neutral and cross-platform, as it focuses on Azure Logic Apps' web-based designer and JSON definitions. However, there is a subtle Windows bias in the reference to time zones: the documentation links to a Microsoft Docs page listing Windows time zone identifiers and refers to 'Pacific Standard Time' as an example, which is a Windows-specific time zone ID. No Linux or IANA time zone equivalents are mentioned, and the only time zone reference is to a Windows-centric resource.

Recommendations:

When referencing time zones, mention both Windows time zone IDs and IANA/Olson time zone names, or clarify which are supported by Azure Logic Apps.
Provide a link or reference to IANA time zone documentation (e.g., https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) and clarify if only Windows time zones are accepted.
In examples, consider using UTC or ISO 8601 time zone formats, or explicitly note the mapping between Windows and IANA time zones for cross-platform clarity.
Add a note for Linux/macOS users that Windows time zone IDs may differ from those on their systems, and provide guidance or a mapping table if appropriate.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not show explicit Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-first patterns. However, it lacks Linux-specific examples, commands, or references, and does not address cross-platform development or deployment nuances. The documentation implicitly assumes a platform-agnostic environment but misses opportunities to demonstrate parity by including Linux (or macOS) specific instructions or considerations.

Recommendations:

Add explicit examples or notes for Linux/macOS users, such as common CLI commands (e.g., docker, az CLI) run from Bash or zsh.
Clarify that the instructions and code samples are cross-platform, and mention any platform-specific prerequisites or differences where relevant.
Include references to developing and deploying from Linux or macOS environments, not just Visual Studio (which is Windows-centric), such as Visual Studio Code or JetBrains Rider.
If any tooling or configuration steps differ between Windows and Linux containers (e.g., file system paths, environment variable syntax), call these out explicitly.
Provide links to official .NET and Azure documentation that cover Linux containerization and deployment workflows.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively uses Azure Portal (GUI) instructions and does not provide any command-line examples for either Windows (PowerShell/CLI) or Linux (Bash/CLI). However, this omission results in a lack of parity for Linux users, as there are no Bash/Azure CLI examples, which are commonly used on Linux. There is no explicit Windows bias (no PowerShell, Windows tools, or Windows-first ordering), but the absence of CLI examples is a missed opportunity to support Linux workflows.

Recommendations:

Add Azure CLI (Bash) command-line examples for all major steps (e.g., creating DNS zones, Application Gateway, backend pools, routing rules, and resource cleanup).
Where possible, provide both Azure CLI and PowerShell equivalents, but ensure CLI (Bash) examples are present and not secondary.
Explicitly mention that all steps can be performed via CLI on Linux, and link to relevant Azure CLI documentation.
Consider adding a 'Command-line (CLI)' tab alongside the GUI instructions for each major section.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific commands or examples, but it also does not mention or demonstrate how to upload files to Azure Blob Storage using command-line tools or scripts. The only reference for uploading files is a link to a portal-based quickstart, which is typically Windows-centric and GUI-based. There are no examples for Linux users (e.g., using azcopy, Azure CLI, or Python scripts), which may leave Linux users without clear guidance.

Recommendations:

Add explicit examples for uploading files to Azure Blob Storage using cross-platform tools such as Azure CLI, azcopy, or Python scripts.
Include both GUI (portal) and command-line instructions, making it clear which methods are OS-agnostic.
Where possible, provide sample commands for both Windows and Linux/macOS terminals to ensure parity.
Mention that the Azure portal is accessible from any OS, but also highlight CLI alternatives for users who prefer or require command-line operations.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page for Azure Data Factory's Copy activity does not display overt Windows bias in terms of language, tools, or ordering of examples. However, it lacks any platform-specific examples or instructions, such as how to set up or use the self-hosted integration runtime on Linux, or how to perform related tasks from a Linux environment. The only platform-specific reference in the 'Related content' section is a tutorial for hybrid copy using PowerShell, which is primarily a Windows tool, with no Linux or cross-platform equivalent tutorial linked.

Recommendations:

Add explicit examples or references for Linux environments, such as how to install and configure the self-hosted integration runtime on Linux.
Include links to tutorials or quickstarts that use Linux-native tools (e.g., Bash, shell scripts) or cross-platform approaches (e.g., Azure CLI).
In the 'Related content' section, balance PowerShell/Windows-focused tutorials with Linux-focused or cross-platform guides.
Wherever platform-specific instructions are needed (e.g., setting up integration runtime, troubleshooting), provide both Windows and Linux steps or clearly indicate cross-platform compatibility.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation assumes the use of a 'Self-hosted Integration Runtime machine' and instructs users to download and install the Informix 64-bit Client SDK to set up an ODBC connection, but does not specify or provide guidance for Linux environments. There are no explicit references to Windows, but the lack of Linux-specific instructions or examples (such as how to install the Informix Client SDK or configure ODBC on Linux) suggests a bias toward Windows environments.

Recommendations:

Add explicit instructions for setting up the Informix Client SDK and ODBC connections on Linux-based Integration Runtime hosts, including package names, installation commands, and configuration file locations.
Include Linux-specific examples for configuring DSNs and environment variables.
Clarify in the prerequisites section that both Windows and Linux are supported, and provide links or references to official IBM documentation for Linux installation.
If there are limitations or differences in Linux support, document them clearly.

Create pull request

Bias Types:

⚠️ windows_tools

Summary:

The documentation is largely cross-platform and neutral, but there is a subtle Windows bias in the SSH key conversion guidance: it mentions only the PuTTY tool (a Windows utility) for converting PPK to OpenSSH format, without referencing Linux or macOS alternatives. Additionally, the only explicit file path example for private keys uses a Windows-style path (D:\privatekey_openssh), with no Linux-style path shown. There are no PowerShell or Windows command-line examples, but the implicit assumption of Windows tooling and paths may disadvantage Linux users.

Recommendations:

When mentioning conversion from PPK to OpenSSH format, include Linux/macOS alternatives such as 'use the ssh-keygen tool on Linux/macOS to convert keys' or provide a command-line example.
Provide both Windows and Linux-style file path examples for properties like privateKeyPath (e.g., 'D:\privatekey_openssh' and '/home/user/.ssh/id_rsa').
If referencing tools, mention cross-platform or platform-specific options equally, and avoid assuming the user is on Windows.
Consider adding a note or section clarifying that all features and configuration steps are supported on both Windows and Linux self-hosted integration runtimes, if applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias such as PowerShell-heavy examples or exclusive mention of Windows tools. However, it references 'network monitor (netmon) trace' for troubleshooting, which is a Windows-specific tool, and does not provide equivalent instructions or tool suggestions for Linux environments. There are no command-line examples (Windows or Linux), but the troubleshooting steps assume familiarity with Windows-centric tooling.

Recommendations:

When suggesting the use of 'network monitor (netmon) trace', also mention equivalent Linux tools such as 'tcpdump' or 'Wireshark', and provide brief instructions or links for capturing network traces on Linux.
Where troubleshooting steps require system-level diagnostics, ensure both Windows and Linux approaches are described.
Review the documentation for any other implicit assumptions of a Windows environment and add Linux alternatives where appropriate.
If providing JSON configuration or code snippets, clarify that these are platform-agnostic, or note any platform-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page exhibits a subtle 'windows_first' bias, primarily in the default values and terminology for row delimiters (e.g., '\r\n' as the default for writing, which is the Windows line ending). There is also a reference to file encodings with 'WINDOWS-' prefixes and a link to a .NET (Windows-centric) API for compression levels. However, there are no explicit Windows-only tools, PowerShell examples, or exclusive mention of Windows patterns. Linux/Unix equivalents are not omitted, but Windows conventions are presented as defaults or primary references.

Recommendations:

Explicitly mention both Windows (\r\n) and Unix/Linux (\n) line endings as equally supported and clarify when each is used.
Provide examples or notes for common Linux/Unix usage patterns (e.g., using '\n' as a row delimiter, or file naming conventions).
When listing encodings, clarify that 'WINDOWS-' encodings are for compatibility and mention Linux/Unix equivalents.
Where documentation links to Windows/.NET APIs (e.g., compression), also reference cross-platform or Linux-relevant documentation if available.
Add a short section or note on cross-platform considerations, especially for users moving files between Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_tools

Summary:

The documentation page is largely platform-neutral and does not provide OS-specific examples or instructions. However, there is a subtle Windows bias in the encodingName property list, which includes several 'WINDOWS-xxxx' encodings and many IBM codepages, but does not explicitly mention Linux/Unix-specific encodings or reference their usage. Additionally, the only external reference for compression level points to the .NET API documentation, which is more familiar to Windows users.

Recommendations:

When listing encoding options, clarify that the 'WINDOWS-xxxx' encodings are supported cross-platform and mention common Linux/Unix encodings (such as 'UTF-8', 'ISO-8859-1', etc.) explicitly as being supported.
Where external documentation is referenced (such as compression levels), provide links or context for equivalent concepts/tools on Linux (e.g., reference gzip/bzip2 CLI tools or man pages).
If mentioning codepages or encodings, briefly note their typical platform associations (e.g., 'WINDOWS-1252 (common on Windows), ISO-8859-1 (common on Linux/Unix)'), to help users from all platforms understand applicability.
If relevant, add examples or notes for using JSON files and compression with Linux tools (e.g., using jq, gzip, tar) in the context of Azure Data Factory pipelines.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not display explicit Windows bias in terms of command-line examples, tools, or terminology. However, it omits any mention of Linux or cross-platform considerations for the self-hosted integration runtime, which is a critical component that can run on both Windows and Linux. There are no examples, screenshots, or instructions that clarify platform-specific steps or requirements, potentially leaving Linux users without guidance.

Recommendations:

Add a section clarifying that the self-hosted integration runtime can be installed and run on both Windows and Linux, with links to relevant installation guides for each platform.
Include platform-specific notes or screenshots where differences exist (e.g., service installation, runtime configuration).
If any troubleshooting or log collection steps are referenced (such as in the related content), ensure Linux paths and commands are included alongside Windows equivalents.
Explicitly state that the instructions are platform-agnostic, or provide parallel instructions for both Windows and Linux where applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively uses the Azure Portal (web UI) for all configuration steps and does not provide any command-line examples. There are no references to Windows-specific tools or PowerShell, but there is also a complete absence of CLI-based instructions (such as Azure CLI or Bash), which are commonly used in Linux environments. This omission may disadvantage Linux users or those who prefer automation and scripting.

Recommendations:

Add equivalent Azure CLI command-line instructions for all major steps (creating private endpoints, approving/rejecting connections, etc.), as Azure CLI is cross-platform and widely used on Linux.
Include Bash script examples where appropriate to demonstrate automation of these tasks.
Explicitly mention that all portal-based steps can also be performed via CLI, and provide links to relevant Azure CLI documentation.
Ensure screenshots or instructions do not assume a Windows-only environment (e.g., avoid referencing Windows file paths or tools in future updates).

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation gives instructions for safely removing disks with 'Windows systems' mentioned first, followed by Linux. Both platforms are acknowledged, but the ordering prioritizes Windows. No PowerShell-specific commands or Windows-only tools are present, and Linux is not omitted.

Recommendations:

Present Windows and Linux instructions in parallel or alternate the order to avoid implicit prioritization.
Where possible, provide explicit commands for both platforms (e.g., for 'safely remove disks'), and clarify if the Windows step refers to a specific GUI or command-line action.
Consider including macOS instructions if the product supports it, or explicitly state platform limitations.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation presents the Windows VM password reset steps before the Linux VM steps, even though the procedures are nearly identical. There are no exclusive Windows tools, PowerShell commands, or missing Linux examples, but the ordering subtly prioritizes Windows.

Recommendations:

Alternate the order of Windows and Linux sections in similar documentation, or present both procedures in parallel to avoid implicit prioritization.
Explicitly state that the steps are identical for both OS types, highlighting any differences only where necessary.
Ensure that any references to command-line or scripting methods (e.g., PowerShell) are always paired with equivalent Linux (e.g., Bash/CLI) instructions in linked articles.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not explicitly mention or provide examples for either Windows or Linux environments when configuring the host computer or network settings. However, it implicitly assumes a generic setup and omits any OS-specific instructions or examples. This results in a 'missing_linux_example' bias, as there are no Linux-specific commands or guidance for configuring network interfaces, which is a common point of divergence between Windows and Linux users.

Recommendations:

Add explicit instructions for configuring the host computer's Ethernet adapter on both Windows and Linux (e.g., using Windows network settings and Linux ifconfig/ip commands).
Include screenshots or terminal commands for Linux network configuration alongside any Windows examples.
Clarify that the setup process is OS-agnostic where possible, but provide parity in examples for both major platforms.
If any device management tools or utilities are required, specify cross-platform alternatives or note any differences in usage between Windows and Linux.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions for connecting to the Azure Stack Edge Pro 2 device but does not specify or provide examples for Linux users. Steps such as configuring the Ethernet adapter and handling browser security warnings are described generically, but there are no Linux-specific commands, screenshots, or troubleshooting notes. The lack of explicit Linux guidance may make it harder for non-Windows users to follow the tutorial.

Recommendations:

Add explicit instructions for configuring a static IP address on Linux (e.g., using nmcli, ifconfig, or editing /etc/network/interfaces).
Include Linux-specific notes or screenshots for handling browser certificate warnings.
Mention any differences in browser behavior or network configuration tools between Windows, Linux, and macOS.
Provide troubleshooting tips for common issues encountered on Linux systems.
Ensure parity by including both Windows and Linux (and optionally macOS) steps wherever OS-specific actions are required.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not show overt Windows bias in terms of tools, commands, or examples, but it lacks parity by not providing any OS-specific troubleshooting steps or examples for either Windows or Linux. While SMB/NFS shares are mentioned (which are cross-platform), there are no explicit examples or guidance for Linux users, such as command-line instructions or references to Linux-specific tools. The only OS-specific mention is 'Symbolic links aren't allowed in Linux', which is presented as a limitation rather than guidance. There are no PowerShell commands, Windows tool references, or Windows-first patterns, but the absence of Linux examples or troubleshooting steps constitutes a subtle bias.

Recommendations:

Add explicit troubleshooting examples for both Windows and Linux environments, such as sample commands for renaming files or folders using Windows Explorer, PowerShell, Linux shell (mv), etc.
Include references to common Linux tools (e.g., find, mv, ls) for identifying and correcting naming issues.
Provide guidance for mounting SMB/NFS shares on both Windows (using File Explorer or net use) and Linux (using mount command), ensuring parity.
Clarify any OS-specific behaviors or limitations for both platforms, not just Linux.
Where screenshots are provided, include both Windows and Linux UI/CLI equivalents where applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively uses Azure Portal (GUI) instructions and screenshots, with no command-line examples provided for any platform. While this avoids explicit Windows or PowerShell bias, it also omits parity for Linux users who may prefer or require CLI-based workflows (e.g., Azure CLI, Bash). There are no references to Windows-specific tools, but the absence of CLI instructions constitutes a bias by omission, as many cross-platform users expect or require non-GUI alternatives.

Recommendations:

Add equivalent Azure CLI instructions for all major steps (e.g., assigning managed identities, setting role assignments, configuring Key Vault access).
Ensure CLI examples are presented in a cross-platform manner (e.g., using Bash syntax, not PowerShell).
Where possible, provide both Portal (GUI) and CLI workflows, and indicate that the CLI steps work on Windows, Linux, and macOS.
Explicitly mention that all steps can be performed via the Azure CLI, and link to relevant Azure CLI documentation.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation mentions the Windows generalization tool (Sysprep) before the Linux equivalent (deprovision), and the parenthetical note '(Run sysprep)' for Windows appears before '(Run deprovision)' for Linux. However, both platforms are mentioned and linked, and no platform-specific commands or tools are otherwise favored.

Recommendations:

Present Windows and Linux options in parallel or alternate the order to avoid always listing Windows first.
Provide explicit step-by-step instructions or links for both Sysprep (Windows) and waagent deprovision (Linux), ensuring equal detail.
Include screenshots or examples for both Windows and Linux generalization processes if applicable.
Use neutral phrasing such as 'for Windows (Sysprep) or Linux (deprovision)' or 'for Linux (deprovision) or Windows (Sysprep)' to balance representation.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on using the Azure portal UI to attach and detach data disks, without providing any OS-specific (Windows or Linux) command-line examples. However, it omits any mention of post-attachment steps required inside the VM, such as mounting and formatting disks, which differ between Windows and Linux. This omission can disadvantage Linux users, as the process for making a new disk usable is not covered for either OS, but is especially critical for Linux where manual mounting is common.

Recommendations:

Add a section describing post-attachment steps for both Windows and Linux VMs, such as initializing, partitioning, and mounting the disk (for Linux, using fdisk/lsblk/mkfs/mount; for Windows, using Disk Management or PowerShell).
Provide example commands for both Linux (bash) and Windows (PowerShell) to guide users through making the new disk available inside the VM.
Explicitly mention that after attaching a disk in the Azure portal, further steps are required inside the VM, and link to relevant documentation for both OSes.
Ensure parity in instructions and examples for both Windows and Linux users throughout the documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page describes how to create Generation 2 VMs in Azure DevTest Labs using the Azure portal, but does not provide any OS-specific examples or instructions. There is no explicit Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-first patterns. However, the documentation omits any discussion or examples related to Linux-specific considerations, such as SSH access, Linux username conventions, or Linux image selection, which are relevant for cross-platform parity.

Recommendations:

Add explicit notes or examples for creating both Windows and Linux Generation 2 VMs, including any differences in image selection or configuration.
Clarify how to set up authentication for Linux VMs (e.g., SSH keys vs. passwords) in the 'User name' and 'Password' sections.
Include screenshots or descriptions that show both Windows and Linux images in the image selection step.
Mention any Linux-specific Generation 2 VM limitations or requirements, if applicable.
Provide guidance on connecting to Linux VMs (e.g., using SSH) in addition to the generic 'Connect' instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page provides only a C# code example and does not include any platform-specific command-line instructions or tooling references. However, it lacks parity in code examples for other platforms or languages (such as Python, JavaScript, or shell scripting), and does not mention or demonstrate how to extract the query-charge header using tools or methods common on Linux (e.g., curl, jq, bash). There is no explicit Windows bias in terms of mentioning Windows tools or PowerShell, but the absence of Linux-oriented examples or guidance constitutes a subtle bias.

Recommendations:

Add examples using cross-platform command-line tools such as curl or HTTPie to demonstrate how to extract the query-charge header from the API response.
Include code snippets in other popular languages (e.g., Python, JavaScript) that are commonly used on Linux and macOS, not just C#.
Explicitly mention that the API can be accessed from any platform and provide guidance for both Windows and Linux users.
If referencing SDKs, provide links and examples for SDKs in multiple languages, not just .NET/C#.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation mentions Windows DNS and its default zone file location before mentioning BIND (the most common DNS server on Linux/Unix). No Linux-specific tools or commands are provided, but both Windows and Linux are referenced in the context of obtaining zone files. No PowerShell or Windows-only command-line examples are present, and the main workflow is via the Azure portal (cross-platform). However, the order of presentation gives Windows DNS precedence.

Recommendations:

List BIND (Linux/Unix) before Windows DNS when discussing sources of zone files, or present both in parallel to avoid perceived prioritization.
Provide explicit examples or references for obtaining zone files from both Windows DNS and BIND (e.g., sample commands or file paths for both platforms).
If mentioning default file paths, clarify that %systemroot% is Windows-specific and provide the typical BIND zone file path (e.g., /etc/bind/ or /var/named/).
Consider including a table or section summarizing how to obtain zone files from common DNS servers on both Windows and Linux.

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 for either Windows (PowerShell/Command Prompt) or Linux (Bash/CLI). However, there is an implicit bias in that no CLI-based (cross-platform) instructions are given, which are often preferred by Linux users and automation scenarios. There are no references to Windows-specific tools, but the lack of Azure CLI or Bash examples means Linux users do not see parity with their typical workflows.

Recommendations:

Add Azure CLI examples for all major steps (creating child DNS zones, verifying NS records, deleting resources), as Azure CLI is cross-platform and widely used on Linux.
If possible, provide both Azure CLI and PowerShell examples, but ensure CLI examples are presented first or equally to avoid Windows-first bias.
Include a note or section on how to perform these tasks via command line for automation and scripting scenarios, which are common in Linux environments.
Reference relevant documentation for Azure CLI DNS zone management.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only GUI-based instructions and KQL query examples, with no mention of command-line tools, scripts, or workflows for either Windows or Linux. However, there is a lack of parity for Linux users in that there are no CLI (e.g., Azure CLI, Bash) or automation examples, which are commonly used in Linux environments. There is also no mention of PowerShell or Windows-specific tools, so explicit Windows bias is minimal, but the absence of Linux/CLI examples may disadvantage Linux users.

Recommendations:

Add Azure CLI command examples for configuring diagnostic settings and exporting logs, as Azure CLI is cross-platform and widely used in Linux environments.
Include sample Bash scripts for automating log export or querying operations.
Mention how to access and analyze logs from the storage account using Linux tools (e.g., azcopy, jq, grep).
Clarify that all steps can be performed from any OS using the Azure Portal, but provide parity by showing how to accomplish the same tasks via CLI for users who prefer or require non-GUI workflows.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively demonstrates manifest-based file ingestion using the Postman desktop app, without providing any command-line or scripting examples (such as curl, HTTPie, or shell scripts) that would be more familiar or accessible to Linux users. There is no mention of Linux-specific tools or workflows, nor are there instructions for performing the same tasks outside of a GUI environment. This may disadvantage users who prefer or require non-GUI, scriptable, or Linux-native approaches.

Recommendations:

Provide equivalent examples using command-line tools such as curl or HTTPie for each API call demonstrated in Postman.
Include sample shell scripts (bash) to automate the ingestion workflow, making it easier for Linux users to follow along.
Mention that the API can be accessed from any platform and that Postman is just one of several possible tools.
If possible, provide instructions for installing and using Postman on Linux, or suggest alternative Linux-friendly API clients.
Ensure that any downloadable resources (such as sample files) are accessible and usable from the Linux command line.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only a C# code example for retrieving HTTP headers and does not include any command-line examples for either Windows (e.g., PowerShell, CMD) or Linux (e.g., curl, bash). However, the only code sample is platform-specific (C#/.NET), which is more commonly associated with Windows development. There are no Linux shell or cross-platform command-line examples, and no mention of Linux tools or workflows.

Recommendations:

Add examples using cross-platform command-line tools such as curl or HTTPie to demonstrate how to retrieve HTTP headers and check operation status from Linux or macOS environments.
Include bash or shell script snippets for parsing HTTP response headers and bodies.
If providing language-specific examples, consider including Python (requests), Node.js, or other popular cross-platform languages in addition to C#.
Clarify that the REST API can be accessed from any platform, and provide explicit Linux/macOS usage guidance 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. There are no references to Windows-specific tools, PowerShell, or command-line interfaces, but there is also a lack of parity for Linux users, as no CLI (Azure CLI, Bash, etc.) or cross-platform automation examples are provided. This omission can be considered a bias of omission, as users on Linux (or those preferring automation) are not served.

Recommendations:

Add Azure CLI examples for each major step (creating storage account, deploying the web app, subscribing to events, uploading blobs) alongside the portal instructions.
Include Bash shell commands for uploading files to Blob storage (e.g., using az storage blob upload or curl with SAS tokens).
Explicitly mention that all steps can be performed on any OS using the Azure CLI, and provide links to relevant CLI documentation.
Consider providing PowerShell and Bash equivalents if scripting is relevant, to ensure parity for both Windows and Linux/macOS users.
Add a note or section for users who prefer automation or non-GUI workflows, pointing them to CLI or ARM/Bicep template alternatives.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to configure private endpoints for Azure Event Grid namespaces using the Azure Portal GUI, with no command-line examples or references to platform-specific tools. There is no explicit Windows bias (e.g., PowerShell or Windows tools), but there is a lack of parity for users who prefer or require CLI-based instructions, which are especially relevant for Linux users.

Recommendations:

Add Azure CLI examples for all major steps (creating a namespace with private access, adding private endpoints, managing connections).
If applicable, provide PowerShell examples alongside Azure CLI, but ensure Azure CLI (cross-platform) is presented first or equally.
Include notes or links to documentation for automating these tasks on Linux systems.
Explicitly mention that all Azure CLI commands work on Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides only Azure Portal (GUI) instructions for configuring IP firewall settings and does not include any command-line examples. There is no mention of Windows-specific tools or PowerShell, but there is also a lack of CLI examples (such as Azure CLI or Azure PowerShell), which are important for cross-platform parity. This omission can disadvantage Linux users who typically rely on CLI tools.

Recommendations:

Add Azure CLI examples for configuring IP firewall settings, as Azure CLI is cross-platform and widely used on Linux.
If including PowerShell examples, ensure they are presented alongside Azure CLI examples, not before them.
Explicitly mention that the steps can be performed via the Azure Portal (web interface) from any OS, but provide CLI alternatives for automation and scripting.
Review other related documentation pages to ensure consistent inclusion of cross-platform command-line instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to create, view, and manage Azure Event Grid namespaces using the Azure portal, with no mention of command-line tools or automation. There are no examples or instructions for performing these tasks using CLI tools such as Azure CLI, PowerShell, or REST APIs. While there is no explicit Windows bias (e.g., PowerShell or Windows-only tools), the lack of command-line or scriptable examples means Linux users (who often prefer CLI-based workflows) are not equally served.

Recommendations:

Add step-by-step instructions for creating, viewing, and managing namespaces using the Azure CLI, which is cross-platform and widely used on Linux.
Include equivalent examples using Azure PowerShell for users who prefer that environment, but ensure Azure CLI examples are given equal prominence.
Provide REST API examples for advanced users or automation scenarios, making sure to show how to use curl or similar tools common on Linux.
Explicitly mention that all portal-based steps are platform-agnostic, but highlight CLI and API options for users who prefer non-GUI workflows.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to enable managed identity for Azure Event Grid system topics using the Azure Portal UI, with no command-line examples provided. There is no mention of CLI-based workflows (such as Azure CLI or Azure PowerShell), which are commonly used on both Windows and Linux. However, there is no explicit Windows bias in terms of referencing Windows tools or PowerShell, nor are Windows-specific patterns or terminology used. The main bias is the lack of parity for users who prefer or require command-line instructions, which are especially important for Linux users.

Recommendations:

Add equivalent instructions using the Azure CLI (az eventgrid system-topic identity assign, etc.), which works cross-platform (Windows, Linux, macOS).
If PowerShell examples are added, ensure Azure CLI examples are also provided and presented first or side-by-side.
Explicitly mention that the Azure CLI can be used from any OS, and provide links to relevant CLI documentation.
Consider including automation or scripting examples for managed identity assignment to support DevOps and Linux-centric workflows.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation mentions using the Azure portal or Azure CLI to subscribe to events, but does not provide any concrete examples or command-line instructions for either Windows (e.g., PowerShell) or Linux (e.g., Bash). However, there is a subtle bias in that no Linux-specific tooling, shell, or example is mentioned, and the lack of explicit cross-platform command-line examples may leave Linux users underserved.

Recommendations:

Add explicit Azure CLI command-line examples for subscribing to events, shown in a Bash shell context to demonstrate Linux compatibility.
If PowerShell or Windows-specific tools are ever mentioned, ensure equivalent Bash/Linux examples are provided alongside.
Clarify that Azure CLI is cross-platform and works on Windows, macOS, and Linux.
Include sample commands for both Bash and PowerShell if scripting is discussed in future updates.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page exclusively uses Azure Portal (web UI) instructions and screenshots, with no command-line examples for any platform. There are no references to Windows-specific tools, PowerShell, or Windows-first patterns. However, there is a lack of parity for Linux users, as there are no CLI (Azure CLI, Bash, etc.) examples provided, which are commonly used on Linux and cross-platform environments.

Recommendations:

Add equivalent Azure CLI command examples for all major steps (creating system topics, enabling managed identity, assigning roles, creating event subscriptions).
Where possible, provide Bash scripts or command-line snippets alongside portal instructions to support Linux and cross-platform users.
Explicitly mention that all steps can be performed via Azure CLI or REST API, and link to relevant documentation.
Ensure screenshots or instructions do not assume a Windows environment (e.g., avoid referencing Windows-specific file paths or tools).

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 and does not include any command-line examples. There are no references to Windows-specific tools, but there is also a complete absence of CLI-based instructions (such as Azure CLI, Bash, or PowerShell), which can disadvantage Linux users or those who prefer automation and scripting. The lack of parity in command-line examples constitutes a subtle bias by omission.

Recommendations:

Add equivalent instructions for setting up alerts using the Azure CLI, which is cross-platform and works on both Linux and Windows.
If relevant, provide Bash script examples for automating alert creation.
Include PowerShell examples only if Azure CLI is also covered, and present CLI/Bash examples before or alongside PowerShell to ensure Linux parity.
Explicitly mention that all steps can be performed via the Azure CLI and link to relevant CLI documentation.

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 include any command-line examples or tooling guidance at all. As a result, there is an implicit bias in that there are no Linux (or Windows) examples, which could disadvantage Linux users if future updates add Windows/Powershell examples only.

Recommendations:

If command-line or scripting examples are added in the future, ensure that both Windows (PowerShell/Command Prompt) and Linux (Bash/Azure CLI) examples are provided.
Explicitly mention that the instructions are platform-agnostic if no OS-specific steps are required.
If referencing tools (such as Azure CLI, PowerShell, or REST API), provide parity in documentation and usage examples for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page references Azure RBAC samples specifically in the context of .NET (a technology most commonly associated with Windows environments) and does not provide or mention equivalent Linux or cross-platform examples. There are no explicit Linux or cross-platform command-line examples, and the only sample link points to a Windows-centric technology stack.

Recommendations:

Include links to RBAC and authentication samples in other languages/platforms commonly used on Linux (e.g., Python, Java, Node.js).
Explicitly mention that the concepts and APIs are cross-platform, and provide example commands or code snippets for both Windows (PowerShell/.NET) and Linux (Bash, Python, etc.).
Add a section or note clarifying that all features are available on both Windows and Linux, and provide links to Linux-friendly tooling or documentation where appropriate.
Ensure that sample repositories referenced in 'Next steps' include or point to Linux-compatible samples and instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation only provides instructions for enabling managed identity via the Azure portal, with no mention of command-line tools or scripts. There are no examples using Azure CLI, PowerShell, or other automation tools. However, the absence of CLI examples means there is no explicit Windows or PowerShell bias, but there is a lack of parity for Linux users who may prefer or require command-line instructions.

Recommendations:

Add step-by-step instructions for enabling managed identity using Azure CLI, which is cross-platform and widely used on Linux.
If relevant, provide PowerShell examples alongside Azure CLI, but ensure CLI examples are given equal or higher prominence.
Explicitly mention that the Azure portal is platform-agnostic, but highlight automation options for both Windows and Linux users.
Include links to official Azure CLI and PowerShell documentation for further automation and scripting guidance.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any platform-specific examples or instructions, but all linked sample repositories are .NET-based, which may implicitly favor Windows users. There are no explicit Linux or cross-platform instructions or examples.

Recommendations:

Include explicit instructions or examples for running the replication tasks on Linux (e.g., using .NET Core on Linux).
Mention cross-platform compatibility of the provided samples, if applicable.
Provide alternative examples or notes for users on macOS/Linux, such as command-line instructions or scripts.
Highlight any platform-specific prerequisites or differences, if they exist.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or tooling instructions, but it also does not include any Windows- or Linux-specific commands, tools, or patterns. However, the absence of any example commands or configuration steps (for either Windows or Linux) means there is a missed opportunity to demonstrate parity or inclusivity for Linux users. The only minor indicator is the use of the endpoint 'yournamespace.servicebus.windows.net', which is Azure-specific but not inherently Windows-biased. No explicit Windows bias is present, but Linux users are not directly supported with examples.

Recommendations:

Add example commands for configuring the minimum TLS version using cross-platform tools such as Azure CLI (az), which works on both Windows and Linux.
If showing PowerShell or Azure Portal steps, also include equivalent Azure CLI or REST API examples to ensure Linux parity.
Explicitly mention that the configuration steps apply equally to Windows, Linux, and macOS environments when using cross-platform tools.
If referencing troubleshooting steps (such as network tracing), suggest tools available on both Windows (e.g., Wireshark) and Linux (e.g., tcpdump, Wireshark).

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to configure Azure DDoS Protection Plan using the Azure Portal GUI, with no command-line examples provided for any platform. 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 may disadvantage Linux users or those who prefer automation and scripting.

Recommendations:

Add Azure CLI examples for each step, showing how to create firewall policies, secured virtual networks, DDoS Protection Plans, and associations via command line.
Ensure that any scripting examples are cross-platform (e.g., Bash/Azure CLI rather than PowerShell-only).
Include a section comparing portal, PowerShell, and Azure CLI approaches, with links to relevant documentation for each.
Explicitly mention that all steps can be performed via Azure CLI and provide links or code snippets for Linux/macOS users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any platform-specific configuration examples or tooling references (Windows or Linux). However, the only configuration guidance links to the Azure portal, with no mention of CLI, PowerShell, or Linux-based tools. This omission may disadvantage Linux users who prefer command-line or automation-based workflows.

Recommendations:

Add examples for configuring BGP communities using Azure CLI and/or Azure PowerShell, ensuring both Windows and Linux users are supported.
Include references or links to documentation for automating BGP community configuration via scripts (e.g., Bash for Linux, PowerShell for Windows).
Explicitly mention that the Azure portal is cross-platform, but also provide parity for users who prefer non-GUI approaches.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively uses the Azure Portal (GUI) for all configuration steps and does not provide any command-line examples. There are no references to Windows-specific tools or PowerShell, but there is also a complete absence of CLI-based instructions (such as Azure CLI or Azure PowerShell), which are commonly used on both Windows and Linux. This omission can disadvantage Linux users who prefer or require command-line automation, as the Azure CLI is cross-platform and widely used in Linux environments.

Recommendations:

Add parallel instructions using the Azure CLI for each major step (e.g., creating the ExpressRoute circuit, enabling private peering, creating the virtual network gateway, and linking resources).
Ensure that all CLI examples are tested and work on both Windows and Linux shells (e.g., Bash).
If referencing PowerShell, always provide Azure CLI equivalents and present them either before or alongside PowerShell examples.
Explicitly mention that the Azure CLI is available cross-platform and provide installation links for Linux users.
Consider including automation scripts or templates (e.g., ARM, Bicep, Terraform) that are platform-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation is generally platform-neutral, focusing on network concepts and configuration requirements. However, there is a notable instance of Windows bias: in the section on advertising default routes, only Windows VM license activation is mentioned as being affected, with a workaround link specifically for Windows (KMS activation). There are no Linux-specific examples, issues, or workarounds discussed, nor are Linux tools or patterns referenced.

Recommendations:

When discussing issues that affect VM license activation due to routing (such as KMS for Windows), also mention whether there are equivalent concerns for Linux VMs (e.g., activation, repository access, or other licensing mechanisms).
If there are Linux-specific routing or activation considerations (such as access to package repositories or cloud-init endpoints), include them alongside Windows examples.
Where possible, provide parity in troubleshooting or workaround documentation for both Windows and Linux VM scenarios.
Explicitly state if a limitation or workaround is only relevant to Windows, and clarify that Linux VMs are unaffected, if that is the case.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page exclusively describes how to view and configure alerts for Azure ExpressRoute circuit maintenance using the Azure portal GUI. There are no command-line examples or automation instructions provided for any platform, but notably, there is a lack of CLI, PowerShell, or Bash examples. This omission can be considered a bias of omission, as many Azure docs provide PowerShell or Windows-centric instructions without Linux equivalents. In this case, the absence of both PowerShell and Bash/CLI examples means Linux users do not have parity for automation or scripting.

Recommendations:

Add Azure CLI examples for viewing and configuring Service Health alerts, as Azure CLI is cross-platform and widely used on Linux.
If PowerShell examples are added, ensure Bash/Azure CLI equivalents are also provided.
Include references to relevant REST API endpoints for advanced automation, with sample requests using curl or similar Linux-friendly tools.
Explicitly mention that all steps can be performed using the Azure CLI or REST API, and link to relevant documentation for those workflows.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation lists the creation of a random password for a Windows VM before mentioning the creation of a Linux VM, and references a Windows VM specifically in the checklist of resources. However, the main implementation steps and code samples are platform-agnostic, and the verification and CLI instructions use Azure CLI, which is cross-platform. There are no PowerShell-specific examples, and both Windows and Linux VMs are mentioned, though Windows is listed first.

Recommendations:

List the creation of Linux and Windows VMs together or mention Linux first to avoid implicit prioritization of Windows.
Provide equivalent detail for both Linux and Windows VM creation steps, or clarify that both are optional and can be created as needed.
Ensure that any references to OS-specific resources or steps are balanced and that neither platform is implied as the default.
If possible, add explicit notes that the instructions and code samples are cross-platform and work on both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page exhibits a mild 'windows_first' bias. In the section discussing supported cipher suites, recommendations are made specifically for Windows 10 and later, with additional compatibility notes for Windows 8.1, 8, and 7. There are no equivalent recommendations or compatibility notes for Linux or macOS clients. No PowerShell commands or Windows-specific tools are mentioned, but the only OS-specific guidance is for Windows.

Recommendations:

Add equivalent recommendations or compatibility notes for Linux distributions (e.g., minimum OpenSSL versions or cipher suite support in common Linux browsers/clients).
Include a note about how to check or configure supported cipher suites on Linux systems.
If mentioning Windows compatibility, also mention macOS and Linux client compatibility to ensure parity.
Consider providing a table or matrix showing cipher suite support across major operating systems (Windows, Linux, macOS) and browsers.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation demonstrates a subtle Windows bias by referencing Windows 10 and the Windows Subsystem for Linux (WSL) as the primary environment for running Bash, and by providing installation guidance specifically for WSL on Windows 10. While all CLI examples use Bash syntax, the documentation positions Windows (with WSL) as the default context, and only briefly mentions that examples can be adapted for the Windows Command prompt, without providing explicit Windows Command Prompt or PowerShell examples. There are no explicit Linux-native instructions or examples, nor are there PowerShell-heavy or Windows tools used in the commands.

Recommendations:

Present Bash usage in a platform-neutral way, e.g., 'The examples use Bash syntax, which is available on Linux, macOS, and Windows (via WSL or other means)'.
Provide explicit instructions or notes for running the examples on native Linux and macOS systems, not just Windows with WSL.
If mentioning WSL, also mention native Linux and macOS as supported environments.
Consider including a table or section that shows how to adapt the variable setting and commands for Windows Command Prompt and/or PowerShell, or link to a guide for translating Bash to Windows shell syntax.
Avoid positioning Windows as the default or primary platform unless there is a technical reason.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples, commands, or tooling, but it also does not mention or show how to perform tasks using Linux or cross-platform tools. All instructions are GUI-based and generic, but there is a lack of parity for users who may prefer or require CLI-based (e.g., Bash, Azure CLI) instructions, which are common on Linux.

Recommendations:

Add equivalent step-by-step instructions using Azure CLI commands, which are cross-platform and commonly used on Linux.
Include examples for configuring DNS using command-line tools (e.g., Azure CLI or PowerShell Core, which is cross-platform), not just portal-based steps.
Explicitly mention that the steps can be performed from any OS using the Azure Portal, and provide links or references to CLI documentation for automation or scripting needs.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any OS-specific examples, but the only code sample shown is in C#, which is cross-platform. However, there are no explicit references to Windows, Windows tools, or PowerShell, nor are there any instructions or examples that are Windows-specific. The main bias is the lack of explicit Linux (or cross-platform) command-line or deployment examples, which could help Linux users understand how to interact with IoT Edge modules on their systems.

Recommendations:

Add explicit examples or references for both Windows and Linux environments, especially for common tasks such as deploying modules, managing containers, or interacting with the IoT Edge runtime.
Include sample commands for both PowerShell (Windows) and Bash (Linux) where appropriate.
Clarify in the documentation that Azure IoT Edge is supported on both Windows and Linux, and provide links to OS-specific setup guides.
If showing code samples for interacting with the IoT Edge runtime, consider including examples in languages commonly used on Linux (e.g., Python, Bash scripts) in addition to C#.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page is generally Linux-focused, as HDInsight clusters are Linux-based and all operational examples (SSH, bash, hbase shell, etc.) use Linux conventions. However, there is a minor instance of Windows bias: the SSH command is shown in a Windows Command Prompt (cmd) block (```cmd) before any bash or Linux terminal block, which may suggest a Windows-first approach for remote connection, even though the rest of the workflow is Linux-native.

Recommendations:

Use bash syntax highlighting for SSH commands, or provide both Windows (cmd/PowerShell) and Linux/macOS (bash) SSH command examples side by side.
Clarify in the prerequisites or first SSH example that the commands are intended for Linux/macOS terminals, but can also be run from Windows using PowerShell or WSL.
If Windows-specific tools or patterns are not required, default to bash examples, as the clusters themselves are Linux-based.
If targeting cross-platform users, add a short section or note on how to SSH from Windows (e.g., using PowerShell, Windows Terminal, or PuTTY), and from Linux/macOS (native terminal).

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides a high-level overview of HPC lift-and-shift migration but does not include any platform-specific examples or commands. However, it omits concrete examples for both Windows and Linux, and does not mention any Windows-specific tools or patterns. The only product recommendation is Azure CycleCloud with Slurm, which is a Linux-native scheduler. There is a lack of explicit Linux command-line or configuration examples, which may leave Linux-focused administrators without actionable guidance.

Recommendations:

Add explicit Linux-based examples for common HPC administrative tasks (e.g., sample Slurm configuration, Linux CLI commands for job submission, storage mounting, or monitoring).
Include references to Linux-native tools and workflows (such as SSH, rsync, or Linux scripting for automation).
Provide parity by ensuring that any product or tool recommendations (such as CycleCloud) are accompanied by Linux usage scenarios and step-by-step guides.
If Windows tools or PowerShell are not relevant, clarify that the guidance is platform-agnostic or primarily Linux-focused, to set expectations for the reader.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page provides only Azure Portal (GUI) instructions for resource group configuration and does not include any command-line examples. There is a lack of parity for Linux users, as no Azure CLI or Bash examples are provided, nor are there any PowerShell examples. The absence of Linux-friendly command-line instructions may disadvantage users who prefer or require CLI-based workflows, especially on Linux systems.

Recommendations:

Add Azure CLI (az) command-line examples for all resource group operations, as the Azure CLI is cross-platform and works natively on Linux.
If PowerShell examples are added in the future, ensure that Azure CLI examples are always provided alongside them.
Explicitly mention that resource group management can be performed via the Azure CLI on Linux, macOS, and Windows.
Consider including Bash scripting examples for automation scenarios relevant to Linux users.

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-specific tools, commands, or workflows. There is an implicit bias due to the absence of Linux guidance, which may leave Linux users without clear instructions for common troubleshooting scenarios.

Recommendations:

Add explicit troubleshooting steps for both Windows and Linux environments, including relevant command-line examples for each.
Mention and provide examples for Linux-compatible tools (such as azcopy or relevant shell commands) alongside any Windows-specific tools.
Clarify whether the described procedures (e.g., deleting journal files, rerunning commands) are the same on Linux, and provide file path examples for both platforms.
Include a section or note addressing any platform-specific differences or considerations for Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on the Azure portal GUI and does not provide any command-line examples or automation options for either Windows (PowerShell) or Linux (CLI, Bash). However, it does not show explicit Windows bias such as PowerShell commands or Windows-only tools. The main bias is the lack of parity for users who prefer or require command-line or automated setup, which is common in Linux environments.

Recommendations:

Provide equivalent Azure CLI (cross-platform) commands for all portal-based steps, enabling Linux and automation-friendly workflows.
If PowerShell examples are ever added, ensure Azure CLI and/or REST API examples are included alongside them.
Document any prerequisites or differences for Linux-based network appliances or tools, if relevant.
Mention and link to API or CLI documentation for users who want to script or automate the process, and update the FAQ if/when API support becomes available.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides a conceptual overview of TPM attestation with Azure DPS but does not include any platform-specific examples or instructions. However, it references 'the set of TPM tools being used, and the device operating system' without giving concrete examples for either Windows or Linux. There is a lack of practical guidance or examples for Linux users, which may leave them underserved compared to Windows users if other documentation pages provide Windows-specific instructions.

Recommendations:

Add explicit examples or references for both Windows and Linux TPM tooling (e.g., tpm2-tools for Linux, Windows built-in TPM management tools).
Include sample commands or workflows for taking ownership of a TPM and extracting EK_pub/SRK_pub on both Windows (e.g., using PowerShell or TPM.msc) and Linux (e.g., using tpm2_getpubek, tpm2_createprimary, etc.).
Provide links to platform-specific TPM documentation or guides for both operating systems.
Ensure that any future updates or related articles maintain parity by presenting Linux and Windows instructions side-by-side.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides command-line examples exclusively using the Azure CLI, which is cross-platform, and does not mention or show any Windows-specific tools (such as PowerShell or CMD), nor does it reference Windows-only patterns. However, it also does not provide any Linux- or macOS-specific examples, shell syntax, or notes about platform-specific considerations. Thus, while not overtly Windows-biased, the documentation lacks explicit Linux parity in examples or guidance.

Recommendations:

Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS, to reassure non-Windows users.
Where relevant, provide example shell commands using both Bash (for Linux/macOS) and PowerShell (for Windows), especially if there are differences in quoting, environment variables, or command syntax.
Mention any platform-specific prerequisites or considerations (e.g., installation instructions for Azure CLI on Linux).
Add a note or section clarifying that the documented procedures are cross-platform, and link to official Azure CLI installation guides for all supported operating systems.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page generally presents Linux as the primary platform for Azure IoT Edge, but when discussing Windows support, it consistently refers to 'IoT Edge for Linux on Windows' (EFLOW) as the recommended approach. Windows is mentioned after Linux in most tables and explanations, but the Windows experience is always described as running Linux containers via a VM, not as a first-class native experience. There are no explicit PowerShell-heavy examples, Windows-only tools, or missing Linux examples, but the phrasing and ordering suggest a Linux-first, Windows-second approach, with Windows support being indirect.

Recommendations:

Clarify that Windows support is via EFLOW and explain the rationale for this approach, possibly in a dedicated section.
If possible, provide more parity in examples or instructions for both Linux and Windows (even if Windows is via EFLOW), such as installation or troubleshooting steps.
Explicitly state the limitations or differences in experience between native Linux and Windows (EFLOW) to set expectations.
Consider adding a brief summary table at the top comparing native Linux, EFLOW on Windows, and (deprecated) Windows containers for quick reference.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page demonstrates a subtle Windows bias by consistently mentioning 'IoT Edge for Linux on Windows (EFLOW)' as a primary variant, with detailed versioning and support information. While the core product is cross-platform, the prominence and repeated focus on the Windows-hosted Linux variant (EFLOW) may give the impression that Windows is the preferred or primary platform, even though the underlying runtime is Linux-based. There are no explicit PowerShell examples, Windows-only tools, or missing Linux examples, but the structure and emphasis place Windows (via EFLOW) before native Linux deployments.

Recommendations:

Balance the coverage of EFLOW and native Linux deployments by providing equivalent detail and visibility for both.
Include a section or table summarizing native Linux distributions and their support status, similar to the EFLOW version table.
Clarify in the introduction that IoT Edge is primarily a Linux-based solution, and EFLOW is a way to run it on Windows, rather than presenting EFLOW as a co-equal or primary deployment method.
Ensure that future documentation and release notes provide parallel information for both native Linux and EFLOW, so that Linux users do not feel secondary.

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 show any examples for Linux systems, command-line interfaces, or automation methods. There are no explicit references to Windows, PowerShell, or Windows-only tools, but the lack of Linux-specific guidance or examples may leave Linux users uncertain about the onboarding process.

Recommendations:

Explicitly mention that the onboarding script supports both Windows and Linux servers, if applicable.
Provide example commands or screenshots for running the onboarding script on both Windows (e.g., PowerShell or Command Prompt) and Linux (e.g., Bash).
Clarify any OS-specific prerequisites or steps, such as required permissions or dependencies for Linux systems.
Include links to Linux-specific onboarding documentation or troubleshooting guides.
If automation methods are referenced, give parity between Windows and Linux automation tools (e.g., PowerShell and Bash scripts, Ansible, etc.).

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation presents connection instructions for Windows virtual machines (using RDP) before Linux virtual machines (using SSH or RDP). While both platforms are mentioned, the ordering and phrasing prioritize Windows, which may subtly reinforce a Windows-centric perspective.

Recommendations:

Present Linux and Windows connection instructions in parallel or alternate the order in which they are described to avoid always listing Windows first.
Provide explicit command-line examples for both SSH (Linux) and RDP (Windows) connections, ensuring parity in detail and clarity.
Where possible, use neutral language such as 'For Linux or Windows virtual machines...' instead of always leading with Windows.
Consider including screenshots or step-by-step instructions for both SSH (Linux) and RDP (Windows) workflows to ensure equal visibility.

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 and Linux. However, there are repeated PowerShell-specific tips for escaping double quotes, which are only relevant to Windows users. There are no Linux- or Bash-specific examples or tips, and no mention of Linux tools or shell patterns.

Recommendations:

Add Bash/Linux shell equivalents for escaping quotes in CLI commands, e.g., show how to use single quotes or proper escaping in Bash.
Include a note or example for Linux/macOS users on how to handle JSON strings in CLI commands.
Balance PowerShell-specific tips with Bash-specific tips to ensure parity.
Explicitly state that the Azure CLI commands work cross-platform and provide any OS-specific caveats where relevant.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any OS-specific examples or instructions, but it also does not mention or demonstrate how to access effective security rules using command-line tools or scripts on either Windows (e.g., PowerShell) or Linux (e.g., Bash, CLI). This omission results in a lack of Linux parity, as users on Linux systems are not shown how to interact with the feature outside the Azure portal.

Recommendations:

Add examples for accessing effective security rules using Azure CLI commands, which are cross-platform and work on both Windows and Linux.
If scripting examples are provided in the future, ensure both PowerShell (Windows) and Bash (Linux) examples are included.
Explicitly mention that the Azure portal is OS-agnostic, but provide links or references to documentation for command-line access on different platforms.
Include a section on automating rule retrieval using scripts, with parity between Windows and Linux approaches.

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, nor does it reference Windows patterns or tools before Linux equivalents. However, it lacks explicit Linux (or cross-platform) command-line examples for key steps such as Git operations, pipeline setup, or script execution. All instructions are given through Visual Studio Code's GUI and Azure DevOps web portal, which are cross-platform, but there is no mention of how to perform these tasks via CLI on Linux or macOS, nor are there any terminal-based examples.

Recommendations:

Add explicit CLI examples for common tasks (e.g., initializing a Git repo, adding remotes, committing, pushing) using cross-platform commands (git, Azure CLI) to ensure parity for Linux/macOS users.
Mention that all steps can be performed on Windows, Linux, or macOS, and clarify any platform-specific requirements or limitations.
Where possible, provide Azure CLI or bash script equivalents for actions currently described only via GUI (e.g., pipeline creation, resource group management).
Include a note or section on using the Azure Logic Apps extension and Azure DevOps tasks from Linux/macOS environments, confirming cross-platform support.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation references both Azure CLI and PowerShell as alternatives to the management SDKs, but lists Azure CLI first, followed by PowerShell and REST API. There are no explicit examples or instructions that are Windows-specific, nor is there an absence of Linux alternatives. However, the mention of PowerShell (a Windows-native tool, though now cross-platform) alongside Azure CLI (which is cross-platform and more commonly used on Linux) could suggest a slight Windows-first bias in tool listing order.

Recommendations:

Ensure that when listing management tools, cross-platform options like Azure CLI are always mentioned first, and clarify their cross-platform compatibility.
Explicitly state that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, to avoid the perception that PowerShell is Windows-only.
Where possible, provide example commands for both Azure CLI and PowerShell, or clarify that instructions apply equally across platforms.
Consider adding a short note or table summarizing tool availability and platform compatibility for new users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation primarily describes the auto-shutdown feature in general terms and highlights some limitations for Linux labs, but does not provide any Linux-specific configuration examples or guidance. The only mention of Linux is in the context of feature limitations, with no equivalent positive or step-by-step Linux instructions.

Recommendations:

Include explicit Linux examples or screenshots where applicable, especially if the configuration steps or UI differ for Linux-based labs.
Provide a table or section summarizing feature support and limitations for both Windows and Linux, including supported distributions and versions.
Offer troubleshooting tips or alternative approaches for Linux users, particularly for unsupported distributions like Data Science Virtual Machine - Ubuntu.
Ensure that any limitations for Linux are balanced with actionable guidance, not just caveats.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any OS-specific examples, commands, or tools, but it also does not mention or show parity for Linux or Windows environments. There are no explicit references to Windows tools, PowerShell, or command-line examples for any platform. However, the lack of any example commands or screenshots showing both Windows and Linux VMs may implicitly bias the documentation towards users who are familiar with the Azure Portal UI, which is platform-agnostic but often more familiar to Windows users.

Recommendations:

Add explicit examples or notes clarifying that IP flow verify works for both Windows and Linux VMs.
Include screenshots or walkthroughs that reference both Windows and Linux VM scenarios to demonstrate parity.
If CLI or PowerShell examples are added in the future, ensure that equivalent Azure CLI (cross-platform) and PowerShell (Windows and cross-platform) instructions are provided.
Mention in the overview that the feature is OS-agnostic and can be used with any VM OS supported by Azure.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any command-line examples or troubleshooting steps that are specific to either Windows or Linux. However, it also does not include any CLI-based troubleshooting steps (such as using Azure CLI, PowerShell, Bash, or kubectl commands), and all instructions are given via the Azure Portal UI. This results in a lack of parity for users who prefer or require command-line or Linux-native troubleshooting approaches.

Recommendations:

Add equivalent Azure CLI and/or Bash command examples for each troubleshooting step, especially for verifying managed private endpoint approval, checking NSG rules, and validating private link service configuration.
Include kubectl command examples for verifying AKS service and load balancer port configurations, as these are commonly performed via the command line in Linux environments.
Where possible, provide both portal-based and CLI-based instructions side by side to support both Windows and Linux users.
Explicitly mention that steps can be performed via CLI or portal, and link to relevant Azure CLI or kubectl documentation.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on virtualization platforms (VMware, Hyper-V, and physical servers) and does not provide any OS-level examples, commands, or tooling. However, there is a notable absence of Linux-specific guidance, examples, or references—especially regarding permissions, agent installation, or migration scenarios. There are no Windows-specific tools or PowerShell examples, but the lack of Linux parity (e.g., Linux command-line, sudo, or Linux migration nuances) is evident.

Recommendations:

Include explicit references to Linux servers in assessment and migration scenarios, clarifying support and any limitations.
Add Linux-specific guidance for permissions, agent installation, and troubleshooting (e.g., using sudo, systemd, or relevant Linux commands).
Provide Linux command-line examples alongside any Windows or PowerShell instructions in future documentation updates.
Clarify whether physical server migration guidance applies equally to Linux and Windows, and highlight any OS-specific considerations.
Link to or create documentation that addresses common Linux migration scenarios, including application and service discovery on Linux.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides a general overview of Azure Migrate assessment types and prerequisites but does not include any OS-specific examples or instructions. However, it lacks explicit mention or examples for Linux workloads, tools, or considerations, focusing instead on generic terms like 'servers', 'VMware', 'Hyper-V', and 'physical servers'. There are no PowerShell or Windows-specific commands, but the absence of Linux-specific guidance or examples constitutes a subtle bias.

Recommendations:

Explicitly mention support for both Windows and Linux workloads in the assessment types and prerequisites.
Include examples or notes on assessing Linux servers, such as supported Linux distributions, any required agents or configurations, and common migration considerations.
Provide links to Linux-specific documentation or troubleshooting guides where relevant.
Clarify in the discovery and assessment sections that both Windows and Linux operating systems are supported, and highlight any differences in data collection or assessment for Linux workloads.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples, commands, or screenshots, but it implicitly assumes a Windows environment by omitting any mention of Linux-specific steps, tools, or considerations. There are no references to Linux shell commands, Linux-based replication appliances, or guidance for Linux administrators. The only OS-specific mention is in the context of Azure Hybrid Benefit for Windows Server, with no equivalent discussion for Linux systems.

Recommendations:

Add explicit instructions or notes for deploying and managing the replication appliance on Linux-based systems, if supported.
Include Linux-specific examples for DNS configuration (e.g., editing /etc/hosts instead of 'hosts file' terminology, which is ambiguous).
Clarify whether the replication appliance and Mobility service support Linux hosts, and provide links to Linux installation guides if available.
Mention any Linux-specific prerequisites, troubleshooting steps, or differences in the migration process.
Balance the Azure Hybrid Benefit section by noting any relevant licensing or migration considerations for Linux VMs.

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 Bash). While this avoids explicit Windows or PowerShell bias, it also omits parity for Linux users who may prefer or require CLI-based workflows. The absence of CLI examples (especially Azure CLI, which is cross-platform) can be considered a subtle bias, as it does not address the needs of users on Linux or those automating deployments.

Recommendations:

Add Azure CLI examples alongside portal instructions for all major steps (resource creation, configuration, deletion).
If PowerShell examples are added in the future, ensure Azure CLI (or Bash) equivalents are provided and presented with equal prominence.
Explicitly mention that the Azure CLI can be used from Linux, macOS, and Windows, and provide links to relevant installation guides.
Consider including a table or section summarizing equivalent commands for Azure CLI, PowerShell, and portal actions.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any OS-specific troubleshooting examples or instructions, but it also does not mention Linux or provide Linux-specific guidance. The absence of Linux examples or references may make Linux users feel unsupported, especially since Azure Migrate can be used for both Windows and Linux migrations.

Recommendations:

Add explicit troubleshooting sections or examples for Linux-based appliances and workloads.
Ensure that links to troubleshooting guides include Linux-specific issues and solutions where applicable.
Mention Linux support in the context of app discovery, assessment, and migration, clarifying any differences or limitations.
Provide parity in troubleshooting steps for both Windows and Linux environments, or clearly state if a feature is Windows-only.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides troubleshooting steps and configuration guidance for Azure NAT Gateway integration with various Azure services, but it does not include any command-line examples, scripts, or troubleshooting steps specific to either Windows or Linux. However, in areas where validation or troubleshooting is suggested (such as 'ping a virtual machine on your Web Apps and check the traffic via a network capture'), there are no examples or tool recommendations for either platform. The documentation is neutral in terms of explicit Windows bias (no PowerShell, Windows tools, or Windows-first ordering), but it also lacks parity by not providing Linux (or cross-platform) command-line examples or tool suggestions.

Recommendations:

Add cross-platform command-line examples for validating NAT gateway usage, such as using curl, wget, or traceroute for Linux/macOS and their Windows equivalents.
When suggesting network capture, recommend tools available on both platforms (e.g., tcpdump for Linux, Wireshark for both, or Windows equivalents) and provide example commands.
Explicitly mention that the troubleshooting steps can be performed from either Windows or Linux VMs, and provide sample commands for both.
If referencing Azure CLI, clarify that it is cross-platform and provide example commands for common tasks (e.g., checking public IP, updating NAT gateway settings) that work on all supported OSes.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of tools or command-line examples, as it relies entirely on Azure Portal UI instructions. However, there is a lack of parity for Linux users: there are no examples or guidance for performing VPN troubleshooting using CLI tools (such as Azure CLI, Bash, or PowerShell), nor is there mention of how to access or interpret logs from a Linux environment. The documentation implicitly assumes a GUI/portal workflow, which may not suit Linux administrators who prefer or require command-line or scriptable solutions.

Recommendations:

Add step-by-step instructions for using Azure CLI (az network watcher vpn-troubleshoot) to perform the same troubleshooting tasks, including log retrieval and interpretation.
Provide examples for downloading and analyzing diagnostic logs using Bash or other Linux-native tools.
Mention and link to PowerShell and CLI documentation equally, ensuring both Windows and Linux administrators can follow along.
Clarify that the portal-based workflow is cross-platform, but offer alternatives for users who prefer or require command-line access.

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 Bash scripts). While this avoids explicit Windows bias (e.g., PowerShell-only commands), it also omits Linux-friendly approaches, such as Azure CLI commands, which are cross-platform and commonly used on Linux. There is no mention of Linux tools, shell commands, or parity for non-Windows environments.

Recommendations:

Add Azure CLI examples for all policy assignment, remediation, and compliance-check steps. Azure CLI is cross-platform and works on Linux, macOS, and Windows.
If relevant, provide Bash script snippets for automating policy management tasks.
Include a section or callout that highlights how to perform these tasks using the Azure CLI or ARM templates, with links to relevant documentation.
Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid references to Windows-specific file paths or tools).

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to manage NSG flow logs using the Azure Portal UI, with no mention of command-line alternatives such as Azure CLI, PowerShell, or scripting. There are no examples or instructions for Linux users or for cross-platform command-line tools, which could disadvantage users who prefer or require non-Windows environments.

Recommendations:

Add Azure CLI examples for all policy assignment and compliance tasks, as Azure CLI is cross-platform and widely used on Linux.
If relevant, include PowerShell examples, but always provide Azure CLI or REST API equivalents and present them first or side-by-side.
Explicitly mention that the Azure Portal is accessible from any OS, but also provide command-line and automation options for users who do not use the Portal.
Link to documentation on using Azure Policy with ARM templates, Azure CLI, and REST API for full cross-platform coverage.
Consider a section or callout for 'Command-line and automation options' to highlight parity for Linux and automation-focused users.

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 Bash). While this avoids explicit Windows or PowerShell bias, it also omits Linux-friendly approaches, such as Azure CLI or Bash scripting, which are commonly used on Linux and cross-platform environments. This lack of parity may disadvantage users who prefer or require command-line automation, especially on Linux systems.

Recommendations:

Add equivalent Azure CLI examples for all policy assignment and compliance-checking steps. The Azure CLI is cross-platform and works well on Linux, macOS, and Windows.
Where possible, provide Bash script snippets for automating the tasks described, or reference official documentation for CLI-based policy management.
Explicitly mention that all tasks can be performed via Azure CLI or PowerShell, and provide links to those instructions if not included inline.
Ensure screenshots and UI references are supplemented with command-line alternatives to support users working in non-GUI or Linux environments.

Create pull request

No problematic pages found in this scan. All pages appear to be Linux-friendly! 🐧