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 801-825 of 2121 flagged pages
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 is mentioned first in availability sections, and Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, despite the CLI being more cross-platform. The portal instructions and screenshots are also Windows-oriented, and there is no mention of Linux-native scripting or automation tools (e.g., Bash, shell scripts). While Linux is supported and examples are present (notably in the CLI commands), the ordering and tool selection subtly prioritize Windows users.
Recommendations
- Alternate the order of Windows and Linux instructions/examples, or present them in parallel to avoid 'Windows first' bias.
- Include explicit Bash/shell script examples for automation, not just Azure CLI and PowerShell.
- Clarify that Azure CLI is fully cross-platform and highlight its use in both Linux and Windows environments.
- Add notes or screenshots showing the Azure portal experience on Linux (if differences exist), or clarify that the portal is OS-agnostic.
- Where PowerShell is mentioned, also mention Bash or other Linux-native scripting options for parity.
Create Pull Request
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 Windows bias in several ways: Windows installation and usage instructions are consistently presented before Linux equivalents, with more detail and screenshots for Windows GUI tools. Troubleshooting examples rely on Windows-specific tools like PowerShell's Test-NetConnection, with no Linux alternatives given. The Hybrid Connection Manager GUI is only available on Windows, and its usage is described in depth, while Linux users are directed to CLI usage with less visual guidance. Some troubleshooting steps and connectivity tests are Windows-centric, and Linux users are left to infer equivalent commands.
Recommendations
- Present Linux and Windows instructions in parallel, giving equal prominence to both platforms.
- Include Linux equivalents for all troubleshooting commands (e.g., provide 'nc', 'telnet', or 'curl' examples alongside PowerShell).
- Add more screenshots or step-by-step instructions for Linux CLI usage, similar to the Windows GUI walkthrough.
- Explicitly mention limitations or differences for Linux users (e.g., lack of GUI) at the start of relevant sections.
- Where a tool or feature is Windows-only (like the GUI), suggest alternative workflows or third-party tools for Linux.
- Ensure all code snippets and connectivity tests have Linux versions, not just Windows/PowerShell.
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 .NET web apps hosted on IIS web servers within VMware environments, which are Windows-centric technologies. There is no mention of Linux-based hosting options (such as Kestrel, Apache, or Nginx), nor are there any examples or guidance for discovering .NET apps running on Linux servers. All tools and workflows referenced (Azure Migrate appliance, IIS) are Windows-specific.
Recommendations
- Include information about discovering .NET web apps hosted on Linux servers, such as those running on Kestrel, Apache, or Nginx.
- Provide parallel examples or workflows for Linux environments, including any differences in the discovery process.
- Mention and link to tools or documentation relevant to Linux-based .NET app discovery, if supported.
- Clarify in the introduction or prerequisites if the discovery process is currently limited to Windows/IIS environments, and provide guidance for Linux users.
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, the Windows section is more detailed, with explicit PowerShell scripts and Windows-specific file paths and tools (e.g., PowerShell, %HOME%, %LOCAL_EXPANDED%). The Windows approach is described with more step-by-step scripting, while the Linux section is more concise and assumes familiarity with shell scripting and Linux tools. In some cases, Windows-specific tools and patterns (like PowerShell and .cmd files) are emphasized, and the Windows instructions are presented before or in more detail than their Linux equivalents.
Recommendations
- Ensure Linux and Windows instructions are presented with equal detail and clarity. For example, provide a full sample Linux shell script for the Tomcat server.xml transformation, similar to the detailed PowerShell script for Windows.
- Where possible, present Linux and Windows instructions in parallel, rather than giving one platform a more prominent or detailed section.
- Avoid assuming more technical familiarity for Linux users; provide step-by-step instructions and explanations for both platforms.
- Include Linux-native tools and patterns (e.g., bash scripts, systemd, cron) with the same prominence as Windows tools (e.g., PowerShell, .cmd files).
- Where Azure CLI commands are shown, ensure both Windows and Linux path conventions are included in examples.
- Consider providing a summary table or section that highlights the differences and similarities between Linux and Windows approaches, to help users quickly find the relevant instructions for their platform.
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 focusing exclusively on Windows-based deployment and configuration patterns for ASP.NET apps. All runtime version checks, file paths, and tooling references (such as Kudu, CMD, PowerShell, and Visual Studio) are Windows-centric, with no equivalent Linux examples or instructions. Linux-based App Service environments and their configuration methods are not mentioned, leaving a gap for users deploying to Linux.
Recommendations
- Add parallel Linux-based instructions and examples for each section, especially for runtime version checks and environment variable access.
- Include Linux file paths and commands (e.g., using Bash in Kudu or SSH) alongside Windows CMD/PowerShell examples.
- Clarify which instructions apply to Windows App Service plans and which to Linux, and provide links to Linux-specific documentation where appropriate.
- Mention and demonstrate deployment and configuration using cross-platform tools (such as the Azure CLI in Bash) and editors (such as VS Code) in addition to Visual Studio.
- Explicitly state any differences in behavior or configuration between Windows and Linux App Service environments.
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
Missing Windows Example
Linux Tools
Linux First
Summary
The documentation provides detailed, step-by-step instructions and command-line examples for Linux containers, including Azure CLI usage and SSH client commands. In contrast, Windows containers are only mentioned briefly, with no equivalent command-line or tool-based examples. The Linux workflow is prioritized and illustrated with actual commands and output, while Windows users are told only that browser SSH is supported and Azure CLI is not. No Windows-specific tools, PowerShell, or workflow details are given.
Recommendations
- Add equivalent step-by-step instructions for connecting to Windows containers, including any available command-line tools (e.g., PowerShell, Windows SSH clients) or alternative workflows.
- Clarify whether Windows containers support SSH via any local tools, and provide examples if possible.
- If browser SSH is the only supported method for Windows, provide screenshots and a detailed walkthrough similar to the Linux section.
- Explicitly mention any limitations or differences for Windows containers up front, and consider a parity table comparing Linux and Windows SSH access options.
- Ensure that both Linux and Windows sections have similar depth and clarity in their instructions.
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 page demonstrates a Windows bias primarily in the section for identifying Azure Traffic Manager endpoints, where only a PowerShell script is provided for detection of non-Azure endpoints. There are no equivalent Bash, Azure CLI, or cross-platform scripting examples for Linux or macOS users. The instructions for running the script assume a Windows/PowerShell environment, and there is no mention of how to perform the same task on Linux or macOS. Elsewhere, while REST API and Azure CLI commands are referenced (which are cross-platform), the only explicit scripting example is PowerShell. This may hinder Linux/macOS users from easily following the guidance.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for identifying Traffic Manager endpoints, or at least mention how Linux/macOS users can perform the same checks.
- When referencing scripts, clarify if they are cross-platform or provide alternatives for non-Windows environments.
- Add explicit instructions or links for running the detection queries or scripts in Linux/macOS environments.
- Review future documentation to ensure that scripting and automation examples are not Windows/PowerShell-centric unless absolutely necessary, and always provide parity for Linux users.
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 demonstrates Windows bias by referencing Windows directory paths (e.g., D:\home\site\wwwroot, D:\home\data\SitePackages) before mentioning Linux equivalents, and by using Windows-style path separators in examples. There is a lack of explicit Linux-specific instructions or examples, and the documentation assumes familiarity with Windows conventions and tools, such as FTP and directory creation in Windows paths. Linux paths are mentioned only parenthetically and not in examples or step-by-step instructions.
Recommendations
- Provide Linux-specific examples alongside Windows ones, including explicit Linux directory paths (e.g., /home/site/wwwroot, /home/data/SitePackages) in commands and instructions.
- Use platform-agnostic language and path separators, or clearly distinguish between Windows and Linux instructions.
- Include troubleshooting and deployment steps that address Linux-specific scenarios, such as permissions and file system differences.
- Add examples using Linux-native tools (e.g., SCP, SFTP, rsync) for uploading ZIP packages, in addition to FTP.
- Ensure parity in documentation for both Windows and Linux App Service environments, including screenshots or terminal outputs where appropriate.
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
Powershell Heavy
Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Azure App Service on Windows with iisnode. All configuration and troubleshooting steps are tailored to Windows, referencing Windows-specific tools (e.g., iisnode, web.config, named pipes, Win32 error codes, Kudu CMD/PowerShell). There are no Linux or cross-platform examples, and Linux equivalents for configuration, logging, or debugging are not mentioned.
Recommendations
- Add equivalent sections or links for Node.js on Azure App Service Linux, including best practices and troubleshooting steps.
- Provide Linux-based configuration and troubleshooting examples, such as using PM2, NGINX, or Linux file paths.
- Include Linux shell (bash) commands and screenshots for common tasks (e.g., installing profiler tools, accessing logs).
- Reference Linux-specific error logs and diagnostic tools (e.g., /var/log, journalctl) where appropriate.
- Clearly indicate at the start of the document that the content is Windows-specific, and provide a link to Linux-focused documentation if available.
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 Tools
Missing Linux Example
Summary
The documentation consistently lists Windows-related options and SKUs before Linux equivalents, and pricing is described in terms of Windows SKUs (e.g., 'charged as if you have one instance of Windows I1v2'). There is a lack of Linux-specific examples, pricing references, or parity in SKU explanations. Windows containers and plans are mentioned with specific notes, while Linux is only referenced generically, with no detailed Linux-specific guidance or examples.
Recommendations
- When listing supported workloads, alternate or parallelize the order of Windows and Linux (e.g., 'Linux web apps, Windows web apps').
- In pricing sections, provide Linux-specific pricing details and examples alongside Windows, or clarify if pricing is identical.
- In SKU tables and notes, explicitly mention Linux container support and any limitations, not just Windows.
- Where Windows-specific limitations are called out (e.g., 'Windows containers don't support large SKUs'), provide equivalent Linux information, even if just to state there are no such limitations.
- Include Linux-focused usage scenarios or configuration examples to ensure parity.
- If referencing Windows tools or patterns (such as SKUs named after Windows), clarify Linux applicability or provide Linux-specific alternatives.
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
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio and its NuGet package manager as the primary method for installing dependencies, with CLI instructions only mentioned secondarily. It also describes UI-based steps such as right-clicking folders and using the Azure Portal, which are more familiar to Windows users. There are no explicit Linux or cross-platform development environment examples, nor are there terminal-based instructions for common Linux workflows (e.g., using VS Code, command-line file creation, or deployment via CLI).
Recommendations
- Provide parallel instructions for Linux users, such as using VS Code or command-line editors to create and edit files.
- List CLI-based NuGet installation instructions before or alongside Visual Studio GUI steps.
- Include examples of setting environment variables and deploying using Azure CLI or GitHub Actions, not just via the Azure Portal.
- Avoid Windows-centric terminology like 'right-click' and instead describe file creation in a platform-neutral way.
- Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide any OS-specific notes as needed.
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 page exhibits Windows bias primarily by referencing Azure Storage Explorer with Windows-specific instructions and links (e.g., 'tabs=windows'), and by omitting Linux equivalents or cross-platform alternatives for key steps such as generating SAS tokens and uploading files. There are no examples or guidance for Linux users regarding these operations, and the only GUI tool mentioned is Storage Explorer, which is often presented with a Windows focus. The CLI examples (Azure CLI) are cross-platform, but initial setup and file management steps lack Linux parity.
Recommendations
- Provide explicit instructions or examples for Linux users, such as using Azure CLI or azcopy for uploading files and generating SAS tokens.
- Avoid linking to documentation or instructions that are Windows-specific unless Linux/macOS alternatives are also provided.
- Mention and demonstrate cross-platform tools (e.g., azcopy, Azure CLI) for all file management and SAS generation tasks.
- If referencing Azure Storage Explorer, clarify its availability on Linux/macOS and provide relevant instructions or screenshots.
- Ensure that all steps, especially those involving file operations, have both GUI and CLI options, with clear notes on platform compatibility.
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 exclusively providing PowerShell examples for per-app scaling, referencing Azure PowerShell cmdlets, and omitting equivalent CLI or Linux-native instructions. There are no Bash, Azure CLI, or cross-platform scripting examples, and the PowerShell approach is presented first and exclusively, which may disadvantage Linux or macOS users.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands to ensure Linux and macOS users can follow along without needing PowerShell.
- Include Bash scripting examples where appropriate, especially for configuring app settings or deploying ARM templates.
- Explicitly mention that PowerShell examples are cross-platform only if true, or clarify platform requirements.
- Reorder or parallelize documentation sections so that PowerShell and CLI examples are presented together, or alternate which comes first.
- Reference Linux-native tools or workflows where possible, such as using curl or jq for REST API calls, or using the Azure portal for platform-agnostic 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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but the PowerShell examples are presented alongside CLI examples without clarifying platform applicability. There is no explicit mention that PowerShell commands are Windows-centric, nor is there a Bash/Linux shell example for PowerShell commands. Additionally, outbound IPv6 support is noted as being available only for Windows apps, with no Linux parity or roadmap mentioned.
Recommendations
- Clearly indicate which commands are platform-specific (e.g., label PowerShell examples as Windows-only, and Azure CLI as cross-platform).
- Provide Bash/Linux shell equivalents for PowerShell commands, or clarify that Azure CLI commands are recommended for Linux/macOS users.
- When mentioning features (like outbound IPv6) that are Windows-only, provide a status update or roadmap for Linux support, or at least acknowledge the limitation more prominently.
- Where possible, provide Linux-specific troubleshooting or usage notes, especially in sections that discuss testing connectivity or command-line usage.
- Consider ordering examples with cross-platform tools (Azure CLI) first, and PowerShell (Windows-specific) second, to avoid implicit Windows-first bias.
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 exhibits mild Windows bias. Windows-specific features and limitations (such as Windows Containers subnet sizing and Windows Server Active Directory domain join) are described in detail, while Linux-specific scenarios are only briefly mentioned (e.g., a single note about Linux continuous deployment network dependencies). There are no Linux-specific configuration examples, troubleshooting steps, or parity discussions. Windows terminology and features (e.g., Kudu console, Windows Containers, Windows Server AD) are referenced without Linux equivalents or alternatives.
Recommendations
- Add Linux-specific examples for subnet sizing, container deployment, and troubleshooting (e.g., how Linux containers affect subnet IP usage).
- Include equivalent Linux tools and patterns (e.g., reference SSH, Bash, or Linux-native troubleshooting utilities alongside Kudu and Windows tools).
- Provide parity in limitations and feature descriptions for Linux (e.g., discuss any Linux-specific networking or integration caveats).
- Expand the Linux continuous deployment section to include more details and examples, such as common dependencies, troubleshooting, and configuration steps.
- Ensure that references to Windows features (e.g., Windows Containers, Windows Server AD) are balanced with Linux alternatives or a clear statement if not applicable.
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 several signs of Windows bias. It references Windows-specific tools (such as IIS diagnostics, Procdump, and PowerShell), and links to resources with 'Windows' in the title. Examples and instructions for troubleshooting and diagnostics (e.g., enabling .NET Profiler, using Kudu console) are focused on Windows environments, with no mention of Linux equivalents or alternatives. PowerShell is suggested for app management, but Bash/CLI alternatives are not presented. There are no examples or guidance for Linux-based App Service environments, which are common in Azure.
Recommendations
- Add explicit instructions and examples for Linux-based App Service environments, including how to enable diagnostics, collect logs, and troubleshoot performance issues.
- Include Bash/Azure CLI commands alongside PowerShell for managing and restarting apps.
- Reference Linux-compatible tools for memory dumps and diagnostics (e.g., gcore, strace, lsof), and explain how to use them in App Service on Linux.
- Clarify which features and extensions (such as Application Insights Profiler, Kudu console) are available or behave differently on Linux, and provide links to Linux-specific documentation.
- Avoid using 'Windows' in resource titles or links unless the content is truly Windows-only; provide parity links for Linux where possible.
- Ensure that troubleshooting steps and mitigation strategies are presented for both Windows and Linux environments, or clearly indicate any platform limitations.
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: logging types and features are described for Windows in more detail and are listed first, with Linux-specific instructions and limitations often relegated to later sections or footnotes. Several advanced logging features (web server logging, detailed error messages, failed request tracing) are available only for Windows, with no Linux equivalents or workarounds described. Examples and tooling references (such as Log Parser and Visual Studio) are Windows-centric, and Linux-specific logging patterns or tools are not mentioned.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows instructions, not after them.
- Clearly indicate feature parity (or lack thereof) for Linux and suggest alternative approaches or workarounds for missing features.
- Include references to Linux-native tools for log access and analysis (e.g., tail, grep, less, jq for JSON logs) where appropriate.
- Offer code samples for logging in popular Linux-supported languages and frameworks (e.g., Node.js, Python, Java) and show how to configure them for Azure App Service.
- If certain logging types (like web server logging or failed request tracing) are unavailable on Linux, explicitly state this and suggest alternative monitoring or debugging strategies.
- Mention cross-platform tools (such as Azure CLI, Kudu, or Azure Storage Explorer) equally for both platforms.
- Balance the order of presentation so that Linux and Windows instructions are given equal prominence.
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 the 'Premium V3 availability' section, Windows SKU availability is listed before Linux, and the Linux command requires an extra flag. In the automation section, both Azure CLI and Azure PowerShell are shown, but PowerShell (a Windows-centric tool) is given equal prominence to the cross-platform Azure CLI, and the PowerShell example uses Windows-specific worker size names. Throughout the document, there are multiple references to the Azure portal UI, which is platform-agnostic, but there are no explicit Linux shell or scripting examples beyond Azure CLI.
Recommendations
- Present Linux and Windows options in parallel or alternate their order to avoid always listing Windows first.
- Clarify that Azure CLI is fully cross-platform and recommend it as the default automation tool for parity.
- If showing PowerShell, also consider including Bash or shell script equivalents for Linux users, especially for automation.
- In PowerShell examples, clarify if the commands are cross-platform (PowerShell Core) or Windows-only.
- Where worker size names differ between platforms, document both sets of options.
- Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows.
- If possible, add a short Bash script example for Linux users to automate common tasks.
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/IIS environments, with repeated references to PowerShell scripts and Windows-specific tools. There are no examples, tools, or guidance for migrating .NET apps from Linux environments or for Linux-based hosting scenarios. The documentation assumes the source environment is always Windows/IIS, omitting Linux/Apache/Nginx scenarios entirely.
Recommendations
- Add explicit guidance and tooling for migrating .NET apps hosted on Linux (e.g., Apache, Nginx) to Azure App Service.
- Include Linux shell (bash) script examples alongside PowerShell, or reference cross-platform CLI tools where available.
- Document any limitations or differences when migrating from Linux environments, and provide remediation steps.
- Mention and link to Azure App Service for Linux documentation, and clarify support for Linux-based .NET Core/ASP.NET Core apps.
- Where possible, present migration options for both Windows and Linux environments in parallel, rather than focusing solely on Windows/IIS.
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
Missing Linux Example
Windows First
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows-specific tools (such as web.config and iisnode) without providing Linux equivalents or clarifying cross-platform applicability. Examples and configuration guidance (e.g., for auto-healing and Node.js hosting) reference Windows-centric patterns first or exclusively, and there is a lack of explicit Linux-native configuration examples or alternatives.
Recommendations
- For features like auto-healing, clarify whether configuration via web.config is only for Windows or provide equivalent Linux configuration instructions (e.g., using app settings or startup scripts).
- When mentioning iisnode or web.config for Node.js apps, add guidance for Linux-based App Service plans, such as using PM2, process.json, or environment variables.
- Wherever a Windows-specific tool or pattern is referenced, provide a Linux-native alternative or note if the feature is not available on Linux.
- Ensure that all code/configuration examples are provided for both Windows and Linux environments, or clearly indicate platform applicability.
- Consider restructuring sections to avoid always presenting Windows-first, and instead present both platforms equally or in parallel.
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 moderate Windows bias. Windows-specific information is often presented first (e.g., SKU availability, portal instructions), and PowerShell examples are provided alongside Azure CLI, but there are no Linux shell (bash) or automation examples. The portal instructions and screenshots use Windows-centric terminology and navigation. While Linux support is mentioned, practical Linux-specific guidance (such as bash scripting or Linux-native tools) is missing.
Recommendations
- Provide bash shell script examples for Linux users, especially in the 'Automate with scripts' section.
- Ensure that Linux-specific instructions (e.g., for custom containers) are included and presented with equal prominence to Windows instructions.
- Add screenshots and navigation steps for the Azure portal as seen from Linux environments (if any differences exist).
- Clarify any differences in scaling, deployment, or automation workflows between Windows and Linux App Service plans.
- List Linux SKU availability before or alongside Windows, not after.
- Include troubleshooting steps and error messages specific to Linux deployments.
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
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows instructions for configuring data sources in Tomcat and JBoss on Azure App Service. However, the Windows section is notably more detailed, with extensive use of PowerShell scripts and Windows-specific paths and tools. The Windows instructions rely heavily on PowerShell and Windows environment variables, while Linux instructions use shell scripts and standard Linux utilities. In several places, Windows tooling (PowerShell, CMD scripts, Windows paths) is described in greater detail and with more step-by-step guidance than the Linux equivalents. The Linux instructions are present and functional, but the documentation leans toward Windows-centric patterns and tools, especially in the Tomcat server-level configuration section.
Recommendations
- Provide equally detailed, step-by-step Linux instructions for Tomcat server-level configuration, including troubleshooting and edge cases.
- Offer Bash script examples for Linux that parallel the PowerShell scripts given for Windows, including reusable functions and error handling.
- Highlight Linux-native tools and patterns (e.g., systemd, shell scripting, Linux file paths) with the same depth as Windows tools.
- Ensure that Linux instructions are presented before or alongside Windows instructions, not after.
- Add explicit Linux examples for tasks like setting environment variables, copying files, and running transforms, matching the detail of Windows examples.
- Include a summary table comparing Windows and Linux approaches for each major configuration step.
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 by referencing Azure Storage Explorer with a direct link to the Windows tab for generating SAS tokens, and by not providing alternative Linux-native tooling or explicit cross-platform instructions for uploading files or generating SAS URLs. All command-line examples use Azure CLI, which is cross-platform, but the only GUI tool mentioned is Storage Explorer, with no mention of Linux alternatives or parity. There are no PowerShell-specific commands, but the documentation assumes the use of tools and workflows more familiar to Windows users.
Recommendations
- Provide explicit instructions or links for using Azure Storage Explorer on Linux and macOS, or mention that it is cross-platform.
- Include alternative CLI-based workflows for uploading files and generating SAS URLs (e.g., using 'az storage blob upload' and 'az storage blob generate-sas'), especially for users who may not use GUI tools.
- Avoid linking directly to Windows-specific tabs or instructions; ensure parity in documentation for Linux and macOS users.
- Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if necessary.
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 focusing exclusively on Windows-based deployment and management patterns for ASP.NET apps. All runtime version discovery and management instructions reference Windows file paths, tools (Kudu, CMD, PowerShell), and Visual Studio workflows, with no mention of Linux App Service environments or equivalent Linux tooling. There are no Linux-specific examples or parity notes for users deploying to Linux App Service.
Recommendations
- Add parallel instructions and examples for Linux App Service environments, including how to check installed .NET runtimes and access diagnostic tools on Linux.
- Include Linux shell (bash) commands and file paths where appropriate, or explicitly state when a feature is Windows-only.
- Reference Linux-compatible deployment tools (such as Azure CLI, FTP, or Git) and clarify any differences in workflow for Linux-hosted ASP.NET apps.
- Provide guidance on accessing environment variables and logs in Linux containers or App Service on Linux.
- Clearly label sections as Windows-specific when Linux alternatives are not available, and link to Linux documentation where possible.
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 exclusively discusses discovery of .NET web apps deployed on IIS web servers within VMware environments, which are Windows-centric technologies. There is no mention of Linux-based web servers (such as Apache or Nginx), nor are there examples or guidance for discovering .NET apps running on Linux. All discovery capabilities and dashboard features are described in the context of Windows/IIS, and all referenced resources focus on ASP.NET on IIS.
Recommendations
- Include information about discovering .NET web apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx).
- Provide examples or workflows for Linux-based environments, including any differences in discovery steps or requirements.
- Mention whether the Azure Migrate appliance supports Linux web servers, and if not, clarify the scope and provide alternative guidance.
- Add parity in referenced resources by linking to Linux-focused migration/discovery documentation if available.
- Explicitly state any current limitations regarding Linux support to set user expectations.