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 501-525 of 2121 flagged pages
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 primarily referencing Windows-centric development tools and workflows, such as Visual Studio and right-click context menu actions, without providing equivalent instructions for Linux environments. Package installation is described first via the Visual Studio NuGet package manager, with CLI instructions mentioned secondarily. There are no explicit Linux or cross-platform editor examples (e.g., VS Code, JetBrains Rider), nor are Linux-specific commands or patterns (such as file creation via terminal or use of Linux environment variables) provided. The instructions for managing secrets and environment variables focus on the Azure portal and do not mention alternatives like editing configuration files or using CLI tools in Linux shells. Overall, the page assumes a Windows development environment and omits guidance for Linux users.
Recommendations
- Provide explicit instructions for creating and editing files using cross-platform tools (e.g., VS Code, nano, vim) and terminal commands.
- Include package installation examples using the dotnet CLI (e.g., 'dotnet add package Microsoft.SemanticKernel') before or alongside Visual Studio NuGet manager instructions.
- Describe how to manage environment variables and secrets using CLI tools (e.g., Azure CLI, Bash) and configuration files, not just through the Azure portal UI.
- Avoid referencing right-click context menu actions; instead, use instructions that work in any OS (e.g., 'create a new file named OpenAI.razor in the Pages folder').
- Mention Linux and macOS as supported platforms for .NET and Azure App Service, and provide troubleshooting tips or links for those environments.
- Ensure all code and deployment steps are cross-platform, and clarify any OS-specific requirements or differences.
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
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell examples are provided alongside Azure CLI, but no Linux shell equivalents (e.g., Bash scripts or REST API calls) are shown for tasks like retrieving outbound IP addresses. The outbound IPv6 support section explicitly states that outbound IPv6 is only available for Windows apps, with Linux apps limited to IPv4. Windows-oriented tools (PowerShell) are featured, and Windows-specific features are mentioned before Linux equivalents or limitations.
Recommendations
- Provide Bash and REST API examples for all commands, especially for retrieving IP addresses, to ensure parity for Linux users.
- Clarify if PowerShell commands can be run on Linux (via PowerShell Core), or offer equivalent Bash/CLI instructions.
- Explicitly mention Linux limitations and roadmap for outbound IPv6 support, and provide alternative solutions for Linux users where possible.
- Ensure that examples and instructions are presented in a platform-neutral order (e.g., Azure CLI first, then PowerShell), or grouped by OS.
- Where features are Windows-only, suggest workarounds or alternatives for Linux users, and link to relevant documentation.
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 demonstrates a Windows bias by referencing Windows-specific tools (IIS, Procdump, web.config), focusing on PowerShell for management, and linking to Windows-centric resources. There is little to no mention of Linux equivalents or guidance for Linux-based App Service environments, and examples or instructions for Linux users are missing.
Recommendations
- Include Linux-specific instructions and examples for enabling diagnostics, collecting logs, and troubleshooting (e.g., mention differences in log locations, diagnostic tools, and configuration files for Linux App Service).
- When referencing tools like Kudu, clarify differences in available features and commands between Windows and Linux App Service plans.
- Provide parity in management examples, such as using Azure CLI or Bash scripts alongside PowerShell, and avoid presenting PowerShell as the only or primary option.
- When discussing configuration (e.g., auto-heal via web.config), note the Linux equivalent (such as app settings or other configuration mechanisms).
- Link to Linux-focused documentation or sections, and ensure that all referenced tools/resources are applicable to both Windows and Linux, or clearly state platform limitations.
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
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific paths (e.g., D:\home), using Windows-centric terminology and folder structures, and mentioning Windows containers before Linux containers. There are no Linux-specific examples, commands, or equivalent Linux filesystem paths provided. The only tool mentioned for disk usage is Azure Web Apps Disk Usage, with no mention of Linux alternatives. The documentation does not provide parity for Linux users in terms of examples, troubleshooting, or operational details.
Recommendations
- Include Linux-specific examples, such as Linux filesystem paths (/home/site, /home/LogFiles, etc.) and how local cache works on Linux-based App Service plans.
- Mention Linux tools or commands for checking disk usage (e.g., du, df) alongside Azure Web Apps Disk Usage.
- Clarify differences in behavior and support for local cache between Windows and Linux App Service environments, including any limitations or alternative features.
- Provide troubleshooting steps and environment variable inspection methods for Linux environments (e.g., using SSH, Bash commands).
- Ensure that references to containers mention Linux and Windows equivalently, and provide links or instructions for both.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-managed-identity.md
...main/articles/app-service/overview-managed-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is heavily featured as a primary automation and scripting tool, with numerous examples and dedicated tabs. There are no explicit Linux shell (bash, sh) or platform-specific examples, and Windows-centric tools (PowerShell, Azure PowerShell module) are referenced before or instead of Linux alternatives. The lack of Linux-specific instructions or parity in command-line examples may hinder Linux users, especially those who do not use PowerShell.
Recommendations
- Add explicit bash or shell script examples alongside PowerShell for all CLI operations, especially for token retrieval and identity management.
- Clarify that Azure CLI commands work cross-platform and provide sample usage in Linux environments (e.g., with environment variable syntax differences).
- Include troubleshooting notes or platform-specific caveats for Linux users, such as file permissions, environment variable access, or REST endpoint invocation.
- Where PowerShell is used for scripting, offer equivalent bash scripts or Python snippets for Linux users.
- Review and update related tutorials and linked content to ensure Linux parity and visibility.
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 Windows-first bias by providing detailed subnet/IP calculations specifically for Windows Containers, mentioning Windows Server Active Directory, and referencing Windows-specific features (e.g., NetBIOS). Linux-specific guidance is minimal and only briefly mentioned (e.g., a single note about Linux continuous deployment network dependencies). There are no Linux container or Linux-specific configuration examples, and troubleshooting steps focus on Azure CLI (cross-platform) but do not provide parity for Linux-specific scenarios or tools.
Recommendations
- Add equivalent subnet/IP calculation examples for Linux containers, highlighting any differences in resource usage or configuration.
- Include Linux-specific limitations or considerations (if any), such as integration with Linux authentication or file systems.
- Provide Linux-focused troubleshooting steps or references, especially for common issues encountered with Linux-based App Service deployments.
- Ensure that Linux and Windows examples are presented with equal prominence, or clarify when guidance applies to both platforms.
- Mention Linux equivalents for Windows-specific features (e.g., alternatives to Windows Server Active Directory or NetBIOS for Linux environments).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/reference-app-settings.md
...ob/main/articles/app-service/reference-app-settings.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways. Windows-specific tools, paths, and conventions (such as 'D:\home', 'w3wp.exe', 'applicationHost.config', and references to IIS and Web Deploy/MSDeploy) are mentioned frequently and often before their Linux equivalents. Many environment variables and examples are described in terms of Windows usage, with Linux alternatives either missing, less detailed, or mentioned secondarily. Some features are described as 'native Windows apps only' or default to Windows behaviors, and references to Microsoft documentation (such as time zones) link to Windows-specific resources. Build automation and deployment sections provide more detail for Windows/Kudu than Linux/Oryx. There are also cases where Linux examples or usage patterns are omitted or less emphasized.
Recommendations
- Ensure Linux equivalents are always mentioned alongside Windows-specific instructions, with equal detail and prominence.
- Provide Linux-specific examples (e.g., file paths, process names, configuration files) wherever Windows examples are given.
- Avoid defaulting to Windows terminology (such as 'D:\home')—use platform-agnostic notation or list both Windows and Linux paths.
- Reference Linux documentation (such as time zone lists) in addition to or instead of Windows documentation.
- Balance build automation and deployment sections so that Oryx/Linux coverage matches Kudu/Windows coverage.
- Where features are Windows-only, clearly indicate Linux alternatives or limitations.
- Review all environment variable descriptions for platform bias and add Linux context where missing.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates Windows bias by presenting Visual Studio (a Windows-centric IDE) and its Package Manager Console (PowerShell-based) as the primary method for installing NuGet packages, with these instructions appearing before or alongside the cross-platform .NET CLI. There is no mention of Linux-specific tooling, editors, or package installation workflows. All examples and instructions assume a Windows development environment, omitting Linux alternatives or parity.
Recommendations
- Add explicit instructions for installing NuGet packages on Linux/macOS using the .NET CLI, and clarify that the CLI works cross-platform.
- Mention and provide examples for using popular cross-platform editors (e.g., VS Code) and their workflows for package management.
- Avoid referencing Windows-only tools (such as Visual Studio's Package Manager Console) without offering Linux/macOS equivalents.
- Include notes or sections on running and deploying .NET web apps on Linux-based App Service environments.
- Ensure that all command-line instructions are platform-neutral or provide platform-specific alternatives where necessary.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-storage.md
...cles/app-service/scenario-secure-app-access-storage.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation instructions for required NuGet packages using both the .NET Core CLI and the Visual Studio Package Manager Console, but the latter is a Windows-only tool and is presented second. There are no explicit Linux-specific instructions or examples, and the only IDE mentioned is Visual Studio, which is primarily associated with Windows. No Linux-native tools or editors are referenced, and there are no bash or shell examples.
Recommendations
- Add explicit instructions for installing the packages on Linux, such as using the .NET CLI in a bash shell.
- Mention cross-platform editors like VS Code and provide guidance for users on Linux and macOS.
- Clarify that the .NET Core CLI commands work on Windows, Linux, and macOS, and consider listing them first.
- Avoid referencing Windows-only tools (like Visual Studio's Package Manager Console) without providing Linux/macOS alternatives.
- Include a note or section for Linux/macOS users to ensure parity and inclusivity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-app-access-sql-database-as-user-dotnet.md
...utorial-connect-app-access-sql-database-as-user-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While Azure CLI is used for most automation steps (which is cross-platform), several sections reference Windows-centric tools (such as SQL Server Management Studio and Active Directory Integrated authentication), and the only IDE-specific publishing instructions are for Visual Studio (Windows). There are no explicit Linux or macOS examples for local debugging, publishing, or database management, and Windows tools are mentioned first or exclusively in several places.
Recommendations
- Add explicit instructions for local debugging and publishing from Linux/macOS environments, including examples using VS Code, JetBrains Rider, or command-line .NET tools.
- Include cross-platform alternatives to SQL Server Management Studio, such as Azure Data Studio, and show how to use sqlcmd on Linux/macOS.
- When mentioning authentication flows, clarify how they work on non-Windows platforms and provide examples for those environments.
- Avoid referencing Windows-only features (such as Integrated Windows authentication) without also describing Linux/macOS equivalents or alternatives.
- Ensure screenshots and step-by-step instructions for portal or CLI actions are not Windows-centric, and add notes for Linux/macOS users where workflows differ.
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. Examples and tool references (e.g., Log Parser, W3C log format) 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 supported, or clearly state if a feature is unavailable on Linux.
- Include Linux-native tools and patterns for accessing and analyzing logs (e.g., using tail, less, grep, or open-source log viewers) alongside Windows tools.
- Ensure that sections such as 'Enable web server logging', 'Log detailed errors', and 'Access log files' contain explicit Linux guidance or alternatives.
- Clarify differences in feature availability between Windows and Linux in summary tables and throughout the documentation.
- Add code and configuration examples for popular Linux stacks (Node.js, Python, Java) where only .NET/Windows examples are currently provided.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-msi-sql-database.md
...icles/app-service/tutorial-connect-msi-sql-database.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows/Visual Studio workflows, providing PowerShell and Windows tool examples, and omitting explicit Linux development environment instructions. Key steps such as connecting to SQL Database and project modification are described in the context of Windows tools (Visual Studio, PowerShell), with no equivalent Linux or cross-platform guidance. Visual Studio for Windows is featured before cross-platform editors, and there are no examples for Linux-based SQL tools or development environments.
Recommendations
- Add explicit instructions and examples for Linux and macOS development environments, including using VS Code and JetBrains Rider.
- Provide SQL Database connection steps using cross-platform tools such as sqlcmd (with installation instructions for Linux/macOS) or Azure Data Studio.
- Include CLI-based workflows for project modification and publishing, avoiding reliance on Visual Studio GUI steps.
- Ensure all PowerShell examples have Bash or shell equivalents.
- Reorder sections to present cross-platform or neutral tooling (e.g., Azure CLI, VS Code) before or alongside Windows-specific tools.
- Clarify that all steps can be performed on Linux/macOS, and provide troubleshooting notes for non-Windows environments.
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 tools and patterns (such as web.config and iisnode) without providing equivalent Linux guidance or examples. Linux-specific instructions are minimal and appear after Windows-centric advice. There are no Linux command-line examples or references to Linux-native configuration files, and the use of Windows terminology (like web.config) is presented as the default.
Recommendations
- Provide Linux-specific configuration examples alongside Windows examples, such as using app settings or environment variables instead of web.config for auto-healing.
- Include Linux-native process management and monitoring tools (e.g., systemd, supervisord) in addition to iisnode and web.config.
- When mentioning tools like iisnode or web.config, clarify their applicability (Windows only) and immediately offer Linux alternatives.
- Add examples for configuring Node.js apps on Linux App Service (e.g., startup commands, environment variables) and reference Linux-specific documentation.
- Ensure that troubleshooting and best practice sections include parity for both Windows and Linux hosting environments.
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 demonstrates a Windows-first bias by presenting Windows SKU availability before Linux, providing Azure PowerShell automation examples (which are Windows-centric), and referencing Windows-specific patterns and tools. While Linux is mentioned and a Linux-specific CLI command is given for SKU availability, there are no Linux shell (bash) or scripting examples, and PowerShell is presented as a primary automation tool. The documentation does not offer parity in Linux-native scripting or tooling guidance.
Recommendations
- Present Linux and Windows options in parallel, or alternate which is shown first to avoid a Windows-first impression.
- Include Linux-native automation examples, such as bash scripts using Azure CLI, alongside PowerShell examples.
- Clarify that Azure CLI is cross-platform and can be used on both Windows and Linux, and provide example commands in both environments.
- Where PowerShell is referenced, note its availability on Linux, or provide bash equivalents.
- Ensure that any references to Windows-specific tools or patterns are matched with Linux equivalents, or clearly state any platform limitations.
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
Summary
The documentation demonstrates a Windows bias by providing PowerShell scripts as the only automation example for identifying impacted Traffic Manager profiles, without offering equivalent Bash, Azure CLI, or cross-platform alternatives. References to 'Open PowerShell' and running '.ps1' scripts assume a Windows environment. No Linux shell or Bash examples are provided for these scenarios, and there is no mention of how to perform these tasks on non-Windows platforms.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for all PowerShell automation examples, ensuring Linux and macOS users can perform the same tasks.
- When referencing downloadable scripts, offer both PowerShell and Bash versions, or clarify how to run PowerShell scripts on Linux/macOS (e.g., via PowerShell Core).
- Avoid instructions that assume the user is on Windows (e.g., 'Open PowerShell'); instead, use cross-platform language such as 'Open your terminal or command prompt'.
- Explicitly mention cross-platform compatibility for scripts and tools, and provide guidance for users on Linux/macOS where necessary.
- Where possible, use Azure CLI or REST API examples as the primary automation method, as these are natively cross-platform.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-deploy-run.md
...cles/app-service/configure-language-java-deploy-run.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation attempts to provide parity between Windows and Linux, but there are several areas where Windows is prioritized or Linux is underrepresented. Windows examples and tools (such as Kudu, Advanced Tools, and FTPS) are sometimes mentioned first or exclusively. Some instructions, especially around process management and diagnostics (e.g., finding Java PIDs, using Kudu/Process Explorer), are Windows-centric or lack equivalent Linux guidance. There are also references to Windows-specific conventions (like web.config) and tools without always providing Linux alternatives or clarifying differences. In some cases, Linux-specific details are present but less detailed or less prominent than their Windows counterparts.
Recommendations
- Ensure that for every Windows-specific tool or workflow (e.g., Kudu, Process Explorer, FTPS), there is a clear Linux equivalent or an explicit note if not available.
- When presenting examples or instructions, alternate the order (sometimes Linux first) or present both platforms side-by-side to avoid 'windows_first' bias.
- Expand Linux troubleshooting and diagnostic sections to match the detail provided for Windows (e.g., how to find Java PIDs, manage files, or access logs without Kudu).
- Avoid referencing Windows-only files (like web.config) in a way that could confuse Linux users; clarify when something is not applicable.
- Where possible, provide cross-platform CLI examples and highlight any differences in behavior or file locations between Windows and Linux.
- Review all included links and references to ensure Linux documentation is as comprehensive and discoverable as Windows documentation.
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 extensive use of Windows-specific tools such as the App Service Migration Assistant (Windows MSI) and PowerShell scripts. There is no mention of Linux-based .NET hosting environments (e.g., Apache, Nginx, Kestrel on Linux), nor are there migration paths, tools, or examples for Linux-hosted .NET apps. The documentation repeatedly references Windows containers and IIS, and does not provide parity for Linux users.
Recommendations
- Add documentation and tooling for migrating .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel) to Azure App Service.
- Include Linux-specific migration examples and workflows, such as using Bash scripts or Linux-native tools.
- Mention Linux migration scenarios alongside Windows scenarios, rather than focusing exclusively on Windows/IIS.
- Provide parity in downloadable tools (e.g., a Linux-compatible migration assistant or containerization scripts).
- Clarify in the documentation which tools are Windows-only and provide alternatives or guidance for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/getting-started.md
...docs/blob/main/articles/app-service/getting-started.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the .NET/ASP.NET Core sections, where Windows tools (Visual Studio, Azure PowerShell) are listed before cross-platform or Linux-native tools. Some quickstart links and examples default to Windows or PowerShell, and the 'Next step' call-to-action promotes an ASP.NET (typically Windows-centric) workflow. In contrast, Linux and CLI-first options are less prominent or appear later, and in some stacks (e.g., Python), Windows is included in the quickstart tabs even for Linux scenarios.
Recommendations
- Ensure all stacks provide both Windows and Linux examples equally, with clear labeling and parity in depth.
- When listing tools or workflows, alternate the order or group by platform rather than listing Windows tools first.
- Provide Azure CLI and Bash examples alongside or before PowerShell, especially in quickstart and deployment guides.
- Review quickstart links and tabs to ensure Linux options are not hidden behind Windows defaults or tabs.
- For the 'Next step' section, offer multiple next steps for different platforms/stacks, not just ASP.NET/Windows.
- Highlight cross-platform tools (e.g., Visual Studio Code, Azure CLI) as primary options where possible.
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 by listing Windows SKU availability before Linux, providing both Azure CLI and Azure PowerShell automation examples (with PowerShell being Windows-centric), and referencing Windows containers before Linux containers. There are no Linux shell-specific examples or explicit Linux command-line instructions beyond the Azure CLI, and PowerShell is presented as a primary automation tool.
Recommendations
- Present Linux and Windows options in parallel or alternate their order to avoid always listing Windows first.
- Include Bash or shell script examples for automation, not just Azure CLI and PowerShell.
- When referencing containers, alternate or combine mentions of Windows and Linux containers, or explicitly state support for both up front.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
- Consider adding a section or callout for Linux users, especially for automation and scripting scenarios.
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. PowerShell commands are used for connectivity tests without Linux equivalents. The GUI for Hybrid Connection Manager is only available on Windows, and the documentation provides more detailed, step-by-step guidance for Windows users. Linux instructions are present but sometimes less detailed or refer users to other sections. Some troubleshooting steps and tools (e.g., Test-NetConnection) are Windows-specific, with no direct Linux alternatives provided.
Recommendations
- Provide Linux equivalents for all PowerShell commands (e.g., use 'nc', 'telnet', or 'curl' for connectivity tests).
- When listing instructions or tools, present both Windows and Linux options side by side, or alternate which comes first.
- Expand Linux installation and usage instructions to match the detail level of Windows sections.
- Offer guidance on using common Linux troubleshooting tools (e.g., 'nslookup', 'dig', 'ss', 'netcat') where only Windows tools are mentioned.
- Clarify any feature parity differences (such as the absence of a GUI on Linux) and suggest alternative workflows for Linux users.
- Ensure all screenshots and examples have Linux equivalents where possible, or provide terminal output samples for Linux.
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. It assumes the use of Windows-based App Service instances, referencing Windows file paths, tools (CMD, PowerShell, Kudu), and Visual Studio workflows exclusively. There are no Linux-specific instructions, examples, or mentions of Linux-based App Service environments for ASP.NET (non-Core) apps. Linux equivalents for listing .NET Framework versions, accessing diagnostic tools, or configuring the environment are missing.
Recommendations
- Add explicit notes clarifying whether instructions apply to Windows, Linux, or both App Service environments.
- Provide Linux-specific instructions or clearly state if certain features (e.g., .NET Framework, not .NET Core) are only available on Windows App Service.
- Include examples using Linux tools (e.g., Bash, SSH, Linux file paths) where applicable, or explain the lack of support.
- Mention and link to documentation for running ASP.NET apps in Linux containers, if that's the only Linux option.
- Balance the order of presentation: if both Windows and Linux are supported, present them side-by-side or alternate which comes first.
- Clarify that Visual Studio and Kudu are Windows-centric tools, and suggest alternatives for Linux-based workflows (e.g., VS Code, Azure CLI, FTP/SSH).
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 referencing Azure Storage Explorer (a GUI tool with a primary focus on Windows) for uploading files and generating SAS tokens, and by linking specifically to the Windows tab for SAS generation. There are no explicit Linux or cross-platform CLI examples for these steps, and no mention of Linux-native tools or workflows for uploading files or generating SAS tokens. All command-line examples use Azure CLI, which is cross-platform, but the initial file upload and SAS generation steps are Windows-centric.
Recommendations
- Provide CLI-based examples (using az storage blob upload and az storage blob generate-sas) for uploading files and generating SAS tokens, which work on both Linux and Windows.
- Mention and link to Linux/macOS-compatible alternatives to Azure Storage Explorer, or clarify that Storage Explorer is available cross-platform.
- Avoid linking only to the Windows tab for Storage Explorer instructions; ensure parity by including Linux/macOS tabs or CLI alternatives.
- Include a note or section specifically addressing Linux users, outlining equivalent steps for file upload and SAS generation.
- Where GUI tools are mentioned, always provide a CLI alternative for parity.
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 server-level data sources in Tomcat, but the Windows section is notably more detailed, with step-by-step PowerShell scripts and explicit use of Windows-specific tools and paths. The Windows instructions are longer, more prescriptive, and introduce Windows tools (PowerShell, cmd, Windows paths) before or more prominently than their Linux equivalents. The Linux section, while present, is less detailed and assumes more prior knowledge. There is also a reliance on PowerShell and Windows environment variables in the Windows section, which is not matched by equivalent Linux scripting guidance.
Recommendations
- Ensure Linux and Windows sections have parity in detail and step-by-step guidance. For example, provide a full sample Linux shell script (not just a snippet) for the startup process, similar to the PowerShell script for Windows.
- Introduce Linux instructions before or alongside Windows instructions, rather than after, to avoid a 'Windows-first' impression.
- Where Windows-specific tools (like PowerShell) are used, provide equivalent Linux shell (bash/sh) scripts and explain their usage in equal detail.
- Use neutral language and structure (e.g., present both OS tabs together, or default to Linux if usage data supports it).
- Explicitly mention any differences in capabilities or limitations between Linux and Windows App Service environments.
- Where possible, use cross-platform tools or commands (e.g., Azure CLI) in examples, and clarify any OS-specific steps.
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 is no mention of Linux-based hosting scenarios, Linux web servers (such as Apache or Nginx), or discovery of .NET Core/ASP.NET Core apps running on Linux. All examples and capabilities are described in the context of Windows tools and environments.
Recommendations
- Include information about discovering .NET (Core) web apps hosted on Linux servers, including supported distributions and web servers (e.g., Apache, Nginx).
- Provide parallel documentation and examples for Linux-based environments, not just IIS/Windows.
- Clarify whether Azure Migrate supports Linux-hosted .NET apps and, if so, describe the process and any differences.
- Mention any limitations or roadmap items if Linux discovery is not currently supported.
- Ensure that references and linked resources also cover Linux scenarios where applicable.
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 using iisnode. All configuration and troubleshooting steps reference Windows-specific tools, file paths, and concepts (e.g., web.config, named pipes, Win32 error codes, node.exe, Kudu CMD/PowerShell). There are no equivalent examples or guidance for Linux-based App Service environments, nor are cross-platform considerations discussed.
Recommendations
- Add a parallel section or separate article for Node.js on Azure App Service Linux, covering best practices and troubleshooting steps relevant to Linux environments.
- Provide Linux-specific examples, such as using PM2 or systemd for process management, and reference Linux file paths and logging locations.
- Include instructions for accessing the Kudu SSH/Bash console on Linux App Service, not just CMD/PowerShell.
- When discussing configuration (e.g., process management, logging, debugging), mention both Windows (iisnode/web.config) and Linux (e.g., PM2/ecosystem.config.js, environment variables) approaches.
- Clarify at the start of the article that the content is Windows-specific, and provide clear links to Linux-focused documentation.
- Balance the order of presentation so that Linux and Windows approaches are given equal prominence where both are supported.