Scan Details - Linux-first Docs for Azure

163

Pages Scanned

57

Pages Flagged

163

Changed Pages

35.0%

% Pages Flagged

Live Progress

🔴 Connecting...

0%

Phase: discovery

Processing: Initializing...

Activity Feed

00:00:06 Scan started

Scan Information

Started At: 2025-08-16 00:00:06

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

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. All migration tools and examples focus exclusively on migrating from Windows environments, specifically IIS servers, and use Windows-specific tools such as the App Service Migration Assistant (MSI installer) and PowerShell scripts. There is no mention of Linux-based hosting environments (e.g., Apache, Nginx), nor are there examples or tools for migrating .NET apps from Linux servers. The documentation also refers to Windows containers and does not provide parity for Linux containers or Linux-based migration scenarios.

Recommendations:

Include migration guidance and tools for .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel).
Provide Linux shell (bash) script examples alongside PowerShell scripts for discovery and migration.
Mention and document migration paths for .NET Core/ASP.NET Core apps running on Linux.
Add references to Linux-compatible tools or clarify if current tools are Windows-only.
Ensure that documentation tables and tool descriptions explicitly state platform support and offer alternatives for Linux users.
Highlight containerization options for both Windows and Linux containers, not just Windows Containers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific configuration files (web.config), mentioning Windows-native tools (iisnode) for Node.js apps, and omitting equivalent Linux-native examples or tools. While there is a brief mention of running on Linux with PM2, the overall guidance and examples prioritize Windows patterns and tools, with Linux alternatives either missing or mentioned secondarily.

Recommendations:

Provide Linux-native configuration examples alongside or before Windows-specific ones (e.g., show how to configure auto-healing or memory limits for Linux-based App Service plans, not just via web.config).
Include Linux-native process managers and configuration files (e.g., systemd, supervisord, or PM2 ecosystem files) when discussing Node.js app hosting, not just iisnode.
When referencing tools or settings (like iisnode or web.config), explicitly note their applicability (Windows-only) and provide equivalent Linux guidance.
Ensure that troubleshooting and best practices sections include parity for both Windows and Linux App Service environments, with clear, side-by-side examples where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by listing Windows-related commands and tools (such as Azure PowerShell) after Azure CLI, but still giving them prominent, separate sections. The use of PowerShell is highlighted, and the documentation refers to the Azure portal UI, which is more familiar to Windows users. There are no explicit Linux shell or scripting examples beyond the Azure CLI, and no mention of Linux-native tools or patterns. While Linux is acknowledged (e.g., Linux SKU availability), practical Linux-specific automation or scripting guidance is missing.

Recommendations:

Add explicit Linux shell (bash) scripting examples alongside PowerShell, especially for automation tasks.
Clarify that Azure CLI commands work cross-platform and can be used in Linux/macOS environments.
Include references to Linux-native tools or scripting environments where appropriate.
Ensure that any UI instructions are platform-neutral or clarify parity for Linux users.
Consider providing a table or side-by-side examples for both PowerShell and bash where scripting is discussed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows evidence of Windows bias. Windows is mentioned first in SKU availability, and Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, despite CLI being more cross-platform. There are no Linux shell (bash) or scripting examples, and the use of PowerShell is not contextualized for Linux users. Portal instructions and screenshots do not clarify differences for Linux vs. Windows app deployments. The documentation also refers to 'Development tools' and 'Clone app' features without noting any OS-specific differences or limitations.

Recommendations:

Present Linux and Windows instructions/examples in parallel, or alternate which comes first.
Provide bash shell scripting examples alongside PowerShell for automation, especially for Linux users.
Clarify any OS-specific differences in portal workflows, screenshots, or feature availability.
Explicitly mention if PowerShell commands are cross-platform or provide alternatives for Linux/macOS.
Ensure all automation and scripting sections include both Azure CLI and native Linux shell (bash/zsh) usage where applicable.
Highlight any limitations or differences for Linux users in 'Development tools' or 'Clone app' features.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. Windows instructions, tools, and troubleshooting steps are often presented first or exclusively, with more detailed guidance and screenshots for Windows users. PowerShell is used as the default for network testing, and Windows-specific tools (such as the Hybrid Connection Manager GUI) are emphasized, while Linux alternatives are less detailed or missing. Some troubleshooting steps and examples are only provided for Windows, and GUI-based workflows are not available for Linux users.

Recommendations:

Provide Linux command-line equivalents for all PowerShell examples (e.g., use 'nc' or 'telnet' for network testing instead of only 'Test-NetConnection').
When presenting instructions, alternate the order or present Linux and Windows instructions side by side, rather than always listing Windows first.
Expand Linux installation and usage instructions to match the detail and clarity of the Windows sections, including more screenshots or terminal output where possible.
Offer Linux-specific troubleshooting steps, including commands for checking service status, network connectivity, and DNS resolution.
Clarify any feature gaps (such as the absence of a Linux GUI) and suggest alternative workflows or third-party tools for Linux users.
Ensure that all programmatic and CLI examples are explicitly cross-platform and tested on both Windows and Linux.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias primarily in the 'Scenario 2: Site is an Azure Traffic Manager "nested" or "external" endpoint' section, where only a PowerShell script is provided for identifying impacted Traffic Manager profiles. There are no equivalent Bash, Azure CLI, or cross-platform script examples for Linux or macOS users. The instructions for running the script assume a Windows/PowerShell environment, and there is no mention of Linux-compatible alternatives or guidance for non-Windows users.

Recommendations:

Provide equivalent Bash or Azure CLI scripts for Linux/macOS users to identify impacted Traffic Manager profiles.
When referencing scripts or tools, offer both PowerShell and cross-platform (Bash/CLI) alternatives, or clearly indicate if a solution is Windows-only.
Explicitly mention cross-platform compatibility or provide guidance for running PowerShell scripts on Linux/macOS (e.g., using PowerShell Core).
Review all example commands and ensure parity between Windows and Linux environments, especially for common administrative tasks.
Consider adding a table or section summarizing available tools/scripts for each platform to help users quickly find relevant instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation focuses exclusively on discovering ASP.NET web apps hosted on IIS web servers within VMware environments, which are Windows-centric technologies. There is no mention of Linux-based hosting environments (such as Kestrel, Apache, or Nginx), nor are there examples or guidance for discovering .NET apps running on Linux servers. All discovery capabilities and resources are described in the context of Windows tools and patterns.

Recommendations:

Include information on discovering .NET web apps hosted on Linux servers, such as those running Kestrel, Apache, or Nginx.
Provide parallel examples or workflows for Linux-based environments, including any differences in appliance setup or discovery processes.
Mention whether Azure Migrate supports Linux-hosted .NET apps and, if so, provide links or references to relevant documentation.
Clarify in the introduction that the current guidance is Windows/IIS-specific, and direct Linux users to appropriate resources if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

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

Recommendations:

Add a parallel section or separate guide for Node.js on Azure App Service Linux, covering best practices, configuration, and troubleshooting.
Provide Linux-specific examples for profiling, debugging, and monitoring (e.g., using pm2, systemd, Linux file paths, and logs).
Reference Linux equivalents for configuration (e.g., environment variables, process managers) and troubleshooting (e.g., using SSH, Linux shell, log locations).
Avoid assuming the presence of Windows-only tools (like iisnode, web.config, Win32 error codes) and instead offer cross-platform or Linux-native alternatives.
When presenting examples or recommendations, either provide both Windows and Linux versions or clearly indicate which platform each applies to, with links to the other.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by referencing the Windows file path (C:\home\site\wwwroot) as the default location for the configuration file, and only later mentioning the Linux equivalent. The example path is Windows-specific, and there is no explicit Linux example or screenshot. Additionally, the instructions and examples focus on Windows conventions and tools, with Linux-specific requirements (absolute paths) only mentioned as a note, rather than being presented equally in the main instructions.

Recommendations:

Present both Windows and Linux file paths side-by-side in all relevant instructions and examples (e.g., 'C:\home\site\wwwroot\auth.json' for Windows and '/home/site/wwwroot/auth.json' for Linux).
Include explicit Linux examples and screenshots where applicable.
Avoid using Windows paths as the default or only example; instead, provide both or use a platform-agnostic placeholder.
Clarify platform-specific requirements (such as absolute vs. relative paths) in the main instruction steps, not just in notes.
Where tools or commands are referenced, ensure Linux equivalents are provided or mentioned equally.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a bias towards Windows environments by providing only C# code examples (which are most commonly used on Windows), referencing the Microsoft.IdentityModel.Tokens NuGet package, and not mentioning or providing examples for Linux or cross-platform tools/languages (such as OpenSSL, Python, or Node.js) for generating JWTs. There are no CLI or scripting examples for Linux/macOS users, and the documentation assumes a Windows/.NET development environment.

Recommendations:

Add examples for generating and signing the JWT client secret using cross-platform tools such as OpenSSL, Python (e.g., PyJWT), or Node.js (e.g., jsonwebtoken).
Provide command-line instructions for Linux/macOS users, such as using OpenSSL to handle the .p8 key and generate signatures.
Mention and link to cross-platform libraries and tools for JWT creation, not just .NET/NuGet packages.
Include a note clarifying that the process can be completed on any OS, and provide parity in examples for both Windows and Linux/macOS environments.
If referencing application settings or file editing, mention relevant editors and commands for Linux/macOS as well as Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by referencing Azure Storage Explorer with a Windows-specific tab in the SAS generation link and not providing equivalent Linux-native tooling or CLI examples for file upload and SAS generation. There are no explicit Linux or cross-platform instructions for uploading files or generating SAS tokens, and the only GUI tool mentioned is typically associated with Windows environments.

Recommendations:

Provide explicit CLI-based instructions (using az storage blob upload and az storage blob generate-sas) for uploading files and generating SAS tokens, which work cross-platform.
Mention and link to Linux/macOS versions of Azure Storage Explorer, or clarify its cross-platform availability.
Avoid linking to documentation with Windows-specific tabs by default; either use a neutral tab or include both Windows and Linux/macOS instructions.
Consider including examples using common Linux tools (e.g., curl, azcopy) for file upload and SAS generation.
Add a note or section highlighting cross-platform compatibility and alternative tools for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based deployment and configuration patterns for ASP.NET apps. Examples and instructions reference Windows tools (such as Visual Studio, Kudu, CMD, and PowerShell) and Windows file paths, with no equivalent Linux or cross-platform guidance. There are no Linux-specific examples or mentions of how these tasks would differ or be accomplished on Linux-based App Service plans.

Recommendations:

Add explicit guidance and examples for configuring and deploying ASP.NET apps on Linux-based App Service plans, including relevant command-line examples and file paths.
When showing how to inspect .NET Framework versions, include Linux equivalents or clarify that these steps are Windows-only, and provide Linux alternatives if available.
Balance references to Windows tools (Visual Studio, Kudu, CMD, PowerShell) with Linux-friendly alternatives (such as VS Code, Bash, SSH, or Linux-based Kudu/console).
Clearly indicate when a step or feature is only available on Windows App Service, and provide links or notes for Linux users.
Consider reordering or parallelizing instructions so that Linux and Windows approaches are presented side-by-side, rather than Windows-first or Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Linux and Windows instructions for configuring data sources in Tomcat and JBoss on Azure App Service. However, in the Tomcat server-level configuration section, the Windows instructions are more detailed and prominent, with a heavy reliance on PowerShell scripts and Windows-specific tools and environment variables. The Windows approach is described with step-by-step PowerShell scripting, while the Linux approach uses shell scripts and standard Linux tools, but with less detail and explanation. Additionally, Windows-specific patterns (such as copying Tomcat to a local directory and using %LOCAL_EXPANDED%) are described at length, and PowerShell is the default scripting language for Windows, with no mention of alternatives.

Recommendations:

Ensure that Linux and Windows instructions are presented with equal detail and clarity, including step-by-step explanations and troubleshooting tips for both platforms.
Provide equivalent Linux shell script examples wherever PowerShell scripts are shown for Windows, and vice versa.
Avoid presenting Windows instructions or tools (such as PowerShell) before Linux equivalents unless there is a clear reason; consider parallel presentation or Linux-first ordering if usage data supports it.
Highlight cross-platform tools and approaches (e.g., Azure CLI, bash scripts, or platform-agnostic configuration methods) where possible.
Explicitly mention any differences in capabilities or limitations between Windows and Linux, so users can make informed decisions.
Include links to Linux and Windows documentation in all relevant sections to ensure discoverability.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias: Windows-specific instructions, code samples, and certificate store usage are presented before Linux equivalents. Most code examples (C#, Java) focus on Windows certificate stores, with Linux guidance often deferred or less detailed. There are references to Windows tools and patterns (e.g., certificate store, environment variables, .NET Framework specifics) without equivalent Linux or cross-platform alternatives. Non-Windows languages (Node.js, PHP, Python) are not given direct examples, and Linux-specific instructions are less prominent or detailed.

Recommendations:

Provide Linux examples alongside Windows examples, not after them or as an afterthought.
Include code samples for loading certificates in popular Linux languages (Node.js, Python, PHP, Java) directly in the documentation.
Present Linux and Windows instructions in parallel sections or tabs, ensuring parity in detail and clarity.
Avoid referencing Windows certificate store patterns exclusively; explain Linux certificate handling (e.g., file-based, OpenSSL, environment variables) with equal depth.
When mentioning environment variables or file paths, always provide both Windows and Linux equivalents together.
Ensure that all steps (such as making certificates accessible, loading them in code, and updating/renewing) have explicit Linux instructions, not just references to 'see respective language documentation.'

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation exhibits a moderate Windows bias. While it does provide some cross-platform guidance (notably OpenSSL for certificate export), it frequently references Windows-specific tools (IIS, Certreq.exe), and in automation examples, PowerShell is given equal or more prominence than Linux-native alternatives. There is a lack of explicit Linux or macOS-specific instructions for common certificate management tasks, and Windows tooling is mentioned before or instead of Linux equivalents.

Recommendations:

For every mention of Windows tools (IIS, Certreq.exe), provide equivalent Linux/macOS instructions (e.g., using OpenSSL, certbot, or native Linux commands) and reference them with equal prominence.
In automation sections, always provide both Azure CLI and Azure PowerShell examples, and consider listing Azure CLI (which is cross-platform) first.
Where screenshots or UI steps are shown, clarify if there are OS-specific differences, or note that the steps are OS-agnostic.
Add explicit guidance for Linux and macOS users for certificate generation, export, and upload, including common command-line workflows.
In FAQ and troubleshooting, address Linux-specific scenarios (e.g., trusted root store management in Linux containers) where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on deploying Windows containers, with all examples, variables, and instructions referencing Windows-specific images, pools, and App Service types. There are no examples or guidance for deploying Linux containers, and the use of 'windows-latest' as the default agent pool and 'webAppHyperVContainer' as the app type further reinforce a Windows-centric approach. Linux equivalents and cross-platform options are not mentioned or demonstrated.

Recommendations:

Add parallel examples and instructions for deploying Linux containers, including YAML snippets using 'ubuntu-latest' as the vmImage and 'webAppLinux' as the appType.
Explicitly mention that Azure App Service supports both Windows and Linux containers, and provide guidance for choosing between them.
Include a section or callout explaining differences in deployment steps, variables, and supported features between Windows and Linux container deployments.
Ensure that all variable and task names are platform-agnostic or provide both Windows and Linux variants.
Consider restructuring the documentation to present both Windows and Linux options side-by-side, or provide a platform selection at the beginning.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by consistently presenting Windows-centric tools and workflows, such as PowerShell and WinSCP, and by providing PowerShell examples alongside Azure CLI, but not Linux shell or SFTP examples. Windows tools (e.g., Visual Studio, WinSCP) are mentioned before or instead of cross-platform or Linux-native alternatives. There are no explicit Linux shell command examples or references to Linux FTP clients, and the documentation does not address Linux-specific usage patterns.

Recommendations:

Add Linux shell command examples (e.g., using lftp, curl, or ftp) for connecting and deploying via FTP/S.
Include Linux-native FTP/S clients (e.g., FileZilla, lftp, gFTP) alongside or before Windows tools like WinSCP and Visual Studio.
Provide bash or shell script equivalents for PowerShell commands, especially for extracting FTP/S endpoints from Azure CLI output.
Ensure that cross-platform tools and instructions are presented before or alongside Windows-specific tools.
Mention SFTP (if supported) or clarify its status for Linux users, as it is a common secure file transfer method on Linux.
Explicitly state that the instructions apply to both Windows and Linux, and highlight any OS-specific differences or considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific UI actions (e.g., 'Right click', 'click Save'), using tooling and patterns familiar to Windows users (such as SQL Server Management Studio paradigms and ADO.NET connection strings), and omitting explicit Linux or cross-platform command-line instructions. There are no Linux-specific examples, terminal commands, or guidance for users developing or deploying from Linux environments. The documentation assumes a GUI-based workflow and does not mention or show parity for Linux users, despite the 'linux-related-content' tag.

Recommendations:

Include Linux-specific or cross-platform instructions for all steps, such as using the dotnet CLI, VS Code, or command-line editors instead of GUI actions like 'Right click'.
Provide examples for connecting to Azure SQL from Linux environments, including using the Azure CLI, sqlcmd, or Data Studio on Linux.
When referencing connection strings or authentication, clarify how to obtain and use these on Linux (e.g., environment variables, .NET user secrets, or Key Vault integration).
Add explicit Linux terminal commands for package installation, file creation, and deployment steps.
Avoid Windows-centric language (e.g., 'click Save') or provide alternative instructions for Linux users.
Highlight any cross-platform tools (like Azure Data Studio or VS Code) and show their usage on Linux.
If using code snippets that assume Windows file paths or conventions, provide Linux equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a Windows-first bias by referencing Windows directory paths (e.g., D:\home\site\wwwroot) before Linux equivalents, using Windows-style path separators, and omitting explicit Linux/Bash command examples. The instructions and troubleshooting sections focus on Windows directory structures and do not provide Linux-specific guidance or parity in examples.

Recommendations:

Provide Linux directory paths (e.g., /home/site/wwwroot) alongside Windows paths in all relevant sections, and ensure Linux paths are mentioned first or equally.
Include explicit Linux/Bash command examples where appropriate, especially for file operations or manual deployment steps.
Clarify when instructions or behaviors differ between Windows and Linux App Service plans, and provide platform-specific notes as needed.
Use platform-neutral language and path separators (e.g., <project-root>/app_data/jobs/...) or provide both Windows and Linux variants.
Add troubleshooting steps and examples that address Linux-specific scenarios, such as file permissions or directory structures.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples for configuring Traffic Manager and App Service Environments. There are no equivalent examples using Azure CLI, Bash, or ARM templates, which are more commonly used in Linux or cross-platform environments. The reliance on PowerShell commands and references to PowerShell-based tooling may alienate users working on Linux or macOS, or those who prefer command-line tools that are natively cross-platform.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell scripts shown, ensuring Linux and macOS users can follow along without needing PowerShell.
Include Bash shell command examples where appropriate, especially for DNS lookups or domain configuration steps.
Reference ARM/Bicep templates or Terraform for infrastructure-as-code alternatives that are platform-agnostic.
Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide links to relevant cross-platform tooling.
Reorder or parallelize example sections so that non-Windows approaches are presented alongside or before Windows-specific tooling.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias, especially in the .NET and Python sections. Windows tools (Visual Studio, Azure PowerShell) are listed before or more prominently than Linux equivalents. There are more detailed or explicit references to Windows-based development environments and tools, while Linux or cross-platform options are less emphasized or sometimes missing. The 'Next step' call-to-action also defaults to an ASP.NET (Windows-centric) workflow.

Recommendations:

Ensure Linux and cross-platform tools (e.g., VS Code, CLI, Azure CLI) are listed before or alongside Windows-specific tools in all language stacks.
Provide explicit Linux examples and links for all stacks, especially for .NET and Python, where Windows tools and environments are currently prioritized.
Balance references to Windows tools (e.g., Visual Studio, PowerShell) with equivalent Linux tools (e.g., VS Code, Azure CLI, Bash).
For 'Next step' actions, offer a choice of stack or highlight a cross-platform/language-neutral workflow instead of defaulting to ASP.NET.
Audit all quickstart and tutorial links to ensure Linux instructions are present and as detailed as Windows instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides cross-platform deployment examples for most stacks (ASP.NET Core, Java, Tomcat, Node.js, Python) using Ubuntu runners, but the ASP.NET (classic) example exclusively uses a Windows runner and Windows-specific tools (NuGet, MSBuild) without offering a Linux alternative or mentioning cross-platform options. This prioritizes Windows for ASP.NET scenarios and omits Linux parity for that stack.

Recommendations:

Add a Linux-based example for ASP.NET (classic) deployment, using Mono or .NET SDK for cross-platform builds if possible.
Explicitly mention when a workflow requires Windows-only tools (e.g., MSBuild for full .NET Framework) and provide guidance or links for Linux alternatives or limitations.
Where possible, provide both Windows and Linux workflow examples side-by-side for stacks that can be built on both platforms.
Clarify in the ASP.NET section why Windows is required (if so), and suggest migration paths to .NET Core/5+ for better cross-platform support.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows/Visual Studio tooling and workflows, such as right-clicking in Solution Explorer and using the NuGet package manager in Visual Studio, without providing equivalent Linux or cross-platform instructions. There are no explicit Linux command-line examples or references to Linux-native editors or workflows. The only CLI reference is to the .NET CLI for NuGet, but it is secondary to the Visual Studio/Windows-first approach.

Recommendations:

Provide explicit Linux and cross-platform instructions for file creation and editing, such as using the 'dotnet new page' command or editing files with VS Code, nano, or vim.
List CLI-based package installation (dotnet CLI) before or alongside Visual Studio/NuGet Package Manager instructions, and clarify that both work on Windows, Linux, and macOS.
Include screenshots or terminal commands for Linux environments where relevant, such as setting environment variables or deploying to App Service from a Linux shell.
Avoid instructions that assume a GUI file explorer (e.g., 'Right-click the Pages folder') and instead offer command-line alternatives.
Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and provide parity in examples and tooling references.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page discusses assessing .NET web apps for migration to Azure App Service but implicitly assumes a Windows environment by referencing ASP.NET (commonly associated with Windows/IIS) and does not mention Linux-based .NET app scenarios or provide Linux-specific guidance or examples. There are no references to Linux tools, patterns, or cross-platform considerations, and all linked resources appear to focus on traditional Windows-based ASP.NET applications.

Recommendations:

Explicitly mention support for .NET Core/.NET 5+ web apps running on Linux, and clarify if the assessment process applies equally to Linux-hosted apps.
Include examples or references for assessing .NET apps deployed on Linux (e.g., using Kestrel, Nginx, Apache).
Add documentation links or sections addressing migration and assessment of Linux-hosted .NET web apps.
Clarify any differences in assessment or migration steps between Windows and Linux environments.
Ensure parity in tool recommendations and instructions for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides a single example for clearing the DNS cache, specifically referencing the Windows command 'ipconfig /flushdns', without mentioning equivalent commands for Linux or macOS. No PowerShell scripts or Windows-specific tools are otherwise present, but the troubleshooting section assumes a Windows environment by default.

Recommendations:

When mentioning clearing the DNS cache, include equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
Review all troubleshooting steps and ensure that platform-agnostic or cross-platform guidance is provided wherever possible.
If automation or scripting is discussed, provide both PowerShell (Windows) and Bash (Linux/macOS) examples.
Explicitly state when a step or tool is platform-specific, and offer alternatives for other platforms.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides only Azure CLI and Azure Portal instructions, with no mention of platform-specific command-line environments (such as PowerShell or Bash). However, there is a subtle Windows bias in that all instructions and examples assume use of the Azure CLI, which is cross-platform but often associated with Windows environments, and there is no explicit mention of Linux or Bash-specific workflows. There are no examples or guidance for Linux users regarding environment variables, file paths, or shell commands, and no mention of using Bash or Linux-native tools. The documentation also refers to the Azure Portal UI, which is platform-agnostic, but omits any Linux-specific considerations or examples.

Recommendations:

Add explicit Bash shell examples for Linux users, especially for commands involving file creation, editing, and environment variable management.
Include notes or examples for setting environment variables in both Windows (set/PowerShell) and Linux (export/Bash) environments.
Clarify that the Azure CLI commands work cross-platform and provide any Linux-specific installation or usage notes where relevant.
Where file paths or file operations are mentioned (e.g., creating authsettings.json), provide both Windows and Linux command-line examples (e.g., using echo/cat/touch).
If referencing the Azure CLI, briefly mention that it is available on Windows, Linux, and macOS, and link to platform-specific installation guides.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page presents Windows container SSH access first and describes it as requiring no modifications, while Linux custom containers require additional steps and configuration. The Windows section lacks command-line or PowerShell examples, but the Linux section provides detailed Azure CLI and SSH command-line instructions. There are no PowerShell or Windows CLI examples for Windows containers, and the Linux section is more comprehensive in terms of actionable steps. However, the ordering and initial focus on Windows, as well as the lack of parity in example depth, indicate a mild 'windows_first' and 'missing_linux_example' bias.

Recommendations:

Provide equivalent command-line or PowerShell instructions for connecting to Windows containers, if supported, or clearly state the limitations.
Ensure that both Windows and Linux sections have similar depth and actionable steps, or explain why certain features are only available on one platform.
Consider presenting Linux and Windows instructions in parallel or in a more balanced order to avoid the perception of platform preference.
If browser-based SSH is the only option for Windows containers, explicitly state this and provide troubleshooting or advanced usage tips similar to those given for Linux.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides step-by-step instructions for integrating an ILB App Service Environment with Azure Application Gateway, but it exhibits subtle Windows bias. Specifically, when validating DNS resolution, the only example shown is from a 'command prompt', which implies Windows usage. There are no explicit Linux or cross-platform CLI examples (e.g., using dig or nslookup on Linux/macOS), and no mention of Linux tools or terminal usage. The documentation also references the Azure portal and GUI workflows exclusively, which are platform-agnostic but may implicitly favor Windows users who are more accustomed to GUI-based workflows.

Recommendations:

Include explicit Linux/macOS command-line examples for DNS validation (e.g., show both Windows 'nslookup' and Linux 'dig' or 'nslookup' commands).
When referencing 'command prompt', clarify that the steps apply to both Windows Command Prompt and Linux/macOS terminal, or provide parallel instructions.
Add Azure CLI or PowerShell command examples for key steps (where possible), and ensure both Windows and Linux CLI usage is covered.
Use neutral language such as 'terminal' or 'shell' instead of 'command prompt' to avoid implying a Windows-only environment.
Consider including a section or callout for Linux users, highlighting any differences or additional steps relevant to non-Windows platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation references both Windows and Linux support in App Service Environment, but provides detailed example calculations and operational notes only for Windows Containers. There are no equivalent examples or subnet sizing guidance for Linux Containers. Additionally, Windows-specific SKUs and behaviors are mentioned first or exclusively in several places, while Linux equivalents are not discussed.

Recommendations:

Add equivalent example calculations and subnet sizing guidance for Linux Containers, including any differences in IP address usage or scaling behavior.
When mentioning Windows-specific SKUs or behaviors (e.g., I1v2 Windows), also mention Linux SKUs or note if there are no differences.
Provide parity in operational notes and caveats for both Windows and Linux container scenarios.
Ensure that any platform-specific requirements or exceptions are clearly labeled as such, and that Linux users are not left to infer their requirements from Windows examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides deployment examples for multiple languages and frameworks, with most workflows running on Ubuntu (Linux) runners. However, the ASP.NET (classic) example is the only one that uses a Windows runner and Windows-specific tools (NuGet, MSBuild), and it is presented before the Java, Node.js, and Python examples, which all use Linux runners. There is no Linux-based alternative provided for ASP.NET, and the documentation does not clarify that ASP.NET Core can be built and deployed cross-platform, while classic ASP.NET is Windows-only.

Recommendations:

Explicitly state that classic ASP.NET requires Windows runners due to framework limitations, and clarify that ASP.NET Core is cross-platform.
If possible, provide guidance or links for porting classic ASP.NET apps to .NET Core to enable Linux-based CI/CD.
Consider reordering the examples or grouping them by platform requirements, so that Linux-first examples are not visually deprioritized.
For each example, add a note on why a particular runner (windows-latest or ubuntu-latest) is used, making platform dependencies explicit.
Where Windows-specific tools are used (NuGet, MSBuild), clarify their necessity and provide Linux alternatives or explanations if none exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias by referencing Windows first in the sample app quickstart link (with 'tabs=flask,windows,azure-cli,...') and not providing explicit Linux-specific or cross-platform deployment instructions. There are no PowerShell-specific commands or Windows-only tools, but the absence of Linux/macOS terminal examples or explicit parity in setup steps may disadvantage Linux users.

Recommendations:

Ensure that all quickstart and setup links include Linux/macOS tabs or examples alongside Windows, or default to cross-platform instructions.
Explicitly mention that all CLI commands (such as 'pip install', environment variable setup, etc.) work on Linux/macOS, and provide any necessary differences (e.g., environment variable syntax).
Add a section or note clarifying how to perform environment variable configuration and deployment from Linux/macOS terminals, not just via the Azure portal.
Wherever possible, use cross-platform language and avoid implying Windows as the default environment.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides instructions that are generic but implicitly assume a Windows-centric workflow by referencing the Azure Tools extension for VS Code without mentioning platform differences or providing Linux-specific guidance. There are no examples or notes about using the extension on Linux, nor are alternative Linux-native tools or command-line options discussed.

Recommendations:

Explicitly state that the Azure Tools extension for VS Code is cross-platform and works on Windows, Linux, and macOS.
Include screenshots or notes indicating any platform-specific differences in the UI or installation process.
Provide alternative instructions or references for users who prefer command-line tools (e.g., Azure CLI) on Linux.
Mention any prerequisites or troubleshooting steps that may be relevant for Linux users (such as dependencies or permissions).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both Bash and PowerShell examples, but the explanatory note is specific to PowerShell and appears before the PowerShell code block. There is no equivalent Linux-specific guidance or troubleshooting note, and the instructions for accessing Kudu are written in a way that assumes familiarity with the Azure Portal GUI, which is more commonly used on Windows.

Recommendations:

Add Linux-specific notes or troubleshooting tips, such as handling authentication or file permissions in Bash.
Provide CLI-based instructions for accessing the Kudu environment (e.g., using Azure CLI), not just through the Azure Portal GUI.
Ensure that explanatory notes are balanced between platforms, not only highlighting PowerShell-specific issues.
Consider reordering or parallelizing the presentation so that Bash and PowerShell examples and notes are given equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation presents Windows instructions and tools (7-Zip) before Linux/macOS equivalents and specifically recommends a third-party Windows tool while using built-in utilities for Linux/macOS. However, both platforms are covered in parallel for most steps, and CLI/cURL examples are cross-platform.

Recommendations:

Present macOS/Linux and Windows instructions in parallel or in alphabetical order to avoid implicit prioritization.
For creating ZIP files, mention built-in Windows options (such as right-click > Send to > Compressed (zipped) folder) before or alongside third-party tools like 7-Zip.
Explicitly note that the Azure CLI and cURL commands are cross-platform, and provide any necessary platform-specific flags or considerations.
Ensure screenshots and instructions for credential retrieval and other portal actions are not overly Windows-centric (e.g., avoid Windows-only UI references or terminology).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation describes deleting a resource group using a right-click context menu, which is a GUI pattern most commonly associated with Windows environments. There is no mention of equivalent command-line methods (such as Azure CLI or PowerShell), nor are Linux or cross-platform approaches provided.

Recommendations:

Include instructions for deleting a resource group using the Azure CLI (az group delete), which works across Windows, Linux, and macOS.
If referencing GUI actions, clarify that the instructions apply to the Azure Portal (web-based) rather than a Windows-specific application.
Provide PowerShell and Bash examples for users who prefer command-line interfaces.
Ensure that all examples and instructions are platform-neutral or provide parity between Windows and Linux where possible.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides instructions using the Azure portal UI, which is platform-agnostic, but does not mention or provide examples for enabling streaming logs via command-line tools commonly used on Linux (such as Azure CLI or Bash scripts). There is an implicit Windows-first bias as the absence of CLI examples can disadvantage Linux users who may prefer or require non-GUI methods.

Recommendations:

Add equivalent instructions for enabling streaming logs using the Azure CLI (az webapp log config) with example commands.
Include Bash script examples for automating the process, if applicable.
Explicitly mention that the steps apply to both Windows and Linux App Service plans, or clarify any differences.
Provide links to relevant documentation for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation only describes enabling streaming logs using the Azure Tools for VS Code extension, which is a GUI tool commonly associated with Windows environments. There are no examples or instructions for enabling streaming logs via command-line tools or methods commonly used on Linux systems.

Recommendations:

Add instructions for enabling streaming logs using the Azure CLI, which is cross-platform and widely used on Linux.
Provide examples for enabling streaming logs via the Azure Portal, which is platform-agnostic.
Explicitly mention that the VS Code extension is available on multiple platforms, if applicable, or clarify any platform limitations.
Include screenshots or command snippets for both Windows and Linux environments to ensure parity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation consistently uses Microsoft SQL Server client libraries and ODBC drivers (e.g., 'ODBC Driver 18 for SQL Server') that are traditionally associated with Windows environments. There is no mention of Linux-specific drivers, installation instructions, or troubleshooting for Linux environments. The documentation does not provide guidance for Linux users regarding driver installation, environment variable setup, or potential cross-platform issues.

Recommendations:

Explicitly mention that the ODBC Driver 18 for SQL Server is available for Linux and provide installation instructions for common Linux distributions (e.g., apt-get/yum commands).
Include troubleshooting tips or notes for Linux users, such as driver path issues or required dependencies.
Clarify that the code samples are cross-platform, or provide any necessary adjustments for Linux environments (e.g., case sensitivity, environment variable conventions).
Reference official Microsoft documentation for installing SQL Server drivers on Linux.
If any features or authentication methods are Windows-only, clearly state this and suggest alternatives for Linux where possible.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides step-by-step instructions that implicitly assume a graphical user interface (GUI) similar to Windows, without clarifying if the steps are applicable to Linux environments or providing alternative instructions for Linux users. There is no mention of Linux-specific tools, terminal commands, or differences in workflow, which may leave Linux users uncertain about how to proceed.

Recommendations:

Clarify whether the instructions apply to both Windows and Linux environments, especially if the Azure Portal UI is identical across platforms.
If there are differences for Linux users (such as CLI alternatives or different navigation), provide equivalent Linux instructions or command-line examples.
Explicitly mention that the steps are performed in the Azure Portal, which is web-based and cross-platform, to reassure non-Windows users.
Include links or references to Linux command-line deployment options (e.g., using Azure CLI or Git on Linux) for users who prefer or require non-GUI workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation describes navigation steps in the Azure portal without referencing any platform-specific tools. However, it implicitly assumes a GUI workflow common to Windows users and does not mention or provide examples for Linux command-line alternatives (e.g., using Azure CLI or Bash scripting), which may be preferred by Linux users.

Recommendations:

Add equivalent instructions for configuring application settings using the Azure CLI, which is cross-platform and commonly used on Linux.
Provide Bash script examples for automating configuration changes.
Explicitly mention that the Azure portal steps are platform-agnostic, but offer links or references to command-line alternatives for Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides generic instructions for deploying code using Git credentials but does not include any platform-specific examples. However, it implicitly assumes a Windows-centric workflow by omitting Linux-specific guidance, such as command-line examples for Git operations or FTPS usage on Linux. There is also no mention of Linux tools or terminal commands, which may leave Linux users without clear instructions.

Recommendations:

Add explicit Linux command-line examples for pushing code to the remote Git repository (e.g., using git push from a Linux terminal).
Include FTPS client usage examples for Linux (e.g., lftp, curl, or FileZilla on Linux).
Ensure that instructions and screenshots, if any, are not Windows-specific, or provide Linux equivalents.
Clearly state that the process is cross-platform and provide parity in examples for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation only describes enabling application logging via the Azure Portal UI, which is primarily a Windows-centric workflow. There are no examples or instructions for enabling logging using Linux-native tools, command-line interfaces, or configuration files, which are common in Linux environments.

Recommendations:

Add instructions for enabling application logging using the Azure CLI and/or Azure PowerShell, making sure to include both Bash and PowerShell examples.
Provide guidance for configuring logging in Linux-based App Service environments, such as using configuration files or environment variables.
Explicitly mention any differences in logging behavior or setup between Windows and Linux App Service plans.
Include screenshots or terminal commands relevant to Linux users where appropriate.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation references copying the Git Clone Uri but does not provide any example commands or workflows for setting up a Git remote. There are no explicit Windows-only tools or commands, but the absence of any Linux-specific instructions or parity examples (such as Linux shell commands) suggests a potential bias by omission. The documentation assumes a generic workflow but does not ensure Linux users are equally supported.

Recommendations:

Add explicit example commands for setting up a Git remote on both Windows (e.g., PowerShell or Command Prompt) and Linux (e.g., Bash).
If referencing any tools or commands in future steps, ensure both Windows and Linux equivalents are provided side-by-side.
Clarify that the instructions are platform-agnostic, or specify any platform-specific steps where necessary.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references the Azure portal UI, which is a cross-platform web interface, but does not provide any command-line examples. There is no mention of Linux-native tools (such as Azure CLI in Bash) or command-line alternatives, which may disadvantage Linux users who prefer or require CLI workflows.

Recommendations:

Add equivalent instructions using the Azure CLI (az webapp config appsettings set ...) with examples in Bash.
Explicitly mention that the Azure portal is platform-agnostic, but provide links or examples for both Windows (PowerShell) and Linux (Bash) command-line workflows.
Ensure future documentation includes parity between GUI and CLI instructions, catering to both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation presents Windows examples and instructions before Linux equivalents, indicating a 'windows_first' bias. However, Linux content is present and not missing.

Recommendations:

Reorder the pivots or examples so that Linux and Windows instructions are presented with equal prominence, or alternate which platform appears first.
Explicitly state that both Windows and Linux are supported at the beginning of the documentation.
Ensure that all examples and instructions are equally detailed for both Windows and Linux platforms.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or instructions, but it also omits Linux-specific guidance or examples. This absence may disadvantage Linux users if platform-specific steps are relevant.

Recommendations:

If platform-specific steps are required, provide both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash) examples.
Explicitly mention if the instructions are platform-agnostic, or clarify any differences for Linux users.
Ensure parity by including Linux tooling or command-line instructions where appropriate.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation references the 'az webapp up' command without specifying the operating system or providing examples for either Windows or Linux environments. While not overtly Windows-biased, the lack of explicit Linux examples or mention of cross-platform applicability may leave Linux users uncertain about compatibility.

Recommendations:

Clarify that the 'az webapp up' command works on both Windows and Linux platforms, if applicable.
Provide explicit examples or notes for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash) command usage.
Mention any OS-specific considerations or prerequisites, if they exist.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions for setting a configuration value using a dialog, but does not specify or illustrate how to perform this action on Linux systems, via command line, or using cross-platform tools. There are no explicit Windows tools mentioned, but the lack of Linux-specific or cross-platform examples suggests an implicit bias.

Recommendations:

Add instructions for setting the configuration using the Azure CLI, which works on all platforms.
Provide examples for setting the environment variable in Linux environments, such as using shell commands or editing configuration files.
Clarify whether the dialog is available on both Windows and Linux App Service plans, or provide alternative methods for Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples, but it also does not mention or demonstrate Linux-specific tools or workflows. The absence of any reference to Linux or cross-platform considerations may leave Linux users without guidance.

Recommendations:

Add explicit notes or examples for Linux users, such as how to view logs using common Linux tools or terminals.
Clarify whether the instructions are platform-agnostic or provide parallel steps for both Windows and Linux environments.
Mention any differences in log access or behavior between Windows and Linux deployments, if applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or instructions, but it also does not mention or demonstrate Linux-specific workflows or tools. There is an implicit bias due to the absence of Linux (or Mac) command-line examples, which could leave non-Windows users without clear guidance.

Recommendations:

Add explicit instructions or examples for both Windows (e.g., PowerShell, Command Prompt) and Linux/macOS (e.g., Bash) when describing how to use the Git credentials.
Include sample commands for cloning and pushing to the repository using both Windows and Linux command lines.
Clarify that the process applies equally to all platforms, and mention any platform-specific nuances if they exist.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions using a generic dialog interface without specifying platform-specific steps, but it lacks any mention of Linux-specific tools, command-line instructions, or parity for non-Windows environments. There are no explicit Windows-only examples, but the absence of Linux-focused guidance could disadvantage Linux users.

Recommendations:

Add equivalent instructions for setting SCM_DO_BUILD_DURING_DEPLOYMENT using Linux command-line tools (e.g., Azure CLI, Bash).
Include examples for both Windows (PowerShell, GUI) and Linux (Bash, CLI) environments to ensure parity.
Clarify whether the dialog is available across platforms or provide alternative steps for Linux users if not.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation references setting up a Git remote but does not provide any platform-specific instructions or examples. There is no mention of Linux or cross-platform command-line usage, which may leave Linux users without clear guidance.

Recommendations:

Add explicit examples for setting up a Git remote using both Windows (e.g., PowerShell or Command Prompt) and Linux/macOS (e.g., Bash).
Include command-line snippets for common Git operations on both platforms.
Clarify that the instructions are platform-agnostic if that is the case, or specify any platform-specific steps as needed.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides navigation instructions that are platform-neutral, but it does not include any command-line examples or references to platform-specific tools. However, there is a lack of Linux-specific guidance or CLI-based alternatives, which may disadvantage users who prefer or require non-GUI, cross-platform workflows.

Recommendations:

Add equivalent Azure CLI or PowerShell command examples for users who prefer command-line interfaces.
Include notes or links to documentation for configuring App Service settings via the Azure CLI or ARM templates, which are cross-platform.
Explicitly mention that the instructions apply to both Windows and Linux App Service plans, or clarify any differences if they exist.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not explicitly show Windows bias, as it avoids mentioning any OS-specific tools or commands. However, it also lacks any platform-specific guidance or examples, particularly for Linux users, which may leave gaps in understanding for those not on Windows.

Recommendations:

Add explicit notes or examples for both Windows and Linux users if any steps differ between platforms.
Clarify whether the instructions are platform-agnostic, and if not, provide parallel steps or screenshots for Linux environments.
Include references to common Linux tools or terminal commands if relevant to the deployment process.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation describes how to open an SSH session via the Azure portal's web interface, but does not mention or provide examples for accessing the SSH session using standard Linux or cross-platform command-line tools (e.g., OpenSSH client). This omits guidance for users who prefer or require CLI-based workflows, which are common on Linux.

Recommendations:

Add instructions for connecting to the App Service container using the standard SSH client (e.g., `ssh` command) from a terminal.
Clarify whether the SSH feature is available for both Windows and Linux App Service containers, and note any differences.
Provide equivalent command-line examples for Linux/macOS users, not just browser-based instructions.
Mention any prerequisites or configuration needed to enable SSH access from non-browser clients.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions using the Azure portal UI, which is platform-agnostic, but does not include any examples for configuring application settings via command-line tools such as Azure CLI or PowerShell. This omission can disadvantage Linux users who may prefer or require CLI-based workflows.

Recommendations:

Add examples for configuring application settings using the Azure CLI, which is cross-platform and commonly used on Linux.
If relevant, include PowerShell examples as well, but ensure they are presented alongside or after CLI examples to avoid Windows-first bias.
Explicitly mention that the Azure portal UI is available on all platforms, but provide alternative instructions for users who prefer command-line interfaces.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or instructions, but it also does not mention or illustrate Linux-specific workflows, tools, or commands. While it avoids explicit Windows bias (such as PowerShell commands or Windows-only tools), it misses the opportunity to demonstrate parity by including Linux (or macOS) command-line examples for pushing code to the remote repository.

Recommendations:

Add explicit examples for pushing code using both Windows (e.g., PowerShell or Command Prompt) and Linux/macOS (e.g., Bash) terminals.
Mention common cross-platform tools (such as Git Bash, Terminal, etc.) to ensure users on all platforms feel included.
If screenshots are included elsewhere, ensure they represent a mix of operating systems.
Clarify that the instructions apply equally to all platforms, or provide platform-specific notes where behavior may differ.

Create pull request

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