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 176-200 of 2121 flagged pages
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a clear Windows bias in the 'container-windows' pivot. Windows instructions are presented first, with exclusive use of Windows-specific tools (Visual Studio, Windows Explorer), patterns (right-click, Solution Explorer), and scripting (PowerShell). There are no Linux equivalents or cross-platform alternatives provided in the Windows section, and the workflow is tightly coupled to Windows development environments. The Linux section is separate and more CLI-focused, but the Windows section does not acknowledge or offer parity for Linux users wishing to build Windows containers.
Recommendations
- Add cross-platform instructions for building and running Windows containers, such as using Docker CLI and VS Code on Linux/macOS.
- Provide PowerShell script alternatives or equivalents for Bash, where possible, or note platform limitations.
- Include guidance for users who may be developing on Linux/macOS but need to target Windows containers (e.g., remote Docker hosts, Azure DevOps pipelines).
- Reference open-source or cross-platform tools (e.g., VS Code, Docker Desktop for Mac/Linux) alongside Visual Studio.
- Clarify which steps are strictly Windows-only and suggest workarounds or alternatives for non-Windows environments.
- Ensure parity in troubleshooting and diagnostic steps (e.g., log streaming) across both Windows and Linux pivots.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on development and deployment workflows using Visual Studio, a Windows-centric IDE, with all examples and instructions tailored to Windows users. There is no mention of Linux or cross-platform development environments, nor are alternative tools or command-line workflows for Linux users provided. The use of Visual Studio-specific features and terminology (Solution Explorer, dialog boxes, project templates) further reinforces a Windows bias.
Recommendations
- Add equivalent instructions for developing and deploying WebJobs using cross-platform tools such as VS Code, JetBrains Rider, or command-line interfaces.
- Include examples for Linux and macOS environments, such as using the Azure CLI, .NET CLI, or GitHub Actions for deployment.
- Mention and document how to create, configure, and deploy WebJobs without relying on Visual Studio, including manual file creation and editing.
- Provide guidance for users who do not have access to Visual Studio, including open-source alternatives and platform-agnostic workflows.
- Ensure screenshots and UI references are supplemented with command-line or generic instructions.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows and Visual Studio (Windows) workflows, providing PowerShell and Windows-specific tools and instructions, and omitting equivalent Linux/macOS command-line or development environment examples. Key steps such as database permission grants and local development setup are described using Windows-centric tools (PowerShell, Visual Studio), while Linux alternatives are either missing or less detailed.
Recommendations
- Provide explicit Linux/macOS instructions for all steps, especially for database permission grants (e.g., using sqlcmd on Linux/macOS, or Azure Data Studio).
- Include examples for common Linux-based development environments (e.g., JetBrains Rider, VS Code on Linux, CLI-only workflows).
- When listing development environment setup, avoid putting Windows/Visual Studio first; instead, present cross-platform options in parallel or start with the most platform-agnostic (e.g., Azure CLI, VS Code).
- For all command-line instructions, ensure both PowerShell and Bash/Azure CLI equivalents are given, and clarify which platforms each applies to.
- Add notes or callouts for any steps that are Windows-only, and provide workarounds or alternatives for Linux/macOS users.
- Ensure screenshots and UI walkthroughs are not exclusively from Windows tools; include or reference Linux/macOS equivalents where possible.
App Service
Build a scheduled WebJob using your preferred language
...ocs/blob/main/articles/app-service/tutorial-webjobs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Windowscode Links
Summary
The documentation shows mild Windows bias, especially in the .NET section, where Windows build/publish/packaging commands are presented first and in more detail than Linux equivalents. References to 'windowscode' tabs and links are used for supported file types and CRON expressions, even in Linux, Python, Node, Java, and PHP pivots. The .NET instructions provide both Windows and Linux commands, but Windows is listed first and more prominently. Other language pivots (Python, Node, Java, PHP) focus on Linux and do not show Windows-specific bias.
Recommendations
- Present Linux and Windows instructions side-by-side or alternate which is listed first to avoid implicit prioritization.
- Use neutral or platform-appropriate links for supported file types and CRON expressions, rather than 'windowscode' tabs for all pivots.
- Ensure parity in detail and clarity for Linux instructions, especially in .NET pivots (e.g., explain Linux packaging and execution as thoroughly as Windows).
- Add explicit notes about platform differences and limitations, and provide troubleshooting tips for both Windows and Linux users.
- Consider including PowerShell and Bash examples where appropriate, and clarify which platforms each applies to.
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 →
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. All instructions, screenshots, and examples assume the use of Visual Studio on Windows. Package installation is exclusively demonstrated using the Package Manager Console with PowerShell commands, with no mention of cross-platform alternatives like .NET CLI (dotnet) or Visual Studio Code. There are no instructions or examples for Linux or macOS users, nor any guidance for using open-source or cross-platform tools. The workflow and tooling are Windows-centric throughout.
Recommendations
- Add instructions and examples for using the .NET CLI (dotnet) to create projects, install packages, and run applications, which work on Windows, Linux, and macOS.
- Include guidance for using Visual Studio Code as an alternative to Visual Studio 2022, with relevant screenshots and steps.
- Provide explicit steps for Linux/macOS users, such as how to set environment variables, configure appsettings.json, and run the application from the terminal.
- Mention cross-platform package managers (e.g., dotnet add package) alongside PowerShell/Package Manager Console commands.
- Clarify which steps are Windows-specific and offer alternatives for other operating systems.
- Add notes about Azure Storage Emulator alternatives for Linux/macOS, such as Azurite.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for the Azure WebJobs SDK demonstrates a Windows bias in several ways. All file system examples use Windows-style paths (e.g., 'c:\data\import'), and there are no Linux or cross-platform equivalents shown. The documentation references Visual Studio tooling and .NET Framework before mentioning .NET Core, which is more cross-platform. There is no mention of Linux-specific considerations, nor are there examples of running WebJobs SDK on Linux or using Linux tools. The use of Windows-centric APIs like ServicePointManager and WinHttpHandler is described without alternatives for Linux environments. Overall, the documentation assumes a Windows development environment and omits Linux parity in examples and tooling references.
Recommendations
- Provide Linux and cross-platform examples alongside Windows examples, especially for file paths (e.g., '/home/user/data/import').
- Explicitly mention that the SDK and examples work on Linux and macOS, and describe any platform-specific considerations.
- Include instructions and examples for running WebJobs SDK projects on Linux (e.g., using VS Code, CLI, or Docker), not just Visual Studio on Windows.
- Reference cross-platform APIs and tools where possible, or clarify when a feature is Windows-only.
- Add notes or tables comparing Windows and Linux development workflows for WebJobs SDK, including environment variable configuration and file system access.
App Service
Discover .NET Apps to Azure App Service
...cles/app-service/app-service-migration-discover-net.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation focuses exclusively on discovering ASP.NET web apps hosted on IIS servers, which are Windows-specific. There is no mention of Linux-based web servers (such as Apache or Nginx), nor examples or guidance for discovering .NET apps deployed on Linux. All tooling and discovery patterns described are tailored to Windows environments.
Recommendations
- Add examples and guidance for discovering .NET web apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel).
- Mention whether Azure Migrate supports discovery of .NET apps on Linux, and if so, provide parity in documentation.
- Include Linux-specific discovery steps, troubleshooting, and dashboard features.
- Clarify limitations or differences in discovery capabilities between Windows and Linux environments.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page shows a Windows bias by presenting Windows-specific information and tools first, such as mentioning Windows SKU availability before Linux, and providing Azure PowerShell examples (which are Windows-centric) alongside Azure CLI. There is a lack of Linux-specific automation examples (e.g., Bash scripts), and Windows terminology and tools are referenced more prominently. Linux container limitations are mentioned, but Linux usage patterns are not equally demonstrated.
Recommendations
- Provide Linux/Bash script examples for automating App Service plan creation and scaling, not just Azure CLI and PowerShell.
- Present Linux and Windows information in parallel, or alternate which is presented first, to avoid 'windows_first' ordering.
- Include examples of deploying and scaling Linux-based apps, especially custom containers, to highlight Linux parity.
- Reference cross-platform tools (e.g., Azure CLI, Terraform) before platform-specific tools like PowerShell.
- Clarify any differences in workflow or limitations for Linux users, and provide guidance for Linux-specific scenarios.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based command-line examples and referencing Windows-centric tools and patterns. There are no CLI (az), Bash, or Linux-native instructions, nor is there mention of cross-platform alternatives. The PowerShell approach is presented as the only programmatic method, with no parity for Linux or macOS users who may prefer Bash or the Azure CLI.
Recommendations
- Add equivalent Azure CLI (az) commands for all PowerShell examples, ensuring cross-platform usability.
- Include Bash script examples where appropriate, especially for listing and restoring deleted apps.
- Explicitly mention that PowerShell examples can be run on Linux/macOS via PowerShell Core, or provide guidance for those platforms.
- Reorder sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
- Add a comparison table or note indicating which tools are available on which platforms (Windows, Linux, macOS).
App Service
Secure Your Domain with TLS/SSL
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page shows evidence of Windows bias in several areas. The automation section provides a PowerShell script example but does not include a Bash or Linux shell equivalent, and the PowerShell script is highlighted and presented before any Linux alternatives. The page references Azure CLI but does not provide a direct code sample, whereas the PowerShell sample is embedded. There is no mention of Linux-specific tools or workflows for certificate management, and the documentation does not provide parity for Linux users in automation or scripting examples.
Recommendations
- Add Bash/Linux shell script examples alongside PowerShell, especially in the automation section.
- Provide direct Azure CLI code samples (not just links) for certificate binding, and ensure they are presented before or alongside PowerShell examples.
- Include references to Linux certificate management tools (e.g., OpenSSL) for uploading or preparing certificates.
- Ensure that instructions and screenshots are platform-neutral or include both Windows and Linux variants where relevant.
- Explicitly mention Linux workflows in relevant sections, such as uploading certificates or inspecting HTTPS headers.
App Service
Authentication Types by Deployment Methods
...in/articles/app-service/deploy-authentication-types.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows-centric tools and workflows. Windows tools such as Azure PowerShell and Visual Studio are prominently featured, with dedicated sections and multiple reference links. PowerShell is mentioned explicitly, and Visual Studio (a Windows-first IDE) receives more coverage than cross-platform alternatives. There are no explicit Linux shell (bash) or platform-specific examples, and Linux-native deployment tools or workflows are not discussed. The order of presentation often places Windows tools before cross-platform or Linux-friendly options.
Recommendations
- Add explicit examples for Linux shell (bash) usage, especially for Azure CLI commands.
- Include references to Linux-native deployment workflows (e.g., SCP/SFTP, rsync, or bash scripts) where applicable.
- Provide parity in documentation for Visual Studio Code (cross-platform) and other non-Windows IDEs, including deployment guides for Linux/macOS.
- Ensure that cross-platform tools (like Azure CLI) are presented before or alongside Windows-specific tools.
- Clarify which deployment methods and authentication types are supported on Linux/macOS environments.
- Add notes or sections for Linux users, highlighting any differences or additional steps required.
App Service
Enable integration with an Azure virtual network
...icles/app-service/configure-vnet-integration-enable.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for enabling Azure virtual network integration. However, the PowerShell section is significantly more detailed, with step-by-step parameter preparation, delegation checks, and resource configuration. There are no Linux-specific examples or references to Linux-native tools, and PowerShell (a Windows-centric tool) is given a more prominent and thorough treatment. The CLI example is brief and lacks the depth of the PowerShell walkthrough.
Recommendations
- Expand the Azure CLI section to include detailed, step-by-step instructions equivalent to the PowerShell walkthrough, including subnet delegation checks and resource configuration.
- Add explicit references to Linux environments, such as running Azure CLI commands on Bash or in a Linux shell, and clarify any platform-specific considerations.
- Include troubleshooting steps or notes for Linux users, especially around permissions, environment variables, and context switching.
- Ensure parity in example depth and coverage between CLI and PowerShell, so Linux users are not disadvantaged.
- Consider adding a table or section comparing CLI and PowerShell usage for common tasks, highlighting cross-platform options.
App Service
Hybrid Connections in Azure App Service
...articles/app-service/app-service-hybrid-connections.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows installation instructions, GUI usage, and troubleshooting steps are consistently presented before Linux equivalents. Windows-specific tools (MSI installer, GUI, PowerShell commands) are emphasized, while Linux instructions are sometimes less detailed or presented as alternatives. Troubleshooting examples use PowerShell without providing Linux command equivalents. The legacy Hybrid Connection Manager is only available for Windows, and upgrade instructions for Windows are more automated than for Linux. The GUI is only available on Windows, with Linux users directed to CLI usage.
Recommendations
- Present Windows and Linux instructions in parallel, or alternate which platform is shown first in each section.
- Provide Linux equivalents for all troubleshooting commands (e.g., use 'nc', 'curl', or 'ss' instead of only PowerShell 'Test-NetConnection').
- Include more detailed Linux installation and upgrade instructions, matching the depth of Windows guidance.
- Offer Linux-specific examples for connectivity testing and endpoint verification.
- Clarify any feature parity gaps (e.g., GUI availability) and suggest alternatives or workarounds for Linux users.
- Avoid referencing Windows-only legacy tools without noting Linux alternatives or limitations.
- Where possible, use cross-platform commands (e.g., Azure CLI) in examples instead of platform-specific tools.
App Service
Migrate .NET Apps to Azure App Service
.../articles/app-service/app-service-asp-net-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All migration tools and examples focus exclusively on migrating .NET apps from Windows environments, specifically IIS servers. PowerShell scripts are the only automation option mentioned, and migration assistants are Windows-only. There is no mention of Linux-based .NET hosting scenarios, Linux migration tools, or examples for apps running on Linux (e.g., Apache, Nginx, Kestrel). The documentation assumes the reader is migrating from Windows/IIS and does not address Linux users.
Recommendations
- Add guidance and examples for migrating .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel) to Azure App Service.
- Include Linux-specific migration tools or manual migration steps, such as using rsync, SCP, or Azure CLI on Linux.
- Provide parity in automation examples by including Bash scripts and Linux command-line instructions alongside PowerShell.
- Clarify which migration tools (if any) support Linux environments, and highlight any limitations.
- Mention containerization options for Linux-hosted .NET apps, such as Docker, and provide relevant tutorials.
- Explicitly state Windows-only limitations for tools, and direct Linux users to alternative resources.
App Service
Node.js Best Practices and Troubleshooting
...rvice-web-nodejs-best-practices-and-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically IIS and iisnode, with exclusive references to Windows concepts, tools, and configuration files (such as web.config, named pipes, Win32 error codes, and DLLs). There are no Linux or cross-platform equivalents mentioned, nor any examples for Linux-based deployments or troubleshooting. The guidance assumes the use of node.exe and Windows file paths, and references to Azure App Service features are tied to Windows hosting models.
Recommendations
- Include equivalent guidance for Linux-based Node.js hosting on Azure App Service, such as troubleshooting with PM2 or other Linux process managers.
- Provide examples for Linux environments (e.g., using environment variables, JSON config files, or systemd units instead of web.config and DLLs).
- Mention Linux-specific logging and error locations, such as /home/LogFiles/Application/logging-errors.txt or stdout/stderr streams.
- Reference cross-platform Node.js deployment patterns, and clarify which instructions apply only to Windows/IIS hosting.
- Add troubleshooting steps and configuration options for Node.js apps running on Linux App Service plans, including relevant tools and error codes.
App Service
Use Key Vault References as App Settings
...ticles/app-service/app-service-key-vault-references.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuration tasks, but PowerShell examples are given equal prominence and detail, despite PowerShell being primarily a Windows tool. There is no mention of Linux-specific shell commands (such as Bash or scripting patterns), nor are there examples tailored to Linux environments. The troubleshooting and operational guidance does not address Linux-specific concerns or tools, and the documentation assumes parity between platforms without highlighting potential differences or issues for Linux users.
Recommendations
- Add explicit Bash shell examples alongside Azure CLI and PowerShell, especially for configuration steps.
- Include notes or sections that address Linux-specific considerations, such as file permissions, environment variable handling, or troubleshooting steps relevant to Linux.
- Clarify any platform-specific behaviors, especially where PowerShell commands may not be available or behave differently on Linux.
- Ensure that any references to tools or commands are not Windows-centric, and provide Linux alternatives where appropriate.
- Consider reordering examples to present cross-platform (CLI/Bash) commands before PowerShell, or provide tabs for both Windows and Linux workflows.
App Service
App Service Managed Certificate (ASMC) Changes – July 28, 2025
...e/app-service-managed-certificate-changes-july-2025.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing a PowerShell script for identifying impacted Traffic Manager endpoints, without offering equivalent Bash, Azure CLI, or cross-platform alternatives. Instructions for running the script assume a Windows environment (PowerShell), and there are no Linux/macOS-specific examples or guidance. This may hinder Linux or cross-platform administrators from easily following the mitigation steps.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for identifying impacted Traffic Manager endpoints, ensuring Linux/macOS users can follow the same guidance.
- When referencing scripts, clarify if they are cross-platform or provide alternatives for non-Windows environments.
- Include explicit instructions or examples for running queries or scripts on Linux/macOS terminals, not just PowerShell.
- Where possible, use Azure CLI examples in addition to or instead of PowerShell, as Azure CLI is cross-platform.
- Review other sections for implicit Windows assumptions and add Linux/macOS parity where needed.
App Service
Tutorial: ASP.NET app with Azure SQL Database
...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority
View Details →
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 the use of Visual Studio on Windows. Azure App Service (Windows) is selected by default, and there are no references to Linux-based App Service plans, cross-platform development tools, or command-line alternatives. All code/package management and database commands are shown using PowerShell and Visual Studio tools, with no mention of Linux equivalents or CLI workflows.
Recommendations
- Add instructions and screenshots for deploying from cross-platform tools such as Visual Studio Code, Azure CLI, or GitHub Actions.
- Include examples for publishing to Azure App Service (Linux) and clarify differences in configuration.
- Provide Linux/macOS equivalents for PowerShell commands, such as using Bash and Azure CLI.
- Mention alternative editors (e.g., VS Code) and workflows for developers not using Windows.
- Ensure that database connection and migration steps are documented for non-Windows environments, including using sqlcmd on Linux/macOS.
- Reorder sections to present cross-platform options before or alongside Windows-specific instructions.
App Service
Customize Sign-ins and Sign-outs
...vice/configure-authentication-customize-sign-in-out.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides a detailed example for configuring authorization at the server level specifically for Windows apps using IIS and web.config, while explicitly stating that Linux apps cannot use this method and offers no Linux equivalent. The use of Windows-specific tools (IIS, web.config, Kudu) is highlighted, with no comparable Linux guidance. Other sections are generally cross-platform, but the server-level authorization is Windows-centric.
Recommendations
- Add equivalent Linux guidance for server-level authorization, such as using .htaccess for Apache, nginx config, or middleware in popular Linux web frameworks.
- Include examples for customizing authorization on Linux-based App Service environments, possibly referencing platform-agnostic approaches (e.g., application code, environment variables).
- Present Windows and Linux options side-by-side, or clarify platform differences earlier in the section.
- Avoid language that implies Windows is the default or preferred platform; instead, treat both platforms equally in structure and examples.
App Service
Disable Basic Authentication for Deployment
...n/articles/app-service/configure-basic-auth-disable.md
High Priority
View Details →
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 explanations. In the deployment method table, Windows-centric tools are mentioned first or exclusively, and there is a lack of explicit Linux or cross-platform examples for deployment, troubleshooting, or agent configuration. There are no PowerShell-specific code blocks, but the overall framing and tool selection favor Windows environments.
Recommendations
- Include explicit Linux and macOS deployment examples, especially for command-line operations and troubleshooting.
- For each Windows-specific tool or workflow (e.g., Web Deploy, Visual Studio), mention and link to cross-platform or Linux-native alternatives (e.g., Kudu REST API, VS Code, or CLI-based deployments).
- In the deployment method table, clarify which methods are cross-platform and highlight any differences or requirements for Linux/macOS users.
- Add troubleshooting notes or links for Linux agents in Azure Pipelines, especially where Windows-specific caveats are discussed.
- Ensure screenshots and UI instructions are not Windows-centric, or provide equivalent instructions for Linux/macOS users where applicable.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific content and examples (such as parent images, IIS/.NET Framework details, and PowerShell commands) are often presented first or in greater detail. PowerShell commands are provided alongside Bash/Azure CLI, but Windows tooling and concepts (like C:\home, IIS, System.ConfigurationManager, and Kudu) are emphasized, sometimes with less parity for Linux equivalents. Some Linux-specific instructions are present, but in several sections, Linux examples are less detailed or missing, and Windows terminology is used even in Linux pivots (e.g., references to C:\home in Linux context).
Recommendations
- Ensure Linux and Windows pivots are equally detailed, with parallel examples and explanations for both platforms.
- Avoid referencing Windows paths (e.g., C:\home) in Linux sections; use appropriate Linux paths (/home) and clarify differences.
- Provide Linux-specific troubleshooting, diagnostic, and logging instructions, matching the detail given for Windows (e.g., Kudu, logs, SSH).
- Where PowerShell commands are given, ensure Bash/Azure CLI equivalents are always present and shown first or side-by-side.
- Highlight Linux container features (such as multi-container, Docker Compose, sidecars) with the same prominence as Windows features.
- Review terminology to avoid Windows-centric language in generic or Linux-focused sections.
- Add more Linux-specific examples for environment variable injection, persistent storage, and diagnostic access.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it provides both Azure CLI and PowerShell examples, PowerShell (a Windows-centric tool) is given equal prominence, and some advanced/bulk operations are only possible or documented for PowerShell. Several features (default documents, virtual directories, handler mappings) are explicitly described as Windows-only, with no Linux equivalents or workarounds mentioned. Some instructions and file path examples use Windows conventions (e.g., backslashes, D:\home), and there is little guidance for Linux users in these areas.
Recommendations
- Clearly indicate platform support for each feature at the start of relevant sections, not just in passing.
- For features that are Windows-only (default documents, handler mappings, virtual directories), provide explicit notes about the lack of Linux support and, where possible, suggest Linux alternatives or workarounds (e.g., using startup commands, .htaccess, or custom container entrypoints).
- Where PowerShell is used for advanced/bulk operations, provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if such operations are not supported cross-platform.
- Use platform-neutral file path examples where possible, or provide both Windows and Linux path formats.
- In sections where only Windows tools or patterns are mentioned, add Linux-specific guidance or links to relevant Linux documentation.
- Consider reordering examples so that cross-platform tools (Azure CLI) are presented before PowerShell, to reduce the perception of Windows-first bias.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased towards Windows. Gateway-required virtual network integration is only supported for Windows plans, with explicit statements that Linux apps are not supported. All troubleshooting and connectivity examples use Windows tools (PowerShell's Test-NetConnection, netstat, tcpping), with no mention of Linux equivalents. There are no Linux-specific instructions, examples, or troubleshooting steps, and Windows terminology and UI are used throughout.
Recommendations
- Clearly state Linux limitations early, but also provide guidance for Linux users on alternative approaches (e.g., regional VNet integration).
- Where troubleshooting steps use Windows tools (e.g., Test-NetConnection, netstat), provide Linux equivalents (e.g., nc, ss, netcat, curl) in parallel.
- Add explicit examples or notes for Linux users, even if only to direct them to supported alternatives.
- Ensure UI instructions are platform-neutral or clarify where differences exist for Linux plans.
- Consider a dedicated section comparing Windows and Linux support for VNet integration, with links to Linux-specific documentation.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows instructions and tools (such as Visual Studio and Kudu) are introduced first, with detailed steps for accessing runtime versions and using Windows-specific consoles (CMD, PowerShell). Visual Studio is referenced as the primary publishing tool, and Kudu is mentioned exclusively for Windows. Linux equivalents (such as Oryx, Cloud Shell, and build automation variables) are covered separately and sometimes with less detail. Some sections, like accessing diagnostic logs and exception pages, do not provide Linux-specific troubleshooting or tool references. The overall structure and example order tend to favor Windows scenarios.
Recommendations
- Ensure Linux instructions and examples are presented with equal prominence and detail as Windows, possibly alternating order or combining where possible.
- Provide Linux equivalents for all Windows tools mentioned (e.g., mention Oryx or SSH access alongside Kudu and PowerShell).
- Include Linux-specific troubleshooting steps and diagnostic log access methods.
- Reference cross-platform publishing tools (such as dotnet CLI, GitHub Actions, Azure CLI) alongside Visual Studio.
- Clarify where features or steps differ between Windows and Linux, and avoid assuming Visual Studio as the default tool.
- Add more Linux-focused examples for multi-project deployments, environment variable access, and exception handling.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (CMD, PowerShell, Kudu), Windows file paths, and Visual Studio workflows. There are no Linux-specific examples or instructions for equivalent tasks, such as inspecting .NET Framework versions or accessing environment variables in Linux containers. The documentation assumes a Windows environment throughout, with no parity for Linux users except a brief mention of custom containers.
Recommendations
- Add Linux-specific instructions and examples for each configuration task, especially for inspecting .NET runtime versions and accessing environment variables.
- Include references to Linux tools (e.g., Bash, SSH, Linux file paths) and how to perform similar operations in Linux-based App Service environments.
- Present both Windows and Linux approaches side-by-side or clarify which instructions apply to each platform.
- Provide guidance for users deploying to Linux containers, including relevant commands and configuration patterns.
- Avoid assuming Visual Studio as the only deployment tool; mention cross-platform alternatives like VS Code, GitHub Actions, or Azure CLI from Linux.