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 76-100 of 2121 flagged pages
App Service Certificates in App Service Environment ...icles/app-service/environment/overview-certificates.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 in several areas. The per-app private client certificate method is explicitly limited to Windows code apps, with no Linux equivalent or workaround described. All example commands for certificate verification and generation use PowerShell, and the Kudu console instructions are Windows-centric. There are no Linux shell or cross-platform examples for certificate management, verification, or generation in the private client certificate section. The documentation does acknowledge Linux support for the Root Certificate API, but practical examples and troubleshooting for Linux scenarios are missing.
Recommendations
  • Provide equivalent Linux shell (bash, openssl) examples for certificate verification and generation, especially in the private client certificate section.
  • Clarify whether there are any Linux-compatible alternatives for per-app root certificate configuration, or explicitly state the limitation.
  • Include troubleshooting and verification steps for Linux apps (e.g., how to check trust store contents in Linux containers).
  • Mention cross-platform tools and patterns where possible, not just Windows/PowerShell.
  • If features are Windows-only, offer guidance or workarounds for Linux users, or link to relevant feature requests or roadmap items.
GitHub Create Pull Request
App Service Prerequisites ...cludes/tutorial-microsoft-graph-as-app/introduction.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions first, referencing Visual Studio (a Windows-centric tool), and omitting Linux-specific examples or shell commands. The Azure CLI example is present, but PowerShell is prioritized and no explicit Linux workflow or troubleshooting is discussed.
Recommendations
  • Present Azure CLI (cross-platform) instructions before PowerShell, or side-by-side.
  • Include explicit Linux shell (bash) examples and notes for users deploying from Linux environments.
  • Reference cross-platform development tools (e.g., VS Code) alongside Visual Studio.
  • Add troubleshooting or environment notes for Linux users, especially regarding authentication and permissions.
  • Clarify that all steps can be performed from Linux/macOS terminals using 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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation lists Windows file types and tools (cmd, bat, exe, PowerShell) in detail and gives multiple examples for Windows, while Linux support is described more briefly, with only *.sh* scripts explicitly mentioned and fewer examples of supported file types. Windows examples and tools are presented first and in greater detail, with Linux equivalents either missing or less emphasized.
Recommendations
  • Provide a more comprehensive list of supported Linux file types (e.g., *.py*, *.pl*, *.rb*, *.js*, *.jar*, etc.) similar to the Windows section.
  • Include explicit examples for Linux, such as Python (*.py*), Perl (*.pl*), Ruby (*.rb*), and Java (*.jar*) scripts, not just *.sh*.
  • Balance the order and detail of Windows and Linux sections so that Linux is not always listed after Windows and receives equal coverage.
  • Mention Linux-specific tools or runtimes (e.g., bash, python, node, java) in the same way Windows tools (cmd, PowerShell) are highlighted.
  • Clarify that runtimes for various languages are installed for both Windows and Linux environments, not just Windows.
GitHub Create Pull Request
App Service Set Up Azure Arc for App Service, Functions, and Logic Apps .../articles/app-service/manage-create-arc-environment.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Bash and PowerShell examples for most steps, but PowerShell is given equal prominence throughout, which may signal a Windows bias. There are no Linux-specific examples (e.g., using native Linux tools or shell idioms), and no mention of Linux-specific issues, troubleshooting, or alternative patterns. The use of PowerShell tabs and examples may make the documentation feel Windows-centric, especially since PowerShell is not the default shell on most Linux distributions. There is also a lack of explicit guidance for Linux users, such as handling file paths, permissions, or package management differences.
Recommendations
  • Add explicit Linux troubleshooting notes, such as permissions, file paths, and package installation steps.
  • Clarify that Bash examples are intended for Linux/macOS users and PowerShell for Windows users.
  • Provide guidance for using native Linux tools (e.g., base64, grep, sed) where appropriate.
  • Consider removing PowerShell examples or moving them to a secondary position unless there is a clear user need.
  • Add notes about differences in Azure CLI usage on Linux vs. Windows, such as environment variable syntax and file system locations.
  • Include links to Linux-specific prerequisites (e.g., installing Azure CLI and kubectl on Ubuntu, CentOS, etc.).
GitHub Create Pull Request
App Service Supported platforms and file types ...includes/webjobs-create/webjobs-supported-platforms.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation lists Windows hosting options before Linux and gives Windows-specific file types and tools (e.g., .exe, .cmd, .bat, PowerShell) before mentioning Linux equivalents (e.g., Bash scripts). PowerShell is highlighted as a script type, but no Linux shell alternatives (like zsh) are mentioned. The ordering and emphasis suggest a Windows-centric perspective.
Recommendations
  • List Linux hosting options and script types before or alongside Windows options to avoid implicit prioritization.
  • Include examples of Linux shell scripts beyond Bash, such as zsh or fish, to match the specificity given to PowerShell.
  • Mention Linux-specific tools or patterns (e.g., cron jobs, shell environments) where relevant.
  • Ensure parity in examples and explanations for both Windows and Linux environments throughout the documentation.
GitHub Create Pull Request
App Service Back Up an App ...e-docs/blob/main/articles/app-service/manage-backup.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific terminology and paths (e.g., %HOME%, D:\home\site\wwwroot) are used throughout, often without Linux equivalents or with Windows listed first. Instructions for file exclusion reference Windows paths and tools (Kudu DebugConsole, FTP to D:\home), and PowerShell is mentioned as a scripting option alongside Azure CLI, but no Linux shell (bash) or Linux-specific automation examples are provided. The documentation also references Windows-specific features (MySQL in-app for Web Apps (Windows)), and examples for file system access and backup filtering are Windows-centric. Linux equivalents are either missing or mentioned secondarily.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, including file paths (e.g., /home/site/wwwroot) and shell commands.
  • Include bash or shell script automation samples in addition to PowerShell.
  • When referencing tools like Kudu DebugConsole or FTP, clarify usage for both Windows and Linux environments.
  • Ensure that all file system instructions (such as creating _backup.filter) include both Windows and Linux paths and methods.
  • Avoid listing Windows examples or terminology first; present Windows and Linux options equally.
  • Explicitly mention how backup and restore processes differ or are the same for Linux-based App Service apps.
GitHub Create Pull Request
App Service Per-App Scaling for High-Density Hosting ...blob/main/articles/app-service/manage-scale-per-app.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for per-app scaling, with no equivalent examples for Linux-native tools or cross-platform CLI (such as Azure CLI or Bash). The use of PowerShell cmdlets and variables is specific to Windows environments, and there is no mention of Linux or cross-platform alternatives. The ordering also places Windows tooling first and exclusively.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Provide Bash script examples for configuring per-app scaling, or at least show how to use Azure CLI in Bash.
  • Explicitly mention that the PowerShell examples are for Windows users, and provide guidance for Linux/macOS users.
  • Ensure that documentation consistently includes both Windows and Linux/cross-platform instructions, or links to relevant sections.
  • Consider including a table or section comparing PowerShell and Azure CLI commands for common tasks.
GitHub Create Pull Request
App Service Migrate from gateway-based to regional virtual network integration .../app-service/migrate-gateway-based-vnet-integration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides Azure CLI, Azure PowerShell, and Azure Portal instructions for all major steps, but consistently lists Azure PowerShell examples after Azure CLI and before Linux-native alternatives (if any). Azure PowerShell is a Windows-centric tool, and its inclusion and prominence (including interactive code blocks) may indicate a bias toward Windows users. There are no Linux shell-specific examples (e.g., Bash scripts), and PowerShell is presented as a primary automation method, which is less common on Linux. The documentation does not mention Linux-specific tools or patterns, and does not provide parity for Linux-native scripting environments.
Recommendations
  • Add Bash shell script examples for each CLI step to demonstrate Linux-native automation.
  • Clarify that Azure PowerShell is available cross-platform, but recommend CLI and Bash for Linux users.
  • Explicitly mention Linux support and provide troubleshooting or migration tips for Linux-based App Service apps.
  • Reorder examples so that CLI/Bash instructions appear before PowerShell, or provide tabs for Linux and Windows workflows.
  • Include notes or links to Linux-specific documentation where relevant.
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-12 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 the migration script, providing only PowerShell examples for key steps (such as base64 decoding), and referencing a migration script that is a PowerShell (.ps1) file. There are no Linux shell (bash/sh) equivalents or examples, and Linux tools for decoding or scripting are not mentioned. The prerequisites list PowerShell before Azure CLI and Docker, further reinforcing Windows-first patterns.
Recommendations
  • Provide bash/sh equivalents for all PowerShell commands, especially for base64 decoding and script execution.
  • Offer a migration script in bash or Python, or document how to run the PowerShell script on Linux (e.g., via pwsh).
  • List prerequisites in a cross-platform manner, e.g., 'PowerShell or bash', and clarify platform compatibility for scripts.
  • Include Linux-specific instructions and examples alongside Windows ones throughout the documentation.
  • Reference Linux tools (e.g., base64, curl, jq) where appropriate, and avoid assuming PowerShell as the default scripting environment.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows evidence of Windows bias, particularly in the 'Hybrid Connections' section, which exclusively mentions installing the Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux support or alternatives. The 'Gateway-required virtual network integration' feature is explicitly limited to Windows plans. There are no examples or instructions for Linux-based environments, and Windows tools and patterns are referenced without Linux parity.
Recommendations
  • Explicitly state whether features like Hybrid Connection Manager and Gateway-required virtual network integration support Linux, and provide Linux installation or usage instructions if available.
  • Add Linux-specific examples and guidance throughout the documentation, especially for networking scenarios and tool usage.
  • Where features are Windows-only, clearly indicate this and suggest Linux alternatives or workarounds where possible.
  • Ensure parity in documentation structure by presenting Linux options and examples alongside Windows ones, rather than focusing on Windows first or exclusively.
GitHub Create Pull Request
App Service Operating System Functionality in Azure App Service ...articles/app-service/operating-system-functionality.md
High Priority View Details →
Scanned: 2026-01-12 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 page is heavily focused on Windows-based App Service environments. It describes file, network, and registry access using Windows terminology (e.g., %SystemDrive%, %ResourceDrive%, IIS, ASP.NET, COM components, PowerShell), and provides examples and explanations exclusively for Windows apps. Linux is mentioned only briefly and generically, with no Linux-specific examples, environment variables, or tooling discussed. Windows tools and patterns (IIS, ASP.NET, COM, PowerShell, registry, event logs) are referenced throughout, while Linux equivalents (e.g., /var, /etc, shell scripting, syslog, Linux file permissions) are absent.
Recommendations
  • Add parallel sections or callouts for Linux-based App Service environments, describing file system layout, environment variables (e.g., $HOME, /tmp), and access patterns.
  • Provide Linux-specific examples for file access, network access, and diagnostics (e.g., using Bash scripts, Linux logging mechanisms like syslog, accessing /proc or /etc).
  • Mention Linux tools and frameworks (e.g., Nginx, Apache, shell scripting) where appropriate, alongside Windows tools.
  • Clarify differences in process isolation, permissions, and diagnostic logging between Windows and Linux App Service environments.
  • Include a comparison table or summary highlighting key differences and similarities between Windows and Linux App Service functionality.
GitHub Create Pull Request
App Service Azure App Service Plans ...ob/main/articles/app-service/overview-hosting-plans.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page displays a Windows bias, particularly in the 'Managed Instance on Azure App Service (preview)' section, which is exclusively for Windows web apps and highlights Windows-specific features such as PowerShell scripts, RDP access, and legacy Windows component support. There are no equivalent Linux examples, tools, or parity notes for Linux users. The main documentation references both Windows and Linux as supported operating systems, but advanced features and examples focus on Windows, with Linux-specific guidance missing.
Recommendations
  • Add equivalent Linux-focused sections, especially for advanced hosting options, or explicitly state Linux limitations and roadmap.
  • Provide Linux-specific examples, tools, and configuration patterns (e.g., Bash scripts, SSH access, Linux middleware setup) alongside Windows examples.
  • Clarify feature parity between Windows and Linux App Service plans, including supported runtimes, networking, and storage options.
  • Include links to Linux documentation and migration guidance for users with Linux workloads.
  • Ensure that new features (such as Managed Instance) are described with Linux plans in mind, or provide clear messaging about future Linux support.
GitHub Create Pull Request
App Service Inbound/Outbound IP Addresses .../articles/app-service/overview-inbound-outbound-ips.md
High Priority View Details →
Scanned: 2026-01-12 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 exhibits a Windows bias in several ways: PowerShell examples are provided alongside Azure CLI, but there are no Bash or Linux shell equivalents for commands involving outbound IP discovery. Outbound IPv6 support is called out as available only for Windows apps, with Linux support explicitly missing. The documentation references Windows-specific tools and patterns (PowerShell, outbound IPv6 for Windows) before or instead of Linux alternatives, and does not provide parity in examples or tooling for Linux users.
Recommendations
  • Add Bash or Linux shell equivalents for all command-line examples, especially where PowerShell is used.
  • Clarify the availability of outbound IPv6 support for Linux apps and provide a roadmap or workaround for Linux users.
  • Ensure that examples using Azure CLI are presented before or alongside PowerShell, and explicitly note cross-platform compatibility.
  • Where features are Windows-only, provide clear guidance for Linux users, including alternative approaches or expected timelines for parity.
  • Include notes or examples for Linux-specific environments (e.g., WSL, native Linux terminals) when discussing command execution.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation for Managed Instance on Azure App Service is heavily Windows-centric, with exclusive focus on Windows workloads, tools, and configuration patterns. All examples and features reference Windows technologies (PowerShell scripts, registry, COM, MSI, IIS, GAC, RDP), and there is no mention of Linux equivalents or parity. Linux and container support is explicitly excluded, and configuration, troubleshooting, and best practices are described only in Windows terms.
Recommendations
  • Add Linux-specific examples and configuration patterns where possible, or clarify the roadmap for Linux parity.
  • Include equivalent Linux tooling (e.g., Bash scripts, systemd services, Linux file system mounts) in configuration and troubleshooting sections.
  • Provide a comparison table highlighting feature gaps and planned Linux support.
  • Explicitly state the lack of Linux support at the beginning of the documentation to set expectations.
  • If Linux support is planned, include guidance for migration or future parity.
  • Offer links to Linux App Service documentation for users seeking non-Windows solutions.
GitHub Create Pull Request
App Service Overview of Azure App Service .../azure-docs/blob/main/articles/app-service/overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. Windows-specific features and tools (such as PowerShell scripts, COM, registry, MSI, drive mapping, and RDP) are described in detail, especially in the Managed Instance section, with little or no equivalent Linux information. Windows workloads and tools are mentioned first and more extensively, while Linux support is referenced only briefly or as 'not supported' in certain scenarios. There are no Linux-specific examples or guidance for Linux users, and command-line tooling mentions Azure PowerShell before Azure CLI.
Recommendations
  • Provide Linux-specific examples and guidance, especially for deployment, configuration, and troubleshooting.
  • Mention Azure CLI before or alongside Azure PowerShell when discussing command-line tools, as CLI is cross-platform.
  • Include information about Linux-supported features and limitations in parity with Windows, especially in sections discussing Managed Instance.
  • Add references to Linux-friendly tools and patterns (e.g., Bash scripts, SSH diagnostics, Linux file system access) where relevant.
  • Clarify which features are exclusive to Windows and suggest Linux alternatives or workarounds where possible.
GitHub Create Pull Request
App Service Kudu service overview ...-docs/blob/main/articles/app-service/resources-kudu.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a subtle Windows bias by referencing Windows-specific tools and deployment patterns (such as IIS diagnostic dumps, IIS processes, and deployment webhooks for Windows apps) without mentioning Linux equivalents or clarifying Linux support. There are no Linux-specific examples or references to Linux-based App Service environments, and Windows concepts are mentioned first or exclusively.
Recommendations
  • Include information about Kudu features and diagnostics relevant to Linux-based App Service environments, such as access to Docker logs, process management, and deployment options.
  • Clarify which features are Windows-only and which are available or different on Linux (e.g., IIS dumps/processes vs. Linux process management).
  • Provide Linux-specific examples or references alongside Windows ones, especially for deployment, diagnostics, and process management.
  • Add a section or notes about differences in Kudu functionality between Windows and Linux App Service plans.
GitHub Create Pull Request
App Service Managed Identities ...main/articles/app-service/overview-managed-identity.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured heavily as a primary automation tool, with detailed examples and scripts, while Linux-native alternatives (such as Bash or shell scripting) are absent. In tabbed sections, PowerShell is presented before ARM templates and after Azure CLI, but Linux shell scripting is never mentioned. The documentation assumes the use of Windows tools (PowerShell) for local scripting, and does not provide parity for Linux users who may prefer Bash or other shell environments.
Recommendations
  • Add Bash/shell script examples alongside PowerShell for token retrieval and identity management, especially in sections where PowerShell scripts are shown.
  • Explicitly mention Linux support and provide guidance for Linux users, including any differences in environment variables or tooling.
  • Where PowerShell is referenced, clarify that Azure CLI commands and REST API calls are cross-platform and provide equivalent Bash examples.
  • Consider reordering tabs or examples so that cross-platform tools (Azure CLI, REST API) are presented before platform-specific tools (PowerShell).
  • Add a note or section about using managed identities from Linux-based development environments, including common patterns and troubleshooting tips.
GitHub Create Pull Request
App Service Integrate your app with an Azure virtual network ...main/articles/app-service/overview-vnet-integration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Example Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by providing detailed Windows Containers-specific limits and sample calculations, while omitting equivalent details for Linux containers. Windows-specific features (e.g., Windows Server Active Directory domain join, NetBIOS) are mentioned as unsupported, but there is no comparable discussion for Linux-specific features. The troubleshooting and command-line examples use Azure CLI, which is cross-platform, but the only deep-dive example is for Windows Containers. Linux is only referenced briefly in the context of continuous deployment network dependencies, with no parity in container scaling or subnet sizing guidance.
Recommendations
  • Add a dedicated section for Linux Containers, including subnet sizing, scaling, and networking limits, similar to the Windows Containers section.
  • Provide Linux-specific examples and calculations for App Service plan instance IP requirements.
  • Discuss any Linux-specific unsupported features or limitations to match the Windows-focused list.
  • Ensure that examples and guidance are presented for both platforms, or clarify when guidance applies equally to both.
  • Include troubleshooting steps and environment variable usage examples for Linux-based apps (e.g., how to access WEBSITE_PRIVATE_IP in Linux environments).
GitHub Create Pull Request
App Service Quickstart: Run a Custom Container on App Service ...in/articles/app-service/quickstart-custom-container.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Windows-related pivots (Visual Studio, Azure Portal, PowerShell, CLI) before their Linux equivalents, and by providing dedicated PowerShell and Windows CLI sections. Linux examples are present but are fewer and less prominently positioned, with no Linux-specific CLI or shell examples shown in the main pivot list.
Recommendations
  • Ensure Linux pivots (e.g., Bash/CLI, VS Code) are listed before or alongside Windows pivots to avoid ordering bias.
  • Add Linux-specific CLI or shell examples (e.g., Bash, Azure CLI for Linux) to match the PowerShell and Windows CLI coverage.
  • Provide parity in tooling examples, such as including Linux-native tools and workflows where Windows tools (like Visual Studio and PowerShell) are mentioned.
  • Review and balance the depth of instructions and examples for both platforms to ensure equal clarity and completeness.
GitHub Create Pull Request
App Service Quickstart: Deploy Managed Instance on Azure App Service (Preview) ...in/articles/app-service/quickstart-managed-instance.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. The only configuration (install) script provided is a PowerShell script (Install.ps1) that installs fonts specifically into the C:\Windows\Fonts directory and modifies Windows registry keys. All runtime and deployment examples use ASP.NET V4.8, a Windows-only framework. There are no Linux-based examples, nor any mention of Linux-compatible configuration scripts (e.g., Bash, shell scripts), Linux runtimes, or Linux file paths. The documentation assumes a Windows environment for both app deployment and configuration, and does not address Linux parity.
Recommendations
  • Provide equivalent Linux configuration (install) script examples, such as Bash scripts for font installation in Linux containers.
  • Include instructions and examples for deploying Linux-based runtimes (e.g., Node.js, Python, .NET Core) on Managed Instance.
  • Clarify whether Managed Instance supports Linux plans, and if so, document the differences and options.
  • Show how to register fonts or perform similar configuration tasks in Linux environments (e.g., copying fonts to /usr/share/fonts and running fc-cache).
  • Add notes or sections highlighting limitations or differences between Windows and Linux plans for Managed Instance.
  • Ensure that examples and screenshots do not exclusively reference Windows file paths or features.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page displays mild Windows bias in several areas. In the prerequisites, Windows and PowerShell configuration options are listed before Linux equivalents, and there is a strong emphasis on using PowerShell and Windows tools. The Visual Studio Code extension is mentioned without reference to Linux-specific editors or CLI workflows. While both Linux and Windows Terraform templates are provided, the overall structure and ordering favor Windows users, and there is limited discussion of Linux-specific tooling or workflows beyond the template itself.
Recommendations
  • List Linux/Bash configuration options before Windows/PowerShell options in the prerequisites section.
  • Include examples or references for popular Linux editors (e.g., Vim, Nano) and CLI workflows, not just Visual Studio Code.
  • Add explicit instructions for running Terraform commands on Linux, including any OS-specific considerations (e.g., permissions, package installation).
  • Ensure parity in troubleshooting and cleanup instructions for both Linux and Windows environments.
  • Consider adding a section on using Terraform in native Linux environments outside of Azure Cloud Shell.
GitHub Create Pull Request
App Service Environment Variables and App Settings Reference ...ob/main/articles/app-service/reference-app-settings.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific tools and patterns (such as Web Deploy/MSDeploy, IIS, and Windows file paths) are mentioned more frequently and often before their Linux equivalents. Many environment variables and examples reference Windows paths (e.g., D:\home), Windows-specific behaviors, or tools, while Linux alternatives are sometimes only mentioned as exceptions or in later sections. Some settings and explanations are tailored to Windows scenarios (e.g., machineKey, IIS, w3wp.exe) without equivalent Linux details or examples. In some cases, Linux-specific configuration is referenced only briefly or as an afterthought, and there are missing Linux examples for certain deployment and logging scenarios.
Recommendations
  • Ensure Linux and Windows examples are provided side-by-side for all environment variables, especially where file paths, deployment methods, or logging are involved.
  • When referencing tools (e.g., Web Deploy/MSDeploy, IIS), mention Linux alternatives (such as Oryx, Apache, Nginx) with equal prominence and detail.
  • Avoid using Windows paths (e.g., D:\home) as the default example; instead, show both Windows and Linux paths (e.g., D:\home and /home) together.
  • For settings that are Windows-specific (e.g., machineKey, IIS, w3wp.exe), provide Linux equivalents or explicitly state when no equivalent exists.
  • Add Linux-focused troubleshooting and configuration sections where only Windows guidance is currently present.
  • Review all tables and examples to ensure Linux scenarios are not omitted or relegated to footnotes.
GitHub Create Pull Request
App Service Routine Maintenance, Restarts, and Downtime ...n/articles/app-service/routine-maintenance-downtime.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by consistently presenting Windows-specific features, tools, and examples before their Linux equivalents. Windows mechanisms (such as IIS Application Initialization Module and .NET Core stdout logging) are described in detail, while Linux alternatives are mentioned briefly or as afterthoughts. Several features are explained with Windows-centric terminology and links, with Linux options either missing, less detailed, or referenced only in passing. There is a lack of parity in example depth and guidance for Linux users.
Recommendations
  • Provide equally detailed explanations and examples for Linux-specific mechanisms, such as expanding on WEBSITE_WARMUP_PATH usage and configuration.
  • Include Linux-first or at least parallel examples for features like application initialization, logging, and troubleshooting.
  • Reference Linux-native tools and patterns (e.g., Nginx/Apache warm-up, stdout/stderr logging, systemd service management) where appropriate.
  • Ensure that documentation sections do not default to Windows terminology or tools, and offer Linux alternatives with equal prominence.
  • Add step-by-step guides or links for configuring and troubleshooting Linux App Service environments, matching the depth given to Windows.
  • Review and update all feature descriptions to clarify platform-specific behaviors and limitations for both Windows and Linux users.
GitHub Create Pull Request
App Service Tutorial - .NET Web app accesses Microsoft Graph as the app| Azure ...e/scenario-secure-app-access-microsoft-graph-as-app.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides installation instructions using both the .NET Core CLI and the Visual Studio Package Manager Console. However, the Package Manager Console instructions (PowerShell-based) are presented after the CLI, and there is no explicit mention of Linux-specific development environments or tools. Visual Studio and its console are Windows-centric, and there are no examples or guidance for Linux IDEs (such as VS Code on Linux) or package management workflows specific to Linux. The documentation does not mention Linux prerequisites, nor does it provide parity for Linux users beyond the generic dotnet CLI commands.
Recommendations
  • Add explicit instructions for Linux users, such as using VS Code or JetBrains Rider, and clarify that the dotnet CLI commands work cross-platform.
  • Remove or de-emphasize Package Manager Console instructions, or provide equivalent instructions for Linux environments (e.g., terminal-based workflows).
  • Include a note about platform compatibility for the .NET CLI and clarify that Visual Studio is Windows-only, while VS Code is cross-platform.
  • Provide troubleshooting steps or prerequisites for Linux environments, such as installing .NET SDK on Ubuntu or other distributions.
  • Consider adding screenshots or examples of the workflow on Linux to ensure parity and inclusivity.
GitHub Create Pull Request
App Service Tutorial - .NET Web app accesses storage by using managed identities | Azure ...cles/app-service/scenario-secure-app-access-storage.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting installation instructions for the NuGet packages using Visual Studio's Package Manager Console (PowerShell) and referencing Visual Studio tooling before mentioning the .NET Core command-line interface. There are no explicit Linux-specific instructions or examples, and the use of PowerShell and Visual Studio tools may not be applicable or familiar to Linux users.
Recommendations
  • Provide explicit Linux instructions, such as using the .NET CLI in a bash shell and clarifying that Visual Studio steps are optional.
  • Reorder installation instructions to present cross-platform (dotnet CLI) commands first, followed by Windows-specific tooling.
  • Add notes or sections for Linux/macOS users, including guidance for common editors (VS Code, JetBrains Rider) and terminal usage.
  • Avoid assuming Visual Studio or PowerShell availability; mention alternatives for package management and project setup on Linux.
GitHub Create Pull Request
← Previous Page 4 of 85 Next →