App Service

806
Total Pages
669
Linux-Friendly Pages
137
Pages with Bias
17.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

247 issues found
Showing 126-150 of 247 flagged pages
App Service App Service Managed Certificate (ASMC) Changes – July 28, 2025 ...e/app-service-managed-certificate-changes-july-2025.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides a PowerShell script as the primary method for identifying impacted Traffic Manager endpoints, with no equivalent Bash, Azure CLI, or cross-platform example. The instructions for running the script are Windows-centric (PowerShell only), and Linux/macOS alternatives are not mentioned. The rest of the page generally uses Azure CLI and REST API references, but the critical resource identification workflow is Windows/PowerShell biased.
Recommendations
  • Provide an equivalent Bash or Azure CLI script for identifying non-Azure Traffic Manager endpoints, or clarify how Linux/macOS users can perform the same check.
  • Explicitly mention cross-platform alternatives when referencing PowerShell scripts.
  • Reorder or supplement instructions so that CLI or REST API methods are presented alongside or before Windows/PowerShell-specific tools.
  • Add a note clarifying platform compatibility for all scripts and tools.
GitHub Create Pull Request
App Service Deploy Content Using FTP/S ...zure-docs/blob/main/articles/app-service/deploy-ftp.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (Visual Studio, WinSCP) are mentioned before cross-platform or Linux-native alternatives, and PowerShell is given equal prominence to Azure CLI, despite being Windows-centric. There are no explicit Linux command-line FTP client examples (e.g., lftp, curl, or ftp), nor are Linux GUI clients (e.g., FileZilla, Nautilus) referenced. Troubleshooting and connection examples reference WinSCP documentation, which is Windows-only. This may create friction for Linux/macOS users, who must adapt instructions or seek alternative tools.
Recommendations
  • Add explicit Linux/macOS FTP client examples (e.g., lftp, FileZilla, curl) in the 'Deploy files to Azure' section.
  • Mention cross-platform tools first, or at least equally, before Windows-only tools like WinSCP and Visual Studio.
  • Include Linux/macOS-specific command-line instructions for connecting to FTP/S endpoints.
  • Reference documentation for cross-platform FTP clients (e.g., FileZilla, Cyberduck) in troubleshooting and connection sections.
  • Clarify that Azure CLI is cross-platform and encourage its use for Linux/macOS users.
  • Add a note or section for Linux/macOS users outlining any differences or considerations.
GitHub Create Pull Request
App Service Configure Node.js Apps ...main/articles/app-service/configure-language-nodejs.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally well-structured for both Windows and Linux, using pivot sections for platform-specific instructions. However, there are notable signs of Windows bias: Windows examples and tools (such as IISNode and web.config) are described in greater detail, sometimes before Linux equivalents. PowerShell is referenced for Application Insights instrumentation, but no Linux CLI or Bash alternative is provided. The troubleshooting section for Windows is more extensive, and some advanced configuration (like web.config) is only covered for Windows, with no Linux parallel. In a few cases, Windows instructions or references appear before Linux ones, and some tooling (IISNode, web.config) is Windows-specific without Linux alternatives explained.
Recommendations
  • Provide Linux/Bash alternatives for all PowerShell or Windows-specific instructions, especially for Application Insights instrumentation.
  • Ensure Linux troubleshooting and configuration sections are as detailed as Windows ones (e.g., explain Linux equivalents for web.config, IISNode, or provide links to relevant Linux configuration files).
  • Present Windows and Linux examples in parallel or alternate which platform appears first to avoid implicit prioritization.
  • Where Windows-specific tools are mentioned (IISNode, web.config), explicitly state their Linux counterparts or clarify that they are not applicable on Linux, and provide Linux best practices.
  • Expand Linux sections to match the depth and clarity of Windows sections, especially in troubleshooting and advanced configuration.
GitHub Create Pull Request
App Service Authentication Types by Deployment Methods ...in/articles/app-service/deploy-authentication-types.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page lists deployment methods and authentication types for Azure App Service. It includes several Windows-centric tools (Azure PowerShell, Visual Studio, App Service migration assistant, migration assistant for PowerShell scripts) and references to Windows-first workflows. Examples and references for Linux-native tools (such as Bash, shell scripting, or Linux IDEs) are missing, and Windows tools are mentioned before cross-platform or Linux alternatives in several cases.
Recommendations
  • Add explicit examples and references for Linux/macOS users, such as Bash scripts for Azure CLI and deployment.
  • Include parity for Linux IDEs (e.g., JetBrains Rider, Eclipse, VS Code on Linux) in deployment documentation.
  • Clarify which tools are cross-platform and provide guidance for Linux/macOS usage where PowerShell or Visual Studio is mentioned.
  • Provide links to Linux/macOS-specific documentation or troubleshooting guides.
  • Ensure that cross-platform tools (like Azure CLI and VS Code) are highlighted before Windows-only tools.
GitHub Create Pull Request
App Service Hybrid Connections in Azure App Service ...articles/app-service/app-service-hybrid-connections.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions, tools, and examples are frequently presented first, and troubleshooting steps often reference Windows-specific tools (e.g., PowerShell's Test-NetConnection) without Linux equivalents. The GUI for Hybrid Connection Manager is only available on Windows, with Linux users relegated to CLI usage. Some troubleshooting and connectivity tests are described only for Windows, and legacy tooling is Windows-only. However, Linux installation and usage are covered, and CLI instructions are provided for both platforms.
Recommendations
  • Provide Linux-first or parallel examples for all troubleshooting steps, including alternatives to PowerShell commands (e.g., using 'nc', 'telnet', or 'curl' for connectivity tests).
  • Explicitly mention Linux equivalents for all Windows tools and commands, especially in troubleshooting sections.
  • Consider developing or recommending a cross-platform GUI for Hybrid Connection Manager, or clarify the roadmap for Linux GUI support.
  • Ensure parity in upgrade instructions and notifications for Linux users.
  • Where legacy tools are referenced, clarify Linux alternatives or explicitly state limitations.
  • In all step-by-step guides, present Windows and Linux instructions side-by-side, rather than Windows-first.
GitHub Create Pull Request
App Service Azure App Service Plans ...ob/main/articles/app-service/overview-hosting-plans.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the 'Managed Instance on Azure App Service' section, which is exclusively for Windows workloads and highlights Windows-specific tools (PowerShell, RDP, IIS, COM, MSI). The managed instance feature is not available for Linux, containers, or App Service Environment, and no Linux equivalents or examples are provided. Additionally, links and feature tables sometimes reference Windows-specific pricing and features before Linux. However, the main App Service plan content does acknowledge Linux as a supported OS and most general guidance applies to both platforms.
Recommendations
  • Add explicit Linux examples and guidance where features differ or are unavailable.
  • Include Linux/container-specific managed hosting options or clarify alternatives for Linux users.
  • Balance the order of presentation so Linux is mentioned equally or first where appropriate.
  • Provide links to Linux-specific documentation for scaling, pricing, and advanced features.
  • Clearly indicate which features are Windows-only and suggest Linux alternatives or workarounds.
GitHub Create Pull Request
App Service Use Key Vault References as App Settings ...ticles/app-service/app-service-key-vault-references.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuration tasks, but consistently includes PowerShell (a Windows-centric tool) alongside CLI. In some cases, PowerShell examples are given equal prominence to CLI, and the CLI examples do not mention Linux-specific shell nuances. No Linux/macOS-specific tools or patterns are discussed, and troubleshooting steps reference the Azure portal (cross-platform) but do not mention command-line alternatives for Linux users. There are no explicit Linux/macOS examples or considerations for shell environments.
Recommendations
  • Add explicit Linux/macOS shell examples (e.g., bash, zsh) where CLI commands are shown, including environment variable handling and quoting.
  • Clarify that Azure CLI commands work on Linux/macOS and provide any necessary notes about differences (such as authentication or shell syntax).
  • If PowerShell is shown, consider also showing bash equivalents for scripting tasks.
  • Mention Linux-specific troubleshooting or diagnostic approaches (e.g., using az CLI for status checks) alongside portal-based steps.
  • Where platform-specific configuration is required (e.g., networking for Linux apps), highlight any differences or additional steps for Linux.
GitHub Create Pull Request
App Service Restore Deleted Apps ...blob/main/articles/app-service/app-service-undelete.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell-based command-line examples and referencing the Az PowerShell module for automation. There are no CLI examples using cross-platform tools like Azure CLI, Bash, or scripting for Linux/macOS users. The PowerShell approach is presented as the only automation method, which can create friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and provide installation guidance if PowerShell usage is required.
  • Reorder sections or add notes to clarify that both portal and CLI methods are available regardless of OS.
  • Where possible, provide Bash script examples or highlight REST API options for advanced users.
GitHub Create Pull Request
App Service Fix HTTP 502 and HTTP 503 Errors ...articles/app-service/troubleshoot-http-502-http-503.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the use of Windows-centric tools and examples. The Kudu debug console section highlights PowerShell cmdlets and DOS commands, with no mention of Bash or Linux shell support. The use of ProcDump (a Sysinternals tool) is referenced without alternatives for Linux. Additionally, the restart section only provides a PowerShell example for managing the app, omitting Azure CLI or Bash equivalents. No explicit Linux/macOS troubleshooting commands or patterns are provided.
Recommendations
  • Include examples using Bash or Azure CLI for managing and troubleshooting the app, alongside PowerShell.
  • Clarify that Kudu supports both PowerShell and Bash consoles, and provide Linux/macOS command examples.
  • Mention cross-platform alternatives to ProcDump, such as dotnet-dump or gcore, for memory dumps on Linux.
  • Ensure all tool recommendations and code samples are presented for both Windows and Linux/macOS users, or note platform limitations explicitly.
GitHub Create Pull Request
App Service Tutorial: Connect a web app to SQL Database on behalf of the user ...utorial-connect-app-access-sql-database-as-user-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. While most command-line examples use Azure CLI (cross-platform), critical database management steps reference Windows-centric tools such as SQL Server Management Studio (SSMS) and sqlcmd, with no mention of Linux/macOS alternatives. Visual Studio is referenced for publishing, and Windows terminology (e.g., Integrated Windows authentication) appears before Linux equivalents. No Linux-specific tools (like Azure Data Studio) or explicit parity for Linux/macOS users are provided in database connection or publishing sections.
Recommendations
  • Include instructions for connecting to Azure SQL Database using Azure Data Studio, which is cross-platform, or provide explicit sqlcmd installation and usage steps for Linux/macOS.
  • Add publishing instructions for .NET apps using the dotnet CLI, which works on Linux/macOS, alongside Visual Studio steps.
  • Mention Linux/macOS alternatives for any Windows-specific tools (e.g., SSMS) and clarify which steps are platform-agnostic.
  • When referencing authentication patterns, briefly note Linux/macOS equivalents or differences (e.g., Kerberos, Active Directory integration).
  • Ensure screenshots and walkthroughs do not assume Windows-only environments.
GitHub Create Pull Request
App Service Customize Sign-ins and Sign-outs ...vice/configure-authentication-customize-sign-in-out.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally presents platform-neutral guidance, but in the 'Server level (Windows apps only)' section, it exclusively describes IIS and web.config-based authorization for Windows apps, with no Linux equivalent or alternative provided. The use of Kudu (primarily a Windows tool) is described in detail, and the Windows approach is presented before mentioning that Linux apps cannot use this method. No Linux-specific authorization example or workaround is offered.
Recommendations
  • Add a Linux-specific section describing how to implement server-level authorization for Linux-based App Service apps, such as using middleware in popular frameworks (Node.js, Python, .NET Core, etc.) or configuring access via NGINX/Apache if applicable.
  • Provide parity by including examples for both Windows and Linux platforms where platform-specific configuration is required.
  • Explicitly link to or describe alternative approaches for Linux users when a Windows-only method is presented.
  • Avoid presenting Windows-only solutions first or exclusively in critical sections; ensure Linux/macOS users have clear guidance.
GitHub Create Pull Request
App Service Configure Sign in with Apple (Preview) ...app-service/configure-authentication-provider-apple.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a code example for generating the Apple client secret JWT using C# and the Microsoft.IdentityModel.Tokens NuGet package, which is Windows-centric and does not offer equivalent examples for Linux/macOS users (e.g., using Python, Node.js, or OpenSSL). No mention is made of Linux tools or cross-platform alternatives, and the example assumes a Windows development environment.
Recommendations
  • Add code examples for generating the JWT client secret using cross-platform languages such as Python (with PyJWT), Node.js (with jsonwebtoken), or command-line tools like OpenSSL.
  • Explicitly mention that the JWT generation can be performed on any OS and provide links or references to Linux/macOS-friendly libraries and tools.
  • Reorder or supplement the documentation so that Windows-specific tools are not presented as the only or primary method.
  • Include instructions for handling the .p8 key and JWT signing using Linux command-line utilities.
GitHub Create Pull Request
App Service Configure a Custom Container ...ain/articles/app-service/configure-custom-container.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific instructions, examples, and tools (such as PowerShell and Windows base images) are often presented first or in greater detail. PowerShell commands are provided alongside Bash, but sometimes with more explanation or tips. Windows-centric concepts (like C:\home, IIS, .NET Framework, Windows Server images) are described in depth, while Linux equivalents are sometimes less detailed or missing. Some troubleshooting and diagnostic sections focus on Windows tools and patterns, and certain advanced configuration topics (like customizing ASP.NET machine keys, group managed service accounts, and compute core/memory limits) are only covered for Windows containers. Linux instructions are present but sometimes less prominent or detailed.
Recommendations
  • Ensure Linux examples and instructions are presented with equal prominence and detail as Windows examples, including advanced configuration topics.
  • Provide Linux-first or side-by-side examples for all CLI and scripting instructions, not just Bash but also relevant Linux tools and patterns.
  • Expand Linux-specific troubleshooting, diagnostic, and advanced configuration sections to match the depth of Windows coverage.
  • Avoid presenting Windows instructions or tools before Linux equivalents unless contextually necessary; consider parallel presentation.
  • Clarify where features or settings differ between Windows and Linux, and provide explicit guidance for both platforms.
GitHub Create Pull Request
App Service Configure ASP.NET Apps ...les/app-service/configure-language-dotnet-framework.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. It primarily describes configuration and runtime inspection tasks for ASP.NET apps in Azure App Service using Windows-specific tools and paths (e.g., Kudu CMD/PowerShell, Windows file system locations), without providing equivalent Linux instructions or examples. The guidance assumes the use of Visual Studio and Windows-based deployment flows, with no mention of Linux-based workflows or tools for .NET Framework apps. Linux users may find it difficult to apply these instructions directly, especially for runtime version inspection and environment access.
Recommendations
  • Add explicit instructions and examples for Linux-based App Service plans, including how to inspect .NET Framework/Mono runtime versions and access environment variables.
  • Include Linux shell (bash) commands and file paths where relevant, alongside Windows CMD/PowerShell examples.
  • Clarify which steps are Windows-only and provide links or guidance for Linux alternatives (e.g., using custom containers or .NET Core on Linux).
  • Mention cross-platform deployment tools (e.g., dotnet CLI, GitHub Actions) and workflows, not just Visual Studio.
  • Reorder examples so that Windows and Linux instructions are presented with equal prominence.
GitHub Create Pull Request
App Service Configure Data Sources for Tomcat, JBoss, or Java SE Apps ...es/app-service/configure-language-java-data-sources.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Linux and Windows instructions for configuring data sources in Tomcat and JBoss apps on Azure App Service. However, the Windows section relies heavily on Windows-specific tools (PowerShell scripts, .cmd files, Windows environment variables) and provides detailed, step-by-step instructions using these tools. Linux instructions use shell scripts and standard Linux utilities, but the Windows examples are more elaborate and tool-specific. In several places, Windows tooling (PowerShell, .cmd) is presented as the default or primary method for Windows users, with no cross-platform alternatives (e.g., Bash for Windows). The ordering of sections sometimes places Windows instructions before Linux, and the Windows configuration process is described in greater detail.
Recommendations
  • Provide equivalent Bash or cross-platform scripting examples for Windows users who may prefer WSL or non-PowerShell environments.
  • Ensure Linux and Windows instructions are presented with equal detail and clarity, especially for complex configuration steps.
  • Where possible, use platform-agnostic tools (such as Azure CLI) for configuration steps, and highlight these as the preferred method.
  • Present Linux and Windows instructions side-by-side or in parallel tabs to avoid the perception of Windows-first bias.
  • Add explicit notes when a step is Windows-only, and provide Linux/macOS alternatives or workarounds.
GitHub Create Pull Request
App Service Use TLS/SSL Certificates in App Code ...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows-specific certificate store access is described in detail, with C# and Java examples provided for Windows apps and containers. Windows certificate store concepts and tools are explained first and in greater depth. Linux guidance is limited to file-based access, with only C# examples for Linux containers, and other languages (Node.js, PHP, Python, Java) are deferred to external documentation. There are no Linux-native code examples for languages other than C#, and the Windows workflow is presented as the default or primary pattern.
Recommendations
  • Provide Linux-first or parallel examples for certificate access, especially for popular languages (Node.js, Python, Java, PHP) directly in the documentation.
  • Include Linux-specific tools and patterns (e.g., OpenSSL, environment variable usage, file permissions) where relevant.
  • Balance the depth of explanation for Windows and Linux approaches, ensuring Linux users receive equally actionable guidance.
  • Avoid presenting Windows workflows as the default; use neutral or platform-parallel organization.
  • Add explicit Linux code samples for Java and other major languages, not just C#.
GitHub Create Pull Request
App Service Secure Your Domain with TLS/SSL ...ob/main/articles/app-service/configure-ssl-bindings.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias in its automation section, providing a PowerShell script example for binding a TLS/SSL certificate but omitting equivalent Linux/macOS shell (Bash) examples. The Azure CLI is mentioned, but only as a link without inline code, while the PowerShell example is shown directly. No Linux-specific tools or workflows are discussed, and Windows-centric scripting appears prioritized.
Recommendations
  • Provide inline Azure CLI examples alongside PowerShell, especially for certificate binding tasks.
  • Include Bash shell script snippets for Linux/macOS users where automation is discussed.
  • Explicitly mention cross-platform compatibility for all automation steps.
  • Ensure that any referenced scripts or workflows are available and tested on Linux/macOS environments.
  • Balance the order of examples, showing CLI/Bash first or side-by-side with PowerShell.
GitHub Create Pull Request
App Service Install a TLS/SSL Certificate for Your App ...main/articles/app-service/configure-ssl-certificate.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for RBAC assignment, but PowerShell is highlighted as a primary automation method in the FAQ. Windows-specific tools (IIS, Certreq.exe) are mentioned for certificate export, while Linux alternatives are not described. The FAQ and automation sections list PowerShell before CLI, and some advanced scenarios (like outbound client certificate usage) are noted as Windows-only. However, OpenSSL is referenced for certificate creation/export, which is cross-platform, and Azure CLI examples are present.
Recommendations
  • Add explicit Linux/macOS instructions for certificate export (e.g., using OpenSSL for all scenarios, not just when the request was generated with OpenSSL).
  • In automation sections, present Azure CLI and PowerShell examples side-by-side, or lead with CLI as the more cross-platform option.
  • Clarify which features/scenarios are Windows-only and suggest Linux/macOS alternatives or workarounds where possible.
  • Where Windows tools are mentioned (IIS, Certreq.exe), provide equivalent Linux/macOS steps or links.
  • In FAQ and automation, avoid listing PowerShell first unless it is the only option.
GitHub Create Pull Request
App Service Enable integration with an Azure virtual network ...icles/app-service/configure-vnet-integration-enable.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides detailed Azure PowerShell instructions alongside Azure CLI, but the PowerShell section is much more extensive and step-by-step. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux/macOS users. The CLI example is brief and lacks the depth of the PowerShell walkthrough. No Linux-specific shell examples (e.g., bash, zsh) or platform notes are provided. The order of presentation (CLI, then PowerShell) is reasonable, but the depth of PowerShell coverage suggests a bias toward Windows users.
Recommendations
  • Expand Azure CLI instructions to match the detail and step-by-step guidance provided for PowerShell.
  • Add explicit notes clarifying that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Include bash/zsh example commands where relevant, or clarify that CLI commands work identically on Linux/macOS.
  • Consider adding troubleshooting or context sections for Linux/macOS users (e.g., common permission issues, environment setup).
GitHub Create Pull Request
App Service Configure CI/CD with Azure Pipelines ...ob/main/articles/app-service/deploy-azure-pipelines.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific deployment methods (Web Deploy) are described in detail, with explicit instructions to use Windows agents. Windows is often mentioned first in agent selection, and some examples (e.g., Web Deploy) are only available for Windows, with Linux alternatives not discussed. There is frequent reference to IIS and Windows-specific configuration (web.config, iisnode), while Linux deployment nuances are not covered. Linux agent options are mentioned, but parity in examples and troubleshooting is lacking.
Recommendations
  • Provide equivalent Linux/macOS deployment examples, especially for scenarios where only Windows/Web Deploy is shown.
  • Clarify limitations and alternatives for Linux/macOS users (e.g., suggest ZIP deploy or container-based deployment when Web Deploy is unavailable).
  • Balance agent selection instructions by listing Linux and Windows options together, or alternating order.
  • Add troubleshooting guidance for Linux/macOS agents, especially for errors that currently only mention Windows.
  • Include examples for deploying non-.NET applications (Node.js, Python, Java) on Linux agents, not just ASP.NET on Windows.
GitHub Create Pull Request
App Service Deploy From a Local Git Repository ...ocs/blob/main/articles/app-service/deploy-local-git.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell instructions, but PowerShell examples are given equal prominence and detail, and specific Windows tools (PowerShell, Git Credential Manager) are referenced. There are several places where Windows-centric terminology and tools are mentioned, and Linux/macOS equivalents (such as terminal types or credential managers) are not discussed. Some troubleshooting steps reference Windows-specific errors (e.g., native module binary distribution for Windows), and PowerShell is presented as a primary method for deployment, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, such as using Bash or zsh terminals.
  • Mention Linux/macOS credential managers or clarify that Git Credential Manager is cross-platform, or suggest alternatives.
  • When discussing errors, include Linux/macOS-specific troubleshooting notes (e.g., native module build issues on Linux).
  • Ensure that CLI examples are shown first or equally with PowerShell, and clarify which commands are platform-agnostic.
  • Avoid assuming PowerShell is available or preferred; note that it is Windows-specific and suggest Bash/zsh for Linux/macOS.
  • Where screenshots or UI references are given, clarify any platform differences.
GitHub Create Pull Request
App Service Deploy Files ...zure-docs/blob/main/articles/app-service/deploy-zip.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. The Kudu UI (Advanced Tools in the Azure portal) is described and illustrated, but explicitly does not work for App Service on Linux, with only a brief mention of alternatives. Windows paths and conventions are frequently referenced first, and the Kudu UI workflow is Windows-only. There is no equivalent Linux portal workflow or screenshots. PowerShell examples are provided, but PowerShell is not supported for several deployment types, and Linux-native tools (e.g., scp, rsync) are not mentioned. The documentation does provide CLI and cURL examples, which are cross-platform, but the initial workflow and some notes are Windows-centric.
Recommendations
  • Add explicit Linux/macOS portal workflow examples or screenshots, especially for tasks where the Kudu UI is not available.
  • Mention Linux-native tools (e.g., scp, rsync, SFTP) as alternatives for file deployment, where appropriate.
  • When describing default paths, list Linux paths first or side-by-side with Windows paths.
  • Where PowerShell is not supported, provide equivalent Bash or shell script examples.
  • Clarify which features are Windows-only and provide Linux alternatives or workarounds in the same section, not just as notes.
  • Consider adding a table summarizing feature parity between Windows and Linux App Service environments.
GitHub Create Pull Request
App Service Certificates in App Service Environment ...icles/app-service/environment/overview-certificates.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation demonstrates a notable Windows bias in the 'Private client certificate (per-app configuration)' section. This method is explicitly limited to Windows code apps, with no Linux equivalent or workaround provided. All example commands for certificate verification and generation use PowerShell, and the Kudu console instructions are Windows-specific. There are no Linux shell or cross-platform alternatives for these steps, and the documentation does not mention how Linux users could achieve similar functionality. While the recommended Root Certificate API is cross-platform, the alternative method and its examples are Windows-centric.
Recommendations
  • Clearly state Linux limitations earlier and more prominently in the relevant sections.
  • Provide Linux/macOS equivalents for certificate verification (e.g., using OpenSSL or Bash commands).
  • Offer guidance or workarounds for Linux users who need per-app certificate configuration, or clarify that this is not possible.
  • Include cross-platform examples for generating and exporting certificates, not just PowerShell.
  • Add links or references to Linux documentation for certificate management in App Service Environment.
GitHub Create Pull Request
App Service Set Up Staging Environments ...blob/main/articles/app-service/deploy-staging-slots.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell for all major operations, with PowerShell examples given equal prominence to CLI. However, there is a notable Windows bias: PowerShell is a Windows-centric tool, and its usage is emphasized throughout. Additionally, certain advanced configuration and troubleshooting steps (such as custom warm-up via Web.config and rewrite rules) are described using IIS/Windows-specific patterns, with no Linux or cross-platform equivalents or guidance. The documentation mentions that auto swap is not supported for web apps on Linux, but does not offer alternative solutions or workarounds for Linux users. There are no bash, shell script, or Linux-native tool examples, and Windows patterns (Web.config, IIS, PowerShell) are referenced without Linux parity.
Recommendations
  • Add explicit bash/shell script examples for common operations alongside PowerShell.
  • Clarify which features (such as auto swap) are unavailable on Linux, and suggest alternative deployment strategies for Linux users.
  • Provide Linux-specific guidance for custom warm-up (e.g., using startup scripts, app settings, or platform-agnostic approaches instead of Web.config/IIS).
  • When referencing troubleshooting steps or configuration files, include Linux equivalents (e.g., Nginx/Apache config, environment variables) where applicable.
  • Clearly indicate platform limitations and direct Linux/macOS users to relevant documentation or workarounds.
GitHub Create Pull Request
App Service Geo-Distributed Scale ...-service-app-service-environment-geo-distributed-scale.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exclusively provides Azure PowerShell examples for configuring Traffic Manager and App Service Environments, with no mention of equivalent Azure CLI or REST API commands. This creates a Windows-centric experience, as PowerShell is primarily associated with Windows environments, and Linux/macOS users are more likely to use Azure CLI. The instructions and code samples assume the use of PowerShell, and related links also focus on PowerShell tools. No Linux or cross-platform alternatives are presented, and PowerShell is introduced as 'the easiest way' without discussing other options.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for Traffic Manager profile and endpoint configuration.
  • Mention REST API and Azure Portal as alternative methods for users who do not use PowerShell.
  • Rephrase statements like 'The easiest way...' to be inclusive of CLI and Portal methods.
  • Include notes or sections specifically for Linux/macOS users, highlighting cross-platform tools.
  • Update related content links to include Azure CLI and REST API documentation.
GitHub Create Pull Request
← Previous Page 6 of 10 Next →