Scan Details - Linux-first Docs for Azure

1727

Pages Scanned

72

Pages Flagged

1727

Changed Pages

4.2%

% Pages Flagged

Scan Information

Started At: 2025-08-19 00:01:04

Finished At: 2025-08-19 00:39:45

Status: completed

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

Current Phase: discovery

Problematic Pages

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. Only Windows-based tools (such as the App Service Migration Assistant MSI and PowerShell scripts) are mentioned, with no Linux or cross-platform migration tools or scenarios discussed. The documentation repeatedly references PowerShell and Windows containers, and there are no examples or guidance for migrating .NET apps from Linux servers or using Linux-native tools.

Recommendations:

Include examples and guidance for migrating .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel) to Azure App Service.
List and describe any available cross-platform or Linux-native migration tools, or clarify if such tools are not currently available.
Provide parity in documentation by offering Linux shell (bash) script examples alongside PowerShell scripts.
Mention Linux containerization options and how to migrate Linux-hosted .NET apps to Azure App Service (Linux).
Clarify in the introduction that the current tools are Windows/IIS-focused, and provide links or guidance for Linux scenarios if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation shows subtle Windows bias by referencing Windows-specific configuration files (web.config), mentioning iisnode settings for Node.js apps, and omitting Linux-native equivalents or examples. While there is a brief mention of Linux (regarding PM2 and multi-core), most configuration and troubleshooting guidance assumes a Windows/IIS environment, with no parallel Linux or cross-platform instructions.

Recommendations:

Provide Linux-native configuration examples (e.g., using app settings, environment variables, or Linux startup scripts) alongside or before Windows-specific ones like web.config.
When referencing iisnode or web.config, clarify that these are Windows/IIS-specific and provide equivalent instructions for Linux-based App Service environments (e.g., using process.json, ecosystem.config.js for PM2, or other Linux process managers).
Ensure all troubleshooting and best practice sections include both Windows and Linux scenarios, or clearly indicate when a recommendation is platform-specific.
Highlight cross-platform tools and patterns where possible, and avoid assuming IIS or Windows as the default hosting environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. In sections where both Windows and Linux are relevant (such as SKU availability), Windows examples and commands are listed before Linux equivalents. Automation examples are provided for both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric), but no Linux shell or scripting examples are given. The UI instructions and screenshots are based on the Azure Portal, which is platform-agnostic, but the inclusion of Azure PowerShell as a primary automation method and the ordering of Windows before Linux in command examples suggest a subtle preference for Windows environments.

Recommendations:

Provide Linux shell scripting examples (e.g., Bash) alongside Azure PowerShell for automation, or clarify that Azure CLI is fully cross-platform.
Alternate the order of Windows and Linux examples, or present them in parallel, to avoid the perception of Windows-first bias.
Explicitly state the cross-platform nature of Azure CLI and highlight its suitability for both Windows and Linux users.
If referencing Azure PowerShell, consider also mentioning or linking to Bash scripting or other Linux-native automation approaches.
Ensure that all features and steps are equally documented for both Windows and Linux, especially in sections where differences exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. Windows terminology and instructions are often presented first (e.g., 'Windows SKU availability' before 'Linux SKU availability'). Azure PowerShell is featured as a primary automation tool, and there is a general emphasis on Windows-specific scenarios (such as the distinction between Windows source code apps and containers). While Linux is mentioned and examples are provided, Windows patterns and tools are generally foregrounded.

Recommendations:

Ensure Linux examples and instructions are presented with equal prominence and, where possible, before or alongside Windows examples.
Expand automation sections to include Bash scripting examples for Linux users, not just Azure CLI and PowerShell.
Clarify when instructions or features are Windows-specific versus Linux-specific, and provide parallel guidance for both platforms.
Include more Linux-centric troubleshooting and operational notes, especially in sections that currently focus on Windows behaviors or tools.
Consider adding a table or matrix summarizing feature availability and differences between Windows and Linux for Premium V4.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page focuses exclusively on the discovery of ASP.NET web apps running on IIS web servers within VMware environments, which are Windows-centric technologies. There are no references to Linux-based web servers (such as Apache or Nginx), nor are there examples or guidance for discovering .NET apps hosted on Linux. All tools and workflows mentioned (Azure Migrate appliance, IIS) are Windows-specific, and Linux scenarios are not addressed.

Recommendations:

Include information and examples for discovering .NET web apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx).
Mention whether Azure Migrate supports Linux-based .NET app discovery, and if not, clarify this limitation.
Provide parity in documentation by listing Linux discovery steps, tools, and dashboards where applicable.
If discovery is Windows-only, explicitly state this in the introduction to set expectations for Linux users.
Add links to resources or documentation for migrating Linux-hosted .NET apps to Azure App Service, if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows instructions, tools, and troubleshooting steps are often presented first or exclusively, such as PowerShell commands for connectivity testing and GUI-based management. Linux support is present but less emphasized, with some features (like the GUI) unavailable and some troubleshooting steps lacking Linux equivalents.

Recommendations:

Provide Linux command-line equivalents for all PowerShell or Windows-specific troubleshooting steps (e.g., use 'nc' or 'telnet' for TCP connectivity testing instead of only 'Test-NetConnection').
When listing instructions or tools, present both Windows and Linux options together or alternate which is presented first.
Where the Windows GUI is referenced, clarify Linux alternatives or explicitly state the lack thereof, and suggest CLI workflows as first-class options.
Expand troubleshooting sections to include Linux-native commands and tools (e.g., 'systemctl' for service management, 'dig' or 'host' for DNS lookups).
Ensure that all code snippets and examples are available for both platforms, not just Windows.
Consider adding a parity table or section that summarizes feature differences and available tools for Windows and Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias primarily in the section addressing Azure Traffic Manager endpoints, where only a PowerShell script is provided for identifying affected resources. There are no equivalent Bash, Azure CLI, or cross-platform script examples for Linux or macOS users. The instructions for running the script explicitly reference PowerShell, and there is no mention of how to perform the same task using tools commonly available on Linux. Elsewhere, while REST API and Azure CLI commands are referenced (which are cross-platform), the only concrete script-based automation example is Windows/PowerShell-centric.

Recommendations:

Provide equivalent Bash or Azure CLI scripts for identifying Traffic Manager profiles with non-Azure endpoints, ensuring Linux and macOS users have a clear path.
When referencing automation scripts, offer both PowerShell and Bash (or at least Azure CLI) alternatives, and indicate their platform compatibility.
Explicitly state that Azure CLI and REST API commands are cross-platform, and provide example invocations in both Windows (PowerShell) and Linux (Bash) shells where appropriate.
Avoid presenting Windows/PowerShell solutions first or exclusively; instead, present cross-platform solutions or clearly label platform-specific instructions.
Consider including a table or section summarizing available tools/scripts for each platform (Windows, Linux, macOS) for all major operational tasks described.

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 and troubleshooting steps reference Windows-specific tools, paths, and patterns (e.g., web.config, node.exe, named pipes, Win32 error codes, Kudu CMD/PowerShell, d:\home\LogFiles). There are no examples or guidance for Linux-based App Service environments, and Linux equivalents (such as PM2, systemd, or Linux file paths) are not mentioned. The document assumes the use of Windows-native concepts and tools throughout.

Recommendations:

Add equivalent sections for Node.js applications running on Azure App Service for Linux, including configuration, troubleshooting, and best practices.
Provide Linux-specific examples (e.g., using PM2 or systemd for process management, Linux file paths, and log locations).
Reference Linux-native debugging and profiling tools (such as node --inspect, top, htop, or Linux-based log analysis).
Where possible, present cross-platform guidance or clearly indicate when a step is Windows-only, and provide a Linux alternative.
Include screenshots and instructions for the Azure App Service Linux environment (e.g., Bash/Kudu Bash console) alongside Windows CMD/PowerShell examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based deployment and configuration patterns for ASP.NET apps. All runtime version discovery examples use Windows file paths and Kudu CMD/PowerShell consoles, with no mention of Linux equivalents. The use of Visual Studio as the primary deployment tool and references to Windows-specific tools and directories further reinforce this bias. There are no examples or instructions for Linux-based App Service environments, nor any mention of Bash or Linux shell commands.

Recommendations:

Provide parallel instructions and examples for Linux-based App Service environments, including how to check .NET runtime versions and access diagnostic tools on Linux.
Include Linux/Bash shell commands alongside CMD/PowerShell examples, especially for tasks like listing installed runtimes.
Mention and demonstrate deployment workflows using cross-platform tools (e.g., dotnet CLI, VS Code) in addition to Visual Studio.
Clarify which instructions apply only to Windows App Service plans and provide links or sections for Linux-specific guidance.
Reference Linux file paths and environment variable access patterns where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias. While most command-line examples use the cross-platform Azure CLI, the instructions for generating a SAS URL specifically reference the Azure Storage Explorer with a link that defaults to Windows tabs. There are no explicit Linux or macOS alternatives or mentions for uploading files or generating SAS tokens, and the Storage Explorer instructions may imply a Windows-centric workflow. No PowerShell or CMD scripts are present, but the lack of Linux-native tool examples (such as using az CLI or REST API for SAS generation/upload) is notable.

Recommendations:

Provide explicit instructions or examples for generating SAS URLs and uploading files using Azure CLI or REST API, which are cross-platform and work on Linux/macOS.
Avoid linking to Storage Explorer documentation with Windows-specific tabs by default; mention that Storage Explorer is available on multiple platforms, or provide platform-agnostic instructions.
Add a section or callout for Linux/macOS users, clarifying how to perform each step without relying on GUI tools or Windows-specific workflows.
Where GUI tools are mentioned, always provide an equivalent CLI alternative to ensure parity for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell-based CLI examples for per-app scaling, with no equivalent examples for Linux users (such as Azure CLI/bash). The PowerShell approach is presented first and exclusively, and there is no mention of cross-platform or Linux-native tooling or workflows.

Recommendations:

Add equivalent Azure CLI (az) examples for all PowerShell commands to support Linux and macOS users.
Explicitly mention that PowerShell examples are for Windows and provide guidance for cross-platform users.
Consider providing bash shell scripts or instructions for Linux environments.
Reorder or parallelize examples so that Windows and Linux approaches are given equal prominence.
Clarify that ARM templates are cross-platform, and highlight this as an option for all users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows-first bias by referencing Windows-style paths (e.g., D:\home\site\wwwroot) before Linux equivalents, and by describing deployment behaviors primarily in terms of Windows directory structures. There are no explicit Linux or cross-platform command-line examples, and Linux-specific nuances are only mentioned in passing. The documentation also refers to Windows-centric deployment patterns and tools (such as FTP with Windows paths) without providing Linux alternatives or examples.

Recommendations:

Present both Windows and Linux directory paths together or list Linux paths first where appropriate (e.g., /home/site/wwwroot before D:\home\site\wwwroot).
Include Linux-specific or cross-platform command-line examples, especially for file paths and deployment steps.
Explicitly mention any differences in behavior or requirements for Linux-based App Service plans.
Provide examples using Linux-native tools (e.g., SCP, SFTP, rsync) alongside FTP or Windows tools.
Clarify any platform-specific limitations or features, and ensure parity in troubleshooting and deployment guidance 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 moderate Windows bias. PowerShell examples are provided alongside Azure CLI, but there are explicit references to Windows tools (IIS, Certreq.exe) for certificate export, and automation examples link to both Azure CLI and PowerShell but not to Bash or Linux-native scripting. When discussing certificate creation, Windows tooling is mentioned before Linux equivalents. There is no explicit Linux-focused workflow or parity in some sections, and Windows-specific scenarios (such as outbound client certificates) are called out without Linux alternatives.

Recommendations:

When mentioning certificate export, provide Linux-native instructions (e.g., using OpenSSL) before or alongside Windows tools like IIS and Certreq.exe.
For automation, include Bash or shell script examples in addition to Azure CLI and PowerShell, and clarify that Azure CLI commands work cross-platform.
Where Windows-specific scenarios are described (e.g., outbound client certificates for Windows containers), explicitly state the Linux support status and provide Linux alternatives or workarounds if available.
Ensure that all step-by-step instructions and screenshots are not Windows-centric, or provide parallel Linux guidance where applicable.
Review FAQ and scenario sections to ensure Linux and cross-platform use cases are addressed equally.

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/Windows-centric command examples (e.g., Set-AzContext, Register-AzProviderFeature), referencing the PowerShell Gallery for migration scripts, and not including equivalent Azure CLI (cross-platform) or Bash examples. The 'Next steps' section also prioritizes PowerShell tutorials, and there is no mention of Linux-specific tools or workflows.

Recommendations:

Provide Azure CLI (az) command examples alongside or before PowerShell commands, especially for registration and preview management steps.
Reference Bash or cross-platform shell usage where appropriate, and clarify that Azure CLI is available on Windows, Linux, and macOS.
If migration scripts are available only in PowerShell, mention any alternatives for Linux users or provide guidance on running PowerShell Core on Linux.
Balance tutorial links to include both PowerShell and Azure CLI/Bash walkthroughs.
Review and update language to avoid implying that PowerShell is the default or only supported automation tool.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows bias by emphasizing Windows-specific tools and patterns such as IIS diagnostics, PowerShell, and SysInternals Procdump, while omitting or downplaying equivalent Linux troubleshooting methods. Examples and links are often Windows-centric, and there is little to no mention of Linux-specific diagnostics, commands, or workflows for App Service on Linux.

Recommendations:

Provide parallel Linux examples and instructions for all diagnostic and troubleshooting steps, including log collection, process dumps, and debugging.
Mention Linux equivalents for tools like Procdump (e.g., gcore, gdb) and explain how to use them in App Service on Linux.
When referencing PowerShell or DOS commands in Kudu, also describe how to use the Bash shell and relevant Linux commands if the app is running on Linux.
Clarify when a feature or tool is Windows-only, and offer alternative guidance for Linux-based App Service environments.
Include links to Linux-specific documentation for Application Insights Profiler, diagnostic logging, and troubleshooting.
Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or clearly indicate which instructions apply to which OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a bias toward Windows by referencing Visual Studio and its NuGet package manager as the primary method for installing packages, with CLI instructions only mentioned secondarily. There are no explicit Linux or cross-platform development environment examples (e.g., VS Code, JetBrains Rider, or command-line editors), and no Linux-specific deployment or configuration steps are provided. The workflow assumes a GUI-based, Windows-centric development pattern, with no mention of Linux shell commands or tools.

Recommendations:

Provide explicit Linux and cross-platform instructions for package installation (e.g., using dotnet CLI and NuGet CLI) before or alongside Visual Studio instructions.
Include examples and screenshots for Linux-based development environments, such as VS Code or JetBrains Rider, and mention command-line editors (vim, nano) for file editing.
Add Linux-specific deployment steps, such as using Azure CLI from a Bash shell, and clarify that all steps can be performed on Linux as well as Windows.
Avoid assuming the use of Visual Studio or right-click context menus; describe file creation and editing in a way that is editor-agnostic.
Explicitly state that the instructions are cross-platform and highlight any differences or prerequisites for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but the PowerShell examples are given equal prominence to CLI, and there is no explicit mention of Linux-specific tools or shell environments. In the section on outbound IPv6 support, it is explicitly stated that outbound IPv6 is only available for Windows apps, with Linux apps limited to IPv4. There are no Linux-specific command-line or scripting examples (e.g., Bash scripting, curl for querying metadata), and PowerShell is referenced without clarification that it is cross-platform or how to use it on Linux.

Recommendations:

Clarify that Azure PowerShell can be used on Linux and macOS, or provide Bash/shell script equivalents for PowerShell commands.
Provide Linux-native examples for querying app properties, such as using curl with the Azure Instance Metadata Service or jq for JSON parsing.
Explicitly mention when a feature is Windows-only (as is done for outbound IPv6), and provide guidance or workarounds for Linux users where possible.
When listing command-line options, present Azure CLI (which is cross-platform) before PowerShell, and clarify the environment for each example.
Add a note or section on how to use these commands in common Linux environments, including any prerequisites or differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing detailed information and calculations specifically for Windows Containers, mentioning Windows Server Active Directory domain join, and referencing Windows-specific features (e.g., NetBIOS). Linux is only mentioned in passing, with a single note about Linux continuous deployment network dependencies, and there are no Linux-specific configuration or example sections. There are no PowerShell or CLI examples for either platform, but the focus on Windows-specific limitations and features, as well as the order of presentation, indicates a Windows-first approach.

Recommendations:

Add a parallel section for Linux Containers, including subnet/IP requirements, limitations, and sample calculations similar to the Windows Containers section.
Provide Linux-specific examples or notes where behaviors differ (e.g., file system mounting, authentication, or networking).
Ensure that any Windows-specific limitations or features are clearly marked as such, and that Linux equivalents (or the lack thereof) are explicitly documented.
Include CLI examples (az CLI, Bash) for common tasks, and ensure parity with any Windows or PowerShell examples if/when they are added.
Review the order of presentation to avoid always listing Windows features or limitations first; consider grouping by platform or providing a comparison table.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias by providing more detailed instructions and features for Windows App Service apps, such as web server logging, detailed error messages, and failed request tracing, which are either unavailable or not documented for Linux. Several logging types and advanced features are described only for Windows, with Linux instructions being briefer and lacking parity. Windows-specific tools and log formats (e.g., W3C, Log Parser, Web.config) are referenced without Linux equivalents or alternatives.

Recommendations:

Provide equivalent Linux examples and instructions for all logging types where possible, or clearly state feature parity gaps.
Document Linux-specific logging features, tools, and log access patterns, including any differences in log file locations, formats, or retention policies.
If certain features (e.g., web server logging, failed request tracing) are not available on Linux, explicitly mention this and suggest alternative troubleshooting or logging strategies for Linux users.
Include Linux-friendly tooling recommendations for log analysis and access (e.g., using tail, grep, or Azure CLI on Linux).
Ensure that Linux and Windows instructions are presented with equal prominence and detail, possibly in parallel sections or tables.

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 configuration steps are often mentioned before or more prominently than their Linux equivalents. Examples of Azure CLI and PowerShell commands are provided, but PowerShell and Windows-specific configuration (such as netFrameworkVersion and win-x64) are frequently foregrounded. Some sections, such as ReadyToRun and deployment, provide more detailed or explicit instructions for Windows than for Linux. Linux instructions are present but sometimes less detailed or appear after Windows instructions. There are few, if any, explicit Linux shell (bash) examples, and PowerShell is referenced as a primary automation tool.

Recommendations:

Ensure that for every Windows-specific example or tool (e.g., PowerShell, win-x64), an equivalent Linux example (e.g., bash, linux-x64) is provided with equal prominence and detail.
When listing deployment or configuration options, alternate the order or present both Windows and Linux options side-by-side, rather than defaulting to Windows first.
Add explicit bash shell examples for common CLI operations, not just Azure CLI syntax blocks, to clarify usage on Linux/macOS.
Where PowerShell is mentioned as an automation tool, also mention bash or other cross-platform scripting options.
In tables and instructions, avoid assuming Visual Studio (Windows) as the default IDE; give equal weight to VS Code and CLI workflows.
Review all sections for subtle language that prioritizes Windows (e.g., 'On Windows, ...'), and balance with Linux/macOS notes.
Where configuration settings differ (e.g., netFrameworkVersion vs. linuxFxVersion), provide clear, parallel explanations and examples for both platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by presenting Azure PowerShell instructions and references before Azure CLI in all relevant sections. PowerShell is a Windows-centric tool, and its precedence in the documentation implies a preference for Windows environments. Additionally, there are no explicit Linux shell (bash) examples, and the CLI output examples use PowerShell cmdlets for status checks, even in the CLI section. The use of PowerShell and the ordering of examples may disadvantage Linux users or those who prefer cross-platform tooling.

Recommendations:

Alternate the order of PowerShell and CLI instructions, or present CLI (which is cross-platform) first to improve parity.
In CLI sections, use only CLI commands for all steps, including status checks (e.g., 'az feature show' instead of 'Get-AzProviderFeature').
Add explicit bash shell examples where relevant, especially for scripting or automation scenarios.
Clarify in each section that both PowerShell and CLI are supported on Windows, Linux, and macOS, and provide links to installation guides for both.
Avoid using PowerShell-specific output or terminology in CLI sections to prevent confusion for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates some Windows bias, particularly in the Java section, where command examples are provided for Bash, PowerShell, and Cmd, with PowerShell and Cmd (Windows shells) given equal or greater prominence than Bash (Linux/macOS). The use of terms like 'command prompt' and explicit mention of Windows-specific shells and tools (PowerShell, Cmd) without equivalent emphasis on Linux shells or tools further reinforces this bias. However, most other sections use cross-platform tools (Azure CLI, func) and generic 'terminal or command prompt' language, and the inclusion of Bash examples does provide some Linux support.

Recommendations:

For all code examples, consistently provide Bash (Linux/macOS) as the first/default example, followed by PowerShell and Cmd as alternatives.
When referencing the terminal, use 'terminal' or 'shell' instead of 'command prompt' to be more platform-neutral.
Where PowerShell or Cmd examples are given, ensure that equivalent Bash examples are always present and shown first.
Explicitly mention Linux/macOS compatibility and provide troubleshooting notes for those platforms where relevant.
If referencing Windows-specific environment variables or paths (e.g., JAVA_HOME), also show Linux/macOS equivalents.
Consider adding a short section or note about cross-platform compatibility and any OS-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation generally maintains good cross-platform parity, providing both Bash and Windows CMD examples for command-line operations. However, there is a subtle Windows bias: Windows CMD examples are always present and often appear alongside or before Bash, and there is no mention of Linux-specific shells or tools (e.g., zsh, fish). Visual Studio Code, IntelliJ, and Eclipse are mentioned as IDEs, but Windows-centric tools or patterns (such as the use of CMD and references to 'command prompt') are consistently included. There are no PowerShell-specific examples, but the presence of Windows CMD tabs and terminology like 'command prompt' reflects a mild Windows-first approach. Linux is supported and mentioned (e.g., in Java version tables), but not prioritized.

Recommendations:

Ensure that Bash examples are always listed before CMD/Windows examples to avoid the perception of Windows-first bias.
Explicitly mention that Bash examples work on Linux and macOS, and clarify that CMD examples are for Windows users.
Include references to Linux-specific shells (e.g., zsh) or terminal environments where relevant.
Where 'command prompt' is mentioned, add 'terminal' or 'shell' to be inclusive of Linux/macOS users.
Consider providing a short section or note on any Linux/macOS-specific considerations, even if minimal, to reinforce parity.
If possible, add troubleshooting or environment setup notes for Linux/macOS users (e.g., JAVA_HOME setup, Maven installation).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in its command-line examples and tool references. Feature registration steps are shown primarily using Azure PowerShell cmdlets, with Azure CLI (cross-platform) only mentioned secondarily and without explicit CLI command examples. There are no Linux shell or Bash examples, and the UI workflow descriptions and screenshots focus on graphical interfaces, which are more common in Windows environments. No Linux-specific guidance or parity is provided.

Recommendations:

Provide explicit Azure CLI command examples (e.g., 'az feature register', 'az feature show') alongside or before PowerShell examples, with full syntax and sample output.
Include Bash/Linux shell command equivalents where relevant, especially for automation or scripting scenarios.
Clarify that all command-line steps can be performed on Linux, macOS, and Windows, and specify any OS-specific prerequisites if needed.
Balance UI workflow descriptions with CLI alternatives, especially for users who may not have access to the Azure Portal or prefer automation.
Add a section or callout for Linux/macOS users, highlighting any differences or confirming full parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. In the 'Ways to create snapshots' section, PowerShell is mentioned explicitly alongside Azure CLI, REST API, and Azure portal, but there is no mention of Linux-specific tools or shell scripting. The order of tool presentation (Azure portal, REST API, Azure CLI, PowerShell) places PowerShell before any mention of Linux scripting or command-line usage. There are no Linux/Unix shell examples or references to Linux-native tools, and scripting is only referenced generically. No explicit Linux or Unix command-line examples are provided, nor is there mention of Bash or shell scripting, which are common for Linux users.

Recommendations:

Include explicit Linux/Bash shell examples for snapshot management, such as using Azure CLI commands in Bash.
Mention Linux scripting (e.g., Bash scripts) alongside PowerShell when discussing automation.
Clarify that Azure CLI is cross-platform and provide example commands in both Windows (PowerShell) and Linux (Bash) syntax.
When listing tools, alternate the order or explicitly state parity between PowerShell and Bash/shell scripting.
Add references or links to Linux-specific guidance or best practices for managing Azure NetApp Files snapshots.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by providing detailed, step-by-step instructions and GUI walkthroughs for setting SACLs on SMB shares using Windows tools, while the Linux/NFS equivalent is referenced only via a link without in-page steps. PowerShell is used as the primary example for feature registration, with Azure CLI mentioned only secondarily. There are no Linux command-line examples or screenshots, and Windows administration tools are assumed as the default for certain tasks.

Recommendations:

Provide step-by-step command-line instructions for setting Audit ACEs on NFSv4.1 shares from a Linux host, including example commands (e.g., using setfacl or nfs4_setfacl).
Include Linux/Unix screenshots or terminal output where appropriate, mirroring the Windows GUI walkthroughs.
Present Azure CLI commands before or alongside PowerShell examples for feature registration and management, ensuring parity.
Explicitly mention and demonstrate Linux tools and workflows for all relevant tasks, not just refer to external links.
Balance the prominence of Windows and Linux instructions, ensuring both are equally detailed and accessible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is heavily Windows-centric. All restore options and examples are described in the context of Windows environments, referencing Windows-specific tools (robocopy, Windows Server Backup utility) and PowerShell for automation. There are no mentions of Linux support, tools, or examples, and the documentation implicitly assumes the user is operating on Windows.

Recommendations:

Clarify early in the documentation whether the MARS agent is Windows-only or if Linux is supported. If Linux is not supported, state this explicitly.
If Linux support is available or planned, provide equivalent Linux examples for restore operations, including command-line instructions and references to Linux-native tools.
Avoid referencing Windows tools (e.g., robocopy, Windows Server Backup) exclusively; if alternatives exist for other platforms, mention them.
When describing automation, include both PowerShell and bash (or other Linux shell) examples if cross-platform support exists.
Structure documentation sections so that platform-specific instructions are clearly separated, and avoid always presenting Windows first if multiple platforms are supported.

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 domain controllers. All examples and instructions use Windows tools (PowerShell, ntdsutil.exe), and there are no references to Linux-based Active Directory alternatives or cross-platform scenarios. The documentation assumes the use of Windows Server and does not provide parity for Linux administrators or mention Samba or other open-source AD-compatible solutions.

Recommendations:

Include a section or note clarifying that the instructions are specific to Windows Server Active Directory, and mention whether Linux-based AD-compatible solutions (e.g., Samba) are supported by Azure Backup.
If Azure Backup or related tools support Linux-based domain controllers (e.g., Samba AD DC), provide equivalent backup and restore instructions for those environments.
Where PowerShell scripts are provided, offer equivalent command-line examples for Linux (if applicable), or explicitly state if no equivalent exists.
Reference Linux tools or methods (such as using rsync, tar, or native Samba backup tools) where appropriate, or clarify their (lack of) support.
Ensure that any mention of tools like ntdsutil.exe or DSRM is accompanied by a note about their Windows-specific nature and alternatives (if any) for Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation consistently presents PowerShell (typically used on Windows) examples before Azure CLI (cross-platform) examples. File paths in PowerShell examples use Windows-style paths (e.g., c:\Templates\azuredeploy.json), and there is no explicit mention or example of uploading templates from a Linux or macOS environment (e.g., using Unix-style paths). The Azure CLI section references Bash in Cloud Shell but does not provide parity for local Linux/macOS environments or address differences in shell syntax. There are no Linux-specific troubleshooting notes or examples.

Recommendations:

Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (cross-platform) first.
In upload examples, provide both Windows (c:\...) and Linux/macOS (~/Templates/...) file path examples.
Explicitly mention that Azure CLI commands work on Linux/macOS and provide any necessary syntax adjustments (e.g., for date/time formatting).
Add notes or tabs for Linux/macOS users where shell syntax or environment variables may differ.
In 'Next steps', include links to documentation for deploying templates using Azure CLI on Linux/macOS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell as the tool for restoring encrypted VMs, and by providing links and examples that are exclusively for Windows VM encryption scenarios. There are no Linux-specific restore examples, nor are Linux tools or workflows mentioned. The documentation also references Windows-specific features (e.g., Microsoft Entra ID integration for Windows disk encryption) without Linux equivalents or guidance.

Recommendations:

Add explicit examples and guidance for restoring Linux VMs, especially for encrypted Linux VMs, including relevant tools (e.g., Azure CLI, Bash scripts) and links to Linux documentation.
Where PowerShell is mentioned for VM creation/restoration, also provide equivalent Azure CLI or Bash commands for Linux users.
Include links to documentation about Linux disk encryption and restore processes, ensuring parity with the Windows-focused links.
In scenario tables and explanations, clarify when steps or tools are Windows-specific, and provide Linux alternatives where applicable.
Review all restore scenarios to ensure both Windows and Linux workflows are described with equal prominence and detail.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page lists PowerShell as a supported client before CLI, and does not provide any explicit Linux-specific examples or mention Linux tools. The examples and workload focus are centered on Azure Virtual Machines, SQL Server, and SAP HANA in Azure VMs, which are often associated with Windows environments. There are no Linux command-line examples or references to Linux-native tools, and the documentation does not clarify parity or differences for Linux users.

Recommendations:

Provide explicit Linux CLI examples alongside or before PowerShell examples, especially in sections referencing client tools.
Clarify whether all features and workflows are supported equally on Linux and Windows, and note any differences.
Include references to Linux-native tools or scripts where applicable, and ensure that CLI instructions are cross-platform.
Add a section or FAQ addressing common Linux user scenarios or concerns, such as using Azure CLI on Linux to manage Archive tier operations.
Ensure that documentation screenshots and walkthroughs are not exclusively from Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The glossary demonstrates a Windows bias by referencing Windows-specific technologies (e.g., VSS, DPM, MABS, System State backup, Bare metal backup) and tools (Azure PowerShell, Windows-specific documentation links) more frequently and in greater detail than Linux equivalents. In the few places where Linux is mentioned (e.g., application-consistent backup), it is treated as an afterthought or parenthetical. There are no explicit Linux-focused examples, tools, or documentation links, and Windows patterns and terminology are introduced first or exclusively.

Recommendations:

Add Linux-specific backup concepts and terms (e.g., LVM snapshots, fsfreeze, pre/post backup scripts) to the glossary.
Where Windows-specific tools or technologies are mentioned (e.g., VSS, DPM, MABS, System State backup), provide Linux equivalents or note their absence.
Include references and links to Linux backup documentation and tools (e.g., Azure CLI usage on Linux, Linux agent documentation).
When describing cross-platform features (like application-consistent backup), give equal detail and examples for both Windows and Linux.
Avoid always listing Windows tools or patterns first; alternate or group by platform where appropriate.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing a dedicated link and mention for Azure PowerShell usage (a Windows-centric tool) both in the introduction and in the 'Next steps' section, while not offering equivalent guidance or links for Linux-native tools such as Azure CLI. There are no command-line examples for Linux users, and the only shell command shown is 'kubectl', which is cross-platform but not Azure-specific. The documentation does not mention or link to Azure CLI instructions for backup/restore, nor does it provide Bash or Linux terminal examples, leading to a lack of parity for Linux users.

Recommendations:

Add equivalent Azure CLI instructions and links alongside all PowerShell references, both in the introduction and 'Next steps'.
Provide example commands for both PowerShell and Bash/Azure CLI where relevant, especially for backup and restore operations.
Ensure that any references to Azure PowerShell are paired with Azure CLI alternatives, and do not present PowerShell as the default or only automation option.
Consider adding a section or callout for Linux/macOS users, clarifying that all operations can be performed using Azure CLI and providing direct links to those instructions.
Review screenshots and UI instructions to ensure they are not Windows-specific, and clarify where steps are platform-agnostic.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows tools and concepts (such as Volume Shadow Copy Service, Data Deduplication, and the MABS console UI), and by omitting any Linux-specific instructions or examples. There are no mentions of Linux client support, Linux command-line procedures, or Linux-specific backup/recovery considerations, despite the stated intent to support both server and client machines.

Recommendations:

Include explicit information about Linux support: clarify whether MABS supports Linux clients/servers, and if so, provide setup and usage instructions.
Add Linux-specific examples for installing the protection agent, configuring protection groups, and performing backup and recovery operations (e.g., using command-line tools or scripts).
Mention Linux equivalents for Windows features (such as VSS and Data Deduplication), or clearly state if such features are unavailable or handled differently on Linux.
Ensure that UI instructions are supplemented with CLI or cross-platform alternatives where possible.
If Linux is not supported, clearly state this limitation at the beginning of the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

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 workflows assume the use of Windows Server, Windows-based SQL Server, and DPM. There are no examples or guidance for Linux-based SQL Server deployments, nor are alternative tools or methods for Linux environments mentioned. The only automation reference is to PowerShell, a Windows-centric scripting environment.

Recommendations:

Add explicit mention of Linux support or limitations for SQL Server backup to Azure, clarifying whether DPM or equivalent solutions exist for Linux.
Provide parallel instructions or references for backing up SQL Server on Linux (e.g., using Azure Backup Server, Azure CLI, or native SQL tools).
Include examples and screenshots for Linux-based SQL Server environments, if supported.
Reference cross-platform automation options (such as Azure CLI, REST API, or Bash scripts) alongside or instead of PowerShell.
Clearly state in the prerequisites and introduction that the documented workflow is specific to Windows/DPM, and link to Linux-specific documentation if available.

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 command-line examples using PowerShell and Windows-specific tools (e.g., .exe installers, PowerShell cmdlets). The workflow assumes the use of Hyper-V and Windows Server features, with only minimal mention of Linux support (limited to a single line about file-consistent snapshots). There are no Linux-specific instructions, examples, or parity in tooling or recovery workflows.

Recommendations:

Provide equivalent Linux command-line examples (e.g., using Bash or relevant Linux tools) where applicable, especially for agent installation and firewall configuration.
Include explicit instructions for backing up and recovering Linux VMs, including any differences in workflow or limitations.
Clarify the support level for Linux VMs (e.g., agent installation, recovery options, snapshot consistency) in dedicated sections.
Mention Linux scenarios alongside Windows/Hyper-V scenarios, not as an afterthought or in a separate, minimized section.
If certain features are unavailable for Linux, clearly state this and provide recommended alternatives or workarounds.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a strong Windows bias. It focuses heavily on Windows-specific backup agents (MARS, DPM, MABS), with direct backup support only for Windows machines. Linux is mentioned only to note lack of support in some scenarios, and there are no Linux-specific examples, tools, or workflows described. Windows tools and patterns (VSS, MARS agent, DPM/MABS) are discussed in detail, while Linux backup options are not addressed. The structure and order of information consistently present Windows solutions first and in more depth.

Recommendations:

Add explicit Linux backup scenarios, including supported agents, workflows, and limitations.
Provide Linux-specific examples and references (e.g., using Azure Backup for Linux VMs, integration with native Linux backup tools, or third-party solutions).
Clarify parity or gaps between Windows and Linux support in tables and feature lists.
Include Linux-focused architecture diagrams and process flows where applicable.
If direct backup for Linux is not supported, offer guidance or alternatives for Linux users (e.g., using Azure VM backup extension, scripts, or partner tools).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exclusively references Microsoft Azure Backup Server and Data Protection Manager (DPM), both of which are Windows-based solutions. All troubleshooting steps and error messages assume the use of Windows Server or Windows Client, with no mention of Linux environments, tools, or equivalent recovery processes. There are no examples, recommendations, or troubleshooting guidance for Linux-based backup or recovery scenarios.

Recommendations:

Explicitly state that Azure Backup Server and DPM are Windows-only products, if that is the case, to clarify scope.
If Linux backup and recovery is supported via Azure Backup, add equivalent troubleshooting sections and error messages for Linux-based agents or servers.
Provide links or references to Linux-specific documentation for Azure Backup, if available.
Include examples or notes for Linux administrators, or clarify alternative solutions for Linux environments.
Ensure parity in documentation structure and troubleshooting guidance for both Windows and Linux users where applicable.

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: Windows-specific examples and references (such as PowerShell and Windows tutorials) are provided without equivalent Linux examples; Windows tools and patterns (e.g., bcdedit, netdom, RDP, Windows-specific restore scenarios) are mentioned exclusively or before Linux alternatives; and guidance for Linux VMs is minimal, often limited to brief notes or links, with no step-by-step Linux-specific instructions or CLI examples.

Recommendations:

Provide Linux-specific restore scenarios and examples, including step-by-step instructions for common Linux distributions (e.g., Ubuntu, CentOS, RHEL).
Include equivalent Linux command-line examples (e.g., Azure CLI, Bash scripts) alongside or before PowerShell/Windows commands.
Reference Linux documentation and tools (e.g., SSH, cloud-init, Linux agent troubleshooting) in parity with Windows tools like RDP, bcdedit, and netdom.
Ensure that links to further reading or tutorials are balanced between Windows and Linux (e.g., include /azure/virtual-machines/linux/ links where appropriate).
Add troubleshooting steps and post-restore guidance specific to Linux VMs, such as handling SSH keys, resetting passwords with the VMAccess extension, and dealing with Linux-specific boot or agent issues.
Review all scenario tables and ensure Linux is explicitly addressed, not just as a note or afterthought.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing System Center Data Protection Manager (DPM), a Windows-only tool, as the primary on-premises backup solution. There are no mentions of Linux backup agents, Linux-compatible tools, or examples relevant to Linux environments. The 'Try Azure Backup' link specifically points to a Windows/MARS agent guide, further emphasizing the Windows-centric approach. No Linux-specific instructions, screenshots, or parity guidance are present.

Recommendations:

Include references to Linux backup solutions supported by Azure Backup, such as Azure Backup Server or native Linux agents.
Provide example workflows, screenshots, or command-line instructions for configuring Azure Backup on Linux systems.
Add links to documentation for Linux backup scenarios alongside or before Windows-specific links.
Clarify in the introduction that Azure Backup supports both Windows and Linux workloads, and outline any differences in setup or capabilities.
Ensure parity in examples and terminology, avoiding exclusive focus on Windows tools like DPM.

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 all steps, screenshots, and file paths are specific to Windows environments. There are no examples or mentions of Linux-based Exchange servers, Linux tools, or cross-platform alternatives. Windows conventions (e.g., C:\ paths, DPM Console UI) are used throughout, and no Linux parity or guidance is provided.

Recommendations:

Explicitly state that DPM is a Windows-only solution and clarify platform limitations at the start of the article.
If possible, provide links or references to Linux-compatible backup solutions for Exchange (if supported), or clarify that Exchange Server is only supported on Windows.
Include a section or note for users seeking to back up Exchange workloads on Linux (if such scenarios exist), or direct them to relevant documentation for Linux-based backup tools.
Ensure that related content and automation examples (such as PowerShell scripts) are accompanied by notes about platform compatibility, and suggest alternatives for non-Windows environments where feasible.

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 scripts, Windows Registry edits, and Windows-specific tools (e.g., Certificate Import Wizard, .reg files). There are no Linux or cross-platform instructions, and all administrative steps assume the Azure Backup Server is running on Windows. Linux equivalents for certificate management, scripting, or configuration are not mentioned or provided.

Recommendations:

Provide equivalent Linux-based instructions for certificate import (e.g., using openssl and update-ca-certificates).
Offer shell script (bash) alternatives for PowerShell scripts, or clarify that MABS is Windows-only if that is the case.
Document how to perform configuration steps (such as editing registry or service management) on Linux, or state platform limitations explicitly.
If MABS is not supported on Linux, add a clear note at the top of the documentation stating that all instructions are for Windows environments only.
Include Linux/Unix command-line examples where possible, especially for VMware environments that may be managed from non-Windows systems.

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 backup solution, and does not mention or provide examples for Linux environments or tools. All instructions, tools, and workflows assume a Windows/SharePoint/DPM ecosystem, and the only automation reference is to PowerShell. There are no Linux equivalents, alternative tools, or cross-platform considerations discussed.

Recommendations:

Include information on whether Linux-based SharePoint alternatives (e.g., SharePoint Online, or open-source equivalents) can be backed up to Azure, and how.
If DPM is Windows-only, clearly state this limitation and suggest Azure-native or cross-platform backup solutions for Linux environments.
Provide examples or references for backing up non-Windows workloads (e.g., Linux web servers or databases) to Azure, possibly in a 'See also' section.
If automation is discussed via PowerShell, mention or provide equivalent CLI/bash/REST API examples for Linux users where possible.
Clarify in the prerequisites and introduction that the documented workflow is specific to Windows environments, and link to Linux backup documentation 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 is emphasized as the primary scripting method, and the only detailed example for granting database privileges is a PowerShell script. Instructions for setting environment variables and running scripts are given exclusively for Windows (via Control Panel and System Properties), with no equivalent Linux/macOS guidance. While the PSQL tool is mentioned, its setup and usage are only described in a Windows context. There are no CLI/bash or Linux-native examples for these steps.

Recommendations:

Provide equivalent Linux/macOS instructions for setting environment variables (e.g., using export in bash or editing ~/.bashrc).
Include bash or shell script examples for granting database privileges, alongside or instead of PowerShell scripts.
When referencing tools like PSQL, show installation and usage steps for both Windows and Linux/macOS.
Avoid assuming the user is on Windows in step-by-step guides; offer cross-platform alternatives where possible.
When mentioning scripting options (PowerShell, CLI), present them in a neutral order or group, not with Windows-first prominence.

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 before Linux equivalents, and by omitting explicit Linux/Unix command-line examples. The only explicit tooling reference for assigning permissions points to a PowerShell-based guide, and the 'Next steps' section lists PowerShell before CLI, which is more cross-platform. There are no Linux-specific instructions or examples, and the documentation does not mention Bash, shell scripting, or Linux-native tools for interacting with the REST API.

Recommendations:

Provide explicit examples using Azure CLI (az), which is cross-platform, for all operations currently referenced via PowerShell or the Azure portal.
When referencing external guides (e.g., for assigning permissions), link to both PowerShell and CLI/Linux instructions, or to a neutral, cross-platform page.
In the 'Next steps' section, list Azure CLI before or alongside PowerShell to avoid the impression of Windows-first guidance.
Include example REST API invocations using curl or httpie, which are available on Linux, macOS, and Windows, to demonstrate true cross-platform usage.
Where scripting is discussed, mention both PowerShell and Bash/shell scripting as options for automation.
Audit all referenced links and ensure parity between Windows and Linux instructions throughout the documentation.

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, while lacking equivalent Linux shell or cross-platform scripting examples. Windows-specific update instructions are mentioned before Linux, and there is no mention of Linux-native tools or shell commands for resource management beyond the Azure CLI. The CLI section is brief and lacks parity with the PowerShell section, and there are no Bash or Linux-specific automation examples.

Recommendations:

Provide equivalent Bash or shell script examples for moving Recovery Services vaults using Azure CLI, demonstrating how Linux users can automate these tasks.
Ensure that instructions for updating certificates and CRLs on Linux are as detailed as those for Windows, possibly including example commands (e.g., using apt, yum, or update-ca-certificates).
Present cross-platform (CLI) instructions before or alongside PowerShell examples, emphasizing that both Windows and Linux users are supported.
Mention and link to Linux-native tools or scripting environments (e.g., Bash, zsh) where appropriate, and avoid assuming PowerShell as the default automation environment.
Where scripts are provided, offer both PowerShell and Bash/CLI versions to ensure Linux users have clear, actionable guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. PowerShell is the primary automation method described, with detailed steps and scripts, while Linux-native alternatives are not mentioned. Windows-specific tools (MARS, MABS, DPM, ARMClient via Chocolatey) are referenced without Linux equivalents or cross-platform guidance. The CLI section is minimal and notes its limitations, and there are no Bash or cross-platform scripting examples. The documentation assumes the use of Windows consoles and management tools throughout.

Recommendations:

Provide equivalent Bash or Azure CLI scripts for all PowerShell examples, especially for vault and backup item deletion.
Highlight cross-platform tools and workflows (e.g., Azure CLI, REST API) before or alongside Windows/PowerShell methods.
Document how to install and use ARMClient on Linux/macOS, including package manager alternatives to Chocolatey.
Clarify which management consoles (MARS, MABS, DPM) are Windows-only and suggest Linux-compatible alternatives or note limitations.
Add explicit Linux/macOS instructions for script execution, environment setup, and prerequisites.
Ensure screenshots and UI steps are not exclusively Windows-centric (e.g., avoid only showing Windows-style context menus or dialogs).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias. While it mentions support for both Linux and Windows IaaS VMs, it repeatedly foregrounds Windows-centric tools and scenarios (such as System Center DPM, Windows Server, and Azure Backup Server) without equivalent Linux examples or tools. The 'Next steps' section provides a backup guide specifically for Windows Server but omits any Linux-specific backup instructions. There are no Linux command-line or tool examples, and Windows tools are referenced by name without Linux alternatives.

Recommendations:

Include explicit Linux backup scenarios and examples, such as backing up a Linux VM or using Linux command-line tools.
Balance references to Windows tools (e.g., System Center DPM, Windows Server) with Linux-native backup solutions or mention their parity.
In the 'Next steps' section, add links to documentation for backing up Linux VMs and managing Linux workloads.
Where possible, provide cross-platform examples or clarify when a feature or tool is Windows-only.
Ensure that screenshots, walkthroughs, and sample commands are not exclusively Windows-focused.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation generally presents Windows steps, tools, and troubleshooting guidance before Linux equivalents, and often in greater detail. Windows-specific tools and patterns (e.g., registry edits, Windows Explorer, .NET requirements) are described with more prominence and screenshots. PowerShell is referenced as a primary automation method, while Linux CLI is mentioned secondarily. Although Linux steps are present, they are sometimes less detailed or appear after Windows instructions.

Recommendations:

Present Windows and Linux instructions in parallel or side-by-side, rather than always listing Windows first.
Ensure that Linux troubleshooting steps are as detailed as Windows ones, including screenshots and explicit command examples.
When referencing automation (e.g., PowerShell), also provide equivalent Bash or shell script examples for Linux.
Highlight Linux-specific tools and workflows (e.g., file managers, system utilities) with the same prominence as Windows tools.
Where possible, use neutral language and structure (e.g., 'For Windows' and 'For Linux' headings together) to avoid implying Windows is the default or primary platform.
Expand the 'Next steps' section to include Linux-focused automation and management guides, not just PowerShell and Azure CLI.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows environments, referencing only Windows-specific tools (e.g., 'net stop dpmra'), Windows authentication patterns (NT AUTHORITY\SYSTEM), and making no mention of Linux equivalents or cross-platform considerations. All troubleshooting steps and terminology assume a Windows server context, with no guidance for Linux users or environments.

Recommendations:

Include troubleshooting steps and examples for Linux environments, if Data Protection Manager or Azure Backup Server supports Linux workloads.
Provide equivalent Linux commands (e.g., systemctl or service commands) alongside Windows commands like 'net stop/start'.
Mention Linux authentication/user patterns if applicable, not just Windows-specific accounts like 'NT AUTHORITY\SYSTEM'.
Clarify in the introduction or prerequisites if the product is Windows-only; if not, ensure Linux parity throughout the documentation.
Add notes or sections for Linux-specific errors, logs, and recovery steps where relevant.

Create pull request

Bias Types:

⚠️ windows_only

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is exclusively focused on restoring System State for Windows Server using Azure Backup. All instructions, tools, screenshots, and command-line examples are specific to Windows environments (e.g., Windows Server Backup, wbadmin, MARS agent, Windows Recovery Environment). There are no references to Linux systems, tools, or equivalent recovery processes, and no cross-platform considerations are mentioned.

Recommendations:

Clearly state in the introduction that the procedure is Windows-specific, and provide links to equivalent Linux backup/restore documentation if available.
If Azure Backup supports Linux system state or similar functionality, add a dedicated section or a separate article for Linux, including step-by-step instructions, tools (e.g., rsync, tar, Azure CLI), and recovery workflows.
Where possible, mention cross-platform Azure Backup capabilities and clarify any feature gaps between Windows and Linux.
If Linux is not supported for system state backup/restore, explicitly state this limitation to set user expectations.
Ensure parity in documentation structure and detail for both Windows and Linux scenarios if/when Linux support is available.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias. All examples, tools, and workflows focus exclusively on Microsoft-centric backup solutions (MABS, DPM, MARS), which are only available for Windows environments. There are no references to Linux backup agents, Linux-based workloads, or cross-platform scenarios. Command-line examples and troubleshooting steps reference only Windows tools (e.g., PowerShell cmdlets like Remove-DPMChildDatasource, Remove-OBPolicy). The documentation does not mention or provide parity for Linux backup scenarios, nor does it clarify the lack of support for non-Windows platforms.

Recommendations:

Explicitly state the Windows-only scope of the documented features and tools at the beginning of the article.
Add a section or note addressing the current limitations for Linux and non-Windows workloads, including any roadmap or alternatives for Linux backup security features.
If Azure Backup supports Linux workloads in any capacity, provide equivalent examples, workflows, and troubleshooting steps for Linux environments (e.g., using Azure CLI, shell scripts, or Linux-native agents).
Avoid referencing only Windows tools and PowerShell cmdlets; where possible, include cross-platform command-line examples (e.g., Azure CLI) or clarify when a feature is Windows-specific.
Ensure that future documentation updates track and highlight feature parity (or gaps) between Windows and Linux backup solutions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is exclusively focused on Windows Server, with all instructions, screenshots, and tools (such as the MARS agent) tailored for Windows environments. There are no references to Linux systems, Linux backup tools, or cross-platform parity. The workflow, agent downloads, and backup/restore steps are all Windows-specific, and Linux is not mentioned as a supported scenario or given any equivalent guidance.

Recommendations:

If Azure Backup supports Linux system state or similar backups, add a parallel section or separate article for Linux, including equivalent steps, tools, and screenshots.
Explicitly state in the introduction and prerequisites that the guide is Windows-only, and provide a link to Linux backup documentation if available.
Where possible, mention cross-platform alternatives or clarify the scope (e.g., 'This guide is for Windows Server. For Linux, see...').
If Linux is not supported for system state backup with Azure Backup, clearly state this limitation to avoid confusion.
Ensure future documentation on backup covers both Windows and Linux scenarios, or provides clear parity in examples and tooling.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily biased toward Windows environments. All troubleshooting steps, examples, and tool references are specific to Windows (e.g., MMC console, Internet Explorer, Task Scheduler, Registry Editor, vssadmin, PowerShell). There are no Linux equivalents or mentions, and the MARS agent is treated as a Windows-only solution. Linux users or those seeking cross-platform guidance will find no relevant instructions or parity.

Recommendations:

Clearly state at the beginning whether the MARS agent is Windows-only, and if so, direct Linux users to the appropriate Azure Backup solutions for Linux.
If Linux support is available or planned, provide equivalent troubleshooting steps, examples, and tool references for Linux environments (e.g., using systemctl, journalctl, Linux file paths, and relevant package managers).
Where PowerShell or Windows-specific tools are referenced, add corresponding Linux shell commands or procedures if applicable.
Avoid assuming the use of Internet Explorer or Windows GUI tools; provide browser-agnostic and CLI-based alternatives.
Add a section or links for Linux backup agent troubleshooting, or clarify that Linux users should use a different agent (such as Azure VM backup or Azure Backup for Linux).

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 (Task Manager, Control Panel), Windows service/process names, and Windows file paths. There are no examples or instructions for Linux-based Azure Backup agents, nor are Linux equivalents for troubleshooting steps provided.

Recommendations:

Add parallel troubleshooting instructions for Linux-based Azure Backup agents, including relevant process/service names and commands (e.g., using systemctl, ps, or journalctl).
Include Linux file path examples for log locations, if supported.
Present both Windows and Linux instructions side-by-side or clearly indicate when steps are Windows-specific.
Reference cross-platform tools or clarify OS applicability at the start of each troubleshooting section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows subtle Windows bias by mentioning Windows-specific tools (Volume Shadow Copy Service - VSS) before their Linux equivalents (fsfreeze), and by linking only to Windows VM Agent and snapshot extension documentation. There are no Linux-specific example links or detailed references, and Linux is only mentioned in passing (e.g., 'pre/post scripts for Linux VM backups') without further guidance or parity in documentation links.

Recommendations:

When referencing tools for backup consistency, mention Linux (fsfreeze) before or alongside Windows (VSS), not after.
Provide equivalent documentation links for Linux VM Agent and snapshot extension, not just Windows.
Include Linux-specific examples or scenarios, such as how crash-consistent backups interact with common Linux workloads or filesystems.
Clarify or expand on the use of pre/post scripts for Linux, possibly linking to relevant Linux backup documentation.
Ensure that all instructions, notes, and references are balanced between Windows and Linux environments to improve parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page focuses exclusively on assessing ASP.NET web apps, which are traditionally associated with Windows environments. There are no explicit examples, commands, or tools mentioned for Linux-based .NET web apps. All referenced materials and linked tutorials assume a Windows-centric workflow, and there is no mention of Linux assessment tools or cross-platform considerations.

Recommendations:

Include explicit guidance or examples for assessing .NET web apps running on Linux, such as those hosted on Kestrel or using .NET Core.
Mention and link to any Linux-compatible assessment tools or scripts, if available.
Clarify whether the assessment process and recommendations apply equally to both Windows and Linux-based .NET web apps.
Add a section or note addressing Linux-specific considerations, such as file system differences, service management, or dependency handling.
Ensure parity in documentation by providing at least one Linux-based example or workflow alongside any Windows-centric instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation presents Windows container information before Linux, and the Windows section lacks parity with the Linux section: there are no command-line or Azure CLI examples for Windows containers, while Linux containers receive detailed CLI and SSH instructions. This may give the impression that Windows is prioritized or that Linux is more complex, and it leaves Windows users without equivalent guidance.

Recommendations:

Provide equivalent Azure CLI or PowerShell instructions for connecting to Windows containers, or explicitly state if such functionality is not supported.
Present Linux and Windows instructions in parallel or in a more balanced manner, rather than always listing Windows first.
If certain features (like CLI SSH access) are not available for Windows containers, clearly explain the limitation and suggest any available alternatives.
Ensure that both Linux and Windows sections contain similar levels of detail, including troubleshooting tips, example outputs, and command-line usage where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing the Windows deployment path (C:\home\site\wwwroot) as the default and only later mentioning the Linux equivalent. There are no Linux-specific examples or screenshots, and the Linux path is only mentioned in a note, not in the main instructional steps. No Linux command-line or tooling examples are provided.

Recommendations:

Present both Windows and Linux file paths side-by-side in the main instructions, not just in a note.
Include explicit Linux examples (e.g., using /home/site/wwwroot in the step-by-step instructions and sample commands).
If showing file paths or deployment locations, always show both Windows and Linux equivalents together.
If referencing tools or commands, provide both Windows (PowerShell, CMD) and Linux (Bash, CLI) examples where relevant.
Consider adding a table or section that summarizes platform-specific differences for clarity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by referencing Windows first in the quickstart links (e.g., 'flask,windows,azure-cli,...') and not providing any explicit Linux-specific instructions or examples. While the content is mostly OS-agnostic, there is a lack of parity in highlighting or supporting Linux environments, especially in setup and deployment steps.

Recommendations:

Ensure that quickstart and sample links include both Windows and Linux tabs or provide a neutral default.
Explicitly mention that all steps are cross-platform, or provide Linux/macOS-specific instructions where relevant (e.g., for environment variable setup, file paths, or deployment).
Add a section or note clarifying any OS-specific differences, even if minimal, to reassure Linux users.
Where portal or CLI instructions are given, ensure parity in screenshots or command examples for both Windows and Linux terminals.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation assumes the use of GitHub Codespaces and Azure App Service, which are cross-platform, but it lacks explicit Linux or non-Windows instructions or examples. All terminal commands are given in a generic form, but there is no mention of Linux-specific workflows, nor are there any references to Linux tools or environments. The documentation implicitly assumes a Windows/.NET development environment and does not provide parity guidance for Linux users.

Recommendations:

Explicitly mention that all commands work on Linux, macOS, and Windows, and clarify any OS-specific differences.
Provide alternative instructions or notes for users developing on native Linux environments (e.g., Ubuntu) outside of Codespaces.
Include examples of running the app and deploying from a local Linux terminal, not just Codespaces.
Reference Linux package managers or tools (e.g., apt, snap) where relevant, especially for .NET SDK installation.
Add troubleshooting tips for common Linux-specific issues (e.g., file permissions, environment variables).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation is generally cross-platform and Linux-focused for hosting, but there is a subtle Windows bias in the development and publishing workflow sections. Windows tools and development on Windows are mentioned first or exclusively in some places, and recommendations for local development and build workflows are sometimes Windows-centric. However, Linux is clearly the only supported hosting environment, and most code and configuration examples are OS-agnostic.

Recommendations:

When listing development options, avoid phrases like 'Terminal or command prompt' and instead use 'Terminal (Linux/macOS) or Command Prompt (Windows)' to clarify cross-platform support.
In the publishing section, avoid recommending remote build specifically for Windows users; instead, explain the pros and cons of remote vs. local build for all platforms.
Add explicit Linux/macOS CLI examples where appropriate (e.g., using bash/zsh instead of only generic or Windows-centric command syntax).
Where Visual Studio Code is mentioned, clarify that it is cross-platform and works on Linux/macOS as well as Windows.
Review all references to 'command prompt' and 'cmd' to ensure parity with bash/zsh/terminal instructions.
If mentioning Windows-specific behaviors (such as Python standard library installation), provide the equivalent Linux/macOS context immediately after or alongside.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation exhibits a mild Windows bias, primarily by listing Windows-centric tools (Visual Studio) before cross-platform or Linux-native alternatives, especially in C# sections. Visual Studio is mentioned first for C# quickstarts and deployment, which can imply a Windows-first development workflow. However, the documentation does provide cross-platform alternatives (Visual Studio Code, Azure CLI, Maven, etc.) and does not omit Linux-compatible instructions. There are no PowerShell-heavy examples or missing Linux examples, but the ordering and tool emphasis can subtly prioritize Windows.

Recommendations:

When listing development tools or quickstart options, alternate the order or explicitly mention cross-platform tools (e.g., Visual Studio Code, Azure CLI) before or alongside Windows-only tools like Visual Studio.
Clearly indicate which tools are cross-platform and which are Windows-only, especially in tool lists and quickstart sections.
Where possible, provide explicit Linux/macOS terminal instructions or screenshots alongside Windows/Visual Studio steps.
Consider adding a table or section summarizing tool compatibility across Windows, Linux, and macOS for each language.
Ensure that all references to 'command prompt' clarify that Bash/zsh (Linux/macOS) and Command Prompt/PowerShell (Windows) are supported equally.

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 status, with the Azure CLI (cross-platform) option mentioned only secondarily and without a direct example. There are no Linux-specific examples or references to Linux tools, though the page does link to Linux performance benchmarks. No explicit Windows-only tools or patterns are otherwise present.

Recommendations:

Provide both Azure PowerShell and Azure CLI examples side-by-side, or list Azure CLI (cross-platform) first to promote parity.
Include explicit Linux command-line examples (e.g., bash/CLI) where relevant, especially for common administrative tasks.
Where referencing tools or commands, clarify their cross-platform compatibility and provide equivalent instructions for both Windows and Linux users.
Consider adding a section or callout for Linux administrators if there are any platform-specific considerations or best practices.

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, with a few instances referencing Windows-specific tooling or lacking Linux parity. Notably, remediation steps for VMware Tools vulnerabilities reference the Azure VMware Solution Run command 'Set-Tools-Repo' without clarifying if this is cross-platform or providing Linux-specific guidance. Additionally, the mention of 'VMware Tools for Windows' in one issue highlights a Windows-centric focus, while there are no explicit Linux/Powershell command examples or Linux-specific instructions provided.

Recommendations:

When referencing remediation steps involving VMware Tools, clarify whether the instructions apply to both Windows and Linux VMs. If there are differences, provide explicit Linux steps or commands.
If the 'Set-Tools-Repo' Run command is platform-agnostic, state this clearly. If not, provide equivalent instructions for Linux VMs.
For issues that mention 'VMware Tools for Windows', include a note about the status or remediation for Linux VMware Tools if applicable.
Review all workaround instructions to ensure Linux administrators are equally supported, especially where OS-specific actions may be required.
Consider adding a section or table column indicating OS-specific impact or steps for each issue where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation is generally platform-neutral in its REST API focus, but there are subtle signs of Windows bias. Specifically, in several example responses (notably in the Cross Region Restore section), the 'osType' and 'OsType' fields are set to 'Windows', and VM size examples reference Windows-centric naming. There are no explicit Linux or cross-platform examples, and no mention of Linux-specific considerations or sample payloads. No PowerShell or CLI examples are present, but the implicit assumption of Windows as the default OS in examples suggests a 'windows_first' approach.

Recommendations:

Include example responses and request bodies that show both 'osType': 'Linux' and 'osType': 'Windows' to demonstrate parity.
Explicitly mention that the APIs work for both Windows and Linux VMs, and note any differences if they exist.
Where VM configuration or disk restore is discussed, provide examples or notes for restoring Linux VMs (e.g., handling of Linux-specific boot or disk configurations).
If referencing VM sizes or storage types, include examples that are common for Linux workloads as well.
Add a section or note on any Linux-specific restore considerations (e.g., file system compatibility, agent requirements, etc.).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page exhibits a Windows bias primarily through repeated references to PowerShell objects as the default or primary way to conceptualize and configure backup policies. The term 'PowerShell object' is used multiple times to describe the policy structure, and no equivalent Linux or cross-platform command-line tooling (such as Azure CLI, Bash, or curl) is mentioned. There are no Linux-specific examples or references, and the documentation implicitly assumes familiarity with Windows/PowerShell paradigms.

Recommendations:

Replace or supplement references to 'PowerShell object' with neutral terms such as 'policy object' or 'JSON policy definition', unless specifically discussing PowerShell scripting.
Add equivalent examples using Azure CLI and/or curl for creating and managing backup policies, demonstrating how to interact with the REST API from Linux or cross-platform environments.
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, Azure CLI).
Avoid assuming PowerShell as the default scripting or automation environment; provide parity in documentation for Linux users.
Include a section or callout for Linux/macOS users, highlighting any differences or tips for using the REST API from non-Windows systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation primarily describes migration of Azure VM backups using the Azure Portal and briefly mentions CLI and PowerShell, but does not provide explicit Linux-specific examples or parity for Linux administrators. The only command-line reference is a link to the Azure CLI command, but no PowerShell or Bash/Linux shell examples are shown inline, nor is there any mention of Linux-specific considerations or tools. The structure and language implicitly assume a Windows-centric audience by referencing PowerShell and the Azure Portal UI, with no explicit Linux parity.

Recommendations:

Include explicit Linux/Bash shell examples for CLI operations, such as showing the az backup item set-policy command with sample parameters.
Provide parity between PowerShell and Bash/CLI examples, ideally in tabbed format, so both Windows and Linux administrators can follow along.
Mention any Linux-specific considerations or prerequisites for VM backup migration, if applicable.
Clarify that the Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, and provide installation links for non-Windows platforms.
If PowerShell examples are included elsewhere, ensure Bash/Linux equivalents are also present.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page references PowerShell before Azure CLI when listing ways to create a resource group, which may indicate a subtle 'windows_first' bias. However, both PowerShell and Azure CLI are mentioned, and no examples or tooling are provided that are exclusive to Windows. There are no code samples or instructions that are specific to Windows or PowerShell, and Linux parity is generally maintained.

Recommendations:

When listing cross-platform tools such as PowerShell and Azure CLI, alternate the order or explicitly state that both are fully supported on Windows, Linux, and macOS.
Consider providing explicit examples for both PowerShell and Azure CLI (or Bash) where relevant, to reinforce cross-platform parity.
If mentioning PowerShell, clarify that Azure PowerShell is available on all major platforms, not just Windows.
Ensure that any future additions of code samples or walkthroughs include both Windows and Linux command-line examples.

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 parity for Linux environments. There are no explicit references to Windows tools, PowerShell, or Windows-first patterns, but the lack of Linux-specific guidance or examples could be seen as a subtle bias, especially if readers expect cross-platform operational details.

Recommendations:

Add explicit examples or references for both Windows and Linux environments where relevant (e.g., how to configure VPN or ExpressRoute connections from Linux-based on-premises systems).
Include links or references to Azure CLI and Linux networking tools (such as strongSwan or OpenVPN) for establishing Site-to-Site VPN connections.
Clarify in the prerequisites and connection steps that the guidance applies to both Windows and Linux on-premises environments, or provide separate sections if steps differ.
If PowerShell or Windows-specific tools are not required, explicitly state that the process is OS-agnostic to reassure Linux users.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally presents a balanced approach for both Windows and Linux Azure VMs, especially in the 'Install the VM agent' section, where both platforms are given clear instructions. However, there is a subtle 'windows_first' bias: in the VM agent installation table, Windows instructions are listed before Linux, and the Windows process is described in more detail (with explicit verification steps and version numbers), while the Linux process is more general and refers to distribution repositories. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present elsewhere in the document.

Recommendations:

Present Linux and Windows instructions in parallel or alternate the order in which they are described to avoid implicit prioritization.
Provide equally detailed verification steps for Linux agent installation (e.g., how to check the agent version and service status on Linux).
Where possible, offer command-line examples for both Windows (PowerShell/Command Prompt) and Linux (bash/CLI) for common tasks, even if the Azure Portal is the main method.
Explicitly state that all steps apply equally to both Windows and Linux VMs unless otherwise noted.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not show overt Windows bias in terms of prioritizing Windows tools, PowerShell, or Windows-specific workflows. However, it lacks explicit Linux parity: there are no command-line examples (such as Bash, psql, or Azure CLI) for Linux users, and the only client tool mentioned for database access is pgAdmin (a cross-platform GUI), with no mention of CLI alternatives. There are no PowerShell or Windows-only tools mentioned, but the absence of Linux command-line guidance may disadvantage Linux-first users.

Recommendations:

Add examples for connecting to Azure Database for PostgreSQL using the psql command-line tool, including connection string formats and authentication steps.
Provide Azure CLI commands for managing permissions, backup, and restore operations, in addition to (or instead of) portal screenshots.
Mention and provide examples for Linux-native workflows, such as using Bash scripts for automation.
Clarify that pgAdmin is cross-platform, and suggest alternative tools (e.g., psql) for users who prefer command-line interfaces.
Ensure that all steps (such as firewall configuration and credential management) are documented with both GUI and CLI options.

Create pull request

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