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 26-50 of 2121 flagged pages
App Service Quickstart: Deploy Managed Instance on Azure App Service (Preview) ...in/articles/app-service/quickstart-managed-instance.md
High Priority View Details →
Scanned: 2026-01-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 is notably Windows-centric. The only configuration (install) script provided is a PowerShell script (Install.ps1) that installs fonts specifically to the C:\Windows\Fonts directory and modifies the Windows registry. There are no Linux/macOS equivalents or guidance for non-Windows environments. The sample app and instructions assume a Windows runtime (ASPNET V4.8), and the font installation process is tied to Windows internals. Examples and screenshots reference Windows paths and tools, and there is no mention of Linux-compatible deployment or scripting options.
Recommendations
  • Provide equivalent configuration (install) script examples for Linux (e.g., Bash scripts to copy fonts to /usr/share/fonts and update font cache).
  • Clarify whether Managed Instance supports Linux-based plans and runtimes, and if so, include instructions and examples for those scenarios.
  • Offer sample apps and deployment steps for Linux runtimes (e.g., Node.js, Python, .NET Core) alongside Windows examples.
  • Explicitly state OS limitations or requirements for Managed Instance, so users know if Linux/macOS is supported.
  • Add notes or sections for macOS/Linux users, including how to prepare and deploy configuration scripts for those platforms.
GitHub Create Pull Request
App Service Tutorial for event-driven background processing with the WebJobs SDK ...b/main/articles/app-service/webjobs-sdk-get-started.md
High Priority View Details →
Scanned: 2026-01-14 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 is heavily oriented toward Windows and Visual Studio workflows. All examples and instructions use Visual Studio 2022, Windows UI terminology, and PowerShell/Package Manager Console commands. There are no instructions or examples for Linux/macOS users, such as using VS Code, .NET CLI, or alternative package managers. Steps like project creation, NuGet package installation, and publishing are described only for Windows tools, making it difficult for Linux/macOS users to follow or complete the tutorial.
Recommendations
  • Add parallel instructions for Linux/macOS users using VS Code or JetBrains Rider, and the .NET CLI (e.g., 'dotnet new console', 'dotnet add package').
  • Include screenshots or descriptions for non-Windows environments where applicable.
  • Document how to publish and manage WebJobs from Linux/macOS, including Azure CLI commands.
  • Clarify that PowerShell/Package Manager Console commands are Windows-specific and provide bash/zsh equivalents.
  • Mention cross-platform prerequisites (e.g., .NET SDK installation for Linux/macOS).
GitHub Create Pull Request
App Service Discover .NET Apps to Azure App Service ...cles/app-service/app-service-migration-discover-net.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation focuses exclusively on discovering ASP.NET web apps hosted on IIS servers, which are Windows-specific. There is no mention of Linux-based web servers (e.g., Apache, Nginx) or .NET Core apps running on Linux. All discovery capabilities and examples are centered around Windows tools and environments, with no guidance or parity for Linux/macOS users.
Recommendations
  • Include information about discovering .NET apps hosted on Linux servers, such as those running on Apache or Nginx.
  • Provide examples and tooling for Linux-based environments, including instructions for configuring Azure Migrate to discover .NET Core apps on Linux.
  • Clarify whether the discovery process supports cross-platform .NET apps and, if so, document the steps for non-Windows environments.
  • Add a section comparing Windows and Linux discovery capabilities, highlighting any gaps and workarounds.
GitHub Create Pull Request
App Service Configure Managed Instance on Azure App Service (Preview) ...ain/articles/app-service/configure-managed-instance.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric: all configuration examples use PowerShell scripts (Install.ps1), only Windows installers (MSI), registry keys, and Windows-specific features (IIS, ACLs, RDP) are discussed. No Linux/macOS equivalents, examples, or instructions are provided. The FAQ and prerequisites confirm that Managed Instance is Windows Server 2022 only, and all customization is via Windows tools and patterns.
Recommendations
  • Explicitly state that Managed Instance is Windows-only at the top of the page.
  • If Linux support is planned, provide equivalent instructions and examples for Linux-based managed instances (e.g., Bash scripts, Linux storage mounts, Linux configuration patterns).
  • For cross-platform parity, link to Linux App Service documentation where relevant.
  • Clarify in each section that features like registry keys, Install.ps1, and RDP are not applicable to Linux.
  • Consider adding a comparison table showing which features are Windows-only and which are cross-platform.
GitHub Create Pull Request
App Service Migrate .NET Apps to Azure App Service .../articles/app-service/app-service-asp-net-migration.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias, focusing almost exclusively on migration tools and patterns for ASP.NET apps hosted on IIS (Windows). All listed migration tools (App Service Migration Assistant, PowerShell scripts) are Windows-specific, and examples or instructions for Linux-hosted .NET apps (e.g., on Apache, Nginx, or Kestrel) are absent. The documentation repeatedly references Windows OS, IIS, and PowerShell, with no mention of Linux equivalents or guidance for Linux users.
Recommendations
  • Add explicit guidance and migration steps for .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel).
  • Include Linux-specific migration tools or manual migration instructions, such as using rsync, SCP, or Azure CLI.
  • Provide examples and walkthroughs for containerizing .NET apps from Linux environments.
  • List Linux-compatible assessment and migration resources alongside Windows tools.
  • Clarify limitations or alternative approaches for users not running IIS/Windows.
GitHub Create Pull Request
App Service Node.js Best Practices and Troubleshooting ...rvice-web-nodejs-best-practices-and-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation is heavily focused on Windows-specific technologies (IIS, iisnode, web.config, named pipes, Win32 error codes, DLLs) and troubleshooting paths. There are no Linux or cross-platform equivalents mentioned, and all examples and configuration references are for Windows environments. Linux users are left without guidance for deploying or troubleshooting Node.js apps on Azure App Service outside the Windows/iisnode stack.
Recommendations
  • Add equivalent guidance for Linux-based Azure App Service environments, such as using PM2, NGINX, or Kestrel for Node.js hosting.
  • Include troubleshooting steps and log file locations for Linux-based deployments.
  • Provide configuration examples for Linux (e.g., environment variables, process managers) alongside or before Windows/iisnode examples.
  • Clarify which sections apply only to Windows/iisnode and link to Linux-specific documentation where available.
  • Mention Azure App Service's Linux container support and how Node.js apps are managed there.
GitHub Create Pull Request
App Service Tutorial: ASP.NET app with Azure SQL Database ...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The tutorial is heavily oriented toward Windows and Visual Studio, with all instructions and screenshots referencing Windows-specific tools and workflows. Examples use PowerShell and Visual Studio features that are not available or are significantly different on Linux/macOS. There are no alternative instructions or examples for Linux/macOS users, nor any mention of cross-platform tools or workflows.
Recommendations
  • Add instructions for using Visual Studio Code (VS Code) or the .NET CLI for Linux/macOS users, including how to publish to Azure App Service and connect to Azure SQL Database.
  • Provide examples using Bash and the Azure CLI instead of (or in addition to) PowerShell.
  • Include screenshots and steps for Linux/macOS environments, such as using VS Code, JetBrains Rider, or other cross-platform IDEs.
  • Mention and link to cross-platform alternatives for tasks like package management (e.g., dotnet CLI for NuGet packages), database management (e.g., Azure Data Studio), and log streaming.
  • Clearly indicate which steps are Windows-only and provide parity instructions for other platforms.
GitHub Create Pull Request
App Service Configure gateway-required virtual network integration for your app ...service/configure-gateway-required-vnet-integration.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is heavily biased toward Windows. Gateway-required virtual network integration is explicitly stated to only work for Windows plans, with Linux apps unsupported. All troubleshooting examples use Windows tools (PowerShell's Test-NetConnection, netstat), and there are no Linux/macOS equivalents or guidance. The documentation does not provide parity for Linux users, who cannot complete the task using this method.
Recommendations
  • Clearly state at the beginning that gateway-required integration is Windows-only and suggest regional integration for Linux users.
  • For troubleshooting, provide equivalent Linux/macOS commands (e.g., 'nc', 'telnet', 'ss', 'netcat') alongside PowerShell examples.
  • In sections discussing tools or commands, offer cross-platform alternatives or note platform limitations.
  • Add a comparison table summarizing feature support for Windows vs. Linux plans.
  • Link to regional virtual network integration documentation for Linux users.
GitHub Create Pull Request
App Service Operating System Functionality in Azure App Service ...articles/app-service/operating-system-functionality.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows App Service environments, with examples, terminology, and features (such as registry access, IIS, ASP.NET, COM components, and PowerShell) that are specific to Windows. Linux is mentioned only briefly and in a note, with no equivalent details or examples for Linux-based App Service environments. There are no Linux-specific file system, network, or diagnostic examples, and Windows tools and patterns (e.g., environment variables like %SystemDrive%, registry, IIS directories) are described exclusively.
Recommendations
  • Add a parallel section describing file, network, and diagnostic access for Linux-based App Service environments, including Linux-specific paths, environment variables, and limitations.
  • Provide Linux examples for file access (e.g., using $HOME, /tmp, or other relevant directories) and clarify persistence and sharing across instances.
  • Describe Linux equivalents for diagnostic logging (e.g., stdout/stderr, syslog, application logs) and how to access them.
  • Mention Linux process and code execution details (e.g., shell scripts, bash, Python, etc.) and any restrictions.
  • Clarify which features (such as registry access, IIS, COM, PowerShell) are not applicable to Linux, and provide Linux alternatives where possible.
  • Ensure that Linux-specific tools, patterns, and troubleshooting steps are included alongside Windows examples.
GitHub Create Pull Request
App Service Managed Instance on App Service overview (preview) ...main/articles/app-service/overview-managed-instance.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased toward Windows, with all examples, tools, and configuration patterns centered on Windows technologies (PowerShell, registry, COM, MSI, IIS, RDP, GAC, Windows services). There are no Linux or macOS equivalents, and the platform is explicitly described as Windows-only. Linux users are excluded from using or configuring Managed Instance, and all operational and troubleshooting guidance assumes a Windows environment.
Recommendations
  • Clearly state Windows-only scope at the top of the page and in all relevant sections.
  • Provide links or references to equivalent Linux hosting options (e.g., App Service for Linux, container hosting) for users seeking similar capabilities.
  • Where possible, offer guidance for migrating legacy workloads to Linux or containers, or direct users to modernization resources.
  • If future Linux support is planned, note this and provide a roadmap or feedback channel.
  • Ensure parity in documentation structure and detail for Linux offerings elsewhere in the docs.
GitHub Create Pull Request
App Service Quickstart: Deploy Managed Instance on Azure App Service (Preview) ...in/articles/app-service/quickstart-managed-instance.md
High Priority View Details →
Scanned: 2026-01-13 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 is notably Windows-centric: the only configuration (install) script provided is a PowerShell script targeting Windows font installation in C:\Windows\Fonts and registry edits, with no Linux/macOS equivalent or guidance. The sample app and deployment instructions assume a Windows runtime (ASPNET V4.8), and references to OS-level customization are exclusively for Windows. There is no mention of Linux-based Managed Instance plans, nor examples for Linux shell scripting or deployment.
Recommendations
  • Provide equivalent Linux/macOS configuration (install) script examples (e.g., Bash scripts for font installation in /usr/share/fonts).
  • Clarify whether Managed Instance supports Linux plans; if so, include instructions and examples for Linux runtimes (e.g., Node.js, Python, .NET Core).
  • Offer sample apps and deployment steps for Linux-based environments.
  • Explicitly state OS limitations or support in the prerequisites and plan selection sections.
  • Present examples for both Windows and Linux side-by-side, or indicate which steps are OS-specific.
GitHub Create Pull Request
App Service Develop and deploy WebJobs using Visual Studio .../main/articles/app-service/webjobs-dotnet-deploy-vs.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Visual Studio, a Windows-centric IDE, and describes workflows and UI elements (Solution Explorer, dialog boxes) that are specific to Windows environments. There are no examples or instructions for developing or deploying WebJobs using Linux or macOS tools (such as VS Code, CLI, or cross-platform deployment methods). All screenshots and steps assume a Windows/Visual Studio workflow, and there is no mention of Linux equivalents or alternative approaches for non-Windows users.
Recommendations
  • Add instructions for developing and deploying WebJobs using cross-platform tools such as VS Code and the Azure CLI.
  • Include Linux/macOS-specific examples and workflows, such as using dotnet CLI, zip deployment, or GitHub Actions.
  • Clearly indicate which steps are Windows/Visual Studio-specific and provide parity guidance for Linux/macOS users.
  • Add screenshots and UI references for cross-platform tools where applicable.
  • Reference documentation for deploying WebJobs from non-Windows environments.
GitHub Create Pull Request
App Service Discover .NET Apps to Azure App Service ...cles/app-service/app-service-migration-discover-net.md
High 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 focuses exclusively on discovery of ASP.NET web apps hosted on IIS servers, which are Windows-specific. There is no mention of Linux-based web servers (such as Apache or Nginx), nor are there examples or guidance for discovering .NET apps running on Linux. All tooling and patterns referenced (Azure Migrate appliance, IIS) are Windows-centric, and Linux equivalents are absent.
Recommendations
  • Add sections or examples for discovering .NET web apps hosted on Linux servers (e.g., Apache, Nginx).
  • Mention whether Azure Migrate supports discovery for Linux-based .NET deployments, and provide guidance if available.
  • Include parity in dashboard features and error remediation for Linux scenarios.
  • Explicitly state platform limitations if Linux discovery is not supported, and link to alternative solutions for Linux users.
GitHub Create Pull Request
App Service Restore Deleted Apps ...blob/main/articles/app-service/app-service-undelete.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples and referencing Windows-centric tools and patterns. All command-line instructions use PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native workflows. The documentation does not provide equivalent examples for Linux users or alternative cross-platform approaches, and PowerShell is introduced before any other automation tool (which are not mentioned at all).
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that PowerShell is available on Linux and macOS, but also provide Bash/CLI alternatives for users who prefer native Linux tools.
  • Include guidance for restoring deleted apps using REST API calls or Azure SDKs, which are platform-agnostic.
  • Reorganize sections so that cross-platform tools (e.g., Azure CLI) are presented before or alongside PowerShell, not after or omitted.
  • Add notes or links to documentation on installing and using Azure CLI or PowerShell on Linux/macOS, to improve accessibility for non-Windows users.
GitHub Create Pull Request
App Service Customize Sign-ins and Sign-outs ...vice/configure-authentication-customize-sign-in-out.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias in the 'Authorize or deny users' section, where server-level authorization is described exclusively for Windows apps using IIS and web.config, with no equivalent guidance for Linux apps. Windows tools (IIS, web.config, Kudu) are mentioned, and Linux alternatives are not provided or discussed. The ordering also places Windows-specific instructions before any general or identity provider-level guidance.
Recommendations
  • Provide equivalent examples for Linux apps, such as how to implement server-level authorization using nginx, Apache, or application-level middleware.
  • Explicitly mention that Linux apps require different configuration approaches and link to relevant resources or sample code.
  • Balance the ordering by presenting cross-platform or Linux-specific guidance alongside Windows instructions, rather than focusing on Windows first.
  • Avoid exclusive references to Windows tools (IIS, web.config, Kudu) without offering Linux alternatives or clarifying platform limitations.
GitHub Create Pull Request
App Service Install a TLS/SSL Certificate for Your App ...main/articles/app-service/configure-ssl-certificate.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. It references Windows-specific tools (IIS, Certreq.exe) for certificate export, provides PowerShell examples alongside Azure CLI, and refers to Windows container support in FAQs. Linux alternatives (such as Linux-based certificate management tools) are not mentioned, and Windows tools are listed before or instead of Linux equivalents. There are no explicit Linux-focused examples or guidance, and automation examples are split between Azure CLI and PowerShell, but not Bash or other Linux-native scripting.
Recommendations
  • Add explicit Linux-based instructions and examples for certificate export, such as using OpenSSL on Linux, and clarify steps for Linux users.
  • Include Bash scripting examples for automation alongside Azure CLI and PowerShell.
  • Mention Linux container support and limitations in the FAQ sections, not just Windows containers.
  • When listing tools (e.g., IIS, Certreq.exe), also list Linux alternatives (e.g., OpenSSL, certbot) and provide links to relevant documentation.
  • Ensure that examples and instructions are presented in a cross-platform manner, or provide tabs for Windows and Linux workflows where appropriate.
GitHub Create Pull Request
App Service Configure Managed Instance on Azure App Service (Preview) ...ain/articles/app-service/configure-managed-instance.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily Windows-centric, with all examples, configuration patterns, and terminology tailored exclusively to Windows environments. Only Windows tools (PowerShell, MSI, Registry, RDP) are referenced, and there are no Linux equivalents or cross-platform considerations. The configuration script must be a PowerShell script named Install.ps1, and all customization scenarios (IIS, registry, ACLs, Windows features) are Windows-specific. Remote access is described solely in terms of RDP/Bastion, and troubleshooting/logging paths use Windows filesystem conventions. There is no mention of Linux support, examples, or alternative tooling.
Recommendations
  • Clearly state in the introduction that Managed Instance on Azure App Service is Windows-only, if that is the case. If Linux support is planned or possible, provide equivalent Linux instructions and examples.
  • For each configuration area (scripts, storage, registry, remote access), include Linux-specific guidance or explicitly note if not supported.
  • If configuration scripts are required to be PowerShell, clarify that Bash or other scripting languages are not supported, and consider adding support for Bash scripts for Linux parity.
  • For storage mounts, mention Linux mount patterns (e.g., mounting Azure Files via SMB/NFS on Linux) if/when supported.
  • For remote access, mention SSH as the Linux equivalent to RDP/Bastion, or state that only RDP is supported.
  • For registry keys, clarify that this is a Windows-only concept and provide Linux alternatives (such as environment variables or configuration files) if applicable.
  • In FAQs and troubleshooting, provide Linux file paths and logging conventions if Linux is or will be supported.
  • Review keywords and metadata to ensure Linux-related terms are included if cross-platform support is intended.
GitHub Create Pull Request
App Service Geo-Distributed Scale ...-service-app-service-environment-geo-distributed-scale.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively providing PowerShell examples for configuring Azure Traffic Manager and App Service Environments. There are no CLI (az), Bash, or Linux-native instructions or examples. The use of PowerShell is presented as the 'easiest way' without mention of alternatives, and no Linux tools or cross-platform patterns are discussed.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, showing how to create and configure Traffic Manager profiles and endpoints using Bash or other shells.
  • Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and link to cross-platform tool documentation.
  • Provide screenshots or terminal output from Linux environments where relevant (e.g., DNS lookups using dig or host).
  • Avoid language that implies PowerShell is the only or preferred method; present CLI and PowerShell options side-by-side.
  • Include a section on platform-agnostic automation approaches (e.g., ARM templates, Terraform) for advanced users.
GitHub Create Pull Request
App Service Quickstart: Deploy an ASP.NET web app ...lob/main/articles/app-service/quickstart-dotnetcore.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Visual Studio (Windows-only) is presented as the primary IDE, with detailed steps and screenshots. PowerShell is given its own section, with explicit recommendations for Windows hosting, while Linux deployment is relegated to Azure CLI or other tools. Many examples and instructions (such as file paths and compression commands) use Windows conventions, and some steps (e.g., .NET Framework 4.8) are only available for Windows. In some places, Linux options are mentioned but not shown in detail, and Windows tools or patterns are introduced before Linux equivalents.
Recommendations
  • Provide equal detail and screenshots for Linux workflows, including using Linux-native editors and shell commands.
  • Include explicit Linux file path and command examples (e.g., using zip/tar instead of Compress-Archive, showing bash syntax).
  • Where PowerShell is recommended for Windows, offer Bash or other Linux-native alternatives for Linux users.
  • Clarify which steps are cross-platform and which are Windows-only, and avoid presenting Windows-first unless justified by usage data.
  • Expand instructions for deploying to Azure App Service on Linux, including troubleshooting and configuration tips.
  • For .NET Framework sections, clearly state Windows-only limitations and suggest .NET Core/10 alternatives for Linux users.
GitHub Create Pull Request
App Service Use Private Endpoints for Apps ...main/articles/app-service/overview-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. In the 'Related content' section, Windows-centric tools and examples (Azure PowerShell, ARM templates) are listed before Linux-friendly options (Azure CLI, Terraform). There is a dedicated PowerShell quickstart, but no Bash or Linux shell example. The DNS examples and instructions reference Windows-style host file editing and do not mention Linux equivalents. No explicit Linux command-line examples or Linux-specific troubleshooting are provided.
Recommendations
  • Add explicit Linux/Bash shell examples alongside PowerShell, especially for DNS configuration and endpoint creation.
  • Mention Linux tools and patterns (such as editing /etc/hosts for DNS testing) when discussing host file modification.
  • Ensure parity in quickstart guides: provide Bash/CLI scripts and troubleshooting steps for Linux users.
  • List cross-platform tools (Azure CLI, Terraform) before Windows-specific tools (PowerShell, ARM templates) in 'Related content'.
  • Include notes or links for Linux-specific considerations, such as SELinux, firewall configuration, or systemd-resolved DNS integration.
GitHub Create Pull Request
App Service Create a scheduled WebJob with prebuilt samples ...s/blob/main/articles/app-service/quickstart-webjobs.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Windows as the first platform in prerequisites and examples, providing more Windows-specific sample types (CMD, Batch, PowerShell, F#) than Linux, and including Windows-only scripting languages and tools. Linux examples are limited to cross-platform languages and Bash, with no Linux equivalents for CMD, Batch, PowerShell, or F#. The structure and ordering prioritize Windows users and tools, potentially making Linux users feel secondary.
Recommendations
  • Present Linux and Windows platforms with equal prominence in prerequisites and sample tables.
  • Add Linux equivalents for Windows-specific samples where possible (e.g., provide shell scripts for tasks shown in CMD/Batch/PowerShell).
  • Include Linux-specific scripting languages or tools (e.g., Perl, Ruby, or shell variants) to match the breadth of Windows examples.
  • Ensure that instructions and examples for both platforms are parallel in detail and order.
  • Consider starting with a cross-platform introduction before splitting into OS-specific tabs.
GitHub Create Pull Request
App Service Tutorial - .NET Web app accesses Microsoft Graph as the user | Azure ...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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing installation instructions using Visual Studio's Package Manager Console (PowerShell) and referencing Visual Studio tooling before mentioning cross-platform .NET CLI commands. There are no explicit Linux or cross-platform editor instructions, and the examples assume a Windows development environment. No Linux-specific package installation or editor guidance is provided.
Recommendations
  • Add explicit instructions for installing NuGet packages using the .NET CLI first, emphasizing its cross-platform nature.
  • Include examples for popular Linux-based editors (e.g., VS Code, JetBrains Rider) and terminal usage.
  • Clarify that all .NET CLI commands work on Linux, macOS, and Windows, and provide a section on developing and running the sample on Linux.
  • Avoid referencing Visual Studio tooling (like Package Manager Console) before cross-platform alternatives.
  • Add troubleshooting notes or links for Linux-specific issues (e.g., permissions, environment setup).
GitHub Create Pull Request
App Service Migrate .NET Apps to Azure App Service .../articles/app-service/app-service-asp-net-migration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias throughout. All migration tools and examples focus exclusively on Windows environments, specifically IIS servers and PowerShell scripts. There is no mention of Linux-based .NET hosting (e.g., Kestrel, Apache/Nginx), nor are there migration paths or tools for .NET apps running on Linux. Windows tools and patterns (IIS, PowerShell, MSI installers) are referenced exclusively and repeatedly, with no Linux equivalents or guidance provided.
Recommendations
  • Add migration guidance and examples for .NET apps hosted on Linux (e.g., Kestrel, Apache, Nginx).
  • Include Linux-compatible migration tools or document how to migrate from Linux environments.
  • Provide Bash or shell script equivalents for PowerShell-based migration steps.
  • Mention containerization options for Linux-based .NET apps and how to migrate them to Azure App Service (Linux).
  • Clarify tool/platform support (Windows-only vs. cross-platform) in tool descriptions.
  • Add documentation links and resources for Linux users, including troubleshooting and best practices for Linux migrations.
GitHub Create Pull Request
App Service Configure Premium v4 Tier ...s/app-service/app-service-configure-premium-v4-tier.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-related information and tools. Windows SKU availability is presented before Linux, and Azure PowerShell (a Windows-centric tool) is featured alongside Azure CLI. There are no Linux shell (bash) or scripting examples, and no mention of Linux-specific deployment patterns or tools beyond the Azure CLI flag for Linux workers. The automation section lacks parity for Linux-native scripting, and the overall flow assumes familiarity with Windows tools and the Azure portal, which is more commonly used by Windows users.
Recommendations
  • Provide bash or shell script examples for Linux users alongside PowerShell examples.
  • Present Linux and Windows SKU availability commands together, or alternate their order to avoid Windows-first bias.
  • Include guidance for Linux-native automation (e.g., using bash, curl, or other Linux tools) in addition to Azure CLI and PowerShell.
  • Explicitly mention Linux deployment patterns and tools where relevant, such as using VS Code Remote, GitHub Actions, or other CI/CD options popular in Linux environments.
  • Clarify any differences in the portal experience for Linux vs. Windows app service plans, if applicable.
GitHub Create Pull Request
App Service Hybrid Connections in Azure App Service ...articles/app-service/app-service-hybrid-connections.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and tools (such as PowerShell and GUI usage) are frequently presented first or exclusively, with Linux equivalents sometimes missing or less detailed. Troubleshooting and connectivity testing rely on Windows-specific tools (PowerShell), and GUI management is only available for Windows. Some examples and screenshots are Windows-centric, and legacy support is only for Windows clients.
Recommendations
  • Provide Linux-first or parallel examples for all installation, configuration, and troubleshooting steps.
  • Include Linux-native troubleshooting commands (e.g., 'nc', 'telnet', or 'ss') alongside PowerShell examples for connectivity testing.
  • Expand documentation on Linux CLI usage, including more detailed step-by-step instructions and screenshots where possible.
  • Clarify feature parity and limitations for Linux (e.g., explicitly state GUI is unavailable, but CLI is fully supported).
  • Offer guidance for common Linux distributions and package managers beyond apt (e.g., yum, dnf, zypper).
  • Where legacy or advanced features are Windows-only, provide alternative recommendations or workarounds for Linux users.
GitHub Create Pull Request
← Previous Page 2 of 85 Next →