Scan Details - Linux-first Docs for Azure

464

Pages Scanned

53

Pages Flagged

464

Changed Pages

11.4%

% Pages Flagged

Scan Information

Started At: 2025-07-16 00:00:07

Finished At: 2025-07-16 00:09:05

Status: completed

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

Current Phase: discovery

Problematic Pages

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 referencing Fiddler (a Windows-centric tool) for network debugging, and using Windows-specific instructions such as 'Run as administrator.' There are no Linux or cross-platform alternatives or examples provided for these key troubleshooting steps.

Recommendations:

Provide Azure CLI and/or Azure Cloud Shell examples alongside or instead of PowerShell for checking Application Gateway settings, as these are cross-platform.
Include examples of using Linux-compatible network debugging tools such as tcpdump, Wireshark, or mitmproxy for capturing and analyzing HTTP/HTTPS traffic.
When referencing tools like Fiddler, mention cross-platform alternatives and provide installation and usage instructions for Linux and macOS.
Avoid instructions that are specific to Windows (e.g., 'right click and run as administrator') or provide equivalent steps for Linux/macOS environments.
Ensure screenshots and walkthroughs are not exclusively from Windows environments; include or link to examples from other platforms where possible.

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 configuring Azure Application Gateway with Key Vault certificates. There are no equivalent Azure CLI (cross-platform) or Bash/Linux examples, and PowerShell is referenced as the primary automation tool. The guidance and code snippets assume a Windows-centric workflow, with no mention of Linux shell environments or tooling. Additionally, the 'Next steps' section links only to a PowerShell-based guide.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell code snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
Where automation steps are described, provide both PowerShell and Bash/Azure CLI workflows.
In sections referencing PowerShell, mention Azure CLI as an alternative and provide links to relevant CLI documentation.
Ensure that all portal-based instructions clarify that they are OS-agnostic, and avoid implying that PowerShell is the only automation option.
Update the 'Next steps' section to include links to Azure CLI and ARM/Bicep template guides, not just PowerShell.

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 the PFXImportCertStore function), providing configuration guidance and next steps primarily via PowerShell, and omitting Linux or cross-platform CLI examples. There is no mention of Linux tools or workflows for certificate management or Application Gateway configuration, and the only automation examples referenced are Windows-centric.

Recommendations:

Provide equivalent Azure CLI and/or Azure Cloud Shell examples for configuring Application Gateway and end-to-end TLS, alongside or before PowerShell instructions.
Reference cross-platform certificate management tools (such as OpenSSL) for preparing certificates, including how to generate and convert certificates to PFX format on Linux/macOS.
Link to documentation or guides for Linux users on how to manage certificates and interact with Azure Application Gateway.
Avoid referencing Windows APIs (such as PFXImportCertStore) as the primary or only source for supported algorithms; instead, summarize requirements in a platform-neutral way or provide equivalent Linux references.
Ensure that troubleshooting and next steps sections include both Windows and Linux workflows, or explicitly state that the instructions are cross-platform where applicable.

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 examples use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Bash, Azure CLI, or Linux/macOS equivalents. The instructions assume a Windows environment (e.g., file paths like c:\appgwcert.pfx), and there are no alternative steps or code samples for Linux users.

Recommendations:

Provide parallel examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux/macOS.
Include instructions for creating self-signed certificates using OpenSSL, which is standard on Linux/macOS, alongside the PowerShell method.
Use platform-neutral file paths (e.g., ~/appgwcert.pfx or ./appgwcert.pfx) or clarify the differences for Windows and Linux/macOS.
Explicitly state that the tutorial can be followed from Linux/macOS and provide any necessary prerequisites or differences.
Add a section or callouts for Linux/macOS users, highlighting any steps that differ or require alternative tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by prioritizing Windows terminology and tools. Windows and PowerShell are mentioned or exemplified before Linux equivalents, and PowerShell scripting is given equal prominence to Azure CLI without Linux shell examples. There is no explicit Linux shell (bash) scripting example, and the automation section does not clarify cross-platform usage. The portal instructions and screenshots are Windows-centric, and Linux-specific guidance is minimal or secondary.

Recommendations:

Provide explicit bash/Linux shell scripting examples alongside Azure CLI and PowerShell, clarifying cross-platform compatibility.
When listing commands or tools, present Linux and Windows options together or alternate their order to avoid Windows-first bias.
Include screenshots or instructions for the Azure portal as accessed from Linux/macOS browsers, or clarify that the portal is platform-agnostic.
Expand the automation section to show how to use scripting on Linux (e.g., bash scripts), not just PowerShell.
Where PowerShell is mentioned, clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
Add a note or section highlighting any differences or considerations for Linux users, especially regarding deployment and automation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. While it is generally cross-platform in its language, it provides explicit instructions and links for Windows tools (IIS, Certreq.exe) and PowerShell, and references to Windows-specific certificate management. Linux equivalents (such as certutil, keytool, or OpenSSL on Linux) are not mentioned when Windows tools are. In automation and scripting sections, PowerShell is given equal or greater prominence than Azure CLI, and no bash or Linux-native scripting examples are provided. This could make the documentation less accessible or clear for Linux users.

Recommendations:

When referencing certificate export or management tools, provide Linux equivalents (e.g., mention how to export a certificate using OpenSSL or keytool on Linux, not just IIS or Certreq.exe).
In automation sections, always provide Azure CLI/bash examples before or alongside PowerShell, and clarify which examples are cross-platform.
Explicitly state when a tool or process is Windows-only, and offer alternative instructions for Linux/macOS users.
Add a section or callout for Linux users on how to generate, merge, and export certificates using common Linux tools.
Review FAQ and troubleshooting sections for OS-specific limitations, and clarify when features are Windows-only or have different behaviors on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing PowerShell (a Windows-centric technology) in both structure and content. PowerShell runbooks are described first and in the most detail, with extensive examples and troubleshooting based on Windows file paths (e.g., C:\modules). Many examples and known issues reference Windows-specific patterns, such as environment variables and file paths, with little or no equivalent Linux guidance. The documentation also references Windows tools and concepts (e.g., PowerShell Workflow, graphical runbooks based on Windows PowerShell) and often omits or minimizes Linux-specific details, especially for hybrid worker scenarios. Python runbooks receive less coverage, and Linux-specific instructions or examples are sparse or missing.

Recommendations:

Provide Linux-specific examples and troubleshooting steps alongside or before Windows examples, especially for hybrid worker scenarios.
Avoid using only Windows file paths (e.g., C:\modules); include Linux equivalents (e.g., /opt/automation/modules) where relevant.
Clarify which features and limitations apply to Windows, Linux, or both, particularly for hybrid runbook workers.
Expand Python runbook documentation to include Linux-specific package management, environment setup, and known issues.
Where PowerShell is discussed, explicitly note cross-platform capabilities and provide Linux usage notes or caveats.
For graphical and workflow runbooks, clearly state platform support and provide alternatives or workarounds for Linux users.
Ensure that all code samples, troubleshooting steps, and environment variable references are presented for both Windows and Linux contexts.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily focused on Windows and PowerShell, with all examples and module references using Windows PowerShell cmdlets and patterns. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform scripting. Windows-specific tools and classes (e.g., PSCredential, Get-Credential) are mentioned exclusively, and the documentation does not acknowledge or provide alternatives for Linux environments.

Recommendations:

Add equivalent Azure CLI (az) examples for all major steps, such as authentication, credential management, and resource management, to support Linux and macOS users.
Include Bash or Python script examples for common automation tasks, demonstrating how to interact with Azure Automation and Microsoft Entra ID from non-Windows platforms.
Explicitly mention cross-platform options and clarify which steps or modules are Windows-only, providing links or references to Linux-compatible alternatives.
Reorganize sections to present cross-platform or CLI approaches alongside PowerShell, rather than only after or not at all.
Reference documentation for Azure CLI and SDKs in the 'Next steps' section, not just PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows and PowerShell bias. All code examples for creating, using, and managing webhooks are provided exclusively in PowerShell, with no equivalent Bash, curl, or CLI examples for Linux or cross-platform users. Windows/PowerShell tools and cmdlets (e.g., Invoke-WebRequest, Get-Content, Az Module) are used throughout, and there is no mention of Linux-native tools or workflows. Even REST API usage is shown only via PowerShell. The documentation does not address how to perform these tasks from a Linux environment or with cross-platform tools, and the PowerShell-first approach may hinder accessibility for non-Windows users.

Recommendations:

Provide equivalent examples using Bash and curl for all webhook operations (creation, invocation, deletion, etc.), especially for REST API calls.
Include Azure CLI (az) command examples for creating and managing Automation webhooks, as Azure CLI is cross-platform.
Show how to use common Linux tools (e.g., jq, curl, wget) to interact with webhooks and parse responses.
Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users.
Where PowerShell is required (e.g., for runbook code), clarify that PowerShell Core is available cross-platform and provide notes on any differences.
Add a section or callouts for Linux/macOS users, outlining any prerequisites or differences in workflow.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ cmd_examples

⚠️ powershell_heavy

Summary:

The documentation generally provides both Bash (Linux/macOS) and Cmd (Windows) examples for command-line operations, but Windows/Cmd examples are consistently presented alongside or immediately after Bash, sometimes with slightly more detail. There is a mild 'windows_first' bias in the order of presentation (e.g., Visual Studio Code and Windows-specific tools are often mentioned before Linux alternatives), and the inclusion of Cmd tabs and examples throughout. However, Linux is not neglected: Bash examples are present, and Linux-specific details (such as Java 21 support) are included. There are no sections that are Windows-only or that omit Linux equivalents, but the parity could be improved for a more neutral, cross-platform experience.

Recommendations:

Ensure that Bash (Linux/macOS) examples are always presented first, or alternate the order with Cmd examples to avoid implicit prioritization.
Wherever command-line examples are given, explicitly mention that Bash examples apply to Linux/macOS and Cmd to Windows, to clarify for users.
Add explicit references to Linux terminal environments (e.g., GNOME Terminal, Konsole) in the introductory sections, not just 'Terminal'.
In the 'Getting started' and 'Next steps' sections, include links or notes about Linux-specific development environments or workflows, if available.
Review the order of tool mentions (e.g., Visual Studio Code, IntelliJ, Eclipse) to ensure no implicit Windows preference.
Consider adding troubleshooting or environment setup notes specific to Linux (e.g., setting JAVA_HOME in .bashrc/.zshrc, common Linux JDK installation commands).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias in the feature registration section, where Azure PowerShell commands are presented first and in detail, while Azure CLI (more common on Linux) is only briefly mentioned in passing. The rest of the guide focuses on NFS operations, which are inherently Linux/UNIX-centric, and provides Linux command examples (e.g., umount, mount) exclusively, with no Windows or PowerShell client-side examples. However, the initial registration steps may disadvantage Linux users by not providing full CLI examples up front.

Recommendations:

Provide full Azure CLI command examples for feature registration and status checking, not just a reference link.
Present Azure CLI and PowerShell registration examples side by side, or list CLI first to better support Linux users.
Clarify that the NFS client operations are intended for Linux/UNIX systems, and if Windows NFS client support is relevant, provide equivalent instructions or a note.
Review future documentation for similar patterns where Windows tooling is prioritized or Linux tooling is only referenced indirectly.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows, such as the Active Directory Users and Computers MMC snap-in, and providing detailed steps and screenshots for Windows-based attribute management. There are no equivalent instructions or examples for managing LDAP POSIX attributes from Linux or cross-platform tools. The documentation also references Windows-specific commands and features (e.g., 'net view', Windows File Browser) without Linux or macOS alternatives, and generally presents Windows approaches before Linux ones.

Recommendations:

Provide equivalent instructions and examples for managing LDAP POSIX attributes using Linux tools (e.g., ldapmodify, ldapadd, or Apache Directory Studio) alongside the Windows MMC snap-in.
Include Linux/macOS examples for relevant administrative tasks, such as viewing or editing LDAP attributes, mounting NFS shares, and managing permissions.
When referencing Windows-specific commands (e.g., 'net view', Windows File Browser), also mention Linux equivalents (e.g., smbclient, Nautilus, or command-line tools).
Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or group them under clear OS-specific headings.
Add screenshots or command-line examples from Linux environments where appropriate, especially in sections discussing NFS or LDAP configuration.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily provides Azure PowerShell commands for feature registration and management, with only a brief mention of Azure CLI as an alternative. There are no Linux shell or cross-platform CLI examples, and the PowerShell commands are presented first and in detail, which may disadvantage Linux users or those who prefer CLI tools.

Recommendations:

Provide equivalent Azure CLI command examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that all operations can be performed from Linux, macOS, or Windows using Azure CLI.
Include example shell commands (bash) for Linux users where applicable, especially for NFS-related tasks.
Balance the order of examples so that CLI and PowerShell are given equal prominence, or lead with the more cross-platform option.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page provides a detailed PowerShell command and Windows-specific instructions for resolving NFS client performance issues on Windows, but does not offer equivalent Linux commands or troubleshooting steps. This creates an imbalance, as Linux is a primary platform for NFS usage. Other sections reference Linux (e.g., /etc/fstab) but do not provide Linux-centric troubleshooting or examples where Windows-specific guidance is given.

Recommendations:

For every Windows-specific example (such as enabling CaseSensitiveLookup via PowerShell), provide an equivalent Linux example or troubleshooting step, or explicitly state if the issue is Windows-only.
When discussing mounting or configuring NFS, ensure both Linux and Windows procedures are included, especially in troubleshooting scenarios.
If a problem or configuration is unique to Windows, clarify this in the documentation to avoid confusion for Linux users.
Include Linux command-line examples (e.g., using mount options, sysctl, or nfs-utils configuration) where appropriate, especially in sections where only Windows commands are currently shown.
Review the document for other places where Windows tools or patterns are mentioned without Linux parity, and add Linux equivalents or cross-references.

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 emphasis than their Linux/NFS counterparts. SMB (Windows) is described as the primary use case for dual-protocol and identity management, and Windows terminology (NTFS, SID, NTLM, Active Directory) is used extensively. Official support is stated for SMB on Windows/macOS, but not for Linux (Samba), and there is a lack of Linux command-line or configuration examples compared to references to Windows tools and concepts. Linux/NFS details are present, but practical Linux usage examples (e.g., mounting, permissions, troubleshooting) are missing.

Recommendations:

Provide parallel Linux/NFS examples for all Windows/SMB concepts, such as showing Linux mount commands, permission management, and troubleshooting steps.
Explicitly mention and provide guidance for using Samba on Linux, including any limitations or best practices.
Balance the order of presentation so that Linux/NFS and Windows/SMB are introduced and discussed with equal prominence.
Include Linux-specific tools and configuration file references (e.g., /etc/fstab, idmapd.conf, nfs-utils) alongside Windows tools (e.g., NTFS, SID, Active Directory).
Clarify support status and provide troubleshooting resources for Linux clients (including Samba) to avoid the perception of Windows preference.
Add practical Linux-focused scenarios and FAQs, especially for dual-protocol and identity mapping situations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation is heavily focused on Windows environments, specifically Microsoft Exchange and System Center DPM, both of which are Windows-only products. All instructions, tools, and examples assume a Windows Server environment, with references to Windows file paths, the DPM Administrator Console, and PowerShell automation. There are no Linux equivalents, examples, or even mentions of cross-platform scenarios, making the documentation inaccessible to Linux users or those seeking platform-neutral guidance.

Recommendations:

Clearly state at the beginning that System Center DPM and Exchange Server are Windows-only products, and that the guide is not applicable to Linux environments.
If Azure Backup supports Linux servers or workloads, provide links or sections for Linux backup scenarios, including supported tools and workflows.
For automation, offer examples using cross-platform tools (such as Azure CLI) where possible, or clarify that PowerShell examples are only for Windows.
If any steps or concepts are relevant to Linux (e.g., Azure Backup agent installation, vault credential management), provide parallel Linux instructions or references.
Consider including a comparison table or FAQ addressing platform support and limitations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented toward Windows environments. All administrative steps, scripts, and configuration examples assume the use of Windows tools (e.g., Registry Editor, Certificate Import Wizard, PowerShell scripts). There are no instructions or examples for performing these tasks on Linux-based Azure Backup Server installations, nor are Linux equivalents for registry or certificate management provided. The documentation implicitly assumes the Azure Backup Server is running on Windows, with no mention of Linux support or parity.

Recommendations:

Explicitly state if Azure Backup Server is only supported on Windows. If Linux is not supported, clarify this early in the documentation.
If Linux is supported, provide parallel instructions for Linux environments, including:
- How to import CA certificates using Linux tools (e.g., update-ca-certificates, keytool, etc.).
- How to configure equivalent settings (such as disabling certificate validation) using Linux configuration files or environment variables.
- How to run administrative scripts using Bash or Python, or provide Linux-compatible versions of PowerShell scripts.
- How to modify application settings that are stored in the Windows Registry on Linux (e.g., via config files or environment variables).
Add notes or callouts indicating which steps are Windows-specific and provide alternatives or guidance for Linux users.
Ensure that screenshots and UI references are not exclusively Windows-centric if Linux GUIs or CLI tools are available.
Consider including a section on cross-platform support and any limitations or differences between Windows and Linux deployments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on System Center Data Protection Manager (DPM), a Windows-only tool, and references to PowerShell for automation. There are no examples or mentions of Linux-based backup solutions, commands, or cross-platform alternatives. All instructions and screenshots assume a Windows environment, and there is no guidance for Linux administrators or mixed OS environments.

Recommendations:

Include information about cross-platform or Linux-compatible backup solutions for SharePoint (if any), or clarify that DPM is Windows-only and suggest alternatives for Linux environments.
Provide equivalent command-line examples for Linux where possible, or explicitly state the lack of Linux support.
If automation is discussed via PowerShell, mention if there are REST APIs, CLI tools, or other automation options usable from Linux.
Add a section addressing backup and restore strategies for organizations with non-Windows infrastructure, or link to relevant Azure/Linux documentation.
Clearly state the OS requirements and limitations at the beginning of the article to set expectations for non-Windows users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows environments, specifically focusing on Data Protection Manager (DPM), a Windows-only backup tool. All examples, workflows, and screenshots are based on the DPM GUI, which is only available on Windows. There is no mention of Linux-based SQL Server workloads, nor are there any instructions or examples for backing up SQL Server on Linux. The only automation reference is to PowerShell, a Windows-centric scripting environment.

Recommendations:

Add a section or parallel documentation for backing up SQL Server on Linux to Azure, using supported tools (such as Azure CLI, azcopy, or native SQL tools).
Explicitly state that DPM is a Windows-only tool and provide alternatives for Linux environments, such as Azure Backup integration with Linux or third-party solutions.
Include command-line examples for Linux (bash, shell scripts) alongside PowerShell examples.
Mention and link to documentation for cross-platform backup solutions where available.
Ensure that automation and scripting guidance covers both PowerShell (Windows) and bash/CLI (Linux) scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented towards Windows environments, specifically System Center DPM, which is a Windows-only product. All examples, prerequisites, and tooling references (such as PowerShell, .NET Framework, and MARSAgentInstaller.exe) are Windows-specific. There are no examples or guidance for Linux-based backup scenarios, nor are Linux tools or commands mentioned. The documentation assumes the use of Windows UI elements and Windows server environments throughout.

Recommendations:

Clearly state at the beginning that DPM is a Windows-only product, and provide links or references to equivalent Azure Backup solutions for Linux workloads.
Where possible, include parallel documentation or links for backing up Linux servers to Azure using native Azure Backup agents or other supported Linux backup solutions.
If PowerShell or Windows tools are required, explicitly mention that these steps are for Windows, and provide alternative steps or references for Linux users where applicable.
Add a comparison table or section outlining backup options for both Windows and Linux environments to help users choose the right solution.
Ensure that troubleshooting and prerequisites sections clarify OS-specific requirements and direct Linux users to appropriate resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased towards Windows environments. All installation, configuration, and operational steps assume the use of Windows Server, with no mention of Linux or cross-platform support. Only Windows tools (such as PowerShell cmdlets, Windows Server Deduplication, and Windows registry edits) are referenced, and all examples and instructions are specific to Windows. There are no Linux equivalents, examples, or even statements about (non)support for Linux platforms.

Recommendations:

Explicitly state whether Linux is supported or not for Azure Backup Server. If not supported, clarify this early in the documentation.
If any Linux support exists (for agents, workloads, or management), add equivalent Linux installation and configuration instructions.
Provide examples using Linux tools (e.g., shell commands) where applicable, or clarify that only Windows tools are supported.
Include a comparison table of supported platforms (Windows vs. Linux) for transparency.
Mention any Linux-specific limitations or alternatives for users managing mixed environments.
If only Windows is supported, add a section recommending alternative backup solutions for Linux workloads.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes backup and recovery of SQL Server 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 features. There are no mentions of Linux-based SQL Server deployments, nor are there any instructions or examples for Linux environments.

Recommendations:

Clearly state early in the documentation that MABS and DPM are Windows-only solutions, and specify supported operating systems.
Provide guidance or links for backing up SQL Server running on Linux, such as using Azure Backup with Linux VMs or native SQL Server backup tools.
Include a section comparing backup options for SQL Server on Windows vs. Linux, highlighting parity and differences.
If possible, offer alternative workflows or references for Linux users, such as using Azure Backup for Linux VMs or scripting native SQL Server backups on Linux.
Avoid assuming all SQL Server deployments are on Windows; acknowledge cross-platform scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily Windows-centric: all instructions, screenshots, and examples assume Windows Server environments, specifically referencing Server Manager, ReFS, and PowerShell cmdlets. There are no Linux equivalents or cross-platform guidance, and all tooling and workflows are based on Windows-only features. Linux users are not addressed at all.

Recommendations:

Clarify early in the documentation whether Azure Backup Server supports Linux as a host or if it is strictly a Windows-only product. If it is Windows-only, state this explicitly to avoid confusion.
If any features or workflows are available on Linux, provide parallel instructions and examples for Linux environments, including relevant CLI commands and storage management tools (e.g., using LVM, ext4/xfs, or Linux equivalents of storage pools).
Where PowerShell is used, offer Bash or shell script alternatives if Linux is supported.
Include screenshots or terminal output from Linux environments where applicable.
If Modern Backup Storage and workload-aware storage are not available on Linux, clearly state this and provide alternative recommendations 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 workload and recovery examples are for Windows-based systems and applications (e.g., Windows Server, SQL Server, Exchange, SharePoint), with Linux relegated to a single, limited section. Windows tools and patterns (e.g., NTFS, VSS, Control Panel, system state, bare metal recovery) are referenced throughout, while Linux-specific backup scenarios, tools, or recovery options are not discussed. The Linux section only covers VM-level backup, with no mention of file-level or application-level protection, and requires a Windows-based host for protection. There are no Linux command-line or configuration examples, and Windows terminology and requirements (e.g., NTFS, Visual C++ redistributable, Volume Shadow Copy Service) are presented as defaults.

Recommendations:

Provide Linux-specific backup and recovery scenarios, including file-level and application-level protection, not just VM-level.
Include examples and documentation for Linux-native tools and filesystems (e.g., ext4, XFS, LVM), and clarify support or limitations.
Offer parity in documentation structure: for every Windows workload example, provide a Linux equivalent or explicitly state support status.
Add Linux command-line examples (e.g., shell scripts, CLI commands) for agent installation, configuration, and recovery.
Clarify whether Linux VMs can be protected with application consistency (e.g., using pre/post scripts or VSS-like mechanisms), and document procedures.
Avoid presenting Windows tools and patterns (e.g., NTFS, VSS, Control Panel) as the only or default approach; mention Linux alternatives or note their absence.
Explicitly state any limitations or roadmap for Linux support to set user expectations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively references the Microsoft Azure Backup Server (MABS) console, which is a Windows-only application. All instructions and screenshots pertain to the Windows GUI, with no mention of Linux environments, command-line alternatives, or cross-platform considerations. There are no Linux-specific instructions, nor are there references to managing telemetry via non-Windows tools.

Recommendations:

Clarify early in the documentation that MABS is a Windows-only product, if applicable. If not, provide equivalent instructions for Linux environments.
If telemetry settings can be managed via command-line or scripts (e.g., PowerShell, CLI), provide those examples and note their platform compatibility.
If a Linux version or alternative exists, include parallel steps and screenshots for Linux users.
Explicitly state platform limitations and suggest alternatives for non-Windows users, if MABS is not available on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a strong Windows bias. Windows workloads, tools, and file systems are prioritized throughout, with detailed support matrices and recovery options for Windows environments. Linux support is limited to guest VMs, with only file-consistent snapshots and no item-level/file-level recovery. Windows-specific technologies (NTFS, VSS, ReFS, deduplication, FAT/FAT32, system state, bare metal recovery) are referenced exclusively, and Linux is only mentioned in a single, minimal section. There are no Linux-native backup scenarios or examples, and no mention of Linux file systems or tools.

Recommendations:

Provide Linux-native backup scenarios, not just Linux as a guest VM.
Include item-level/file-level recovery options for Linux VMs, or clearly state limitations and possible workarounds.
Add examples and documentation for Linux file systems (e.g., ext4, XFS) and clarify their support status.
Mention Linux tools and patterns where relevant, not just Windows-specific technologies like VSS, NTFS, ReFS.
Ensure parity in documentation structure: for every Windows example or scenario, provide a Linux equivalent or explicitly state if unsupported.
Clarify agent support and installation procedures for Linux workloads, not just Windows.
Consider a dedicated section for Linux backup and recovery best practices, limitations, and troubleshooting.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting all command-line examples (both PowerShell and Azure CLI) with Windows-style prompts (C:\>), referencing PowerShell modules and workflows first, and omitting explicit Linux/macOS instructions or examples. There is no mention of Linux-specific shell usage, installation, or file paths, and the CLI examples use Windows conventions exclusively.

Recommendations:

Provide both Windows and Linux/macOS command-line examples, using appropriate prompts (e.g., $ for bash, C:\> for Windows).
Include installation instructions for PowerShell and Azure CLI on Linux/macOS, or link to relevant cross-platform guides.
Avoid using Windows-specific file paths or prompts in CLI examples unless specifically targeting Windows users.
Clarify that both PowerShell and Azure CLI are cross-platform, and provide usage notes for different operating systems.
If screenshots are included, consider showing both Windows and Linux/macOS interfaces where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing PowerShell (a Windows-centric tool) in both instructions and tooling tables, frequently referencing PowerShell cmdlets before or instead of cross-platform alternatives. The Azure portal (GUI) and PowerShell are emphasized for key operations, with the Azure CLI (which is more cross-platform) only mentioned later and with less detail. There are no explicit Linux/macOS-specific instructions or examples, and no mention of platform-specific considerations for non-Windows users.

Recommendations:

Ensure all PowerShell examples are paired with equivalent Azure CLI examples, and present both side-by-side or in parallel sections.
Explicitly state that Azure CLI is cross-platform and provide installation and usage notes for Linux/macOS users.
Where GUI instructions are given, clarify that the Azure portal is accessible from any OS with a modern browser.
Review all tooling tables to include and highlight cross-platform tools (e.g., Azure CLI, PP CLI) equally with PowerShell.
Add a section or notes addressing any platform-specific differences or limitations for Linux/macOS users.
Avoid assuming PowerShell is the default scripting environment; clarify when a step is Windows-specific or provide alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a subtle Windows bias by referencing Microsoft-specific tools and admin centers (such as Microsoft 365 Admin Center and Azure portal) without mentioning cross-platform or Linux-native alternatives. There are no command-line examples (PowerShell or otherwise), but where command-line is referenced (in related links), it defaults to Azure PowerShell tabs. No Linux CLI or Azure CLI examples or guidance are provided, and the workflow assumes use of Microsoft portals and tools, which are more familiar to Windows users.

Recommendations:

Include Azure CLI examples alongside or instead of Azure PowerShell, as Azure CLI is cross-platform and widely used on Linux.
When referencing admin centers or portals, mention that these are web-based and accessible from any OS, or provide equivalent command-line instructions.
In related links, ensure that documentation pages default to or include Linux/CLI tabs, not just Azure PowerShell.
Explicitly state that actions can be performed from any OS, and provide parity in instructions for Linux/macOS users.
Where possible, avoid assuming familiarity with Microsoft-specific tools and provide context or alternatives for users from non-Windows backgrounds.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. It frequently references Windows-specific domains (e.g., login.windows.net), lists Azure CLI and Azure PowerShell as primary tools (with PowerShell examples included), and refers to the Azure portal UI, which is more familiar to Windows users. While most command-line examples use Azure CLI and kubectl (cross-platform), PowerShell is mentioned as an alternative to Azure CLI, but no explicit Linux shell or bash alternatives are provided for PowerShell commands. Additionally, Windows-specific terminology and endpoints are referenced before or instead of Linux equivalents, and there is a lack of explicit Linux-focused troubleshooting or installation guidance.

Recommendations:

Where PowerShell is mentioned, provide equivalent bash commands for Linux users, or clarify that Azure CLI commands are cross-platform.
When referencing Azure portal steps, clarify that the portal is web-based and not Windows-specific.
When listing domains or endpoints (e.g., login.windows.net), clarify their cross-platform nature or provide context for Linux users.
Include troubleshooting and installation notes specific to Linux environments, especially for common issues (e.g., permissions, networking).
If referencing Azure CLI, explicitly state its cross-platform compatibility and provide installation links for Linux and macOS.
Avoid listing Windows tools or endpoints first unless they are required; otherwise, present them in a neutral or platform-agnostic order.
Add explicit notes or examples for Linux users where behavioral differences may exist (e.g., file paths, environment variables).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a strong Windows bias. All command-line instructions are provided exclusively using PowerShell, with no mention of Bash, Linux CLI, or cross-platform alternatives. The focus is on Microsoft Entra Domain Services (which is Windows Server Active Directory-compatible), and tools and patterns referenced (such as PowerShell modules and service principals) are specific to Windows environments. There are no Linux or open-source identity provider examples, and the documentation assumes a Windows-centric infrastructure throughout.

Recommendations:

Provide equivalent command-line instructions using Azure CLI (az), which is cross-platform, alongside PowerShell examples.
Include guidance for users managing clusters from Linux or macOS environments, such as using Bash scripts or REST APIs.
Mention and, where possible, document integration patterns with non-Windows identity providers (e.g., MIT Kerberos, OpenLDAP) or clarify their (non-)support.
Avoid assuming the reader is operating from a Windows environment; explicitly state platform requirements and offer alternatives.
Reorder sections or examples so that cross-platform or neutral tooling (e.g., Azure Portal, Azure CLI) is presented before or alongside Windows-specific tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing only a PowerShell example for certificate creation, referencing Windows-specific tools (e.g., ldp.exe), and instructing users to test network setup by joining a Windows VM and using Windows tools. There are no equivalent Linux examples or instructions for performing these tasks on Linux-based systems, despite HDInsight clusters often being Linux-based.

Recommendations:

Provide equivalent Linux command-line examples for certificate creation (e.g., using OpenSSL) alongside the PowerShell example.
Include instructions for testing network setup from a Linux VM, such as using 'ping', 'ldapsearch', or 'openssl s_client' for LDAPS connectivity.
Mention Linux tools and workflows (e.g., using 'nslookup', 'dig', or 'host' for DNS resolution) in parallel with Windows tools.
Avoid assuming the use of Windows VMs for validation steps; explicitly state that either Windows or Linux VMs can be used, and provide guidance for both.
Ensure that all critical configuration and validation steps are documented for both Windows and Linux environments to support cross-platform users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias. All command-line and script examples use Windows tools (CertUtil, PowerShell), and all file paths and instructions assume a Windows environment. There are no Linux or cross-platform examples for verifying file hashes, running the installer, or managing the appliance. The documentation references Windows-specific tools and patterns (e.g., .ps1 scripts, C:\ paths, administrator command window) and does not mention or provide alternatives for Linux users.

Recommendations:

Provide equivalent Linux/bash commands for verifying file hashes (e.g., sha256sum).
Include instructions for running the installer script on Linux-based hosts, if supported, or clarify platform support.
Offer examples using Linux shell (bash) for script execution and file extraction.
Document the location of log files and configuration steps for Linux-based appliances, if applicable.
Explicitly state platform requirements and, if Windows-only, clearly indicate this early in the documentation.
If the appliance supports Linux, ensure parity in screenshots and step-by-step instructions for both platforms.

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 metadata, tools, and PowerShell cmdlets are consistently presented first and in greater detail than Linux equivalents. Windows-specific tools (WMI, PowerShell, Registry, Get-WindowsFeature, etc.) are referenced throughout, while Linux examples, though present, are often grouped together and sometimes less detailed. Some sections (e.g., ASP.NET, Java, Spring Boot web app data) only mention Windows servers, omitting Linux scenarios. The documentation also uses Windows-centric terminology and patterns, and Linux parity is sometimes lacking in both depth and breadth.

Recommendations:

Present Linux and Windows examples side-by-side or in parallel tables/sections to ensure equal visibility.
Where Windows PowerShell cmdlets or WMI classes are listed, provide equivalent Linux commands or tools (e.g., systemctl, lsof, etc.) where possible.
Expand Linux sections to match the detail provided for Windows, especially for application and web server discovery (e.g., include Apache, NGINX, Tomcat on Linux).
Explicitly state when a feature or data point is only available for Windows, and clarify Linux support status.
Include Linux-specific application and feature discovery (e.g., systemd services, package managers, web servers) in the same detail as Windows features.
Review and update sections like ASP.NET, Java, and Spring Boot web app data to include Linux scenarios or clarify if not supported.
Avoid always listing Windows first; alternate order or use neutral grouping (e.g., 'On Windows:' / 'On Linux:').

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a strong Windows bias: all deployment and configuration steps for the Azure Migrate scale-out appliance are exclusively described for Windows Server environments. Only PowerShell scripts and Windows command-line tools (e.g., CertUtil) are provided, with no mention of Linux-based deployment, tools, or equivalent commands. The appliance is required to run on Windows Server 2019/2022, and all examples, screenshots, and troubleshooting steps assume a Windows environment. There is no guidance for Linux users or for deploying the appliance on a Linux server.

Recommendations:

Provide explicit information about whether Linux-based deployment of the Azure Migrate appliance is supported. If not, state this clearly at the beginning of the documentation.
If Linux deployment is supported, add parallel instructions, scripts, and examples for Linux environments (e.g., Bash scripts, Linux command-line equivalents for checksum validation such as sha256sum).
Include guidance on how to perform prerequisite checks, appliance installation, and configuration on Linux servers if supported.
Mention any limitations or differences in functionality between Windows and Linux deployments, if applicable.
If only Windows is supported, consider providing rationale and possible workarounds for Linux-only environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing and exclusively providing Windows-based tools and instructions. PowerShell is the only script-based installer mentioned, and all command-line examples (such as hash verification) use Windows Command Prompt tools (CertUtil). File paths and instructions for installing dependencies (like VDDK) assume a Windows environment. There are no Linux equivalents or examples, and Linux-based deployment or verification methods are not discussed.

Recommendations:

Provide equivalent Linux-based instructions for all command-line operations, such as verifying OVA file hashes (e.g., using sha256sum).
Include guidance for running the appliance installer script on Linux systems, if supported, or clarify platform limitations.
Mention Linux file paths and installation steps for dependencies like VDDK, or explicitly state if only Windows is supported.
Ensure that examples and screenshots reflect both Windows and Linux environments where possible.
If PowerShell is the only supported installer, clearly state this limitation and provide rationale or alternatives for Linux users.

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 detailed instructions for setting up the Azure Migrate appliance using a PowerShell script on Windows Server, but does not offer an equivalent Linux-based setup method. The installation path for required tools (e.g., VDDK) is specified using Windows file paths only. Windows authentication mechanisms and tools (such as PowerShell and Active Directory) are described in detail, while Linux alternatives are mentioned but not elaborated upon or exemplified. There are no Linux shell or command-line examples, and the documentation often lists Windows steps or tools before mentioning Linux support or alternatives.

Recommendations:

Provide a Linux-based method for setting up the Azure Migrate appliance, such as a shell script or instructions for deploying on a Linux VM, alongside the PowerShell/Windows Server method.
Include Linux file paths and installation instructions for required components like the VDDK, not just Windows paths.
Offer Linux command-line examples (e.g., using SSH, scp, or Linux-based configuration steps) wherever Windows/PowerShell examples are given.
Ensure that Linux authentication mechanisms (such as SSH key-based authentication) are described with equal detail and step-by-step guidance as Windows authentication.
List Linux and Windows options together, or alternate which is presented first, to avoid always prioritizing Windows.
Clarify any limitations or differences in feature support between Windows and Linux, and provide workarounds or alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page shows a Windows bias primarily by referencing Windows agents and tools first (or exclusively) in several connector descriptions, especially for Microsoft Exchange and Security Events. Windows-specific terminology (e.g., 'Windows agent', 'Windows machines') is used without equivalent Linux context in multiple places. In contrast, Linux (Syslog) is mentioned only once, and there are no Linux-specific setup or troubleshooting examples for connectors that could apply to both platforms. There is also a lack of parity in prerequisites and instructions for Linux environments.

Recommendations:

For connectors that mention 'Windows agent' or 'Windows machines', add equivalent references and instructions for Linux agents/machines where applicable.
Provide Linux-specific setup, configuration, and troubleshooting examples alongside Windows examples for all relevant connectors.
Where prerequisites or permissions are listed for Windows (e.g., PowerShell, Windows agent), include corresponding Linux commands, tools, or agent instructions.
Avoid using Windows-centric language (e.g., 'Windows agent') as the default; instead, use cross-platform terms or explicitly mention both Windows and Linux.
Ensure that all connectors which can be used on Linux have clear documentation for Linux environments, including links to Linux agent installation and configuration guides.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation exhibits a clear Windows bias. Windows tools (RoboCopy, Azure File Sync, Storage Migration Service) are emphasized and described in detail, while Linux migration scenarios receive minimal attention and lack concrete examples or tool guidance. Windows terminology (NTFS, ACLs, DFS-N, etc.) is used throughout, and migration tables and tool recommendations are Windows-centric. Linux migration is only briefly mentioned, with no step-by-step guides or Linux-native tool recommendations.

Recommendations:

Provide Linux-focused migration examples, including step-by-step guides using Linux-native tools (e.g., rsync, cifs-utils, smbclient) for copying data to Azure file shares.
Include Linux command-line examples alongside Windows/Powershell examples when demonstrating mounting, copying, or migrating data.
Expand the migration guides table to include more detailed Linux scenarios, such as migrating from Linux SMB servers or NFS to Azure Files, and clarify tool support for Linux environments.
Discuss Linux file permission and metadata mapping (e.g., POSIX ACLs vs. NTFS ACLs) and any limitations or considerations.
Balance the order of presentation so that Linux and Windows tools and scenarios are introduced with equal prominence.
Reference Linux-compatible third-party tools (e.g., rsync, rclone) where appropriate, and provide links to their documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily biased towards Windows environments. It exclusively recommends and demonstrates the use of RoboCopy, a Windows-only tool, for migrating to Azure Files. All examples, mounting instructions, and optimization tips are tailored to Windows Server and PowerShell. There is no mention of equivalent Linux tools or workflows, nor are there any Linux-specific examples or guidance, despite the initial checklist noting Linux servers as possible sources.

Recommendations:

Include Linux migration options, such as using rsync, smbclient, or mount.cifs for SMB-based transfers to Azure Files.
Provide parallel Linux command-line examples for mounting Azure file shares and copying data.
Discuss the limitations and considerations for Linux-based SMB clients when migrating to Azure Files.
Reference or link to Linux-specific documentation for Azure Files migrations.
Clarify in the introduction that the guide is Windows-specific, or create a separate Linux migration guide for parity.
Mention cross-platform tools (e.g., AzCopy, where appropriate) and their usage from Linux environments, even if with caveats.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias, primarily by listing Windows-centric tools (such as Visual Studio and PowerShell) before cross-platform or Linux-native alternatives, especially in the C# section. Visual Studio (Windows-only) is always listed first, and PowerShell is mentioned as an HTTP test tool before curl. However, the documentation does make efforts to mention Linux and macOS support, especially for Visual Studio Code and command-line tools. There are no outright missing Linux examples, but the ordering and tool emphasis favor Windows.

Recommendations:

In each language section, list cross-platform tools (such as Visual Studio Code and command-line/terminal) before Windows-only tools like Visual Studio.
In the HTTP test tools section, list curl (a ubiquitous Linux tool) before PowerShell and Microsoft Edge.
Where possible, provide explicit Linux/macOS command-line examples alongside or before Windows/PowerShell examples.
Clarify in tables and descriptions which tools are cross-platform and which are Windows-only, to help Linux users quickly identify their options.
Consider adding a dedicated section or callout for Linux/macOS development tips or common issues.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation mentions both Linux (rsync) and Windows (robocopy) tools for data migration, but consistently lists the Windows tool (robocopy) after the Linux tool (rsync) and does not provide detailed examples for either. However, there is a slight bias in that robocopy (a Windows-specific tool) is highlighted for SMB workloads, while no Linux-native SMB migration tool (such as smbclient or cifs-utils) is mentioned. Additionally, while the documentation is generally cross-platform, it does not provide parity in tool recommendations for Linux users working with SMB shares.

Recommendations:

Include Linux-native SMB migration tools (e.g., smbclient, cifs-utils, or mount.cifs with cp/rsync) alongside robocopy for SMB workloads.
Provide example commands for both Linux and Windows environments for NFS and SMB migrations.
Explicitly state that both Linux and Windows tools are supported for both NFS and SMB, and offer at least one example for each.
Consider listing tools in a neutral order (e.g., alphabetically or grouped by protocol) rather than by OS preference.

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 (including GUI and command-line) for Windows users. Windows-specific tools (File Explorer, dir command) are described in detail, while the Linux section only mentions the df command with less elaboration. There is also a reference to PowerShell in the REST API section, but no equivalent mention of Linux scripting tools.

Recommendations:

Alternate the order of Windows and Linux sections, or present them in parallel to avoid implicit prioritization.
Provide equally detailed instructions and screenshots for Linux users, including both GUI (if applicable, e.g., GNOME Files) and command-line methods.
Mention Linux scripting or automation tools (e.g., Bash scripts, cron jobs) in sections where PowerShell is referenced.
Ensure parity in troubleshooting notes and caveats for both platforms.
Where possible, use neutral language (e.g., 'On Windows, do X. On Linux, do Y.') and avoid always listing Windows first.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page primarily describes known issues and their workarounds for Azure VMware Solution. While most content is platform-neutral, there are a few instances of Windows bias: remediation steps for VMware Tools vulnerabilities reference only the 'Set-Tools-Repo' Run command without clarifying if it applies to both Windows and Linux VMs, and one issue specifically mentions 'VMware Tools for Windows' without discussing Linux equivalents. No Linux-specific guidance or examples are provided, and there is no mention of Linux guest tools or remediation steps for Linux VMs.

Recommendations:

For issues involving VMware Tools, clarify whether the remediation steps (such as using 'Set-Tools-Repo') apply to both Windows and Linux VMs. If not, provide equivalent instructions for Linux guests.
Where an issue references 'VMware Tools for Windows', explicitly state if Linux VMs are affected or provide parallel guidance for Linux.
When referencing commands or tools, specify their applicability to both Windows and Linux environments, or provide platform-specific alternatives as needed.
Consider including examples or notes for Linux guest VM administrators, especially for common cross-platform tasks such as updating VMware Tools or responding to security advisories.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by listing Windows as a primary supported platform (with a dedicated .NET SDK), while Linux is only mentioned in the context of browser support for the JavaScript SDK. There are no Linux-native SDKs, tools, or examples provided, and Linux is not included as a first-class platform in feature tables or SDK links. Linux users are limited to using the web SDK in supported browsers, with no mention of parity for native development or guidance for Linux environments.

Recommendations:

Explicitly mention Linux support (or lack thereof) in the SDK links and feature tables, clarifying options for Linux developers.
If native Linux SDKs are unavailable, provide guidance or workarounds for Linux users (e.g., using the Web SDK in Electron or other cross-platform frameworks).
Add Linux-specific examples or notes where relevant, especially in sections discussing platform support, installation, and development environments.
Ensure that Linux is not only mentioned as a secondary browser platform but is considered in parity with Windows and macOS in all relevant documentation tables and sections.
If Windows-specific features exist, clearly document their absence or alternatives for Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides browser troubleshooting steps that reference Edge and Chrome (and Safari), but omits Linux-specific browsers (such as Firefox) and does not mention Linux-specific instructions for clearing cache or cookies. The order of browser instructions consistently lists Edge (a Microsoft product) first, which may reinforce a Windows-centric perspective. There are no command-line or OS-specific instructions, but the lack of Linux browser examples and the prioritization of Edge indicate a subtle Windows bias.

Recommendations:

Include instructions for Firefox, which is widely used on Linux, for clearing cache/cookies and private browsing.
Add a note or section for Linux users, clarifying that steps for Chrome/Firefox apply to Linux as well, and specify any differences if present.
Rotate the order of browser instructions or use alphabetical order to avoid consistently prioritizing Edge.
Explicitly mention that the instructions are applicable across operating systems where possible, or provide OS-specific notes as needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The tutorial demonstrates a Windows bias by exclusively using Windows Server as the example OS for the workload VM and referencing Windows-specific tools (e.g., Internet Explorer, Remote Desktop) for testing. There are no Linux-based examples or instructions for deploying or testing with a Linux VM, nor are Linux-compatible tools or workflows mentioned.

Recommendations:

Add parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the workload subnet.
Include Linux-specific steps for connecting to the VM (e.g., using SSH instead of RDP) and for testing outbound connectivity (e.g., using curl or wget instead of Internet Explorer).
When describing firewall rule testing, provide both Windows and Linux command-line examples for DNS resolution and web access.
Explicitly mention that the tutorial applies to both Windows and Linux workloads, and provide links to relevant Linux documentation where appropriate.
Ensure that screenshots and UI references are not OS-specific, or provide alternatives for both platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page generally maintains a neutral tone regarding platform bias, but in the 'Next steps' section, it lists 'Work in Apache Hadoop on HDInsight from a Windows PC' before any Linux-specific guidance. Additionally, it references a Windows-specific tooling page without mentioning Linux equivalents, which may suggest a subtle Windows bias.

Recommendations:

Add a parallel link or section for 'Work in Apache Hadoop on HDInsight from a Linux PC' or 'Linux tools for HDInsight' in the 'Next steps' section.
Ensure that Linux-based workflows and tools are mentioned alongside Windows options, ideally in the same section or with equal prominence.
Review referenced documentation (such as 'hdinsight-hadoop-windows-tools.md') to ensure Linux parity in examples and tooling guidance.
Consider reordering or grouping platform-specific links together, or providing a platform-neutral introduction before listing OS-specific resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by specifying 'Windows' as the operating system in the App Service creation step, without mentioning Linux as an option or providing equivalent instructions/examples for Linux-based App Service apps. There are no Linux-specific notes, nor are there alternative steps or clarifications for users deploying on Linux. All examples and configuration steps implicitly assume a Windows environment.

Recommendations:

Explicitly mention that App Service supports both Windows and Linux, and provide guidance for both.
In the 'Configure the Basics tab' section, include a table row for 'Operating System' that lists both 'Windows' and 'Linux' as valid options, with notes on any differences.
If there are any differences in deployment, environment variable configuration, or logging between Windows and Linux App Service, provide parallel instructions or callouts.
Add a note clarifying that the sample app and SRE Agent work on both Windows and Linux App Service plans, or specify any limitations.
Where screenshots or UI steps differ between Windows and Linux, provide both or clarify the differences.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation lists 'Create an application gateway using PowerShell' before 'using the Azure CLI' in the 'Next steps' section, which may suggest a Windows-first bias. However, the main content is platform-neutral and does not provide OS-specific examples or mention Windows-only tools elsewhere.

Recommendations:

List Azure CLI before PowerShell in the 'Next steps' section, as Azure CLI is cross-platform and more inclusive for Linux and macOS users.
Ensure that all example links and walkthroughs provide both PowerShell and Azure CLI options, or clearly indicate parity.
Consider adding explicit Linux/macOS instructions or references where appropriate to reinforce cross-platform support.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation is generally cross-platform and focuses on Visual Studio Code, which is available on Windows, macOS, and Linux. However, there is a subtle Windows bias in the Troubleshooting section, where a Windows-specific issue (default terminal shell set to WSL Bash) is mentioned before any Linux/macOS-specific troubleshooting. No explicit Linux or macOS examples or troubleshooting tips are provided, and no Linux-specific tools or shell commands are referenced. The rest of the guide avoids platform-specific instructions, but the troubleshooting section assumes a Windows-first perspective.

Recommendations:

Add troubleshooting tips relevant to Linux and macOS users, such as common shell or permission issues.
When mentioning Windows-specific issues (e.g., WSL Bash), also mention potential equivalents or common issues on Linux/macOS.
Explicitly state that the instructions apply to all supported platforms, and provide clarifications if any steps differ on Linux or macOS.
Where possible, include screenshots or terminal output from both Windows and Linux/macOS environments to reinforce parity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation mentions PowerShell as the first automation client for running ARG queries, followed by CLI and SDK, which may suggest a Windows-first bias. However, it does also mention Azure CLI and SDK, which are cross-platform, and does not provide any OS-specific command-line examples. No PowerShell-specific scripts or Windows-only tools are shown, and the Kusto queries are platform-agnostic.

Recommendations:

List Azure CLI before PowerShell when mentioning automation clients, as CLI is cross-platform and more accessible to Linux users.
Explicitly state that both PowerShell and Azure CLI are supported on Windows, Linux, and macOS.
Provide example commands for both PowerShell and Azure CLI (or Bash) to demonstrate parity.
Include links to Linux/macOS installation guides for Azure CLI and PowerShell to reinforce cross-platform support.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of language, tools, or examples, but it does lack any explicit mention of Linux or cross-platform considerations. For example, the only protocol recommended for data-in-flight is SMB 3.0 with encryption, which is traditionally associated with Windows environments, though it is available on Linux via Samba. There are no examples or guidance for Linux users, nor are Linux-specific tools, protocols, or workflows mentioned. No PowerShell or Windows-specific commands are present, but the absence of Linux parity is notable.

Recommendations:

Explicitly mention Linux compatibility for Data Box operations, including supported protocols (e.g., NFS, SFTP) if available.
Provide examples or references for connecting to Data Box from Linux hosts, including mounting instructions and security considerations.
Clarify whether recommended protocols like SMB 3.0 are supported and secure on Linux (e.g., via Samba), and provide guidance for Linux administrators.
Include any Linux-specific tools or command-line examples for interacting with Data Box devices.
Add a section or note addressing cross-platform (Windows, Linux, macOS) support and best practices.

Create pull request

No problematic pages found in this scan. All pages appear to be Linux-friendly! 🐧