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 326-350 of 2121 flagged pages
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/getting-started.md ...docs/blob/main/articles/app-service/getting-started.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 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. The .NET section includes Azure PowerShell and Visual Studio as primary options, with Linux-specific instructions (e.g., CLI) listed after. Python examples use 'windows' tabs and lack clear Linux-first instructions. The 'Next step' call-to-action is for deploying an ASP.NET app, reinforcing Windows/.NET as the default. Linux tools and workflows are less emphasized or missing in some stacks, and Windows tools are often mentioned first.
Recommendations
  • Ensure Linux and cross-platform tools (e.g., CLI, VS Code) are listed before or alongside Windows-specific tools like Visual Studio and PowerShell.
  • Provide explicit Linux examples and tabs for all stacks, especially for Python and .NET, rather than defaulting to 'windows' tabs.
  • Add parity for Linux deployment and management tools (e.g., Bash, Azure CLI) in all sections where Windows tools (PowerShell, Visual Studio) are mentioned.
  • Balance the 'Next step' call-to-action to include a non-Windows stack (e.g., Node.js, Java, Python) or provide multiple options.
  • Review and update all quickstart and tutorial links to ensure Linux instructions are as discoverable and detailed as Windows ones.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-custom-container.md ...in/articles/app-service/quickstart-custom-container.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Windows-focused pivots (Visual Studio, Powershell, CLI) before their Linux equivalents, and by providing dedicated sections for Windows-specific tools (Visual Studio, Powershell). Linux examples are present but appear after Windows ones, and there is no explicit parity for Linux command-line tooling (e.g., Bash or shell scripts) or IDEs beyond Visual Studio Code.
Recommendations
  • Ensure Linux pivots (e.g., Azure CLI, Bash, Linux IDEs) are presented with equal prominence and ordering as Windows pivots.
  • Add Linux-specific command-line examples (e.g., Bash scripts) alongside Powershell examples.
  • Include Linux-native tooling (such as nano, vim, or Linux container debugging tools) where Windows tools are mentioned.
  • Review the order of pivots to alternate or group by platform, rather than listing Windows pivots first.
  • Explicitly state platform parity and link to Linux documentation where applicable.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-custom-container.md ...ain/articles/app-service/configure-custom-container.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific instructions, examples, and terminology (such as PowerShell commands, Windows directory paths, and Windows container features) are often presented first or in greater detail than their Linux equivalents. Some sections provide extensive Windows-only details (e.g., parent images, IIS/.NET integration, memory/core limits), while Linux instructions are less detailed or omitted. PowerShell examples are included alongside Bash, but Windows tools and patterns (e.g., Kudu, C:\home) are referenced more frequently and sometimes without Linux parity.
Recommendations
  • Ensure Linux examples are provided wherever Windows examples appear, especially for advanced configuration (e.g., parent images, resource limits, diagnostic commands).
  • Present Linux and Windows instructions in parallel, or alternate which platform is described first to avoid implicit prioritization.
  • Expand Linux-specific sections to match the detail given to Windows (e.g., supported base images, environment variable injection, diagnostic tooling).
  • Include Linux-native troubleshooting and diagnostic steps (e.g., using Bash, Linux file paths, Linux container logs) in parity with Windows tools like Kudu and PowerShell.
  • Clarify platform differences in persistent storage, environment variable handling, and resource management, and provide explicit Linux guidance where only Windows is described.
  • Review and update references to Windows-only features (e.g., IIS, .NET Framework) to ensure Linux alternatives or limitations are documented.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-discover-net.md ...cles/app-service/app-service-migration-discover-net.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
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 (e.g., Apache, Nginx) or .NET Core apps running on Linux. All examples and capabilities described are tailored to Windows environments, with no guidance for Linux users.
Recommendations
  • Include discovery instructions and capabilities for .NET apps hosted on Linux web servers (e.g., Apache, Nginx, Kestrel).
  • Add examples and troubleshooting steps relevant to Linux environments.
  • Mention whether Azure Migrate supports Linux-based .NET app discovery, and if not, clarify the limitations.
  • Provide parity in dashboard features and error remediation guidance for Linux-hosted web apps.
  • Ensure related content links include Linux migration/discovery resources.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-gateway-required-vnet-integration.md ...service/configure-gateway-required-vnet-integration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased toward Windows. Gateway-required virtual network integration is explicitly stated to only work for Windows plans, and Linux apps are excluded. All troubleshooting and connectivity examples use Windows-centric tools and PowerShell commands (e.g., Test-NetConnection, netstat -aon), with no mention of Linux equivalents. There are no Linux-specific instructions, examples, or troubleshooting steps, and Windows tools are referenced exclusively.
Recommendations
  • Clearly indicate Windows-only limitations at the top of the page and provide guidance or links for Linux users to alternative integration methods.
  • Add Linux-specific troubleshooting steps and examples, such as using 'nc', 'telnet', or 'ss' for connectivity checks, and 'netstat', 'lsof', or 'ss' for port listening checks.
  • Where PowerShell commands are given, provide equivalent Bash/Linux commands side-by-side.
  • Reference Linux tools and patterns in troubleshooting and management sections, not just Windows tools.
  • Include a comparison table or section summarizing feature parity and alternatives for Linux users.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-nodejs.md ...main/articles/app-service/configure-language-nodejs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows instructions and tools (such as IISNode and web.config) are often presented first or in greater detail, with Linux equivalents sometimes relegated to later sections or less detailed explanations. PowerShell is referenced for Application Insights instrumentation, but Linux CLI or Bash alternatives are not provided. Some troubleshooting and configuration examples are Windows-specific (e.g., web.config), while Linux-specific issues are less explored. In several cases, Windows deployment patterns and tools are described before their Linux counterparts.
Recommendations
  • Ensure that Linux examples and instructions are presented with equal prominence and detail as Windows ones, ideally side-by-side.
  • Provide Bash or Azure CLI alternatives for all PowerShell instructions, especially for instrumentation and monitoring.
  • Expand troubleshooting sections to include Linux-specific issues and solutions, not just Windows (e.g., configuration file errors, container startup problems).
  • When mentioning Windows tools (like IISNode or web.config), immediately reference the Linux equivalent or clarify if none is needed.
  • Review the order of presentation so that neither platform is consistently prioritized over the other.
  • Where possible, use platform-neutral language and examples, or clearly mark platform-specific content.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate-in-code.md ...icles/app-service/configure-ssl-certificate-in-code.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows-specific instructions, examples, and code samples first and in greater detail. Windows certificate store access is explained with full C# and Java examples, while Linux equivalents are only briefly mentioned or deferred to external documentation. Windows tools and patterns (certificate store, environment variables, user profile loading) are described in depth, while Linux instructions are less prominent and lack parity in language coverage. Non-Windows languages (Node.js, PHP, Python) are referenced only as external links, with no direct examples provided.
Recommendations
  • Provide Linux-specific code samples for all major languages (C#, Java, Node.js, PHP, Python) directly in the documentation, not just as external references.
  • Present Linux and Windows instructions in parallel, with equal detail and prominence, rather than leading with Windows.
  • Include examples of accessing certificates in Linux environments outside containers, such as App Service on Linux.
  • Expand explanations of Linux certificate file formats and access patterns, matching the depth given to Windows certificate store usage.
  • Add guidance for Linux-specific tools and environment variables, similar to the coverage for Windows.
  • Ensure that all code samples and instructions are available for both platforms before referencing external documentation.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-local-git.md ...ocs/blob/main/articles/app-service/deploy-local-git.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
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, and references to running commands in a 'local PowerShell terminal' are prominent. There are mentions of Windows-specific tooling issues (e.g., native Node modules lacking Windows binaries), and troubleshooting examples reference Windows errors. There is no explicit mention or example of using Linux or macOS terminals for PowerShell, nor are there Linux-specific troubleshooting notes. The Git Credential Manager dialog is referenced, which is primarily a Windows tool. Overall, the documentation assumes or prioritizes Windows environments and tools, with limited consideration for Linux/macOS users.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including terminal commands and environment setup.
  • Clarify that Azure CLI commands work cross-platform and provide sample commands in Bash/zsh where appropriate.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., file permissions, SSH key authentication, native module compilation errors on non-Windows OS).
  • Mention alternatives to Git Credential Manager for Linux/macOS, such as credential helpers or SSH.
  • Balance PowerShell and CLI coverage, and note that PowerShell Core is available cross-platform, with examples for non-Windows shells.
  • Avoid referencing Windows-specific errors without also providing Linux/macOS equivalents or context.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-managed-instance.md ...ain/articles/app-service/configure-managed-instance.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows, with all examples and configuration instructions tailored exclusively for Windows environments. Only PowerShell scripts are supported for configuration, and features such as registry key management, RDP/Bastion access, and references to Windows-specific installers (MSI, COM, IIS) are present. There are no Linux equivalents or examples, and the operating system is explicitly stated as Windows Server 2022. The documentation does not mention or support Linux-based managed instances, nor does it provide parity for Linux tools or scripting languages.
Recommendations
  • Clearly state at the top that Managed Instance on Azure App Service is Windows-only, if Linux support is not planned.
  • If Linux support is planned or possible, add equivalent sections and examples for Linux (e.g., Bash scripts, Linux file system mounts, Linux configuration management).
  • Provide parity in tooling and scripting: allow Bash or shell scripts for configuration, and document how to use them.
  • Include Linux storage mount instructions (e.g., NFS, CIFS) and Linux credential management.
  • Offer troubleshooting and log locations for Linux environments.
  • If registry key adapters are Windows-only, clarify this and suggest Linux alternatives (e.g., environment variables, config files).
  • For remote access, document SSH-based diagnostics for Linux, not just RDP/Bastion.
  • Review FAQ and examples to ensure Linux users are not excluded or misled.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-continuous-deployment.md ...n/articles/app-service/deploy-continuous-deployment.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows evidence of Windows bias, notably in the 'External Git' section which states 'For Windows apps, you can select External Git...' and links to Kudu documentation, a tool historically associated with Windows-based App Service. There are no explicit Linux-specific instructions, examples, or clarifications for Linux App Service environments. The documentation also refers to Windows terminology and tools before or instead of Linux equivalents, and omits Linux-focused deployment patterns or troubleshooting.
Recommendations
  • Add explicit instructions and examples for configuring continuous deployment to Linux-based App Service apps, including any differences in workflow, authentication, or build providers.
  • Clarify whether 'External Git' and Kudu workflows apply equally to Linux and Windows App Service environments, and provide Linux-specific guidance if there are differences.
  • Include Linux command-line examples (e.g., Bash, SSH) alongside or before any Windows/PowerShell examples, where relevant.
  • Mention Linux-specific deployment considerations, such as file permissions, case sensitivity, or supported runtimes.
  • Review screenshots and UI references to ensure they are not Windows-centric, and add Linux UI variants if applicable.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/networking-features.md .../blob/main/articles/app-service/networking-features.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias primarily in its coverage of Hybrid Connections, where only Windows Server is mentioned as a supported platform for the Hybrid Connection Manager agent, with no reference to Linux support or alternatives. Additionally, the gateway-required virtual network integration feature is explicitly limited to Windows plans, and this limitation is described before discussing regional integration (which is cross-platform). There are no Linux-specific examples, tools, or parity notes throughout the document, and Windows-centric patterns are mentioned without Linux equivalents.
Recommendations
  • Explicitly state platform support for features like Hybrid Connections and gateway-required VNet integration, including whether Linux is supported or not.
  • If Linux is not supported for Hybrid Connection Manager, provide alternative solutions or workarounds for Linux users.
  • Add Linux-specific examples and guidance where relevant, especially for networking features that behave differently or have different requirements on Linux App Service plans.
  • Where features are Windows-only, mention this limitation early and suggest Linux alternatives if available.
  • Review and update documentation to ensure Linux parity in feature descriptions, examples, and troubleshooting guidance.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/webjobs-create/webjobs-supported-platforms.md ...includes/webjobs-create/webjobs-supported-platforms.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation lists Windows hosting options and file types before Linux equivalents, and gives explicit mention to Windows executables/scripts and PowerShell scripts, while Linux tools (e.g., Bash) are mentioned later and less prominently. There is a stronger emphasis on Windows-specific tools and patterns.
Recommendations
  • List Linux hosting options and file/script types before or alongside Windows equivalents to avoid perceived prioritization.
  • Provide equal detail and prominence for Linux tools (e.g., Bash, shell scripts) and scripting environments.
  • Include explicit examples for Linux (e.g., .sh scripts, Linux containers) and clarify parity in supported features.
  • Avoid grouping Windows-specific tools together at the top of lists; alternate or group by category (e.g., OS-specific, cross-platform).
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-app-service-arc.md ...b/main/articles/app-service/migrate-app-service-arc.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for resource queries, but PowerShell is given equal prominence to CLI, and no Linux-specific shell (bash) or scripting examples are provided. There is no mention of Linux tools or patterns, and the examples do not clarify cross-platform compatibility. The documentation also lacks explicit guidance for Linux users, such as using bash or shell scripts, and does not address potential differences in command usage or environment setup between Windows and Linux.
Recommendations
  • Add explicit bash/shell examples for all CLI commands to demonstrate usage on Linux and macOS.
  • Clarify that Azure CLI commands work cross-platform and provide any necessary notes about differences in shell environments.
  • Deprioritize PowerShell examples or move them after bash/CLI examples to avoid Windows-first impression.
  • Include troubleshooting or environment setup notes for Linux users, such as package installation or permissions.
  • Mention Linux-native tools or patterns where relevant, and ensure parity in guidance for both Windows and Linux users.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-app.md ...e/scenario-secure-app-access-microsoft-graph-as-app.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by providing installation instructions using Visual Studio's Package Manager Console (PowerShell) and referencing Windows-centric tooling before mentioning cross-platform alternatives. There are no explicit Linux-specific instructions or examples, and the command-line instructions do not clarify compatibility with Linux environments.
Recommendations
  • Explicitly mention that the .NET Core command-line instructions (dotnet CLI) work on Linux, macOS, and Windows.
  • Add Linux-specific installation instructions, such as using Bash or terminal commands, and clarify that Visual Studio and its Package Manager Console are Windows-only tools.
  • Provide guidance for Linux users on how to install .NET SDK and run the sample code in a Linux environment.
  • Include troubleshooting notes for common Linux issues (e.g., permissions, environment variables for managed identities).
  • Reorder instructions to present cross-platform (dotnet CLI) steps before Windows-specific (Visual Studio/PowerShell) steps.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-webjobs.md ...s/blob/main/articles/app-service/quickstart-webjobs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows examples and tools first, including Windows-specific scripting languages (CMD, Batch, PowerShell, F#) that have no Linux equivalents. The Windows tab lists more sample types than the Linux tab, and Windows tools/patterns (such as PowerShell and Batch) are mentioned exclusively. Linux examples are limited to cross-platform languages and Bash, with no Linux-specific scripting samples (e.g., shell variants, Python with Linux nuances). The order and breadth of examples favor Windows users.
Recommendations
  • Present Linux and Windows tabs in parallel, with equal prominence and similar breadth of examples.
  • Add Linux-specific scripting samples (e.g., zsh, sh, or other Linux shell scripts) to match the variety of Windows scripting samples.
  • Include Linux-specific instructions or notes where Windows-specific tools (e.g., PowerShell, Batch) are mentioned.
  • Ensure that any language or tool available on Windows is matched with an equivalent or alternative on Linux, or explain the absence.
  • Consider listing cross-platform languages (Python, Node.js, Java, PHP, .NET) before platform-specific scripts in both tabs.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/webjobs-sdk-how-to.md ...s/blob/main/articles/app-service/webjobs-sdk-how-to.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits Windows bias by exclusively providing examples and configuration paths using Windows conventions (e.g., C:\ paths), referencing Visual Studio tooling without mention of cross-platform alternatives, and omitting Linux/macOS-specific instructions or examples. There is no mention of Linux shell commands, Linux file paths, or cross-platform development environments such as VS Code. Windows-specific APIs and settings (e.g., ServicePointManager, WinHttpHandler) are referenced without noting platform differences or Linux equivalents.
Recommendations
  • Provide Linux/macOS equivalents for all file path examples (e.g., use /home/user/data/import alongside C:\data\import).
  • Include instructions and examples for running and developing WebJobs on Linux, such as using VS Code, JetBrains Rider, or the .NET CLI.
  • Mention cross-platform configuration and environment variable management (e.g., using export in Bash, .env files, etc.).
  • Clarify platform-specific APIs (e.g., ServicePointManager, WinHttpHandler) and note any differences or limitations on Linux/macOS.
  • Add notes or sections on deploying and running WebJobs in Linux-based environments, including troubleshooting tips for non-Windows platforms.
  • Reference cross-platform tools and patterns before or alongside Windows-specific ones, ensuring parity in documentation.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-dotnet-framework.md ...les/app-service/configure-language-dotnet-framework.md
High Priority View Details →
Scanned: 2025-09-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based deployment and management patterns for ASP.NET apps in Azure App Service. It references Windows-specific tools (such as Kudu's CMD/PowerShell console and Windows file paths), and does not provide equivalent Linux-based examples or guidance for Linux App Service environments. There are no Linux shell or container-native instructions, and Windows patterns are presented as the default or only option.
Recommendations
  • Add equivalent instructions and examples for Linux-based App Service environments, including how to check .NET runtime versions, access environment variables, and deploy apps.
  • When referencing Kudu or console access, clarify differences between Windows and Linux App Service plans, and provide Linux shell (bash) commands where appropriate.
  • Avoid presenting Windows tools and file paths as the default; instead, structure sections to address both Windows and Linux scenarios, or clearly indicate when a step is Windows-specific.
  • Include notes or links to Linux/container documentation in each relevant section, not just in the introductory note.
  • Where Visual Studio is mentioned, also reference cross-platform deployment tools (such as Azure CLI, GitHub Actions, or VS Code) that work on Linux/macOS.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-php.md ...ob/main/articles/app-service/configure-language-php.md
High Priority View Details →
Scanned: 2025-09-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is structured with a clear separation between Windows and Linux content using pivots, which is good for parity. However, there are several signs of Windows bias: Windows sections are often presented first, Windows-specific tools and patterns (like KuduScript, .dll extensions, and Windows file paths) are emphasized, and some deployment automation examples (e.g., custom deployment scripts for Composer, Bower, Gulp, Grunt) are only detailed for Windows, with no equivalent Linux guidance. In some areas, Linux instructions are less detailed or require more manual steps (e.g., editing .ini files via echo due to lack of editors).
Recommendations
  • Alternate the order of Windows and Linux pivots or present Linux first in some sections to avoid implicit prioritization.
  • Provide equivalent, detailed Linux examples for deployment automation tools (Composer, Bower, Gulp, Grunt), including how to generate and use custom deployment scripts in Linux App Service.
  • Where Windows-specific tools (like KuduScript) are recommended, clarify if/how they are supported on Linux, or provide Linux-native alternatives.
  • For file editing on Linux (e.g., .ini files), suggest practical alternatives or tools for editing files, or provide downloadable templates to reduce manual echo commands.
  • Ensure all troubleshooting and advanced configuration sections have Linux parity, with step-by-step instructions matching the detail level of Windows.
  • Highlight any differences in extension compatibility or deployment patterns between Windows and Linux, and provide guidance for both.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate-in-code.md ...icles/app-service/configure-ssl-certificate-in-code.md
High Priority View Details →
Scanned: 2025-09-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows-first bias: Windows-specific instructions, code samples, and certificate store usage are presented before Linux equivalents. Most code examples (especially for C# and Java) focus on Windows and the Windows certificate store, with Linux guidance being less detailed or deferred. Non-Windows languages (Node.js, PHP, Python, Java) are not given explicit Linux examples, and readers are directed to external documentation. Windows tools and patterns (certificate store, environment variables, file paths) are emphasized, while Linux approaches are less prominent or missing.
Recommendations
  • Provide Linux-specific code examples for all major languages (C#, Java, Node.js, PHP, Python) alongside Windows examples.
  • Present Linux and Windows instructions in parallel or in clearly separated sections/tabs, rather than Windows-first.
  • Include explicit Linux command-line instructions (e.g., bash, Linux file paths) where Windows/Powershell commands are shown.
  • Expand on Linux certificate handling patterns (e.g., using OpenSSL, Linux environment variables) to match the depth of Windows coverage.
  • Avoid referring users to external documentation for Linux scenarios when Windows examples are provided inline.
  • Ensure parity in screenshots, environment variable explanations, and troubleshooting tips for both platforms.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-azure-pipelines.md ...ob/main/articles/app-service/deploy-azure-pipelines.md
High Priority View Details →
Scanned: 2025-09-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific deployment methods (notably Web Deploy) are described in detail, with YAML examples defaulting to 'windows-latest' agents for these scenarios. The FAQ and troubleshooting sections focus on Windows agent requirements for Web Deploy, and there is no equivalent Linux-based deployment method or troubleshooting guidance. The documentation references IIS and Windows-specific patterns (such as web.config and iisnode) without Linux alternatives. While some steps mention both Windows and Linux App Service types, the more advanced or nuanced examples and error messages are Windows-centric.
Recommendations
  • Provide Linux-native deployment examples for advanced scenarios, especially for tasks like Web Deploy, or clarify Linux alternatives (e.g., using zip deploy or FTP).
  • In troubleshooting sections, include common Linux agent issues and their solutions, not just Windows-specific errors.
  • When referencing Windows tools (like IIS, web.config, iisnode), also mention Linux equivalents or note when they are not applicable.
  • Ensure that YAML examples alternate or equally represent both 'windows-latest' and 'ubuntu-latest' agents, especially in sections where the agent OS matters.
  • Explicitly state when a feature is Windows-only and suggest best practices for Linux users.
  • Add links to Linux-focused documentation or external resources where appropriate.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-container-azure-pipelines.md ...ticles/app-service/deploy-container-azure-pipelines.md
High Priority View Details →
Scanned: 2025-09-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on deploying Windows containers, with all examples, variables, and YAML configurations referencing Windows-specific images (e.g., 'windows-latest') and App Service for Windows. There are no Linux container examples, nor any mention of how to adapt the process for Linux-based containers or App Service for Linux. The prerequisites and instructions assume a Windows application and environment throughout.
Recommendations
  • Add parallel examples and instructions for deploying Linux containers, including YAML snippets using 'ubuntu-latest' or other Linux agents.
  • Include a section in prerequisites for Linux apps and Dockerfiles, clarifying any differences in setup.
  • Show how to select App Service for Linux in the deployment task, and provide the appropriate values for Linux container deployment.
  • Wherever variables or configuration options are given (e.g., vmImageName), show both Windows and Linux options side by side.
  • Explicitly mention that the process is similar for Linux containers and link to relevant Linux container documentation if available.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-ftp.md ...zure-docs/blob/main/articles/app-service/deploy-ftp.md
High Priority View Details →
Scanned: 2025-09-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools (such as Visual Studio and WinSCP), referencing Windows-centric FTP clients first, and omitting explicit Linux command-line or tool examples for FTP/S deployment. PowerShell examples are provided, but there are no Linux shell (e.g., curl, lftp, or standard ftp/sftp) command examples. The troubleshooting and connection instructions reference Windows-oriented documentation (e.g., WinSCP) and do not mention Linux alternatives or workflows.
Recommendations
  • Include Linux command-line examples for FTP/S deployment using common tools such as lftp, curl, or the standard ftp command.
  • List cross-platform or Linux-native FTP clients (such as FileZilla, lftp, or GNOME Files) alongside or before Windows tools like WinSCP and Visual Studio.
  • Provide shell (bash) script examples for retrieving FTP/S endpoints and deploying files, in addition to PowerShell.
  • Reference Linux-specific troubleshooting steps or documentation, such as firewall configuration on Linux or passive mode setup in Linux FTP clients.
  • Ensure parity in screenshots and walkthroughs for both Windows and Linux environments.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-github-actions/deploy-github-actions-publish-profile.md ...ithub-actions/deploy-github-actions-publish-profile.md
High Priority View Details →
Scanned: 2025-09-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides cross-platform examples for most stacks (Node.js, Python, Java, Tomcat, ASP.NET Core) using Ubuntu runners and Linux-friendly tooling. However, the ASP.NET (classic) example is Windows-specific: it uses 'windows-latest' runners, Windows paths, and Windows-only tools (NuGet, MSBuild) without offering a Linux alternative or mentioning cross-platform options. This prioritizes Windows for ASP.NET and omits Linux parity for that stack.
Recommendations
  • Add a Linux-based example for ASP.NET (classic) if possible, using Mono or .NET Core-compatible tools, or explicitly state if Windows is required.
  • Clearly indicate in the ASP.NET section why Windows runners/tools are necessary, if that is the case, to inform users of platform constraints.
  • For all stacks, ensure that both Windows and Linux runner options are shown when feasible, or provide guidance on cross-platform compatibility.
  • Consider reordering or grouping examples so that Linux and Windows parity is visually clear, rather than defaulting to Windows for certain stacks.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-diagnostics.md ...blob/main/articles/app-service/overview-diagnostics.md
High Priority View Details →
Scanned: 2025-09-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by frequently highlighting features as 'Windows apps only' (e.g., proactive CPU monitoring, proactive auto-healing, Navigator), providing more detail and tooling for Windows scenarios, and lacking equivalent Linux examples or guidance. Linux support is mentioned, but often as an afterthought, with fewer details and less parity in advanced diagnostics.
Recommendations
  • Provide equivalent Linux examples and detailed guidance for all diagnostic features, or clearly state if a feature is unavailable on Linux.
  • Ensure that Linux and container scenarios are described with the same depth as Windows, including screenshots and step-by-step instructions.
  • Where features are Windows-only, suggest alternative troubleshooting steps or tools for Linux users.
  • Reorganize sections so that Linux and Windows parity is clear, and avoid consistently listing Windows features first.
  • Add explicit callouts or comparison tables that summarize feature availability and differences between Windows and Linux App Service environments.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-managed-identity.md ...main/articles/app-service/overview-managed-identity.md
High Priority View Details →
Scanned: 2025-09-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides extensive Azure PowerShell examples and references, often giving them equal or greater prominence than Azure CLI. PowerShell is a Windows-centric tool, and its heavy use can signal a Windows bias. Additionally, there are no explicit Linux shell (bash) or platform-agnostic scripting examples, and no mention of Linux-specific tools or workflows. The documentation does not clarify cross-platform compatibility for PowerShell commands, which may lead Linux users to assume these instructions are Windows-only.
Recommendations
  • Include explicit bash (Linux shell) examples alongside PowerShell, especially for scripting and token retrieval.
  • Clarify that Azure CLI and PowerShell are both cross-platform, and indicate which commands work on Linux, macOS, and Windows.
  • When listing tabs or options, consider ordering Azure CLI before PowerShell to reflect its broader cross-platform usage.
  • Add notes or links to installing and using Azure PowerShell on Linux/macOS, or recommend Azure CLI as the default for non-Windows users.
  • Where PowerShell is not supported (e.g., adding user-assigned identity in App Service), suggest alternative Linux-friendly approaches.
  • Ensure that all code samples and instructions are tested and clearly marked as cross-platform where applicable.
GitHub Create Pull Request
← Previous Page 14 of 85 Next →