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 876-900 of 2121 flagged pages
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows-first bias by providing more detailed instructions and features for Windows App Service apps, such as web server logging, detailed error messages, and failed request tracing, which are either unavailable or not documented for Linux. Several logging types and advanced features are described only for Windows, with Linux instructions being briefer and lacking parity. Windows-specific tools and log formats (e.g., W3C, Log Parser, Web.config) are referenced without Linux equivalents or alternatives.
Recommendations
- Provide equivalent Linux examples and instructions for all logging types where possible, or clearly state feature parity gaps.
- Document Linux-specific logging features, tools, and log access patterns, including any differences in log file locations, formats, or retention policies.
- If certain features (e.g., web server logging, failed request tracing) are not available on Linux, explicitly mention this and suggest alternative troubleshooting or logging strategies for Linux users.
- Include Linux-friendly tooling recommendations for log analysis and access (e.g., using tail, grep, or Azure CLI on Linux).
- Ensure that Linux and Windows instructions are presented with equal prominence and detail, possibly in parallel sections or tables.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-asp-net-migration.md
.../articles/app-service/app-service-asp-net-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All migration tools and examples focus exclusively on migrating from Windows environments, specifically IIS servers, and make heavy use of PowerShell scripts. There is no mention of Linux-based hosting environments (such as Apache or Nginx), nor are there migration tools or instructions for Linux-origin .NET apps. The documentation references only Windows containers for unsupported apps, and all downloadable tools are for Windows. Linux scenarios are entirely absent.
Recommendations
- Include migration guidance and tools for .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel).
- Provide Linux shell (bash) script equivalents for PowerShell-based migration steps.
- List Linux-based migration tools and resources alongside Windows tools in all tables and sections.
- Add examples and walkthroughs for migrating .NET Core/ASP.NET Core apps running on Linux to Azure App Service (both Linux and Windows plans).
- Clarify which migration tools (if any) support Linux-origin apps, and if not, provide alternative recommendations.
- Ensure parity in documentation structure and prominence for Linux and Windows migration paths.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-best-practices.md
...ain/articles/app-service/app-service-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows a subtle Windows bias by referencing Windows-specific tools and patterns (such as web.config and iisnode) without providing Linux equivalents or clarifying cross-platform differences. For example, configuring auto-healing via web.config and tuning Node.js apps with iisnode settings are both Windows/IIS-specific, but no Linux or cross-platform alternatives are mentioned. While there is a brief mention of running on Linux with PM2, the overall guidance and examples tend to assume a Windows/IIS environment by default.
Recommendations
- For features like auto-healing, provide Linux-specific configuration guidance (e.g., using app settings, startup scripts, or environment variables) alongside web.config instructions.
- When referencing iisnode or web.config, clarify that these are Windows/IIS-specific and offer equivalent Linux-native approaches (such as using PM2, process.json, or other Node.js process managers).
- Include explicit Linux examples and configuration snippets wherever Windows-specific tools or files are mentioned.
- Add a section or callout summarizing key differences in configuration and troubleshooting between Windows and Linux App Service plans.
- Ensure that all best practices are presented in a cross-platform manner, or clearly indicate when a recommendation is platform-specific.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v3-tier.md
...s/app-service/app-service-configure-premium-v3-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In sections where both Windows and Linux are relevant (such as SKU availability), the Windows example is presented first. Automation examples are given for both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric), but no Linux shell scripting or Bash-specific guidance is provided. The portal UI instructions and screenshots do not differentiate between Windows and Linux hosting, potentially assuming a Windows-centric workflow. There is no explicit omission of Linux functionality, but the ordering and tool selection favor Windows users.
Recommendations
- Alternate the order of Windows and Linux examples, or present them together to avoid implicit prioritization.
- Provide Bash or shell script automation examples alongside PowerShell, especially for Linux users.
- Clarify in UI instructions and screenshots when steps are identical or different for Linux and Windows App Service plans.
- Explicitly mention that Azure CLI commands are cross-platform and suitable for both Windows and Linux environments.
- Consider including a table or section summarizing differences (if any) in scaling or deployment steps between Windows and Linux App Service plans.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Windows-specific information and examples are often presented first (e.g., SKU availability), and Azure PowerShell (a Windows-centric tool) is given its own section with example scripts, while Linux-native tools or shell scripting are not. The documentation mentions Windows and Linux support, but the automation and scripting focus is on Azure CLI and PowerShell, with no Linux shell or bash-specific examples. Portal instructions are generic, but the overall pattern prioritizes Windows tools and workflows.
Recommendations
- Provide bash or shell script examples for Linux users alongside PowerShell examples.
- When listing SKU availability or commands, alternate the order or present Windows and Linux options together to avoid 'Windows first' ordering.
- Explicitly mention that Azure CLI is cross-platform and can be used from Linux/macOS terminals, not just Cloud Shell.
- Include notes or examples for Linux-native automation (e.g., using bash scripts, environment variables, or integrating with Linux CI/CD pipelines).
- Where PowerShell is referenced, clarify that Azure PowerShell is available cross-platform, but also provide parity with Linux-native scripting approaches.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-hybrid-connections.md
...articles/app-service/app-service-hybrid-connections.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and tools (such as PowerShell and GUI) are often presented first or exclusively, with Linux alternatives sometimes less detailed or missing. Troubleshooting and connectivity testing examples rely on Windows-specific tools (e.g., PowerShell's Test-NetConnection), and the GUI for Hybrid Connection Manager is only available on Windows, with Linux users directed to CLI without parity in features or screenshots. Some troubleshooting steps lack Linux command equivalents.
Recommendations
- Provide Linux command-line equivalents for all Windows-specific instructions, such as replacing PowerShell's Test-NetConnection with Linux alternatives like nc (netcat) or curl.
- When presenting installation or usage instructions, alternate the order or present both Windows and Linux instructions side by side to avoid 'windows_first' bias.
- Include Linux screenshots or terminal output where Windows GUI screenshots are shown, to give Linux users visual parity.
- Expand troubleshooting sections to include Linux-native tools and commands (e.g., using nslookup, dig, nc, or telnet for connectivity tests).
- Clarify any feature gaps (such as the lack of a GUI on Linux) and, where possible, suggest open-source or cross-platform alternatives.
- Ensure that all examples, especially for common tasks (testing connectivity, managing services), are provided for both Windows and Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-encrypt-at-rest-using-cmk.md
...les/app-service/configure-encrypt-at-rest-using-cmk.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. While most command-line examples use the cross-platform Azure CLI, the only graphical tool mentioned is Azure Storage Explorer, and the instructions for generating a SAS URL link specifically to the Windows tab. There are no Linux- or macOS-specific instructions or alternative tools mentioned for uploading files or generating SAS tokens. The documentation does not acknowledge or provide parity for Linux users in these steps.
Recommendations
- Provide instructions or links for using Azure Storage Explorer on Linux/macOS, or mention that it is cross-platform.
- Include alternative methods for uploading files and generating SAS URLs using only the Azure CLI or other cross-platform tools, especially for users who may not use graphical tools.
- Avoid linking directly to Windows-specific tabs or instructions; ensure that documentation covers all supported platforms equally.
- Explicitly state when a tool or method is cross-platform, and provide any necessary installation or usage notes for Linux/macOS users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-discover-net.md
...cles/app-service/app-service-migration-discover-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on discovering ASP.NET web apps hosted on IIS web servers within VMware environments, which are Windows-centric technologies. There are no examples or mentions of discovering .NET apps hosted on Linux (e.g., Kestrel, Apache, Nginx), nor are Linux-based discovery tools or scenarios discussed. All discovery capabilities and references assume a Windows/IIS environment, omitting Linux equivalents.
Recommendations
- Include information on discovering .NET web apps hosted on Linux servers (e.g., using Kestrel, Apache, or Nginx).
- Provide parallel examples or guidance for Linux-based environments, including supported discovery tools and workflows.
- Explicitly state any limitations or lack of support for Linux-based .NET app discovery, if applicable.
- Reference Linux documentation or migration guides where relevant.
- Ensure that both Windows and Linux scenarios are addressed equally in future documentation updates.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-managed-certificate-changes-july-2025.md
...e/app-service-managed-certificate-changes-july-2025.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias primarily in the guidance for identifying impacted Azure Traffic Manager endpoints, where only a PowerShell script is provided for detection, with no equivalent Bash, Azure CLI, or cross-platform alternative. The instructions for running the script assume a Windows/PowerShell environment, and there is no mention of Linux-compatible approaches. Elsewhere, CLI and REST API examples are provided, which are cross-platform, but the exclusive use of PowerShell for a key scenario stands out.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for identifying Traffic Manager endpoints with non-Azure types, ensuring Linux and macOS users can follow the guidance without requiring PowerShell.
- When referencing scripts or tooling, mention both Windows (PowerShell) and Linux/macOS (Bash/CLI) options, or explicitly state cross-platform compatibility.
- Consider including notes or links to cross-platform tools (such as Azure CLI or Azure Cloud Shell) wherever PowerShell scripts are referenced.
- Review all example commands and scripts to ensure Linux parity, and add Linux/macOS-specific instructions where needed.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide.md
...rvice-web-nodejs-best-practices-and-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Azure App Service on Windows with iisnode. All configuration examples, troubleshooting steps, and tool references (such as web.config, iisnode, named pipes, Win32 error codes, and Kudu CMD/PowerShell) are Windows-specific. There are no Linux equivalents or cross-platform guidance, and Linux tools or patterns are not mentioned at all.
Recommendations
- Add equivalent guidance and examples for Node.js applications running on Azure App Service for Linux, including configuration, troubleshooting, and monitoring.
- Include Linux-specific tools and patterns (e.g., using PM2 or systemd for process management, nginx or Apache for reverse proxy, Linux file paths, and log locations).
- Provide examples for both Windows (web.config/iisnode) and Linux (e.g., server.js/PM2) side by side where applicable.
- Reference Linux troubleshooting steps (such as using SSH, Bash, or Linux-native diagnostic tools) and clarify which steps are Windows-only.
- Update section titles and introductions to clarify the scope (e.g., 'for Windows' vs. 'for Linux') and link to Linux-specific documentation if available.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-dotnet-framework.md
...les/app-service/configure-language-dotnet-framework.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools and environments (such as Visual Studio, Kudu, CMD, and PowerShell) for configuration and diagnostics. All file paths and commands are Windows-specific, and there are no Linux-based examples or instructions for equivalent tasks. The guidance assumes the use of Windows App Service instances and does not address Linux App Service scenarios or tooling.
Recommendations
- Add parallel Linux-based instructions and examples for each configuration task, especially for listing .NET runtimes and accessing diagnostic tools.
- Include Linux file paths and shell commands (e.g., bash) where Windows CMD/PowerShell commands are shown.
- Mention Linux App Service environments explicitly and provide guidance for users deploying to Linux-based App Service plans.
- Reference cross-platform tools (such as the Azure CLI and Kudu's Bash console) equally alongside Windows tools.
- Clarify when a step or tool is Windows-only, and provide alternatives for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-linux-open-ssh-session.md
...ticles/app-service/configure-linux-open-ssh-session.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a 'windows_first' bias by describing Windows container SSH access before Linux, despite Linux being the more common SSH use case. The Windows section is brief and lacks technical depth, while the Linux section provides detailed CLI instructions and examples. However, there is a lack of parity: the Windows section does not offer any CLI or PowerShell-based SSH access examples, nor does it mention Windows-native SSH tools or alternatives. This asymmetry may confuse users seeking equivalent Windows command-line access. Additionally, the documentation references browser-based SSH for Windows but does not clarify if similar browser SSH is available for Linux, nor does it provide PowerShell or Windows SSH client examples.
Recommendations
- Provide equivalent command-line SSH access instructions for Windows containers, including PowerShell or Windows SSH client usage if supported.
- Clarify whether browser-based SSH is available for both Linux and Windows containers, and present this information in a parallel structure.
- If CLI-based SSH is not supported for Windows containers, explicitly state this and suggest any available alternatives (such as RDP, PowerShell Remoting, or Windows OpenSSH client usage).
- Ensure that both Linux and Windows sections include comparable levels of detail and example commands, so users on either platform can follow clear, actionable steps.
- Consider restructuring the page to present Linux and Windows instructions side-by-side for each access method, to avoid implicit prioritization.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate.md
...main/articles/app-service/configure-ssl-certificate.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. PowerShell is presented alongside Azure CLI for automation, but no Linux shell or bash-specific examples are given for certificate management tasks. Windows tools such as IIS and Certreq.exe are mentioned for certificate export, while Linux equivalents are not. In several places, Windows-specific scenarios (such as outbound certificate usage in Windows container apps) are highlighted, and Linux alternatives are omitted or not equally detailed.
Recommendations
- Add explicit Linux and bash examples for certificate export, such as using OpenSSL for all relevant steps, not just one.
- When referencing Windows tools like IIS or Certreq.exe, provide equivalent Linux instructions (e.g., using OpenSSL or certtool) for exporting certificates to .pfx.
- In automation sections, include bash/Azure CLI scripts as first-class citizens, not just PowerShell.
- Clarify feature parity or differences for Linux-based App Service apps, especially in FAQ answers that currently mention only Windows container support.
- Ensure that Linux tools and workflows are mentioned at least as prominently as Windows tools, ideally before or alongside them.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-run-package.md
...s/blob/main/articles/app-service/deploy-run-package.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-style paths (e.g., D:\home\site\wwwroot) before Linux equivalents, using Windows directory separators in examples, and omitting explicit Linux/Bash command examples or Linux-specific instructions. The focus on Windows tools and patterns, such as directory structures and deployment paths, may make it less approachable for Linux users.
Recommendations
- Present both Windows and Linux directory paths and examples side-by-side, or use platform-agnostic notation where possible.
- Include explicit Linux/Bash command examples (e.g., using Bash or sh syntax) alongside Azure CLI commands.
- Clarify when instructions or paths differ between Windows and Linux App Service environments.
- Avoid using only Windows directory separators (\); include Linux-style (/) as well.
- Add troubleshooting notes or tips relevant to Linux users, such as file permission considerations.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/overview.md
...blob/main/articles/app-service/environment/overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently listing Windows workloads and SKUs before Linux equivalents, referencing Windows-specific plans and pricing as defaults, and omitting Linux-specific examples or details in several sections. Windows container limitations are called out explicitly, while Linux equivalents are not discussed in the same detail. There are no command-line or tooling examples, but the narrative and tables prioritize Windows terminology and scenarios.
Recommendations
- Alternate the order of Windows and Linux mentions throughout the documentation to avoid always listing Windows first.
- Where Windows-specific limitations or features are discussed (such as SKU support), provide equivalent information for Linux workloads and containers.
- Include explicit Linux examples or callouts in pricing, scaling, and feature difference sections, especially where Windows is referenced as the default.
- Clarify when statements apply to both Windows and Linux, or only to one, to avoid implying Windows is the primary or default scenario.
- Add a section or table column for Linux-specific limitations or features, mirroring the Windows container notes.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-dotnet-pivot.md
...ent-apps/deploy-intelligent-apps-linux-dotnet-pivot.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows/Visual Studio tools and workflows (e.g., right-clicking folders, using Visual Studio's NuGet package manager) and omitting explicit Linux or cross-platform command-line instructions for key steps. There are no Linux-specific examples or terminal commands for common developer actions, and the documentation assumes a GUI-based, Windows-centric development environment.
Recommendations
- Provide equivalent Linux and cross-platform instructions for all steps, especially for file creation and package installation (e.g., using 'dotnet new', 'dotnet add package', and editing files via CLI or cross-platform editors).
- Include terminal/command-line examples for creating and editing files, not just Visual Studio GUI actions.
- Mention and demonstrate the use of cross-platform tools (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
- Ensure that all NuGet package installation steps include both Visual Studio and dotnet CLI commands, with equal prominence.
- Explicitly state that the instructions are applicable to both Windows and Linux, and provide notes or tips for Linux users where workflows differ.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-per-app.md
...blob/main/articles/app-service/manage-scale-per-app.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell-based command-line examples for per-app scaling, without any equivalent examples for Linux users (e.g., Azure CLI, Bash). The use of PowerShell cmdlets (New-AzAppServicePlan, Set-AzAppServicePlan, Get-AzWebApp, Set-AzWebApp) is exclusive to Windows environments or requires extra setup on Linux. No Linux-native tools or shell examples are provided, and PowerShell is presented as the primary (and only) scripting interface for these operations.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and widely used on Linux.
- Provide Bash or shell script snippets where appropriate, especially for app-level configuration.
- Explicitly mention that PowerShell examples can be run on Linux with PowerShell Core, but recommend Azure CLI for native Linux workflows.
- Reorder sections or provide parallel examples so that Linux-friendly (CLI) approaches are presented alongside or before PowerShell.
- Include a note or table summarizing the available tools for both Windows and Linux users, with links to installation instructions.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. PowerShell examples are provided alongside Azure CLI, but there are no explicit Linux shell or Bash-specific examples for querying outbound IPs (other than a generic nslookup and curl). Azure PowerShell is featured equally with Azure CLI, but the PowerShell examples are not marked as Windows-specific, and there is no mention of Linux alternatives for PowerShell commands. Outbound IPv6 support is noted as available only for Windows apps, but this is a platform limitation, not a documentation bias. However, the overall pattern is that Windows/PowerShell tooling is presented as a default or first-class option, with little explicit Linux parity.
Recommendations
- Clearly label PowerShell examples as Windows-specific, and provide equivalent Bash or Linux shell commands where possible.
- For sections showing Azure CLI and PowerShell, consider using tabbed code blocks labeled 'Azure CLI (cross-platform)' and 'PowerShell (Windows)' to clarify platform applicability.
- Where PowerShell is used to retrieve properties (e.g., outbound IPs), provide a Bash/Unix shell example using Azure CLI and jq or similar tools.
- Explicitly mention when a feature or command is Windows-only, especially in the context of outbound IPv6 support.
- Add a note or section on using Azure CLI in Bash/Linux environments, and ensure all CLI examples are tested cross-platform.
- For completeness, consider referencing cross-platform tools (e.g., dig, host) alongside nslookup for DNS queries.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. It provides detailed guidance and calculations specifically for Windows Containers, including subnet sizing and networking unit calculations, while Linux-specific guidance is limited to a brief note about continuous deployment network dependencies. There are no Linux container subnet/IP calculation examples, and Windows-specific features (e.g., Windows Server Active Directory, NetBIOS) are mentioned as unsupported, but Linux equivalents are not discussed. The overall pattern is to address Windows scenarios in more detail and earlier in the document, with Linux-specific information being sparse or absent.
Recommendations
- Add equivalent subnet/IP calculation examples and networking unit guidance for Linux containers, similar to the detailed section for Windows Containers.
- Include Linux-specific limitations or considerations (e.g., supported features, known issues) in parity with the Windows-focused notes.
- Provide balanced examples and troubleshooting steps for both Windows and Linux container scenarios.
- Ensure that Linux tools, patterns, and deployment considerations are mentioned alongside Windows ones, not only as afterthoughts.
- Review the order of presentation so that Linux and Windows scenarios are treated with equal prominence and depth.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows-centric bias in several ways. It references Windows-specific tools (IIS, Procdump, PowerShell), and features (web.config, .NET Profiler for Windows), and provides examples and links that are either exclusive to or primarily focused on Windows environments. There is little to no mention of Linux-specific diagnostics, tools, or command-line examples, despite Azure App Service supporting Linux. The Kudu Console section highlights PowerShell and DOS commands, with no mention of Bash or Linux shell usage. Diagnostic and mitigation steps (such as auto-heal and profiler) are described in a way that assumes a Windows context, and Linux alternatives or differences are not addressed.
Recommendations
- Add parallel Linux examples and instructions for all diagnostic and troubleshooting steps, including enabling logs, collecting dumps, and using the Kudu Console (e.g., mention Bash shell availability and Linux-compatible tools).
- Clarify when features or tools are Windows-only (e.g., IIS logs, web.config, Procdump, .NET Profiler for Windows) and provide Linux equivalents or alternatives (such as using Application Insights with OpenTelemetry, or Linux-native profiling tools).
- Include references and links to Linux-specific documentation for App Service, such as logging, diagnostics, and scaling on Linux.
- When mentioning PowerShell or DOS commands, also provide Bash/Linux shell equivalents.
- Review all screenshots and walkthroughs to ensure Linux users are represented, or clearly state when a feature is not available on Linux.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows-first bias by providing more detailed instructions and features for Windows App Service apps, such as web server logging, detailed error messages, and failed request tracing, which are not available or documented for Linux. The examples and tooling references (e.g., Log Parser, W3C log format, .NET/ASP.NET logging) are Windows-centric, and Linux-specific guidance is minimal or absent in several sections.
Recommendations
- Provide equivalent Linux examples and instructions for all logging types where possible, or clearly state feature parity gaps.
- Add Linux-specific guidance for accessing and interpreting logs, including recommended tools and log formats.
- When referencing tools (e.g., Log Parser), suggest cross-platform or Linux-native alternatives.
- Ensure that sections are not structured with Windows as the default or primary platform; present Windows and Linux options in parallel where both are supported.
- Expand code examples to include common Linux stacks (Node.js, Python, Java) and their logging patterns.
- Clarify any limitations or differences for Linux explicitly and provide workarounds or alternatives where feasible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
...service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation assumes a development workflow centered on .NET, Azure App Service, and GitHub Codespaces, with all examples and instructions tailored to these environments. There are no explicit Linux or cross-platform terminal instructions, and the use of Azure Developer CLI (azd) and .NET CLI is described without clarifying their cross-platform compatibility. The documentation does not mention Linux-specific development environments, nor does it provide parity for Linux users who may not use Codespaces or Visual Studio. The security and deployment sections reference Azure-centric tools and patterns, which are more familiar to Windows/Azure users.
Recommendations
- Explicitly state that all CLI commands (dotnet, azd) work on Linux, macOS, and Windows, and provide installation links for each OS.
- Include instructions for running the sample app locally on Linux (e.g., using local terminal, VS Code, or JetBrains Rider) in addition to Codespaces.
- Provide alternative deployment instructions for users who do not use GitHub Codespaces, such as using the Azure CLI from a local Linux shell.
- Mention and link to Linux-friendly tools and editors (e.g., VS Code, Vim, Emacs) alongside Codespaces.
- Clarify that Azure App Service and related tools are cross-platform, and highlight any OS-specific considerations.
- If screenshots or UI steps are shown, ensure they are not Windows-specific or provide Linux/macOS equivalents where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-best-practices.md
...ain/articles/app-service/app-service-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific configuration files (such as web.config), mentioning iisnode settings for Node.js apps, and omitting equivalent Linux-native examples or tools. While there is a brief mention of running on Linux and using PM2, most configuration and troubleshooting guidance assumes a Windows/IIS environment, with no parallel Linux-native instructions or examples.
Recommendations
- For every mention of Windows-specific configuration (e.g., web.config, iisnode), provide equivalent Linux-native instructions (e.g., app settings, environment variables, or nginx/apache configuration).
- Include Linux-specific troubleshooting and configuration examples, such as using process managers like systemd or supervisord, and how to configure auto-healing or recycling on Linux-based App Service plans.
- Clarify when a feature or recommendation applies only to Windows-based App Service plans, and provide Linux alternatives or note if unavailable.
- Expand Node.js sections to include Linux-native process management and configuration (beyond PM2), and avoid assuming iisnode is always relevant.
- Where possible, present examples for both Windows and Linux platforms side by side to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows SKUs and examples are presented before Linux equivalents, and Azure PowerShell (a Windows-centric tool) is featured alongside Azure CLI. Portal instructions and screenshots use Windows terminology and UI patterns. While Linux is mentioned, it is often secondary, and there are no Linux shell or scripting examples beyond Azure CLI.
Recommendations
- Present Linux and Windows options in parallel, rather than listing Windows first.
- Include explicit Linux shell (bash) scripting examples where automation is discussed, not just Azure CLI and PowerShell.
- Ensure screenshots and UI instructions clarify any differences between Windows and Linux app workflows.
- When referencing Azure PowerShell, also mention cross-platform compatibility or alternatives for Linux users.
- Where possible, provide parity in troubleshooting and error-handling guidance for both platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-hybrid-connections.md
...articles/app-service/app-service-hybrid-connections.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions, tools, and troubleshooting steps are often presented first or exclusively, with more detailed guidance and screenshots for Windows users. Windows-specific tools (like PowerShell and GUI) are referenced without always providing equivalent Linux commands or alternatives. Some troubleshooting and connectivity test examples rely on Windows tools, and the Linux experience is sometimes described as less feature-rich (e.g., no GUI support).
Recommendations
- Provide Linux examples alongside Windows examples, especially for troubleshooting steps (e.g., include Linux equivalents for PowerShell commands like 'Test-NetConnection', such as 'nc', 'telnet', or 'curl').
- When referencing tools or commands, list both Windows and Linux options together, or alternate the order to avoid always putting Windows first.
- Expand Linux-specific guidance, such as offering more detailed CLI usage instructions and screenshots for Linux where possible.
- Where a GUI is only available for Windows, suggest or document alternative workflows for Linux users, and clarify feature parity.
- Ensure that all steps (installation, configuration, troubleshooting) are equally covered for both platforms, and avoid assuming the user is on Windows.
- Where possible, use cross-platform tools (e.g., Azure CLI, curl) in examples to promote parity.