App Service

432
Total Pages
240
Linux-Friendly Pages
192
Pages with Bias
44.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2121 issues found
Showing 251-275 of 2121 flagged pages
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-10 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 oriented toward Windows development environments. All examples and instructions assume the use of Visual Studio 2022 on Windows, with steps referencing Windows-specific UI elements and workflows. Package installation is exclusively demonstrated using the PowerShell-based Package Manager Console, with no mention of Linux or cross-platform alternatives such as .NET CLI. There is no guidance for Linux or macOS users, nor any mention of equivalent tools or workflows for those platforms.
Recommendations
  • Add instructions and examples for using the .NET CLI (dotnet commands) to install NuGet packages, which work on Linux, macOS, and Windows.
  • Include guidance for setting up and running the project in Visual Studio Code or JetBrains Rider, which are cross-platform IDEs.
  • Provide alternative steps for project creation, building, and publishing using command-line tools available on Linux and macOS.
  • Mention that the WebJobs SDK and related tooling are supported on non-Windows platforms, and clarify any platform-specific limitations.
  • Add screenshots or descriptions for Linux/macOS environments where relevant (e.g., file system operations, environment variable configuration).
  • Explicitly note differences in local development experience between Windows and Linux/macOS, such as the absence of the Azure Storage Emulator and alternatives like Azurite.
GitHub Create Pull Request
App Service Use the Azure WebJobs SDK ...s/blob/main/articles/app-service/webjobs-sdk-how-to.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 exhibits Windows bias in several ways: examples and configuration paths use Windows conventions (e.g., c:\data\import), there is no mention of Linux-specific patterns or cross-platform considerations, and Windows-centric tools (such as Visual Studio) are referenced without Linux alternatives. No Linux-specific instructions, examples, or troubleshooting are provided, and all code snippets and file paths assume a Windows environment.
Recommendations
  • Add Linux-specific examples, such as using Linux-style file paths (e.g., /data/import) in binding configurations.
  • Include instructions for developing and running WebJobs on Linux, such as using VS Code, JetBrains Rider, or command-line .NET tools.
  • Mention cross-platform compatibility explicitly, and provide troubleshooting tips for common Linux issues (e.g., file permissions, environment variable conventions).
  • Reference Linux equivalents for Windows tools (e.g., Azure CLI usage on bash, deployment via GitHub Actions, etc.).
  • Ensure all configuration and code samples are platform-neutral or provide both Windows and Linux variants.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md ...s/app-service/app-service-configure-premium-v4-tier.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 several Windows biases: Windows is mentioned first in availability, and Windows-specific tools (PowerShell) are featured alongside Azure CLI, but there are no Linux shell (bash) or scripting examples. The automation section provides Azure PowerShell scripts but omits Linux-native scripting approaches. The portal instructions and screenshots are Windows-centric, and Linux-specific guidance is limited to a single CLI flag for SKU availability. There are no examples using Linux command-line tools or shell scripting, nor is there parity in step-by-step instructions for Linux users.
Recommendations
  • Add bash shell scripting examples for automating Premium v4 app creation and scaling, alongside PowerShell.
  • Include explicit instructions and screenshots for Linux users, such as using Azure CLI in a Linux terminal.
  • Present Linux and Windows options together, or alternate which is shown first, to avoid Windows-first ordering.
  • Clarify any platform-specific differences in the portal experience for Linux-hosted apps.
  • Provide parity in troubleshooting and error-handling steps for Linux environments.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-managed-certificate-changes-july-2025.md ...e/app-service-managed-certificate-changes-july-2025.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a PowerShell script as the only automation example for identifying impacted Traffic Manager endpoints, with no equivalent Bash, Azure CLI, or Linux-native instructions. The step-by-step guidance for running the script assumes a Windows/PowerShell environment, and there are no Linux or cross-platform alternatives mentioned. This prioritizes Windows tooling and patterns, potentially excluding users on Linux or macOS.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for identifying impacted Traffic Manager endpoints, ensuring Linux and macOS users have a first-class experience.
  • When referencing automation scripts, offer both PowerShell and Bash/Azure CLI examples side-by-side, or clearly indicate cross-platform alternatives.
  • Explicitly mention that the PowerShell script can be run in cross-platform environments (e.g., PowerShell Core on Linux/macOS) if applicable, and provide installation instructions if needed.
  • Review all step-by-step instructions to ensure they are not Windows-centric; include notes or links for Linux/macOS users where differences exist.
  • Encourage community contributions for Linux-native tooling or scripts if official support is not available.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-linux-open-ssh-session.md ...ticles/app-service/configure-linux-open-ssh-session.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Windows Example Linux Tools Linux First
Summary
The documentation provides detailed, step-by-step instructions and command-line examples for connecting to Linux containers via SSH, including Azure CLI usage and Linux SSH commands. In contrast, Windows containers are only mentioned briefly, with no equivalent command-line or PowerShell examples, and it is stated that SSH via Azure CLI is not supported for Windows. Linux tools and patterns (e.g., bash, top, ssh) are used exclusively in the examples, and the Linux workflow is presented in much greater detail.
Recommendations
  • Add equivalent step-by-step instructions for connecting to Windows containers, including any available command-line or PowerShell workflows.
  • Clarify or expand on browser-based SSH access for Windows containers, possibly with screenshots and troubleshooting tips.
  • If Azure CLI or PowerShell support is unavailable for Windows containers, explicitly state this and suggest alternative approaches or workarounds.
  • Include Windows-specific tools or commands (e.g., PowerShell, Windows SSH client) where relevant, and provide parity in example depth and clarity.
  • Ensure both Linux and Windows container sections have similar structure, detail, and actionable guidance.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-azure-pipelines.md ...ob/main/articles/app-service/deploy-azure-pipelines.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific deployment methods (Web Deploy) are described in detail, with explicit instructions to use Windows agents and references to IIS and web.config for Node.js on Windows. Linux deployment options are mentioned but not explored in equivalent depth, and examples for Linux-specific deployment methods (such as using Kudu or zip deploy) are missing. Windows agent selection is often shown first or exclusively in key examples, and troubleshooting sections focus on Windows agent issues. There is a lack of parity in examples and troubleshooting for Linux agents and deployment patterns.
Recommendations
  • Provide equivalent Linux deployment examples, such as using zip deploy or Kudu REST API, and clarify when these are preferred over Web Deploy.
  • Include troubleshooting sections for common Linux agent issues (e.g., file permissions, package paths, environment variables).
  • When listing agent specifications, present Linux options first or equally (e.g., 'ubuntu-latest' before or alongside 'windows-latest').
  • Add examples for deploying Node.js, Python, and Java apps specifically to Linux App Service, including configuration nuances.
  • Discuss Linux-specific build and deployment patterns, such as using shell scripts, environment variables, and file transforms.
  • Clarify which deployment tasks and features are supported on Linux agents and App Service on Linux, and highlight any limitations.
  • Avoid language that assumes Windows as the default platform (e.g., 'If your agent isn't running Windows...' could be rephrased to address both platforms).
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-managed-instance.md ...ain/articles/app-service/configure-managed-instance.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 biased toward Windows, with all examples, configuration scripts, and tooling focused exclusively on Windows Server and PowerShell. There is no mention of Linux support, nor are any Linux equivalents or examples provided. Windows-specific features (registry keys, RDP, MSI installers, IIS configuration) are discussed in detail, while Linux alternatives are absent.
Recommendations
  • Clarify whether Managed Instance supports Linux workloads. If not, state this explicitly at the top of the documentation.
  • If Linux support is planned or available, provide equivalent examples for Linux, such as Bash scripts, Linux storage mount patterns, and configuration via Linux tools.
  • Include documentation for Linux-specific configuration (e.g., environment variables, file permissions, package managers like apt/yum).
  • Offer parity in remote access guidance (e.g., SSH instead of RDP/Bastion for Linux).
  • Discuss Linux-relevant security and troubleshooting practices.
  • If only Windows is supported, consider renaming sections and the product to make the Windows-only nature clear, reducing confusion for cross-platform users.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/getting-started.md ...docs/blob/main/articles/app-service/getting-started.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, especially in the .NET and Python sections. Windows-centric tools like Visual Studio and Azure PowerShell are listed before cross-platform or Linux alternatives. In several places, Windows examples or tabs are prioritized or exclusively mentioned, while Linux equivalents are less visible or omitted. The 'Next step' call-to-action also highlights a Windows-oriented technology (ASP.NET) over other stacks.
Recommendations
  • Ensure that Linux and cross-platform examples (e.g., CLI, Visual Studio Code) are presented before or alongside Windows-specific tools like Visual Studio and PowerShell.
  • Add explicit Linux examples and tabs where only Windows or PowerShell instructions are currently provided, especially in .NET and Python quickstarts.
  • Balance the order of tool recommendations so that Linux-friendly options are not consistently listed after Windows tools.
  • Include Linux deployment and management patterns (e.g., Bash, Azure CLI) in all relevant sections, not just as secondary options.
  • For 'Next step' actions, rotate or randomize the featured stack, or provide links for multiple stacks to avoid defaulting to Windows-centric technologies.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-configure-credentials.md ...n/articles/app-service/deploy-configure-credentials.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation presents command-line examples for Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) given its own tab and detailed usage. There are no explicit Linux shell or Bash examples, and the documentation does not mention Linux-specific tools or workflows. While Azure CLI is cross-platform, the absence of Linux/Bash-specific guidance and the prominence of PowerShell suggest a Windows bias.
Recommendations
  • Add explicit Bash/Linux shell examples where relevant, especially for credential management and Git operations.
  • Include notes or examples for Linux users, such as using Bash to escape special characters in usernames/passwords.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific caveats.
  • Consider adding a 'Linux' or 'Bash' tab alongside CLI and PowerShell for parity.
  • Mention Linux-native tools or workflows (e.g., using curl, sftp, or scp for FTP/S deployment) where appropriate.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/overview-certificates.md ...icles/app-service/environment/overview-certificates.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation displays a Windows bias in several areas. The per-app private client certificate method is explicitly limited to Windows code apps, with no Linux equivalent or workaround described. All example commands for certificate verification and creation use PowerShell, with no Linux shell or OpenSSL alternatives. The instructions for checking certificate installation reference the Kudu PowerShell console only, omitting Linux scenarios. The documentation does mention that the recommended Root Certificate API method works for both Windows and Linux, but practical examples and troubleshooting for Linux are missing or secondary.
Recommendations
  • Add Linux-specific instructions and examples for per-app certificate management, or clarify Linux limitations and alternatives.
  • Provide equivalent Linux shell commands (e.g., using OpenSSL) for certificate creation, export, and verification.
  • Include guidance for checking certificate installation on Linux apps, such as using SSH, App Service SSH console, or Linux filesystem paths.
  • Explicitly state any feature parity gaps and suggest workarounds for Linux users.
  • Ensure that examples and troubleshooting steps are presented for both Windows and Linux platforms, not just Windows/PowerShell.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-per-app.md ...blob/main/articles/app-service/manage-scale-per-app.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only PowerShell examples for per-app scaling, with no equivalent examples for Linux-native tools (such as Bash, Azure CLI, or REST API). PowerShell is primarily a Windows-centric tool, and its exclusive use may disadvantage Linux users. The ARM template section is platform-neutral, but the lack of Linux command-line examples and the focus on PowerShell indicate a Windows bias.
Recommendations
  • Add Azure CLI examples for all PowerShell commands shown, demonstrating equivalent functionality for Linux/macOS users.
  • Include Bash script snippets where appropriate, especially for configuring app settings.
  • Mention REST API options for users who prefer platform-agnostic automation.
  • Explicitly state that PowerShell examples are cross-platform (if true), or clarify any platform limitations.
  • Reorder sections to present Azure CLI and PowerShell examples side by side, or alternate which comes first.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-asp-net-migration.md .../articles/app-service/app-service-asp-net-migration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All migration tools and examples focus exclusively on Windows environments, specifically IIS servers and Windows OS. PowerShell scripts are the only automation examples provided, with no mention of Bash, Linux CLI, or Linux-native migration tools. There is no guidance for migrating .NET apps hosted on Linux servers or using Linux web servers (e.g., Apache, Nginx). The documentation repeatedly references Windows-specific tools and patterns before any consideration of Linux alternatives.
Recommendations
  • Add examples and guidance for migrating .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel) to Azure App Service.
  • Include Linux-native migration tools or scripts, such as Bash or Python, and provide parity with PowerShell examples.
  • Mention and document any Azure migration tools that support Linux environments, or clarify limitations if none exist.
  • Provide a comparison table of migration approaches for both Windows and Linux environments.
  • Explicitly state platform prerequisites and limitations for each tool, so Linux users are aware of their options.
  • Highlight containerization options for Linux-hosted .NET apps, not just Windows Containers.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-hybrid-connections.md ...articles/app-service/app-service-hybrid-connections.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows tools and patterns (such as PowerShell commands, GUI instructions, and MSI installers) are mentioned first and in greater detail than their Linux equivalents. Troubleshooting and connectivity checks use PowerShell examples without Linux alternatives. The GUI for Hybrid Connection Manager is only available on Windows, and the legacy version is Windows-only. Some instructions (e.g., port configuration, service management) are more detailed for Windows, and Linux steps are sometimes less explicit or referenced as secondary. In troubleshooting, connectivity tests are shown only for Windows/PowerShell, with no Linux command-line equivalents provided.
Recommendations
  • Provide Linux command-line equivalents for all PowerShell examples (e.g., use 'nc', 'telnet', or 'curl' for connectivity tests).
  • Ensure troubleshooting steps include both Windows and Linux instructions, especially for network and DNS checks.
  • Present Windows and Linux instructions in parallel or side-by-side, rather than Windows-first.
  • Expand Linux installation and management instructions to match the detail provided for Windows, including service management and upgrade notifications.
  • Clarify any feature gaps (such as GUI availability) and suggest Linux-friendly alternatives where possible.
  • Include more Linux screenshots and examples to balance the visual representation.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-undelete.md ...blob/main/articles/app-service/app-service-undelete.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias by exclusively providing PowerShell-based examples and instructions for restoring deleted Azure App Service apps. There are no CLI (az), Bash, or Linux-native instructions, and all command-line guidance is centered around PowerShell cmdlets, which are most commonly used on Windows. The documentation does not mention or prioritize Linux-friendly tools or workflows, nor does it provide parity for users who prefer Bash, Azure CLI, or other cross-platform approaches.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for all PowerShell cmdlet instructions.
  • Include Bash script examples for common restore scenarios.
  • Explicitly mention that PowerShell cmdlets can be run cross-platform (if true), or provide guidance for Linux/macOS users on how to install and use Azure PowerShell.
  • Reorder sections or provide parallel instructions so that Linux-friendly tools (Azure CLI, Bash) are presented alongside or before PowerShell examples.
  • Clarify any limitations or differences in restore functionality between platforms (Windows, Linux, macOS) if applicable.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-dotnet-sqldatabase.md ...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. All examples and instructions use Visual Studio (Windows-only), reference Windows-specific Azure App Service hosting, and rely on Windows tools like SQL Server Object Explorer and PowerShell/Package Manager Console. There are no Linux or cross-platform alternatives provided for app deployment, database management, or command-line operations.
Recommendations
  • Add instructions and examples for deploying ASP.NET apps using cross-platform tools such as the Azure CLI, .NET CLI, and VS Code.
  • Include Linux hosting options for Azure App Service (e.g., 'Azure App Service (Linux)') and provide guidance for selecting and configuring them.
  • Provide equivalent steps for database management using Azure CLI, az sql commands, or Data Studio, rather than relying solely on Visual Studio and SQL Server Object Explorer.
  • Replace or supplement PowerShell and Package Manager Console commands with .NET CLI and Bash equivalents.
  • Explicitly mention platform differences and provide links to Linux/macOS-specific documentation where relevant.
  • Ensure screenshots and UI instructions are not exclusively tied to Windows/Visual Studio.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-key-vault-references.md ...ticles/app-service/app-service-key-vault-references.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides both Azure CLI and Azure PowerShell examples for configuration tasks, but PowerShell examples are always presented alongside or immediately after CLI examples, with no mention of Linux-specific shell environments (e.g., Bash) or Linux-native tools. There is no explicit Linux example or guidance for Linux users, and the troubleshooting and portal navigation instructions are generic but do not address platform-specific differences. The documentation assumes familiarity with PowerShell, which is primarily a Windows tool, and does not provide parity for Linux users who may prefer Bash or other shells.
Recommendations
  • Add explicit Bash examples for all CLI commands, clarifying shell syntax differences where relevant.
  • Clearly indicate which commands and tools are cross-platform and provide guidance for Linux/macOS users where PowerShell is referenced.
  • Where PowerShell is used, offer equivalent Bash/CLI instructions, and clarify any platform-specific prerequisites or behaviors.
  • Include troubleshooting steps or links that address platform-specific issues for Linux and macOS users.
  • Review portal navigation instructions for any UI differences between platforms and document them as needed.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-discover-net.md ...cles/app-service/app-service-migration-discover-net.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation focuses exclusively on discovering ASP.NET web apps hosted on IIS servers within VMware environments, which are Windows-centric technologies. There are no examples, mentions, or guidance for discovering .NET apps running on Linux (e.g., Kestrel, Apache, Nginx) or for Linux-based hosting environments. All tooling and discovery patterns described are tailored to Windows/IIS, with no parity for Linux scenarios.
Recommendations
  • Add sections describing discovery of .NET web apps hosted on Linux environments (e.g., Kestrel, Apache, Nginx).
  • Include examples and guidance for discovering .NET apps on Linux VMs, containers, or physical servers.
  • Mention Linux-compatible discovery tools or clarify limitations if Azure Migrate appliance does not support Linux-hosted .NET apps.
  • Provide parity in dashboard features and error remediation guidance for Linux-hosted web apps.
  • Explicitly state platform support and limitations at the beginning of the article.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide.md ...rvice-web-nodejs-best-practices-and-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows-specific tooling and patterns, particularly IIS and iisnode, which are not available or relevant on Linux-based Azure App Service environments. All configuration and troubleshooting examples reference Windows concepts (e.g., web.config, named pipes, Win32 error codes, DLLs, Windows file paths), and there are no Linux equivalents or alternative instructions for Node.js apps running on Linux App Service. This creates a strong Windows bias and leaves Linux users without guidance.
Recommendations
  • Add equivalent sections for Node.js on Linux App Service, covering configuration, troubleshooting, and best practices (e.g., using PM2, systemd, or Kudu for process management).
  • Provide Linux-specific examples for log locations, error diagnosis, and configuration files (e.g., referencing app settings, environment variables, or startup scripts instead of web.config).
  • Mention that iisnode and related settings are only applicable to Windows-based App Service plans, and link to Linux documentation where appropriate.
  • Include troubleshooting steps for common Linux scenarios (e.g., file permissions, process crashes, out-of-memory errors) and how to access logs on Linux.
  • Ensure parity in recommendations for performance tuning, debugging, and monitoring on Linux (e.g., using Azure Monitor, Application Insights, or Linux-native tools).
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-customize-sign-in-out.md ...vice/configure-authentication-customize-sign-in-out.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Authorize or deny users' section, where configuration for fine-grained authorization is described only for Windows apps using IIS and web.config, with no Linux equivalent or alternative provided. Windows-specific tools (IIS, web.config) are mentioned exclusively, and the section is introduced as 'Server level (Windows apps only)', placing Windows solutions before any mention of Linux. Other sections generally use cross-platform Azure CLI examples, but the lack of Linux parity in authorization guidance is notable.
Recommendations
  • Provide equivalent guidance for Linux-based App Service apps, such as how to implement fine-grained authorization using common Linux web servers (e.g., Nginx, Apache) or middleware in popular frameworks.
  • Explicitly state how Linux users can achieve similar authorization outcomes, possibly with code samples or configuration examples.
  • Ensure that examples and instructions for platform-specific features are balanced, or clearly indicate when a feature is unavailable on Linux and suggest alternatives.
  • Consider adding a comparison table or section outlining differences and solutions for both Windows and Linux App Service environments.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-common.md ...ocs/blob/main/articles/app-service/configure-common.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. While it covers both Azure CLI and PowerShell, there is a notable emphasis on Windows-specific tools, features, and patterns. Many advanced configuration options (such as default documents, virtual directories, and handler mappings) are explicitly stated to be available only for Windows apps, with no Linux equivalents or workarounds provided. PowerShell examples are detailed and prominent, and Windows terminology (e.g., references to IIS, D:\home paths, and applicationHost.config) is used throughout. Linux-specific behaviors are mentioned only briefly, and Linux parity is not addressed for Windows-only features.
Recommendations
  • Clearly indicate feature parity (or lack thereof) between Windows and Linux App Service plans at the start of each relevant section.
  • Where features are Windows-only (e.g., default documents, handler mappings, virtual directories), provide explicit notes about the absence of these features on Linux, and suggest alternative approaches or workarounds for Linux users if possible.
  • Include Linux-specific examples and guidance, especially for common configuration tasks, to balance the heavy focus on PowerShell and Windows tools.
  • Avoid using Windows-centric terminology (such as D:\home paths or IIS-specific concepts) without clarifying their relevance or irrelevance to Linux users.
  • Add links or references to Linux App Service documentation or community resources for users seeking equivalent functionality.
  • Where PowerShell is used for advanced scenarios, provide Bash or cross-platform CLI equivalents where possible.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-gateway-required-vnet-integration.md ...service/configure-gateway-required-vnet-integration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is strongly Windows-centric: gateway-required virtual network integration is explicitly stated to only work for Windows plans, with Linux apps excluded. All troubleshooting and connectivity examples use Windows tools (PowerShell's Test-NetConnection, netstat), and there are no Linux equivalents or instructions. The documentation does not provide parity for Linux users, nor does it mention how to perform similar tasks on Linux platforms.
Recommendations
  • Clearly state Linux limitations at the beginning, but also provide guidance for Linux users on alternative solutions (e.g., regional VNet integration).
  • Include Linux command equivalents for troubleshooting (e.g., use 'nc', 'telnet', or 'ss' for TCP connectivity, 'netstat' or 'ss' for port listening, 'dig' or 'host' for DNS checks).
  • Where PowerShell examples are given, add corresponding Bash/Linux shell examples.
  • Add a section or callout for Linux users describing supported integration methods and troubleshooting steps.
  • Ensure tool recommendations are cross-platform or provide alternatives for both Windows and Linux.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-basic-auth-disable.md ...n/articles/app-service/configure-basic-auth-disable.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 references Windows-specific tools and deployment patterns (such as Web Deploy and Visual Studio) without providing equivalent Linux alternatives or examples. Windows-centric terminology (e.g., 'Web Deploy', 'Visual Studio deployment') is used throughout, and Linux-native deployment tools or workflows are not mentioned. In the Azure Pipelines section, special attention is given to Windows agents and their requirements, while Linux agent details are minimal or absent. There are no explicit Linux command-line or scripting examples, and the documentation assumes familiarity with Windows-based deployment tools.
Recommendations
  • Add explicit Linux deployment examples, such as using SCP, SFTP, rsync, or Linux-native CI/CD tools.
  • Include references to Linux agents in Azure Pipelines, with details on authentication and deployment differences.
  • When mentioning Visual Studio or Web Deploy, also mention cross-platform alternatives (e.g., VS Code, Azure CLI, Git, or third-party tools) and provide parity in instructions.
  • Clarify which instructions or tools are cross-platform and which are Windows-only.
  • Provide troubleshooting and fallback guidance for Linux/macOS users, especially for scenarios where Windows tools are unavailable.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-custom-container.md ...ain/articles/app-service/configure-custom-container.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 content and examples (such as parent images, IIS/.NET integration, and PowerShell commands) are often presented first or in greater detail. PowerShell commands are provided alongside Bash, but some advanced configuration and diagnostic sections focus on Windows tools and patterns (e.g., Kudu, registry settings, System.ConfigurationManager). Linux equivalents are sometimes mentioned later or with less detail, and certain Linux-specific features (like multi-container Docker Compose) are relegated to notes or separate sections. Some advanced Windows features (machine key injection, compute core customization) lack direct Linux counterparts or examples.
Recommendations
  • Ensure Linux examples and instructions are presented with equal prominence and detail as Windows, especially in shared sections.
  • Provide Linux-specific parent image recommendations and caching details similar to the Windows section.
  • For every PowerShell example, include a Bash/Linux shell equivalent, and vice versa.
  • Expand Linux diagnostic and troubleshooting guidance to match Windows coverage (e.g., environment variable injection, SSH/Kudu usage).
  • Clarify which features are Windows-only, and offer Linux alternatives or workarounds where possible.
  • Review the order of presentation so that Linux and Windows instructions are interleaved or presented in parallel, rather than Windows-first.
  • Add more Linux-specific advanced configuration examples (e.g., memory/cpu limits, health checks) where possible.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-dotnet-framework.md ...les/app-service/configure-language-dotnet-framework.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 exclusively referencing Windows-based deployment and configuration patterns, such as Visual Studio publishing, Windows file paths, and Kudu's CMD/PowerShell consoles. There are no Linux-specific examples or instructions, and Windows tools and terminology are used throughout without mentioning Linux equivalents or alternatives.
Recommendations
  • Add Linux-specific instructions and examples, such as accessing .NET runtime versions and environment variables in Linux App Service environments.
  • Include references to Linux tools (e.g., Bash, SSH, Linux file paths) alongside Windows tools like CMD and PowerShell.
  • Clarify which steps or commands apply to Windows, Linux, or both, and provide parity in guidance for both platforms.
  • Mention deployment options and troubleshooting steps for Linux-based ASP.NET hosting, not just Windows.
  • Where Visual Studio is referenced, also mention cross-platform alternatives (e.g., VS Code, CLI-based deployment).
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-data-sources.md ...es/app-service/configure-language-java-data-sources.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides detailed, step-by-step instructions for configuring Tomcat server-level data sources on Windows, including PowerShell scripts and Windows-specific file paths and tools. In contrast, Linux instructions are less detailed, relying on generic shell scripts and mentioning tools like xsltproc and libxslt only briefly. Windows configuration is described with more explicit automation and troubleshooting steps, and Windows-specific tools (PowerShell, .cmd files) are used exclusively, with no Linux equivalents for scripting or automation. The Linux section lacks parity in terms of example scripts, troubleshooting, and automation guidance.
Recommendations
  • Provide a full example Linux startup script for automating Tomcat configuration, similar to the detailed PowerShell script for Windows.
  • Include troubleshooting steps and marker file logic for Linux, mirroring the Windows approach.
  • Offer equivalent Linux automation using bash or Python, and describe how to check for previous configuration and handle idempotency.
  • List Linux-specific tools and commands before or alongside Windows tools, not after.
  • Ensure that all configuration steps shown for Windows (copying Tomcat, setting CATALINA_BASE, applying XSLT, placing driver JARs) are equally detailed for Linux.
  • Add explicit instructions for setting environment variables and app settings via CLI or portal for Linux, with examples.
  • Avoid using Windows-specific terminology (e.g., .cmd, PowerShell) without Linux equivalents.
GitHub Create Pull Request
← Previous Page 11 of 85 Next →