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 701-725 of 2121 flagged pages
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 servers within VMware environments, which are Windows-centric technologies. There are no references to Linux-based hosting environments (such as Kestrel or Apache/Nginx with .NET), nor are there examples or guidance for discovering .NET apps running on Linux servers. All discovery capabilities and examples are implicitly or explicitly tied to Windows tools and patterns.
Recommendations
- Include guidance and examples for discovering .NET web apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx).
- Mention whether Azure Migrate supports discovery of .NET apps on Linux, and if so, provide instructions or links.
- Add parity in documentation by listing Linux discovery capabilities alongside Windows/IIS, or clarify if such support is not available.
- If only Windows is supported, explicitly state this limitation to set user expectations.
- Provide sample discovery flows or troubleshooting steps for both Windows and Linux environments.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and in some sections, PowerShell is shown immediately after CLI without mention of Bash or Linux-native tools. There are no Linux-specific or Bash-native command examples (e.g., using curl, jq, or REST API with bash), and the only non-Azure CLI command shown is nslookup, which is cross-platform but not explicitly called out as such. Outbound IPv6 support is noted as available only for Windows apps, but this is a platform limitation, not a documentation bias. Overall, the documentation leans toward Windows/PowerShell tooling and does not provide Linux-native or Bash-centric examples, which may disadvantage Linux users.
Recommendations
- Add explicit Bash/Linux-native command examples (e.g., using curl with Azure REST API, jq for parsing JSON, etc.) alongside Azure CLI and PowerShell.
- Clearly indicate which commands are cross-platform and which are Windows-specific.
- When listing command-line examples, alternate the order or provide tabs for 'Windows (PowerShell)', 'Linux/macOS (Bash/CLI)', and 'Azure CLI' to ensure parity.
- Where PowerShell is shown, provide equivalent Bash or shell script snippets for common tasks.
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- For sections that only show PowerShell, add a note or link to Linux/Bash alternatives.
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
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Azure App Service on Windows using iisnode. All configuration examples, troubleshooting steps, and tool references (e.g., iisnode, web.config, named pipes, Win32 error codes, Kudu CMD/PowerShell) are Windows-specific. There are no Linux equivalents or examples provided, and Linux tools or patterns are not mentioned. The document assumes the use of Windows file paths and debugging tools, and does not address how to perform similar tasks on Linux-based App Service environments.
Recommendations
- Add equivalent sections or notes for Linux-based Azure App Service environments, including differences in configuration and troubleshooting.
- Provide Linux-specific examples (e.g., using PM2 or systemd instead of iisnode, nginx or Apache configuration, Linux file paths, and log locations).
- Include troubleshooting steps and diagnostic commands for Linux (e.g., using SSH, Bash, Linux process monitoring tools like top/htop, journalctl, etc.).
- Mention cross-platform Node.js debugging tools and how to use them on both Windows and Linux.
- Clearly indicate at the top of the document that the content is Windows-specific, and link to a parallel Linux-focused guide if available.
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 missing or less detailed. Troubleshooting and testing examples use Windows-specific commands (e.g., PowerShell's Test-NetConnection), and the GUI for Hybrid Connection Manager is only available on Windows. Linux users are directed to CLI usage, but equivalent Linux-native troubleshooting commands are not provided. Some sections, such as troubleshooting, lack parity in Linux examples.
Recommendations
- Provide Linux-native command examples alongside Windows ones (e.g., use 'nc' or 'telnet' for TCP connectivity tests instead of only PowerShell's Test-NetConnection).
- Present Windows and Linux instructions in parallel or in a more balanced order, rather than always listing Windows first.
- Where a GUI is only available on Windows, offer equivalent CLI workflows for Linux with screenshots and step-by-step instructions.
- In troubleshooting sections, include Linux-specific commands for DNS resolution (e.g., 'dig', 'host', or 'nslookup') and network connectivity testing.
- Explicitly state any feature gaps or differences between Windows and Linux, and provide workarounds or alternatives where possible.
- Ensure that all critical workflows (installation, configuration, troubleshooting) have complete Linux coverage, not just references to CLI.
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 Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing PowerShell scripts as the only automation example for identifying impacted Traffic Manager endpoints, without offering equivalent Bash or cross-platform (Linux/macOS) alternatives. The guidance for running scripts assumes a Windows/PowerShell environment, and there is no mention of Linux shell, Bash, or cross-platform scripting options. This may hinder Linux/macOS users or those working in non-Windows environments.
Recommendations
- Provide Bash or Azure CLI script equivalents for all PowerShell automation examples, especially for identifying Traffic Manager endpoints.
- Explicitly mention that the PowerShell scripts can be run on PowerShell Core (which is cross-platform), or provide instructions for Linux/macOS users.
- When referencing scripts, offer both Windows (PowerShell) and Linux/macOS (Bash/CLI) options side by side, or clearly indicate platform compatibility.
- Ensure that all automation and scripting guidance is accessible to users regardless of their operating system.
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 demonstrates a Windows bias by prioritizing Windows-centric tools and workflows (e.g., Visual Studio, right-click actions, NuGet package manager) and omitting explicit Linux or cross-platform alternatives. There are no Linux-specific instructions or examples, and the use of GUI-based steps (like right-clicking folders) assumes a Windows development environment. Command-line instructions are referenced but not shown, and Linux-friendly editors or deployment methods are not mentioned.
Recommendations
- Provide explicit Linux and cross-platform instructions alongside Windows steps, such as using the dotnet CLI for project/file creation and NuGet package installation.
- Include examples for common Linux editors (e.g., VS Code, Vim, nano) and file system navigation.
- Replace or supplement GUI-based instructions (e.g., right-click to add files) with command-line equivalents that work on all platforms.
- Add deployment guidance for Linux-based development environments, including relevant CLI commands and troubleshooting tips.
- Ensure that all referenced tools and workflows (e.g., package management, environment variable configuration) have Linux-compatible alternatives clearly documented.
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
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All runtime version examples and tooling references (such as Kudu, CMD, PowerShell, and Visual Studio) are specific to Windows environments. There are no Linux-specific instructions or examples, nor is there mention of Linux-based deployment or configuration patterns for ASP.NET apps. The documentation assumes the use of Windows App Service instances and omits guidance for Linux-based App Service or containers, despite a brief mention in the introductory note.
Recommendations
- Add parallel Linux-based examples for listing .NET runtime versions, such as using SSH or the Linux Kudu Bash console.
- Include instructions for configuring and deploying ASP.NET apps on App Service Linux plans, including differences in environment variables, file paths, and diagnostic logging.
- Mention and provide examples for Linux-based deployment tools (e.g., dotnet CLI, VS Code, GitHub Actions) alongside Visual Studio.
- Clarify when instructions are Windows-specific and provide links or sections for Linux/container-based workflows.
- Highlight any differences in accessing diagnostic logs or environment variables between Windows and Linux App Service environments.
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 exhibits a Windows-first bias: logging types and features are described for Windows in greater detail and are presented before Linux equivalents. Several logging features (web server logging, detailed error messages, failed request tracing) are described only for Windows, with no Linux instructions or explicit mention of Linux support or alternatives. Tooling references (e.g., Log Parser, W3C log format) are Windows-centric. Linux logging capabilities are described in less detail, and some features are noted as unavailable or limited for non-Windows stacks.
Recommendations
- Provide equivalent Linux/container instructions for all logging types, or explicitly state when features are unavailable on Linux.
- Add Linux-specific examples and clarify differences in log formats, locations, and access methods.
- Mention and recommend cross-platform or Linux-native tools for log analysis (e.g., grep, less, jq) alongside or instead of Windows tools like Log Parser.
- Ensure parity in detail and structure between Windows and Linux sections, including tables and step-by-step guides.
- Clearly indicate feature availability per platform in all relevant sections, not just in summary tables.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-data-sources.md
...es/app-service/configure-language-java-data-sources.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Linux and Windows instructions for configuring data sources in Tomcat and JBoss on Azure App Service. However, in the Tomcat server-level configuration section, the Windows instructions are more detailed and make heavy use of Windows-specific tools and patterns, such as PowerShell scripts and Windows environment variables. The Windows section is longer and more prescriptive, with explicit PowerShell automation, while the Linux section relies on shell scripting and manual steps. The documentation also introduces Windows-specific concepts (e.g., copying Tomcat to a local directory, using %LOCAL_EXPANDED%, and setting up startup.cmd) that have no direct Linux equivalent, and the PowerShell script is given in full, whereas the Linux script is more generic. The Linux instructions are present and functional, but the Windows approach is more prominent and tool-specific.
Recommendations
- Provide equally detailed Linux shell script examples for automating Tomcat server-level configuration, similar to the PowerShell script given for Windows.
- Where possible, present Linux and Windows instructions in parallel or with equal prominence, rather than giving a longer, more detailed Windows section.
- Include Linux-native automation tools (e.g., bash scripts, systemd service files, or cloud-init) as first-class citizens, not just as generic shell snippets.
- Avoid Windows-specific terminology (e.g., %LOCAL_EXPANDED%, startup.cmd) without providing clear Linux equivalents.
- Consider providing a table or side-by-side comparison of steps for both platforms to ensure parity and clarity.
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
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows-centric bias in several areas. Diagnostic and troubleshooting tools such as Kudu and Procdump are described with a focus on Windows environments, and PowerShell/DOS commands are mentioned as the default for the debug console. Application Insights Profiler is linked specifically to Windows instructions. There are no explicit Linux or cross-platform examples, and Linux-native tools or workflows are not discussed. Azure PowerShell is recommended for app management without mention of Azure CLI or Linux shell equivalents.
Recommendations
- Add equivalent Linux examples and instructions throughout, especially for diagnostic and troubleshooting steps.
- Mention and provide examples for using Azure CLI and Bash shell alongside or instead of Azure PowerShell.
- Clarify which features/tools are available on both Windows and Linux App Service plans, and note any differences.
- Include Linux-native tools (e.g., strace, lsof, top) for troubleshooting and explain how to access them in App Service for Linux.
- Update links and references to include both Windows and Linux documentation where available.
- In sections mentioning Kudu, clarify the differences in available commands and features between Windows and Linux App Service environments.
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 page exhibits a Windows-first bias by referencing Windows-style paths (e.g., D:\home\site\wwwroot) before Linux equivalents, and by providing operational details and examples primarily in the context of Windows environments. There is a lack of explicit Linux or cross-platform command examples, and some instructions (e.g., manual directory creation) only mention Windows paths. Linux-specific nuances are only briefly mentioned, and there are no Linux shell or file system examples.
Recommendations
- Provide Linux path examples (e.g., /home/site/wwwroot) alongside Windows paths in all relevant sections, not just in passing.
- Include explicit Linux/macOS shell command examples where manual file operations are described (e.g., creating directories, managing files).
- Clarify when instructions or behaviors differ between Windows and Linux App Service environments.
- Ensure that all file paths, deployment locations, and troubleshooting steps are described for both Windows and Linux environments.
- Add a table or section summarizing key differences and commands for both Windows and Linux App Service plans.
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
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for command-line operations, referencing Azure PowerShell cmdlets exclusively, and omitting equivalent instructions for Linux users (such as Azure CLI or Bash). The use of PowerShell as the primary automation tool and the absence of cross-platform command-line examples make it less accessible for developers working on Linux or macOS.
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 examples are also available on Linux and macOS (if true), or clarify platform requirements.
- Provide Bash script examples where appropriate, especially for automation scenarios.
- Ensure that documentation sections do not assume Windows as the default environment by presenting cross-platform tools (e.g., Azure CLI) first or in parallel with PowerShell.
- Include a note or table summarizing the available tools (PowerShell, Azure CLI, ARM templates) and their platform compatibility.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-local-cache.md
...blob/main/articles/app-service/overview-local-cache.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows-first bias by referencing Windows-style paths (e.g., D:\home), using Windows terminology and folder structures throughout, and omitting Linux-specific equivalents or examples. The only tool mentioned for disk usage is a Windows-centric site extension, and there are no Linux command-line or file path examples. While there is a note about Linux containers, the main documentation assumes a Windows environment and does not provide parity for Linux users.
Recommendations
- Provide Linux-specific examples, including file paths (e.g., /home/site) and environment variables as they appear on Linux-based App Service plans.
- Mention and demonstrate how to check disk usage and environment variables using Linux tools (e.g., du, df, or bash commands) in addition to the Azure Web Apps Disk Usage extension.
- Clarify differences in local cache behavior and configuration between Windows and Linux App Service plans, including any limitations or alternative approaches.
- Ensure that all instructions and best practices are applicable to both Windows and Linux environments, or clearly indicate when a feature is Windows-only.
- Add a section or callouts for Linux users, summarizing key differences and providing links to relevant Linux documentation.
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 exhibits a mild Windows bias. It provides detailed calculations and limits specifically for Windows Containers, while Linux-specific guidance is limited to a brief note about network dependencies for Linux continuous deployment. There are no Linux container-specific examples or parity in subnet/IP calculations. Windows terminology and features (e.g., Windows Server Active Directory, NetBIOS) are mentioned without Linux equivalents or clarifications. The overall structure and examples prioritize Windows scenarios, with Linux-specific information appearing only as exceptions or footnotes.
Recommendations
- Add a parallel section for Linux Containers, including subnet/IP address calculation examples and any unique limitations or considerations.
- Where Windows-specific features or limitations are mentioned (e.g., Windows Server Active Directory, NetBIOS), clarify Linux equivalents or explicitly state if not applicable.
- Provide Linux-focused deployment and configuration examples, especially for common scenarios such as scaling, networking, and troubleshooting.
- Ensure that Linux and Windows guidance are presented with equal prominence and detail, ideally side-by-side or in clearly labeled subsections.
- Expand the Linux continuous deployment section to include more comprehensive guidance, such as required endpoints, troubleshooting tips, and best practices.
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 GUI options for Windows users. Linux support is present but less emphasized, with some features (like the GUI) unavailable and some troubleshooting steps (e.g., PowerShell commands) lacking Linux equivalents.
Recommendations
- Provide Linux examples alongside Windows ones, especially in troubleshooting sections (e.g., suggest 'nc' or 'telnet' as alternatives to 'Test-NetConnection' in PowerShell).
- Avoid presenting Windows instructions or tools first by default; use parallel tabbed instructions for both platforms wherever possible.
- Where a feature is Windows-only (e.g., GUI), clearly state this early and offer equivalent CLI workflows for Linux, with equal detail and screenshots.
- In troubleshooting, include Linux-native commands for network testing (e.g., 'nslookup', 'dig', 'nc', 'curl') and explain how to interpret their results.
- Balance the use of screenshots and step-by-step guides for both Windows and Linux, ensuring Linux users have visual aids and detailed instructions.
- When referencing tools or commands, avoid assuming PowerShell is available; always provide a Linux alternative.
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 demonstrates a subtle Windows bias by referencing Windows-centric tools and configuration patterns (such as web.config and iisnode) without providing equivalent Linux-native examples or alternatives. While there is a brief mention of Linux (regarding PM2 for Node.js), most configuration and troubleshooting guidance assumes a Windows environment or omits Linux-specific instructions.
Recommendations
- For features like auto-healing, provide Linux-native configuration examples (e.g., using app settings or startup scripts) alongside web.config instructions.
- When referencing iisnode or web.config, clarify their applicability to Windows-based App Service plans and provide alternatives for Linux-based plans (such as using process managers like PM2 or configuring environment variables).
- Include explicit Linux examples for diagnostics, scaling, and backup configuration, ensuring parity with Windows instructions.
- When mentioning tools or configuration files (like web.config), always note their platform specificity and link to Linux equivalents or documentation.
- Review all troubleshooting and best practice sections to ensure that both Windows and Linux workflows are equally represented and easy to follow.
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 moderate Windows bias. In sections where both Windows and Linux are relevant (such as SKU availability), the Windows example is presented first, and the Linux example is secondary. The automation section provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples, but does not mention Linux-native scripting tools or workflows. The portal instructions and screenshots do not clarify any differences for Linux users, and the 'Development tools' section references features (like 'Clone app') without noting platform-specific considerations.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid 'windows_first' bias.
- Explicitly mention that Azure CLI is cross-platform and suitable for both Windows and Linux users.
- If providing PowerShell examples, consider also providing Bash or shell script equivalents for Linux users.
- Clarify in portal instructions and screenshots whether the experience is identical for Linux and Windows App Service plans, or note any differences.
- In the 'Automate with scripts' section, add a Bash script example for Linux users, especially for tasks like redeployment or automation.
- Review tool recommendations to ensure Linux-native tools and workflows are equally represented and explained.
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
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows terminology and tools (such as PowerShell) are mentioned prominently and often before their Linux equivalents. The 'Automate with scripts' section provides both Azure CLI and PowerShell examples, but PowerShell is a Windows-centric tool. There are no explicit Linux shell (bash) or scripting examples, and the documentation does not mention Linux-native tools or patterns. In the availability section, Windows SKU availability is listed before Linux, and the overall tone and examples lean towards Windows-first usage.
Recommendations
- Provide bash shell scripting examples alongside PowerShell for automation, especially in the 'Automate with scripts' section.
- When listing availability or features, present Linux and Windows options in parallel or alternate the order to avoid Windows-first bias.
- Mention Linux-native tools or scripting environments (e.g., bash, sh) where automation is discussed.
- Clarify in the prerequisites and automation sections that all CLI commands work cross-platform, and explicitly state any differences or requirements for Linux users.
- Include screenshots or walkthroughs from both Windows and Linux perspectives where applicable, especially for command-line operations.
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 demonstrates a strong Windows bias. All migration tools and examples focus exclusively on migrating from Windows environments, specifically IIS servers, and make heavy use of Windows-specific tools such as the App Service Migration Assistant (MSI installer) and PowerShell scripts. There is no mention of Linux-based hosting environments, migration from Linux web servers, or equivalent Linux tooling. The documentation does not provide guidance or examples for users running .NET apps on Linux servers (e.g., Apache, Nginx, Kestrel), nor does it mention cross-platform migration scenarios.
Recommendations
- Add sections or examples for migrating .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel) to Azure App Service.
- Include Linux-specific migration tools or manual migration steps, such as using rsync, SCP, or Azure CLI on Linux.
- Provide parity in documentation by offering both Windows and Linux migration paths, including sample scripts and commands for each.
- Mention and link to any available cross-platform or Linux-compatible migration tools, or clarify if such tools are not available.
- Ensure that PowerShell scripts are accompanied by Bash or shell script equivalents where possible.
- Explicitly state the limitations or lack of support for Linux-based migrations if that is the case, and provide guidance for manual migration.
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 page exhibits a Windows-first bias by referencing Windows file paths (e.g., D:\home\site\wwwroot) before Linux equivalents, describing deployment behaviors primarily in terms of Windows directories, and omitting explicit Linux command-line or file path examples. There is also an assumption of Windows-style directory structures and deployment patterns, with little to no mention of Linux-specific nuances or parity in examples.
Recommendations
- Provide Linux-specific examples and file paths (e.g., /home/site/wwwroot) alongside Windows ones in all relevant sections.
- Explicitly mention Linux behaviors and differences where applicable, such as directory permissions, file system case sensitivity, and deployment nuances.
- Include sample commands and troubleshooting steps that are relevant to Linux environments (e.g., bash commands, Linux CLI nuances).
- Ensure that all references to file paths, deployment directories, and manual steps are presented in both Windows and Linux formats.
- Clarify any differences in behavior or limitations between Windows and Linux App Service plans.
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 exclusively discusses discovery of ASP.NET web apps hosted on IIS servers within VMware environments, which are Windows-centric technologies. There are no references to Linux-based web servers (such as Apache or Nginx), nor are there any examples or guidance for discovering .NET apps hosted on Linux. All tools and processes described (e.g., Azure Migrate appliance, IIS) are Windows-specific, and Linux scenarios are entirely omitted.
Recommendations
- Include information about discovering .NET web apps hosted on Linux servers, such as those running on Apache, Nginx, or Kestrel.
- Provide equivalent discovery guidance and tooling for Linux environments, or clearly state any current limitations.
- Add examples or documentation links for Linux-based .NET app discovery and migration.
- Ensure that references to tools and processes are inclusive of both Windows and Linux hosting scenarios, or explicitly clarify the scope.
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 Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing PowerShell scripts as the only example for scripting/automation tasks (such as identifying Traffic Manager endpoints), referencing PowerShell before or instead of cross-platform alternatives, and omitting equivalent Bash or Linux shell examples. There is no mention of Linux/macOS-compatible scripting or tooling for users who do not use Windows or PowerShell.
Recommendations
- Provide Bash/Azure CLI script examples alongside PowerShell scripts for all automation and resource identification tasks.
- Explicitly mention that PowerShell scripts can be run cross-platform using PowerShell Core, or provide alternative instructions for Linux/macOS users.
- When referencing scripts or tools, avoid assuming the user is on Windows; instead, present both Windows and Linux options, or clarify cross-platform compatibility.
- For each scenario where a PowerShell script is linked or described, add a corresponding Bash/Azure CLI example or link to a GitHub repository with cross-platform scripts.
- Instruct users on how to use Azure CLI (which is cross-platform) for resource queries and management, not just PowerShell.
- Review all step-by-step instructions to ensure they are not Windows-centric and that Linux users are equally supported.
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
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Azure App Service on Windows using iisnode. All configuration and troubleshooting steps are tailored to Windows, with exclusive references to Windows-specific tools (e.g., iisnode, web.config, named pipes, Win32 error codes, Kudu CMD/PowerShell). There are no examples or guidance for Linux-based App Service or cross-platform scenarios, and Linux equivalents (such as PM2, systemd, or nginx) are not mentioned.
Recommendations
- Add equivalent guidance and examples for Node.js applications running on Azure App Service Linux, including configuration, troubleshooting, and monitoring steps.
- Include Linux-specific tools and patterns (e.g., PM2, systemd, nginx, environment variables) alongside or before Windows/iisnode examples.
- Provide cross-platform troubleshooting steps and clarify which instructions apply only to Windows.
- Offer PowerShell and Bash (or shell) command examples side-by-side where relevant.
- Reference Linux log file locations and diagnostic tools (e.g., /var/log, journalctl) in troubleshooting sections.
- Link to Linux-focused documentation or external resources for parity.
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 Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by exclusively referencing Azure Storage Explorer (a GUI tool with a primary focus on Windows) for uploading files and generating SAS tokens, and by linking to Storage Explorer instructions with a Windows-specific tab in the URL. There are no examples or instructions for performing these tasks using Linux-native tools (such as the Azure CLI, azcopy, or command-line methods). The rest of the guide uses Azure CLI, which is cross-platform, but the initial steps and tooling references favor Windows users.
Recommendations
- Provide equivalent instructions for uploading files and generating SAS tokens using Azure CLI and/or azcopy, which are cross-platform and work on Linux, macOS, and Windows.
- Avoid linking to Storage Explorer documentation with a Windows-specific tab in the URL, or provide links/tabs for Linux and macOS as well.
- Explicitly mention that Storage Explorer is available on multiple platforms, and provide download links for all supported OSes.
- Where GUI tools are referenced, also provide command-line alternatives for Linux users.
- Add a section or callout for Linux/macOS users to ensure parity in the onboarding and setup experience.
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
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based deployment and configuration patterns for ASP.NET apps. All runtime version discovery commands use Windows file paths and Kudu's CMD/PowerShell consoles, with no mention of Linux equivalents. Visual Studio (a Windows-centric tool) is assumed as the primary deployment method, and there are no examples or guidance for Linux-based App Service environments or tools. Linux or cross-platform scenarios are only mentioned in passing, with no actionable instructions.
Recommendations
- Add explicit instructions and examples for configuring ASP.NET apps on Linux-based App Service plans, including how to check installed .NET runtimes and access diagnostic tools.
- Provide Linux shell (bash) equivalents for all file system and runtime inspection commands, and clarify when a command is Windows-specific.
- Include deployment guidance using cross-platform tools (such as the .NET CLI and VS Code) alongside Visual Studio instructions.
- Clearly indicate which instructions apply to Windows, Linux, or both, and ensure Linux guidance is not relegated to footnotes or external links.
- Mention and demonstrate use of Kudu SSH/bash console for Linux App Service, not just CMD/PowerShell for Windows.