App Service

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

Bias Trend Over Time

Pages with Bias Issues

247 issues found
Showing 26-50 of 247 flagged pages
App Service Supported platforms and file types ...includes/webjobs-create/webjobs-supported-platforms.md
High Priority View Details →
Scanned: 2026-01-10 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 lists Windows hosting options and file types before Linux equivalents, and gives more detailed mention to Windows-specific tools (executables, batch files, PowerShell scripts) before mentioning Bash and other scripting languages. There are no explicit Linux-specific examples or tools highlighted, and PowerShell is called out separately, reinforcing a Windows-centric perspective.
Recommendations
  • List Linux hosting options and file types before or alongside Windows equivalents to avoid ordering bias.
  • Explicitly mention Linux-specific tools or patterns, such as shell scripts, cron jobs, or systemd services, where relevant.
  • Provide Linux-specific examples (e.g., sample Bash script usage or integration patterns) to match the detail given for Windows tools.
  • Include a note clarifying cross-platform support and parity, emphasizing that both Windows and Linux are first-class citizens.
  • Consider grouping file/script types by platform or presenting them in a parallel structure to highlight equal support.
GitHub Create Pull Request
App Service Migrate Docker Compose to sidecars ...es/app-service/migrate-sidecar-multi-container-apps.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by requiring PowerShell for both the prerequisites and migration script, providing only PowerShell examples for critical steps (such as base64 decoding), and referencing Windows-centric tools and workflows before any Linux alternatives. There are no Bash or Linux shell examples, and the migration script is only available as a PowerShell script (.ps1), which excludes native Linux users. The documentation does not mention or provide parity for Linux shell usage, nor does it offer alternative scripts or commands for non-Windows environments.
Recommendations
  • Provide Bash or Linux shell equivalents for all PowerShell commands, especially for base64 decoding and other scripting steps.
  • Offer a migration script in Bash (.sh) or cross-platform scripting language (e.g., Python), or document how to run the PowerShell script on Linux using PowerShell Core.
  • List prerequisites for both Windows and Linux environments, including installation instructions for PowerShell Core on Linux if required.
  • Ensure examples are given for both Windows and Linux users, or present Linux examples first to avoid implicit Windows prioritization.
  • Explicitly mention Linux compatibility and provide troubleshooting tips for Linux users where workflows differ.
GitHub Create Pull Request
App Service Managed Identities ...main/articles/app-service/overview-managed-identity.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently as a primary automation tool, with detailed examples and instructions for both App Service and Functions. There are no explicit Linux shell (bash) or cross-platform scripting examples outside of Azure CLI, and PowerShell is presented as a first-class option, which is more commonly used on Windows. Additionally, some instructions (e.g., for creating user-assigned identities in Functions) are only available for PowerShell, and the lack of bash or Linux-native scripting alternatives may hinder Linux users. The documentation does not mention or recommend Linux-specific tools or patterns, and PowerShell examples are given equal or greater prominence than Azure CLI.
Recommendations
  • Add bash shell scripting examples alongside PowerShell for all automation steps, especially for token retrieval and identity management.
  • Explicitly state cross-platform compatibility for Azure CLI and ARM template examples, and clarify that these tools work equally well on Linux and macOS.
  • Where PowerShell is used, provide equivalent bash or shell script snippets to ensure Linux users have clear guidance.
  • Mention Linux-native tools (such as curl, jq) for REST endpoint interactions and token retrieval, and provide sample commands.
  • Review and update any instructions that are PowerShell-only to include Linux-compatible alternatives, or note platform limitations where applicable.
GitHub Create Pull Request
App Service Migration Checklist - Azure App Service on Arc-enabled Kubernetes to Azure Container Apps on Arc-enabled Kubernetes ...b/main/articles/app-service/migrate-app-service-arc.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for resource queries, but PowerShell is given equal prominence to CLI, which is more cross-platform. There are no Linux-specific shell examples (e.g., Bash), and no mention of Linux-native tools or patterns. The documentation does not reference Windows tools directly, but the inclusion of PowerShell examples (which are most commonly used on Windows) and the lack of Linux shell examples indicate a subtle Windows bias.
Recommendations
  • Add Bash shell examples for all CLI commands to demonstrate usage on Linux and macOS.
  • Clarify that Azure CLI commands work cross-platform and provide explicit instructions for Linux users where relevant.
  • Consider removing or de-emphasizing PowerShell examples unless there is a specific Windows-only scenario.
  • Include notes or sections addressing Linux-specific considerations, such as permissions, environment setup, or troubleshooting.
  • Ensure that any references to tools or patterns are balanced between Windows and Linux environments.
GitHub Create Pull Request
App Service Managed Instance on App Service overview (preview) ...main/articles/app-service/overview-managed-instance.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows-specific features and tooling, such as PowerShell scripts, registry modifications, COM components, MSI installers, IIS Manager, and RDP access. All configuration and operational examples reference Windows tools and patterns, with no Linux equivalents or parity. The platform is described as Windows-only, and Linux/container support is explicitly excluded. Windows terminology and tools are mentioned first and exclusively throughout the page.
Recommendations
  • Add explicit Linux support or roadmap information if planned, including equivalent configuration and operational patterns.
  • Provide Linux/bash script examples alongside PowerShell for configuration tasks, where applicable.
  • Reference Linux-native tools (e.g., SSH, systemd, cron, Linux package managers) in relevant sections.
  • Clarify which features are Windows-only and suggest Linux alternatives or workarounds for users needing cross-platform solutions.
  • Include a comparison table of Windows vs. Linux capabilities for Managed Instance and App Service, highlighting gaps and parity.
  • If Linux support is not planned, make this limitation prominent at the top of the documentation.
GitHub Create Pull Request
App Service Create an App by Using a Terraform Template ...n/articles/app-service/provision-resource-terraform.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias in several areas: Windows and PowerShell configuration options are listed before Linux equivalents in the prerequisites, and Windows-specific tools (PowerShell, Visual Studio Code extension) are highlighted. While both Linux and Windows Terraform templates are provided, the initial orientation and tooling recommendations lean toward Windows environments. There is also a lack of parity in mentioning Linux-native editors or shell environments outside Cloud Shell Bash.
Recommendations
  • List Linux and Windows configuration options in parallel or alternate order to avoid Windows-first impression.
  • Include explicit instructions and examples for Linux desktop environments (e.g., Ubuntu, Fedora) outside of Azure Cloud Shell.
  • Mention Linux-native editors (e.g., Vim, Nano, Emacs) alongside Visual Studio Code for authoring Terraform files.
  • Highlight Bash and other Linux shells equally with PowerShell in all relevant sections.
  • Ensure that any tooling recommendations (such as VS Code extensions) clarify cross-platform compatibility and suggest alternatives where appropriate.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-managed-certificate-changes-july-2025.md ...e/app-service-managed-certificate-changes-july-2025.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a PowerShell script as the only automated method for identifying impacted Traffic Manager profiles, with no equivalent Bash, Azure CLI, or Linux-native example. All step-by-step instructions for resource identification are Windows/PowerShell-centric, and there is no mention of cross-platform alternatives. This creates a bias toward Windows users and may hinder Linux or macOS administrators.
Recommendations
  • Provide equivalent Azure CLI or Bash scripts for identifying impacted Traffic Manager profiles, ensuring Linux and macOS users have a supported method.
  • When referencing scripts or tools, mention both PowerShell and CLI/Bash options, or explicitly state platform compatibility.
  • Include examples or guidance for running the detection and mitigation steps on Linux-based systems.
  • Consider adding a table or section summarizing available tools/scripts for both Windows (PowerShell) and Linux/macOS (Bash/CLI), with links to each.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-discover-net.md ...cles/app-service/app-service-migration-discover-net.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation focuses exclusively on discovering ASP.NET web apps hosted on IIS within VMware environments, referencing only Windows-based tools and patterns. There is no mention of Linux-based web servers (such as Apache or Nginx), nor are there examples or guidance for discovering .NET apps hosted on Linux. The content and related links reinforce a Windows-first perspective.
Recommendations
  • Include guidance and examples for discovering .NET web apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel).
  • Mention whether Azure Migrate supports Linux-based .NET app discovery, and if not, clarify this limitation.
  • Add parity in documentation by providing Linux-specific instructions, tools, and troubleshooting steps.
  • List Linux environments and discovery capabilities alongside Windows/IIS to ensure cross-platform inclusivity.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-undelete.md ...blob/main/articles/app-service/app-service-undelete.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong bias towards Windows environments by exclusively providing PowerShell-based examples and instructions for restoring deleted Azure App Service apps. There are no examples or guidance for users of Linux or macOS, such as using Azure CLI, Bash, or REST API. The only non-PowerShell method mentioned is the Azure portal, but all automation and scripting is PowerShell-centric. This may alienate or hinder users who primarily use Linux or cross-platform tools.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for all PowerShell cmdlets shown, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include REST API examples or references for advanced users who may wish to automate app restoration without PowerShell.
  • When listing command-line options, present Azure CLI and PowerShell examples side-by-side, or at least mention both, to avoid the perception of Windows-first bias.
  • Explicitly state that PowerShell examples can be run cross-platform using Azure PowerShell Core, or provide Bash scripting alternatives where possible.
  • Review and update the documentation to ensure that Linux and macOS users have clear, supported pathways for performing all documented tasks.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-dotnet-sqldatabase.md ...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased toward Windows and Visual Studio users. All instructions and screenshots are based on Visual Studio for Windows, with no mention of Linux or cross-platform development tools. Steps for publishing, configuring, and managing the app and database rely on Visual Studio GUI and Windows-specific tools (e.g., SQL Server Object Explorer, Package Manager Console, PowerShell). There are no examples or instructions for Linux users or those using cross-platform tools like VS Code, Azure CLI, or the Azure Portal directly.
Recommendations
  • Add parallel instructions for Linux and macOS users, including how to perform each step using cross-platform tools such as VS Code, Azure CLI, and the Azure Portal.
  • Provide command-line examples (e.g., using Azure CLI, dotnet CLI, or Bash) for app deployment, database creation, and configuration, in addition to Visual Studio GUI steps.
  • Include screenshots and workflow descriptions for non-Windows environments.
  • Mention and link to Linux-compatible tools and workflows early in the tutorial, not just as an afterthought.
  • Clarify which steps are Windows-specific and provide alternatives for other platforms where possible.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-customize-sign-in-out.md ...vice/configure-authentication-customize-sign-in-out.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation contains a Windows bias in the 'Authorize or deny users' section, where server-level authorization is described exclusively for Windows apps using IIS and web.config, without providing equivalent Linux guidance. The Kudu console and web.config editing are presented as the main approach, with no mention of Linux alternatives or parity. Other sections use cross-platform Azure CLI examples and avoid OS-specific instructions.
Recommendations
  • Add a section describing how to implement server-level authorization for Linux-based App Service apps, such as using middleware in popular frameworks (e.g., Node.js, Python, .NET Core) or configuring authorization in the application code.
  • Explicitly state that server-level authorization via web.config is not available on Linux, and provide links or examples for common Linux-based approaches.
  • Ensure that for every Windows/IIS-specific example, an equivalent Linux/app-level example is provided, or at least referenced.
  • Review the order of presentation to avoid 'Windows first' bias—consider presenting cross-platform or Linux approaches alongside Windows ones.
  • Mention any built-in features or best practices for authorization on Linux App Service (e.g., using .htaccess for PHP, or app-level authorization for other stacks).
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/app-service-app-service-environment-geo-distributed-scale.md ...-service-app-service-environment-geo-distributed-scale.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples for configuring Traffic Manager and App Service Environments. There are no equivalent examples using Azure CLI, Bash scripts, or ARM templates, which are commonly used on Linux and cross-platform environments. The only automation tooling mentioned is PowerShell, and the narrative assumes its use without referencing alternatives. This may hinder accessibility for Linux or macOS users and those who prefer cross-platform tools.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, ensuring Linux and macOS users can follow along without needing PowerShell.
  • Mention and link to ARM/Bicep template documentation for users who prefer declarative infrastructure-as-code approaches.
  • When introducing automation tooling, mention Azure CLI and ARM templates alongside PowerShell, rather than only referencing PowerShell.
  • Include screenshots or terminal output from Bash or cross-platform shells where relevant.
  • Review the language to avoid assuming PowerShell as the default tool; use more inclusive phrasing such as 'using Azure PowerShell or Azure CLI...'
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/webjobs-create/webjob-types.md ...es/app-service/includes/webjobs-create/webjob-types.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation presents Windows examples and tools (cmd, bat, exe, PowerShell) in detail and lists them first, while Linux sections are less detailed, only mentioning .sh scripts and providing fewer examples. Windows-specific tools and file types are emphasized, and Linux equivalents (e.g., .sh, .py, .js) are not given the same breadth or specificity.
Recommendations
  • Provide Linux examples with the same level of detail as Windows, including supported file types for Bash, Python, Node.js, and Java.
  • List Linux and Windows sections in parallel structure, ensuring neither is prioritized in order or detail.
  • Explicitly mention Linux tools and runtimes (e.g., bash, python, node, java) and their supported file types, similar to how Windows tools are listed.
  • Include examples for Linux containers that match the variety shown for Windows containers (e.g., .py, .jar, .war).
  • Consider a summary table comparing supported file types across both platforms for clarity and parity.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-basic-auth-disable.md ...n/articles/app-service/configure-basic-auth-disable.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It references and prioritizes Windows-centric tools and workflows such as Web Deploy (a Windows-only tool), Visual Studio, and FTP, which are more commonly used in Windows environments. The fallback and troubleshooting sections mention Windows agents specifically and provide more detail for Windows scenarios. There is a lack of explicit Linux or cross-platform examples, and no mention of Linux-native deployment tools or command-line patterns outside of the Azure CLI. Powershell is implied via references to the Azure portal and Windows agents, but not directly shown. Linux deployment agents and workflows are not covered in detail, and there are no Linux-specific troubleshooting steps or parity checks.
Recommendations
  • Add explicit Linux examples and troubleshooting steps, especially for deployment agents and self-hosted runners.
  • Mention Linux-native tools and workflows (e.g., SCP, SFTP, rsync, or Linux-based CI/CD runners) where relevant.
  • Clarify which deployment methods and tools are cross-platform and which are Windows-only.
  • Provide parity in troubleshooting guidance for Linux agents (e.g., what to do if authentication fails on a Linux agent).
  • Include Bash or shell script examples for common tasks, not just Azure CLI.
  • When referencing Visual Studio or Web Deploy, also mention cross-platform alternatives (e.g., VS Code, Git, or other CI/CD tools).
  • Review and balance the order of presentation so that Windows and Linux options are given equal prominence.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-custom-container.md ...ain/articles/app-service/configure-custom-container.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific instructions, tools, and examples (such as PowerShell and Windows paths) are often presented first or exclusively, with Linux equivalents sometimes missing or less detailed. Some sections, especially those about persistent storage, memory, and CPU configuration, provide more context and examples for Windows users, while Linux instructions are less prominent or absent. PowerShell commands are frequently included alongside Bash, but not always with parity in Linux-specific guidance. Windows tools and patterns (e.g., Kudu, IIS, .NET Framework) are referenced more extensively.
Recommendations
  • Ensure all configuration examples (e.g., for persistent storage, memory, CPU, environment variables) provide both Bash (Linux) and PowerShell (Windows) commands with equal prominence.
  • When introducing concepts or features, avoid presenting Windows-specific details first; instead, use neutral or parallel explanations for both platforms.
  • Expand Linux-specific sections to match the depth and clarity of Windows sections, including troubleshooting, logs access, and advanced configuration.
  • Where Windows tools (e.g., Kudu, IIS) are mentioned, provide Linux alternatives or clarify their applicability to Linux containers.
  • Review for sections where only Windows parent images, paths, or frameworks are discussed, and add corresponding Linux examples (e.g., base images, file paths, frameworks).
  • Audit for any missing Linux examples, especially in advanced scenarios (e.g., custom entrypoints, SSH, persistent storage), and add them where needed.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/webjobs-create/webjobs-supported-platforms.md ...includes/webjobs-create/webjobs-supported-platforms.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation lists Windows hosting options before Linux and prioritizes Windows file/script types (.exe, .cmd, .bat) and PowerShell scripts (.ps1) ahead of Bash (.sh) and other cross-platform scripting languages. This ordering and emphasis suggest a Windows-centric perspective, with Windows tools and patterns mentioned first and in more detail.
Recommendations
  • List Linux hosting options and script types before or alongside Windows equivalents to avoid implicit prioritization.
  • Provide equal detail and examples for Linux tools (e.g., Bash, shell scripts) and mention them as prominently as Windows tools.
  • Include explicit examples for both Windows and Linux platforms to demonstrate parity.
  • Avoid grouping Windows-specific file types together at the top of lists; interleave with Linux equivalents.
  • Add notes or sections highlighting Linux-specific considerations, best practices, or troubleshooting tips.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-sidecar-multi-container-apps.md ...es/app-service/migrate-sidecar-multi-container-apps.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exhibits a Windows bias by requiring PowerShell for the migration script, only providing PowerShell commands for scripting and base64 decoding, and not offering equivalent Bash/Linux shell examples. The script-based migration is only supported via a PowerShell script, and Linux alternatives are not mentioned. Additionally, PowerShell is listed as a prerequisite before Azure CLI, and Windows tooling is assumed throughout.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell commands, especially for base64 decoding and script execution.
  • Offer a Bash or cross-platform version of the migration script, or document how to run the PowerShell script on Linux (e.g., with pwsh).
  • List prerequisites in a cross-platform neutral order, and clarify that Azure CLI and Docker are cross-platform.
  • Explicitly mention support for Linux/macOS environments, and provide guidance for users on those platforms.
  • Where only PowerShell is available, note this limitation and suggest alternatives or workarounds for Linux users.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/networking-features.md .../blob/main/articles/app-service/networking-features.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias primarily in the Hybrid Connections section, where only Windows Server is mentioned as a supported platform for the Hybrid Connection Manager, with no mention of Linux support or alternatives. Additionally, the gateway-required virtual network integration feature is explicitly limited to App Service Windows plans, with no Linux equivalent or workaround discussed. There are no Linux-specific examples, tools, or instructions provided, and Windows tools/patterns are referenced before any cross-platform or Linux options.
Recommendations
  • Explicitly state whether Hybrid Connection Manager is available for Linux, and if not, provide alternative solutions or workarounds for Linux users.
  • Include Linux-specific instructions, examples, or notes wherever Windows-only features are mentioned, or clarify platform limitations.
  • Where features are Windows-only (e.g., gateway-required VNet integration), offer guidance for Linux users on equivalent networking patterns or recommend supported alternatives.
  • Add parity in documentation by providing examples, screenshots, and step-by-step guides for both Windows and Linux environments where applicable.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-private-endpoint.md ...main/articles/app-service/overview-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows and PowerShell examples and tools before Linux equivalents, and by omitting explicit Linux-focused instructions or examples. The related content section lists Azure PowerShell before ARM templates and Terraform, and there are no Bash or Linux CLI-specific examples. The text also refers to Windows and Linux apps together but does not provide parity in examples or troubleshooting for Linux environments.
Recommendations
  • Add explicit Linux/Bash CLI examples alongside or before PowerShell examples, especially in sections referencing Azure CLI.
  • Ensure that Linux tools and workflows (such as Bash scripting, Linux DNS tools, etc.) are mentioned and demonstrated where relevant.
  • In the 'Related content' section, list Azure CLI and ARM template examples before PowerShell, or group them without preference.
  • Include troubleshooting notes or examples specific to Linux environments (e.g., modifying /etc/hosts, using dig/nslookup on Linux).
  • Clarify any platform-specific differences in setup or behavior for Windows vs. Linux apps, and provide guidance for both.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-data-sources.md ...es/app-service/configure-language-java-data-sources.md
High Priority View Details →
Scanned: 2026-01-06 22:28
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides both Windows and Linux instructions for configuring data sources in Tomcat and JBoss on Azure App Service. However, the Windows section is notably more detailed, with extensive PowerShell scripting and Windows-specific patterns (e.g., copying Tomcat to a local directory, using %LOCAL_EXPANDED%, and leveraging PowerShell for XSLT transforms). The Linux instructions are present but less detailed, often referencing external scripts or general approaches without as much step-by-step guidance. Windows tools and patterns (e.g., PowerShell, Windows environment variables) are emphasized, and the Windows section appears after the Linux section but is much more comprehensive. There are also cases where Linux instructions reference uploading scripts but do not provide as much explicit scripting detail as for Windows.
Recommendations
  • Provide equally detailed, step-by-step Linux examples for tasks that are covered in detail for Windows, such as automating Tomcat configuration changes using shell scripts (e.g., bash) instead of PowerShell.
  • Where PowerShell scripts are given for Windows, provide equivalent bash or shell scripts for Linux, including examples for copying Tomcat, performing XSLT transforms, and managing environment variables.
  • Avoid using Windows-specific environment variables (e.g., %HOME%, %LOCAL_EXPANDED%) in general explanations; instead, provide Linux equivalents (e.g., $HOME, /home/site/wwwroot) side-by-side.
  • Ensure that Linux tools (e.g., bash, sh, sed, xsltproc) are mentioned and demonstrated with the same level of detail as Windows tools.
  • Consider reordering or parallelizing the instructions so that for each major step, both Windows and Linux approaches are presented together for easier comparison.
  • Add troubleshooting tips and common pitfalls for Linux users, similar to what is often included for Windows scenarios.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-nodejs.md ...main/articles/app-service/configure-language-nodejs.md
High Priority View Details →
Scanned: 2026-01-06 22:28
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and tools (such as IISNode and web.config) are often presented first or in more detail, with Linux equivalents sometimes relegated to later sections or less detailed explanations. There is a reference to using PowerShell for Application Insights instrumentation, but no equivalent Linux CLI or Bash example. Some troubleshooting and configuration steps are Windows-specific (e.g., web.config), while Linux guidance is less prominent or missing for certain scenarios.
Recommendations
  • Ensure parity in example order: Present Windows and Linux instructions side-by-side or alternate which platform is described first.
  • Provide Linux/Bash alternatives for all PowerShell or Windows-specific instructions, especially for Application Insights instrumentation.
  • Expand troubleshooting and configuration sections to include Linux-specific guidance and common issues (e.g., container startup, permissions, config files).
  • Where Windows tools (IISNode, web.config) are discussed, clearly highlight Linux equivalents (PM2, startup scripts, etc.) and provide matching detail.
  • Audit all examples to ensure both platforms are equally represented and that Linux users are not required to infer steps from Windows instructions.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-app-service-certificate.md ...s/app-service/configure-ssl-app-service-certificate.md
High Priority View Details →
Scanned: 2026-01-06 22:28
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing Azure PowerShell examples alongside Azure CLI, but does not mention or provide Linux-specific shell examples (e.g., Bash, OpenSSL, or Linux certificate management tools). The ordering of examples places PowerShell after CLI, but the FAQ specifically references PowerShell. There is no mention of Linux certificate management patterns or tools, and all screenshots and portal instructions are platform-agnostic but implicitly Windows-oriented (e.g., PowerShell, lack of Linux shell references).
Recommendations
  • Add explicit Linux/Bash examples for certificate export and management, such as using OpenSSL to handle .pfx files.
  • Include notes or sections describing how to perform certificate management tasks on Linux systems, including command-line tools commonly used on Linux.
  • Balance the FAQ and troubleshooting sections to reference both PowerShell and Linux/Bash workflows.
  • If screenshots are relevant, include examples from Linux environments (e.g., Azure Cloud Shell in Bash mode).
  • Clarify that Azure CLI commands work cross-platform and provide guidance for Linux users where workflows differ.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md ...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority View Details →
Scanned: 2026-01-06 22:28
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by providing a PowerShell script example for automating certificate binding, while not offering equivalent Linux shell (Bash) examples. The automation section lists Azure CLI and PowerShell, but only the PowerShell script is shown inline, with no Bash or cross-platform scripting examples. The documentation refers to uploading .pfx files (a Windows-centric certificate format) without mentioning Linux-friendly alternatives like .pem. There is also a lack of explicit Linux workflow guidance, and Windows tools/patterns are mentioned or implied first.
Recommendations
  • Add Bash or cross-platform shell script examples alongside PowerShell in the automation section.
  • Provide explicit Linux workflow guidance, including certificate formats commonly used on Linux (.pem, .crt) and how to convert them to .pfx if needed.
  • Ensure Azure CLI examples are shown inline, not just as links, and clarify that Azure CLI is cross-platform.
  • Mention Linux tools (e.g., OpenSSL) for certificate management and provide example commands.
  • Review the order of tool presentation to avoid always listing Windows/PowerShell first.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-best-practices.md ...ain/articles/app-service/app-service-best-practices.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. It references Windows-specific tools and patterns (e.g., web.config, iisnode) without providing equivalent Linux alternatives or examples. In sections discussing configuration and troubleshooting, only Windows-centric approaches are described, and Linux methods are either omitted or mentioned secondarily. There are also missing Linux-specific examples for common scenarios, such as configuring auto-healing or Node.js process management outside of containers.
Recommendations
  • For every mention of web.config or iisnode, provide equivalent Linux configuration methods (e.g., app settings, environment variables, or nginx/Apache config).
  • Include Linux-specific examples for auto-healing and process management, such as using PM2 or systemd for Node.js apps.
  • When referencing tools or configuration files, clarify which are Windows-specific and offer parallel Linux guidance.
  • Ensure that troubleshooting and best practice sections include both Windows and Linux workflows, with examples for each.
  • Review and update the Node.js section to include Linux-native hosting guidance, not just iisnode.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v3-tier.md ...s/app-service/app-service-configure-premium-v3-tier.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting Windows (non-Linux) examples and tools first in several sections. PowerShell is given equal or more prominence than Azure CLI, and the Azure portal (a GUI tool more familiar to Windows users) is the primary method described for most operations. Linux-specific instructions are minimal and only appear for SKU availability checks.
Recommendations
  • Provide Linux examples and instructions alongside or before Windows/PowerShell examples, especially in automation sections.
  • Include Bash shell and scripting examples for Linux users, not just Azure CLI and PowerShell.
  • Clarify that Azure CLI commands can be run on both Windows and Linux, and provide context for cross-platform usage.
  • Add screenshots or walkthroughs using the Azure CLI in a Linux terminal, not just the Azure portal.
  • Ensure that any references to the Azure portal are supplemented with equivalent command-line instructions for both platforms.
GitHub Create Pull Request
← Previous Page 2 of 10 Next →