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 151-175 of 247 flagged pages
App Service Getting started with Azure App Service ...docs/blob/main/articles/app-service/getting-started.md
Medium 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 demonstrates a moderate Windows bias, particularly in the .NET and Python sections. Windows tools like Visual Studio and Azure PowerShell are listed before Linux alternatives, and examples often default to Windows or PowerShell tabs. Linux/macOS equivalents are present but sometimes less prominent or appear after Windows options. The 'Next step' call-to-action also points to a Windows-centric technology (ASP.NET). Other stacks (Java, Node.js, PHP) show better Linux parity.
Recommendations
  • Ensure Linux/macOS examples and tools are listed alongside or before Windows options in all tables and quickstarts.
  • Add explicit Linux/macOS tabs/examples for PowerShell-heavy sections, or clarify cross-platform CLI alternatives.
  • Balance the order of tool presentation (e.g., list Visual Studio Code and CLI before Visual Studio and PowerShell where possible).
  • Provide 'Next step' actions for non-Windows stacks, or rotate them to avoid Windows-first impression.
  • Audit linked quickstarts to ensure Linux/macOS instructions are equally detailed and discoverable.
GitHub Create Pull Request
App Service Supported platforms and file types ...includes/webjobs-create/webjobs-supported-platforms.md
Medium 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 lists Windows hosting options and file types before Linux equivalents, and provides more detail for Windows-specific tools (executables, batch files, PowerShell scripts) than for Linux (only Bash scripts are mentioned explicitly). There are no Linux-specific examples or references to Linux tools such as shell scripts beyond Bash, nor are Linux usage patterns highlighted.
Recommendations
  • List Linux hosting options and file types before or alongside Windows options to avoid ordering bias.
  • Expand the file/script types section to include more Linux-specific examples, such as shell scripts (.sh), and mention common Linux tools (e.g., cron, shell utilities).
  • Provide explicit Linux usage examples or patterns, similar to the detail given for Windows (e.g., how to use Bash scripts, Python scripts on Linux).
  • Clarify that both Windows and Linux platforms are equally supported and provide parity in documentation examples.
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-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 paths (e.g., %HOME%, D:\home\site\wwwroot) and terminology are used throughout, often without Linux equivalents or with Linux information presented secondarily. Examples for file exclusion and backup filtering use Windows-style paths and drive letters. The Kudu DebugConsole and FTP upload instructions reference Windows file systems. While Azure CLI is cross-platform, PowerShell is mentioned as a scripting option without equivalent Bash or Linux shell samples. The documentation does not provide Linux/macOS-specific instructions or examples for tasks like file uploads, path references, or scripting, which may create friction for non-Windows users.
Recommendations
  • Provide Linux/macOS equivalents for all file paths and commands (e.g., /home/site/wwwroot instead of D:\home\site\wwwroot).
  • Include Bash or Linux shell script samples alongside PowerShell examples.
  • Clarify instructions for uploading files using Linux/macOS tools (e.g., SCP, SFTP, or Azure CLI).
  • Present cross-platform examples together, or alternate which OS is shown first.
  • Explicitly state when instructions are OS-agnostic and when OS-specific steps are required.
GitHub Create Pull Request
App Service Inbound/Outbound IP Addresses .../articles/app-service/overview-inbound-outbound-ips.md
Medium 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 both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but PowerShell examples are always shown directly after CLI, with no mention of Linux-specific tools or shell environments. The outbound IPv6 support section explicitly states that outbound IPv6 is only available for Windows apps, with no workaround or parity for Linux apps. There are no Linux/macOS-specific examples or guidance for users who may not use PowerShell.
Recommendations
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and recommend CLI for Linux/macOS users.
  • Provide bash or shell script examples where appropriate, especially for tasks like parsing output.
  • Explicitly mention limitations for Linux apps (e.g., outbound IPv6) and suggest alternatives or workarounds if available.
  • Avoid listing PowerShell examples before CLI, or group them under OS-specific tabs (Windows/PowerShell, Linux/macOS/CLI).
  • Add notes or sections for Linux/macOS users where platform-specific behavior exists.
GitHub Create Pull Request
App Service Prerequisites ...cludes/tutorial-microsoft-graph-as-app/introduction.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for granting Microsoft Graph permissions to a managed identity, but PowerShell is presented first and in greater detail. PowerShell is typically associated with Windows environments, and the instructions reference Visual Studio (a Windows-first IDE) for initial setup. There are no explicit Linux/macOS-specific instructions or examples, and no mention of alternative Linux tools or shell environments.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more accessible to Linux/macOS users.
  • Add explicit notes or examples for Linux/macOS users, such as using Bash or zsh.
  • Mention that Azure CLI commands work on Linux/macOS and provide troubleshooting tips for those platforms.
  • Avoid referencing Windows-centric tools (like Visual Studio) without mentioning alternatives (such as VS Code or command-line deployment).
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
Medium 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 lists Windows file types and tools (cmd, bat, exe, PowerShell) in detail and gives multiple examples for Windows, while Linux sections only mention *.sh* scripts and provide fewer examples. Windows examples are presented first and with more variety, while Linux examples are minimal and lack parity (e.g., no mention of Bash, Python, or Node.js in the main Linux code section except as a conditional example).
Recommendations
  • Expand Linux sections to list all supported file types (e.g., *.sh*, *.py*, *.js*, *.jar*) explicitly, matching the detail given for Windows.
  • Provide Linux-specific tool references (e.g., Bash, Python, Node.js) in the same way as Windows tools (cmd, PowerShell).
  • Give Linux examples for each runtime, not just conditional ones (e.g., show *.py*, *.js*, *.jar* as supported file types for Linux code and containers).
  • Present Windows and Linux sections in parallel structure, ensuring equal coverage and clarity.
  • Avoid listing Windows examples first unless there is a technical reason; consider alternating or combining lists for neutrality.
GitHub Create Pull Request
App Service Per-App Scaling for High-Density Hosting ...blob/main/articles/app-service/manage-scale-per-app.md
Medium 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 provides detailed instructions for per-app scaling using PowerShell cmdlets, which are primarily Windows-centric. No equivalent examples are given for Linux/macOS users (e.g., Azure CLI or Bash). The PowerShell section appears before the ARM template section, reinforcing a Windows-first approach. There is no mention of Linux-native tools or cross-platform alternatives for command-line configuration.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, showing how to create and update App Service plans and apps with per-app scaling using az commands.
  • Explicitly mention that ARM templates and Azure CLI are cross-platform and suitable for Linux/macOS users.
  • Reorder sections so that cross-platform methods (ARM template, Azure CLI) are presented before or alongside PowerShell.
  • Include notes or links for Linux/macOS users on how to perform these tasks without PowerShell.
GitHub Create Pull Request
App Service Use Private Endpoints for Apps ...main/articles/app-service/overview-private-endpoint.md
Medium 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 lists Windows-centric tools and examples before Linux equivalents, notably in the 'Related content' section where Azure PowerShell is highlighted as a primary method for creating private endpoints, and no explicit Linux shell or Bash examples are provided. The documentation references Windows and Linux support but does not provide parity in example commands or troubleshooting steps for Linux/macOS users. The mention of modifying the host entry for DNS testing is generic, but lacks Linux/macOS-specific instructions (e.g., editing /etc/hosts).
Recommendations
  • Add explicit Bash/Azure CLI examples for all major operations, especially in quickstart and troubleshooting sections.
  • Ensure that Linux/macOS instructions (such as editing /etc/hosts for DNS tests) are included alongside Windows instructions.
  • In 'Related content', list Azure CLI and ARM template methods before or alongside PowerShell to avoid Windows-first ordering.
  • Provide troubleshooting steps and tool recommendations for Linux/macOS users (e.g., using dig/nslookup for DNS validation).
GitHub Create Pull Request
App Service Overview of Azure App Service .../azure-docs/blob/main/articles/app-service/overview.md
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias, especially in the Managed Instance section, which exclusively highlights Windows-specific features (COM, registry, MSI, drive mapping, PowerShell scripts, RDP) and tools. Linux and container support are explicitly excluded from Managed Instance, with no Linux equivalents or examples provided. Windows tools and patterns are described in detail, while Linux is only mentioned as unsupported in this context. Additionally, Windows workloads and technologies are listed first and in greater detail.
Recommendations
  • Add equivalent Linux-focused examples and features where possible, or clarify Linux alternatives for legacy scenarios.
  • Provide parity in documentation by including Linux/container deployment and management patterns alongside Windows-specific ones.
  • Explicitly mention Linux tooling and scripting options (e.g., Bash, shell scripts) in relevant sections, especially where PowerShell is highlighted.
  • Ensure that Linux and container support are described with equal detail in decision guides and feature lists.
  • If features are Windows-only, provide guidance or links for Linux users to achieve similar outcomes or explain limitations.
GitHub Create Pull Request
App Service Migrate Docker Compose to sidecars ...es/app-service/migrate-sidecar-multi-container-apps.md
Medium Priority View Details →
Scanned: 2026-01-12 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 shows a notable Windows bias. The script-based migration is exclusively PowerShell-based, with no Bash or Linux shell equivalent provided. The prerequisites list PowerShell first, and all scripting examples for automation use PowerShell. Even in the manual migration, decoding the base64 Docker Compose config is shown only with a PowerShell command, with no Linux/macOS alternative. There are no Bash or shell script examples, and no mention of cross-platform alternatives for users on Linux or macOS.
Recommendations
  • Provide a Bash or shell script equivalent for the migration script, or document how to run the PowerShell script on Linux/macOS (e.g., via pwsh).
  • Include Linux/macOS-specific commands for base64 decoding (e.g., `base64 -d`), alongside the PowerShell example.
  • List prerequisites in a cross-platform way, e.g., 'PowerShell (Windows/macOS/Linux) or Bash (Linux/macOS)'.
  • Ensure all automation steps have both PowerShell and Bash examples, or note cross-platform compatibility.
  • Explicitly mention how Linux/macOS users can perform each step, especially for scripting and decoding tasks.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page shows evidence of Windows bias primarily in the 'Hybrid Connections' section, where the required relay agent (Hybrid Connection Manager) is only available for Windows Server 2012 or newer, with no mention of Linux or macOS alternatives. Additionally, the 'Gateway-required virtual network integration' feature is explicitly limited to App Service Windows plans, with no Linux equivalent or workaround described. There are no Linux/macOS-specific examples or parity notes for these features, and Windows tools are mentioned first and exclusively in critical sections.
Recommendations
  • Explicitly state OS limitations for features like Hybrid Connections and Gateway-required VNet Integration at the top of relevant sections.
  • Provide Linux/macOS alternatives or workarounds for Hybrid Connections, or clarify if none exist.
  • Add parity notes or links to Linux-compatible networking solutions for outbound connectivity.
  • Where features are Windows-only, suggest alternative approaches for Linux users (e.g., VPN, VNet Integration, or other Azure services).
  • Include examples and instructions for Linux-based deployments where possible, or clarify feature availability by OS.
GitHub Create Pull Request
App Service Managed Identities ...main/articles/app-service/overview-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides extensive Azure PowerShell examples and references, which are primarily Windows-centric. PowerShell is featured as a first-class option in most code tabs, and some instructions (such as for creating user-assigned identities for Functions) are only available in PowerShell, with explicit notes about lack of support in other tools. While Azure CLI and ARM template examples are present (which are cross-platform), the prominence and depth of PowerShell coverage, as well as the lack of explicit Bash or Linux shell examples, indicate a moderate Windows bias. There are no explicit Linux/macOS-specific instructions or troubleshooting notes.
Recommendations
  • Add explicit Bash/Linux shell examples where possible, especially for token retrieval and scripting tasks.
  • Clarify that Azure CLI commands work on Linux/macOS and provide any necessary environment setup notes for those platforms.
  • Where PowerShell is used, offer equivalent Bash or shell scripts for Linux/macOS users.
  • Note any platform-specific limitations or differences (e.g., PowerShell module availability, CLI differences) to help non-Windows users avoid confusion.
  • Ensure that instructions for creating and assigning user-assigned identities are fully supported and documented for Linux/macOS environments.
GitHub Create Pull Request
App Service Quickstart: Run a Custom Container on App Service ...in/articles/app-service/quickstart-custom-container.md
Medium 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 presents Windows-related pivots (Visual Studio, Azure Portal, PowerShell, CLI) before their Linux equivalents, and includes Windows-specific tools like PowerShell and Visual Studio. Linux examples are present but appear after Windows ones, and there is no explicit parity check to ensure Linux users have equivalent guidance for all scenarios.
Recommendations
  • Reorder pivots to present Linux and Windows options side-by-side or alternate their order to avoid implicit prioritization.
  • Ensure all Windows-specific tools (e.g., PowerShell, Visual Studio) have clear Linux/macOS equivalents (e.g., Bash, Visual Studio Code) with matching depth and clarity.
  • Add a summary table comparing Windows and Linux workflows for quick reference.
  • Explicitly mention cross-platform compatibility and highlight differences or limitations for each OS.
GitHub Create Pull Request
App Service Quickstart: Deploy an ASP.NET web app ...lob/main/articles/app-service/quickstart-dotnetcore.md
Medium 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 demonstrates a moderate Windows bias. Visual Studio (Windows-only) is presented first and in greatest detail, with extensive screenshots and step-by-step instructions. PowerShell instructions are included, but are explicitly recommended only for Windows hosting, and PowerShell-specific commands (e.g., Compress-Archive) are used without Linux equivalents. Some CLI and VS Code instructions are cross-platform, but Windows tools and patterns (Visual Studio, PowerShell) are mentioned before Linux alternatives. There are no explicit Linux shell examples for tasks like zipping files for deployment, and some portal instructions favor Windows (e.g., GitHub deployment limitations for Linux).
Recommendations
  • Add explicit Linux/macOS shell examples for tasks like zipping published files (e.g., using 'zip' or 'tar' commands).
  • Provide parity in screenshots and step-by-step instructions for VS Code and CLI workflows, matching the detail given to Visual Studio.
  • Clarify which steps are cross-platform and which are Windows-only, especially in PowerShell and Visual Studio sections.
  • Where PowerShell is recommended for Windows, provide equivalent Bash or shell instructions for Linux users.
  • In portal instructions, clarify limitations for Linux and offer alternative deployment steps for Linux users.
  • Consider reordering sections so that cross-platform tools (CLI, VS Code) are presented before or alongside Windows-only tools.
GitHub Create Pull Request
App Service Create a scheduled WebJob with prebuilt samples ...s/blob/main/articles/app-service/quickstart-webjobs.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows examples and tooling first, listing Windows-specific script types (CMD, Batch, PowerShell, F#) before Linux equivalents. The Windows tab includes more language/script options than the Linux tab, and the overall structure prioritizes Windows in both order and breadth of examples.
Recommendations
  • Present Windows and Linux options side-by-side or in a neutral order, rather than listing Windows first.
  • Expand Linux sample coverage to include additional script types where possible (e.g., F#, PowerShell Core if supported, etc.).
  • Explicitly state any platform limitations for script types, and provide guidance or alternatives for Linux users.
  • Ensure parity in documentation detail and sample availability for both platforms.
GitHub Create Pull Request
App Service Kudu service overview ...-docs/blob/main/articles/app-service/resources-kudu.md
Medium 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 for Kudu service overview demonstrates a mild Windows bias. Several features and examples reference Windows-specific tools (IIS diagnostic dumps, IIS processes, site extensions, deployment webhooks for Windows apps) without mentioning Linux equivalents or clarifying their availability on Linux-based App Service plans. There are no examples or notes for Linux users, and Windows terminology appears first or exclusively in critical feature lists.
Recommendations
  • Explicitly state which features are available on Linux-based App Service plans and which are Windows-only.
  • Provide examples or notes for Linux users, such as how to access logs or manage processes on Linux plans.
  • Balance feature lists by mentioning Linux-specific capabilities or clarifying cross-platform support.
  • Add links to documentation about Kudu usage on Linux App Service plans.
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-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 a moderate Windows bias. Windows-specific tools, paths, and conventions are frequently mentioned first or exclusively (e.g., references to D:\home, applicationHost.config, IIS, w3wp.exe, .bat files, and Windows-only environment variables). Many examples and explanations use Windows-centric terminology, and some features/tools (like Web Deploy/MSDeploy, machineKey, Jetty/Tomcat startup scripts) are described only for Windows or with much greater detail for Windows than Linux. Linux equivalents are sometimes mentioned, but often as a secondary note or with less detail. Some sections (such as build automation and logging) provide more configuration options or examples for Windows than Linux. There are also cases where Linux-specific examples or parity are missing or less clear.
Recommendations
  • Ensure Linux and macOS equivalents are always mentioned alongside Windows tools and paths, not just as secondary notes.
  • Provide Linux/macOS-specific examples and configuration details for all environment variables and features, especially for deployment, logging, and build automation.
  • Avoid using Windows paths (e.g., D:\home) as the primary example; show both Windows and Linux paths together.
  • Where Windows tools (e.g., Web Deploy/MSDeploy, applicationHost.config) are referenced, add clear Linux alternatives or state if not applicable.
  • Balance the detail and explanation between Windows and Linux/macOS sections, especially for language-specific settings and runtime behaviors.
  • Add explicit tabs or sections for Linux/macOS where only Windows is currently covered.
GitHub Create Pull Request
App Service Routine Maintenance, Restarts, and Downtime ...n/articles/app-service/routine-maintenance-downtime.md
Medium 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 moderate Windows bias. Windows-specific features and tools (such as IIS Application Initialization Module and .NET Core stdout logging) are described in detail, with Linux equivalents mentioned briefly or as afterthoughts. Windows examples and terminology (e.g., 'Windows Worker', IIS modules) are presented first and more extensively, while Linux guidance is limited to short notes (e.g., WEBSITE_WARMUP_PATH) without further explanation or examples. Some troubleshooting and logging recommendations are Windows-centric, and Linux users may need to infer or research their own approaches.
Recommendations
  • Provide detailed Linux-specific examples for application warm-up (e.g., how to configure WEBSITE_WARMUP_PATH, with sample settings and use cases).
  • Include Linux/macOS equivalents for logging strategies, such as stdout/stderr logging, integration with syslog, or other common Linux logging patterns.
  • When referencing Windows tools (like IIS Application Initialization), offer parallel guidance for Linux (e.g., Nginx/Apache warm-up strategies, startup probes).
  • Ensure that Linux features are described with equal depth and clarity as Windows features, including troubleshooting steps and configuration details.
  • Present examples for both Windows and Linux side-by-side, or alternate which platform is shown first.
GitHub Create Pull Request
App Service Enable Diagnostic Logging ...n/articles/app-service/troubleshoot-diagnostic-logs.md
Medium 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 exhibits a moderate Windows bias. Logging features such as web server logging, detailed error messages, and failed request tracing are described exclusively for Windows, with no Linux equivalents or alternatives mentioned. Windows-specific tools (e.g., Log Parser) and file paths are referenced, while Linux instructions are less detailed and appear after Windows sections. Some features, like blob storage logging for application logs, are noted as unavailable for non-.NET stacks, but no Linux workarounds or parity suggestions are provided.
Recommendations
  • Add explicit Linux equivalents or alternatives for web server logging, detailed error messages, and failed request tracing, or clarify their absence and suggest third-party solutions.
  • Provide Linux-first or side-by-side examples for all logging features, including file paths and access methods.
  • Mention Linux-compatible tools for reading and parsing logs, not just Windows-centric ones like Log Parser.
  • Clarify feature parity and limitations for Linux and containerized environments, and suggest best practices for those platforms.
  • Ensure that instructions for enabling and accessing logs are equally detailed for Linux and Windows.
GitHub Create Pull Request
App Service Troubleshoot Performance Degradation ...es/app-service/troubleshoot-performance-degradation.md
Medium 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 several Windows-centric biases. Diagnostic sections reference IIS, W3C log formats, and Windows-specific tools like Procdump and PowerShell, with no mention of Linux equivalents. The Kudu console is described as supporting PowerShell and DOS commands, but not Bash or Linux shells. Links and examples for enabling .NET Profiler and auto-heal reference Windows-specific resources. There are no explicit Linux/macOS troubleshooting examples, nor are Linux tools or workflows discussed.
Recommendations
  • Include Linux-specific instructions and examples for diagnostics, such as using Bash in Kudu, Linux log formats, and troubleshooting tools (e.g., using strace, lsof, or Linux-native dump tools).
  • Clarify which features and tools are available for Linux-based App Service plans, and provide links to Linux documentation where applicable.
  • Add parity for restart and management examples, such as using Azure CLI (cross-platform) instead of only PowerShell.
  • Reference Linux/macOS equivalents for memory dumps and profiling, such as dotnet-trace, dotnet-dump, or gcore.
  • Explicitly state when a feature or tool is Windows-only, and offer alternatives for Linux users.
GitHub Create Pull Request
App Service Tutorial: Access Azure databases with managed identity ...les/app-service/tutorial-connect-msi-azure-database.md
Medium 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 moderate Windows bias, especially in the 'Set up your dev environment' section. Windows tools (Visual Studio for Windows, Azure PowerShell) are presented first and in greater detail, while Linux/macOS alternatives (Visual Studio for Mac, Azure CLI) are described as less integrated or as workarounds. PowerShell is included as a primary authentication method, and Visual Studio for Mac is explicitly noted as lacking integration. The overall flow and examples prioritize Windows-centric development environments and tools.
Recommendations
  • Present Linux/macOS development options (Azure CLI, VS Code, etc.) before or alongside Windows tools, not after.
  • Expand instructions for Linux/macOS environments, including common IDEs (e.g., JetBrains Rider, Eclipse, PyCharm) and their integration with Azure authentication.
  • Provide explicit examples for signing in and authenticating on Linux/macOS, including shell commands and troubleshooting tips.
  • Clarify that all code samples and CLI commands work cross-platform unless otherwise noted.
  • Add parity for PowerShell by including Bash/Zsh equivalents where relevant.
  • Avoid language that implies Windows is the default or preferred platform.
GitHub Create Pull Request
App Service Tutorial: Build and Run a Custom Image in Azure App Service ...main/articles/app-service/tutorial-custom-container.md
Medium 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 demonstrates a notable Windows bias in the 'container-windows' pivot. Windows examples are presented first, with detailed step-by-step instructions using Windows-specific tools (Visual Studio, Windows Explorer, PowerShell scripts). There is heavy reliance on Windows patterns and tools, such as installing fonts via Windows Explorer and using InstallFont.ps1. Linux equivalents for these steps are not provided, and the Windows pivot is much more prescriptive and tool-dependent than the Linux pivot, which is more generic and CLI-focused.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific steps, especially for tasks like installing fonts, building images, and running containers.
  • Include examples using cross-platform tools (e.g., VS Code, Docker CLI) in both pivots.
  • Avoid assuming Visual Studio or Windows Explorer as the default environment; mention alternatives like VS Code and file managers on Linux/macOS.
  • Where PowerShell scripts are used, offer Bash or shell script alternatives for Linux.
  • Ensure parity in detail and guidance between Windows and Linux pivots, so Linux users are not left with generic instructions while Windows users get step-by-step guidance.
GitHub Create Pull Request
App Service Securely connect .NET apps to Azure SQL Database using Managed Identity ...icles/app-service/tutorial-connect-msi-sql-database.md
Medium 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 demonstrates a moderate Windows bias. Windows/PowerShell tools and workflows (Visual Studio for Windows, PowerShell, SQLCMD) are presented first and in greater detail. Linux/macOS alternatives (Azure CLI, Visual Studio Code) are mentioned, but not as thoroughly, and some critical steps (like granting SQL permissions) are shown only with Windows/PowerShell tools. There are no explicit Linux/macOS SQL client examples for database permission tasks.
Recommendations
  • Provide equivalent Linux/macOS examples for database permission steps, such as using sqlcmd on Linux, Azure Data Studio, or other cross-platform SQL clients.
  • Present cross-platform tools (Azure CLI, Visual Studio Code) before or alongside Windows-specific tools to avoid Windows-first ordering.
  • Include explicit instructions for running sqlcmd or database permission commands on Linux/macOS, including installation and authentication steps.
  • Clarify that PowerShell and Visual Studio for Windows steps are not required and offer alternatives for non-Windows environments.
  • Ensure parity in detail and screenshots for Linux/macOS workflows.
GitHub Create Pull Request
App Service Customize Sign-ins and Sign-outs ...vice/configure-authentication-customize-sign-in-out.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally cross-platform, but the 'Server level (Windows apps only)' section provides detailed instructions for Windows/IIS (web.config) authorization, with no equivalent for Linux. Windows-specific tools (Kudu, web.config) are mentioned exclusively, and Linux alternatives are not discussed. The section is labeled as Windows-only, but Linux users are left without guidance for similar tasks.
Recommendations
  • Add a parallel section for Linux apps, describing how to implement server-level authorization (e.g., using middleware in Node.js, .htaccess for Apache, or NGINX config).
  • Explicitly mention Linux alternatives to Kudu (such as SSH, FTP, or Azure CLI for file management).
  • Provide code samples for Linux-based app stacks (Node.js, Python, PHP) showing how to restrict access at the application level.
  • Clarify in the 'Server level' section that Linux users should use application-level authorization and link to relevant guides.
GitHub Create Pull Request
App Service Configure Sign in with Apple (Preview) ...app-service/configure-authentication-provider-apple.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and Azure CLI management experiences before mentioning their limitations, and by providing only a C#/.NET example for JWT signing using Microsoft.IdentityModel.Tokens. There are no Linux-specific or cross-platform command-line examples, nor are alternative JWT signing methods (such as using OpenSSL, Python, or Node.js) provided. The documentation does not mention Linux tools or workflows, and does not offer parity for developers working outside the Windows/.NET ecosystem.
Recommendations
  • Add Linux-friendly examples for generating and signing JWTs, such as using OpenSSL, Python (PyJWT), or Node.js (jsonwebtoken).
  • Include CLI commands that work on both Windows and Linux, or explicitly mention platform differences.
  • Reference Linux management tools or workflows where appropriate, such as Bash scripts or Linux text editors for handling the .p8 file.
  • Provide parity in code samples by including at least one non-.NET example for JWT creation and signing.
  • Clarify any platform-specific limitations or requirements, and suggest alternatives for Linux users.
GitHub Create Pull Request
← Previous Page 7 of 10 Next →