Scan Details - Linux-first Docs for Azure

1890

Pages Scanned

53

Pages Flagged

1890

Changed Pages

2.8%

% Pages Flagged

Scan Information

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

Finished At: 2025-09-16 00:41:23

Status: completed

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

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page provides only a PowerShell script example for programmatically accessing Azure AD B2C audit logs, with no equivalent example for Linux users (e.g., Bash, curl, or Python). The use of PowerShell and references to Azure Cloud Shell (which supports PowerShell by default) implicitly favors Windows environments and tools, potentially excluding or inconveniencing Linux and macOS users.

Recommendations:

Add a Bash/curl example for querying the Microsoft Graph API to retrieve audit logs, showing how to authenticate and download logs using common Linux tools.
Provide a Python script example using the requests library to demonstrate cross-platform access to the API.
Explicitly mention that the API can be accessed from any platform, and link to platform-agnostic Microsoft Graph API documentation.
If referencing Azure Cloud Shell, clarify that both Bash and PowerShell environments are available, and provide examples for both.
Review other automation or scripting sections to ensure parity between Windows/PowerShell and Linux/Bash tooling.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented around Azure Portal (a web UI) and Microsoft-centric tools such as Logic Apps and Microsoft Teams, with no mention of Linux-native or cross-platform alternatives. There are no CLI, Bash, or Linux automation examples, and all workflow automation is described using Microsoft GUI tools. The notification workflow is tied to Microsoft Teams, with no mention of alternatives like Slack or email. The documentation assumes the use of the Azure Portal and does not provide parity for users who prefer or require command-line or Linux-based automation.

Recommendations:

Provide equivalent examples using Azure CLI and Bash scripts for automation steps, including event subscription and API property updates.
Include instructions for configuring notifications using cross-platform tools (e.g., Slack, email, or webhooks) in addition to Microsoft Teams.
Mention and demonstrate how to automate the workflow using PowerShell, Azure CLI, or REST API calls, with examples runnable on Linux/macOS.
Add a section or callouts for users who prefer infrastructure-as-code (e.g., using Bicep, ARM templates, or Terraform) for setting up Logic Apps and event subscriptions.
Ensure that any references to Microsoft-specific tools (Teams, Logic Apps) are balanced with alternatives or at least acknowledge that other options exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows terminology and tools (such as PowerShell) are presented prominently, and scripting examples are provided for both Azure CLI and Azure PowerShell, but not for Linux-native shells or tools. The order of presentation often puts Windows or PowerShell first, and there are no explicit Linux shell (bash) or deployment examples. While Linux is mentioned in SKU availability, parity in automation and scripting is lacking.

Recommendations:

Provide bash shell scripting examples alongside PowerShell for automation tasks.
Ensure that Linux-specific deployment and configuration steps are included where relevant, especially for custom containers.
When listing tools or commands, alternate the order or present Linux and Windows options together to avoid 'windows_first' bias.
Clarify any differences in behavior or requirements between Windows and Linux App Service plans, especially in automation and scaling.
Add explicit Linux-native guidance (e.g., using bash scripts, Linux CLI environments) for common tasks such as scaling and deployment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides automation and scripting examples exclusively using PowerShell scripts for resource discovery and mitigation (e.g., identifying Traffic Manager endpoints and retrieving site config values). There are no equivalent examples or scripts for Linux/macOS users (such as Bash or cross-platform Azure CLI scripts). This creates a bias toward Windows users and may hinder Linux users from following the guidance efficiently.

Recommendations:

Provide equivalent Bash or cross-platform shell script examples for all PowerShell scripts referenced, especially for resource discovery and mitigation steps.
When referencing downloadable scripts (e.g., from GitHub), include both PowerShell (.ps1) and Bash (.sh) versions, or at least mention alternatives for Linux/macOS users.
Instruct users on how to use Azure CLI (which is cross-platform) for all automation tasks, and ensure that CLI examples are as detailed as PowerShell ones.
Explicitly state that the PowerShell scripts are for Windows and provide guidance or links for Linux/macOS users.
Review all automation and scripting guidance to ensure Linux parity and avoid assuming a Windows-first environment.

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 in Azure App Service. It references Windows-specific tools (such as Kudu's CMD/PowerShell console and Windows file paths), and does not provide equivalent Linux-based examples or guidance for Linux App Service environments. There are no Linux shell or container-native instructions, and Windows patterns are presented as the default or only option.

Recommendations:

Add equivalent instructions and examples for Linux-based App Service environments, including how to check .NET runtime versions, access environment variables, and deploy apps.
When referencing Kudu or console access, clarify differences between Windows and Linux App Service plans, and provide Linux shell (bash) commands where appropriate.
Avoid presenting Windows tools and file paths as the default; instead, structure sections to address both Windows and Linux scenarios, or clearly indicate when a step is Windows-specific.
Include notes or links to Linux/container documentation in each relevant section, not just in the introductory note.
Where Visual Studio is mentioned, also reference cross-platform deployment tools (such as Azure CLI, GitHub Actions, or VS Code) that work on Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation is structured with a clear separation between Windows and Linux content using pivots, which is good for parity. However, there are several signs of Windows bias: Windows sections are often presented first, Windows-specific tools and patterns (like KuduScript, .dll extensions, and Windows file paths) are emphasized, and some deployment automation examples (e.g., custom deployment scripts for Composer, Bower, Gulp, Grunt) are only detailed for Windows, with no equivalent Linux guidance. In some areas, Linux instructions are less detailed or require more manual steps (e.g., editing .ini files via echo due to lack of editors).

Recommendations:

Alternate the order of Windows and Linux pivots or present Linux first in some sections to avoid implicit prioritization.
Provide equivalent, detailed Linux examples for deployment automation tools (Composer, Bower, Gulp, Grunt), including how to generate and use custom deployment scripts in Linux App Service.
Where Windows-specific tools (like KuduScript) are recommended, clarify if/how they are supported on Linux, or provide Linux-native alternatives.
For file editing on Linux (e.g., .ini files), suggest practical alternatives or tools for editing files, or provide downloadable templates to reduce manual echo commands.
Ensure all troubleshooting and advanced configuration sections have Linux parity, with step-by-step instructions matching the detail level of Windows.
Highlight any differences in extension compatibility or deployment patterns between Windows and Linux, and provide guidance for both.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows-first bias: Windows-specific instructions, code samples, and certificate store usage are presented before Linux equivalents. Most code examples (especially for C# and Java) focus on Windows and the Windows certificate store, with Linux guidance being less detailed or deferred. Non-Windows languages (Node.js, PHP, Python, Java) are not given explicit Linux examples, and readers are directed to external documentation. Windows tools and patterns (certificate store, environment variables, file paths) are emphasized, while Linux approaches are less prominent or missing.

Recommendations:

Provide Linux-specific code examples for all major languages (C#, Java, Node.js, PHP, Python) alongside Windows examples.
Present Linux and Windows instructions in parallel or in clearly separated sections/tabs, rather than Windows-first.
Include explicit Linux command-line instructions (e.g., bash, Linux file paths) where Windows/Powershell commands are shown.
Expand on Linux certificate handling patterns (e.g., using OpenSSL, Linux environment variables) to match the depth of Windows coverage.
Avoid referring users to external documentation for Linux scenarios when Windows examples are provided inline.
Ensure parity in screenshots, environment variable explanations, and troubleshooting tips for both platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation demonstrates a moderate Windows bias. Windows-specific deployment methods (notably Web Deploy) are described in detail, with YAML examples defaulting to 'windows-latest' agents for these scenarios. The FAQ and troubleshooting sections focus on Windows agent requirements for Web Deploy, and there is no equivalent Linux-based deployment method or troubleshooting guidance. The documentation references IIS and Windows-specific patterns (such as web.config and iisnode) without Linux alternatives. While some steps mention both Windows and Linux App Service types, the more advanced or nuanced examples and error messages are Windows-centric.

Recommendations:

Provide Linux-native deployment examples for advanced scenarios, especially for tasks like Web Deploy, or clarify Linux alternatives (e.g., using zip deploy or FTP).
In troubleshooting sections, include common Linux agent issues and their solutions, not just Windows-specific errors.
When referencing Windows tools (like IIS, web.config, iisnode), also mention Linux equivalents or note when they are not applicable.
Ensure that YAML examples alternate or equally represent both 'windows-latest' and 'ubuntu-latest' agents, especially in sections where the agent OS matters.
Explicitly state when a feature is Windows-only and suggest best practices for Linux users.
Add links to Linux-focused documentation or external resources where appropriate.

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 YAML configurations referencing Windows-specific images (e.g., 'windows-latest') and App Service for Windows. There are no Linux container examples, nor any mention of how to adapt the process for Linux-based containers or App Service for Linux. The prerequisites and instructions assume a Windows application and environment throughout.

Recommendations:

Add parallel examples and instructions for deploying Linux containers, including YAML snippets using 'ubuntu-latest' or other Linux agents.
Include a section in prerequisites for Linux apps and Dockerfiles, clarifying any differences in setup.
Show how to select App Service for Linux in the deployment task, and provide the appropriate values for Linux container deployment.
Wherever variables or configuration options are given (e.g., vmImageName), show both Windows and Linux options side by side.
Explicitly mention that the process is similar for Linux containers and link to relevant Linux container documentation if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by prioritizing Windows tools (such as Visual Studio and WinSCP), referencing Windows-centric FTP clients first, and omitting explicit Linux command-line or tool examples for FTP/S deployment. PowerShell examples are provided, but there are no Linux shell (e.g., curl, lftp, or standard ftp/sftp) command examples. The troubleshooting and connection instructions reference Windows-oriented documentation (e.g., WinSCP) and do not mention Linux alternatives or workflows.

Recommendations:

Include Linux command-line examples for FTP/S deployment using common tools such as lftp, curl, or the standard ftp command.
List cross-platform or Linux-native FTP clients (such as FileZilla, lftp, or GNOME Files) alongside or before Windows tools like WinSCP and Visual Studio.
Provide shell (bash) script examples for retrieving FTP/S endpoints and deploying files, in addition to PowerShell.
Reference Linux-specific troubleshooting steps or documentation, such as firewall configuration on Linux or passive mode setup in Linux FTP clients.
Ensure parity in screenshots and walkthroughs for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a bias toward Windows environments by referencing Windows-specific UI patterns (e.g., 'Right click', 'Save'), using tooling and workflows (such as Azure Data Studio and SQL Server Management Studio) that are more commonly associated with Windows, and omitting explicit Linux command-line or cross-platform instructions. There are no PowerShell scripts, but the absence of Linux-specific examples or CLI-based workflows makes it less accessible for Linux users.

Recommendations:

Provide equivalent Linux instructions for file operations (e.g., using 'dotnet new', 'touch', or editors like vim/nano instead of 'Right click').
Include examples of connecting to Azure SQL using cross-platform tools such as Azure CLI, sqlcmd, or Data Studio on Linux.
When referencing UI actions (like 'Right click'), add alternative command-line or editor-based steps.
Explicitly mention that all code and deployment steps can be performed on Linux, and highlight any OS-specific considerations.
Add screenshots or terminal commands for Linux environments where applicable.
Ensure that all prerequisites and tooling (such as .NET SDK, Azure CLI, and editors) are referenced in a cross-platform manner.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides cross-platform examples for most stacks (Node.js, Python, Java, Tomcat, ASP.NET Core) using Ubuntu runners and Linux-friendly tooling. However, the ASP.NET (classic) example is Windows-specific: it uses 'windows-latest' runners, Windows paths, and Windows-only tools (NuGet, MSBuild) without offering a Linux alternative or mentioning cross-platform options. This prioritizes Windows for ASP.NET and omits Linux parity for that stack.

Recommendations:

Add a Linux-based example for ASP.NET (classic) if possible, using Mono or .NET Core-compatible tools, or explicitly state if Windows is required.
Clearly indicate in the ASP.NET section why Windows runners/tools are necessary, if that is the case, to inform users of platform constraints.
For all stacks, ensure that both Windows and Linux runner options are shown when feasible, or provide guidance on cross-platform compatibility.
Consider reordering or grouping examples so that Linux and Windows parity is visually clear, rather than defaulting to Windows for certain stacks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a Windows bias by frequently highlighting features as 'Windows apps only' (e.g., proactive CPU monitoring, proactive auto-healing, Navigator), providing more detail and tooling for Windows scenarios, and lacking equivalent Linux examples or guidance. Linux support is mentioned, but often as an afterthought, with fewer details and less parity in advanced diagnostics.

Recommendations:

Provide equivalent Linux examples and detailed guidance for all diagnostic features, or clearly state if a feature is unavailable on Linux.
Ensure that Linux and container scenarios are described with the same depth as Windows, including screenshots and step-by-step instructions.
Where features are Windows-only, suggest alternative troubleshooting steps or tools for Linux users.
Reorganize sections so that Linux and Windows parity is clear, and avoid consistently listing Windows features first.
Add explicit callouts or comparison tables that summarize feature availability and differences between Windows and Linux App Service environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing Windows-style paths (e.g., D:\home), using Windows terminology and folder structures throughout, and mentioning Windows containers before Linux containers. There are no Linux-specific examples or equivalent Linux path references, and tools or instructions that would be familiar to Linux users are absent. The only tool mentioned for checking disk usage is a GUI site extension, with no mention of command-line alternatives suitable for Linux users.

Recommendations:

Include Linux path equivalents (e.g., /home/site) alongside Windows paths in all examples and explanations.
When discussing containers, mention Linux containers first or provide parallel instructions/examples for both Windows and Linux containers.
Provide Linux-friendly methods for checking folder sizes (e.g., using du in Kudu SSH/console) in addition to the Azure Web Apps Disk Usage extension.
Clarify any differences in local cache behavior or configuration for Linux-based App Service plans.
Ensure that all code snippets, environment variable checks, and troubleshooting steps are applicable to both Windows and Linux environments, or clearly indicate platform-specific differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides extensive Azure PowerShell examples and references, often giving them equal or greater prominence than Azure CLI. PowerShell is a Windows-centric tool, and its heavy use can signal a Windows bias. Additionally, there are no explicit Linux shell (bash) or platform-agnostic scripting examples, and no mention of Linux-specific tools or workflows. The documentation does not clarify cross-platform compatibility for PowerShell commands, which may lead Linux users to assume these instructions are Windows-only.

Recommendations:

Include explicit bash (Linux shell) examples alongside PowerShell, especially for scripting and token retrieval.
Clarify that Azure CLI and PowerShell are both cross-platform, and indicate which commands work on Linux, macOS, and Windows.
When listing tabs or options, consider ordering Azure CLI before PowerShell to reflect its broader cross-platform usage.
Add notes or links to installing and using Azure PowerShell on Linux/macOS, or recommend Azure CLI as the default for non-Windows users.
Where PowerShell is not supported (e.g., adding user-assigned identity in App Service), suggest alternative Linux-friendly approaches.
Ensure that all code samples and instructions are tested and clearly marked as cross-platform where applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Linux and Windows deployment paths, but there are subtle biases favoring Windows. In Visual Studio Code deployment, the Windows instructions are more detailed and include extra steps (such as web.config generation) that are not paralleled for Linux. Windows-specific tools and patterns (like web.config, Application Insights, and certain App Service settings) are mentioned without Linux equivalents or context. The CLI and portal sections default to Linux but still reference Windows-specific options. There is also a lack of explicit Linux troubleshooting or configuration guidance where Windows gets extra notes.

Recommendations:

Ensure Linux and Windows instructions are equally detailed, especially in Visual Studio Code deployment steps.
When mentioning Windows-specific concepts (e.g., web.config, Application Insights), provide Linux equivalents or clarify that they are not needed on Linux.
Add troubleshooting tips and notes for Linux deployments, similar to the extra guidance given for Windows.
Avoid presenting Windows-specific steps or tools before Linux ones unless Linux is the default/recommended path.
Where possible, use cross-platform terminology and avoid assuming Visual Studio Code or Azure App Service behaviors are identical across OSes—call out differences explicitly.
Include explicit examples or notes for common Linux shell environments (bash, zsh) when providing command-line instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in several ways: Windows-specific paths and tools are often mentioned first or exclusively (e.g., 'D:\home', references to 'w3wp.exe', 'applicationHost.config', and Windows-specific environment variables). Many settings and explanations are tailored to Windows App Service or native Windows apps, with Linux equivalents either mentioned later, less prominently, or omitted. Some examples and defaults reference Windows conventions (such as time zones linked to Windows documentation, or logging paths using Windows syntax). In build automation, the Kudu (Windows) section is more detailed and comes before the Oryx (Linux) section. Several environment variables are described as 'Windows only' or have Windows-specific behaviors, with Linux alternatives not always fully explained.

Recommendations:

For every Windows-specific example or path (e.g., 'D:\home'), provide the Linux equivalent (e.g., '/home').
When referencing tools or processes (e.g., 'w3wp.exe', 'applicationHost.config'), also mention the Linux or cross-platform alternatives, or clarify when they are not applicable.
Avoid linking only to Windows documentation (such as time zones); include Linux/Unix equivalents or note differences.
Present Linux and Windows options in parallel, rather than always listing Windows first.
Expand the Oryx (Linux) build automation section to match the detail of the Kudu (Windows) section, and ensure parity in explanations and examples.
Clearly indicate when a setting is platform-specific, and provide guidance for both platforms where possible.
Where defaults differ by platform, explicitly state the default for each (not just for Windows).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows and Visual Studio workflows, with all examples and instructions assuming the use of Visual Studio on Windows. There are no references to Linux, macOS, or cross-platform tools, and all file paths, tools (e.g., Server Explorer, Output window), and troubleshooting steps are specific to the Windows ecosystem. Windows-specific tools like Log Parser and IIS are mentioned, while Linux equivalents or cross-platform alternatives are absent. No command-line or non-GUI (CLI) approaches are provided, and there is no mention of how to perform similar troubleshooting on Linux-based App Service environments or from non-Windows development environments.

Recommendations:

Add equivalent instructions and examples for troubleshooting Azure App Service apps using cross-platform tools such as Visual Studio Code, Azure CLI, and Azure Portal.
Include Linux/macOS workflows for remote debugging, log streaming, and file access, especially for developers not using Visual Studio on Windows.
Reference and provide examples for using Azure CLI and/or Azure Cloud Shell to enable and access logs, download files, and perform remote debugging.
Mention and document open-source or cross-platform log analysis tools (e.g., jq, grep, awk, GoAccess) alongside Windows tools like Log Parser.
Clarify which features are only available on Windows or with Visual Studio, and provide alternatives or workarounds for Linux-based App Service plans.
Add a section or callouts for Linux App Service troubleshooting, including differences in log locations, configuration, and available features.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and PowerShell examples for Azure CLI commands, but consistently presents Bash (Linux/macOS) syntax first, followed by PowerShell (Windows) syntax. However, the documentation refers to running commands in 'PowerShell or a bash shell' and provides explicit PowerShell syntax for every CLI example, which is not always the case in Microsoft docs. There is no exclusive use of Windows tools or patterns, and Linux users are well supported. The use of Visual Studio Code (cross-platform) and Azure CLI (cross-platform) further reduces Windows bias.

Recommendations:

Continue providing both Bash and PowerShell examples for all CLI commands.
Consider explicitly stating that all tools and steps are supported on Linux, macOS, and Windows.
Where possible, include screenshots or references for Linux/macOS environments in addition to Azure Portal (which is OS-agnostic).
If any step is OS-specific (e.g., file paths, shell commands), clarify the differences for each platform.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page is generally cross-platform and avoids explicit Windows-only tooling or examples. However, there is a subtle Windows bias in the troubleshooting section, where only the Windows-specific command ('ipconfig /flushdns') is mentioned for clearing the DNS cache. No equivalent Linux or macOS instructions are provided, and the Windows method is given as the sole example. There are no PowerShell scripts, Windows tools, or patterns otherwise, but the omission of Linux/macOS parity in this instance constitutes a minor bias.

Recommendations:

When mentioning DNS cache clearing, provide equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo service nscd restart') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
Wherever OS-specific troubleshooting steps are given, include instructions for all major platforms (Windows, Linux, macOS) to ensure parity.
Consider adding a short table or note with DNS cache clearing commands for each OS in the troubleshooting section.
Review other troubleshooting or automation sections for similar implicit Windows-first assumptions, and add cross-platform guidance as needed.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exclusively uses Azure CLI commands and portal instructions, with no mention of platform-specific tools or shell environments (such as PowerShell or Bash). However, there is a subtle bias in that all command-line examples use the Azure CLI in a way that is most familiar to Windows users (e.g., backslash line continuations), and there are no explicit Linux/Bash shell examples or notes about cross-platform usage. There are also no references to Linux-specific tools, patterns, or considerations, and no mention of how to perform these actions outside the Azure CLI or portal (e.g., via REST with curl, or using Bash scripting).

Recommendations:

Add explicit Bash/Linux shell examples, including line continuations with backslashes and/or semicolons as appropriate.
Clarify that Azure CLI commands are cross-platform, and provide notes or examples for running them in Bash/Linux environments (e.g., using \ for line continuation in Bash, or using single-line commands).
Include alternative instructions for performing API calls using curl or other common Linux tools, especially for the REST API examples.
If any PowerShell-specific instructions are relevant, provide equivalent Bash/Linux commands.
Add a note about the cross-platform nature of Azure CLI and how to install/use it on Linux, or link to the Linux installation guide.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides cross-platform deployment examples for various languages, with most workflows running on Ubuntu (Linux). However, the ASP.NET (not Core) example exclusively uses 'windows-latest' runners and Windows-specific tools (NuGet, MSBuild), and it is presented before the Java, Node.js, and Python examples. There is no equivalent Linux-based example for classic ASP.NET, which may disadvantage Linux users or those seeking parity.

Recommendations:

Provide a Linux-based example for deploying ASP.NET applications, if technically feasible (e.g., using Mono or .NET Core for compatible projects).
Clearly explain why Windows runners are required for certain workloads (such as classic ASP.NET) and suggest alternatives or workarounds for Linux users.
Ensure that for each language or framework, both Windows and Linux deployment options are documented where possible.
Consider reordering or grouping examples so that Windows-specific workflows are not always presented before Linux ones, or explicitly call out platform requirements in headings.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides instructions that are generic but implicitly assume a Windows environment by referencing VS Code UI patterns and terminology commonly associated with Windows users. There are no Linux-specific instructions or clarifications, and no mention of alternative workflows or considerations for Linux users.

Recommendations:

Explicitly mention that the instructions apply to all platforms (Windows, Linux, macOS) if true.
Include notes or screenshots showing the process on Linux (and macOS) to ensure parity.
Highlight any differences in UI or behavior that Linux users might encounter.
If there are command-line alternatives (e.g., using Azure CLI), provide those as well for users who may not use VS Code or prefer terminal workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation uses UI navigation steps that are generic but implicitly reflect a Windows-centric perspective by referencing the Azure portal's left toolbar and settings structure, which may be more familiar to Windows users. There are no examples or instructions for performing the same configuration via Linux-friendly methods, such as Azure CLI, Bash, or ARM templates, nor is there mention of command-line alternatives.

Recommendations:

Add equivalent instructions for configuring application settings using Azure CLI and Bash, which are commonly used on Linux.
Provide examples of how to set application settings via ARM templates or REST API for cross-platform parity.
Explicitly mention that the Azure portal UI is the same across platforms, or clarify any differences if they exist.
Include a section or links for command-line and automation options to ensure Linux and macOS users are equally supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both Bash and PowerShell examples, but the instructions for accessing the Kudu Environment are written in a way that assumes the user is using the Azure portal UI, which is more familiar to Windows users. Additionally, the PowerShell example is given equal prominence, and the note about username quoting specifically addresses PowerShell behavior, suggesting a Windows-centric perspective.

Recommendations:

Include explicit instructions for accessing the Kudu Environment from Linux/macOS terminals, such as using the Azure CLI or direct URL access, not just the Azure portal UI.
Add notes or troubleshooting tips relevant to Bash/Linux users, similar to the PowerShell-specific note.
Consider listing the Bash example before the PowerShell example to avoid implicit prioritization of Windows environments.
Mention any platform-specific prerequisites or differences in behavior between Bash and PowerShell to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation describes a resource deletion process using a graphical user interface with right-click actions, which is a pattern most commonly associated with Windows environments. There are no equivalent instructions or examples for Linux users, such as command-line alternatives or references to cross-platform tools.

Recommendations:

Include command-line instructions (e.g., using Azure CLI or Bash) for deleting a resource group, which are accessible and familiar to Linux users.
Avoid describing only GUI-based workflows; provide parity with terminal-based methods.
Explicitly mention that the instructions apply to the Azure Portal (if that's the case), and offer alternatives for users who prefer or require non-GUI approaches.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation describes enabling streaming logs in Azure App Service exclusively through the Azure portal UI, which is a cross-platform method, but it does not mention or provide examples for command-line alternatives (such as Azure CLI or PowerShell). There is no explicit Windows-only tool or command, but the omission of CLI examples (which are often used on Linux) and the lack of mention of Linux-specific considerations may disadvantage Linux users.

Recommendations:

Add Azure CLI examples for enabling streaming logs, as CLI is widely used on Linux.
If PowerShell examples are provided elsewhere, ensure equivalent Azure CLI or Bash examples are also included.
Mention any Linux-specific considerations for App Service logging, if applicable.
Structure the documentation so that cross-platform (CLI, REST API) methods are presented alongside or before platform-specific UI instructions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references the Azure Tools for VS Code extension, which is commonly used on Windows, and does not provide any alternative instructions or examples for enabling streaming logs via Linux command-line tools or native Azure CLI commands. There is no mention of Linux-specific workflows or tools.

Recommendations:

Add instructions for enabling streaming logs using the Azure CLI, which is cross-platform and commonly used on Linux.
Include examples for enabling streaming logs via the Azure portal, which is OS-agnostic.
Explicitly mention that the VS Code extension is available on all platforms, if applicable, or provide alternatives for Linux users.
Ensure that documentation covers both GUI and command-line approaches to accommodate users on different operating systems.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides UI navigation steps that are generic, but it implicitly assumes a Windows-style interface (e.g., 'menu on the left side', 'top menu bar') without clarifying if the experience is the same on Linux or cross-platform environments. There are no examples or notes for Linux users, nor is there mention of command-line alternatives that might be more familiar to Linux users.

Recommendations:

Clarify if the UI steps are identical across Windows, Linux, and Mac platforms, or note any differences.
Include command-line instructions (e.g., using Azure CLI) as an alternative to GUI steps, which is often preferred by Linux users.
Explicitly mention platform parity or provide screenshots/examples for both Windows and Linux environments.
Add a note or section addressing any platform-specific considerations for Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation does not provide any platform-specific examples or commands, but it implicitly assumes a Windows-centric workflow by referencing the 'Git prompt' without clarifying cross-platform usage. There are no explicit Linux or macOS instructions or examples, and no mention of platform-specific tools or differences.

Recommendations:

Add explicit instructions or examples for both Windows (e.g., Command Prompt, PowerShell) and Linux/macOS (e.g., Bash terminal) when describing how to use the credentials.
Clarify that the Git prompt and authentication process are similar across platforms, or note any differences if they exist.
Provide sample git commands for both Windows and Linux/macOS environments to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both PowerShell and Azure CLI examples for scripting tasks, but PowerShell (a Windows-centric tool) is consistently listed before Azure CLI in all code example tabs. There are no explicit Linux shell or bash examples, and the PowerShell examples may not be directly usable on Linux systems. The portal instructions are platform-agnostic, but scripting guidance is Windows-first.

Recommendations:

Alternate the order of PowerShell and Azure CLI tabs, or list Azure CLI first to reflect its cross-platform nature.
Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell examples may require PowerShell Core on non-Windows systems.
Add bash shell examples where appropriate, especially for common scripting tasks.
Clarify in the prerequisites or introduction that all tasks can be performed from Linux, macOS, or Windows using Azure CLI, and provide links to installation instructions for each OS.
Where PowerShell is used, specify if the script is compatible with PowerShell Core (cross-platform) or only Windows PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation describes navigation steps using the Azure portal UI, which is generally cross-platform. However, there is an implicit Windows-first bias as there are no references to Linux-specific workflows, CLI commands, or alternative methods that Linux users might prefer. There are no examples or instructions for performing the same task using the Azure CLI, Bash, or other non-Windows tools.

Recommendations:

Add equivalent instructions for configuring application settings using the Azure CLI, which is platform-agnostic and commonly used on Linux.
Include Bash or shell command examples for Linux users.
Explicitly state that the Azure portal steps are the same across operating systems, or provide links to documentation for Linux/macOS users.
Consider adding a section titled 'Using the Azure CLI' or 'Command-line Instructions' to ensure parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation references 'FTPS credentials' and describes deployment steps without providing platform-specific guidance. FTPS is often associated with Windows tools, and there are no examples or instructions for Linux users or alternative tools commonly used on Linux (such as command-line FTP clients or scp/rsync). The lack of Linux-specific examples or mention of cross-platform tools suggests a subtle Windows bias.

Recommendations:

Include explicit instructions or examples for deploying code using common Linux tools (e.g., lftp, curl, or command-line git).
Mention cross-platform deployment methods and tools, ensuring both Windows and Linux users are addressed.
If FTPS is required, provide example commands for both Windows (e.g., FileZilla, WinSCP) and Linux (e.g., lftp, curl).
Clarify that the credentials can be used with any standard FTPS or Git client, and link to relevant documentation for both platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides instructions that are tailored to the Azure App Service interface without specifying platform differences, but the steps and terminology (such as 'File System' logging) are more commonly associated with Windows-based App Service plans. There is no mention of Linux-specific logging options or differences, nor are Linux examples provided.

Recommendations:

Explicitly state whether the instructions apply to both Windows and Linux App Service plans.
If there are differences in logging configuration or terminology for Linux-based App Service, provide parallel instructions or note the differences.
Include examples or screenshots for both Windows and Linux App Service environments.
Mention any Linux-specific logging options (such as Docker logs or Linux file system paths) if applicable.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation refers to copying the 'Git Clone Uri' for later use but does not provide any example commands or instructions for setting up the Git remote. There is no explicit mention of Windows tools, but the lack of Linux-specific or cross-platform instructions/examples (such as terminal commands for adding a Git remote) suggests a bias by omission, as it assumes a generic or possibly Windows-centric workflow.

Recommendations:

Add explicit cross-platform instructions for setting up a Git remote, including both Windows (Command Prompt/PowerShell) and Linux/macOS (bash) command examples.
Where possible, provide screenshots or terminal snippets for both environments.
Clarify that the instructions apply to all platforms, or specify any platform-specific steps if necessary.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing 'Azure App Service on Windows pricing' and omitting any mention of Linux-based App Service plans or their pricing/features. There are no Linux-specific instructions, screenshots, or links, and the terminology and examples assume a Windows environment.

Recommendations:

Include references and links to Azure App Service on Linux pricing and documentation alongside Windows equivalents.
Add notes clarifying differences (if any) in scaling workflows or available features between Windows and Linux App Service plans.
Provide screenshots and examples for both Windows and Linux App Service environments.
Ensure that all feature comparisons and limitations are presented for both Windows and Linux tiers, or clearly state if a feature is Windows-only.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a subtle Windows bias by referencing 'local cache for Windows apps' as a mitigation for cold starts, without mentioning an equivalent for Linux apps or clarifying Linux support. No Linux-specific examples, tools, or guidance are provided, and the only platform-specific advice is Windows-focused.

Recommendations:

When mentioning features like local cache, clarify whether similar functionality exists for Linux apps, and provide links or documentation for Linux equivalents if available.
Include examples or notes for both Windows and Linux App Service plans when discussing mitigation strategies, such as cold start reduction.
Review all platform-specific recommendations to ensure Linux parity, or explicitly state if a feature is Windows-only.
Consider adding a section or FAQ entry addressing any differences in maintenance experience or preparation steps for Linux-based App Service plans.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions and examples primarily using the Azure portal and Azure CLI, which are cross-platform. However, in the 'Test in virtual network' section, only the nslookup utility is mentioned for DNS validation, with no explicit Linux or PowerShell-specific examples. There are no Windows-specific tools or PowerShell commands, but the documentation does not provide explicit Linux command-line examples or mention Linux-specific tools, which may leave Linux users without clear guidance for certain steps.

Recommendations:

Include explicit Linux command-line examples where relevant, such as using 'dig' alongside 'nslookup' for DNS validation.
Where CLI commands are shown, clarify that Azure CLI is cross-platform and works on both Windows and Linux.
If referencing tools/utilities, provide both Windows and Linux equivalents (e.g., 'nslookup' and 'dig').
Add a note or section for Linux users if there are any OS-specific considerations or troubleshooting steps.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation presents Windows examples and instructions before Linux equivalents, as seen in the order of the code pivots. While Linux content is present, the structure prioritizes Windows scenarios, which may suggest a bias toward Windows users.

Recommendations:

Alternate the order of pivots so that Linux examples are presented first in some cases, or present both Windows and Linux pivots side-by-side where possible.
Explicitly mention at the top that instructions are available for both Windows and Linux, to signal parity.
Ensure that the depth and clarity of Linux examples match those of Windows, and that all features are equally documented.
Consider adding a summary table comparing Windows and Linux approaches for quick reference.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides an instruction to create an App Service Web App but does not specify or illustrate how this action would differ or be performed on Linux versus Windows platforms. There is no mention of Linux-specific steps, tools, or considerations.

Recommendations:

Include explicit instructions or notes for both Windows and Linux users if the process differs.
If the UI or CLI tools behave differently on Linux, provide screenshots or command examples for both platforms.
Clarify whether the 'Create App Service Web App...' option is available and behaves identically on Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or instructions, but it also omits any mention of Linux or cross-platform considerations. This absence can be seen as a subtle bias, as it may implicitly assume a default (often Windows) environment without clarifying applicability to Linux users.

Recommendations:

Explicitly state whether the instructions apply to both Windows and Linux environments.
If there are platform-specific steps or differences, provide examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash).
Clarify any prerequisites or environment-specific considerations for Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation references the use of the 'az webapp up' command without providing any platform-specific examples. While the command is cross-platform, there is no indication of how to run it on Linux or macOS, nor are there any shell-specific examples (e.g., Bash vs. PowerShell). This lack of explicit Linux (or non-Windows) guidance may unintentionally bias the documentation toward Windows users, especially if other pages in the documentation set default to Windows examples.

Recommendations:

Include explicit examples for running the 'az webapp up' command in both Bash (Linux/macOS) and PowerShell (Windows) shells.
Add a note clarifying that the Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
If there are platform-specific considerations (such as authentication or environment setup), provide guidance for each major OS.
Ensure that future documentation consistently provides parity between Windows and Linux/macOS examples.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions for setting a configuration value using a dialog interface, but does not specify or illustrate how to perform this action on Linux systems or via command-line tools commonly used on Linux. There is no mention of Linux-specific methods or parity with Windows approaches.

Recommendations:

Add explicit instructions for setting the configuration using Linux command-line tools, such as the Azure CLI or environment variable export commands.
Include examples for both Windows (e.g., PowerShell, GUI) and Linux (e.g., Bash, CLI) to ensure parity.
Clarify whether the dialog interface is available on both Windows and Linux, or specify alternatives for Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not explicitly mention or provide examples for Linux users. While it references the VS Code Output window, which is cross-platform, there is no guidance or examples specific to Linux environments, nor is there mention of Linux-specific tools or workflows.

Recommendations:

Add explicit statements confirming that the instructions apply equally to Linux, macOS, and Windows.
Include examples or screenshots from Linux environments to demonstrate parity.
Mention any Linux-specific considerations or troubleshooting steps, if applicable.
Clarify that VS Code Output window behavior is consistent across platforms, or note any differences.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions using a generic dialog interface without specifying any platform-specific commands or tools. However, it does not include any command-line examples for either Windows (e.g., PowerShell) or Linux (e.g., Bash), which could leave Linux users without clear guidance if they prefer or require CLI-based configuration.

Recommendations:

Add equivalent command-line examples for both Windows (PowerShell) and Linux (Bash) to set the environment variable.
Explicitly mention how to perform this configuration using CLI tools such as Azure CLI or environment variable files on both platforms.
Ensure that any future examples or instructions are presented for both Windows and Linux users to maintain parity.

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 how to perform the task on either Windows or Linux, but the absence of Linux (or any cross-platform) command-line examples is a missed opportunity for parity.

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).
Ensure that any future steps referencing command-line actions include both Windows and Linux/macOS syntax.
Consider providing a generic, cross-platform Git command example (e.g., 'git remote add origin <Git Clone Uri>') and clarifying that it works on all major platforms.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides generic instructions for using the Azure portal and does not mention or provide examples for either Windows or Linux environments. However, it omits any command-line or OS-specific instructions, which could be relevant for users who prefer or require CLI-based workflows, especially on Linux.

Recommendations:

Add equivalent instructions for accessing resource groups using the Azure CLI (az group show) with example commands.
Include both Windows (PowerShell) and Linux (Bash) command-line examples where relevant.
Clarify that the instructions are for the Azure portal UI, and provide links or references to CLI documentation for both Windows and Linux users.

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 lacks any platform-specific guidance or examples, and does not provide Linux-specific instructions or parity checks, which could be seen as a missed opportunity for inclusivity.

Recommendations:

Add explicit notes or examples for both Windows and Linux users where relevant, especially if file paths, environment variable syntax, or tooling might differ.
Clarify that the instructions are platform-agnostic if that is the case, or specify any steps that may differ between Windows and Linux.
Include troubleshooting or verification steps for both Windows and Linux environments to ensure parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not explicitly show Windows bias through tools or commands, but it also lacks any platform-specific examples or instructions. There are no Linux or Windows-specific commands, but the absence of any mention of Linux (or Windows) means Linux parity is not addressed.

Recommendations:

Add explicit notes or examples for both Windows and Linux users if platform-specific steps exist.
Clarify whether the instructions are platform-agnostic or if there are differences for Linux environments.
Include screenshots or terminal examples from both Windows and Linux if applicable.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation describes accessing an SSH session via the Azure portal and a web URL, but does not mention or provide examples for accessing the service using standard SSH clients or command-line tools commonly used on Linux systems. There is no explicit Windows bias, but the lack of Linux-specific or cross-platform command-line examples may disadvantage Linux users.

Recommendations:

Add instructions or examples for connecting to the App Service container using standard SSH clients (e.g., the `ssh` command-line tool) on Linux and macOS.
Clarify whether the SSH feature is available for both Windows and Linux App Service containers, and note any differences.
Provide parity in documentation by including both browser-based and command-line access methods, ensuring users on all platforms have clear guidance.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides generic instructions for configuring an application setting in Azure App Service but does not include any platform-specific examples. However, it also does not mention or provide examples for Linux environments (e.g., using Azure CLI, bash, or Linux-specific configuration methods), which may leave Linux users without clear guidance.

Recommendations:

Add explicit instructions or examples for configuring application settings using the Azure CLI or bash, which are commonly used in Linux environments.
Include a note or section clarifying that the instructions apply to both Windows and Linux App Service plans, or specify any differences.
Provide screenshots or command-line examples relevant to Linux users to ensure parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions for obtaining deployment credentials but does not include any platform-specific examples or commands. However, it also does not mention or demonstrate how to use these credentials on either Windows or Linux, resulting in a lack of Linux parity if users expect command-line guidance.

Recommendations:

Add explicit examples for both Windows (e.g., using PowerShell or Command Prompt) and Linux/macOS (e.g., using Bash) to show how to use the credentials when pushing code.
Include sample git commands for both platforms, demonstrating how to input the credentials when prompted.
Clarify that the process is cross-platform and provide any platform-specific notes if there are differences in credential handling.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation presents Windows defaults before Linux in the configuration table and mentions Windows-specific limitations and behaviors. However, it does not provide Windows/Powershell-only examples, nor does it omit Linux equivalents. The CLI examples are cross-platform (Azure CLI), and Linux-specific behaviors are mentioned alongside Windows. There is a slight bias in listing Windows defaults first and referencing Windows-specific limitations before Linux.

Recommendations:

List Linux and Windows defaults in parallel columns or alternate which OS is mentioned first to avoid implicit prioritization.
Where Windows-specific limitations are mentioned, also highlight any Linux-specific limitations (if any), or explicitly state when there are none.
Continue to use cross-platform tools like Azure CLI for examples, and avoid Windows/Powershell-only instructions.
Consider adding a summary table or section that clearly delineates differences and similarities between Windows and Linux App Service behaviors for DNS.

Create pull request

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