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 1301-1325 of 2121 flagged pages
App Service Use TLS/SSL Certificates in App Code ...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page presents Windows examples and concepts first, with detailed code samples for accessing certificates via the Windows certificate store in C# and Java. Linux-specific guidance is limited to a brief section with only C# examples for loading certificates from files, and other languages (Node.js, PHP, Python, Java) are referenced but not demonstrated. Windows tools and patterns (certificate store, thumbprint usage, environment variables) are emphasized throughout, while Linux equivalents are less prominent and lack parity in language coverage.
Recommendations
  • Provide code samples for Linux environments in languages other than C#, such as Node.js, PHP, Python, and Java.
  • Reorganize sections so that Linux and Windows guidance are presented with equal prominence, possibly using tabs or parallel subsections.
  • Expand explanations for Linux certificate handling, including common patterns and tools (e.g., OpenSSL, file permissions, environment variables).
  • Add explicit examples for accessing certificates in Linux containers using popular frameworks and languages.
  • Clarify when Windows-specific instructions are not applicable to Linux, and offer Linux alternatives where possible.
GitHub Create Pull Request
App Service Managed Identities ...main/articles/app-service/overview-managed-identity.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, ARM templates, and portal usage. While Azure CLI is cross-platform, PowerShell examples are prominent and often shown alongside or before CLI examples. In some sections (e.g., assigning user-assigned identities for Functions), PowerShell is the only option, and it is explicitly stated that PowerShell is not supported for App Service. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is referenced in code blocks and explanations, which may create friction for Linux/macOS users. The documentation does not reference Windows-specific tools, but the prominence of PowerShell and lack of Linux/macOS-specific guidance or troubleshooting constitutes a mild bias.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users where possible, especially for token retrieval and identity assignment.
  • Clarify that Azure CLI commands work equally well on Linux/macOS and Windows, and highlight cross-platform compatibility.
  • Where PowerShell is used, provide equivalent Bash or shell alternatives, or explicitly state when only PowerShell is supported.
  • Include troubleshooting or notes for Linux/macOS environments, especially when PowerShell is not supported.
  • Consider reordering examples so that Azure CLI (cross-platform) is shown before PowerShell.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally platform-neutral, but the 'Hybrid Connections' section exclusively mentions installing Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux/macOS support or alternatives. No PowerShell or Windows command examples are present, but the lack of Linux/macOS guidance for Hybrid Connections creates friction for non-Windows users.
Recommendations
  • Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide installation instructions or alternatives if so.
  • If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative approaches for Linux/macOS users.
  • Review other sections for any implicit Windows assumptions and ensure parity in examples and tool recommendations.
GitHub Create Pull Request
App Service Environment Variables and App Settings Reference ...ob/main/articles/app-service/reference-app-settings.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific paths, tools, and terminology (such as 'D:\home', 'w3wp.exe', IIS, Web Deploy/MSDeploy, and Windows-specific environment variables) are frequently mentioned, often before their Linux equivalents. Windows examples and settings are sometimes described first or in more detail, while Linux-specific information is less prominent or appears later. Some sections (e.g., build automation) default to Windows/Kudu and require switching tabs for Linux/Oryx. Windows tools and patterns (like Web Deploy, MSDeploy, and IIS logging) are referenced without always providing Linux alternatives or parity.
Recommendations
  • Ensure Linux-specific paths and variables (e.g., '/home') are mentioned alongside Windows paths, not just as parentheticals.
  • Where Windows tools (e.g., Web Deploy, MSDeploy, IIS) are referenced, provide equivalent Linux guidance or clarify if no equivalent exists.
  • Present Linux and Windows information equally in tables and descriptions, avoiding Windows-first ordering.
  • Expand Linux-specific examples and explanations, especially for build automation, logging, and deployment.
  • Clarify which settings are Windows-only and which are cross-platform, ideally with clear labeling or pivots.
  • Add more Linux/macOS-focused troubleshooting and usage notes where relevant.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally cross-platform and neutral, but the 'Hybrid Connections' section introduces Windows bias by requiring the Hybrid Connection Manager to be installed only on Windows Server 2012 or newer. There are no Linux/macOS equivalents or instructions provided, and no mention of alternative approaches for non-Windows environments. This creates friction for Linux/macOS users wishing to use Hybrid Connections.
Recommendations
  • Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide installation instructions or alternatives if possible.
  • If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative connectivity solutions for Linux/macOS users.
  • Where possible, provide Linux/macOS examples or parity for any tooling or configuration steps.
  • Review other sections for implicit Windows bias (e.g., screenshots, CLI instructions) and ensure cross-platform guidance is provided.
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-02-25 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page prioritizes Windows examples and tools, especially in the 'Load certificates in Windows apps' section, where only Windows certificate store access is shown in detail for C# and Java. Linux-specific guidance is limited to file-based certificate loading, with no code samples for non-C# languages (Node.js, PHP, Python, Java) on Linux. Windows certificate store and related tools are discussed before Linux equivalents, and Linux guidance is often deferred to external documentation.
Recommendations
  • Add explicit Linux code samples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from files in Azure App Service Linux environments.
  • Provide Linux-focused guidance earlier in the document, or in parallel with Windows instructions, to avoid Windows-first ordering.
  • Include examples of using Linux tools (such as OpenSSL or relevant libraries) for certificate management and loading.
  • Clarify when Windows-specific instructions are not applicable to Linux, and provide Linux alternatives where possible.
  • Expand the 'Load a certificate from a file' section to include Linux-specific nuances and security best practices.
GitHub Create Pull Request
App Service Back Up an App ...e-docs/blob/main/articles/app-service/manage-backup.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Azure Portal and Azure CLI instructions, which are cross-platform. However, there are several subtle Windows biases: (1) Windows directory paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are used as primary examples, with Linux equivalents only mentioned in passing; (2) The use of Kudu DebugConsole and FTP references Windows-style paths and tools; (3) The 'Automate with scripts' section mentions Azure PowerShell alongside Azure CLI, but does not provide Bash or Linux shell script samples or parity; (4) Windows terminology and patterns (e.g., slot names, directory structure) are presented first or exclusively in some sections.
Recommendations
  • Provide Linux-specific examples and directory paths (e.g., /home/site/wwwroot) alongside Windows paths wherever file operations are discussed.
  • Explicitly mention Linux/macOS methods for uploading files (e.g., SCP, SFTP, Linux FTP clients) in addition to Windows FTP.
  • Add Bash or Linux shell script samples in the 'Automate with scripts' section to complement Azure PowerShell.
  • When referencing environment variables or paths, show both Windows (%HOME%) and Linux ($HOME) conventions.
  • Clarify cross-platform compatibility of tools like Kudu DebugConsole and ensure screenshots/examples reflect both OS environments.
GitHub Create Pull Request
App Service Environment Variables and App Settings Reference ...ob/main/articles/app-service/reference-app-settings.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides environment variable references for Azure App Service across Windows and Linux, but exhibits Windows bias in several ways. Windows-specific tools (such as msbuild, Web Deploy/MSDeploy, IIS, and site extension feeds) are mentioned first or exclusively in many sections. Windows paths and conventions (e.g., D:\home, %HOME%) are often shown before Linux equivalents, and Windows-specific environment variables are more thoroughly documented. Linux build automation (Oryx) is referenced, but Windows build automation (Kudu) is described first and in more detail. Some examples and explanations default to Windows terminology, and Windows tools are referenced more frequently. However, Linux-specific settings and variables are present, and most critical features are documented for both platforms.
Recommendations
  • Ensure Linux and Windows examples are presented side-by-side or in parallel, rather than Windows-first.
  • Expand Linux-specific documentation, especially for build automation (Oryx), with equivalent detail to Windows/Kudu.
  • Where paths or environment variables differ, always show both Windows and Linux formats (e.g., D:\home vs /home).
  • Avoid referencing Windows tools (msbuild, IIS, Web Deploy) without mentioning Linux alternatives or clarifying platform applicability.
  • Add more Linux/macOS-specific troubleshooting and configuration guidance where relevant.
GitHub Create Pull Request
App Service Managed Identities ...main/articles/app-service/overview-managed-identity.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides instructions for enabling and managing managed identities in Azure App Service and Azure Functions. While it covers multiple platforms (Azure portal, Azure CLI, Azure PowerShell, ARM templates), PowerShell examples are given their own dedicated sections and are often more detailed. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. Additionally, PowerShell examples are sometimes shown before CLI equivalents, and there is no explicit mention of Bash or Linux-specific shell usage. The CLI examples are cross-platform, but the documentation does not clarify this or provide Linux/macOS-specific guidance. There are also no explicit Linux/macOS screenshots or notes about parity.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide explicit Bash shell examples where relevant.
  • Reduce the prominence of PowerShell by ensuring CLI examples are shown first or equally, and note that PowerShell is Windows-centric.
  • Add notes or sections for Linux/macOS users, including any differences in environment variables, shell usage, or authentication.
  • Consider including screenshots or instructions for Linux/macOS where portal steps differ.
  • Explicitly state platform parity for all code samples and tooling.
GitHub Create Pull Request
App Service Configure a Custom Container ...ain/articles/app-service/configure-custom-container.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance via zone pivots, but Windows-specific examples, tools, and explanations are often presented first or in greater detail. PowerShell commands are frequently included alongside Bash/Azure CLI, and Windows-specific concepts (such as IIS, .NET Framework, and C:\home directory) are described in depth. Some sections (e.g., customizing memory, CPU, health ping) show Windows-focused tables and PowerShell examples before Linux equivalents, even when the feature is cross-platform.
Recommendations
  • Ensure Linux examples and explanations are presented with equal prominence and detail as Windows, especially for cross-platform features.
  • Where possible, show Linux/Bash examples first or side-by-side with Windows/PowerShell to avoid implicit prioritization.
  • Expand Linux-specific guidance (e.g., persistent storage, environment variable injection, diagnostic log access) to match the depth of Windows sections.
  • Clarify when features or settings are Windows-only, and provide Linux alternatives or explicit notes when features differ.
  • Review and balance the use of PowerShell and Windows tools; ensure Linux tools (e.g., Bash, SSH, Docker Compose) are equally represented.
GitHub Create Pull Request
App Service Configure gateway-required virtual network integration for your app ...service/configure-gateway-required-vnet-integration.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is primarily focused on gateway-required virtual network integration, which is explicitly stated to be a Windows-only feature. However, troubleshooting and connectivity examples (such as Test-NetConnection and netstat -aon) are given using Windows/PowerShell commands, with no Linux/macOS equivalents or guidance. Windows tools and patterns are mentioned exclusively, and Linux users are told the feature is unavailable for their workloads, but no migration or alternative troubleshooting guidance is provided for Linux users.
Recommendations
  • Clearly state early in the document that gateway-required virtual network integration is Windows-only, and direct Linux users to regional virtual network integration or other supported alternatives.
  • Where troubleshooting steps are given (e.g., Test-NetConnection, netstat -aon), provide equivalent Linux/macOS commands (such as nc, curl, or netstat) for users working with regional virtual network integration or other scenarios.
  • Add a section summarizing Linux limitations and migration paths, linking to regional virtual network integration documentation.
  • Ensure that all example commands and tools are either cross-platform or alternatives are provided for Linux/macOS users.
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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed, step-by-step code examples for Windows apps and containers, including C# and Java code for accessing certificates via the Windows certificate store. Linux guidance is limited to brief C# file-loading examples, with no equivalent code samples for other languages (Node.js, PHP, Python, Java) on Linux. Windows-specific tools and patterns (certificate store, environment variables, .NET Framework) are emphasized and explained first, while Linux instructions are less comprehensive and often refer users to external language documentation.
Recommendations
  • Add explicit Linux code examples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from /var/ssl/certs and /var/ssl/private.
  • Provide more detailed guidance on Linux certificate handling, including file formats, permissions, and environment variable usage.
  • Balance the order of presentation so Linux and Windows examples are given equal prominence, possibly using tabs or parallel sections.
  • Clarify any differences in certificate management between Windows and Linux, including potential pitfalls or best practices.
  • Where possible, avoid referring Linux users to external documentation for basic tasks that are explained in detail for Windows.
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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for RBAC role assignment, but PowerShell is presented as a primary automation method in several places. Windows-specific tools (IIS, Certreq.exe) are referenced for certificate export, and the PowerShell example is given equal prominence to Azure CLI. The FAQ and automation sections list PowerShell before Linux-native alternatives. However, Linux tooling (OpenSSL) is also covered, and Azure CLI is included for most tasks, so Linux users are not blocked but may experience friction.
Recommendations
  • Ensure that Azure CLI examples are always presented before or alongside PowerShell, especially in automation sections.
  • Expand certificate export instructions for Linux/macOS users, including more detailed OpenSSL guidance and troubleshooting.
  • Add explicit notes or links for Linux/macOS users when referencing Windows-only tools (IIS, Certreq.exe), suggesting alternative workflows.
  • In FAQ and automation sections, list Azure CLI and Linux-native tools first, or provide parity in example ordering.
  • Clarify when a step is Windows-only and provide Linux/macOS alternatives where possible.
GitHub Create Pull Request
App Service Back Up an App ...e-docs/blob/main/articles/app-service/manage-backup.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Azure portal and Azure CLI instructions for backup and restore, which are cross-platform. However, there are several subtle Windows biases: Windows file paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are used in examples and explanations, and Kudu DebugConsole is referenced with Windows-style paths. FTP upload instructions and screenshots also use Windows paths. The mention of Azure PowerShell as a scripting option is present, but no Linux shell (bash) or macOS-specific scripting samples are referenced. Windows file system patterns and terminology are used before Linux equivalents, and Linux paths are only briefly mentioned in a table. Overall, Linux/macOS users can complete the tasks, but the documentation is somewhat Windows-centric.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/site/wwwroot) alongside Windows paths in all relevant sections.
  • Explicitly mention that Azure CLI works on Windows, Linux, and macOS, and provide bash shell scripting samples where PowerShell is referenced.
  • Add screenshots or instructions showing Linux/macOS directory structures and tools (e.g., using SCP or SFTP instead of FTP for uploading files).
  • When referencing Kudu DebugConsole, clarify that it is accessible from any OS and show both Windows and Linux path conventions.
  • In tables and explanations, list Linux/macOS information before or alongside Windows information to avoid 'windows_first' bias.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally platform-neutral, but the 'Hybrid Connections' section specifies that the relay agent (Hybrid Connection Manager) must be installed on Windows Server 2012 or newer. No Linux or macOS equivalent is mentioned, nor is it stated if Linux is unsupported or if alternatives exist. This creates friction for Linux users wishing to use Hybrid Connections.
Recommendations
  • Clarify whether Hybrid Connection Manager is available for Linux/macOS, or explicitly state if it is Windows-only.
  • If Linux/macOS support exists, provide installation instructions and examples for those platforms.
  • If Windows-only, suggest alternative approaches for Linux users (e.g., VPN, VNet Integration) and link to relevant documentation.
  • Review other sections for platform-specific tooling and ensure parity or clear guidance for Linux/macOS users.
GitHub Create Pull Request
App Service Environment Variables and App Settings Reference ...ob/main/articles/app-service/reference-app-settings.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service, supporting both Windows and Linux platforms. However, there is a notable Windows bias: Windows-specific paths (e.g., 'D:\home') and tools (e.g., msbuild, Web Deploy/MSDeploy, IIS, applicationHost.config) are mentioned frequently and often before their Linux equivalents. Windows-centric terminology and examples (such as referencing `%HOME%` and `.dll` extensions) appear throughout, while Linux-specific details are sometimes relegated to notes or parentheticals. Build automation and deployment sections prioritize Windows (Kudu) before Linux (Oryx), and Windows tools are described in greater detail. Some settings reference Windows behaviors or files without always providing Linux alternatives.
Recommendations
  • Ensure Linux examples and paths (e.g., '/home') are shown alongside Windows ones, not just in parentheticals.
  • Where Windows tools (e.g., msbuild, Web Deploy) are referenced, provide equivalent Linux tooling or clarify if not applicable.
  • Present Linux and Windows build automation sections in parallel or with equal prominence.
  • Add Linux/macOS-specific troubleshooting notes where only Windows errors are described.
  • Clarify when environment variables or settings are Windows-only, and provide Linux alternatives or explicitly state if not applicable.
GitHub Create Pull Request
App Service Configure a Custom Container ...ain/articles/app-service/configure-custom-container.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance using zone pivots, but Windows-specific examples, tools, and explanations are often presented first or in more detail. PowerShell commands are frequently shown alongside Bash, sometimes with Windows-specific explanations. Windows tools and patterns (such as IIS, .NET Framework, and Windows directory paths) are referenced more prominently, and some sections (like customizing memory and CPU) are Windows-only, with no Linux equivalent provided.
Recommendations
  • Ensure Linux examples and explanations are given equal prominence and detail as Windows, especially for advanced configuration topics.
  • Where PowerShell commands are shown, always provide Bash equivalents and clarify any OS-specific differences.
  • For sections that are Windows-only (e.g., memory and CPU customization), explicitly state Linux limitations or alternatives, or link to Linux-specific documentation.
  • Review the order of examples and explanations to avoid consistently presenting Windows first.
  • Expand Linux-specific troubleshooting and advanced configuration guidance to match Windows coverage.
GitHub Create Pull Request
App Service Configure gateway-required virtual network integration for your app ...service/configure-gateway-required-vnet-integration.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is focused on gateway-required virtual network integration, which is explicitly stated to only work for Windows plans. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command) are Windows-centric, and Linux/macOS equivalents are not provided. The use of Windows tools and terminology appears first and exclusively, creating friction for Linux/macOS users who may need to troubleshoot or test connectivity from VMs.
Recommendations
  • Clarify early and prominently that gateway-required virtual network integration is Windows-only, as already stated, to set expectations.
  • Where troubleshooting steps involve Windows-specific tools (e.g., PowerShell Test-NetConnection), provide Linux/macOS equivalents such as 'nc' (netcat), 'telnet', or 'curl' for TCP connectivity testing.
  • Add examples for Linux/macOS users in troubleshooting sections, especially for connectivity and DNS testing.
  • Mention that Linux App Service plans must use regional virtual network integration, and link to relevant documentation.
  • Consider reordering troubleshooting guidance to present cross-platform tools first or in parallel.
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-02-22 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 presents Windows-specific certificate loading patterns and code examples first, with detailed C# and Java samples for Windows certificate stores. Linux guidance is less prominent, often deferred to external language/platform documentation, and Linux code samples are limited to C#. There is a notable emphasis on Windows tools and stores, with Linux equivalents mentioned later or less thoroughly.
Recommendations
  • Provide Linux-specific code samples for popular languages (Node.js, Python, Java, PHP) directly in the documentation, not just C#.
  • Ensure Linux guidance is presented alongside Windows guidance, not only after or as an afterthought.
  • Add explicit instructions for accessing certificates in Linux App Service environments for each major language.
  • Include examples of using Linux environment variables for certificate paths in code samples.
  • Clarify when Windows-specific instructions are not applicable to Linux users, and offer Linux alternatives.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally cross-platform and neutral, but the 'Hybrid Connections' section introduces Windows bias by only mentioning installation of the Hybrid Connection Manager on Windows Server, with no mention of Linux support or alternatives. There are no explicit PowerShell-heavy examples or Windows-first ordering, but the omission of Linux guidance for Hybrid Connections is notable.
Recommendations
  • Clarify whether Hybrid Connection Manager is available for Linux hosts, and if so, provide installation instructions or links for Linux.
  • If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative approaches for Linux users.
  • Review other sections for tool references and ensure parity in examples and guidance for Linux/macOS where applicable.
GitHub Create Pull Request
App Service Environment Variables and App Settings Reference ...ob/main/articles/app-service/reference-app-settings.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service across platforms, but there is a consistent pattern of Windows-first presentation and more detailed coverage of Windows-specific variables and tools. Windows paths, tools (such as msbuild, Web Deploy/MSDeploy), and configuration files (like applicationHost.config, Web.config) are referenced more frequently and often before Linux equivalents. Some sections, such as Build Automation, provide more detailed explanations for Windows (Kudu) than for Linux (Oryx), and Windows-specific deployment and logging variables are described in greater detail. Linux and container-specific settings are present, but often after Windows, and sometimes with less context or explanation.
Recommendations
  • Ensure Linux and container examples are presented alongside Windows examples, not after.
  • Where Windows tools (e.g., msbuild, Web Deploy) are mentioned, provide Linux equivalents or clarify when none exist.
  • Balance the level of detail in descriptions for Linux (Oryx) and Windows (Kudu) build automation.
  • When referencing file paths or configuration files, provide both Windows and Linux paths in all examples.
  • Add more Linux/container-specific troubleshooting and usage notes where appropriate.
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-02-21 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 automating certificate operations, but PowerShell is mentioned equally or slightly more prominently. Windows-specific tools (IIS, Certreq.exe) are referenced for certificate export, and PowerShell is listed as a primary automation option. Linux tools (OpenSSL) are mentioned for certificate creation/export, but Windows tools are referenced first or equally, and some links point to Windows documentation. There is no section that is Windows-only, but Windows patterns and tooling are visible throughout.
Recommendations
  • Ensure Linux equivalents are always mentioned alongside Windows tools (e.g., for certificate export, link to OpenSSL documentation before or equally with Windows tools).
  • Provide Bash or shell script examples for automation, not just PowerShell and Azure CLI.
  • Clarify that Azure CLI works cross-platform and highlight its use for Linux/macOS users.
  • When referencing certificate export, include step-by-step OpenSSL instructions before Windows-specific tools.
  • Review FAQ and automation sections to ensure Linux/macOS parity in examples and links.
GitHub Create Pull Request
App Service Back Up an App ...e-docs/blob/main/articles/app-service/manage-backup.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page for Azure App Service backups is generally cross-platform, but there are several areas where Windows bias is evident. Windows directory paths (e.g., `%HOME%`, `D:\home\site\wwwroot`) are used as primary examples, and tools like Kudu DebugConsole and FTP are referenced with Windows-centric paths. PowerShell is mentioned alongside Azure CLI for automation, but Linux shell examples are not provided. The documentation often presents Windows patterns first, with Linux equivalents mentioned later or not at all.
Recommendations
  • Provide Linux/macOS directory path examples (e.g., `/home/site/wwwroot`) alongside Windows paths.
  • Clarify that tools like Kudu DebugConsole and FTP are available and usable from Linux/macOS environments, and provide relevant instructions.
  • Include bash or shell script samples for automation, not just Azure CLI and PowerShell.
  • When referencing environment variables or file paths, show both Windows and Linux formats.
  • Ensure screenshots and instructions in the portal are not Windows-centric unless the feature is Windows-only.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally cross-platform and focuses on Azure App Service networking features, which apply to both Windows and Linux hosted apps. However, the 'Hybrid Connections' section exclusively mentions installing the Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux support or alternatives. This creates friction for Linux users who may need to use Hybrid Connections but are not provided guidance or examples for their platform.
Recommendations
  • Clarify whether Hybrid Connection Manager is available for Linux, and provide installation instructions or alternatives for Linux hosts if supported.
  • Explicitly state platform limitations for features that are Windows-only, such as Gateway-required virtual network integration, to avoid confusion.
  • Where possible, provide Linux-specific examples or note parity for features that are cross-platform.
  • Add a note or link to documentation about Hybrid Connection Manager support for Linux, or explain why it is Windows-only if that is the case.
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-02-21 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific instructions and code samples (especially for certificate loading) are presented first and in greater detail, with C# and Java examples focused on the Windows certificate store. Linux guidance is present but less prominent, and non-Windows language examples (Node.js, PHP, Python, Java) are deferred to external documentation. Windows tools and patterns (certificate store, environment variables, user profile loading) are emphasized, while Linux equivalents are less thoroughly explained.
Recommendations
  • Provide Linux examples alongside Windows examples in each relevant section, not just in container-specific tabs.
  • Include code samples for loading certificates in popular languages (Node.js, Python, Java, PHP) on both Windows and Linux, rather than referring users to external documentation.
  • Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or use tabbed content for all major OSes.
  • Clarify any differences in certificate handling between Windows and Linux up front, and provide guidance for cross-platform scenarios.
  • Expand on Linux-specific environment variables and best practices, similar to the detail given for Windows.
GitHub Create Pull Request
← Previous Page 53 of 85 Next →