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 1426-1450 of 2121 flagged pages
App Service Quickstart: Use Terraform to configure an Azure App Service Environment v3 ...articles/app-service/environment/creation-terraform.md
Medium Priority View Details →
Scanned: 2026-01-14 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 instructions for verifying results, but the PowerShell section is given equal prominence despite being Windows-specific. There are no explicit Linux/macOS shell examples (e.g., bash), and PowerShell is not cross-platform by default for many users. The CLI examples use shell variable syntax compatible with bash, but do not clarify Linux/macOS usage or differences. No Linux-specific troubleshooting or tool references are present.
Recommendations
  • Clarify that Azure CLI examples are compatible with bash on Linux/macOS and provide explicit bash/zsh instructions if needed.
  • Note that Azure PowerShell is primarily for Windows, and suggest cross-platform alternatives (e.g., Azure CLI) for Linux/macOS users.
  • Add troubleshooting notes or links relevant to Linux/macOS environments.
  • If PowerShell Core is supported on Linux/macOS, mention this and provide installation guidance.
  • Ensure that any referenced scripts or commands are tested on Linux/macOS and document any differences.
GitHub Create Pull Request
App Service Deploy Files ...zure-docs/blob/main/articles/app-service/deploy-zip.md
Medium Priority View Details →
Scanned: 2026-01-14 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 Windows bias in several ways: the Kudu ZIP deploy UI is only available for Windows (with Linux users directed to alternatives), Windows paths and conventions are mentioned first and more frequently, and some instructions (such as Kudu UI steps and default paths) are Windows-centric. There is a lack of Linux-specific examples or screenshots, and Linux alternatives are mentioned only as side notes. PowerShell examples are included, but Linux shell equivalents are not shown for those commands.
Recommendations
  • Provide explicit Linux/macOS instructions and screenshots where the UI or workflow differs.
  • List Linux paths and conventions alongside Windows, not after or as a note.
  • Offer Linux shell equivalents for PowerShell commands (e.g., Bash scripts for deployment).
  • Clearly indicate which features/tools are Windows-only and provide step-by-step Linux alternatives in the main flow, not just as a note.
  • Consider reordering sections so Linux and Windows parity is clear, or use side-by-side tabs for OS-specific instructions.
GitHub Create Pull Request
App Service Geo-Distributed Scale ...-service-app-service-environment-geo-distributed-scale.md
Medium Priority View Details →
Scanned: 2026-01-14 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 notable Windows bias by exclusively providing PowerShell-based examples for configuring Azure Traffic Manager and App Service Environments. No equivalent instructions or code samples are given for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). The only automation tooling referenced is PowerShell, and the workflow assumes familiarity with Windows-centric tools and patterns. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer platform-native tools.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, ensuring Linux/macOS users can follow along without installing PowerShell.
  • Explicitly mention cross-platform alternatives (Azure CLI, REST API, ARM templates) and link to their documentation.
  • Where screenshots or tool references are shown (e.g., DNS lookup), clarify that the steps are platform-agnostic or provide Linux/macOS command examples (e.g., using dig or nslookup).
  • Reorder or parallelize examples so that Windows and Linux/macOS instructions are presented together, rather than Windows-first.
GitHub Create Pull Request
App Service Getting started with Azure App Service ...docs/blob/main/articles/app-service/getting-started.md
Medium Priority View Details →
Scanned: 2026-01-14 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, particularly in the .NET and Python sections. Windows tools (Visual Studio, Azure PowerShell) are listed first or exclusively, and Windows-centric workflows are emphasized. Linux alternatives (CLI, VS Code, Azure CLI) are present but often appear after Windows options or are less detailed. Some sections (e.g., custom containers) do provide Linux-specific guidance, but overall, Windows users are prioritized in example order and tool recommendations.
Recommendations
  • Ensure Linux and macOS examples are presented alongside Windows examples, ideally with equal prominence.
  • List cross-platform tools (VS Code, CLI, Azure CLI) before Windows-only tools (Visual Studio, PowerShell) to avoid implicit prioritization.
  • Expand Linux-specific instructions, especially for .NET and Python, to match the detail provided for Windows workflows.
  • Add explicit tabs or pivots for Linux/macOS where currently only Windows is shown.
  • Review 'Next step' actions to include non-Windows starting points (e.g., deploy via CLI or VS Code).
GitHub Create Pull Request
App Service [Portal](#tab/azure-portal) ...torial-dotnet-storage-managed-identity/introduction.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents Windows-centric tools (PowerShell, Visual Studio) and patterns before Linux/macOS equivalents. PowerShell examples are given equal prominence to Azure CLI, and Visual Studio is referenced as the default publishing tool. The portal instructions assume familiarity with Windows UI conventions. There are no explicit Linux/macOS examples or notes about platform differences.
Recommendations
  • Add explicit notes or sections for Linux/macOS users, especially regarding publishing workflows and managed identity enablement outside Visual Studio.
  • Clarify that Azure CLI commands work cross-platform and are recommended for Linux/macOS users.
  • Provide examples using VS Code or other cross-platform editors for app publishing and identity enablement.
  • Avoid assuming Visual Studio as the default tool; mention alternatives for Linux/macOS.
  • Consider listing Azure CLI examples before PowerShell, as CLI is more universal.
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-14 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 provides multiple examples for Windows environments, including both code and container tabs. In contrast, Linux sections only mention *.sh* scripts and provide fewer examples, omitting common Linux file types (e.g., *.py*, *.pl*) and tools. Windows examples and tools are presented first and more comprehensively.
Recommendations
  • Expand Linux sections to list other common script types (e.g., *.py*, *.pl*, *.rb*, *.php*) and clarify which runtimes are pre-installed.
  • Provide parity in examples: for each Windows example (e.g., PowerShell, Node.js, Java), offer equivalent Linux examples.
  • List Linux tools and runtimes explicitly, similar to the Windows section.
  • Consider reordering or presenting Windows and Linux examples side-by-side for equal prominence.
GitHub Create Pull Request
App Service Monitor Azure App Service .../blob/main/articles/app-service/monitor-app-service.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation mentions querying Azure activity logs using the Azure portal, PowerShell, REST API, or CLI, listing PowerShell before CLI and not providing any Linux-specific examples or tools. There is also a reference to Visual Studio integration for Application Insights, which is a Windows-centric tool, without mention of equivalent Linux/macOS development environments. No explicit Linux/macOS examples or parity guidance are provided, and Windows tools/patterns are mentioned first or exclusively in relevant sections.
Recommendations
  • Explicitly mention and provide examples for querying activity logs using Azure CLI and Bash, especially for Linux/macOS users.
  • Include references to cross-platform development tools (such as VS Code) alongside Visual Studio.
  • Ensure that any PowerShell examples are paired with Azure CLI or Bash equivalents.
  • Add notes or sections clarifying Linux/macOS compatibility for all monitoring features.
  • Where possible, provide screenshots or walkthroughs for Linux/macOS environments in addition to Windows.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions and examples for per-app scaling using Azure PowerShell cmdlets, which are primarily associated with Windows environments. There are no equivalent examples or guidance for Linux/macOS users, such as using Azure CLI or Bash scripts. The exclusive use of PowerShell and lack of cross-platform tooling creates friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, demonstrating how to enable per-app scaling and configure number of workers using az commands.
  • Include Bash script examples where appropriate, especially for app-level configuration.
  • Explicitly mention that PowerShell Core is cross-platform if that is intended, or clarify any Windows-specific requirements.
  • Reorder sections or provide parallel examples so that Linux/macOS users are not required to translate PowerShell commands themselves.
GitHub Create Pull Request
App Service Networking Features .../blob/main/articles/app-service/networking-features.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation shows evidence of Windows bias primarily in the section describing Hybrid Connections, which requires installation of Hybrid Connection Manager on 'Windows Server 2012 or newer.' There is no mention of Linux or macOS support or alternatives for this critical connectivity feature. Additionally, the Gateway-required virtual network integration is explicitly limited to 'App Service Windows plans.' No Linux equivalents or workarounds are discussed, and Windows terminology appears first or exclusively in these sections.
Recommendations
  • Explicitly state whether Hybrid Connection Manager is available for Linux/macOS, and if not, provide alternative solutions or workarounds for non-Windows environments.
  • For Gateway-required virtual network integration, clarify Linux support status and suggest alternatives for Linux App Service plans.
  • Where features are Windows-only, add clear notes and links to Linux-compatible networking features.
  • Provide parity in examples and instructions for Linux/macOS users, especially for critical deployment and connectivity scenarios.
  • Consider adding a comparison table indicating OS support for each networking feature.
GitHub Create Pull Request
App Service Azure App Service Plans ...ob/main/articles/app-service/overview-hosting-plans.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Managed Instance on Azure App Service' section, which is exclusively for Windows web apps and highlights Windows-specific tools and patterns (PowerShell, RDP, IIS, COM, MSI, registry). There are no equivalent Linux features or examples provided, and the section is presented as a major capability without Linux parity. Additionally, the link to App Service plan details points to a Windows-specific pricing page, and the overall documentation tends to mention Windows features and tools before Linux equivalents.
Recommendations
  • Add equivalent Linux hosting options and document their features, limitations, and use cases.
  • Provide Linux-specific examples and tooling (e.g., Bash scripts, SSH access, Linux middleware setup) where Windows tools are mentioned.
  • Ensure pricing and feature comparison links include both Windows and Linux plans equally.
  • Clearly indicate when features are Windows-only and suggest Linux alternatives or workarounds.
  • Balance the order of presentation so Linux is not consistently secondary to Windows.
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-14 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 shown alongside CLI without clarifying platform differences. The outbound IPv6 support section explicitly states that outbound IPv6 is only available for Windows apps, with Linux apps limited to IPv4. There are no Linux-specific command examples (e.g., bash scripts, Linux-native tools) for tasks like querying IPs, and PowerShell is referenced without noting its limited availability on Linux/macOS. The documentation generally presents Windows capabilities first or exclusively in some areas.
Recommendations
  • Clarify platform compatibility for PowerShell commands and recommend Azure CLI as the cross-platform default.
  • Add explicit Linux/macOS command examples where relevant (e.g., using curl, dig, or jq for JSON parsing).
  • In the outbound IPv6 section, provide a clear roadmap or alternatives for Linux users, or link to updates on Linux support.
  • When listing commands, present Azure CLI examples first, as it is cross-platform, and note PowerShell as an option for Windows users.
  • Explicitly state any feature limitations for Linux apps at the beginning of relevant sections.
GitHub Create Pull Request
App Service Managed Identities ...main/articles/app-service/overview-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, ARM templates, and the Azure portal. While Azure CLI and ARM templates are cross-platform, there is a notable emphasis on Azure PowerShell, which is traditionally associated with Windows environments. In several sections, PowerShell examples are given their own tabs, and in some cases, PowerShell is the only scripting language shown for certain tasks (e.g., retrieving tokens). Additionally, PowerShell is referenced for tasks that are not supported in the CLI (e.g., user-assigned identity for Functions). The ordering of examples often places PowerShell before CLI or other cross-platform tools, and there are no explicit Linux/macOS shell (bash) examples, nor is there mention of Linux-specific tools or workflows.
Recommendations
  • Add bash or shell script examples for tasks currently only shown in PowerShell, especially for token retrieval and identity management.
  • Ensure that Azure CLI examples are always present and, where possible, shown before or alongside PowerShell examples.
  • Clarify that Azure CLI is fully cross-platform and recommend it as the primary automation tool for Linux/macOS users.
  • Where PowerShell is required, note that PowerShell Core is available cross-platform, and provide installation guidance for non-Windows users.
  • Consider including explicit Linux/macOS workflow notes or troubleshooting tips where platform differences may arise.
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-14 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-specific pivots (Visual Studio, PowerShell, CLI) before Linux equivalents and includes multiple Windows-only tools (Visual Studio, PowerShell) without clear Linux alternatives. Linux pivots are present but less prominent, and there is no evidence of missing Linux examples, but the ordering and tool selection favor Windows users.
Recommendations
  • Ensure Linux pivots (e.g., VS Code, Azure CLI) are presented with equal prominence and ordering as Windows pivots.
  • Add explicit Linux CLI and shell examples where only PowerShell or Windows CLI are shown.
  • Include Linux-native tooling and workflows (e.g., Bash, Docker Compose) alongside Windows tools.
  • Consider grouping pivots by platform (Windows/Linux) rather than by tool to avoid implicit prioritization.
  • Add a summary table or section comparing Windows and Linux workflows for parity.
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-14 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 paths (e.g., D:\home), tools (Web Deploy/MSDeploy), and configuration patterns are frequently mentioned, often before or in greater detail than their Linux equivalents. Several environment variables and examples reference Windows-only features or tools, such as IIS, applicationHost.config, and machineKey, with less emphasis or explanation for Linux alternatives. Some sections (e.g., TLS/SSL, logging, deployment) provide more detail for Windows scenarios, and Windows-centric terminology (e.g., .bat files, %HOME%) is used throughout. Linux-specific settings are present but often less detailed or appear after Windows instructions.
Recommendations
  • Ensure Linux and macOS equivalents are described with equal detail and clarity.
  • Present Linux examples and paths (e.g., /home) alongside Windows ones, not after or as an aside.
  • Add explicit Linux/macOS tooling references where Windows tools (e.g., Web Deploy/MSDeploy) are mentioned.
  • Where environment variables are Windows-only, clearly mark them as such and provide Linux alternatives if available.
  • Balance documentation structure so Linux sections are not subordinate or less detailed than Windows sections.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific features (e.g., IIS Application Initialization Module) and tools are described in detail, with Linux equivalents mentioned briefly or as afterthoughts. Windows examples and terminology (such as 'Windows Worker', IIS modules, .NET Core stdout logging) are presented first or exclusively, while Linux alternatives (like WEBSITE_WARMUP_PATH) lack detailed guidance or examples. Some troubleshooting and logging strategies are Windows-centric, with limited Linux parity.
Recommendations
  • Provide detailed Linux-specific examples for application initialization and warm-up, including step-by-step configuration using WEBSITE_WARMUP_PATH.
  • Include Linux-first or parallel examples for logging start-up failures, such as configuring stdout logging or alternative logging mechanisms in Linux containers.
  • Balance the coverage of Windows and Linux features/tools, ensuring Linux features are described with equal depth and clarity.
  • Where Windows-specific modules (e.g., IIS Application Initialization) are referenced, offer Linux-native alternatives (such as Nginx/Apache config or startup scripts) and link to relevant documentation.
  • Add troubleshooting and testing scenarios explicitly for Linux environments, including common failure modes and diagnostic techniques.
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-14 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 exhibits a moderate Windows bias, primarily by prioritizing Visual Studio (Windows-only) and PowerShell workflows, providing more detailed steps and screenshots for Windows tools, and recommending PowerShell for Windows hosting. While Linux options are available via CLI and VS Code, some sections (especially PowerShell) lack Linux equivalents or direct instructions, and Windows-centric tools are often mentioned first or exclusively.
Recommendations
  • Ensure all PowerShell instructions have equivalent Bash/Linux shell examples, especially for deployment and packaging steps.
  • Add explicit Linux/macOS instructions for tasks like zipping and publishing (e.g., using 'zip' instead of 'Compress-Archive').
  • Balance screenshots and step-by-step guides between Windows (Visual Studio) and cross-platform tools (VS Code, CLI).
  • Avoid language such as 'We recommend PowerShell for Windows hosting' without offering Linux alternatives; clarify when a tool is Windows-only and provide Linux guidance.
  • In portal instructions, clarify any OS-specific limitations (e.g., GitHub Actions deployment on Linux) and offer workarounds or links to Linux-specific guides.
  • Where possible, present cross-platform options first or in parallel, rather than defaulting to Windows-first presentation.
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
Medium Priority View Details →
Scanned: 2026-01-14 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 for required NuGet packages using both the .NET Core CLI and the Visual Studio Package Manager Console (PowerShell), but the Visual Studio/PowerShell method is listed second. There are no explicit Linux/macOS-specific instructions or examples, and the only IDE mentioned is Visual Studio (Windows-centric). The .NET Core CLI is cross-platform, but the lack of explicit mention of Linux/macOS environments or alternative editors may create friction for non-Windows users.
Recommendations
  • Explicitly state that the .NET Core CLI commands work on Linux and macOS, and provide example terminal commands for those platforms.
  • Mention and provide instructions for using alternative editors (e.g., VS Code) on Linux/macOS.
  • Add a note clarifying that Visual Studio Package Manager Console is Windows-only, and suggest equivalent workflows for Linux/macOS users.
  • Consider listing cross-platform instructions first to emphasize parity.
GitHub Create Pull Request
App Service Enable Diagnostic Logging ...n/articles/app-service/troubleshoot-diagnostic-logs.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing more detailed instructions and features for Windows-based App Service apps. Windows-specific logging types (web server logging, detailed error messages, failed request tracing) are described in detail, while Linux equivalents are either missing or only briefly mentioned. Windows tools and file paths are referenced, and examples for Windows appear before Linux throughout the page. Some advanced logging features are unavailable or undocumented for Linux, and tooling recommendations (e.g., Log Parser) are Windows-centric.
Recommendations
  • Add equivalent logging instructions and examples for Linux-based App Service apps, especially for web server logging, detailed error messages, and failed request tracing.
  • Clearly indicate which features are unavailable on Linux, and suggest alternative approaches or tools for Linux users.
  • Provide Linux-first or side-by-side examples for common tasks, including file paths, log formats, and access methods.
  • Include recommendations for cross-platform or Linux-native log analysis tools, not just Windows-specific ones.
  • Ensure that all code and CLI examples are tested and applicable for Linux environments, or provide Linux-specific alternatives where necessary.
GitHub Create Pull Request
App Service Tutorial: Connect a web app to SQL Database on behalf of the user ...utorial-connect-app-access-sql-database-as-user-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-14 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 demonstrates some Windows bias, particularly in its reliance on Windows-centric tools (SQL Server Management Studio, references to Integrated Windows authentication), and in the order and prominence of examples. While Azure CLI is used for most automation steps (which is cross-platform), database management and user addition instructions reference Windows-only tools first (SSMS, sqlcmd), and do not provide explicit Linux/macOS alternatives or parity in tooling. The code publishing section mentions Visual Studio and Git Bash, but does not provide parity for Linux/macOS IDEs or workflows. Debugging guidance is also Windows-centric, referencing Visual Studio remote debugging.
Recommendations
  • Include explicit instructions and examples for Linux/macOS users, such as using Azure Data Studio or cross-platform sqlcmd for database management.
  • When referencing tools like SSMS, also mention Azure Data Studio and provide links/examples for installation and usage on Linux/macOS.
  • Provide code publishing instructions for Linux/macOS environments, such as using VS Code, JetBrains Rider, or command-line dotnet CLI.
  • When listing database connection and debugging options, include Linux/macOS compatible workflows and tools.
  • Avoid mentioning Windows tools first; present cross-platform options equally or prioritize platform-neutral solutions.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, particularly in the 'Set up your dev environment' section, where Visual Studio for Windows is presented first and in more detail than alternatives. Windows-specific tools (Visual Studio, Azure PowerShell) are mentioned before their Linux/macOS equivalents, and PowerShell is given a dedicated section. While Linux/macOS options are present, they are often described as workarounds (e.g., using Azure CLI for Visual Studio for Mac), and the flow prioritizes Windows-centric development environments.
Recommendations
  • Reorder the 'Set up your dev environment' section to present cross-platform tools (Azure CLI, Visual Studio Code) before Windows-only tools.
  • Provide equal detail and prominence for Linux/macOS workflows, including explicit instructions for JetBrains Rider or other popular cross-platform IDEs.
  • Avoid language that frames Linux/macOS support as a workaround (e.g., 'Visual Studio for Mac is *not* integrated...'), and instead present it as a first-class workflow.
  • Include troubleshooting tips or notes specific to Linux/macOS environments where relevant.
  • Where PowerShell is mentioned, also provide Bash/zsh equivalents if possible.
GitHub Create Pull Request
App Service Troubleshoot Performance Degradation ...es/app-service/troubleshoot-performance-degradation.md
Medium Priority View Details →
Scanned: 2026-01-14 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 moderate Windows bias. Several troubleshooting tools and examples are Windows-centric, such as references to IIS logging, PowerShell, SysInternals Procdump, and Windows-specific site extensions. Kudu console instructions mention PowerShell and DOS commands but omit Linux shell equivalents. The Application Insights Profiler section links only to Windows-specific instructions. There are no explicit Linux or macOS examples or guidance for equivalent tasks, and Windows tools are mentioned first or exclusively in key sections.
Recommendations
  • Add Linux/macOS-specific instructions and examples for diagnostic logging, troubleshooting, and performance profiling.
  • Include references to Bash, SSH, and Linux command-line usage in Kudu console, alongside PowerShell/DOS.
  • Provide parity for tools like Procdump by mentioning Linux alternatives (e.g., gcore, lsof, strace) and how to use them in App Service on Linux.
  • Link to Application Insights Profiler documentation for Linux-based App Service apps, if available.
  • Clarify which features and tools are available on App Service for Linux vs. Windows, and note any differences.
  • Ensure that examples and tool references are presented for both platforms, or at least alternate between them.
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-14 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 moderate Windows bias. Windows/PowerShell tools and Visual Studio for Windows are presented first and in more detail, while Linux/macOS equivalents (such as Bash, Azure CLI, and Visual Studio Code) are mentioned but receive less attention. Critical steps, like granting database permissions, rely on PowerShell/sqlcmd without explicit Linux/macOS alternatives. Visual Studio for Windows is prioritized over cross-platform editors, and publishing instructions are Windows-centric.
Recommendations
  • Provide explicit Linux/macOS alternatives for all PowerShell/sqlcmd steps, such as using sqlcmd in Bash or Azure Data Studio.
  • Add step-by-step instructions for Visual Studio Code and cross-platform publishing workflows (e.g., Azure CLI, GitHub Actions).
  • Ensure all CLI commands are shown in a cross-platform way, and avoid assuming Visual Studio for Windows as the default.
  • Include notes or tabs for Linux/macOS users wherever Windows-specific tools or UI steps are described.
  • Present cross-platform examples before or alongside Windows-specific ones.
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-14 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 notable Windows bias in the 'container-windows' section. Windows-specific tools (Visual Studio, Windows Explorer), patterns (right-click context menus, font installation via GUI), and scripting (PowerShell .ps1 scripts) are used exclusively and described in detail. There are no equivalent Linux/macOS instructions or examples for building, testing, or deploying custom containers with OS-level integration (such as font installation). The Windows section is presented first, and Linux alternatives for tasks like font installation, project setup, and container orchestration are missing. The Linux section is more CLI-focused and general, but does not address scenarios requiring OS customization (like installing fonts) or provide parity for the Windows-specific workflow.
Recommendations
  • Add Linux/macOS equivalents for all major steps in the Windows workflow, including project setup, font installation, and container orchestration.
  • Provide examples using cross-platform tools (e.g., VS Code, CLI commands) instead of or alongside Windows-only tools like Visual Studio and Windows Explorer.
  • Include Linux-specific instructions for installing fonts in containers (e.g., using apt-get or fontconfig in Dockerfile).
  • Offer PowerShell script alternatives in Bash or shell scripts for Linux/macOS users.
  • Ensure that both Windows and Linux workflows are presented with equal detail and clarity, and consider presenting both pivots side-by-side or in parallel.
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-13 00:00
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 and examples for Windows (IIS/web.config) authorization, with no equivalent for Linux. Windows tools (Kudu, web.config) are mentioned exclusively, and the Windows method is described before alternatives. Linux users are told they cannot use this method, but no Linux-specific guidance or parity is offered.
Recommendations
  • Add equivalent Linux guidance for server-level authorization, such as using .htaccess for Apache, NGINX config, or middleware in common frameworks.
  • Explicitly mention how Linux users can achieve similar authorization goals, possibly with code samples or links to relevant documentation.
  • Reorder sections or clarify that Windows/IIS methods are platform-specific and not the primary/default approach.
  • Where Windows tools are referenced (Kudu, web.config), provide Linux alternatives or note their absence.
GitHub Create Pull Request
App Service Secure Your Domain with TLS/SSL ...ob/main/articles/app-service/configure-ssl-bindings.md
Medium Priority View Details →
Scanned: 2026-01-13 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 moderate Windows bias in its automation section, where only PowerShell and Azure CLI scripts are referenced, with PowerShell examples shown explicitly and Azure CLI only linked. No Linux/macOS-specific shell examples (e.g., Bash) are provided, and the PowerShell script is highlighted, suggesting a Windows-first approach. The main workflow is portal-based and cross-platform, but scripting guidance is skewed toward Windows users.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users alongside PowerShell.
  • Show Azure CLI examples directly in the documentation, not just as a link.
  • Ensure that scripting sections do not prioritize Windows tools or patterns over cross-platform alternatives.
  • Clarify that all portal-based steps are platform-agnostic, and highlight any platform-specific differences if they exist.
GitHub Create Pull Request
← Previous Page 58 of 85 Next →