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 1276-1300 of 2121 flagged pages
App Service Install a TLS/SSL Certificate for Your App ...main/articles/app-service/configure-ssl-certificate.md
Medium Priority View Details →
Scanned: 2026-03-04 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 managing Key Vault permissions, but PowerShell is given equal or slightly more prominence in some sections. There are references to Windows-specific tools (IIS, Certreq.exe) for exporting certificates, and links to Windows Server documentation for certificate export. In the automation FAQ, both Azure CLI and PowerShell are mentioned, but PowerShell is listed second. There are no Linux-specific certificate management examples (e.g., OpenSSL is mentioned, but not with Linux-specific context), and Windows tools are referenced for certificate export.
Recommendations
  • Add explicit Linux/macOS examples for certificate export and management, especially for common tasks like exporting to .pfx (e.g., using OpenSSL on Linux/macOS).
  • When referencing Windows tools (IIS, Certreq.exe), provide equivalent Linux/macOS instructions or links.
  • In automation sections, ensure Azure CLI examples are shown first, as it is cross-platform, and clarify when PowerShell is Windows-only.
  • Where possible, provide bash scripts or command-line examples for Linux/macOS users.
  • Review links to ensure they do not point only to Windows Server documentation when cross-platform alternatives exist.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-03-04 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 describes Azure App Service networking features without explicit Windows bias. However, the 'Hybrid Connections' section requires installing Hybrid Connection Manager on a Windows Server 2012 or newer host, with no mention of Linux/macOS support or alternatives. This omission creates friction for Linux users who may need to use Hybrid Connections but cannot install the required agent on their preferred OS.
Recommendations
  • Clarify whether Hybrid Connection Manager is available for Linux/macOS hosts. If not, explicitly state the Windows-only requirement and suggest alternative approaches for Linux users.
  • If possible, provide or link to Linux/macOS-compatible relay agents or tools for Hybrid Connections.
  • For all examples and tool references, ensure parity by mentioning Linux/macOS equivalents or limitations where relevant.
GitHub Create Pull Request
App Service Managed Identities ...main/articles/app-service/overview-managed-identity.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, ARM templates, and the Azure portal. While Azure CLI and ARM templates are cross-platform, PowerShell examples are prominent and sometimes shown before CLI examples. In some sections, PowerShell is used for both CLI and PowerShell tabs (e.g., 'az identity create' is labeled as 'azurepowershell-interactive'), which may confuse Linux/macOS users. Additionally, PowerShell is given its own code tab for token retrieval, but there is no equivalent Bash or shell script example. The documentation does not mention Windows-specific tools, but the ordering and prominence of PowerShell can create friction for non-Windows users.
Recommendations
  • Ensure that Azure CLI examples are always shown before PowerShell examples, as CLI is more cross-platform.
  • Add Bash or shell script examples for token retrieval from the REST endpoint, especially in the 'Connect to Azure services in app code' section.
  • Clarify labeling in code blocks to distinguish between Azure CLI and PowerShell, avoiding confusion (e.g., do not use 'azurepowershell-interactive' for Azure CLI commands).
  • Consider adding explicit notes or examples for Linux/macOS users where PowerShell is not supported or less common.
  • Where possible, provide parity in scripting examples (e.g., Bash, Python) alongside PowerShell.
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-03-04 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 covers environment variables and app settings for Azure App Service across both Windows and Linux platforms. However, there is a notable Windows bias: Windows-specific paths, tools (such as Web Deploy/MSDeploy, IIS, and site extensions), and examples are often mentioned first or exclusively, with Linux equivalents sometimes missing or appearing later. Some settings and explanations reference Windows conventions (e.g., `D:\home`, `%HOME%`, `.dll` extensions, Windows-specific build automation with Kudu) before Linux paths or tools. In several sections, Windows-centric terminology and features (such as site extensions, msbuild, and IIS logging) are prioritized or lack Linux parity in explanation or examples.
Recommendations
  • Ensure Linux paths and conventions (e.g., `/home`, `/tmp`) are mentioned alongside Windows paths in all relevant settings.
  • Provide Linux-specific examples and explanations for deployment, build automation, logging, and language runtimes where only Windows tools or patterns are described.
  • Clarify which settings are Windows-only and which are cross-platform, ideally with clear labeling or tabbed sections.
  • Add Linux equivalents for Windows tools (e.g., Web Deploy/MSDeploy) or explicitly state when no equivalent exists.
  • Review all examples and ensure Linux/macOS users can follow them without ambiguity or missing information.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-03-03 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 a Windows Server 2012 or newer host, with no mention of Linux support or alternatives. This creates friction for Linux users who may wish to use Hybrid Connections. No PowerShell or Windows-first examples are present, but the omission of Linux guidance for Hybrid Connection Manager is a notable gap.
Recommendations
  • Clarify whether Hybrid Connection Manager supports Linux hosts, and if so, provide installation and usage instructions for Linux.
  • If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest Linux-compatible alternatives for outbound connectivity.
  • Review other sections for tool-specific guidance and ensure parity for Linux/macOS users where possible.
  • Add a note or table summarizing platform support for each networking feature, especially where Windows-only tools are required.
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-03-03 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 approaches (such as using the Windows certificate store and C#/.NET examples) are presented first and in greater detail, with full code samples for both C# and Java on Windows. Linux guidance is present but less comprehensive: Linux-specific code examples are only provided for C#, and for other languages (Node.js, PHP, Python, Java), Linux users are told to consult external documentation. There is also a reliance on Windows concepts (certificate store, thumbprints) and tools, with Linux equivalents mentioned later or less prominently.
Recommendations
  • Provide Linux-specific code samples for popular languages (Node.js, Python, Java, PHP), not just C#.
  • Present Windows and Linux approaches in parallel sections or tabs, rather than Windows-first.
  • Expand explanations of Linux certificate handling, including how to use environment variables and file paths in various languages.
  • Clarify any differences in certificate formats or handling between Windows and Linux.
  • Where possible, avoid assuming familiarity with Windows certificate stores or tools when discussing cross-platform scenarios.
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-03-03 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 tools (such as Kudu, MSDeploy, Web Deploy) are mentioned first and in more detail, and Windows-related environment variables and paths (e.g., D:\home, %HOME%) are often shown before or instead of Linux equivalents. Several sections (e.g., Build Automation, Logging, Caching) default to Windows terminology and examples, with Linux information sometimes appearing as an afterthought or in separate tabs. Some settings are described only for Windows, even when Linux equivalents exist.
Recommendations
  • Ensure Linux and macOS examples and paths are shown alongside Windows examples, not just as secondary notes.
  • Where Windows tools (e.g., Kudu, MSDeploy) are discussed, provide equivalent Linux tooling or clarify Linux alternatives (e.g., Oryx, ZIP deploy).
  • Use platform-neutral terminology where possible, or clearly indicate when a setting is Windows-only.
  • For each environment variable, specify applicability (Windows, Linux, or both) in the main table, not just in descriptions.
  • Add Linux/macOS-specific troubleshooting and configuration guidance where relevant.
  • Review ordering of sections and examples to avoid always presenting Windows first.
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-03-02 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 covered in detail with C# and Java examples, while Linux guidance is limited to C# file loading and lacks parity for other languages. Windows tools and patterns (certificate store, thumbprint access) are emphasized first and more thoroughly. Linux examples for Node.js, PHP, Python, and Java are missing, and users are referred to external documentation. Windows-specific environment variables and certificate store details are prominent, while Linux guidance is less comprehensive.
Recommendations
  • Add Linux-specific code examples for Node.js, PHP, Python, and Java, showing how to load certificates from file paths.
  • Present Linux and Windows guidance in parallel sections, rather than Windows-first.
  • Expand Linux container documentation to include environment variable usage and certificate loading patterns for multiple languages.
  • Clarify differences between Windows and Linux certificate handling earlier in the article.
  • Provide links or snippets for Linux language documentation where external guidance is referenced.
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-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation generally provides cross-platform guidance for managing TLS/SSL certificates in Azure App Service, with a strong focus on Azure Portal and Azure CLI. However, there are several instances where Windows tools (IIS, Certreq.exe) are referenced for certificate export, and PowerShell examples are given alongside Azure CLI. In some cases, Windows tools are mentioned before Linux alternatives, and PowerShell is presented as a primary automation option. While Linux users can complete all tasks (notably with OpenSSL and Azure CLI), the documentation could better highlight Linux/macOS parity and alternatives.
Recommendations
  • When referencing certificate export tools, mention Linux/macOS alternatives (such as OpenSSL) before or alongside Windows tools like IIS or Certreq.exe.
  • Ensure all automation examples (e.g., for RBAC/Key Vault permissions) provide Azure CLI as the primary or first option, with PowerShell as an alternative.
  • Wherever PowerShell is shown, explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit notes or callouts for Linux/macOS users in sections that reference Windows-specific tools.
  • Consider adding a table or section summarizing certificate generation/export steps for both Windows and Linux/macOS environments.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-03-02 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 are available for 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. There are no PowerShell-heavy examples or Windows-first ordering, but the omission of Linux instructions for Hybrid Connections creates friction for Linux users.
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 alternatives for Linux users.
  • Review other sections to ensure any tool or feature that has platform-specific requirements is clearly documented for both Windows and Linux.
  • Where possible, provide parity in examples and instructions for both Windows and Linux 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-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally covers both Windows and Linux App Service environments, but there is a consistent pattern of mentioning Windows paths, tools, and behaviors first or exclusively in some sections. Several environment variable descriptions provide Windows-centric examples (e.g., paths like D:\home), reference Windows tools (like msbuild, Web Deploy/MSDeploy, applicationHost.config), and sometimes omit equivalent Linux examples or details. However, Linux is also covered in most sections, and there are Linux-specific variables and notes. The bias is moderate: Linux users can complete tasks, but may experience friction due to Windows-first presentation and lack of parity in some explanations.
Recommendations
  • When providing path examples, always show both Windows and Linux equivalents (e.g., D:\home and /home).
  • For variables or features that behave differently on Windows and Linux, clearly document both behaviors and provide examples for each.
  • Avoid referencing Windows tools (e.g., msbuild, Web Deploy) without mentioning Linux alternatives or clarifying their applicability.
  • In tables and lists, alternate or parallelize Windows and Linux information rather than consistently listing Windows first.
  • Where features are Windows-only, explicitly state this to avoid confusion.
  • Expand Linux-specific sections (e.g., Oryx build automation) to match the detail level of Windows (Kudu) sections.
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-03-01 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, the troubleshooting section and connectivity testing examples use PowerShell commands (e.g., Test-NetConnection) and Windows tools (netstat -aon) without providing Linux/macOS equivalents. The examples and guidance are Windows-centric, and Linux users are not provided with alternative commands or approaches for equivalent tasks.
Recommendations
  • Add Linux/macOS equivalent commands for network troubleshooting, such as using 'nc' (netcat), 'ss', or 'telnet' for TCP connectivity testing, and 'lsof' or 'netstat' for port/process mapping.
  • Explicitly state that the troubleshooting steps are Windows-specific and provide parallel instructions for Linux users where applicable.
  • Where PowerShell is used, offer Bash or shell alternatives for Linux/macOS environments.
  • Clarify that gateway-required integration is Windows-only, but troubleshooting and network diagnostics may be relevant for Linux users in related scenarios.
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-03-01 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 operations, but PowerShell is presented as a primary scripting option alongside CLI. Windows tools such as IIS and Certreq.exe are referenced for certificate export, with only a brief mention of OpenSSL for Linux/macOS users. Windows-specific tools are mentioned before Linux equivalents, and the PowerShell example is given equal prominence to Azure CLI, which may create friction for Linux/macOS users. However, most steps are portal-based and platform-agnostic, and OpenSSL is referenced for certificate creation/export.
Recommendations
  • Expand Linux/macOS guidance for certificate export, including step-by-step OpenSSL instructions for common scenarios.
  • Provide Bash shell scripting examples for automation alongside PowerShell.
  • Mention OpenSSL and Linux/macOS tools before or alongside Windows tools such as IIS and Certreq.exe.
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Add links to Linux/macOS-specific certificate management documentation 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-03-01 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 provides detailed, step-by-step examples for accessing certificates in Windows apps (including C# and Java code for Windows certificate store), but gives only minimal guidance for Linux apps and containers. Linux examples are limited to C# file loading, and other languages (Node.js, PHP, Python, Java) are referenced only generically, with no concrete code samples. Windows-specific tools and patterns (certificate store, environment variables, user profile loading) are described in depth, while Linux equivalents are not explained or demonstrated. Windows content appears first and is more comprehensive.
Recommendations
  • Add concrete code examples for loading certificates in Linux containers and apps for popular languages (Node.js, Python, Java, PHP), not just C#.
  • Provide step-by-step instructions for accessing certificates in Linux environments, including how to use environment variables and file paths.
  • Ensure Linux guidance is as detailed as Windows guidance, including troubleshooting and best practices.
  • Consider presenting Linux and Windows sections in parallel or tabs, rather than Windows-first.
  • Clarify any differences in certificate handling between Windows and Linux, and provide guidance for cross-platform scenarios.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-03-01 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 introduces Windows bias by requiring the installation of Hybrid Connection Manager only on Windows Server hosts, with no mention of Linux support or alternatives. No Linux-specific examples or guidance are provided for this feature, which may create friction for Linux users wishing to use Hybrid Connections.
Recommendations
  • Clarify whether Hybrid Connection Manager is available for Linux or 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 (such as VPN, ExpressRoute, or other outbound connectivity features).
  • Where possible, provide Linux/macOS equivalents or examples for any tooling or configuration steps.
  • Review other sections for opportunities to add Linux-specific guidance, especially for outbound connectivity scenarios.
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-03-01 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 provides extensive coverage of both Windows and Linux environment variables and app settings for Azure App Service. However, there are several instances where Windows-specific details, paths, and tools are mentioned first or exclusively, and Linux equivalents are only mentioned later or in less detail. Some examples and references (such as file paths, time zones, and logging) default to Windows conventions, and certain features/tools (e.g., Web Deploy/MSDeploy, Kudu) are described with a Windows-centric perspective. There are also a few cases where Linux examples or tools are missing or less emphasized.
Recommendations
  • Ensure that all examples (such as file paths, environment variable values, and configuration snippets) are provided for both Windows and Linux, or clearly indicate when a setting is platform-specific.
  • When describing features or tools that have both Windows and Linux implementations (e.g., deployment engines, logging paths), provide Linux information with equal prominence and detail.
  • Avoid defaulting to Windows-first language (e.g., 'D:\home' before '/home'), or alternate the order to avoid implicit prioritization.
  • Where Windows-only tools are mentioned (e.g., MSDeploy, Web Deploy), explicitly state their Linux equivalents or clarify if no equivalent exists.
  • Add more Linux-specific troubleshooting tips and usage notes where applicable.
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-28 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 RBAC assignment, but PowerShell is given equal prominence and is referenced in automation FAQs. Windows tools (IIS, Certreq.exe) are mentioned for certificate export, with only a brief reference to OpenSSL for Linux/macOS users. Windows-specific tooling is mentioned first or equally, and links to Windows documentation are provided for certificate export. There is no explicit Linux/macOS example for exporting certificates from non-Windows sources, and PowerShell is referenced in automation guidance.
Recommendations
  • Add explicit Linux/macOS guidance for certificate export, such as detailed OpenSSL instructions, and clarify the process for users who do not use IIS or Certreq.exe.
  • Provide Linux/macOS-specific automation examples (e.g., Bash scripts) alongside PowerShell, especially in the FAQ section.
  • When referencing tools, list cross-platform options first or equally, and avoid linking only to Windows documentation for certificate export.
  • Clarify that Azure CLI is cross-platform and encourage its use for automation when 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-28 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 in several places, but there are notable Windows-centric patterns. Windows file paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are used as defaults, and Windows tools like PowerShell are mentioned alongside Azure CLI. The Kudu DebugConsole example is Windows-oriented, and FTP upload instructions reference Windows paths. Linux equivalents are mentioned but often after Windows, and Linux-specific instructions are less detailed.
Recommendations
  • Provide Linux/macOS-specific file path examples (e.g., /home/site/wwwroot) alongside Windows paths wherever file operations are described.
  • Ensure parity in tool recommendations: mention Bash and Linux-native scripting alongside PowerShell, and provide sample scripts for both.
  • Clarify that Kudu DebugConsole and FTP can be used from any OS, and show Linux/macOS screenshots or terminal commands where appropriate.
  • Where environment variables are referenced, show both Windows (%HOME%) and Linux ($HOME) conventions.
  • In sections describing file uploads or directory navigation, include Linux/macOS instructions and paths.
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-28 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 covers both Windows and Linux environment variables for Azure App Service, but there is a notable Windows-first and Windows-tools bias. Windows paths, tools, and concepts (such as D:\home, Web Deploy/MSDeploy, IIS, and .bat files) are mentioned first or exclusively in many places, and examples often use Windows syntax. Linux equivalents are sometimes mentioned, but often as an afterthought or in a secondary position. Some sections, like build automation, are split into Windows (Kudu) and Linux (Oryx) tabs, but the Windows tab appears first. There are also variables and explanations that reference Windows-only features without always clarifying Linux alternatives. In some cases, Linux-specific examples or explanations are missing or less detailed.
Recommendations
  • Ensure that for every Windows-specific example, an equivalent Linux/macOS example is provided, with equal detail and prominence.
  • When referencing file paths, always show both Windows and Linux paths (e.g., D:\home and /home) together.
  • Avoid using Windows tools (e.g., .bat files, MSDeploy) as the default or only example; mention Linux tools and workflows with equal weight.
  • Where tabs are used for Windows and Linux, consider making Linux the first tab or randomize the order to avoid implicit prioritization.
  • Add explicit notes when a feature or variable is Windows-only, and provide Linux alternatives or workarounds where possible.
  • Audit the documentation for variables or features that are only described in Windows terms (e.g., IIS, applicationHost.config) and clarify their applicability or alternatives for Linux.
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-28 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 (e.g., Test-NetConnection PowerShell command, netstat usage) are Windows-centric, and Linux/macOS equivalents are not provided. Windows tools and patterns are mentioned first and exclusively in command examples, creating friction for Linux/macOS users who may need to perform similar troubleshooting tasks.
Recommendations
  • Clearly state early in the document that gateway-required virtual network integration is Windows-only, and highlight alternatives for Linux apps (such as regional virtual network integration).
  • Where troubleshooting steps involve Windows tools (e.g., Test-NetConnection, netstat -aon), provide Linux/macOS equivalents (e.g., nc, curl, netstat, ss) or mention that these steps are for Windows VMs and suggest alternatives for Linux VMs.
  • Add explicit guidance or links for Linux users on how to test connectivity and debug networking issues in Azure environments.
  • Ensure that any portal instructions or UI references clarify if they are Windows-specific or applicable to all platforms.
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-28 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 provides detailed, step-by-step code examples for accessing certificates in Windows apps and Windows containers, including C# and Java code for the Windows certificate store. Linux examples are limited to C# file-based loading and lack parity for other languages (Node.js, PHP, Python, Java). Windows-specific tools and patterns (certificate store, environment variables, user profile settings) are described in depth, while Linux guidance is brief and often refers users to external language/platform documentation.
Recommendations
  • Add Linux-specific code examples for Node.js, PHP, Python, and Java, showing how to load certificates from the injected file paths.
  • Provide more detailed guidance on Linux certificate handling, including environment variable usage and best practices for certificate file permissions.
  • Ensure that Linux instructions and examples are presented alongside Windows examples, rather than referring users to external documentation.
  • Clarify any differences in certificate handling between Windows and Linux containers, especially for popular frameworks and languages.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-02-28 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 the relay agent (Hybrid Connection Manager) on Windows Server 2012 or newer, with no mention of Linux/macOS support or alternatives. There are no PowerShell-heavy examples or Windows-first ordering, but the lack of Linux guidance for Hybrid Connections is a notable gap.
Recommendations
  • Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide installation instructions or alternatives if so.
  • If Hybrid Connections is Windows-only, explicitly state this limitation to inform Linux users.
  • Where possible, provide Linux/macOS equivalents or note feature parity for tools and agents.
  • Review other sections for potential platform-specific instructions and ensure parity in examples and guidance.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-02-27 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 requires installing Hybrid Connection Manager on Windows Server, with no mention of Linux/macOS support or alternatives. This creates friction for Linux users wishing to use Hybrid Connections. No PowerShell-heavy or Windows-first ordering is observed elsewhere, and most features are described generically.
Recommendations
  • Clarify whether Hybrid Connection Manager supports Linux/macOS, and provide installation instructions or alternatives if available.
  • If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative outbound connectivity methods for Linux-hosted apps.
  • Review other sections for potential OS-specific tool mentions and ensure parity in examples and guidance.
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-27 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 patterns first, especially for certificate loading in app code. Windows certificate store usage is explained in detail, with C# and Java code samples for Windows, while Linux examples are limited to C# file-based loading. Other languages (Node.js, PHP, Python, Java) are mentioned only as 'see external docs,' with no Linux-specific code samples. Windows tools and concepts (certificate store, thumbprint, environment variables) are emphasized, and Linux parity is lacking in practical examples and guidance.
Recommendations
  • Add Linux-specific code samples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from file paths in Linux containers.
  • Provide more detailed guidance for Linux users, including how to handle certificate permissions, file formats, and environment variables.
  • Present Linux and Windows approaches side-by-side, or use tabs to avoid Windows-first bias.
  • Clarify differences in certificate handling between Windows and Linux, especially for non-.NET workloads.
  • Link to or create documentation for Linux-specific certificate management in App Service.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page provides backup and restore guidance for Azure App Service apps. While it covers both Windows and Linux app scenarios, there are several areas where Windows patterns, terminology, and tooling are prioritized or presented first. Examples and instructions often reference Windows paths (e.g., `%HOME%`, `D:\home\site\wwwroot`), Windows-centric tools (Kudu DebugConsole, FTP), and PowerShell samples are mentioned alongside Azure CLI. Linux equivalents are sometimes present but less emphasized, and Windows-specific terminology appears first in explanations.
Recommendations
  • Provide Linux/macOS-specific examples and paths (e.g., `/home/site/wwwroot`) alongside Windows paths in all relevant sections.
  • Clarify that Kudu DebugConsole and FTP are cross-platform, or offer alternatives for Linux users (such as SSH or SCP where applicable).
  • Ensure that Azure CLI instructions are equally emphasized for Linux/macOS users, and avoid presenting PowerShell as the primary scripting option.
  • Where file paths or environment variables are referenced, show both Windows and Linux formats.
  • Review screenshots and UI references to ensure they are not Windows-only unless the feature is exclusive to Windows.
  • Explicitly state when instructions apply to both Windows and Linux apps, and highlight any OS-specific differences.
GitHub Create Pull Request
← Previous Page 52 of 85 Next →