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 126-150 of 2121 flagged pages
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 subtle Windows bias by referencing Windows-specific tools and deployment patterns (such as Web Deploy and Visual Studio) without equivalent emphasis or examples for Linux users. Windows tools and deployment methods are mentioned first or exclusively in several places, and there are no explicit Linux or cross-platform deployment tool examples (e.g., SCP, rsync, or Linux-native deployment workflows). The CLI examples use Azure CLI (which is cross-platform), but the fallback and troubleshooting sections focus on Windows agents and tools, with only brief mentions of non-Windows agents.
Recommendations
- Include explicit Linux and macOS deployment examples, such as using SCP, SFTP, or rsync for file transfer, and demonstrate how to deploy from a Linux shell.
- When referencing deployment tools like Web Deploy and Visual Studio, also mention cross-platform alternatives (e.g., VS Code, Git CLI, or Azure CLI from Linux/macOS).
- In troubleshooting and fallback sections, provide guidance for both Windows and Linux agents, and clarify any differences in behavior or requirements.
- Reorder sections or tables to avoid always listing Windows tools and methods first; consider grouping by platform or providing parallel instructions.
- Add notes or links to documentation specifically for Linux/macOS users where workflows or tools differ.
Create Pull Request
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-specific concepts, tools, and examples (such as IIS, .NET Framework, Windows Server images, and PowerShell commands) are frequently presented first or in greater detail. PowerShell examples are provided alongside Bash, but Windows-specific tooling and patterns (like Kudu, C:\home, and registry settings) are emphasized. Some advanced configuration and diagnostic sections are more detailed for Windows containers, while Linux equivalents are either less detailed or missing. Linux content is present, but often appears after Windows content or with less coverage.
Recommendations
- Ensure Linux and Windows sections have parity in detail and coverage, especially for advanced configuration and diagnostics.
- Present Linux and Windows examples side-by-side, or alternate which platform is presented first in each section.
- Expand Linux-specific troubleshooting, logging, and diagnostic instructions to match the depth of Windows sections (e.g., SSH, Kudu, log access).
- Provide Linux equivalents for Windows-specific tools and patterns (e.g., clarify Kudu usage for Linux, explain /home vs C:\home, and detail environment variable injection for non-.NET stacks).
- Where PowerShell is used, ensure Bash/Linux CLI examples are equally prominent and complete.
- Review all notes and tips to ensure Linux users are not left out of important caveats or recommendations.
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 environments. Gateway-required virtual network integration is explicitly stated as only working for Windows plans, with Linux apps excluded. Troubleshooting and connectivity examples use Windows-specific tools and commands (such as PowerShell's Test-NetConnection and netstat), with no mention of Linux equivalents. The documentation does not provide Linux-specific guidance or parity in examples, and Windows terminology and tools are referenced first and exclusively.
Recommendations
- Clearly state Linux limitations earlier and provide alternative integration options for Linux apps.
- Include Linux troubleshooting examples using common tools (e.g., 'nc', 'ss', 'telnet', 'dig', 'netcat') alongside Windows/PowerShell commands.
- Reference Linux equivalents for environment variable inspection (e.g., using 'printenv' or 'env' in Kudu SSH console).
- Add a section or links for Linux users describing supported integration methods and how to achieve similar connectivity.
- Ensure parity in documentation structure by presenting Windows and Linux guidance side-by-side where possible, or explicitly noting when features are Windows-only.
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 towards Windows and Visual Studio workflows, with all examples and instructions assuming use of Visual Studio on Windows. Azure App Service (Windows) is selected by default, and there are no references to Linux-based App Service, 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 options.
Recommendations
- Include instructions and examples for deploying ASP.NET apps using cross-platform tools such as Visual Studio Code, Azure CLI, or GitHub Actions.
- Provide guidance for publishing to Azure App Service (Linux) and highlight differences in configuration or deployment steps.
- Add Linux/macOS equivalents for package management (e.g., dotnet CLI commands instead of PowerShell/Package Manager Console).
- Show how to connect to Azure SQL Database using sqlcmd or Azure Data Studio on Linux/macOS.
- Mention alternative editors (VS Code, JetBrains Rider) and workflows for non-Windows users.
- Clarify which steps are Windows-specific and provide parity for Linux/macOS environments where possible.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. While it covers both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric), certain features and examples are described as available only for Windows apps, with no Linux equivalents or workarounds provided. Windows-specific tools, patterns, and terminology (such as IIS handler mappings, virtual directories, and references to D:\home paths) are mentioned exclusively or before Linux alternatives. Some sections (e.g., default documents, handler mappings, path mappings) are explicitly limited to Windows, and this is not always accompanied by Linux guidance. PowerShell examples are extensive, and some bulk operations are noted as unavailable in PowerShell, but Linux-specific scripting or alternatives are not discussed.
Recommendations
- For every Windows-only feature (e.g., default documents, handler mappings, virtual directories), explicitly state the Linux equivalent or clarify if there is none, and provide recommended Linux-native approaches or workarounds.
- Where PowerShell is used for scripting, provide equivalent Bash or shell script examples for Linux users, especially for bulk operations.
- When referencing file paths (e.g., D:\home), also mention the Linux file system structure or container mount points as appropriate.
- If a feature is not available on Linux, suggest alternative best practices or link to relevant Linux/container documentation.
- Ensure that cross-platform tools (like Azure CLI) are presented first or equally, and highlight any differences in usage or behavior between Windows and Linux App Service plans.
- Add a summary table or section that clearly lists which configuration features are supported on Windows, Linux, or both, to help users quickly identify platform limitations.
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-specific tools and patterns, such as Visual Studio, Kudu (CMD/PowerShell), and Windows file paths. All examples for inspecting .NET Framework versions use Windows commands and directories, with no mention of Linux equivalents or how to perform these tasks on Linux-based App Service instances. There are no Linux-specific instructions, examples, or parity in tooling discussed.
Recommendations
- Add equivalent instructions and examples for Linux-based App Service instances, including how to check .NET runtime versions and access environment variables.
- Include Linux shell (bash) commands and file paths where appropriate, especially in sections showing runtime versions and accessing diagnostic logs.
- Mention Linux deployment patterns and tools (e.g., using VS Code, CLI, or Git on Linux) alongside Visual Studio.
- Clarify which instructions are Windows-specific and provide links or sections for Linux workflows.
- Ensure that references to Kudu, CMD, and PowerShell are balanced with Linux alternatives, such as SSH or bash consoles.
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-specific tools and workflows (Visual Studio, Kudu, PowerShell, CMD) are introduced before Linux equivalents, and Windows instructions often appear first in sections. Some features (like Visual Studio publishing and Kudu access) are described only for Windows, with Linux alternatives either missing or less detailed. Powershell and CMD are referenced for Windows, while Linux relies on Azure CLI and shell scripts. In some cases, Linux examples are present but less emphasized or detailed.
Recommendations
- Ensure that Linux instructions and examples are presented with equal prominence and detail as Windows, possibly alternating which platform is described first.
- Provide Linux equivalents for all Windows-specific tools and workflows (e.g., mention how to access runtime versions or logs without Kudu/PowerShell).
- Avoid assuming Visual Studio as the default tool; mention cross-platform alternatives like VS Code or CLI-based deployment for both platforms.
- Expand Linux sections to match the depth of Windows instructions, especially for deployment, diagnostics, and configuration.
- Where possible, unify instructions using platform-agnostic tools (e.g., Azure CLI) and clearly note any platform-specific differences.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation generally provides parity between Windows and Linux, but there are several instances of Windows bias. Windows examples and concepts (such as IISNode, web.config, and PowerShell) are introduced first or exclusively, and some troubleshooting and Application Insights instructions focus on Windows or PowerShell without equivalent Linux or Bash examples. Windows-specific tools and patterns (IISNode, web.config) are explained in detail, while Linux equivalents (such as nginx or container startup scripts) are not covered as thoroughly. Some sections (like troubleshooting and Application Insights instrumentation) lack Linux-specific guidance or examples.
Recommendations
- Alternate the order of Windows and Linux pivots so Linux is not always second.
- Provide Linux/Bash equivalents for PowerShell instructions, especially for Application Insights instrumentation.
- Expand troubleshooting guidance for Linux, including common errors and configuration files (e.g., nginx.conf, Dockerfile).
- Include more details about Linux hosting patterns (e.g., how containers are started, how to customize startup beyond PM2).
- Where Windows-specific tools (IISNode, web.config) are mentioned, offer Linux analogs or explain why they are not needed.
- Ensure all examples (especially in troubleshooting and advanced configuration) have both Windows and Linux variants.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by presenting Windows-specific instructions, examples, and code samples first and in greater detail. Windows certificate store access is described extensively for both C# and Java, while Linux instructions are limited to file-based access and only shown for C#. There are no Linux-specific code samples for Java, Node.js, PHP, or Python, and references to those platforms are deferred to external documentation. Windows tools and environment variables are mentioned more prominently, and Windows-centric patterns (certificate store usage) are prioritized.
Recommendations
- Add Linux-specific code samples for Java, Node.js, PHP, and Python, demonstrating how to load certificates from the provided Linux file paths.
- Present Linux and Windows instructions in parallel, or use tabs to allow users to select their platform, rather than listing Windows first.
- Provide equal detail for Linux scenarios, including environment variable usage and best practices for certificate management.
- Include references to common Linux tools (e.g., OpenSSL, keytool) for certificate handling, not just Windows certificate store.
- Clarify any platform-specific differences in certificate formats and access patterns, ensuring Linux users are not referred out-of-page for essential guidance.
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
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring virtual network integration, but the PowerShell section is significantly more detailed and step-by-step. PowerShell, a Windows-centric tool, is given equal or greater prominence than the cross-platform Azure CLI. There are no Linux-specific shell examples (e.g., Bash), nor are there references to Linux-native tools or workflows. The documentation assumes familiarity with PowerShell patterns and does not mention Linux or macOS environments.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, including environment variable usage and scripting patterns common on Linux.
- Clarify that both Azure CLI and PowerShell are cross-platform, but note any platform-specific caveats or installation instructions.
- Provide guidance for Linux/macOS users, such as how to install and use Azure CLI and PowerShell on those platforms.
- Balance the depth of examples: ensure CLI instructions are as detailed as PowerShell, including steps for checking subnet delegation and resource context.
- Mention alternative tools or workflows that are common in Linux environments, such as using REST API calls via curl or automation with shell scripts.
App Service
Configure Data Sources for Tomcat, JBoss, or Java SE Apps
...es/app-service/configure-language-java-data-sources.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides detailed, step-by-step instructions for configuring Tomcat data sources on Windows, including PowerShell scripts and Windows-specific file paths and tools. The Windows section is notably longer and more explicit than the Linux section, which relies more on high-level descriptions and expects familiarity with Linux scripting and package management. Windows-specific tools (PowerShell, .cmd files) are used exclusively in the Windows example, while Linux instructions are more generic and less detailed. There is a lack of parity in example depth and explicitness, with Windows examples being more comprehensive and Linux examples assuming prior knowledge.
Recommendations
- Provide equally detailed Linux examples, including sample bash scripts for startup configuration, file copying, and XSLT application.
- Include explicit Linux file paths and commands for all steps (e.g., copying Tomcat, setting CATALINA_BASE, checking for marker files).
- Offer sample Linux startup scripts analogous to the Windows 'startup.cmd' and 'configure.ps1', using bash and standard Linux utilities.
- Clarify Linux-specific troubleshooting steps and edge cases, similar to the Windows section.
- Ensure that Linux instructions do not assume advanced prior knowledge; make them beginner-friendly.
- Where PowerShell is used for Windows, provide bash or shell script equivalents for Linux.
- List Linux instructions before or alongside Windows instructions to avoid 'windows_first' bias.
App Service
SSH Access for Linux and Windows Containers
...ticles/app-service/configure-linux-open-ssh-session.md
High Priority
View Details →
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 briefly mentioned, with no equivalent command-line or PowerShell examples, and it is stated that Azure CLI SSH sessions are not supported for Windows. The Linux workflow is described in detail, while Windows is covered superficially.
Recommendations
- Add equivalent step-by-step instructions for connecting to Windows containers, including any available command-line or PowerShell methods, even if limited.
- Clarify or expand on browser-based SSH access for Windows containers, including screenshots and troubleshooting steps.
- If Azure CLI or PowerShell is not supported for Windows containers, explicitly state alternatives or workarounds.
- Ensure parity in example depth and tooling references for both platforms, or clearly explain platform limitations.
App Service
Configure CI/CD with Azure Pipelines
...ob/main/articles/app-service/deploy-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific deployment methods (Web Deploy) are described in detail, with explicit instructions and error messages about Windows agents. Examples for Web Deploy only use Windows agents, and troubleshooting focuses on Windows scenarios. The use of IIS and web.config for Node.js is highlighted, and Windows agent selection is often mentioned before Linux. There are no Linux equivalents or parity for Web Deploy, and Linux deployment patterns (such as SSH, rsync, or container-based workflows) are not discussed. The documentation assumes familiarity with Windows tools and patterns, and Linux-specific deployment nuances are underrepresented.
Recommendations
- Provide Linux-specific deployment examples, especially for scenarios where Windows-only tools (like Web Deploy) are unavailable.
- Explicitly mention alternative deployment methods for Linux agents, such as ZIP deploy, container deploy, or FTP.
- Clarify which tasks and deployment methods are cross-platform and which are Windows-only, ideally in a comparison table.
- Add troubleshooting and FAQ entries for common Linux agent issues, not just Windows/Web Deploy problems.
- Ensure that agent selection instructions (ubuntu-latest, windows-latest) are presented with equal prominence and context.
- Include examples for popular Linux frameworks and deployment patterns (e.g., Python, Node.js, Java) using Linux agents.
- Avoid assuming IIS/web.config patterns for Node.js and clarify Linux equivalents (e.g., using PM2, Nginx, or Apache).
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 environments by listing Windows-centric tools (PowerShell, Visual Studio, migration assistant for PowerShell scripts) and providing references and examples for these tools. Linux-native equivalents (such as Bash scripting or Linux deployment tools) are not mentioned, and Windows tools are often listed before cross-platform or Linux-friendly alternatives. There are no explicit Linux-specific examples or references, and the documentation assumes familiarity with Windows tooling.
Recommendations
- Add examples and references for Linux-native deployment methods, such as Bash scripts, SSH, and Linux package managers.
- Include parity for Linux command-line tools alongside PowerShell, such as showing az CLI usage in Bash or Zsh.
- Mention and link to Linux-friendly IDEs and editors (e.g., JetBrains Rider, Eclipse) in addition to Visual Studio.
- Provide guidance for deploying from Linux environments, including authentication flows and troubleshooting steps.
- Clarify which deployment methods and authentication types are cross-platform and which are Windows-specific.
- Add documentation for using App Service migration tools from Linux environments, if available, or note their limitations.
App Service
Configure continuous deployment
...n/articles/app-service/deploy-continuous-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing 'Windows apps' specifically in the External Git section, and by mentioning tools and patterns (such as Kudu) that are historically Windows-centric without clarifying Linux applicability. There are no explicit Linux or cross-platform examples, nor is there guidance for Linux users or mention of Linux-specific deployment considerations. The documentation assumes the reader is using the Azure portal, which is platform-agnostic, but does not provide parity for Linux scenarios or command-line alternatives (e.g., Bash, CLI).
Recommendations
- Add explicit examples and instructions for deploying Linux-based apps, including any differences in workflow or configuration.
- Clarify whether tools like Kudu and App Service Build Service work identically for Linux and Windows apps, and note any platform-specific limitations.
- Include Linux command-line examples (e.g., Bash, Azure CLI) alongside or in place of Windows-centric instructions.
- Avoid referring to features as 'for Windows apps' unless there is a Linux equivalent or a clear explanation of why Linux is not supported.
- Provide parity in troubleshooting and FAQ sections for Linux deployments.
App Service
Deploy From a Local Git Repository
...ocs/blob/main/articles/app-service/deploy-local-git.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions, but PowerShell is given a dedicated section with detailed steps, including automatic remote creation behavior specific to PowerShell. There are references to Windows-specific issues (e.g., native modules lacking Windows binaries) and tools (e.g., Git Credential Manager dialog, MSBuild for ASP.NET). The troubleshooting section highlights Windows-specific errors and solutions before mentioning Linux alternatives. There are no explicit Linux shell or platform-specific examples, and the documentation assumes the use of PowerShell and Windows tools in several places.
Recommendations
- Add explicit Linux/macOS terminal instructions and examples alongside PowerShell, especially for steps like creating the remote and configuring deployment.
- Mention platform-specific behaviors (e.g., how Git Credential Manager works on Linux/macOS, or alternatives like credential helpers).
- Include troubleshooting notes for common Linux/macOS errors (e.g., file permissions, SSH key issues, native module compilation on Linux).
- Balance references to build tools (e.g., mention dotnet CLI for .NET Core apps on Linux, not just MSBuild for ASP.NET).
- Clarify which steps are platform-agnostic and which require adaptation for Linux/macOS users.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits several forms of Windows bias. Windows-specific paths (e.g., D:\home\site\wwwroot) are mentioned before Linux equivalents, and the Kudu UI deployment method is noted as unavailable for Linux, with alternatives suggested only in a side note. PowerShell examples are provided for most deployment scenarios, while Linux shell or Bash equivalents are not always present. The use of Windows-centric terminology and tools (such as 'Advanced Tools' in the Azure portal and PowerShell commands) is prevalent, and Linux-specific deployment nuances or troubleshooting are not addressed. In some cases, features are marked as 'not supported' in PowerShell, but Linux alternatives are not elaborated.
Recommendations
- Present Linux and Windows paths and behaviors with equal prominence, ideally side-by-side or in a table.
- For each deployment method, provide both PowerShell and Bash (or Linux shell) examples, especially for local operations.
- When a feature is unavailable for Linux (e.g., Kudu UI), offer detailed Linux-friendly alternatives (such as FTP, CLI, or API) with step-by-step instructions.
- Include troubleshooting tips or notes for Linux users, especially where deployment behaviors differ from Windows.
- Avoid Windows-centric terminology or clarify when instructions apply to both platforms.
- Explicitly state platform limitations and provide parity guidance for Linux users.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. Windows tools (Visual Studio, WinSCP) are listed first or exclusively, PowerShell examples are provided without Linux shell equivalents, and there are no explicit Linux command-line or tool examples (e.g., lftp, FileZilla, curl, or sftp). The troubleshooting and connection instructions reference Windows tools and patterns, with no mention of Linux-specific alternatives or guidance.
Recommendations
- Add Linux shell examples for FTP/S endpoint retrieval (e.g., using curl, lftp, or ftp commands).
- Include Linux-friendly FTP/S clients (e.g., FileZilla, lftp, gFTP) alongside Windows tools in the deployment section.
- Provide Bash or shell script equivalents for PowerShell commands.
- Mention Linux-specific firewall configuration considerations for FTP/S ports.
- Ensure troubleshooting steps reference both Windows and Linux environments, including relevant logs and error messages.
- Reorder or balance tool recommendations so that Linux and cross-platform options are presented equally or before Windows-only tools.
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools and patterns (PowerShell, Web.config, IIS applicationInitialization) are referenced throughout, often before or in more detail than Linux alternatives. PowerShell examples are given equal prominence to Azure CLI, but some advanced configuration (custom warm-up, troubleshooting) relies on Windows-specific concepts (Web.config, IIS, D:\ paths) without Linux equivalents or guidance. There is no mention of Linux-specific troubleshooting paths or configuration files, and auto swap is explicitly unsupported for Linux, but this limitation is not explained or mitigated.
Recommendations
- Add Linux-specific troubleshooting guidance, including log file locations and relevant configuration files (e.g., appsettings.json, environment variables).
- Where Windows-specific features (Web.config, IIS applicationInitialization) are referenced, provide Linux alternatives or note their absence.
- Clarify limitations for Linux (e.g., auto swap not supported) and suggest workarounds or alternatives for Linux users.
- Ensure parity in examples: for every PowerShell example, provide a Bash or shell script equivalent where possible.
- Explicitly state when a feature or setting is Windows-only, and link to Linux/container documentation for comparable deployment slot workflows.
- Include notes or links for deploying with Linux-native tools (e.g., SCP, rsync, Git) and troubleshooting with Linux logs.
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 Azure PowerShell examples for configuring Traffic Manager and App Service Environments, with no mention of equivalent Linux-friendly tools such as Azure CLI or REST API. The use of PowerShell is presented as the 'easiest' method, and no alternative cross-platform instructions are offered. This may disadvantage users on Linux or macOS who do not use PowerShell.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands shown, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that the same operations can be performed via Azure CLI, REST API, or portal, and provide links or brief instructions.
- Avoid language that implies PowerShell is the only or preferred method; instead, present multiple options side-by-side.
- Include screenshots or terminal output from Linux environments where relevant, to demonstrate parity.
- Review related content and links to ensure Linux-friendly documentation is referenced.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows-specific logging types and instructions first and in greater detail. Several logging features (web server logging, detailed error messages, failed request tracing) are described only for Windows, with no Linux equivalent or alternatives provided. Windows tools and file paths are mentioned explicitly, while Linux instructions are brief and lack parity in features and examples.
Recommendations
- Add equivalent Linux logging features or clarify which features are unavailable on Linux, and suggest alternatives where possible.
- Provide Linux-specific examples and instructions for accessing and interpreting logs, including file paths and formats.
- Include information about Linux-compatible tools for log analysis and streaming, such as tail, grep, or third-party log viewers.
- Ensure that Linux and container instructions are as detailed as Windows instructions, including configuration, retention, and troubleshooting steps.
- Explicitly state feature parity or differences between Windows and Linux throughout the documentation, so users can make informed choices.
App Service
Routine Maintenance, Restarts, and Downtime
...n/articles/app-service/routine-maintenance-downtime.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by providing detailed explanations and examples for Windows-specific features (such as IIS Application Initialization and .NET Core stdout logging) before mentioning Linux equivalents, and sometimes omitting Linux-specific implementation details. Windows tools and modules are referenced directly, while Linux alternatives are only briefly mentioned or lack comparable depth.
Recommendations
- Provide Linux-specific examples and implementation details for features like application initialization, warm-up paths, and logging, similar to the Windows/IIS coverage.
- Ensure Linux mechanisms (e.g., WEBSITE_WARMUP_PATH) are explained with step-by-step instructions or code samples.
- Reference Linux-native tools and patterns (such as Nginx/Apache modules, systemd service readiness, or container health checks) where appropriate.
- Present Windows and Linux guidance in parallel, rather than Windows-first, to improve parity and accessibility for Linux users.
- Expand troubleshooting and logging sections to include Linux logging best practices (e.g., journald, syslog, file-based logging) and how to configure them for start-up diagnostics.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific paths and tools (e.g., D:\home, applicationHost.config, IIS, MSDeploy, Web Deploy) are frequently mentioned, often before or instead of Linux equivalents. Many environment variables and examples reference Windows conventions, tools, or behaviors, with Linux alternatives either missing, less detailed, or presented secondarily. Some sections (such as build automation and logging) are much more detailed for Windows/Kudu than for Linux/Oryx. Several settings are described as 'Windows only' or have Windows-centric explanations, while Linux-specific guidance is sparse or absent.
Recommendations
- Ensure all environment variable descriptions provide both Windows and Linux paths/examples where applicable (e.g., HOME, logging directories).
- Present Linux and Windows options side-by-side, or use tabs to separate platform-specific instructions, rather than listing Windows first.
- Expand Linux-specific documentation, especially for build automation (Oryx), logging, and deployment, to match the detail provided for Windows/Kudu.
- Include Linux equivalents for Windows tools (e.g., MSDeploy, applicationHost.config), or clearly state when a feature is Windows-only and suggest Linux alternatives.
- Add more Linux/POSIX-centric examples (e.g., shell commands, Linux file paths) and clarify any differences in environment variable behavior between platforms.
- Review all references to Windows-only features and ensure Linux users are guided to appropriate alternatives or workarounds.
App Service
Supported platforms and file types
...includes/webjobs-create/webjobs-supported-platforms.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation lists Windows hosting options and file types before Linux equivalents, and gives more detailed attention to Windows-specific tools (executables, batch files, PowerShell scripts) before mentioning Bash and other scripting languages. This ordering and emphasis may suggest a Windows-centric perspective.
Recommendations
- List Linux hosting options and file types alongside or before Windows equivalents to avoid implicit prioritization.
- Provide equal detail for Linux tools and scripting options (e.g., mention shell scripts, Linux utilities, and their usage).
- Include examples for both Windows and Linux platforms to demonstrate parity.
- Explicitly state that both Windows and Linux are first-class citizens for WebJobs, and highlight any platform-specific considerations.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias in several areas: Windows paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are referenced first and exclusively in backup filter instructions, with no Linux equivalents provided. Tools and workflows such as Kudu DebugConsole and FTP are described using Windows-centric terminology and paths. Examples for file exclusion and backup configuration use Windows-style paths and do not mention Linux alternatives. There are no explicit Linux command-line or file system examples, and instructions for Linux users are missing or only referenced generically. The documentation also references Windows-specific features (e.g., MySQL in-app for Web Apps (Windows)) before Linux equivalents.
Recommendations
- Add Linux-specific examples for file paths (e.g., /home/site/wwwroot instead of D:\home\site\wwwroot) and environment variables ($HOME instead of %HOME%).
- Include instructions and screenshots for Linux-based App Service environments, especially for tasks like creating and uploading the _backup.filter file.
- Provide parity in tool references, such as mentioning Linux-compatible methods for file upload (e.g., SCP, SFTP, Azure CLI) alongside FTP and Kudu.
- Ensure that all examples and troubleshooting steps reference both Windows and Linux platforms, or clarify platform-specific differences.
- When mentioning features or limitations, list Linux and Windows options together, or alternate the order to avoid Windows-first presentation.