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 1326-1350 of 2121 flagged pages
App Service Environment Variables and App Settings Reference ...ob/main/articles/app-service/reference-app-settings.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 covers environment variables and app settings for Azure App Service, supporting both Windows and Linux platforms. However, there are several instances where Windows-specific paths, tools, and terminology are presented first or exclusively. Windows paths (e.g., D:\home) are often shown before Linux equivalents, and Windows-specific tools like Web Deploy/MSDeploy and IIS are referenced without always providing Linux alternatives. Some sections (such as Kudu build automation) focus heavily on Windows, with Linux (Oryx) relegated to a separate tab. Examples and explanations frequently default to Windows conventions, creating friction for Linux/macOS users.
Recommendations
  • Ensure all environment variable descriptions provide both Windows and Linux path examples, with Linux shown equally or first where appropriate.
  • Where Windows tools (e.g., Web Deploy/MSDeploy, IIS, site extensions) are mentioned, explicitly note Linux alternatives or limitations.
  • For build automation, provide equal detail for Oryx (Linux) as for Kudu (Windows), including environment variables and usage examples.
  • Avoid defaulting to Windows terminology (e.g., %HOME%, D:\home) in general explanations; use platform-neutral language or show Linux equivalents alongside.
  • Add Linux/macOS-specific troubleshooting tips and examples where Windows-specific guidance is given.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-02-20 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 does not focus on Windows-specific features. However, the 'Hybrid Connections' section exclusively mentions installing the Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux/macOS support or alternatives. This omission may create friction for Linux users who wish to use Hybrid Connections.
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 users.
  • Where possible, provide parity or guidance for Linux/macOS users in sections that reference tools or agents.
  • Review other sections for implicit Windows assumptions and ensure Linux/macOS users are not excluded from critical workflows.
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-20 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 PowerShell examples for certificate-related tasks, but PowerShell is mentioned prominently and sometimes before CLI. Windows-specific tools (IIS, Certreq.exe) are referenced for certificate export, and links to Windows documentation are provided. Linux tools (OpenSSL) are included, but Windows methods are described in detail and referenced first in some sections. The FAQ and automation sections list PowerShell before CLI, and Windows export methods are given more prominence.
Recommendations
  • Ensure Linux/CLI examples are always provided alongside PowerShell, and shown first where possible.
  • Expand instructions for Linux/macOS users, including OpenSSL usage and troubleshooting.
  • Add links to Linux/macOS certificate export documentation, not just Windows.
  • Clarify when Windows tools are optional, and provide parity for Linux/macOS users.
  • In automation/FAQ sections, list CLI and Linux-native methods before PowerShell/Windows tools.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a comprehensive reference for environment variables and app settings in Azure App Service, covering both Windows and Linux platforms. However, there is evidence of Windows bias: Windows-specific paths (e.g., D:\home) and tools (e.g., msbuild, Web Deploy/MSDeploy, IIS, site extensions) are often mentioned first or exclusively. Windows terminology and examples (such as referencing Windows time zones, Windows-specific logging, and legacy Windows deployment tools) appear before Linux equivalents, even in sections that apply to both platforms. Some settings and explanations are more detailed for Windows, while Linux-specific guidance is less prominent or deferred to external links (e.g., Oryx configuration).
Recommendations
  • Ensure Linux examples and paths (e.g., /home) are presented alongside Windows ones, not only as afterthoughts.
  • When describing settings, clarify applicability for Windows, Linux, and containers, and provide parity in explanations and examples.
  • Add Linux-specific deployment and build automation examples (e.g., Oryx usage, Linux container paths, relevant shell commands).
  • Avoid referencing Windows tools (e.g., msbuild, Web Deploy) without also mentioning Linux alternatives or noting their platform specificity.
  • Where Windows terminology is used (e.g., time zones, logging paths), provide equivalent Linux information or links.
  • Consider restructuring sections so that Linux and Windows are treated equally, or use clear pivots/tabs for each platform.
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-20 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 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 for the Windows certificate store. Linux guidance is present but less detailed, and non-Windows language/platform examples (Node.js, PHP, Python, Java) are deferred to external documentation. The use of Windows certificate store and related APIs is emphasized, while Linux users are directed to file-based approaches with less explanation.
Recommendations
  • Provide Linux-specific code samples (not just C#) for common languages supported on App Service, such as Node.js, Python, Java, and PHP, showing how to load certificates from the injected file paths.
  • Present Linux and Windows instructions/examples in parallel or with equal prominence, rather than Windows-first.
  • Expand the Linux section to explain best practices for certificate handling, including environment variable usage for certificate paths.
  • Include explicit examples for loading certificates in Java on Linux, as well as for other popular stacks.
  • Clarify any differences in certificate formats or permissions between Windows and Linux containers.
  • Where external documentation is referenced, provide direct links to relevant sections for each language/platform.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides examples and instructions for both Windows and Linux platforms, but there are several areas where Windows patterns, terminology, and tools are presented first or exclusively. For instance, file paths and directory references use Windows-style paths (e.g., `%HOME%`, `D:\home\site\wwwroot`), and the use of Kudu DebugConsole is described with Windows-centric paths. The 'Automate with scripts' section references Azure PowerShell alongside Azure CLI, but does not provide parity for Linux shell scripting. Additionally, FTP upload instructions and screenshots are Windows-oriented. Linux equivalents are mentioned but often after Windows, and some instructions (such as file upload locations) are not clearly mapped for Linux users.
Recommendations
  • Provide Linux-specific examples and file paths (e.g., `/home/site/wwwroot`) alongside Windows paths wherever file operations are described.
  • Clarify how to access Kudu DebugConsole and upload files for Linux-based App Service apps, including screenshots or instructions for Linux environments.
  • Ensure that CLI and scripting examples are not biased toward PowerShell; include Bash shell script examples for Linux users.
  • When referencing environment variables or directories, note the Linux equivalents and differences explicitly.
  • Where screenshots or instructions are Windows-centric, add Linux/macOS alternatives or clarify any differences.
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-19 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 for Azure App Service, which is explicitly stated to only work for Windows plans. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command, netstat -aon) are Windows-centric, and Linux/macOS equivalents are not provided. The use of Windows tools and commands without Linux alternatives creates friction for cross-platform users, especially those troubleshooting from Linux VMs or environments.
Recommendations
  • Clarify early that the feature is Windows-only for App Service, but troubleshooting steps may apply to cross-platform scenarios (e.g., VMs in the virtual network).
  • Provide Linux/macOS equivalents for troubleshooting commands, such as using 'nc' (netcat), 'telnet', or 'ss' for TCP connectivity, and 'lsof' or 'netstat' for port listening.
  • When referencing PowerShell commands, add a note or example for Linux users (e.g., 'On Linux, use nc hostname port' or 'ss -ltn').
  • Ensure that any guidance for VM-level troubleshooting is platform-neutral or includes both Windows and Linux/macOS instructions.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-02-19 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 section on Hybrid Connections requires installation of Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux/macOS support or alternatives. This creates friction for Linux users who may need to access on-premises resources via Hybrid Connections. No PowerShell-heavy or Windows-first ordering is observed, but the lack of Linux guidance for Hybrid Connections is notable.
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 Linux-friendly alternatives for outbound connectivity (such as VPN, ExpressRoute, or other Azure features).
  • Where tools or features are Windows-specific, add a note about platform limitations and link to relevant Linux/macOS documentation or guidance.
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-19 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 provides a comprehensive reference for environment variables and app settings in Azure App Service, covering both Windows and Linux platforms. However, there are several instances where Windows-specific tools, paths, and terminology are mentioned first or exclusively, such as referencing Windows directory paths (e.g., D:\home), IIS, Web Deploy/MSDeploy, and site extension feeds. Some settings and examples use Windows conventions (e.g., `%HOME%`, `.dll` extensions, references to `applicationHost.config`) before or instead of Linux equivalents. While Linux-specific variables and sections are present (e.g., Oryx build automation, Linux container settings), Windows terminology and examples often appear first or are more detailed, and some Linux-specific settings lack equivalent examples or explanations.
Recommendations
  • Ensure Linux paths and conventions (e.g., `/home`, `/etc`) are mentioned alongside Windows paths wherever relevant.
  • Provide Linux-specific examples and explanations for settings that currently only reference Windows tools or patterns (e.g., Web Deploy, site extensions, logging paths).
  • Balance the order of presentation so that Linux and Windows are treated equally, rather than Windows-first.
  • Clarify when a setting is Windows-only or Linux-only, and provide parity where possible.
  • Expand Linux build automation and deployment examples to match the detail provided for Windows/Kudu.
  • Avoid referencing Windows tools (e.g., IIS, MSDeploy) in general sections unless explicitly noting their platform specificity.
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-19 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-specific certificate loading methods and code examples first, with detailed instructions for accessing certificates via the Windows certificate store in C# and Java. Linux guidance is limited to brief C# file-loading examples, and other languages (Node.js, PHP, Python, Java) are referenced only generically, without concrete Linux examples. Windows tools and patterns (certificate store, thumbprint usage, environment variables) are emphasized throughout, while Linux equivalents are less detailed and appear later in the document.
Recommendations
  • Provide concrete Linux examples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from the file paths provided.
  • Include Linux-specific guidance earlier in the document, alongside Windows instructions, to improve parity.
  • Expand on Linux container certificate handling, including sample code for accessing certificates via environment variables.
  • Clarify differences in certificate management between Windows and Linux, and offer troubleshooting tips for Linux users.
  • Balance the order of presentation so Linux and Windows instructions are equally prominent.
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-19 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 permissions, but PowerShell is presented as a primary automation option alongside CLI. In the certificate export section, Windows-specific tools (IIS and Certreq.exe) are mentioned for generating/exporting certificates, with only a brief reference to OpenSSL for Linux/macOS users. Windows tools and patterns are referenced before Linux equivalents, and links to Windows documentation are provided for certificate export. There are no Linux/macOS-specific walkthroughs or screenshots, and PowerShell is given equal prominence to CLI for automation, despite CLI being more cross-platform.
Recommendations
  • Add explicit Linux/macOS instructions and examples for certificate generation and export, including OpenSSL commands and troubleshooting.
  • Provide links to Linux/macOS documentation for certificate management, not just Windows Server docs.
  • Present Azure CLI as the primary automation method, with PowerShell as an alternative for Windows users.
  • Include Linux/macOS screenshots or clarify that the portal experience is identical across platforms.
  • Mention cross-platform tools (like OpenSSL) before Windows-specific tools in relevant sections.
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-18 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: Windows file paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are used throughout, and Kudu DebugConsole is referenced with Windows-style paths. FTP upload instructions and screenshots reference Windows directories. The 'Automate with scripts' section lists Azure PowerShell samples before CLI samples, and PowerShell is mentioned as a scripting option, which is more Windows-centric. Linux-specific paths (/home) are mentioned but always after Windows equivalents. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of Linux tools for file upload (such as SCP or SFTP).
Recommendations
  • Include Linux/macOS file path examples alongside Windows paths (e.g., /home/site/wwwroot).
  • Show both Windows and Linux environment variable usage (e.g., $HOME vs %HOME%).
  • Provide Bash shell examples for CLI usage and file uploads (e.g., using SCP/SFTP).
  • Clarify that Kudu DebugConsole and FTP are accessible from any OS, and show Linux/macOS usage.
  • List Azure CLI samples before PowerShell samples, or present them together.
  • Add screenshots or instructions for Linux/macOS users where relevant.
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-18 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 examples and concepts (certificate store, C#/.NET code, Windows-MY store, Windows containers) are presented first and in greater detail, with Linux equivalents appearing later or being referenced less directly. Non-Windows languages (Node.js, PHP, Python, Java) are not given explicit code examples, and Linux-specific instructions are sometimes deferred to external documentation. Windows-specific tools and patterns (certificate store, environment variables, user profile loading) are discussed in depth, while Linux guidance is more generic and less comprehensive.
Recommendations
  • Provide explicit code examples for Linux environments and popular languages (Node.js, Python, PHP, Java) for loading certificates, rather than referring users to external documentation.
  • Present Linux and Windows instructions side-by-side or in parallel tabs to ensure parity and reduce friction for Linux users.
  • Expand Linux container guidance to match the detail given for Windows containers, including environment variable usage and file path handling.
  • Clarify when instructions are Windows-specific and offer Linux alternatives where possible.
  • Add more detailed explanations for Linux certificate handling, including common pitfalls and best practices.
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-18 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 is prevalent, and Linux users are excluded from actionable steps, even in troubleshooting sections.
Recommendations
  • Clearly state early in the document that gateway-required virtual network integration is Windows-only, and provide guidance for Linux users to use regional virtual network integration.
  • Where troubleshooting steps are given (e.g., Test-NetConnection), offer Linux/macOS equivalents (such as 'nc', 'telnet', or 'curl' commands) for users who may be troubleshooting from a Linux VM.
  • Add explicit links or sections for Linux users, directing them to supported alternatives and migration paths.
  • Ensure that any example commands or tools are accompanied by cross-platform alternatives where relevant, especially in sections not strictly limited by Windows-only features.
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-18 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 PowerShell examples for automating certificate management, but PowerShell is mentioned prominently and linked alongside CLI. Windows tools such as IIS and Certreq.exe are referenced for certificate export, with only brief mention of OpenSSL for Linux/macOS users. Windows-specific tooling is mentioned before Linux alternatives, and links to Windows documentation are provided for certificate export. However, Linux-compatible instructions (OpenSSL) are present, and the overall guidance is not Windows-exclusive.
Recommendations
  • Ensure Linux/macOS equivalents are always provided alongside Windows tools (e.g., for certificate export, link to OpenSSL documentation and provide step-by-step OpenSSL instructions before or alongside Windows tools).
  • When listing automation options, mention Azure CLI first, as it is cross-platform, and clarify that PowerShell is Windows-centric.
  • Add explicit notes or sections for Linux/macOS users where Windows tools (IIS, Certreq.exe) are referenced, including alternative methods.
  • Provide links to Linux/macOS certificate management documentation and tools.
  • Review screenshots and UI instructions to ensure they are not Windows-specific unless the feature is Windows-only.
GitHub Create Pull Request
App Service Managed Identities ...main/articles/app-service/overview-managed-identity.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parity across Azure Portal, Azure CLI, Azure PowerShell, and ARM template methods for managing identities. However, PowerShell examples are present throughout, and in some sections (such as 'Add a user-assigned identity'), PowerShell is given its own tab even when Azure CLI is more cross-platform. Additionally, PowerShell is referenced in CLI sections (e.g., 'azurepowershell-interactive' code block for az CLI), and PowerShell is listed as a language example for token retrieval, while Bash or Linux shell equivalents are missing. Azure CLI is present, but PowerShell is sometimes mentioned first or more prominently.
Recommendations
  • Ensure that Azure CLI examples use proper shell syntax and are labeled as 'bash' or 'shell' where appropriate, not 'azurepowershell-interactive'.
  • Add Bash/Linux shell examples for token retrieval from the REST endpoint, alongside PowerShell.
  • Where PowerShell is given its own tab, ensure that Bash or Linux shell equivalents are also provided, especially for scripting scenarios.
  • Review the order of examples and tabs to ensure Azure CLI (cross-platform) is listed before PowerShell (Windows-centric) where possible.
  • Clarify that Azure CLI is fully supported on Linux/macOS and highlight any limitations or differences if present.
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-18 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 both Windows and Linux platforms. However, there is a noticeable Windows bias: Windows-specific examples (such as directory paths like `D:\home`), tools (Kudu, Web Deploy/MSDeploy), and terminology (IIS, applicationHost.config) are often mentioned first or exclusively. Some settings and explanations default to Windows conventions, with Linux alternatives appearing later or in less detail. Several environment variables and features are described primarily in the context of Windows, with Linux equivalents sometimes missing or less emphasized.
Recommendations
  • Ensure Linux examples (e.g., `/home` paths, Linux deployment tools) are presented alongside Windows examples, not just as secondary notes.
  • Where Windows tools (e.g., Web Deploy/MSDeploy, Kudu) are discussed, provide clear Linux alternatives (e.g., Oryx, ZIP deploy, FTP, Git) and link to relevant Linux documentation.
  • When describing environment variables, show both Windows and Linux values/formats in tables and explanations.
  • Avoid defaulting to Windows terminology (e.g., 'applicationHost.config', 'D:\home') without also referencing Linux equivalents.
  • Add Linux/macOS-specific troubleshooting tips and configuration notes where Windows-specific guidance is given.
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-17 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 C# and Java code for accessing certificates via the Windows certificate store. Linux guidance is limited, mostly referencing file-based access and deferring language-specific examples to external documentation. Windows-specific tools and patterns (certificate store, environment variables, .NET Framework) are emphasized, while Linux and non-Windows language examples are sparse or missing.
Recommendations
  • Provide code examples for loading certificates in popular Linux-hosted languages (Node.js, Python, PHP, Java) directly in the documentation, not just C#.
  • Present Linux and Windows guidance in parallel sections or tabs, rather than Windows-first.
  • Expand Linux-specific instructions beyond file paths, including sample code for common certificate operations.
  • Clarify any differences in certificate handling between Windows and Linux containers, including environment variable usage.
  • Add explicit guidance for macOS scenarios if relevant.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides some Windows-specific guidance and examples, such as referencing IIS and Certreq.exe for certificate export, and links to a Windows Server 2008 guide for exporting certificates. PowerShell and Azure CLI are both presented for RBAC, but in the FAQ and automation sections, PowerShell is mentioned before CLI. There are no explicit Linux/macOS certificate export instructions or references to Linux tools (other than OpenSSL), and the Windows export path is more detailed. This may create friction for Linux/macOS users, especially those unfamiliar with Windows certificate tooling.
Recommendations
  • Add explicit Linux/macOS instructions for exporting certificates (e.g., using OpenSSL for .pfx export when the certificate was generated on Linux).
  • When referencing certificate export, provide parity between Windows (IIS/Certreq.exe) and Linux/macOS (OpenSSL) methods, with links to relevant documentation for both.
  • In automation and FAQ sections, list Azure CLI and PowerShell examples in parallel or in a neutral order, or clarify that both are supported equally.
  • Where possible, avoid linking only to Windows-specific documentation for common tasks (e.g., exporting .pfx files), and include cross-platform alternatives.
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-17 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', 'applicationHost.config', IIS, and Web Deploy/MSDeploy) are frequently mentioned first or exclusively, while Linux equivalents are sometimes missing or only referenced later. Some sections (e.g., build automation, logging, caching) provide more detail for Windows scenarios and tools, with Linux alternatives referenced but not always explained equally. Examples and explanations often default to Windows conventions, even when Linux is supported.
Recommendations
  • Where Windows paths or tools are mentioned (e.g., 'D:\home', 'applicationHost.config', IIS, Web Deploy/MSDeploy'), add equivalent Linux paths or tools (e.g., '/home', Nginx/Apache, Oryx build, ZIP deploy) and explain differences.
  • Ensure Linux-specific environment variables and behaviors are documented with equal detail and clarity as Windows.
  • When listing environment variables, avoid defaulting to Windows-first order; consider grouping by OS or providing parallel tables/examples for Windows and Linux.
  • Add explicit Linux/macOS examples where only Windows examples are given (e.g., for deployment, logging, caching, build automation).
  • Clarify which settings are Windows-only and which are cross-platform, to reduce confusion for Linux 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-16 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 provides detailed, step-by-step code examples for Windows environments (Windows certificate store, C#, Java), but Linux examples are limited to C# file loading and lack parity for other languages. Windows-specific tools and patterns (certificate store, environment variables, .NET Framework) are emphasized, and Windows instructions are generally given before Linux equivalents. References to Linux for Node.js, PHP, Python, and Java are deferred to external documentation, creating friction for Linux users.
Recommendations
  • Add code examples for loading certificates in Linux environments for Node.js, PHP, Python, and Java directly in the documentation.
  • Present Windows and Linux instructions side-by-side or in parallel tabs to avoid Windows-first ordering.
  • Include more details about Linux-specific certificate handling, such as permissions, file formats, and common pitfalls.
  • Clarify when a feature or example is Windows-only, and provide Linux alternatives where possible.
  • Expand on the use of environment variables for certificate paths in Linux containers, with practical code samples.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is for 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, netstat -aon) are Windows-centric, and Linux/macOS equivalents are not provided. Windows tools and patterns are mentioned first or exclusively, creating friction for cross-platform users who may need to troubleshoot from Linux VMs or environments.
Recommendations
  • Clarify early in the document that gateway-required virtual network integration is Windows-only, and that troubleshooting steps are primarily for Windows environments.
  • Where troubleshooting steps involve Windows tools (e.g., PowerShell Test-NetConnection, netstat -aon), provide Linux/macOS equivalents (e.g., nc, curl, ss, netstat, telnet) for users working with Linux VMs or hybrid environments.
  • Add explicit notes or sections for Linux users, even if the integration feature itself is Windows-only, since network troubleshooting may occur from Linux hosts.
  • Ensure that examples for connectivity testing and network diagnostics are cross-platform where possible, or clearly indicate if a step is Windows-specific.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a comprehensive reference for environment variables and app settings in Azure App Service, covering both Windows and Linux environments. 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 often mentioned first or exclusively, with Linux equivalents sometimes missing or appearing later. Some sections (such as build automation) default to Windows/Kudu explanations before Linux/Oryx, and Windows-specific configuration details are more verbose. Examples and explanations frequently use Windows conventions, and Windows tools are referenced without always providing Linux alternatives.
Recommendations
  • Ensure Linux examples and paths (e.g., /home) are shown alongside Windows ones, not just as parentheticals.
  • When referencing Windows tools (e.g., msbuild, Web Deploy), provide Linux alternatives or clarify their applicability.
  • Balance explanations for build automation: present Oryx (Linux) and Kudu (Windows) equally, and avoid defaulting to Windows-first.
  • Where possible, provide Linux-specific troubleshooting and configuration guidance, not just Windows.
  • Review sections for Windows-centric terminology (e.g., applicationHost.config, IIS) and clarify scope/applicability.
  • Add explicit notes or tables indicating which settings are Windows-only, Linux-only, or cross-platform.
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-15 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 certificate store access is explained in detail with C# and Java examples, while Linux is only referenced later and with less detail. Windows tools and patterns (certificate store, thumbprint access, environment variables) are described first and most thoroughly. Linux examples are limited to C# file loading, and other languages (Node.js, PHP, Python, Java) are not shown for Linux, with users referred to external documentation. Windows-specific instructions and terminology dominate the initial sections.
Recommendations
  • Provide explicit Linux examples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from the file paths provided.
  • Reorganize sections so Linux and Windows approaches are presented in parallel, rather than Windows first.
  • Expand Linux guidance to include common certificate handling patterns and troubleshooting tips.
  • Clarify which instructions are Windows-only and which are cross-platform.
  • Add sample code for accessing certificates in Linux containers for languages other than C#.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Feature Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is for a feature (gateway-required virtual network integration) that is explicitly Windows-only. This is stated up front, and Linux apps are not supported. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command, netstat -aon) are Windows-centric, with no equivalent Linux/macOS commands or guidance provided. The use of Windows tools and PowerShell is exclusive, and Linux users are not given alternative instructions, even for general networking troubleshooting.
Recommendations
  • Add explicit statements clarifying that gateway-required virtual network integration is Windows-only, and direct Linux users to regional virtual network integration.
  • Where troubleshooting steps are generic (e.g., testing TCP connectivity, checking listening ports), provide Linux/macOS equivalents such as 'nc', 'ss', or 'netstat' commands.
  • For PowerShell examples, add Bash/Linux command alternatives where applicable, even if only for VM troubleshooting.
  • Link to regional virtual network integration documentation for Linux users throughout the page.
GitHub Create Pull Request
← Previous Page 54 of 85 Next →