App Service

806
Total Pages
669
Linux-Friendly Pages
137
Pages with Bias
17.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

247 issues found
Showing 1-25 of 247 flagged pages
App Service Managed Instance on App Service overview (preview) ...main/articles/app-service/overview-managed-instance.md
High Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased toward Windows, with all examples, configuration options, and tooling (PowerShell, registry, MSI, IIS, RDP) being Windows-specific. There is no mention of Linux equivalents, and the platform is explicitly stated as Windows-only. Linux users are excluded from using this feature, and no guidance is provided for Linux or cross-platform scenarios.
Recommendations
  • Clearly state at the top that Managed Instance is Windows-only and provide links to Linux/container alternatives.
  • Add a comparison table or section highlighting feature parity and differences between Windows Managed Instance and Linux App Service plans.
  • Offer migration guidance for Linux users, including recommended hosting options and how to achieve similar isolation/customization.
  • If future Linux support is planned, mention roadmap or alternatives.
  • Ensure that documentation for related features (e.g., configuration scripts, storage mounts) includes Linux/container examples where applicable.
GitHub Create Pull Request
App Service Migrate .NET Apps to Azure App Service .../articles/app-service/app-service-asp-net-migration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page is heavily focused on Windows-based migration scenarios, tools, and patterns. All migration tools listed are for Windows (IIS) servers, and PowerShell scripts are the only automation examples provided. There is no mention of Linux-based .NET hosting environments, nor are there examples or guidance for migrating .NET apps from Linux or macOS platforms. Windows tools and approaches are presented exclusively and first, creating friction for users on non-Windows platforms.
Recommendations
  • Add guidance and examples for migrating .NET apps hosted on Linux (e.g., Kestrel, Apache, Nginx) to Azure App Service.
  • Include automation examples using Bash scripts or cross-platform CLI tools, not just PowerShell.
  • Clarify whether migration tools support Linux-based .NET Core/ASP.NET Core apps, and provide parity tooling or manual migration steps if not.
  • Explicitly mention limitations of current tools for non-Windows environments and suggest alternative migration approaches.
  • Present Windows and Linux migration scenarios side-by-side where possible, rather than focusing solely on Windows.
GitHub Create Pull Request
App Service Node.js Best Practices and Troubleshooting ...rvice-web-nodejs-best-practices-and-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation is heavily focused on Windows/IIS environments, specifically through the use of iisnode, web.config, and references to Windows-specific concepts (such as Win32 error codes, named pipes, DLLs, and the EmptyWorkingSet function). All configuration and troubleshooting steps are tailored to Windows/IIS, with no mention of Linux-based Azure App Service environments or their equivalents (e.g., PM2, nginx, or Linux process management). There are no Linux/macOS examples, and Windows tools and patterns are referenced exclusively.
Recommendations
  • Add equivalent guidance for Node.js apps running on Linux-based Azure App Service, including configuration, logging, and troubleshooting steps.
  • Provide examples using Linux-native process managers (e.g., PM2) and configuration files (e.g., ecosystem.config.js) alongside Windows/IIS examples.
  • Include troubleshooting steps and file paths relevant to Linux environments (e.g., /home/LogFiles/...).
  • Reference Linux/macOS diagnostic tools and patterns (e.g., systemd, journalctl, lsof, top) where appropriate.
  • Clearly indicate which sections apply only to Windows/IIS and provide parity for Linux-based hosting where possible.
GitHub Create Pull Request
App Service Managed Instance on App Service overview (preview) ...main/articles/app-service/overview-managed-instance.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows-specific features and tools, such as PowerShell install scripts, registry modifications, IIS Manager, RDP, and Windows services. All configuration and troubleshooting examples use Windows paradigms, with no Linux equivalents or examples provided. The product itself is described as Windows-only, and Linux users are directed to other hosting options without parity in features or examples.
Recommendations
  • Clearly state Windows-only scope at the top of the page to set expectations.
  • Where possible, provide Linux or cross-platform alternatives for configuration, scripting, and diagnostics.
  • If Linux support is planned, outline roadmap and expected parity features.
  • Include links to equivalent Linux documentation for similar tasks (e.g., Bash scripts for configuration, Linux diagnostics tools).
  • Present hosting options in a way that does not prioritize Windows patterns by default, but instead clarifies platform-specific capabilities.
GitHub Create Pull Request
App Service Operating System Functionality in Azure App Service ...articles/app-service/operating-system-functionality.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily focused on Windows-specific concepts, tools, and environment variables (e.g., %SystemDrive%, %ResourceDrive%, IIS, ASP.NET, application pool identity, registry access, COM components, PowerShell). Linux is mentioned only briefly and generically, with no concrete examples, environment variables, or equivalent tooling discussed. There are no Linux/macOS-specific examples or guidance, and Windows terminology and patterns dominate throughout.
Recommendations
  • Add equivalent Linux/macOS examples for file paths, environment variables, and storage (e.g., $HOME, /tmp, /var/log).
  • Discuss Linux-specific runtime behaviors, such as permissions, process isolation, and logging.
  • Include Linux container details beyond the generic statement about root access; provide examples of common tasks (file access, logging, diagnostics) in Linux environments.
  • Mention Linux equivalents for Windows tools (e.g., shell scripts instead of PowerShell, Linux diagnostic/logging tools).
  • Balance the documentation structure so Linux and Windows are treated equally, with parallel sections/examples.
GitHub Create Pull Request
App Service Tutorial: ASP.NET app with Azure SQL Database ...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The tutorial is heavily oriented toward Windows users, with all instructions and screenshots based on Visual Studio for Windows. Steps for publishing, configuring, and managing the app and database are exclusively described using Windows tools (Visual Studio, SQL Server Object Explorer, Package Manager Console, PowerShell/sqlcmd). There are no Linux/macOS equivalents or alternative workflows provided, and Windows-specific options (e.g., 'Azure App Service (Windows)') are selected by default. This creates friction for developers using Linux or macOS, who cannot follow the tutorial as written.
Recommendations
  • Add instructions and screenshots for Visual Studio Code and/or CLI-based workflows (e.g., Azure CLI, dotnet CLI) that work on Linux/macOS.
  • Provide examples for publishing and managing the app using cross-platform tools (e.g., Azure CLI, VS Code, GitHub Actions).
  • Include SQL connection and migration steps using platform-agnostic tools (e.g., Azure Data Studio, sqlcmd for Linux/macOS, or direct SQL scripts).
  • Mention and link to Linux/macOS setup guides for .NET development and Azure deployment.
  • Clearly indicate which steps are Windows-only and offer alternatives for other platforms.
GitHub Create Pull Request
App Service Configure an App Service App ...ocs/blob/main/articles/app-service/configure-common.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates several forms of Windows bias. Many advanced configuration features (default documents, virtual directories, handler mappings) are explicitly Windows-only, with no Linux equivalents or alternatives described. PowerShell examples are provided for every operation, and Windows-specific tools and concepts (IIS, applicationHost.config, D:\home paths) are referenced without Linux parity. In some cases, Windows features are described first or in more detail, and Linux limitations are mentioned only as notes. Bulk editing via JSON is supported in CLI but not PowerShell, but this is noted. Overall, Linux users are left without guidance for several critical configuration scenarios.
Recommendations
  • Clearly indicate Windows-only features at the start of relevant sections and provide links to Linux alternatives or workarounds where possible.
  • For features unavailable on Linux (default documents, handler mappings, virtual directories), suggest Linux-native approaches (e.g., configuring startup commands, using container entrypoints, web server config files).
  • Add Linux-specific examples and explanations for common configuration tasks, especially where the workflow differs from Windows.
  • Balance PowerShell and CLI coverage, and ensure CLI examples are presented first or equally, as CLI is cross-platform.
  • Where a feature is not available on Linux, explicitly state this and offer guidance on how to achieve similar outcomes using Linux tools or conventions.
GitHub Create Pull Request
App Service Configure gateway-required virtual network integration for your app ...service/configure-gateway-required-vnet-integration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows, as gateway-required virtual network integration is explicitly stated to only work for Windows plans. Linux apps are not supported, and there are no Linux-specific instructions, examples, or troubleshooting guidance. All command-line examples and troubleshooting steps use Windows tools (e.g., PowerShell's Test-NetConnection, netstat -aon), with no mention of Linux equivalents. This creates a significant barrier for Linux users, who cannot use this feature or follow the guide.
Recommendations
  • Clearly state at the beginning that gateway-required virtual network integration is not supported for Linux apps, and direct Linux users to regional virtual network integration.
  • Provide parity documentation for regional virtual network integration with Linux-specific instructions, examples, and troubleshooting steps.
  • Where troubleshooting or connectivity testing is discussed, include Linux equivalents (e.g., nc, ss, netcat, dig) alongside Windows tools.
  • Add a comparison table highlighting feature support for Windows vs. Linux plans to help users quickly determine applicability.
  • Ensure all relevant links to Linux-compatible features are prominent and easy to find.
GitHub Create Pull Request
App Service Configure Managed Instance on Azure App Service (Preview) ...ain/articles/app-service/configure-managed-instance.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric: all configuration examples use PowerShell scripts (Install.ps1), only Windows Installer (MSI), IIS, COM, and registry keys are mentioned, and all operational details (RDP, registry, file paths) are Windows-specific. There are no Linux/macOS equivalents, nor any mention of cross-platform support or alternative scripting languages. The FAQ and all technical steps reinforce Windows-only usage, making the guide inaccessible for Linux/macOS users.
Recommendations
  • Clearly state Windows-only support in the introduction and prerequisites.
  • If Linux support is planned, provide equivalent examples for Linux (e.g., Bash scripts, Linux storage mounts, Linux configuration patterns).
  • Add a comparison table showing feature parity or gaps between Windows and Linux Managed Instance (if applicable).
  • Mention alternatives for Linux users, or link to Linux-specific documentation if available.
  • Avoid using Windows terminology (e.g., registry, MSI, RDP) without noting their absence or alternatives on Linux.
GitHub Create Pull Request
App Service Quickstart: Deploy Managed Instance on Azure App Service (Preview) ...in/articles/app-service/quickstart-managed-instance.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. The configuration (install) script is exclusively provided as a PowerShell script targeting Windows (Install.ps1), with explicit instructions to copy fonts to C:\Windows\Fonts and modify the Windows registry. There are no Linux/macOS equivalents or examples for configuration scripts, nor any mention of how to achieve similar functionality on non-Windows platforms. The runtime stack and sample app are .NET (ASPNET V4.8), which is Windows-centric, and the font installation process is described only for Windows. Overall, Linux/macOS users are left without guidance for adapting these steps.
Recommendations
  • Provide equivalent configuration (install) script examples for Linux (e.g., Bash scripts to copy fonts to /usr/share/fonts and update font cache).
  • Clarify whether Managed Instance supports Linux-based plans and, if so, document the differences in configuration script handling.
  • Include sample app deployment instructions for Linux runtimes (e.g., Node.js, Python, .NET Core) if supported.
  • Explicitly state platform limitations and offer workarounds or alternatives for non-Windows users.
  • Add notes or links to documentation on how to install fonts and dependencies on Linux/macOS environments.
GitHub Create Pull Request
App Service Develop and deploy WebJobs using Visual Studio .../main/articles/app-service/webjobs-dotnet-deploy-vs.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented around Visual Studio and Windows-specific workflows, with all examples and instructions assuming use of Visual Studio on Windows. There is no mention of Linux/macOS alternatives, nor are cross-platform tools or command-line approaches covered in detail. The use of Solution Explorer, right-click context menus, and Visual Studio-specific dialogs excludes Linux/macOS users who cannot run Visual Studio natively.
Recommendations
  • Add instructions for developing and deploying WebJobs using cross-platform tools such as VS Code, the Azure CLI, or GitHub Actions.
  • Include Linux/macOS-specific guidance for project setup, deployment, and configuration.
  • Provide command-line examples for creating, configuring, and deploying WebJobs without relying on Visual Studio.
  • Mention and link to any available cross-platform templates or SDK usage patterns.
  • Clarify which steps are Windows-only and offer alternatives for non-Windows environments.
GitHub Create Pull Request
App Service Tutorial for event-driven background processing with the WebJobs SDK ...b/main/articles/app-service/webjobs-sdk-get-started.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows and Visual Studio workflows. All examples and instructions assume the use of Visual Studio 2022 on Windows, with no mention of Linux/macOS alternatives or cross-platform tools. Package installation is shown only via PowerShell commands in the Visual Studio Package Manager Console, and project setup steps rely on Visual Studio UI elements. There are no instructions for using .NET CLI, VS Code, or other cross-platform approaches. This creates friction for Linux/macOS users and may prevent them from following the tutorial.
Recommendations
  • Add instructions for creating and managing projects using the .NET CLI (dotnet new, dotnet add package, etc.), which works on all platforms.
  • Include examples for installing NuGet packages via the CLI, not just PowerShell/Visual Studio.
  • Mention and provide steps for using VS Code or other cross-platform editors.
  • Clarify that the SDK and code are cross-platform, and provide explicit guidance for Linux/macOS users.
  • Reorder or parallelize instructions so that Windows and Linux/macOS workflows are presented equally.
  • Replace or supplement screenshots and UI references with CLI commands where possible.
GitHub Create Pull Request
App Service Discover .NET Apps to Azure App Service ...cles/app-service/app-service-migration-discover-net.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page focuses exclusively on discovering ASP.NET web apps hosted on IIS servers, which are Windows-specific. There is no mention of Linux-based hosting environments (e.g., Apache, Nginx, Kestrel), nor are Linux discovery tools or patterns discussed. All examples and capabilities center on Windows/IIS, and Linux alternatives are absent.
Recommendations
  • Include information about discovering .NET web apps hosted on Linux environments (e.g., Kestrel, Apache, Nginx).
  • Document whether Azure Migrate supports discovery for Linux-hosted .NET apps, and provide relevant instructions if available.
  • Add examples and dashboard screenshots for Linux scenarios, if supported.
  • Clarify limitations or provide links to Linux-specific migration resources if discovery is Windows-only.
GitHub Create Pull Request
App Service Develop and deploy WebJobs using Visual Studio .../main/articles/app-service/webjobs-dotnet-deploy-vs.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Visual Studio workflows, which are primarily Windows-centric. All examples and instructions reference Visual Studio UI elements (Solution Explorer, dialog boxes, wizards) and do not mention or provide alternatives for Linux/macOS users. There are no instructions for developing or deploying WebJobs using cross-platform tools (such as VS Code, CLI, or other IDEs), nor are Linux-specific patterns or examples provided.
Recommendations
  • Add instructions for developing and deploying WebJobs using cross-platform tools such as Azure CLI, PowerShell Core, or VS Code.
  • Include examples for Linux/macOS users, such as using dotnet CLI commands to publish WebJobs.
  • Clarify which steps are Windows-only and provide equivalent steps for other platforms where possible.
  • Mention alternative editors and workflows (e.g., VS Code, JetBrains Rider) and how to accomplish the same tasks outside Visual Studio.
  • Provide links to relevant Linux/macOS documentation for Azure WebJobs deployment.
GitHub Create Pull Request
App Service Tutorial: ASP.NET app with Azure SQL Database ...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The tutorial is heavily oriented toward Windows and Visual Studio workflows, with all examples and instructions assuming use of Visual Studio on Windows. Azure App Service (Windows) is selected by default, and all tooling references (e.g., SQL Server Object Explorer, NuGet Package Manager Console, Package Manager Console, log streaming) are Visual Studio-specific. There are no instructions or examples for Linux/macOS users, nor for cross-platform tools like VS Code, CLI, or Azure Portal alternatives.
Recommendations
  • Add instructions for deploying from Linux/macOS, using cross-platform tools like VS Code, Azure CLI, or the Azure Portal.
  • Include examples for publishing the ASP.NET app using the dotnet CLI and Azure CLI, not just Visual Studio.
  • Provide guidance for configuring Azure App Service (Linux) and highlight differences.
  • Offer SQL Database connection and migration steps using platform-agnostic tools (e.g., sqlcmd, Azure Data Studio, or direct CLI commands) instead of only PowerShell/Visual Studio.
  • Clarify which steps are Windows-only and provide alternatives for other platforms.
  • Reorder examples so that platform-agnostic or Linux/macOS approaches are presented alongside or before Windows-specific instructions.
GitHub Create Pull Request
App Service Use Private Endpoints for Apps ...main/articles/app-service/overview-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows is mentioned first in the list of supported platforms for private endpoints, and the related content section lists Azure PowerShell as a primary method for creating private endpoints, with no explicit Linux shell or Bash examples. The use of Windows-centric terminology and tools (e.g., PowerShell, references to Windows DNS patterns) is more prominent than Linux equivalents, and Linux-specific instructions or examples are missing or less visible.
Recommendations
  • Explicitly provide Linux/Bash examples alongside PowerShell, especially in quickstart and scripting sections.
  • List Linux and Windows platforms together or alternate their order to avoid Windows-first perception.
  • Include references to Linux-native tools and workflows (e.g., Bash, curl, dig for DNS) where relevant.
  • Clarify that all CLI instructions (e.g., Azure CLI) are cross-platform, and provide sample commands for both Windows and Linux environments.
  • Add troubleshooting notes or examples for common Linux scenarios (e.g., modifying /etc/hosts, using Linux DNS tools).
GitHub Create Pull Request
App Service Quickstart: Run a Custom Container on App Service ...in/articles/app-service/quickstart-custom-container.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page displays a Windows bias by listing Windows-specific pivots (Visual Studio, PowerShell, CLI) before their Linux equivalents, and by providing dedicated sections for Windows tools (PowerShell, Visual Studio) while Linux pivots are limited to Visual Studio Code and Azure Portal. There is no mention of Linux command-line or shell examples (e.g., Bash), and Windows tooling (PowerShell, Visual Studio) is given more prominence and variety than Linux alternatives.
Recommendations
  • Add Linux shell (Bash) and CLI examples alongside Windows PowerShell and CLI pivots.
  • Ensure Linux pivots are presented with equal prominence and order as Windows pivots.
  • Include Linux-native tools and workflows (e.g., Docker CLI, Bash scripts) in the quickstart.
  • Provide parity in the number and detail of examples for both Windows and Linux environments.
  • Review and balance the use of platform-specific terminology and tooling throughout the documentation.
GitHub Create Pull Request
App Service Overview of Azure App Service .../azure-docs/blob/main/articles/app-service/overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias, especially in the 'Managed Instance on App Service (preview)' section, which focuses exclusively on Windows-specific technologies (COM, registry, MSI, drive mapping, PowerShell scripts, RDP). Windows tools and patterns (PowerShell, RDP, registry, drive letters) are mentioned without Linux equivalents or alternatives. Linux and container support are only referenced as not supported in Managed Instance, and no Linux-specific examples, tools, or patterns are provided elsewhere on the page.
Recommendations
  • Provide Linux-specific examples and scenarios, especially for deployment, configuration, and diagnostics.
  • Mention Linux tools (e.g., Bash, SSH, systemd) alongside Windows tools like PowerShell and RDP.
  • Clarify which features are available on Linux and how to achieve similar outcomes (e.g., startup scripts, diagnostics) on Linux-based App Service plans.
  • Include parity tables or explicit guidance for Linux users where features differ or are unavailable.
  • Ensure that command-line tool references (Azure CLI, Azure PowerShell) include both Windows and Linux usage patterns.
GitHub Create Pull Request
App Service Tutorial: ASP.NET app with Azure SQL Database ...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected 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 a Windows environment. There are no Linux or cross-platform alternatives provided for key steps such as publishing, database management, or command-line operations. Windows-specific tools (Visual Studio, SQL Server Object Explorer, PowerShell, Package Manager Console) are used exclusively, and Azure App Service (Windows) is selected by default. No mention is made of Linux-based development environments, deployment from Linux, or using cross-platform tools like Azure CLI or VS Code.
Recommendations
  • Add instructions and examples for deploying ASP.NET apps from Linux environments, including using VS Code and the Azure CLI.
  • Provide equivalent steps for publishing to Azure App Service (Linux), including screenshots and configuration details.
  • Include cross-platform command-line examples (bash, Azure CLI) for database setup, migrations, and managed identity configuration.
  • Mention and demonstrate how to use SQL tools available on Linux (e.g., sqlcmd, Azure Data Studio) for database management.
  • Clarify which steps are Windows-specific and offer alternatives for macOS and Linux users.
  • Reference cross-platform .NET development workflows and tooling where possible.
GitHub Create Pull Request
App Service Customize Sign-ins and Sign-outs ...vice/configure-authentication-customize-sign-in-out.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a dedicated section for Windows apps, detailing how to configure authorization via IIS and web.config, but does not offer equivalent guidance or examples for Linux-based apps. Windows-specific tools (IIS, web.config) are mentioned exclusively, and Linux alternatives are not discussed or referenced. The overall flow and examples are platform-neutral except for the authorization section, which is Windows-centric.
Recommendations
  • Add equivalent guidance for Linux-based apps, such as how to implement authorization using common web servers (e.g., Nginx, Apache) or application-level code.
  • Include Linux-specific configuration examples for restricting access, such as sample code or configuration for popular frameworks (Node.js, Python, etc.) running on Linux App Service.
  • Explicitly mention that Linux apps require application-level authorization and provide links or code samples for common scenarios.
  • Balance the documentation by presenting both Windows and Linux approaches side-by-side where platform-specific configuration is required.
GitHub Create Pull Request
App Service Configure a Custom Container ...ain/articles/app-service/configure-custom-container.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific concepts, tools, and examples (such as PowerShell commands, IIS, .NET Framework, Windows Server base images, and C:\home paths) are often presented first or in greater detail. PowerShell examples are provided alongside Bash, but sometimes with more explanation. Windows-specific features (like machine key injection, group managed service accounts, and memory/core customization) receive dedicated sections, while Linux equivalents are less emphasized or missing. Some advanced configuration and troubleshooting guidance is richer for Windows containers. Linux coverage is present, but sometimes less detailed or appears after Windows content.
Recommendations
  • Ensure Linux examples and guidance are provided with equal detail and prominence as Windows, especially for advanced scenarios (e.g., memory/core limits, diagnostic logs, environment variable injection).
  • Present Linux and Windows instructions in parallel or side-by-side, rather than Windows-first ordering.
  • Expand Linux-specific troubleshooting and configuration sections to match the depth of Windows coverage (e.g., persistent storage, diagnostic logs, SSH access, environment variable handling).
  • Where PowerShell is used, ensure Bash/Linux CLI equivalents are always shown and explained equally.
  • Highlight Linux-specific base images, patterns, and best practices in the same way as Windows (e.g., recommend official Linux base images for .NET, Node, Python, etc.).
  • Review and update references to Windows-only tools or paths (e.g., C:\home) to clarify Linux equivalents (/home), and avoid implying Windows as the default.
GitHub Create Pull Request
App Service Configure ASP.NET Core apps .../articles/app-service/configure-language-dotnetcore.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific instructions and tools (such as Visual Studio and Kudu) are introduced first and receive more detailed attention, while Linux equivalents are mentioned later or in separate pivots. Windows tools like Kudu and PowerShell are referenced before Linux alternatives, and Visual Studio is presented as the default publishing tool. Linux instructions are present but sometimes less detailed or introduced after Windows steps.
Recommendations
  • Ensure that Linux instructions are presented with equal prominence and detail as Windows instructions, possibly by alternating which platform is shown first in examples.
  • Provide Linux-native tooling examples (such as SSH, Bash, or VS Code Remote) alongside or before Windows tools like Kudu and PowerShell.
  • Expand Linux-specific sections to match the depth of Windows instructions, including troubleshooting, deployment, and configuration scenarios.
  • Where Visual Studio is referenced, also mention cross-platform alternatives (such as VS Code, JetBrains Rider, or CLI workflows) for Linux users.
  • Review all examples to ensure Linux parity, especially in areas like build automation, diagnostics, and environment variable configuration.
GitHub Create Pull Request
App Service Disable Basic Authentication for Deployment ...n/articles/app-service/configure-basic-auth-disable.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It frequently references Windows-centric deployment tools and patterns, such as Web Deploy (MSDeploy), Visual Studio, and FTP, which are traditionally associated with Windows environments. These tools are mentioned before or instead of Linux-native equivalents. There is a lack of explicit Linux or cross-platform deployment examples (e.g., SFTP, rsync, SCP, or Linux-specific CLI workflows), and troubleshooting guidance is focused on Windows agents. The documentation does not provide parity for Linux users in terms of deployment methods, troubleshooting, or alternative tool recommendations.
Recommendations
  • Include Linux-native deployment examples (e.g., SFTP, SCP, rsync) and clarify their support or limitations with Azure App Service.
  • Add troubleshooting guidance for Linux agents and self-hosted runners, not just Windows agents.
  • Mention cross-platform tools and workflows (such as VS Code, Git CLI, or Azure CLI on Linux/macOS) alongside Windows tools.
  • Provide parity in documentation for both Windows and Linux environments, including screenshots and step-by-step instructions.
  • Explicitly state which deployment methods and authentication mechanisms are supported or unsupported on Linux and macOS.
GitHub Create Pull Request
App Service Configure ASP.NET Apps ...les/app-service/configure-language-dotnet-framework.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-specific tools and patterns, such as Visual Studio publishing, Kudu with CMD/PowerShell, and referencing Windows file paths. There are no Linux-specific examples or instructions, and Windows deployment methods and tooling are mentioned exclusively or before any Linux alternatives. The lack of parity for Linux users is evident, especially in sections about runtime version discovery and deployment.
Recommendations
  • Add equivalent Linux instructions and examples, such as using Bash in Kudu or SSH for Linux-based App Service environments.
  • Include Linux file paths and commands for listing .NET Framework/Mono assemblies in Linux containers.
  • Mention Linux deployment tools and patterns (e.g., dotnet CLI, VS Code, GitHub Actions) alongside Visual Studio.
  • Clarify which steps apply to Windows, Linux, or both, and provide links to Linux-specific documentation where relevant.
  • Ensure that environment variable access and diagnostic logging examples include Linux container scenarios.
GitHub Create Pull Request
App Service Authentication Types by Deployment Methods ...in/articles/app-service/deploy-authentication-types.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows such as Azure PowerShell, Visual Studio, and migration assistants tailored for Windows environments. Examples and references for deployment methods are heavily skewed towards Windows tools, with PowerShell and Visual Studio featured prominently and before cross-platform alternatives. There is a lack of explicit Linux or macOS command-line examples, and no mention of Linux-specific deployment patterns or tools (e.g., Bash, SSH, SCP, rsync, or Linux package managers). The documentation does not provide parity for Linux users in terms of guidance, examples, or tool recommendations.
Recommendations
  • Add Linux/macOS-specific deployment examples using Bash, native SSH, SCP, or rsync commands.
  • Include references to Linux-friendly tools and workflows, such as deploying from a Linux terminal or using Linux-based CI/CD pipelines.
  • Provide parity in documentation for Visual Studio Code on Linux/macOS, including screenshots and step-by-step guides.
  • Explicitly mention cross-platform compatibility for Azure CLI and clarify any differences in authentication or usage on Linux.
  • Add guidance for deploying Java, Python, Node.js, and other non-Windows-centric stacks from Linux environments.
  • Ensure migration tools and scripts have Linux equivalents or alternatives, and document their usage.
GitHub Create Pull Request
← Previous Page 1 of 10 Next →