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 101-125 of 2121 flagged pages
App Service Fix HTTP 502 and HTTP 503 Errors ...articles/app-service/troubleshoot-http-502-http-503.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by highlighting PowerShell as the primary CLI tool for app management and referencing Windows-specific tools like ProcDump. The debug console examples mention PowerShell and DOS commands, but do not reference Bash or Linux shell commands. There are no explicit Linux or Bash examples, nor are Linux troubleshooting tools or patterns mentioned.
Recommendations
  • Include equivalent Linux/Bash command examples in the Kudu debug console section, such as using Bash commands for diagnostics.
  • Mention Linux-native troubleshooting tools (e.g., gcore, strace, lsof) alongside ProcDump for memory dumps and diagnostics.
  • Provide Azure CLI examples for app management and troubleshooting, as Azure CLI is cross-platform and preferred by many Linux users.
  • Explicitly state that Kudu supports both PowerShell and Bash consoles, and show how to access and use the Bash console.
  • Ensure that references to management tools (like PowerShell) are paired with cross-platform alternatives (Azure CLI, Bash scripts) and that examples are provided for both Windows and Linux users.
GitHub Create Pull Request
App Service Tutorial: Connect a web app to SQL Database on behalf of the user ...utorial-connect-app-access-sql-database-as-user-dotnet.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 page demonstrates a moderate Windows bias. While most configuration and deployment steps use Azure CLI (which is cross-platform), key database management and user provisioning steps reference Windows-centric tools like SQL Server Management Studio (SSMS) and sqlcmd, without mentioning Linux alternatives. Additionally, publishing instructions prioritize Visual Studio (Windows) before mentioning Git Bash, and local debugging guidance focuses on Visual Studio remote debugging. There are no explicit Linux or cross-platform alternatives for these steps, and no mention of Linux-native SQL tools (e.g., Azure Data Studio, sqlcmd on Linux, or ODBC tools).
Recommendations
  • Include instructions for connecting to Azure SQL Database using Linux-native tools such as Azure Data Studio, sqlcmd on Linux, or other cross-platform SQL clients.
  • When describing publishing workflows, mention cross-platform IDEs (e.g., VS Code) and CLI-based deployment methods before or alongside Visual Studio.
  • For local debugging, provide guidance for Linux/macOS environments, such as using VS Code's remote debugging, or other cross-platform debugging tools.
  • Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary setup steps for non-Windows environments.
  • When referencing database management tools, list cross-platform options first or alongside Windows tools, and provide links to their documentation.
GitHub Create Pull Request
App Service Enable Diagnostic Logging ...n/articles/app-service/troubleshoot-diagnostic-logs.md
High Priority View Details →
Scanned: 2026-01-12 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 a Windows-first bias: logging features and instructions for Windows apps are described in greater detail and appear before Linux equivalents. Several logging types (web server logging, detailed error messages, failed request tracing) are exclusive to Windows, with no Linux alternatives or explanations. Examples and tooling references (e.g., Log Parser, W3C log format) are Windows-centric. Linux instructions are less detailed and sometimes missing, especially for advanced diagnostics.
Recommendations
  • Provide equivalent Linux examples and instructions for all logging types, or explicitly state when features are unavailable on Linux.
  • Include Linux-specific tools and patterns for accessing and analyzing logs (e.g., using grep, tail, jq, or Docker log commands).
  • Clarify differences in logging capabilities between Windows and Linux, and offer workarounds or alternatives for Linux users.
  • Ensure parity in documentation structure: present Linux and Windows instructions side-by-side where possible, rather than Windows-first.
  • Expand code examples to include Linux-friendly languages and frameworks, and show how to configure logging for those environments.
GitHub Create Pull Request
App Service Troubleshoot Performance Degradation ...es/app-service/troubleshoot-performance-degradation.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 exhibits several signs of Windows bias. Windows-specific tools and patterns, such as PowerShell, IIS diagnostics, and SysInternals Procdump, are mentioned exclusively or before any Linux equivalents. Diagnostic instructions and examples focus on Windows technologies (e.g., .NET Profiler for Windows, web.config for auto-heal), and there are no Linux-specific troubleshooting examples or references to Linux-native tools (such as Bash, Linux process dump tools, or Linux logging paths). The Kudu console is described as supporting PowerShell and DOS commands, with no mention of Bash or Linux shell support. Overall, Linux users may find it difficult to apply the guidance directly to their environments.
Recommendations
  • Add Linux-specific troubleshooting examples, such as using Bash in Kudu, Linux process dump tools (e.g., gcore, lsof), and Linux logging paths.
  • Include instructions for enabling diagnostics and collecting logs on Linux-based App Service plans, referencing Linux equivalents to IIS logs and .NET Profiler.
  • Mention Linux-native configuration files (e.g., appsettings.json, environment variables) for auto-heal or similar features, not just web.config.
  • Provide parity in restart and management examples, e.g., using Azure CLI or Bash scripts, not only Azure PowerShell.
  • Clarify which features and tools are available on Linux App Service plans, and note any differences or limitations.
GitHub Create Pull Request
App Service Tutorial: Access Azure databases with managed identity ...les/app-service/tutorial-connect-msi-azure-database.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, especially in the 'Set up your dev environment' section. Visual Studio for Windows is presented first and in more detail, while Visual Studio for Mac is described as lacking integration and requiring a workaround. Windows-specific tools (Visual Studio, Azure PowerShell) are mentioned before their Linux/macOS equivalents. Azure PowerShell and Visual Studio Windows receive more prominent placement and explanation than cross-platform or Linux-native tools. There are no explicit Linux examples or mentions of Linux-specific development environments (e.g., JetBrains Rider, VS Code on Linux, Bash shell), and the guidance for Linux users is limited to using Azure CLI.
Recommendations
  • Add explicit examples and instructions for Linux development environments, such as VS Code on Linux, JetBrains Rider, or command-line workflows using Bash.
  • Present cross-platform tools (Azure CLI, VS Code) before Windows-specific tools (Visual Studio, Azure PowerShell) to avoid 'windows_first' bias.
  • Include instructions for signing in and configuring Microsoft Entra authentication on Linux and macOS, not just Windows.
  • Clarify that Azure CLI and VS Code are fully supported on Linux and macOS, and provide links to installation guides for those platforms.
  • Where Visual Studio for Windows is mentioned, also mention equivalent steps for Linux/macOS environments, or note any limitations.
  • Consider adding troubleshooting or FAQ entries specifically for Linux/macOS users.
GitHub Create Pull Request
App Service Tutorial: Build and Run a Custom Image in Azure App Service ...main/articles/app-service/tutorial-custom-container.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 exhibits a Windows bias in several ways. The Windows container tutorial is presented first, with detailed step-by-step instructions using Windows-specific tools (Visual Studio, Windows Explorer, PowerShell scripts) and patterns. The Linux container tutorial, while present and thorough, is positioned after the Windows section and does not receive the same level of integration with IDE tooling or OS-specific features. Windows tools and workflows (Visual Studio, Windows font installation, PowerShell) are mentioned exclusively in the Windows section, with no Linux equivalents or cross-platform alternatives suggested. There are missing Linux examples for scenarios like installing fonts or using IDEs for container orchestration, and the Windows section does not reference Linux alternatives or parity.
Recommendations
  • Present Windows and Linux instructions in parallel or with equal prominence, rather than Windows-first.
  • Where Windows-specific tools (Visual Studio, PowerShell) are used, provide Linux equivalents (e.g., VS Code, Bash scripts) or note cross-platform alternatives.
  • For OS-specific operations (like installing fonts), include Linux examples (e.g., using fc-cache, copying fonts to /usr/share/fonts) and discuss how to adapt the sample for Linux containers.
  • Avoid exclusive use of Windows terminology (e.g., 'Windows Explorer') and provide cross-platform instructions (e.g., 'File Manager' or CLI alternatives).
  • Highlight cross-platform container orchestration tools (e.g., Docker Compose, VS Code Remote Containers) and provide examples for both Windows and Linux.
  • Ensure parity in troubleshooting tips (e.g., line ending issues are discussed for Linux, but similar issues for Windows should be mentioned if relevant).
  • Consider adding a summary table comparing Windows and Linux workflows for common tasks (building, deploying, debugging, logging, SSH access).
GitHub Create Pull Request
App Service Securely connect .NET apps to Azure SQL Database using Managed Identity ...icles/app-service/tutorial-connect-msi-sql-database.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 demonstrates a Windows bias by prioritizing Windows/Visual Studio workflows, using PowerShell and Windows-specific tools for key steps (such as SQLCMD in PowerShell), and omitting explicit Linux or cross-platform alternatives for several operations. Linux development environments and tools are not given equal prominence or example coverage, especially for database administration and local development setup.
Recommendations
  • Provide explicit Linux/macOS equivalents for all command-line steps, especially for SQL Database administration (e.g., using sqlcmd in Bash, Azure Data CLI, or cross-platform tools).
  • Add examples and instructions for setting up and debugging .NET apps with managed identity on Linux/macOS, including using VS Code and the .NET CLI.
  • Ensure that cross-platform tools (like Azure CLI and VS Code) are introduced before or alongside Windows-specific tools (Visual Studio, PowerShell).
  • Include notes or sections on using Docker or WSL for cross-platform development and testing.
  • When referencing PowerShell or Windows tools, always provide the corresponding Bash or shell commands for parity.
  • Highlight any differences or additional steps required for Linux/macOS users, especially around authentication and environment setup.
GitHub Create Pull Request
App Service Build a scheduled WebJob using your preferred language ...ocs/blob/main/articles/app-service/tutorial-webjobs.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 Windowscode Tabs Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias, especially in the .NET section. Windows build and packaging instructions are presented before Linux equivalents, and the use of Windows-specific runtime identifiers (win-x64) and file extensions (.exe) is prominent. The reference to 'windowscode' tabs in links and supported file types further centers Windows as the default. Linux instructions are present but often secondary, and some advanced scenarios (like PowerShell or Windows container specifics) are referenced without Linux parity. Other language pivots (Python, Node, Java, PHP) focus on Linux, but the .NET pivot is Windows-centric.
Recommendations
  • Present Linux and Windows instructions side-by-side or in parallel, rather than listing Windows first.
  • Use neutral language and avoid defaulting to Windows-specific terms (e.g., 'windowscode' tabs, .exe) in cross-platform contexts.
  • Ensure all advanced scenarios (such as deployment, troubleshooting, and supported file types) have Linux equivalents and are equally documented.
  • Clarify when instructions apply to both platforms, and highlight any platform-specific differences explicitly.
  • Provide Linux container and shell examples wherever Windows/PowerShell examples are given.
  • Review links and references to ensure they do not default to Windows-specific tabs or content.
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 oriented toward Windows development environments, specifically Visual Studio 2022 and PowerShell-based workflows. All setup, package installation, and deployment instructions assume the use of Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. Package installation is demonstrated exclusively with PowerShell commands in the Package Manager Console, and there are no examples for .NET CLI or other Linux-friendly tools. The use of Windows-centric UI instructions (menus, dialogs) and screenshots further reinforces this bias. There is no guidance for Linux or macOS users, nor any mention of alternative editors or command-line workflows.
Recommendations
  • Add equivalent instructions for Linux and macOS users, including setup steps using the .NET CLI (e.g., 'dotnet new', 'dotnet add package') instead of or alongside Visual Studio and PowerShell.
  • Provide examples for installing NuGet packages using the .NET CLI: 'dotnet add package <package-name> --version <version>' and clarify how to edit configuration files in non-Windows environments.
  • Include guidance for using cross-platform editors such as VS Code, and clarify which steps are specific to Visual Studio versus general .NET development.
  • Add screenshots or textual instructions for Azure portal interactions that are platform-agnostic.
  • Explicitly state platform requirements and offer parity for Linux/macOS users wherever possible, including testing and deployment steps.
  • Mention any limitations or differences when running WebJobs SDK projects on Linux or macOS, and provide troubleshooting tips for those platforms.
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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), using Windows-specific UI terms (Solution Explorer, dialog boxes), and omitting any mention of Linux development environments, CLI workflows, or cross-platform tooling. All examples and instructions assume a Windows/Visual Studio workflow, with no parity for Linux or cross-platform scenarios.
Recommendations
  • Add instructions for developing and deploying WebJobs using cross-platform tools such as Visual Studio Code, Azure CLI, or GitHub Actions.
  • Include Linux-specific examples, such as using the Azure CLI or zip deployment from a Linux shell.
  • Clarify which steps are Windows/Visual Studio-specific and provide alternative steps for Linux/macOS users.
  • Reference cross-platform .NET Core workflows and highlight any differences in deployment from non-Windows environments.
  • Mention and link to documentation for deploying WebJobs from Linux or macOS, and provide parity in feature coverage.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: file paths and examples use Windows-style paths (e.g., 'c:\data\import'), references to Windows-specific .NET APIs and classes (such as ServicePointManager and WinHttpHandler), and no explicit mention of Linux equivalents or cross-platform considerations for local development, configuration, or file system bindings. There are no Linux/macOS-specific examples, and Windows-centric tooling (Visual Studio) is referenced without alternatives. This may make it harder for Linux users to follow or adapt the guidance.
Recommendations
  • Provide Linux/macOS-specific examples alongside Windows ones, especially for file paths and environment variable configuration.
  • Mention cross-platform .NET Core compatibility explicitly and clarify any platform-specific limitations or differences.
  • Include references to cross-platform development tools (e.g., VS Code, CLI) in addition to Visual Studio.
  • Use environment variable and file path examples that are platform-agnostic or show both Windows and Linux formats.
  • Clarify whether APIs like ServicePointManager and WinHttpHandler have different behaviors or equivalents on Linux/macOS.
  • Add notes or sections on running and deploying WebJobs SDK projects on Linux-based environments, including Azure App Service for Linux.
GitHub Create Pull Request
App Service Use Key Vault References as App Settings ...ticles/app-service/app-service-key-vault-references.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring Key Vault references, but PowerShell examples are consistently presented alongside or immediately after CLI examples, and no Linux-specific shell (e.g., Bash) or OS-specific guidance is given. There is a lack of explicit Linux-native instructions or troubleshooting steps, and Windows-centric tools (PowerShell) are featured without parity for Linux users. The troubleshooting and portal navigation instructions do not mention platform differences, and the documentation does not address Linux-specific nuances beyond a brief mention in networking configuration.
Recommendations
  • Add explicit Bash shell examples for all CLI commands, clarifying usage on Linux and macOS.
  • Where PowerShell is used, provide equivalent Linux-native scripting (e.g., Bash, zsh) or clarify that Azure CLI works cross-platform.
  • Include troubleshooting steps or notes for Linux users, especially regarding file system mounting and managed identity propagation.
  • Clarify any platform-specific behavior in portal navigation or diagnostics, if applicable.
  • Ensure that any references to OS-specific tools (e.g., PowerShell) are balanced with Linux alternatives or guidance.
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-11 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 apps. Windows-specific tools and configuration files (IIS, web.config) are mentioned exclusively, while Linux alternatives are not discussed. The documentation also introduces the Windows method before clarifying that it does not apply to Linux, and does not suggest Linux-native approaches.
Recommendations
  • Add a section describing how to implement fine-grained authorization for Linux apps, such as using middleware in popular frameworks (Node.js, Python, .NET Core, etc.) or leveraging nginx/Apache configuration.
  • Provide code samples or configuration examples for Linux-based App Service environments.
  • Mention Linux alternatives (e.g., appsettings.json, environment variables, or framework-specific authorization modules) alongside Windows methods.
  • Avoid presenting Windows solutions first or exclusively; ensure both platforms are covered equally and in parallel.
  • Clarify platform applicability at the beginning of relevant sections, and link to external resources for Linux authorization best practices if needed.
GitHub Create Pull Request
App Service Restore Deleted Apps ...blob/main/articles/app-service/app-service-undelete.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 command examples, nor is there mention of cross-platform tools or workflows. The PowerShell approach is presented as the primary (and only) scripting method, which may disadvantage users on Linux or macOS who prefer or require non-Windows tooling.
Recommendations
  • Add equivalent examples using the Azure CLI (az) for all PowerShell cmdlets shown, including listing deleted apps and restoring them.
  • Include Bash script snippets or instructions for Linux/macOS users.
  • Explicitly mention that PowerShell Core is cross-platform, but also provide non-PowerShell alternatives for users who do not wish to install PowerShell.
  • Reorder sections so that cross-platform methods (Azure CLI, REST API) are presented before or alongside PowerShell examples.
  • Clarify which tools are available on which platforms and provide guidance for Linux/macOS users.
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 00:00
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 running on IIS servers, which are Windows-specific. There is no mention of Linux-based web servers (e.g., Apache, Nginx) or .NET Core apps running on Linux. All examples and tooling (Azure Migrate appliance, IIS) are Windows-centric, with no guidance for Linux environments.
Recommendations
  • Include information and examples for discovering .NET apps hosted on Linux web servers (e.g., Apache, Nginx, Kestrel).
  • Mention whether Azure Migrate supports Linux-based .NET app discovery, and provide instructions if available.
  • Add parity in dashboard features and troubleshooting guidance for Linux-hosted apps.
  • Clarify any limitations or differences in discovery capabilities between Windows and Linux environments.
GitHub Create Pull Request
App Service Install a TLS/SSL Certificate for Your App ...main/articles/app-service/configure-ssl-certificate.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific tools (IIS, Certreq.exe) are mentioned for certificate export, and PowerShell is given as an automation example alongside Azure CLI. There is no mention of Linux equivalents for certificate export (e.g., using OpenSSL on Linux for certificates generated outside Azure), and Windows container support is called out explicitly in FAQ answers before Linux/container scenarios. Linux-specific instructions or parity for common certificate management tasks are missing.
Recommendations
  • Add explicit Linux-based examples for certificate export and management, such as using OpenSSL for certificates generated on Linux systems.
  • When mentioning Windows tools (IIS, Certreq.exe), also mention Linux alternatives (e.g., OpenSSL, certbot) and provide links to relevant documentation.
  • In automation sections, provide Bash scripts or Linux CLI equivalents alongside PowerShell examples.
  • Clarify platform-specific limitations and capabilities for both Windows and Linux, especially in FAQ answers (e.g., outbound client certificate support, trusted root store modification).
  • Review screenshots and UI instructions to ensure they are not Windows-centric, or provide notes for Linux users where UI/experience differs.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows-specific features and workflows. All examples and instructions assume a Windows Server environment, with exclusive use of PowerShell scripts (Install.ps1), references to Windows tools (MSI installers, IIS, registry keys), and RDP/Bastion for remote access. There are no Linux equivalents or examples provided, and the operating system is explicitly stated as Windows Server 2022. Linux patterns, tools, or scripting languages are not mentioned.
Recommendations
  • Clearly indicate in the introduction that Managed Instance on Azure App Service is Windows-only, and provide links to Linux alternatives if available.
  • If Linux support is planned, add equivalent examples for Linux (e.g., Bash scripts, Linux storage mounts, Linux configuration patterns).
  • Where possible, abstract instructions to be OS-agnostic, or provide separate sections for Windows and Linux.
  • Mention Linux-specific tooling and remote access methods (e.g., SSH, Linux package managers) if/when supported.
  • Clarify limitations for non-Windows users and suggest migration paths or alternative Azure services for Linux workloads.
GitHub Create Pull Request
App Service Getting started with Azure App Service ...docs/blob/main/articles/app-service/getting-started.md
High Priority View Details →
Scanned: 2026-01-11 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 shows evidence of 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 the .NET section, Windows tools are presented first, and Azure PowerShell is included as a primary option, while Linux-specific instructions are less prominent. Python examples reference Windows tabs and instructions, and the Next Step call-to-action is for deploying an ASP.NET app, which is typically associated with Windows. Linux-specific examples and parity are stronger in Java, Node.js, and PHP sections, but overall, Windows tools and patterns are prioritized or more visible in several places.
Recommendations
  • Ensure that Linux and cross-platform tools (such as VS Code, CLI, Azure CLI) are listed before or alongside Windows-specific tools in all language stacks.
  • Provide explicit Linux examples and instructions for all stacks, especially .NET and Python, including bash/terminal commands and Linux deployment scenarios.
  • Avoid listing Azure PowerShell as a primary deployment tool unless a Linux equivalent (Azure CLI) is also presented with equal prominence.
  • Balance the 'Next step' call-to-action to include a Linux-friendly or cross-platform example, not just ASP.NET (which is often Windows-centric).
  • Audit all quickstart and tutorial links to ensure Linux tabs are present and easy to find, not buried under Windows defaults.
  • Highlight Linux container options and deployment patterns wherever custom containers are discussed.
GitHub Create Pull Request
App Service Secure Your Domain with TLS/SSL ...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell automation before Azure CLI, referencing Azure PowerShell in metadata, and omitting Linux-specific command-line examples or tools. While the main workflow is portal-based and cross-platform, scripting and automation sections prioritize Windows-centric tools and do not provide parity for Linux users.
Recommendations
  • Provide Linux-specific examples, such as Bash scripts or shell commands, especially for certificate upload and binding.
  • List Azure CLI examples before PowerShell, or present both side-by-side to avoid Windows-first ordering.
  • Include references to Linux tools (e.g., OpenSSL, curl) for certificate management and validation.
  • Remove or balance metadata tags that highlight Azure PowerShell unless CLI and Linux scripting are equally represented.
  • Add explicit guidance for Linux users, such as how to prepare .pfx files or automate tasks using Bash/CLI.
GitHub Create Pull Request
App Service Manage Deployment Credentials ...n/articles/app-service/deploy-configure-credentials.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure portal, but does not include explicit Linux shell or Bash examples, nor does it mention Linux-specific tools or workflows. Azure PowerShell is referenced and explained in detail, even though it is primarily a Windows-centric tool. The order of presentation often lists Azure CLI first (which is cross-platform), but PowerShell is given equal prominence, and there are no Linux/Bash-specific instructions or screenshots. There is a note about Bash variable interpolation, but no concrete Bash command examples.
Recommendations
  • Add explicit Bash/Linux shell command examples, especially for common deployment tasks.
  • Include screenshots or instructions for Linux environments (e.g., using terminal, file paths, etc.).
  • Mention Linux-specific tools or workflows where relevant (e.g., using curl, scp, or native Git commands).
  • Clarify that Azure CLI is cross-platform and provide usage notes for both Windows and Linux users.
  • Reduce emphasis on Azure PowerShell or clearly state its platform limitations.
  • Add troubleshooting tips for Linux users, such as handling credential formats and escaping characters in Bash.
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-11 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 page exhibits a strong Windows bias. Migration tools and examples focus almost exclusively on ASP.NET apps running on Windows/IIS servers, with repeated references to PowerShell scripts and Windows-specific migration assistants. There are no Linux migration examples, nor are Linux-based web servers (such as Apache or Nginx) or Linux migration tools mentioned. Windows tools and patterns are described first and in detail, while Linux scenarios are absent.
Recommendations
  • Add migration guidance and examples for .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel).
  • Include Linux-specific migration tools or scripts, or clarify if existing tools support Linux environments.
  • Provide parity in documentation by listing Linux migration options alongside Windows/IIS options in tables and tool descriptions.
  • Add sample commands and walkthroughs using Bash or other Linux-native tooling, not just PowerShell.
  • Explicitly state platform limitations for each tool, and link to alternative approaches for Linux-based .NET apps.
GitHub Create Pull Request
App Service Hybrid Connections in Azure App Service ...articles/app-service/app-service-hybrid-connections.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a moderate Windows bias. Windows instructions and tools (such as PowerShell and GUI) are consistently presented before Linux equivalents, and some troubleshooting steps only provide Windows/PowerShell examples. Windows-specific tools and patterns (like the GUI and MSI installer) are described in greater detail, while Linux instructions are more limited and sometimes lack parity (e.g., no GUI, less troubleshooting guidance).
Recommendations
  • Provide Linux-first or side-by-side examples for all installation, configuration, and troubleshooting steps.
  • Include Linux-native troubleshooting commands (e.g., netcat, curl, ss, or nc) alongside PowerShell examples.
  • Expand Linux documentation to match the detail given for Windows, especially for CLI usage and service management.
  • Offer parity in upgrade instructions (e.g., provide a recommended upgrade workflow for Linux, not just 'check version').
  • Where GUI is unavailable on Linux, offer equivalent CLI workflows with screenshots or step-by-step guidance.
  • Ensure all environment variable and configuration steps are clearly documented for both platforms.
  • Add explicit notes when a feature/tool is Windows-only, and suggest Linux alternatives if possible.
GitHub Create Pull Request
App Service Configure Premium v4 Tier ...s/app-service/app-service-configure-premium-v4-tier.md
High Priority View Details →
Scanned: 2026-01-11 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 displays a moderate Windows bias. Windows is mentioned first in availability, and PowerShell is featured as an automation option alongside Azure CLI, but there are no Linux shell (bash) or scripting examples. The portal instructions and screenshots are Windows-centric, and there is no mention of Linux-specific tools or patterns for automation or management. While Linux SKU availability is shown, the overall flow and examples prioritize Windows tools and workflows.
Recommendations
  • Add bash shell scripting examples for automating Premium v4 app creation and scaling, demonstrating parity with PowerShell.
  • Include Linux-specific instructions and screenshots for the Azure portal where UI or workflow differs.
  • Mention Linux-native tools (such as az CLI usage in bash, or automation with cron) where relevant.
  • Ensure that Linux examples are presented alongside or before Windows examples to balance the order of presentation.
  • Clarify any differences in deployment or management steps for Linux-based App Service apps, especially for custom containers.
GitHub Create Pull Request
App Service App Service Managed Certificate (ASMC) Changes – July 28, 2025 ...e/app-service-managed-certificate-changes-july-2025.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell script for identifying affected Traffic Manager endpoints, without offering equivalent Bash, Azure CLI, or cross-platform scripting examples. The instructions for running the script assume a Windows environment (PowerShell), and there is no mention of Linux or macOS alternatives for the same task. Additionally, the PowerShell-based approach is presented first and exclusively, which may disadvantage users on non-Windows platforms.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for identifying affected Traffic Manager endpoints, ensuring Linux and macOS users can perform the same checks without requiring PowerShell.
  • Explicitly mention cross-platform alternatives where possible, such as using Azure CLI or REST API queries, and provide example commands for those environments.
  • When referencing scripts or tools, clarify their platform compatibility and, if only a Windows/PowerShell version is available, link to or suggest community-maintained alternatives for Linux/macOS.
  • Consider restructuring sections so that cross-platform or platform-neutral solutions (e.g., Azure CLI, REST API, ARG queries) are presented before or alongside Windows/PowerShell-specific solutions.
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-11 00:00
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, such as iisnode, web.config, named pipes, Win32 error codes, and references to DLLs. All configuration and troubleshooting examples are given in terms of Windows concepts and files (e.g., web.config, node.exe, Win32 errors, DLLs), with no mention of Linux equivalents or cross-platform alternatives. There are no Linux or cross-platform deployment, configuration, or troubleshooting examples provided.
Recommendations
  • Add equivalent guidance for Linux-based App Service environments, such as configuration and troubleshooting steps for Node.js apps running on Linux.
  • Include examples using Linux-native process managers (e.g., PM2, systemd) and configuration files (e.g., ecosystem.config.js) alongside web.config/iisnode examples.
  • Reference Linux error codes and log locations, and provide troubleshooting steps for common Linux-specific issues.
  • Clarify which instructions apply only to Windows-based App Service and provide links or sections for Linux-based workflows.
  • Offer parity in debugging and profiling recommendations, including Linux-compatible tools and methods.
GitHub Create Pull Request
← Previous Page 5 of 85 Next →