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 301-325 of 2121 flagged pages
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/networking-features.md .../blob/main/articles/app-service/networking-features.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias primarily 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. There are no Linux-specific examples, tools, or instructions throughout the page, and Windows-specific limitations (e.g., Gateway-required VNet integration only for Windows plans) are described before alternatives. The documentation does not provide parity for Linux users in terms of guidance or tooling.
Recommendations
  • Explicitly state whether Hybrid Connection Manager is available for Linux, and provide installation/configuration instructions for Linux if supported.
  • For features limited to Windows (e.g., Gateway-required VNet integration), clearly indicate Linux alternatives or workarounds.
  • Include Linux-specific examples, screenshots, and CLI instructions where relevant.
  • Add a comparison table or section summarizing feature parity and differences between Windows and Linux App Service plans.
  • Ensure that documentation for networking features is platform-neutral where possible, or clearly highlights platform-specific differences.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-authentication-authorization.md ...s/app-service/overview-authentication-authorization.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows mild Windows bias. The architecture section describes Windows (IIS module) before Linux/container (Ambassador pattern), and references IIS modules as the default for non-container deployments. There are no Linux-specific command-line examples or explicit parity in troubleshooting/logging sections. The only CLI examples use Azure CLI (az rest), which is cross-platform, but there are no references to Linux-specific tools or troubleshooting patterns. No PowerShell examples are present, but Windows terminology and patterns are mentioned first.
Recommendations
  • Present Linux/container architecture before or alongside Windows/IIS module architecture to avoid Windows-first ordering.
  • Include Linux-specific troubleshooting/logging guidance (e.g., mention how to access logs in Linux containers, reference Linux tools like journalctl or docker logs).
  • Add explicit examples or notes for Linux users, such as how to configure authentication in Linux containers, or how to inspect authentication headers in Linux environments.
  • Reference Linux-native tools or patterns where relevant, such as curl for testing endpoints, or mention how authentication behaves in Linux-based hosting environments.
  • Ensure that any references to Windows/IIS modules are balanced with equivalent Linux/container information.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-inbound-outbound-ips.md .../articles/app-service/overview-inbound-outbound-ips.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page shows a moderate Windows bias. PowerShell examples are provided for querying outbound IP addresses, but no equivalent bash or Linux shell examples are given. Outbound IPv6 support is explicitly stated as available only for Windows apps, with Linux apps limited to IPv4. Windows/PowerShell tooling is mentioned before Linux alternatives, and there is no mention of Linux-specific troubleshooting or command-line patterns beyond Azure CLI. The documentation does not provide parity in examples or features for Linux users.
Recommendations
  • Add bash/Linux shell examples for querying outbound IP addresses (e.g., using curl, jq, or az CLI in bash).
  • Clarify feature parity for outbound IPv6 support and provide roadmap or alternatives for Linux apps.
  • Where PowerShell is used, also provide equivalent bash/Linux commands, especially for Azure CLI usage.
  • Explicitly mention any limitations or differences for Linux-hosted apps in relevant sections.
  • Include troubleshooting steps or examples for Linux environments (e.g., using dig instead of nslookup, which is more common on Linux).
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/operating-system-functionality.md ...articles/app-service/operating-system-functionality.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows-specific concepts, terminology, and examples. Windows environment variables (%SystemDrive%, %ResourceDrive%, %HOME%), Windows file paths (d:\, c:\), IIS, ASP.NET, COM components, PowerShell, and Windows registry access are described in detail, while Linux equivalents are either missing or only briefly mentioned. Linux is referenced only in a note, with no substantive examples or parity in explanations. Diagnostic logging and registry sections are Windows-centric, and tools like Kudu and Web Deploy are described only in a Windows context.
Recommendations
  • Add equivalent Linux examples and terminology throughout, such as $HOME, /tmp, and Linux filesystem paths.
  • Describe how file access, network access, and process execution work for Linux-based App Service apps, including container specifics.
  • Include Linux-specific diagnostic logging options and clarify which Windows-only features (like ETW, registry) are not available or have Linux alternatives.
  • Provide parity in troubleshooting and deployment examples, e.g., using SCP, rsync, or Linux CLI tools alongside Web Deploy and PowerShell.
  • Explicitly state differences and similarities between Windows and Linux App Service environments in each section, not just in a single note.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-managed-identity.md ...main/articles/app-service/overview-managed-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is heavily featured as a primary automation tool, with detailed examples and scripts, while Linux shell equivalents (e.g., Bash) are not provided. The use of Azure PowerShell is prominent, and instructions for App Service management via PowerShell are given even when not supported for all scenarios. Windows-centric tools and patterns (PowerShell, Azure PowerShell modules) are mentioned and exemplified before or instead of Linux-native alternatives. No Bash, shell, or Linux-specific command-line examples are present, and there is no mention of Linux-specific considerations or tooling.
Recommendations
  • Add Bash or shell script examples alongside PowerShell for all CLI operations, especially for token retrieval and identity management.
  • Explicitly mention Linux compatibility and provide instructions for Linux environments where relevant (e.g., using curl or wget for REST endpoint access).
  • Balance the order of examples so that CLI and platform-neutral tools (Azure CLI, REST API) are presented before PowerShell.
  • Include troubleshooting or notes for Linux users, such as environment variable access and file system differences.
  • Where PowerShell is not supported (e.g., user-assigned identity for App Service), clarify Linux alternatives or workarounds.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-private-endpoint.md ...main/articles/app-service/overview-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. Windows is mentioned before Linux in the important note about supported platforms, and PowerShell is listed as a primary method for creating private endpoints alongside the Azure portal and CLI. The related content section lists Azure PowerShell before ARM templates and Terraform, and there is no explicit Linux shell example or mention of Linux-specific tooling. The documentation refers to Windows-centric tools and patterns (e.g., PowerShell, Azure portal) and does not provide parity for Linux users in terms of example commands or troubleshooting steps.
Recommendations
  • Ensure that Linux is mentioned equally and/or first when listing supported platforms.
  • Provide explicit Bash or Linux shell examples alongside PowerShell examples.
  • Include references to Linux-native tools (e.g., Bash, curl, dig) for DNS and network troubleshooting.
  • List Azure CLI and ARM template methods before PowerShell in related content to reflect cross-platform parity.
  • Add troubleshooting and configuration steps relevant to Linux environments, such as modifying /etc/hosts or using Linux DNS utilities.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-vnet-integration.md ...main/articles/app-service/overview-vnet-integration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. Windows-specific features and limitations (such as Windows Containers IP calculations and Windows Server Active Directory domain join) are described in detail, while Linux-specific scenarios are mentioned only briefly (e.g., a single reference to Linux continuous deployment network dependencies). There are no Linux-specific configuration or troubleshooting examples, and the only command-line example provided uses Azure CLI, which is cross-platform but lacks explicit Linux shell context or PowerShell alternatives. Windows-centric tools and patterns (Active Directory, NetBIOS, Windows Containers) are referenced without Linux equivalents or parity notes.
Recommendations
  • Add Linux-specific examples, such as how to configure virtual network integration for Linux-based App Service apps, including troubleshooting steps and network dependencies.
  • Include parity notes for features that are Windows-only (e.g., Windows Containers, Active Directory domain join), clarifying Linux alternatives or limitations.
  • Provide explicit Linux shell and PowerShell examples for command-line operations where relevant.
  • Mention Linux-native tools or patterns (e.g., LDAP integration, Linux container networking) where Windows tools are referenced.
  • Ensure that references to platform-specific features are balanced and presented in parallel sections (e.g., 'Windows-specific limits' and 'Linux-specific limits').
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-dotnetcore.md ...lob/main/articles/app-service/quickstart-dotnetcore.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. Visual Studio (Windows-only) is presented as the primary IDE, with detailed steps and screenshots for both .NET 10 and .NET Framework 4.8. PowerShell instructions are included, but are explicitly recommended only for Windows hosting, and the PowerShell deployment steps use Windows-style paths and tools (e.g., Compress-Archive). The .NET Framework 4.8 workflow is Windows-exclusive, and the portal instructions default to Windows for GitHub Actions deployment. While cross-platform options (VS Code, CLI, Azure Portal) are present, Windows tools and workflows are often mentioned first or in greater detail, and Linux-specific nuances (such as deployment differences or file system commands) are not covered in depth.
Recommendations
  • Ensure Linux parity by providing explicit Linux shell (bash) examples for file operations, such as zipping published files, in CLI and PowerShell sections.
  • Include screenshots and step-by-step instructions for deploying from Linux environments, especially for VS Code and CLI workflows.
  • Clarify when instructions are Windows-only and provide equivalent Linux alternatives, especially in PowerShell and Visual Studio sections.
  • In portal instructions, highlight Linux deployment options and document any differences or limitations (e.g., GitHub Actions setup for Linux).
  • Present cross-platform tools (CLI, VS Code) before Windows-specific tools (Visual Studio, PowerShell) to avoid 'windows_first' ordering.
  • Expand troubleshooting and tips for Linux users, such as handling permissions, file paths, and environment setup.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/resources-kudu.md ...-docs/blob/main/articles/app-service/resources-kudu.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by referencing Windows-specific tools and patterns, such as IIS diagnostic dumps, IIS process management, and deployment webhooks for Windows apps. There are no Linux-specific examples or mentions of Linux equivalents for these features. The documentation lists Windows tools and features before any mention of cross-platform or Linux alternatives, and omits Linux deployment scenarios or diagnostic tools.
Recommendations
  • Include examples and documentation for Linux-based App Service environments, such as how to access Linux diagnostic logs and manage Linux processes.
  • Mention Linux equivalents to IIS features (e.g., Apache/Nginx logs, process management via standard Linux tools) where relevant.
  • Provide deployment webhook examples for Linux apps, or clarify differences in webhook support between Windows and Linux.
  • Ensure feature lists and examples are presented in a cross-platform manner, or explicitly note platform-specific limitations and alternatives.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/provision-resource-terraform.md ...n/articles/app-service/provision-resource-terraform.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits 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 PowerShell and Windows-specific setup. The Visual Studio Code extension is recommended, which is more commonly used on Windows. While both Linux and Windows Terraform templates are provided, the Windows container template is given equal prominence, and Windows-specific tools and patterns (PowerShell, VS Code) are mentioned throughout.
Recommendations
  • List Linux/Bash configuration options before Windows/PowerShell options in the prerequisites to avoid implicit prioritization.
  • Include explicit instructions or recommendations for Linux-native editors (e.g., Vim, Nano) alongside VS Code.
  • Provide links to Linux-specific setup guides and troubleshooting resources.
  • Ensure parity in example depth and clarity between Linux and Windows sections.
  • Mention cross-platform alternatives to PowerShell where relevant.
  • Clarify that all steps and tools are available and supported on Linux, and highlight any platform-specific differences.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-custom-container.md ...in/articles/app-service/quickstart-custom-container.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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-specific pivots (Visual Studio, PowerShell, CLI) before their Linux equivalents and providing dedicated sections for Windows tools such as PowerShell and Visual Studio. Linux pivots are present but less prominent, and there is no explicit parity in command-line tooling (e.g., Bash or Linux shell examples). The structure and ordering suggest a preference for Windows workflows.
Recommendations
  • Ensure Linux pivots (e.g., VS Code, Azure CLI, Bash) are listed with equal prominence and ordering as Windows pivots.
  • Add explicit Linux shell command examples (e.g., Bash) alongside PowerShell examples.
  • Include Linux-specific tooling and workflows (such as Docker commands on Linux, Linux file paths) in the quickstart.
  • Review the included files to confirm Linux instructions are as detailed and accessible as Windows instructions.
  • Consider a unified CLI section that demonstrates cross-platform usage, rather than splitting by OS.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-managed-instance.md ...in/articles/app-service/quickstart-managed-instance.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias. The only configuration (install) script provided is a PowerShell script (Install.ps1) that installs fonts to the C:\Windows\Fonts directory and modifies the Windows registry. All examples and instructions for OS-level customization reference Windows-specific paths, tools, and patterns. There are no equivalent examples or instructions for Linux-based App Service plans, nor is there mention of how to adapt the process for Linux environments. The runtime stack example is also Windows-specific (.NET Framework 4.8), and the font installation process is exclusively tailored to Windows.
Recommendations
  • Provide equivalent Linux examples, such as a Bash shell script for font installation in Linux-based App Service plans (e.g., copying fonts to /usr/share/fonts and running fc-cache).
  • Clarify whether Managed Instance supports Linux plans, and if so, include instructions for both Windows and Linux scenarios.
  • When showing configuration scripts, offer both PowerShell and Bash script samples, and explain any OS-specific differences.
  • Mention Linux runtime stack options (e.g., .NET Core, Node.js, Python) alongside Windows examples.
  • Avoid assuming C:\Windows\Fonts as the only font directory; include Linux font directories in examples and screenshots.
  • Explicitly state OS limitations or requirements for features that are Windows-only.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-app.md ...e/scenario-secure-app-access-microsoft-graph-as-app.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 the required NuGet packages using both the .NET Core CLI and the Visual Studio Package Manager Console. However, the Package Manager Console (PowerShell) instructions are given equal prominence to the cross-platform .NET CLI, and there is no mention of Linux-specific development environments or tools (e.g., VS Code, bash). The instructions and tooling references (Visual Studio, Package Manager Console) are Windows-centric, and there are no examples or guidance for Linux users beyond the CLI commands.
Recommendations
  • Explicitly mention that the .NET Core CLI commands work on Linux, macOS, and Windows.
  • Add instructions for using VS Code or other cross-platform editors to install NuGet packages.
  • Clarify that the Package Manager Console is only available in Visual Studio (Windows), and suggest alternatives for Linux users.
  • Provide a brief section or note for Linux users, including example commands for common Linux shells (e.g., bash, zsh) if relevant.
  • Ensure parity in tooling references by mentioning cross-platform options before or alongside Windows-specific tools.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/routine-maintenance-downtime.md ...n/articles/app-service/routine-maintenance-downtime.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 prioritizing Windows-specific features and tools (such as IIS Application Initialization and .NET Core stdout logging) in its explanations and examples. Windows mechanisms are described in detail and mentioned first, while Linux equivalents are referenced briefly or as afterthoughts, with minimal guidance or examples. There is a lack of parity in example depth and actionable instructions for Linux users.
Recommendations
  • Provide detailed Linux-specific examples and instructions alongside Windows ones, especially for features like application initialization and logging.
  • Mention Linux mechanisms (e.g., WEBSITE_WARMUP_PATH) with equal prominence and detail as Windows tools.
  • Include code/configuration samples for Linux environments (e.g., how to set WEBSITE_WARMUP_PATH, recommended logging strategies for Linux apps).
  • Ensure that feature descriptions and troubleshooting steps are platform-neutral or clearly separated for Windows and Linux, with equal coverage.
  • Avoid referencing Windows tools (IIS, .NET Core stdout logging) without offering Linux alternatives or guidance.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 it lists the Visual Studio/PowerShell method after the cross-platform CLI. However, there is a notable absence of explicit Linux or macOS tooling or workflow examples. The only IDE mentioned is Visual Studio, which is primarily a Windows tool. There are no references to Linux-specific editors, package managers, or environment setup, nor are there instructions for using the .NET CLI on Linux/macOS or for running the sample app in a Linux environment.
Recommendations
  • Add explicit instructions for installing NuGet packages on Linux/macOS using the .NET CLI, including any prerequisites for .NET SDK installation on those platforms.
  • Mention cross-platform IDEs such as Visual Studio Code, and provide guidance for using them on Linux/macOS.
  • Include a note or section on running and debugging the sample application in a Linux environment (e.g., using the dotnet CLI, configuring environment variables, troubleshooting common Linux issues).
  • Avoid assuming Visual Studio is available; clarify that the .NET CLI commands work on Windows, Linux, and macOS.
  • If referencing PowerShell, also mention Bash equivalents for Linux/macOS users.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/troubleshoot-diagnostic-logs.md ...n/articles/app-service/troubleshoot-diagnostic-logs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed instructions and feature support for Windows-based App Service apps before Linux equivalents. Several logging features (web server logging, detailed error messages, failed request tracing) are described as Windows-only, with no Linux alternatives or workarounds mentioned. Examples and tooling references (such as Log Parser and W3C log format) are Windows-centric. Linux instructions are less detailed and lack parity in logging features and troubleshooting guidance.
Recommendations
  • Provide equivalent Linux examples and instructions for all logging features, or clearly document feature gaps and suggest alternatives.
  • Add troubleshooting and diagnostic guidance specific to Linux and containerized environments, including supported logging formats and access methods.
  • Reference Linux-friendly tools for log analysis and access, such as grep, tail, or open-source log viewers, alongside Windows tools.
  • Clarify which features are Windows-only at the start of each section, and offer Linux workarounds or roadmap information if features are missing.
  • Ensure that code and CLI examples are provided for both Windows and Linux platforms, or explicitly state platform limitations.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/troubleshoot-http-502-http-503.md ...articles/app-service/troubleshoot-http-502-http-503.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary CLI tool for managing Azure resources, mentioning DOS commands in the Kudu console, and highlighting the use of Windows-specific tools like ProcDump. There are no examples or mentions of Linux shell commands, Linux-native troubleshooting tools, or parity for Linux-based workflows. The order of presentation also places Windows-centric tools and patterns before any Linux alternatives, which are absent.
Recommendations
  • Include examples using Bash/SSH for managing Azure App Service apps, especially for restart and troubleshooting operations.
  • Mention Linux-native tools (e.g., gcore, strace, lsof) for diagnostics and memory dumps alongside ProcDump.
  • Clarify that Kudu supports both PowerShell and Bash consoles, and provide examples for each.
  • Add guidance for Linux-based App Service environments, including troubleshooting steps and tool recommendations.
  • Ensure that references to command-line management (e.g., restarting apps) include both PowerShell and Azure CLI (az) examples, with parity in instructions.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-storage.md ...cles/app-service/scenario-secure-app-access-storage.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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). However, it lists the Visual Studio/PowerShell method after the cross-platform .NET CLI, but still includes Windows-specific tooling (Visual Studio, Package Manager Console) without mentioning Linux or macOS equivalents. There is no explicit guidance for Linux users (e.g., using Bash, VS Code, or other editors), nor are there instructions for installing .NET or running the sample on Linux. The only code example is in C#, which is cross-platform, but the tooling instructions lean toward Windows environments.
Recommendations
  • Add explicit instructions for Linux/macOS users, such as using Bash or zsh terminals.
  • Mention cross-platform editors like VS Code and how to install NuGet packages there.
  • Clarify that the .NET CLI commands work on all platforms, and provide a note for Linux/macOS users.
  • Remove or supplement references to Visual Studio/Package Manager Console with alternatives for non-Windows environments.
  • Include a section or note on how to set up the environment and run the sample on Linux/macOS.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/troubleshoot-performance-degradation.md ...es/app-service/troubleshoot-performance-degradation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell is mentioned as the primary CLI for managing and restarting apps, with no mention of Bash, Azure CLI, or Linux shell equivalents. Diagnostic tools such as Kudu and Procdump are described in a Windows-centric manner, and links reference 'Windows Azure Websites' and Windows-specific troubleshooting. There are no explicit Linux or cross-platform examples for collecting diagnostics, managing apps, or using alternative tools, and Windows terminology (IIS, web.config, DOS commands) is used without Linux parity.
Recommendations
  • Include Azure CLI and Bash/Linux shell examples alongside PowerShell for management tasks such as restarting apps.
  • Mention Linux equivalents for diagnostic tools (e.g., alternatives to Procdump for memory dumps on Linux).
  • Clarify which features and tools are available on Linux-based App Service plans, and provide links to Linux-specific documentation where applicable.
  • Avoid Windows-centric terminology (e.g., IIS, web.config, DOS commands) or provide Linux equivalents (e.g., Nginx/Apache, appsettings.json, Bash commands).
  • Add explicit instructions or examples for enabling diagnostics and collecting logs on Linux-based App Service environments.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-msi-sql-database.md ...icles/app-service/tutorial-connect-msi-sql-database.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways: Windows/PowerShell tools and workflows (Visual Studio for Windows, PowerShell, SQLCMD) are presented first or exclusively, with detailed instructions and screenshots. Linux/macOS equivalents (such as using Azure CLI, VS Code, or cross-platform SQL tools) are either relegated to later sections, given less detail, or omitted entirely. There are no explicit Linux-specific examples for database access or development environment setup, and the use of PowerShell and Visual Studio for Windows is emphasized throughout.
Recommendations
  • Provide explicit Linux/macOS development environment setup instructions, including using VS Code, JetBrains Rider, or CLI tools.
  • Include examples for connecting to Azure SQL Database using cross-platform tools such as sqlcmd (via Docker), Azure Data Studio, or the Azure CLI.
  • Add instructions for running database migration and debugging from Linux/macOS, not just Visual Studio for Windows.
  • Ensure parity in step-by-step guidance and screenshots for Linux/macOS workflows.
  • Mention and demonstrate using Bash scripts and CLI commands where PowerShell is used, and clarify cross-platform compatibility.
  • Reorder sections so that Windows and Linux/macOS approaches are presented equally, or use tabs for OS-specific instructions.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-msi-azure-database.md ...les/app-service/tutorial-connect-msi-azure-database.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias, particularly in the 'Set up your dev environment' section. Visual Studio for Windows is presented first and in more detail, while Visual Studio for Mac is described as lacking integration and requires a workaround. Windows-specific tools (Visual Studio, Azure PowerShell) are mentioned before Linux alternatives, and PowerShell is included as a primary method for authentication. There is little explicit mention of Linux or cross-platform CLI usage outside of Azure CLI, and no Linux-specific development environment examples (e.g., JetBrains Rider, VS Code on Linux, or native Linux shell usage) are provided.
Recommendations
  • Present cross-platform development environments (e.g., VS Code, JetBrains Rider) before or alongside Windows-specific tools.
  • Include explicit Linux development environment setup instructions, such as using Azure CLI in Bash or Zsh, and clarify that Azure CLI and VS Code are cross-platform.
  • Add examples for signing in and using managed identity from Linux shells (bash, zsh) and highlight parity with Windows tools.
  • Avoid presenting Windows tools (Visual Studio, PowerShell) before their cross-platform or Linux equivalents; use neutral ordering or group by platform.
  • Clarify that Azure CLI and VS Code instructions apply equally to Linux, macOS, and Windows, and provide screenshots or terminal examples from Linux environments.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-custom-container.md ...main/articles/app-service/tutorial-custom-container.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 clear Windows bias in the 'container-windows' pivot. Windows instructions are presented first, and the workflow is tightly coupled to Windows-specific tools such as Visual Studio, Windows Explorer, and PowerShell scripts. The Windows section lacks parity with Linux: it does not offer alternative approaches for Linux users (e.g., building Windows containers from Linux, using cross-platform editors, or non-PowerShell font installation). The Linux section is more cross-platform, relying on CLI and Docker, but the Windows section is exclusively Windows-centric.
Recommendations
  • Add instructions for building and deploying Windows containers from Linux or macOS environments, if supported.
  • Provide alternative tooling options (e.g., VS Code, Docker CLI) for users who do not use Visual Studio or Windows Explorer.
  • Include non-PowerShell methods for tasks like font installation (e.g., using Dockerfile commands directly or cross-platform scripting).
  • Clarify in the prerequisites and throughout the tutorial whether Windows is strictly required, and if so, explain why.
  • Offer guidance for users who wish to migrate apps but do not have access to Windows or Visual Studio.
  • Ensure that both pivots (Windows and Linux) have comparable depth and clarity, and that Linux users are not disadvantaged in terms of available examples and tooling.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-webjobs.md ...ocs/blob/main/articles/app-service/tutorial-webjobs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windowscode Tabs Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias, especially in the .NET section. Windows build and packaging instructions are presented before Linux equivalents, with explicit tabs for Windows and Linux. References to 'windowscode' tabs and supported file types are present in all pivots, even those that are Linux-only (Python, PHP). The .NET instructions provide more detail for Windows, including the need for a 'run.sh' script only in Linux, which may imply Windows as the default. Other language pivots (Python, Node, Java, PHP) focus on Linux, but still reference 'windowscode' tabs and supported file types, which may be confusing or misleading for Linux users.
Recommendations
  • Present Windows and Linux instructions with equal prominence, or default to Linux-first if the majority of pivots are Linux-only.
  • Avoid referencing 'windowscode' tabs or Windows-specific file types in Linux-only pivots (Python, PHP, Node, Java). Instead, provide a link to a generic supported file types section.
  • Clarify when instructions are OS-specific, and avoid implying Windows as the default (e.g., explain why 'run.sh' is needed for Linux, and what the equivalent is for Windows).
  • Where possible, provide parity in detail and troubleshooting steps for both Windows and Linux workflows.
  • Consider adding explicit troubleshooting or FAQ sections for Linux users, especially for common issues (e.g., permissions, executable formats).
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/webjobs-sdk-get-started.md ...b/main/articles/app-service/webjobs-sdk-get-started.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong Windows bias by exclusively using Visual Studio 2022 for project creation, configuration, and deployment, and by providing only PowerShell/Package Manager Console commands for NuGet package installation. There are no instructions or examples for Linux or cross-platform development environments (such as VS Code, CLI, or JetBrains Rider), nor are alternative tools or workflows mentioned. Steps for local testing, configuration, and deployment are all tailored to Windows and Visual Studio users, with no guidance for Linux or macOS users.
Recommendations
  • Add equivalent instructions for creating and managing the project using cross-platform tools such as .NET CLI and VS Code.
  • Include NuGet package installation examples using 'dotnet add package' commands, which work on all platforms.
  • Provide steps for configuring and running the WebJobs SDK on Linux and macOS, including environment variable setup and local testing.
  • Mention and link to alternative editors (VS Code, Rider) and their relevant workflows.
  • Clarify which steps are platform-specific and offer parity for non-Windows environments wherever possible.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/webjobs-sdk-how-to.md ...s/blob/main/articles/app-service/webjobs-sdk-how-to.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for the Azure WebJobs SDK exhibits Windows bias in several ways. All file path examples use Windows-style paths (e.g., 'c:\data\import'), and there is no mention of Linux or cross-platform alternatives. The documentation references Visual Studio tooling and .NET Framework without mentioning cross-platform editors or Linux-specific instructions. Additionally, examples involving ServicePointManager and WinHttpHandler are Windows-centric, with no discussion of Linux equivalents or considerations. There are no Linux or bash shell examples, and environment variable usage is described generically but not illustrated with platform-specific differences.
Recommendations
  • Include Linux/macOS file path examples (e.g., '/home/user/data/import') alongside Windows paths.
  • Explicitly mention cross-platform compatibility and provide instructions for running WebJobs SDK on Linux, including any differences in configuration or tooling.
  • Add examples using popular cross-platform editors (e.g., VS Code) and .NET Core CLI commands, not just Visual Studio.
  • Discuss any platform-specific limitations or considerations, such as differences in HTTP handlers or environment variable conventions.
  • Where environment variables or configuration files are referenced, show both Windows (set, appsettings.json) and Linux (export, .env) usage patterns.
  • If certain features or APIs are Windows-only (e.g., WinHttpHandler), note alternatives or limitations for Linux users.
GitHub Create Pull Request
← Previous Page 13 of 85 Next →