Scan Details - Linux-first Docs for Azure

541

Pages Scanned

70

Pages Flagged

541

Changed Pages

12.9%

% Pages Flagged

Live Progress

🔴 Connecting...

0%

Phase: discovery

Processing: Initializing...

Activity Feed

00:01:05 Scan started

Scan Information

Started At: 2025-08-21 00:01:05

Finished At: In Progress

Status: in_progress

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

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell instructions before Azure CLI, referencing PowerShell-specific cmdlets (e.g., Get-AzProviderFeature) even in CLI sections, and omitting explicit Linux shell examples or guidance. The step-by-step instructions and screenshots are tailored to the Azure Portal UI, which is platform-agnostic but often more familiar to Windows users. There are no bash or Linux-specific command-line examples, nor is there mention of Linux-native tooling or scripting approaches.

Recommendations:

Provide explicit bash/Linux shell examples for Azure CLI commands, including output parsing and scripting patterns.
Ensure CLI instructions reference platform-appropriate commands for viewing feature registration status (e.g., 'az feature list' or 'az feature show'), rather than PowerShell cmdlets.
Add notes or examples for Linux users, such as using the Azure CLI in bash, zsh, or other shells, and clarify any differences in command syntax or output formatting.
Balance the order of examples by presenting CLI instructions before or alongside PowerShell, rather than consistently after.
Include references to Linux-native automation tools (e.g., Ansible, shell scripts) where relevant, especially in sections discussing deployment automation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and cmdlets for migration and preview registration, with no mention of Bash, Linux, or cross-platform CLI alternatives. The only code examples provided are PowerShell-based, and the 'Next steps' section lists a PowerShell tutorial before mentioning the Azure CLI. There is no explicit guidance or examples for Linux users or Bash scripting, and Windows-centric tools and patterns are assumed throughout.

Recommendations:

Provide equivalent Azure CLI (bash-friendly) examples alongside all PowerShell commands, especially for migration and preview registration.
Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash syntax where appropriate.
Ensure that tutorials and 'Next steps' sections list both PowerShell and CLI options equally, or alternate their order to avoid Windows-first bias.
Where scripts are referenced (such as migration scripts), clarify if cross-platform options exist or provide links to GitHub repositories with both PowerShell and Bash versions.
Add a note or section for Linux users, highlighting any differences or considerations when using Application Gateway with Linux-based management tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias: all migration tools and examples focus exclusively on migrating from Windows/IIS environments, with repeated references to PowerShell scripts and Windows-specific tools. There are no examples, tools, or guidance for migrating .NET apps from Linux environments or for Linux-based hosting scenarios. The documentation assumes the source environment is always Windows/IIS, omitting Linux/Apache/Nginx scenarios entirely.

Recommendations:

Add explicit guidance and tooling for migrating .NET apps hosted on Linux (e.g., Apache, Nginx) to Azure App Service.
Include Linux shell (bash) script examples alongside PowerShell, or reference cross-platform CLI tools where available.
Document any limitations or differences when migrating from Linux environments, and provide remediation steps.
Mention and link to Azure App Service for Linux documentation, and clarify support for Linux-based .NET Core/ASP.NET Core apps.
Where possible, present migration options for both Windows and Linux environments in parallel, rather than focusing solely on Windows/IIS.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a subtle Windows bias by referencing Windows-specific tools (such as web.config and iisnode) without providing Linux equivalents or clarifying cross-platform applicability. Examples and configuration guidance (e.g., for auto-healing and Node.js hosting) reference Windows-centric patterns first or exclusively, and there is a lack of explicit Linux-native configuration examples or alternatives.

Recommendations:

For features like auto-healing, clarify whether configuration via web.config is only for Windows or provide equivalent Linux configuration instructions (e.g., using app settings or startup scripts).
When mentioning iisnode or web.config for Node.js apps, add guidance for Linux-based App Service plans, such as using PM2, process.json, or environment variables.
Wherever a Windows-specific tool or pattern is referenced, provide a Linux-native alternative or note if the feature is not available on Linux.
Ensure that all code/configuration examples are provided for both Windows and Linux environments, or clearly indicate platform applicability.
Consider restructuring sections to avoid always presenting Windows-first, and instead present both platforms equally or in parallel.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. In the 'Premium V3 availability' section, Windows SKU availability is listed before Linux, and the Linux command requires an extra flag. In the automation section, both Azure CLI and Azure PowerShell are shown, but PowerShell (a Windows-centric tool) is given equal prominence to the cross-platform Azure CLI, and the PowerShell example uses Windows-specific worker size names. Throughout the document, there are multiple references to the Azure portal UI, which is platform-agnostic, but there are no explicit Linux shell or scripting examples beyond Azure CLI.

Recommendations:

Present Linux and Windows options in parallel or alternate their order to avoid always listing Windows first.
Clarify that Azure CLI is fully cross-platform and recommend it as the default automation tool for parity.
If showing PowerShell, also consider including Bash or shell script equivalents for Linux users, especially for automation.
In PowerShell examples, clarify if the commands are cross-platform (PowerShell Core) or Windows-only.
Where worker size names differ between platforms, document both sets of options.
Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows.
If possible, add a short Bash script example for Linux users to automate common tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows-specific information is often presented first (e.g., SKU availability, portal instructions), and PowerShell examples are provided alongside Azure CLI, but there are no Linux shell (bash) or automation examples. The portal instructions and screenshots use Windows-centric terminology and navigation. While Linux support is mentioned, practical Linux-specific guidance (such as bash scripting or Linux-native tools) is missing.

Recommendations:

Provide bash shell script examples for Linux users, especially in the 'Automate with scripts' section.
Ensure that Linux-specific instructions (e.g., for custom containers) are included and presented with equal prominence to Windows instructions.
Add screenshots and navigation steps for the Azure portal as seen from Linux environments (if any differences exist).
Clarify any differences in scaling, deployment, or automation workflows between Windows and Linux App Service plans.
List Linux SKU availability before or alongside Windows, not after.
Include troubleshooting steps and error messages specific to Linux deployments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows is frequently presented first in tabbed instructions, and Windows-specific tools (such as the GUI for Hybrid Connection Manager and PowerShell commands) are emphasized or exclusively available. Troubleshooting steps and connectivity tests often use PowerShell examples without providing equivalent Linux commands. The Linux experience is sometimes less fully described (e.g., no GUI, less detail in some steps), and in troubleshooting, Linux-native tools are not always mentioned.

Recommendations:

Alternate the order of Windows and Linux instructions in tabbed sections, or present both equally where possible.
For every PowerShell example (e.g., Test-NetConnection), provide an equivalent Linux command (such as nc, curl, or telnet).
Expand Linux-specific instructions, especially in troubleshooting and connectivity testing, to match the detail and guidance given for Windows.
Where GUI tools are only available for Windows, explicitly note this and provide enhanced CLI/alternative guidance for Linux users.
In troubleshooting, include Linux-native tools (e.g., nslookup, dig, netcat) alongside Windows tools.
Ensure all steps and screenshots that are provided for Windows are matched with Linux equivalents where feasible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exhibits a Windows bias primarily in the section addressing Azure Traffic Manager endpoints, where only a PowerShell script is provided for identifying non-Azure endpoints. There are no equivalent Bash, Azure CLI, or cross-platform scripting examples for Linux or macOS users. The instructions for running the script explicitly reference PowerShell and Windows-style workflows (e.g., '.\TrafficManagerNonAzureEndpoints.ps1'), and no alternative is mentioned. This may hinder Linux/macOS users who do not have access to PowerShell or prefer native tools. Elsewhere, while REST API and Azure CLI commands are referenced, the only concrete scripting example is PowerShell, and there is a general lack of explicit Linux-first or cross-platform guidance.

Recommendations:

Provide equivalent Bash or Azure CLI scripts for identifying non-Azure Traffic Manager endpoints, or at least reference how to run the PowerShell script on Linux/macOS (e.g., via PowerShell Core).
When referencing scripts, clarify their cross-platform compatibility or provide alternatives for Linux/macOS users.
Wherever PowerShell is used, offer Azure CLI or Bash alternatives, especially for discovery and automation tasks.
Explicitly mention that Azure CLI commands are cross-platform and provide example invocations in both Windows (cmd/PowerShell) and Linux/macOS (Bash) syntax.
Consider including a table or section summarizing all available tools/scripts for each OS, ensuring Linux users are not left out.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively discusses discovery of .NET web apps deployed on IIS web servers within VMware environments, which are Windows-centric technologies. There is no mention of Linux-based web servers (such as Apache or Nginx), nor are there examples or guidance for discovering .NET apps running on Linux. All discovery capabilities and dashboard features are described in the context of Windows/IIS, and all referenced resources focus on ASP.NET on IIS.

Recommendations:

Include information about discovering .NET web apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx).
Provide examples or workflows for Linux-based environments, including any differences in discovery steps or requirements.
Mention whether the Azure Migrate appliance supports Linux web servers, and if not, clarify the scope and provide alternative guidance.
Add parity in referenced resources by linking to Linux-focused migration/discovery documentation if available.
Explicitly state any current limitations regarding Linux support to set user expectations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ 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). 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.

Recommendations:

Provide equivalent guidance and examples for Node.js applications running on Azure App Service Linux, including configuration, troubleshooting, and profiling steps.
Include Linux-specific tools and patterns (e.g., using pm2, systemd, Linux file paths, and environment variables) alongside or before Windows-specific instructions.
Offer cross-platform examples where possible, or clearly separate Windows and Linux sections to avoid confusion.
Reference Linux troubleshooting tools (such as top, htop, journalctl, or Linux log file locations) and explain how to access logs and debug on Linux-based App Service.
Clarify in the introduction that the page is Windows-specific, or provide links to Linux-focused documentation if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by referencing Azure Storage Explorer with a direct link to the Windows tab for generating SAS tokens, and by not providing alternative Linux-native tooling or explicit cross-platform instructions for uploading files or generating SAS URLs. All command-line examples use Azure CLI, which is cross-platform, but the only GUI tool mentioned is Storage Explorer, with no mention of Linux alternatives or parity. There are no PowerShell-specific commands, but the documentation assumes the use of tools and workflows more familiar to Windows users.

Recommendations:

Provide explicit instructions or links for using Azure Storage Explorer on Linux and macOS, or mention that it is cross-platform.
Include alternative CLI-based workflows for uploading files and generating SAS URLs (e.g., using 'az storage blob upload' and 'az storage blob generate-sas'), especially for users who may not use GUI tools.
Avoid linking directly to Windows-specific tabs or instructions; ensure parity in documentation for Linux and macOS users.
Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if necessary.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based deployment and management patterns for ASP.NET apps. All runtime version discovery and management instructions reference Windows file paths, tools (Kudu, CMD, PowerShell), and Visual Studio workflows, with no mention of Linux App Service environments or equivalent Linux tooling. There are no Linux-specific examples or parity notes for users deploying to Linux App Service.

Recommendations:

Add parallel instructions and examples for Linux App Service environments, including how to check installed .NET runtimes and access diagnostic tools on Linux.
Include Linux shell (bash) commands and file paths where appropriate, or explicitly state when a feature is Windows-only.
Reference Linux-compatible deployment tools (such as Azure CLI, FTP, or Git) and clarify any differences in workflow for Linux-hosted ASP.NET apps.
Provide guidance on accessing environment variables and logs in Linux containers or App Service on Linux.
Clearly label sections as Windows-specific when Linux alternatives are not available, and link to Linux documentation where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides both Linux and Windows instructions for configuring data sources in Tomcat and JBoss on Azure App Service. However, the Windows section is notably more detailed, with extensive use of PowerShell scripts and Windows-specific paths and tools. The Windows instructions rely heavily on PowerShell and Windows environment variables, while Linux instructions use shell scripts and standard Linux utilities. In several places, Windows tooling (PowerShell, CMD scripts, Windows paths) is described in greater detail and with more step-by-step guidance than the Linux equivalents. The Linux instructions are present and functional, but the documentation leans toward Windows-centric patterns and tools, especially in the Tomcat server-level configuration section.

Recommendations:

Provide equally detailed, step-by-step Linux instructions for Tomcat server-level configuration, including troubleshooting and edge cases.
Offer Bash script examples for Linux that parallel the PowerShell scripts given for Windows, including reusable functions and error handling.
Highlight Linux-native tools and patterns (e.g., systemd, shell scripting, Linux file paths) with the same depth as Windows tools.
Ensure that Linux instructions are presented before or alongside Windows instructions, not after.
Add explicit Linux examples for tasks like setting environment variables, copying files, and running transforms, matching the detail of Windows examples.
Include a summary table comparing Windows and Linux approaches for each major configuration step.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows tools and patterns (IIS, Certreq.exe, PowerShell) are mentioned explicitly, sometimes without Linux equivalents or with Windows-first ordering. PowerShell and Azure CLI are both shown for some automation, but in certificate export/import scenarios, Windows tools are referenced directly, and Linux workflows are less detailed or only briefly mentioned (e.g., OpenSSL). There are missing Linux-specific examples for some certificate management tasks, and the documentation assumes familiarity with Windows-centric approaches.

Recommendations:

For every mention of Windows tools (IIS, Certreq.exe), provide equivalent Linux workflows (e.g., using OpenSSL, certbot, or other common Linux utilities) with step-by-step instructions.
When showing automation or scripting, always provide both Azure CLI (cross-platform) and PowerShell examples, and present them in parallel tabs, not with PowerShell first.
Explicitly mention Linux and macOS compatibility for all command-line instructions, and clarify any OS-specific prerequisites or differences.
Add troubleshooting tips or notes for Linux users, especially for certificate export/import and file format handling.
Review all screenshots and UI references to ensure they are not Windows-specific, or add clarifying notes for Linux users where needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows-first bias by consistently referencing Windows file paths (e.g., D:\home\site\wwwroot) before Linux equivalents, and in some sections, omitting Linux paths entirely. The instructions and examples focus on Windows directory structures and deployment patterns, with minimal or no explicit Linux-specific guidance or examples. There is also a reliance on Windows-centric terminology and tools, such as the use of backslashes in paths and references to drive letters, which may not be familiar or applicable to Linux users.

Recommendations:

Provide Linux file path equivalents (e.g., /home/site/wwwroot) alongside Windows paths in all relevant sections, not just in introductory remarks.
Include explicit Linux-focused examples and instructions, especially for manual deployment steps (e.g., creating directories, handling permissions).
Avoid using Windows drive letters and backslashes as the default; present both Windows and Linux path formats in parallel.
Clarify any differences in behavior or requirements between Windows and Linux App Service environments.
Where tools or commands are platform-specific, offer alternatives or note cross-platform compatibility.
Review and update all references to deployment directories and file operations to ensure Linux parity and clarity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools and workflows (such as Visual Studio and right-click context menus), and omitting explicit Linux or cross-platform alternatives. Instructions for package installation and project manipulation are given with a Windows-first perspective, and there are no Linux-specific or cross-platform command-line examples for common tasks such as file creation, navigation, or package management.

Recommendations:

Provide explicit Linux and cross-platform instructions for all steps, especially for project/file creation and package installation (e.g., using dotnet CLI and text editors like VS Code or nano).
When referencing Visual Studio or right-click actions, also describe equivalent CLI commands (e.g., 'dotnet new razor' or 'touch OpenAI.razor') and mention cross-platform editors.
For NuGet package installation, show both Visual Studio GUI and dotnet CLI commands (e.g., 'dotnet add package Microsoft.SemanticKernel').
Avoid assuming the use of Windows-specific tools or workflows; ensure all steps can be followed on Linux and macOS.
Add a section or callouts for Linux/macOS users, highlighting any differences or additional steps required.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for per-app scaling, with no equivalent examples for Linux-native tools (such as Azure CLI or Bash). The use of PowerShell cmdlets and parameters is exclusive, and there is no mention of how to perform these tasks on Linux or macOS environments. The ARM template section is platform-neutral, but all imperative (command-line) instructions are Windows-centric.

Recommendations:

Add Azure CLI examples for all PowerShell commands, showing how to create and configure per-app scaling using az commands.
Include Bash shell examples where appropriate, especially for scripting scenarios.
Explicitly mention that the PowerShell examples are cross-platform only if they are (e.g., Azure PowerShell Core), or clarify if they are Windows-only.
Present Azure CLI (or REST API) examples before or alongside PowerShell to avoid a 'Windows-first' impression.
Add a note or section for Linux/macOS users, guiding them to equivalent tooling and commands.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for retrieving outbound IP addresses, but PowerShell examples are always presented after CLI and without explicit mention of cross-platform compatibility. There is no explicit mention that Azure PowerShell can be used on Linux/macOS, nor are there any Bash or Linux-native command examples (other than nslookup and curl). The outbound IPv6 support section specifically notes that outbound IPv6 is only available for Windows apps, with no Linux parity or roadmap. There are no Linux-specific troubleshooting or example scenarios, and the documentation does not clarify which commands are cross-platform or provide Linux-specific guidance where behavior differs.

Recommendations:

Explicitly state that Azure PowerShell is cross-platform and can be used on Linux/macOS, or clarify if any commands are Windows-only.
Provide Bash or Linux-native command examples (e.g., using jq with az CLI output) where appropriate, especially for common tasks like querying IP addresses.
Add a note or table summarizing feature parity (such as outbound IPv6 support) between Windows and Linux App Service plans, and provide guidance or alternatives for Linux users where features are missing.
Ensure that examples and instructions are not presented in a 'Windows first' order; consider alternating or grouping by platform.
Include troubleshooting steps or caveats for Linux users, especially where network tools or behaviors may differ.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias. It provides detailed subnet/IP calculations specifically for Windows Containers, mentions Windows Server Active Directory domain join as a non-supported feature, and references Kudu (primarily a Windows-based tool) for environment variable inspection. While Linux is mentioned in the context of continuous deployment, there are no Linux-specific configuration or troubleshooting examples, and Windows-specific scenarios are described in greater detail.

Recommendations:

Add parallel examples and calculations for Linux containers and Linux-based App Service plans, not just Windows Containers.
Include Linux-specific limitations, best practices, and troubleshooting steps where relevant (e.g., for environment variables, scaling, and networking).
Mention Linux-native tools (such as SSH, Bash, or Linux-based diagnostic tools) alongside or instead of Windows tools like Kudu.
Ensure that any Windows-specific features or limitations are matched with Linux equivalents or explicitly state when a feature is Windows-only.
Provide balanced coverage in examples and sample calculations for both Windows and Linux scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias: logging types and features are described in detail for Windows before Linux, and several logging features (web server logging, detailed error messages, failed request tracing) are only available or described for Windows. Linux instructions are less detailed and sometimes missing. Windows-specific tools and file paths are mentioned (e.g., Log Parser, D:\home\LogFiles), while Linux equivalents are not provided.

Recommendations:

Provide Linux parity by explicitly stating which logging features are available or unavailable for Linux, and offer alternative solutions or workarounds where features are Windows-only.
Include Linux-specific examples, such as file paths (/home/LogFiles), and recommend cross-platform tools for log analysis instead of or in addition to Windows-only tools like Log Parser.
Structure sections to present both Windows and Linux instructions in parallel, rather than focusing on Windows first and relegating Linux to later or shorter sections.
Clarify limitations for Linux (e.g., lack of web server logging, detailed error messages, failed request tracing) and suggest best practices for Linux users.
Where possible, provide code or configuration examples for popular Linux stacks (Node.js, Python, Java, etc.), not just .NET/ASP.NET.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by frequently referencing Windows-specific tools and patterns, such as PowerShell, IIS diagnostics, and SysInternals Procdump. Examples and instructions for troubleshooting and diagnostics are primarily oriented toward Windows environments, with little to no mention of Linux equivalents or cross-platform alternatives. The Kudu console is described as supporting PowerShell and DOS commands, but there is no mention of Bash or Linux shell support. Diagnostic features like Failed Request Tracing and .NET Profiler are referenced with Windows-specific links and terminology, and there is no guidance for Linux-based App Service environments.

Recommendations:

Include Linux-specific troubleshooting steps and examples, such as using Bash in the Kudu console, Linux diagnostic tools, and log formats.
Reference Linux equivalents for IIS features, such as Apache/Nginx error logs and tracing.
Provide parity in instructions for enabling diagnostics and profiling for Linux-based App Service plans (e.g., Application Insights for Node.js, Python, Java).
Add examples for managing and restarting apps using Azure CLI and Bash, not just PowerShell.
Clarify which features and tools are available on Linux App Service plans and provide links to relevant documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias. While it covers both Windows and Linux scenarios, Windows-specific tools, settings, and examples are often mentioned first or in more detail. Some deployment and configuration instructions are Windows-centric, and Linux equivalents are sometimes less prominent or missing. PowerShell is referenced as an option, but Linux shell examples are less emphasized. In performance and deployment sections, Windows commands and settings are presented before Linux, and ReadyToRun instructions focus on Windows before Linux. Some CLI commands and explanations are tailored to Windows users, with Linux guidance added as an afterthought or in a separate tab.

Recommendations:

Ensure that all command-line examples (e.g., Azure CLI, dotnet publish) are shown for both Windows and Linux, with equal prominence.
When listing tools or methods (e.g., Visual Studio, Visual Studio Code, Azure CLI, PowerShell), avoid listing Windows-specific tools first by default; alternate order or group by platform.
Provide Linux shell (bash) equivalents for any PowerShell or Windows Command Prompt examples.
In sections like ReadyToRun and deployment, present Linux and Windows instructions side-by-side or in parallel tabs, not with Windows first.
Where platform-specific settings are required (e.g., netFrameworkVersion vs. linuxFxVersion), make sure both are described with equal detail and visibility.
Explicitly mention any differences or limitations for Linux users up front, not only in footnotes or after Windows instructions.
Review all code snippets and ensure none assume a Windows file system or path structure unless platform-specific.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides examples and instructions that reference PowerShell and Windows-centric tools (such as Visual Studio and Visual Studio Code) and does not offer equivalent Linux-specific guidance or examples. The use of PowerShell as a pivot language and the absence of Linux command-line examples or references to Linux-native editors (such as VS Code on Linux or CLI workflows) indicate a bias toward Windows environments. There are no explicit instructions for Linux users on installing extensions or managing project files.

Recommendations:

Add explicit Linux/macOS examples for installing and managing extensions, including CLI commands and file operations.
Reference cross-platform editors (such as VS Code on Linux/macOS) and provide parity with Visual Studio instructions.
Include bash/zsh shell examples alongside PowerShell where CLI commands are shown.
Clarify that Azure Functions Core Tools and related workflows are cross-platform, and provide troubleshooting or setup notes for Linux users.
Where project file editing is required, show how to do this using Linux-native tools (nano, vim, etc.) or VS Code on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ cmd_examples

⚠️ missing_linux_tool_examples

Summary:

The documentation provides both Bash and Windows CMD examples for command-line operations, but Windows CMD examples are consistently presented alongside Bash, rather than prioritizing Linux-specific shell environments (e.g., zsh, fish). There is no evidence of exclusive use of Windows tools or PowerShell, nor are Windows-specific patterns or tools mentioned before Linux equivalents. However, the documentation does not include Linux-specific troubleshooting, nor does it mention Linux-only tools or workflows (such as systemd, journalctl, or Linux file paths). The examples and instructions are generally cross-platform, but the presence of CMD examples and lack of Linux-specific tool references indicate a mild Windows-first bias.

Recommendations:

Add explicit Linux troubleshooting steps and references to common Linux tools (e.g., journalctl for logs, systemd for service management).
Include Linux-specific examples for environment variable configuration and file system paths.
Consider prioritizing Bash or POSIX shell examples, and move CMD examples to secondary tabs or footnotes.
Mention differences in local development environments (e.g., how to install Maven/Java on Linux vs. Windows).
Provide guidance for Linux package management (apt, yum) for installing prerequisites.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page is generally cross-platform and Linux-focused for hosting, but there is evidence of Windows bias in development and publishing workflows. Windows tools and patterns (such as Visual Studio Code and command prompt) are mentioned first or exclusively in several places, and remote build is recommended specifically for Windows users. There is also a tendency to refer to 'command prompt' generically, which is a Windows-specific term, and PowerShell/Windows-centric workflows are implied in publishing and development instructions. Linux equivalents (such as bash, terminal, or shell) are not always mentioned, and guidance for Linux users is less explicit.

Recommendations:

Use neutral terminology such as 'terminal' or 'shell' instead of 'command prompt', and clarify when instructions apply to both Windows and Linux.
Provide explicit Linux/bash examples alongside Windows/command prompt examples, especially for publishing and development workflows.
When recommending remote build for Windows users, also provide guidance for Linux/Mac users and clarify any differences.
Mention Linux tools and patterns (e.g., bash, zsh, Linux package managers) where appropriate, and ensure parity in instructions.
Ensure that all references to development environments (e.g., Visual Studio Code, Azure CLI) include cross-platform installation and usage notes.
Review all sections for implicit Windows assumptions and add Linux-specific notes or examples where missing.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows some Windows bias, particularly in the Java section where command examples are presented for Bash, PowerShell, and Cmd, with PowerShell and Cmd (Windows shells) given equal prominence to Bash (Linux/macOS). The Java Maven archetype instructions list Bash first, but Windows shells are not clearly deprioritized. There are also references to Windows-style paths (e.g., '\src\main\java\com\fabrikam'), and the use of 'command prompt' terminology, which is more common in Windows contexts. While most CLI examples are cross-platform, the documentation does not always clarify Linux-specific nuances, and some steps (like stopping the function host) use Windows-centric key combinations (Ctrl+C and 'choose y'), which may differ on Linux. There are no explicit Linux-only examples or troubleshooting tips, and some tools (like jq) are mentioned as available in Azure Cloud Shell but not directly addressed for local Linux environments.

Recommendations:

For every example that lists PowerShell or Cmd, ensure Bash or sh is listed first and clearly marked as the default for Linux/macOS users.
When referencing file paths, use POSIX-style paths (forward slashes) or provide both Windows and Linux/macOS path formats.
Avoid using 'command prompt' as a generic term; instead, use 'terminal' or specify 'Windows Command Prompt' when appropriate.
Provide explicit Linux/macOS troubleshooting notes where behaviors may differ (e.g., process termination, permissions, environment variables).
Clarify installation and usage of tools like jq for Linux users, not just in the context of Azure Cloud Shell.
Include a section or callouts for common Linux/macOS issues or tips, such as case sensitivity, shell differences, or required dependencies.
Ensure that all scripts and code snippets are tested and work as-is on both Windows and Linux/macOS platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation for creating an SMB volume in Azure NetApp Files demonstrates a Windows bias. All examples and instructions for managing SMB permissions and shares are provided exclusively for Windows environments, referencing Windows tools such as MMC and the Windows Security tab. There are no examples or guidance for managing SMB shares or permissions from Linux or macOS clients, nor are cross-platform tools or commands mentioned. The documentation assumes the administrator is using a Windows client for all SMB management tasks.

Recommendations:

Include instructions and examples for managing SMB shares and permissions from Linux clients, such as using smbclient, mount.cifs, or setfacl.
Mention and provide examples of cross-platform tools (e.g., Samba utilities) for accessing and managing SMB shares.
Where Windows-specific tools are referenced (e.g., MMC, Security tab), add equivalent steps or notes for Linux/macOS environments, or clarify if certain features are only available via Windows.
In sections about mounting or accessing SMB shares, provide both Windows and Linux command-line examples.
Review and update the documentation to ensure Linux and macOS administrators can perform all necessary tasks without requiring access to a Windows machine.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for feature registration and status checking, mentioning PowerShell before Azure CLI, and omitting any Linux-specific or cross-platform command-line examples. There are no examples or guidance for Linux users or for using non-Windows tools to access or automate metrics.

Recommendations:

Provide equivalent Azure CLI examples alongside PowerShell commands, with full syntax and output expectations.
Present Azure CLI (cross-platform) examples before or alongside PowerShell to avoid the impression of Windows-first bias.
Include explicit instructions or examples for Linux/macOS users, such as using bash or shell scripts for automation.
Where screenshots or UI navigation are shown, clarify that the Azure portal is web-based and platform-agnostic.
Audit for any other sections where only Windows tools or terminology are used, and add Linux/cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation lists both Azure CLI and PowerShell as supported CLI tools, but PowerShell is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows-centric tool (even though it is now cross-platform, its usage is still heavily associated with Windows). There are no explicit Linux shell (bash) examples or references, and no mention of Linux-native tooling or usage patterns. The documentation does not provide any Linux-specific guidance or examples, which may make Linux users feel less prioritized.

Recommendations:

Add explicit bash/Linux shell examples for common Azure NetApp Files operations using Azure CLI.
Clarify that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
If mentioning PowerShell, note that it is available cross-platform, but provide parity by including bash or shell equivalents.
Consider listing Azure CLI before PowerShell in tables and descriptions, as it is the primary cross-platform tool.
Include a section or note for Linux users about installation and usage best practices.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias. All configuration commands and monitoring instructions use Windows-specific tools (PowerShell cmdlets like Get-SmbClientNetworkInterface, set-SmbClientConfiguration, and Windows Performance Monitor). References to SMB features and encryption are framed in terms of Windows versions and tools, with no mention of Linux or cross-platform SMB clients. There are no Linux or Samba examples, and no discussion of how to achieve similar monitoring or configuration on non-Windows systems.

Recommendations:

Add equivalent Linux/Samba examples for SMB Multichannel configuration and verification (e.g., using smb.conf, smbstatus, or smbtree).
Include Linux command-line tools (such as netstat, ifconfig, ethtool, or perf) for monitoring network interfaces and SMB connections.
Discuss SMB feature support and configuration for popular Linux distributions, including how to enable or verify SMB Multichannel, signing, and encryption in Samba.
Provide performance monitoring guidance for Linux (e.g., using iostat, atop, or other Linux-native tools).
Reference both Windows and Linux documentation for SMB features, and clarify any differences in feature support or configuration steps.
Where possible, use cross-platform terminology and avoid assuming the reader is using Windows exclusively.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. In several sections, Windows workloads and tools are mentioned first or exclusively, such as in the 'Windows Apps and SQL Server solutions' and SAP NetWeaver sections, where Windows-specific technologies (e.g., DFS Namespaces, SMB, FSLogix) are highlighted. There are references to Windows tools and patterns (DFS-N, FSLogix, SMB) without always providing equivalent Linux/NFS or cross-platform alternatives. Some solution areas (e.g., Virtual Desktop Infrastructure) focus almost entirely on Windows-based technologies, with little or no mention of Linux-based desktop solutions. While Linux workloads are covered in detail in some sections, the overall structure and example ordering often prioritize Windows scenarios.

Recommendations:

Ensure that for every Windows-specific example or tool (e.g., DFS-N, FSLogix, SMB), a Linux/NFS or cross-platform equivalent is provided and described with equal prominence.
When listing solution references, alternate or group by platform rather than consistently listing Windows first.
Expand Virtual Desktop Infrastructure coverage to include Linux-based VDI solutions, if supported.
In sections where Windows tools are discussed (e.g., DFS-N for SAP), provide parallel guidance for Linux/NFS-based approaches.
Review all example scenarios to ensure Linux and open-source workloads are given equal depth and visibility as Windows workloads.
Where possible, use neutral, cross-platform terminology and avoid implying Windows is the default or primary use case.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell command examples for feature registration, mentioning PowerShell before Azure CLI, and omitting explicit Linux or cross-platform command-line examples. The registration steps are shown exclusively with PowerShell, and while Azure CLI is referenced, no CLI command-line examples are provided. There are no Linux-specific instructions or screenshots, and the UI instructions use Windows-centric terminology (e.g., 'right-click').

Recommendations:

Provide Azure CLI command-line examples alongside PowerShell for all registration and management steps, showing both syntaxes explicitly.
Include Linux/macOS-specific instructions or notes where relevant, especially for command-line operations.
Use neutral UI terminology (e.g., 'select', 'open context menu') instead of 'right-click', or clarify how to perform these actions on different platforms.
Add screenshots or CLI output examples from non-Windows environments to demonstrate parity.
Consider a tabbed or side-by-side format for PowerShell and CLI examples, making it clear that both are supported and cross-platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several areas. Windows administration steps and tools (such as GUI instructions and PowerShell commands) are presented first and in detail, while Linux/NFS instructions are less explicit and often deferred to other documentation. PowerShell is used for feature registration, with Azure CLI only briefly mentioned. There are no Linux command-line examples for setting audit ACEs or SACLs, and Windows GUI tools are described in detail, but equivalent Linux workflows are missing.

Recommendations:

Provide explicit Linux command-line examples for setting Audit ACEs on NFSv4.1 volumes, such as using nfs4-acl-tools or setfacl.
Include step-by-step instructions for configuring audit ACEs on Linux, similar to the detailed Windows GUI steps.
Present Azure CLI examples for feature registration before or alongside PowerShell, and ensure parity in instructions for both platforms.
Balance the order of presentation so that Linux and Windows instructions are given equal prominence.
Reference Linux administration hosts and tools (e.g., nfs4-acl-tools, setfacl) where appropriate, not just Windows hosts.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by listing PowerShell as a primary tool for snapshot management and automation, and by referencing Windows-centric scripting and tools before Linux alternatives. There are no explicit Linux shell or scripting examples, and the documentation does not mention Linux-specific tools or patterns for managing Azure NetApp Files snapshots. While NFS and SMB are mentioned for volume creation, the operational examples and tooling references favor Windows environments.

Recommendations:

Include Linux shell (bash) and scripting examples alongside PowerShell, especially for common tasks such as creating, restoring, and deleting snapshots.
Reference Linux-native tools (e.g., Azure CLI usage in bash, REST API calls via curl, automation with cron jobs) equally or before Windows/PowerShell tools.
Provide sample commands for both Windows and Linux environments when discussing manual and automated snapshot management.
Clarify cross-platform support and parity in tooling, ensuring that Linux administrators have clear guidance and examples.
Add links to Linux-focused documentation or community resources for Azure NetApp Files snapshot management.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation page exhibits Windows bias by referencing PowerShell as the restore method for encrypted VMs, and by only linking to Windows-specific disk encryption documentation. There are no Linux-specific restore examples, nor are Linux disk encryption scenarios mentioned. The restore scenarios table and linked articles focus on Windows tools and patterns, omitting Linux equivalents.

Recommendations:

Include Linux-specific restore instructions and examples, especially for encrypted VMs (e.g., using CLI or Azure portal for Linux VMs).
Add links to Linux disk encryption documentation (such as Azure Disk Encryption for Linux).
Mention Linux restore scenarios explicitly in tables and descriptions, ensuring parity with Windows.
Provide sample commands for both PowerShell (Windows) and Bash/CLI (Linux) where applicable.
Clarify which restore options and features are available for Linux VMs, and note any differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows VM examples, referencing Windows-specific tools and patterns (such as PowerShell and bcdedit), and omitting equivalent Linux-focused guidance or examples. Linux scenarios are only briefly mentioned, with minimal actionable detail, and no Linux command-line or tool examples are provided.

Recommendations:

Provide Linux-specific examples alongside Windows ones, especially for restore operations, disk attachment, and post-restore steps.
Include Linux command-line (e.g., Bash, Azure CLI) and tool usage (such as cloud-init, SSH, or Linux disk mounting) in relevant sections.
Balance references to Windows and Linux documentation links (e.g., for attaching disks, resetting passwords, or configuring networking).
Where PowerShell is mentioned, also provide equivalent Azure CLI or Bash scripts for Linux users.
In post-restore troubleshooting, add Linux-specific recovery steps (e.g., using GRUB, resetting SSH keys, fixing fstab, or re-enabling cloud-init).
Explicitly call out differences in restore workflows or limitations for Linux VMs, not just Windows.
Ensure that screenshots and UI walkthroughs are not exclusively Windows-centric, and clarify when steps are OS-agnostic.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily biased towards Windows and PowerShell usage. All examples are provided exclusively in PowerShell, with Windows file paths (e.g., C:\), and there is no mention of Bash, Azure CLI, or Linux-native tooling. Even when Linux VMs are referenced, the instructions and code samples remain PowerShell-centric, assuming the user is running PowerShell (likely on Windows) and using Windows-style file handling. There are no Linux command-line examples or guidance for users who manage Azure resources from Linux environments.

Recommendations:

Provide equivalent examples using Azure CLI (az) and Bash scripts for Linux users.
Include Linux file path examples (e.g., /home/user/vmencryption_config.json) alongside Windows paths.
Clarify which steps are OS-agnostic and which are specific to Windows or Linux.
Add a section or callouts for performing these operations from a Linux or cross-platform environment.
Reference cross-platform tools and patterns (e.g., Azure Cloud Shell, which supports both PowerShell and Bash).
Ensure that Linux VM scenarios are given equal prominence and not treated as an afterthought.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias by mentioning Windows tools (Volume Shadow Copy Service - VSS) before Linux equivalents (fsfreeze), and by linking to Windows-specific VM agent and snapshot extension documentation without providing Linux equivalents or examples. There are no Linux-specific backup configuration examples or links to Linux agent/snapshot documentation, and the use of pre/post scripts for Linux is only mentioned as a scenario where crash-consistent backup should not be used, without further guidance.

Recommendations:

Provide equal coverage of Linux backup mechanisms, such as linking to Linux VM agent and snapshot extension documentation.
Include Linux-specific examples or scenarios for configuring crash-consistent backups.
Mention Linux tools (e.g., fsfreeze) alongside Windows tools (VSS), and ensure they are described with equal prominence.
Clarify agent and extension requirements for both Windows and Linux VMs, with direct links to relevant documentation for each OS.
Add guidance or examples for Linux users who use pre/post scripts, including alternatives or best practices for crash-consistent backups.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page provides general guidance for backing up and restoring encrypted Azure VMs, mentioning both Windows and Linux support. However, when it comes to practical examples and command-line instructions, only PowerShell commands are provided (e.g., for identifying a VM's associated key vault), with no equivalent Linux (Bash/CLI) examples. Additionally, Windows tools and terminology (BitLocker, PowerShell) are mentioned before their Linux equivalents (dm-crypt), and there is a lack of parity in step-by-step instructions for Linux users.

Recommendations:

Add Bash/Azure CLI examples alongside PowerShell commands for all VM and Key Vault operations.
When describing encryption technologies, mention Linux (dm-crypt) first or equally with Windows (BitLocker), and provide links to relevant Linux documentation.
Ensure all procedural steps (such as identifying a VM's key vault, setting access policies) include both Windows and Linux command-line instructions.
Review screenshots and UI instructions to ensure they are OS-neutral or provide notes for Linux-specific considerations.
Explicitly state that both Windows and Linux VMs are supported in all relevant sections, and avoid implying Windows is the default or primary platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several areas. Windows-specific tools (VSS) and PowerShell are mentioned first and in detail, while Linux equivalents are referenced only briefly or generically (e.g., 'pre/post scripts' and 'freeze' tool). There are no concrete Linux command/script examples, and guidance for Linux is less prescriptive. The restore example specifically references PowerShell for managed disk restores, with no Linux CLI or automation alternatives provided.

Recommendations:

Provide Linux CLI (az CLI) and shell script examples alongside PowerShell examples for backup and restore operations.
Mention Linux tools (e.g., LVM snapshots, fsfreeze) with equal detail as VSS for Windows.
Include step-by-step Linux backup/restore automation workflows, not just generic references to 'pre/post scripts'.
Present Windows and Linux instructions in parallel, rather than listing Windows first.
Clarify any differences in agent/extension installation and configuration for Linux VMs.
Add troubleshooting and best practices sections specific to Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page primarily describes backup configuration and management using the Azure Portal, which is platform-agnostic. However, in the 'Related content' section, Azure PowerShell is listed before Azure CLI and REST API, suggesting a Windows-first approach. There are no explicit Linux-specific examples, nor are Linux command-line tools or patterns mentioned. The documentation does not provide parity in examples for Linux users, such as Bash scripts or CLI walkthroughs, and omits references to Linux desktop environments when describing portal navigation.

Recommendations:

List Azure CLI examples before or alongside Azure PowerShell to avoid Windows-first ordering.
Add explicit step-by-step examples using Azure CLI for all major backup and restore operations, not just in related content.
Include Bash script samples for automating backup tasks on Linux.
Mention that the Azure Portal is accessible from any OS and clarify any platform-specific differences if they exist.
Where screenshots are shown, note that the UI is identical across platforms and browsers.
Ensure REST API examples include curl commands for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exhibits a Windows bias by referencing Windows-specific tools and patterns before Linux equivalents. For example, the OS disk swap is linked only to Windows documentation, and PowerShell is suggested for VM creation without mentioning Linux alternatives (such as Azure CLI or Bash). Linux-specific restore steps are relegated to a separate section, and there are no Linux command examples or references to Linux-native tooling. Windows terminology and links appear first or exclusively in several places.

Recommendations:

Provide Linux-specific examples alongside Windows ones, such as using Azure CLI or Bash scripts for VM creation from restored disks.
Include links to both Windows and Linux OS disk swap documentation.
Mention Linux tools and patterns (e.g., cloud-init, SSH) where relevant, not just PowerShell.
Ensure that restore steps for Linux VMs are integrated throughout the guide, not isolated in a separate section.
Add parity in troubleshooting and next steps, referencing both Windows and Linux agent/extension issues.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by primarily referencing the Azure portal (a GUI tool most familiar to Windows users), mentioning PowerShell/CLI scripts for permissions without providing explicit Linux (bash) examples, and omitting any Linux-specific command-line workflows for mounting or restoring disks. There are no examples or instructions tailored for Linux administrators, despite SAP HANA commonly running on Linux.

Recommendations:

Add explicit Linux command-line (bash) examples for mounting and restoring disks, such as using 'lsblk', 'mount', or 'fdisk' to identify and mount attached disks.
Provide Azure CLI examples in bash syntax, not just PowerShell, for assigning permissions and managing resources.
Include a section or callouts specifically for Linux administrators, detailing steps that would be performed on a Linux VM (e.g., mounting disks, updating fstab, checking disk status).
Ensure parity in screenshots and instructions for both Windows and Linux environments, or clarify when steps are OS-agnostic.
Avoid referencing PowerShell or Windows tools/scripts as the default; instead, present both PowerShell and bash/CLI alternatives side by side.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by consistently listing Azure portal and Azure PowerShell methods before Azure CLI, which is more commonly used on Linux. Examples and links for configuration tasks (SKU selection, subnet, public IP, host scaling) are provided for Azure portal and PowerShell, with CLI included but always after Windows-centric tools. There are no explicit Linux shell or scripting examples, nor references to Linux-specific workflows or tools. The documentation does not mention Linux desktop usage or provide parity for Linux administrators beyond the CLI.

Recommendations:

Alternate the order of examples so that Azure CLI is listed before PowerShell and portal in some sections, or group them without implied priority.
Add explicit Bash or shell script examples for common configuration tasks, demonstrating usage from a Linux environment.
Include notes or sections addressing Linux-specific workflows, such as using SSH keys from Linux, or integrating with Linux desktop environments.
Ensure that all features and configuration steps have CLI examples and links, and verify that CLI instructions are as detailed as PowerShell ones.
Consider adding troubleshooting or tips sections for Linux users, e.g., common issues when connecting from Linux clients.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides detailed instructions and code samples for performing tasks using the Azure portal and Azure PowerShell, but does not include equivalent examples for Linux/Unix command-line users (e.g., Azure CLI or Bash). The only command-line automation shown is via PowerShell, which is primarily a Windows tool, though it is available cross-platform. There are no Bash, Azure CLI, or shell script examples, and no mention of Linux-native tools or workflows.

Recommendations:

Add Azure CLI examples for all tasks currently demonstrated with PowerShell, including adding and removing custom domains.
Include Bash or shell script snippets where appropriate, especially for users managing DNS or CDN resources from Linux/macOS environments.
Explicitly mention that PowerShell is available cross-platform, but provide parity with Azure CLI to serve Linux-first users.
Consider including a table or section comparing how to accomplish the same tasks in PowerShell, Azure CLI, and the Azure portal.
Reference Linux-native DNS management tools (e.g., dig, nsupdate) for DNS verification steps, where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (a web GUI that is most commonly used on Windows), and by mentioning tools and patterns that are typically associated with Windows environments (such as Power BI, Azure Commerce Toolbox, and PowerShell scripts) without providing equivalent Linux or cross-platform CLI examples. There are no instructions or examples using Azure CLI, Bash, or Linux-native tools, nor are there references to Linux-specific workflows. The documentation assumes use of the Azure portal and PowerShell for administrative tasks, and does not mention or prioritize Linux-compatible methods for billing account setup and migration.

Recommendations:

Add equivalent examples using Azure CLI (az billing, az account, etc.) for all major steps, including billing account setup, role assignment, and migration validation.
Include Bash script snippets for common administrative tasks, such as exporting billing data or managing roles, to demonstrate Linux compatibility.
Reference cross-platform tools (such as Azure CLI and REST API calls) before or alongside Windows-specific tools like PowerShell.
Explicitly state that all steps can be performed on Linux, macOS, and Windows, and provide links to platform-agnostic documentation.
Where screenshots of the Azure portal are shown, consider including CLI output examples for parity.
Mention and link to documentation for Linux users on installing and using Azure CLI and other relevant tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for retrieving the service principal ID, but lists Azure CLI first. However, there is a notable emphasis on Azure PowerShell, and no explicit mention of Linux or bash-specific patterns, nor any examples using bash scripting or Linux-native tools. The rest of the documentation is platform-neutral, focusing on REST API calls, but the lack of Linux-specific guidance or examples may disadvantage Linux users.

Recommendations:

Add explicit bash/shell script examples for key steps, such as retrieving service principal IDs and making REST API calls.
Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS environments.
Include troubleshooting notes or tips relevant to Linux environments (e.g., authentication, environment variables).
Where PowerShell is mentioned, also provide equivalent bash/CLI commands side-by-side.
Ensure that any tool references (e.g., Azure CLI, PowerShell) specify their availability and installation instructions for Linux.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page focuses exclusively on assessing ASP.NET web apps, implicitly targeting Windows-based workloads without mentioning Linux-based .NET web apps or providing Linux-specific guidance. All linked resources and terminology (e.g., ASP.NET, App Service migration) are traditionally associated with Windows environments, and there is no discussion of Linux tools, commands, or assessment nuances for Linux-hosted .NET apps.

Recommendations:

Include explicit references to both Windows and Linux-hosted .NET web apps in the assessment process.
Provide examples or links for assessing .NET Core/ASP.NET Core apps running on Linux, including any differences in assessment steps or tooling.
Mention any Linux-compatible tools or scripts for assessment, or clarify if the process is identical across platforms.
Add a section or note on platform-specific considerations (e.g., file system, dependencies, environment variables) when assessing apps for migration.
Ensure that documentation and linked resources address both Windows and Linux scenarios equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a 'windows_first' bias by referencing the Windows deployment path (C:\home\site\wwwroot) first and only providing a Linux-specific path as a note later. There are no Linux-specific examples or step-by-step instructions, and the guidance for Linux is limited to a note about absolute paths, without parity in example or detail.

Recommendations:

Provide Linux-specific examples alongside Windows examples, such as using /home/site/wwwroot/auth.json as the default path in the main instructions.
When mentioning file paths, always present both Windows and Linux formats together (e.g., C:\home\site\wwwroot\auth.json for Windows, /home/site/wwwroot/auth.json for Linux).
Include a dedicated section or callout for Linux users, outlining any platform-specific considerations or steps.
Ensure that all configuration steps and references are equally detailed for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_windows_cli_example

Summary:

The documentation presents Windows container SSH access first, but only describes browser-based SSH for Windows, while Linux containers receive detailed Azure CLI and SSH client instructions. There are no PowerShell or Windows CLI examples for Windows containers, and the Linux section is much more comprehensive in terms of tooling and usage patterns.

Recommendations:

Provide equivalent CLI or PowerShell instructions for opening SSH sessions to Windows containers, if supported.
Clarify why Azure CLI SSH is not supported for Windows containers and suggest any alternative approaches.
Balance the order of presentation so that Linux and Windows instructions are given equal prominence.
If Windows containers only support browser SSH, explicitly state this limitation and offer guidance for advanced scenarios or troubleshooting.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias. In the prerequisites and quickstart links, 'windows' is explicitly listed as a tab or context before Linux, and there are no explicit Linux or cross-platform shell examples for environment variable setup, deployment, or local development. All environment variable instructions reference the Azure portal GUI, with no CLI or Linux shell alternatives. There are no PowerShell-specific commands, but the absence of Linux/Bash examples and the ordering of 'windows' first in quickstart links indicate a subtle bias.

Recommendations:

Provide explicit Linux/Bash shell examples for setting environment variables, running the app, and deploying to Azure App Service.
Ensure that quickstart and sample links either default to cross-platform or include both Windows and Linux tabs equally, with Linux not always listed after Windows.
Include Azure CLI commands for common tasks (e.g., setting app settings, deploying) alongside portal instructions.
Clarify that all Python and Flask instructions are cross-platform, and add notes or callouts for any OS-specific steps.
Where possible, use neutral language and ordering (e.g., 'Windows or Linux') in lists and instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation assumes a development environment based on GitHub Codespaces and .NET, but does not provide any explicit Windows-only commands or tools. However, it lacks explicit Linux or cross-platform terminal instructions, and does not mention Linux-specific deployment or testing steps. The use of 'Open in Browser' and reliance on Azure App Service (which is cross-platform) is neutral, but the absence of Linux CLI or shell examples, and the lack of mention of Linux development environments, results in a subtle Windows or general non-Linux bias.

Recommendations:

Explicitly mention that all commands (e.g., 'dotnet run', 'azd up') work on Linux, macOS, and Windows, and provide any necessary shell syntax differences if applicable.
Include examples of running the sample app and deploying from a Linux terminal (e.g., bash), or clarify that the instructions are cross-platform.
If using Codespaces, note that it is a Linux-based environment, and provide guidance for users developing locally on Linux or macOS.
Add troubleshooting notes for common Linux-specific issues (e.g., permissions, case sensitivity, environment variables).
Where GUI actions are described (e.g., 'Open in Browser'), provide CLI alternatives (e.g., using 'xdg-open' on Linux or 'open' on macOS).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation generally uses cross-platform tools (Docker, .NET, Git) and console commands, which are not inherently Windows-specific. However, in the Docker run example with persisted data, the bind mount path uses a Windows-style path (C:\aace:/app/.aace) without providing a Linux/macOS equivalent. There are no explicit Linux/macOS examples for bind mounts or file paths, and the only file path example is Windows-specific. This may cause confusion or extra effort for Linux/macOS users.

Recommendations:

Provide both Windows and Linux/macOS examples for Docker bind mounts. For example, include a Linux example like: -v "$HOME/.aace:/app/.aace".
When showing file paths, present both Windows and Unix-style paths side by side or in tabs.
Explicitly mention that the console commands work on all platforms, and clarify any platform-specific differences.
Consider adding a note or section for Linux/macOS users to ensure parity and clarity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation focuses exclusively on ASP.NET Core and .NET tooling, referencing only the 'launchSettings.json' file and environment variable configuration patterns typical of Windows development environments. There are no examples or guidance for setting environment variables or running the application in Linux or cross-platform scenarios, and the workflow assumes Visual Studio or similar Windows-centric tooling.

Recommendations:

Include instructions for setting environment variables on Linux/macOS (e.g., using 'export ASPNETCORE_ENVIRONMENT=Production' in the shell).
Show how to run the application from the command line in Linux/macOS environments, not just via 'dotnet run' with 'launchSettings.json'.
Mention that 'launchSettings.json' is primarily used by Visual Studio and may not apply in non-Windows or non-IDE scenarios.
Add a section or callout for cross-platform developers, clarifying how to configure and test environment-specific settings outside of Windows.
Provide equivalent bash/zsh shell commands alongside any Windows/Visual Studio-specific instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively provides .NET/C# code samples and instructions, which are platform-neutral at the code level but implicitly favor Windows environments by omitting any Linux-specific guidance, shell commands, or cross-platform considerations. All package installation examples use 'dotnet' CLI, which is available on Linux, but there are no explicit references to Linux environments, shell usage, or alternative patterns for Linux users. There is no mention of Powershell, but the documentation assumes a Windows-centric context by focusing on ASP.NET and .NET Core without acknowledging Linux deployment scenarios.

Recommendations:

Add explicit notes confirming that all instructions and code samples work on Linux as well as Windows.
Include Linux-specific examples, such as using bash/zsh to set environment variables (e.g., 'export AppConfigurationEndpoint=...') alongside Windows examples.
Mention Linux deployment scenarios (e.g., running .NET apps on Ubuntu, Docker containers, or Azure App Service for Linux) and provide links to relevant documentation.
Clarify that the 'dotnet' CLI commands are cross-platform and provide troubleshooting tips for common Linux issues (e.g., file permissions, environment variable case sensitivity).
Where environment variables are referenced, show both Windows (set) and Linux (export) syntax.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation demonstrates mild Windows bias by referencing Windows tools and patterns before Linux equivalents in several places. For example, when describing how to install redis-cli on Windows, the documentation recommends using WSL (Windows Subsystem for Linux) and Windows Terminal, and provides links to Windows-specific resources. Additionally, when discussing how to retrieve cache keys, Azure PowerShell is mentioned alongside Azure CLI, and PowerShell is referenced in both the main instructions and the related content section. Linux examples are present and accurate, but Windows-specific tooling and patterns are often mentioned first or with more detail.

Recommendations:

Provide Linux-native instructions and examples with equal prominence to Windows instructions.
When listing methods to retrieve cache keys, mention Azure CLI before Azure PowerShell, or present both together without preference.
Include explicit Linux and macOS terminal usage instructions, not just Windows/WSL.
Avoid framing Windows tools (WSL, Windows Terminal) as the default or preferred way to use redis-cli on Windows; mention cross-platform alternatives equally.
Ensure that references to PowerShell are balanced with Bash or other Linux shell equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias, primarily by listing Windows-centric tools such as Visual Studio before cross-platform or Linux-friendly alternatives, and by referencing Visual Studio (a Windows-first IDE) as the primary quickstart and deployment tool for C#. However, the documentation does provide parity for other languages and mentions cross-platform tools like Visual Studio Code and Azure CLI throughout. There are no PowerShell-heavy examples, and Linux is not excluded, but Windows tools are often mentioned first or more prominently.

Recommendations:

Ensure that cross-platform tools (Visual Studio Code, Azure CLI, Maven, etc.) are listed before or alongside Windows-specific tools like Visual Studio, especially in introductory and quickstart sections.
Explicitly mention Linux and macOS compatibility where applicable, particularly when referencing the 'command prompt' or CLI-based workflows.
For C# and other languages where Visual Studio is highlighted, provide equal visibility to Visual Studio Code and CLI-based workflows, including links to Linux/macOS instructions where available.
Avoid using 'command prompt' as a generic term; specify 'terminal' or 'shell' to be inclusive of Linux/macOS users.
Where PowerShell is referenced, ensure that Bash or other shell equivalents are also mentioned if possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates Windows bias primarily by referencing Windows-specific resources first, such as linking to the Windows Azure portal documentation for creating proximity placement groups (PPGs), without mentioning or providing equivalent Linux or cross-platform instructions. There are no examples or guidance for Linux users, nor are Linux tools or workflows referenced, despite SAP HANA being commonly deployed on Linux.

Recommendations:

Provide links to both Windows and Linux documentation for tasks like creating proximity placement groups, or use cross-platform documentation where possible.
Include explicit instructions or examples for Linux users, especially for common SAP HANA deployment scenarios.
Reference Linux tools, commands, or Azure CLI examples alongside or before Windows-specific tools to ensure parity.
Clarify that the guidance applies to both Windows and Linux environments, or specify any differences in workflow or requirements.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides both Linux and Windows instructions for mounting NFS volumes, with Linux instructions being more detailed and comprehensive. However, there are subtle biases: the Windows section refers to the Windows-specific 'Mount' command-line utility and links to Windows documentation, and the Windows mounting workflow requires first mounting the volume on a Unix/Linux VM and running chmod, which may not be intuitive for Windows-only administrators. The Linux section is more robust, but the Windows section is presented after the Linux section, and Windows-specific tools are mentioned without Linux equivalents in that context.

Recommendations:

Provide more context for Windows administrators who may not have access to a Linux/Unix VM for the chmod step, or suggest alternatives (such as configuring permissions at volume creation).
Include a brief explanation of the differences between Linux and Windows NFS client capabilities and limitations up front, so users can make informed decisions.
Where Windows-specific tools are mentioned (such as the 'Mount' utility), ensure Linux equivalents are also referenced in similar contexts for parity.
Consider adding troubleshooting or best practices sections for both platforms, not just Linux.
Clarify that the Linux mounting instructions are generally more flexible and supported, and highlight any limitations for Windows NFS clients in a summary table.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation displays a mild Windows bias. PowerShell examples and registration steps are presented before Azure CLI and REST API equivalents, and the registration workflow is described primarily using PowerShell commands. While Azure CLI and REST API instructions are present, PowerShell is often listed first or given more detail, which may disadvantage Linux users who typically use CLI or REST. There are no explicit Linux-specific examples or references to Linux tools or shell scripting patterns.

Recommendations:

Present Azure CLI examples before PowerShell, or at least in parallel, to reflect cross-platform usage.
Expand CLI instructions to match the detail and workflow coverage given to PowerShell.
Add explicit Linux shell (bash) usage notes or examples where relevant, especially for registration and querying steps.
Clarify that all CLI and REST API instructions are fully supported on Linux, and provide troubleshooting tips for common Linux environments.
Where screenshots or UI references are given, note any OS-specific behaviors or differences if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation describes deleting Azure NetApp Files volume replications and volumes primarily through GUI instructions and screenshots that reflect a Windows-style interface (right-click context menus, dialog confirmations). There are no CLI examples (such as Azure CLI, Bash, or PowerShell), nor are Linux-specific workflows or tools mentioned. The documentation implicitly assumes a Windows environment by referencing right-click actions and GUI navigation patterns common to Windows, without providing parity for Linux users who may use different interfaces or prefer command-line operations.

Recommendations:

Add Azure CLI and/or REST API examples for deleting replications and volumes, with step-by-step instructions.
Include screenshots or instructions for performing these actions via the Azure Portal on Linux (if any differences exist).
Explicitly mention that the operations can be performed from any OS via the Azure Portal, and clarify any OS-specific differences.
Provide PowerShell and Bash script examples for automation, ensuring both Windows and Linux users are supported.
Avoid language that assumes a Windows GUI (e.g., 'right-click') and offer equivalent steps for Linux users (e.g., contextual menu access via keyboard or alternative navigation).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page exhibits mild Windows bias by presenting the Azure PowerShell example for feature registration status before mentioning the Azure CLI alternative. The only explicit command example is for PowerShell, with the CLI option referenced parenthetically. There are no Linux-specific examples, tools, or patterns shown, though Linux is referenced in a performance benchmarking link. No Windows-only tools or patterns are otherwise discussed.

Recommendations:

Provide both Azure PowerShell and Azure CLI command examples side-by-side, or present CLI first to improve parity for Linux users.
Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS environments.
Include Linux-specific operational examples or troubleshooting steps where relevant.
Ensure that any scripts or automation guidance are available in Bash/CLI as well as PowerShell.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides a balanced overview of features for both Windows (SMB/Active Directory) and Linux (NFS/LDAP) environments. However, there is a subtle Windows bias in some areas: Windows/SMB/Active Directory features and terminology (e.g., Windows File Explorer, NTFS, Windows client, FSLogix, Citrix, Azure VMware Solution) are sometimes mentioned first or in more detail, and Windows-centric tools and workflows (e.g., SMB Continuous Availability, Access-based Enumeration, non-browsable shares) are described with explicit references to Windows clients. Linux/NFS features are present and described, but Windows/SMB scenarios are often foregrounded, especially in features related to user access, security, and integration with enterprise environments.

Recommendations:

When describing features that apply to both SMB (Windows) and NFS (Linux), ensure that Linux/NFS examples, terminology, and client perspectives are presented with equal prominence and detail.
Where Windows tools or workflows (e.g., Windows File Explorer, NTFS, FSLogix) are mentioned, provide equivalent Linux tools or workflows (e.g., Linux file managers, POSIX permissions, Linux VDI solutions) and describe their usage.
Avoid phrases like 'the Windows client hides the folder...' without also mentioning the behavior on Linux/NFS clients, or clarify if the feature is Windows-only.
For features like Access-based Enumeration and non-browsable shares, explicitly state their applicability (or lack thereof) to NFS/Linux clients, and provide Linux/NFS-specific guidance where possible.
Review the order of protocol mentions (e.g., 'SMB, NFSv4.1, and dual-protocol') and alternate the order or use 'NFS/SMB' where appropriate to avoid always foregrounding Windows/SMB.
Where integration with enterprise identity solutions is discussed, ensure parity in coverage between Active Directory (Windows) and LDAP/Unix identity management solutions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias, primarily through the use of Windows-specific tooling and commands (e.g., 'Set-Tools-Repo' for VMware Tools updates) without providing equivalent Linux guidance or examples. There are references to 'VMware Tools for Windows' and remediation steps that assume a Windows environment, but no mention of Linux guest remediation or Linux-specific commands. No PowerShell-heavy scripting or Windows-first ordering is observed; however, Linux parity is lacking in the examples and instructions.

Recommendations:

Where remediation steps involve guest OS actions (such as updating VMware Tools), provide instructions or references for both Windows and Linux guests.
If using Azure VMware Solution Run commands that are Windows-centric, clarify if/how Linux guests are supported, and provide Linux command equivalents if available.
Explicitly mention whether vulnerabilities or updates affect both Windows and Linux guests, and detail steps for each where applicable.
Review all examples and workarounds to ensure Linux users are not excluded and have clear guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page exhibits mild Windows bias. The only explicit OS-specific section is 'Install the VM agent', where Windows instructions (MSI installer, file path, executable name) are listed first and in more detail, while Linux instructions are more generic and less step-by-step. The initial VM creation link points to a Windows VM guide, not a Linux one. There are no PowerShell or CLI examples, but Windows-specific tools and patterns are mentioned before Linux equivalents.

Recommendations:

Provide equal, step-by-step instructions for installing/updating the Linux agent, including example commands for RPM/DEB installation.
Add a link to the Linux VM creation quickstart alongside the Windows VM creation link.
Ensure that screenshots and examples are OS-neutral or provide both Windows and Linux variants where relevant.
Mention Linux agent version verification steps, similar to the Windows agent verification.
Review all sections for implicit prioritization of Windows tools and rephrase to treat Windows and Linux equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily through its exclusive use of Azure Portal screenshots and step-by-step instructions, which implicitly assume a graphical, Windows-centric workflow. All code examples are provided only for C# (.NET) and JavaScript SDKs, with no CLI, Bash, or Linux-native tooling shown. There are no references to Linux command-line tools, nor are there instructions for provisioning or sending SMS via cross-platform or Linux-friendly methods (such as Azure CLI, REST API via curl, or PowerShell alternatives for Linux). The developer experience and tutorials focus on GUI and SDKs typical for Windows environments, omitting Linux-specific guidance.

Recommendations:

Add examples using Azure CLI and REST API (e.g., curl) for provisioning and sending SMS, which are platform-agnostic and widely used on Linux.
Include screenshots or instructions for accessing Messaging Connect via the Azure Portal on Linux (e.g., using a browser on Ubuntu) or mention that the portal is accessible from any OS.
Provide Bash and PowerShell (cross-platform) scripts for common tasks, such as authentication and sending SMS, to ensure parity for Linux users.
Explicitly state that all features and workflows are supported on Linux and macOS, not just Windows, and link to relevant cross-platform SDK documentation.
Add troubleshooting and setup notes for Linux environments, such as installing SDKs or dependencies on Ubuntu, Fedora, etc.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation consistently references Visual Studio Code and Azure Functions workflows, which are cross-platform, but all instructions and linked quickstarts are tailored to Visual Studio Code usage patterns. There is no mention of Linux-specific command-line workflows, nor are there examples for running or deploying the function outside of Visual Studio Code. The documentation implicitly assumes the user is using Visual Studio Code, which, while available on Linux, is not the default editor for many Linux users. There is also no mention of alternative editors, terminal-based workflows, or Linux-specific deployment/testing instructions.

Recommendations:

Add explicit instructions for setting up and running the function using command-line tools (e.g., Azure Functions Core Tools, npm, and the Azure CLI) on Linux.
Include examples for deploying and running the function using only the terminal, without relying on Visual Studio Code.
Mention and provide links to Linux-specific documentation or quickstarts for Azure Functions.
Clarify that Visual Studio Code is optional and that all steps can be performed on Linux using alternative editors and terminal commands.
Provide troubleshooting tips or notes for common Linux environments (e.g., Ubuntu, Fedora) where paths, permissions, or dependencies may differ.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes the transfer process using the Azure portal web interface, with screenshots and instructions that implicitly assume a Windows-centric experience. There are no examples or mentions of Linux-specific tools, command-line interfaces (such as Azure CLI), or cross-platform automation options. All instructions and troubleshooting steps focus on GUI navigation, which is most commonly associated with Windows environments, and there is no guidance for users who may prefer or require Linux-native workflows.

Recommendations:

Add equivalent instructions for performing subscription transfers using Azure CLI, which is cross-platform and widely used on Linux.
Include examples or references for automating the transfer process via PowerShell and Bash, highlighting parity between Windows and Linux scripting environments.
Mention that the Azure portal is accessible from any modern browser on Linux, and clarify that the process is not limited to Windows users.
Provide troubleshooting steps and next actions that include CLI commands, not just portal navigation.
Ensure that screenshots and instructions do not implicitly assume a Windows environment (e.g., avoid Windows-specific UI elements or terminology).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively uses the Azure portal (a web GUI) for all management tasks and does not provide any command-line examples, such as Azure CLI or PowerShell. While this avoids explicit Windows/Powershell bias, it implicitly favors Windows users by omitting Linux-friendly CLI instructions. There is no mention of Linux tools, shell commands, or cross-platform automation patterns, and the only tool referenced is the Azure portal, which is most commonly used by Windows users. There are no examples for Azure CLI, which is widely used on Linux and macOS.

Recommendations:

Add Azure CLI examples for all major operations (moving, viewing, deleting, tagging discount resources), as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that all operations can be performed via Azure CLI and provide links to relevant CLI documentation.
If PowerShell is referenced in related documentation, ensure Azure CLI equivalents are provided and shown before or alongside PowerShell examples.
Include notes or sections for automation and scripting approaches suitable for Linux environments.
Clarify that the Azure portal is accessible from any OS, but provide parity for users who prefer command-line or automated workflows.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page exhibits a 'windows_first' bias by listing .NET and ASP.NET Core (Windows-centric frameworks) and their samples before other cross-platform or Linux-native technologies. The table of configuration provider libraries leads with Microsoft/.NET providers, and the feature matrix columns are ordered with .NET first, followed by Java Spring, Kubernetes, and then other languages. However, there are no explicit Windows-only tools, PowerShell examples, or missing Linux examples; the bias is primarily in ordering and emphasis.

Recommendations:

Reorder the provider libraries table to alternate or group by platform type (e.g., .NET, Java, Python, JavaScript, Go) or by popularity, rather than always leading with .NET/Windows-centric frameworks.
In the feature matrix, consider rotating the order of columns or providing a note that the order does not imply priority or platform preference.
Explicitly mention cross-platform compatibility for each provider, especially for .NET Standard and .NET Core, to clarify that they are not Windows-only.
If possible, add Linux-specific or cross-platform usage notes or examples where relevant, to reinforce parity.
Ensure that documentation samples and links are balanced across platforms and not predominantly .NET/Windows.

Create pull request

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