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 976-1000 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-customize-sign-in-out.md
...vice/configure-authentication-customize-sign-in-out.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing server-level authorization instructions exclusively for Windows apps using IIS and web.config, with no equivalent Linux example. The section explicitly states that Linux apps cannot use this method and does not offer alternative guidance for Linux users. Additionally, the use of Windows-specific patterns (IIS, web.config) is presented before any cross-platform or Linux-compatible approaches.
Recommendations
- Provide equivalent Linux guidance for server-level authorization, such as using .htaccess for Apache, NGINX configuration, or middleware-based authorization in common Linux web stacks.
- Include explicit examples and configuration steps for Linux-based App Service environments.
- Reorganize the documentation to present cross-platform or Linux-compatible solutions alongside or before Windows-specific instructions.
- Clarify which features or instructions are platform-specific and always offer alternatives where possible.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-common.md
...ocs/blob/main/articles/app-service/configure-common.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. While it covers both Azure CLI and PowerShell, PowerShell (a Windows-centric tool) is given equal prominence, and some advanced/bulk operations are only possible in PowerShell or are not possible at all outside it. Several features (default documents, virtual directory mapping, handler mappings) are explicitly Windows-only, but this is not always clearly stated at the top of those sections. Examples for Linux-specific workflows or tools are minimal or absent, and Windows-specific paths and patterns (e.g., D:\home, site\wwwroot) are used throughout. The documentation often references Windows tools and patterns before or instead of Linux equivalents.
Recommendations
- Clearly indicate at the beginning of each section which features are Windows-only, and provide Linux alternatives or workarounds where possible.
- Where PowerShell is used for advanced/bulk operations, provide equivalent Bash or cross-platform scripting examples, or state explicitly if not possible.
- Avoid using Windows-specific paths (e.g., D:\home, site\wwwroot) in generic examples; provide Linux path equivalents or clarify when these are Windows-only.
- For features not available on Linux (e.g., handler mappings, virtual directories), suggest alternative approaches for Linux users or link to relevant Linux/container documentation.
- Ensure that Linux and container workflows are given equal prominence, not just mentioned in passing or as exceptions.
- Where CLI commands have platform-specific caveats (e.g., quoting, escape characters), provide both Windows (PowerShell/CMD) and Linux (Bash) examples.
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 (e.g., App Service Migration Assistant for Windows, PowerShell scripts for IIS). There is no mention of Linux-based .NET hosting environments (such as Kestrel or Apache/Nginx), nor are there migration paths or tools described for Linux servers. The documentation assumes the source environment is always Windows/IIS, omitting Linux scenarios entirely.
Recommendations
- Add guidance and tooling for migrating .NET apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx) to Azure App Service.
- Include Linux-specific migration examples and scripts, such as Bash or shell scripts, alongside PowerShell examples.
- Mention and document any Azure App Service migration tools or workflows that support Linux-based .NET apps, or clarify if such support is not available.
- Present migration scenarios for both Windows and Linux environments, ensuring parity in documentation structure and detail.
- If certain tools are Windows-only, explicitly state this and provide alternative recommendations for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-gateway-required-vnet-integration.md
...service/configure-gateway-required-vnet-integration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a clear Windows bias: it states that gateway-required virtual network integration only works for Windows plans and explicitly excludes Linux apps. All troubleshooting and connectivity examples use Windows-specific tools (e.g., PowerShell's Test-NetConnection, netstat -aon), with no mention of Linux equivalents or guidance for Linux users. There are no Linux command-line examples or references, and the documentation does not address how Linux users should approach similar troubleshooting or integration tasks.
Recommendations
- Where possible, provide Linux equivalents for all troubleshooting and connectivity commands (e.g., use 'nc' or 'telnet' for TCP checks, 'ss' or 'netstat' for port listening).
- Explicitly state early in the document that gateway-required integration is not supported for Linux apps, and offer clear alternatives or guidance for Linux users (e.g., recommend regional VNet integration for Linux).
- When referencing tools or commands, present both Windows and Linux options side by side to ensure parity.
- Add a section or callout for Linux users explaining their options and any differences in supported features.
- If certain features are Windows-only, provide links to Linux-supported alternatives and migration guidance.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-undelete.md
...blob/main/articles/app-service/app-service-undelete.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong bias towards Windows and PowerShell usage. All CLI-based restoration instructions and examples are provided exclusively using PowerShell cmdlets from the Az PowerShell module, with no mention of Azure CLI, Bash, or cross-platform scripting alternatives. The documentation assumes the use of Windows-centric tools and patterns, and does not provide parity for Linux or macOS users who may prefer or require non-PowerShell solutions.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available cross-platform, but also provide Bash or shell script examples where appropriate.
- Include notes or sections for Linux/macOS users, clarifying how to perform the same tasks without relying on Windows-specific tools.
- Ensure that any references to tools or workflows are not Windows-centric by default, and present cross-platform options with equal prominence.
- Consider reordering sections so that cross-platform solutions (such as Azure CLI) are presented before or alongside PowerShell examples.
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 generally provides both Windows and Linux instructions, but there is a noticeable Windows-first bias. Windows instructions and tools (such as the GUI and PowerShell commands) are often presented before Linux equivalents, and some troubleshooting steps only provide Windows-specific commands (e.g., PowerShell's Test-NetConnection) without Linux alternatives. The Hybrid Connection Manager GUI is only available on Windows, and this is clearly stated, but the documentation could do more to offer parity in troubleshooting and examples for Linux users.
Recommendations
- Present Windows and Linux instructions/examples in parallel or with equal prominence, rather than listing Windows first by default.
- For troubleshooting steps, provide equivalent Linux commands (e.g., suggest using 'nc' or 'telnet' for TCP connectivity tests instead of only PowerShell's Test-NetConnection).
- Where GUI tools are Windows-only, offer enhanced CLI or alternative Linux workflows and highlight them as first-class options.
- In sections where only Windows tools or patterns are mentioned (such as service management or firewall configuration), add Linux equivalents (e.g., systemctl for service management, ufw/iptables for firewall).
- Ensure all code snippets and walkthroughs have both Windows and Linux versions where applicable.
- Consider adding a summary table at the start of each section indicating OS support and tool availability.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-dotnetcore.md
.../articles/app-service/configure-language-dotnetcore.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by presenting Windows instructions and tools (such as Kudu, CMD, and PowerShell) before Linux equivalents, and by referencing Visual Studio and Windows-specific deployment patterns more prominently. While Linux-specific instructions and examples are present and reasonably thorough, Windows concepts and tools are often introduced first or in more detail, and the overall narrative assumes familiarity with Windows-centric workflows.
Recommendations
- Ensure Linux and Windows instructions/examples are presented in parallel or with equal prominence, rather than Windows-first.
- When referencing tools like Kudu, CMD, or PowerShell, provide equivalent Linux-native alternatives (e.g., SSH, Bash shell, or Linux-based diagnostic tools) and mention them together.
- Balance mentions of Visual Studio with cross-platform tools (e.g., VS Code, CLI-based workflows) to avoid assuming a Windows development environment.
- Where possible, provide side-by-side code blocks or tabs for both Windows and Linux commands, especially for common tasks like viewing logs, setting environment variables, or accessing the console.
- Expand on Linux-native troubleshooting and diagnostic workflows to match the detail given for Windows/Kudu/PowerShell.
- Review the order of sections and examples to avoid always leading with Windows; alternate or group by platform as appropriate.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate.md
...main/articles/app-service/configure-ssl-certificate.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. PowerShell is presented alongside Azure CLI for automation, but there are references to Windows-specific tools (IIS, Certreq.exe) for certificate export, and instructions for exporting certificates from Windows are more detailed than for Linux. There is no explicit mention of Linux-based workflows or tools (such as certbot or Linux certificate stores), and Windows patterns (IIS, Certreq.exe) are mentioned before or instead of Linux equivalents. The FAQ also references Windows container support specifically, without clarifying Linux support.
Recommendations
- Add explicit Linux-based examples for certificate generation and export, such as using OpenSSL on Linux, and mention Linux certificate stores where relevant.
- When referencing Windows tools (IIS, Certreq.exe), provide equivalent Linux instructions (e.g., using OpenSSL, certbot, or other common Linux utilities).
- Ensure parity in automation examples by including Bash scripts or Linux shell commands alongside PowerShell.
- Clarify OS-specific limitations or capabilities, especially in the FAQ, to indicate Linux support or lack thereof.
- Avoid presenting Windows tools or patterns before Linux equivalents; instead, present both together or in parallel tabs.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-custom-container.md
...ain/articles/app-service/configure-custom-container.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 content and examples are often presented first or in more detail, especially regarding base images, persistent storage, and advanced configuration (e.g., customizing memory/CPU, health ping, machine key injection). PowerShell examples are consistently provided alongside Bash, but not vice versa for Linux-specific commands. Some advanced configuration sections (e.g., customizing memory/CPU, health ping) are only described for Windows containers, with no Linux equivalent or guidance. Windows tools and patterns (e.g., Kudu, PowerShell, Windows directory paths) are referenced more prominently or exclusively in some sections.
Recommendations
- Ensure all advanced configuration sections (e.g., memory/CPU limits, health ping behavior) include Linux parity or explicitly state if not supported on Linux.
- When providing command-line examples, always include both Bash (for Linux) and PowerShell (for Windows) where applicable, and clarify which OS each applies to.
- Present Windows and Linux content in parallel or with equal prominence, rather than consistently leading with Windows.
- Where Windows-specific tools or concepts are mentioned (e.g., Kudu, C:\home), ensure Linux equivalents (e.g., /home, SSH, Linux logging paths) are equally described.
- For sections that are only relevant to Windows (e.g., machine key injection), clearly label them as such and provide Linux-specific security/configuration advice where possible.
- Review for missing Linux examples or guidance, especially in sections about advanced configuration, diagnostics, and persistent storage.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias, particularly in the automation section. PowerShell is featured explicitly with a code sample, while the Azure CLI is only referenced via a link without an inline example. There is no mention of Linux-specific tools or shell scripting, and the PowerShell example appears before any Linux/CLI equivalent. The rest of the documentation is mostly platform-neutral, but the automation section lacks parity for Linux users.
Recommendations
- Provide inline Azure CLI examples alongside PowerShell, not just as links, to ensure Linux users have immediate guidance.
- Include Bash or shell script examples where automation is discussed, or at least reference their availability.
- When listing automation options, present Azure CLI (cross-platform) examples before or alongside PowerShell to avoid a Windows-first impression.
- Explicitly mention that both CLI and PowerShell approaches are supported on all platforms, and clarify any platform-specific prerequisites if they exist.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-user-identities.md
...pp-service/configure-authentication-user-identities.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page primarily provides examples and code snippets in C#/.NET, which are most commonly associated with Windows development. Framework-specific alternatives are listed with .NET/ASP.NET first and in greatest detail, while Linux-centric languages and frameworks (such as Python, Node.js, or shell scripting) are not mentioned or exemplified. There are no examples or references to Linux command-line tools, shell environments, or Linux-specific patterns for accessing headers or decoding Base64/JSON. The PHP and Java mentions are brief and lack code samples, and there are no examples for Python, Node.js, or other popular cross-platform stacks.
Recommendations
- Add code examples for accessing and decoding the X-MS-CLIENT-PRINCIPAL header in popular Linux-friendly languages such as Python (Flask/Django), Node.js (Express), and Go.
- Include shell command-line examples (e.g., using curl, jq, base64) for decoding the header, which would be useful for Linux users.
- Balance the framework-specific alternatives section by providing equal detail and code samples for non-Windows stacks.
- Explicitly mention that the process is platform-agnostic and provide guidance for both Windows and Linux environments.
- Consider the order of presentation: do not always list Windows/.NET first; alternate or group by popularity or platform neutrality.
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 Tomcat data sources, but the Windows section is notably more detailed, featuring extensive PowerShell scripting and Windows-specific file paths and tools. Windows configuration steps are described with more granularity, including custom startup scripts and PowerShell automation, whereas Linux instructions are more concise and rely on shell scripting. Additionally, Windows tools (PowerShell, Windows paths) are featured prominently, and in some sections, Windows instructions appear before or are more elaborate than their Linux counterparts.
Recommendations
- Ensure Linux and Windows instructions are equally detailed, providing parity in step-by-step guidance and troubleshooting.
- Where PowerShell scripts are provided for Windows, offer equivalent Bash scripts for Linux, with similar explanations and comments.
- Avoid assuming familiarity with Windows tools (e.g., PowerShell) without offering Linux alternatives (e.g., Bash, shell scripting) in parallel.
- Present Linux and Windows instructions side-by-side or in the same order to avoid implicit prioritization.
- Highlight any platform-specific limitations or differences explicitly, so users on both platforms understand the context.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-basic-auth-disable.md
...n/articles/app-service/configure-basic-auth-disable.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates some Windows bias, primarily through the exclusive mention of Windows-specific deployment tools (such as Web Deploy and MSBuild), and by referencing Visual Studio deployment without mentioning cross-platform alternatives. There are no explicit Linux or macOS-specific deployment tool examples, and the documentation does not provide parity in discussing Linux-native tools or workflows. While Azure CLI examples are cross-platform, the overall framing and tool references are Windows-centric.
Recommendations
- Include examples or references for deploying from Linux/macOS environments, such as using SCP/SFTP, rsync, or Linux-native FTP clients.
- Mention and provide examples for cross-platform deployment tools (e.g., VS Code with Azure extensions, Git, or third-party CI/CD tools) alongside Visual Studio and MSBuild.
- Clarify that Azure CLI commands can be run from any OS, and provide explicit instructions or screenshots for Linux/macOS terminals where appropriate.
- When referencing 'Web Deploy' and 'MSBuild', note their Windows-specific nature and suggest Linux/macOS alternatives or workarounds.
- In the deployment method table, add a column or notes indicating OS compatibility for each method, especially for those that are Windows-only.
- Provide troubleshooting or confirmation steps using Linux/macOS command-line tools (e.g., curl, git, lftp) in addition to or instead of Windows tools.
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 generally provides parity between Linux and Windows, but there are subtle signs of Windows bias. In several sections, Windows examples or instructions are presented before Linux equivalents (windows_first). Some advanced troubleshooting and process management instructions for Windows rely on Kudu/Advanced Tools, which are Windows-specific (windows_tools). There are also areas where PowerShell or Windows-centric tools are referenced more prominently (powershell_heavy). In a few cases, Linux-specific details are less comprehensive or are missing compared to Windows (missing_linux_example).
Recommendations
- Ensure that Linux and Windows instructions are always presented in parallel, or alternate which comes first to avoid implicit prioritization.
- Where Windows-specific tools (like Kudu/Advanced Tools) are referenced, provide equivalent Linux-native instructions or clarify if a feature is not available.
- Avoid using PowerShell or Windows command-line tools as the default or only example; always provide Bash/Azure CLI/Linux-native equivalents.
- Audit all sections for completeness of Linux examples, especially for advanced scenarios (e.g., process management, log analysis, deployment troubleshooting).
- Highlight Linux-specific troubleshooting and customization options, such as using SSH, Linux package managers, and native file paths.
- Where a feature is only available on one platform, clearly state this and provide workarounds or alternatives for the other platform.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-azure-pipelines.md
...ob/main/articles/app-service/deploy-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific deployment methods (Web Deploy) are highlighted, with explicit instructions and troubleshooting for Windows agents, while Linux alternatives are not equally covered. Some examples and error messages assume or require Windows agents, and there is a lack of parity in Linux-specific deployment guidance. Windows tools and patterns (such as IIS, Web Deploy, and references to Windows agent pools) are mentioned without Linux equivalents or alternatives.
Recommendations
- Provide equivalent Linux-based deployment examples, especially for scenarios where only Windows/Web Deploy is discussed.
- Explicitly state when a feature is Windows-only and suggest Linux alternatives (e.g., using ZIP deploy, FTP, or Kudu REST API for Linux agents).
- Include troubleshooting steps and error messages relevant to Linux agents, not just Windows.
- Balance the order of presentation so that Linux and Windows options are presented equally, or clarify platform-specific limitations up front.
- Where Windows tools (like Web Deploy or IIS) are mentioned, provide context or links for Linux users on how to achieve similar results.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-nodejs.md
...main/articles/app-service/configure-language-nodejs.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Windows-specific tools and patterns (such as IISNode and web.config) are described in detail, and Windows instructions or pivots are often presented before Linux equivalents. There is also a reference to using PowerShell for Application Insights instrumentation, but no equivalent Bash or Linux CLI example. Some sections (e.g., troubleshooting, diagnostic logs) provide more detailed or prominent guidance for Windows scenarios.
Recommendations
- Ensure Linux and Windows instructions are presented with equal prominence, alternating which platform appears first in each section or using a neutral introduction.
- Where PowerShell or Windows-specific tooling is referenced (e.g., for Application Insights), provide equivalent Bash or Linux CLI examples.
- Expand Linux-specific troubleshooting guidance to match the detail provided for Windows (e.g., common issues with startup commands, permissions, or container configuration).
- Where Windows-specific files (like web.config) are discussed, add parallel notes for Linux (e.g., startup scripts, Dockerfile, or configuration best practices).
- Review all sections for parity in depth and clarity between Windows and Linux pivots, ensuring that neither platform is treated as the default.
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 Windows bias by referencing Azure Storage Explorer with a direct link to the Windows tab for generating SAS tokens, and does not mention or provide alternatives for Linux users. There are no Linux-specific instructions or examples for uploading files or generating SAS tokens, and the only tool mentioned for these tasks is Azure Storage Explorer, which is often associated with Windows environments. All command-line examples use Azure CLI, which is cross-platform, but the file upload and SAS generation steps lack Linux parity.
Recommendations
- Include instructions or examples for uploading files and generating SAS tokens using Azure CLI or Azure Portal, which are platform-agnostic.
- Explicitly mention that Azure Storage Explorer is available on Linux and macOS, or provide alternative tools/commands for Linux users.
- Avoid linking directly to the Windows tab in documentation references; instead, provide a general link or mention all supported platforms.
- Add a section or note for Linux users on how to perform the same tasks without relying on Windows-centric tools.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-container-azure-pipelines.md
...ticles/app-service/deploy-container-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on deploying Windows containers, with all examples, YAML snippets, and variable defaults set for Windows (e.g., 'windows-latest' VM image). There are no Linux container examples, nor any mention of how to adapt the process for Linux-based applications or App Service for Linux. The App Service deploy task is configured specifically for 'Web App for Containers (Windows)', and the sample Docker image is a Windows/.NET Framework image. Linux tools, images, or deployment targets are not discussed or referenced.
Recommendations
- Add parallel examples and instructions for deploying Linux containers, including YAML snippets using 'ubuntu-latest' or other Linux VM images.
- Explicitly mention how to adapt the pipeline for Linux-based applications and App Service for Linux.
- Include a section or callout noting the differences between deploying to Windows vs. Linux App Service, with links to relevant documentation.
- Provide sample Dockerfiles and image references for Linux-based applications (e.g., ASP.NET Core on Linux).
- Ensure variable names and task configurations are not hardcoded to Windows unless necessary, and show how to parameterize for both OS types.
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 clear Windows bias. It assumes the use of Windows-based App Service instances, referencing Windows file paths, CMD/PowerShell consoles, and Visual Studio as the primary tooling. There are no Linux-specific examples or instructions, and Linux-based deployment or configuration scenarios are not addressed. The documentation does not mention or show how to perform equivalent tasks on Linux App Service plans or containers.
Recommendations
- Add parallel instructions and examples for Linux-based App Service plans, including how to check .NET runtime versions and access diagnostic tools in Linux environments.
- Include Linux shell (bash) commands and file paths where appropriate, alongside Windows CMD/PowerShell examples.
- Clarify when instructions are Windows-specific and provide links or sections for Linux users.
- Reference cross-platform tools (such as Azure CLI, Kudu SSH, or VS Code) equally, and avoid assuming Visual Studio or Windows-only workflows.
- Explicitly mention differences in environment variable access, file system layout, and diagnostic log access between Windows and Linux App Service environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate-in-code.md
...icles/app-service/configure-ssl-certificate-in-code.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 providing detailed, code-rich examples for Windows environments (including both C# and Java with Windows certificate store usage) before mentioning Linux. Windows-specific tools and patterns (such as the Windows certificate store and environment variables) are described in depth, while Linux examples are less prominent, less detailed, and often deferred to external documentation. Non-Windows languages (Node.js, PHP, Python) are not given direct examples, and Linux-specific guidance is less comprehensive.
Recommendations
- Provide Linux examples alongside Windows examples, not after them or as an afterthought.
- Include code samples for Linux environments in multiple languages (e.g., Python, Node.js, Java), not just C#.
- Offer equal detail for Linux certificate handling, including how to load certificates in common Linux programming environments.
- Avoid referring readers to external documentation for Linux/non-Windows languages when Windows examples are provided inline.
- Explicitly mention Linux equivalents for all Windows-specific tools and patterns, such as certificate stores and environment variables.
- Structure the documentation so that Linux and Windows guidance are presented in parallel sections or tabs, ensuring parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-ftp.md
...zure-docs/blob/main/articles/app-service/deploy-ftp.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-centric tools and workflows. PowerShell is given equal prominence to Azure CLI, and Windows tools such as WinSCP and Visual Studio are mentioned before or instead of Linux alternatives. There are no explicit Linux command-line FTP client examples, and the documentation lacks references to common Linux tools or workflows for FTP/S deployment.
Recommendations
- Add explicit Linux command-line FTP/S examples (e.g., using lftp, curl, or ftp commands) alongside or before PowerShell examples.
- Include Linux-native FTP/S clients (e.g., FileZilla, lftp, gFTP) in the list of recommended FTP/S clients.
- When listing tools, alternate or balance the order (e.g., mention Visual Studio and FileZilla together, not just Windows tools first).
- Provide sample shell scripts or CLI commands for Linux users to automate FTP/S deployment.
- Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- Add troubleshooting steps or notes relevant to Linux environments (e.g., firewall configuration, passive mode setup).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-apm.md
...in/articles/app-service/configure-language-java-apm.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation generally provides parity between Linux and Windows for most APM configuration steps, but there are subtle signs of Windows bias. Windows-specific tools (like the Kudu console) are mentioned for Windows scenarios, while Linux uses SSH, but the documentation does not always provide equal detail or guidance for Linux-specific workflows (e.g., Kudu is not mentioned for Linux, and SSH is referenced for both platforms in some places). In the Application Insights section, the Windows app settings include an extra setting (XDT_MicrosoftApplicationInsights_Java=1) not explained for Linux. The ordering of tabs and examples sometimes puts Windows first. There are also references to PowerShell/Windows patterns (e.g., Kudu) without Linux equivalents or explanations.
Recommendations
- Ensure that any Windows-specific tools (like Kudu) have Linux equivalents mentioned, or clarify when a tool is Windows-only.
- Provide equal detail for Linux workflows, including step-by-step instructions for common Linux tools (e.g., using SCP/SFTP for file upload, or Linux-native consoles).
- Explain any differences in app settings between Windows and Linux (e.g., why XDT_MicrosoftApplicationInsights_Java=1 is only for Windows).
- When listing tabbed examples, alternate the order or default to Linux-first to avoid implicit Windows prioritization.
- Avoid referencing PowerShell or Windows-specific patterns unless a Linux equivalent is also provided.
- Review for any missing Linux examples or explanations, especially for advanced configuration or troubleshooting.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-vnet-integration-enable.md
...icles/app-service/configure-vnet-integration-enable.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for configuring virtual network integration. However, it gives a detailed, step-by-step PowerShell workflow (which is Windows-centric), while the CLI section is brief and lacks equivalent depth. There are no Linux shell or Bash-specific examples, and the PowerShell section is more comprehensive, indicating a bias toward Windows tools and workflows.
Recommendations
- Expand the Azure CLI section to provide step-by-step instructions equivalent to the PowerShell section, including parameter preparation, subnet delegation checks, and integration steps.
- Include Bash or shell scripting examples for Linux users, especially for tasks like checking subnet delegation and setting resource context.
- Clearly state that both Azure CLI and PowerShell are cross-platform, but provide explicit Linux/Bash examples to ensure parity.
- Avoid assuming PowerShell as the default advanced scripting tool; balance with Bash or other Linux-native tools where possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-staging-slots.md
...blob/main/articles/app-service/deploy-staging-slots.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it provides both Azure CLI and Azure PowerShell examples for all operations, it frequently references Windows-centric tools and patterns (such as PowerShell and Web.config), and sometimes presents PowerShell examples before CLI. There is also a reliance on Windows-specific configuration (e.g., Web.config, applicationInitialization), and troubleshooting steps reference Windows file paths (D:\home\LogFiles\eventlog.xml). There are no explicit Linux shell or scripting examples, and some features (like auto swap) are noted as unsupported on Linux, but without Linux-specific alternatives or guidance.
Recommendations
- Add explicit Linux shell (bash) examples where relevant, especially for scripting or automation scenarios.
- When referencing configuration files, provide Linux-appropriate equivalents or note differences (e.g., discuss app startup/warm-up for Linux containers, not just Web.config).
- Avoid Windows-centric terminology or file paths in troubleshooting; provide Linux paths or clarify cross-platform locations.
- Ensure parity in feature support explanations: if a feature is not supported on Linux, suggest alternative approaches or workarounds for Linux users.
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more relevant for Linux users.
- Where Visual Studio or other Windows-only tools are mentioned, also mention cross-platform deployment tools (e.g., VS Code, GitHub Actions, Azure DevOps pipelines) and how they can be used from Linux.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-authentication-types.md
...in/articles/app-service/deploy-authentication-types.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 prioritizing Windows-specific tools (PowerShell, Visual Studio) and workflows. PowerShell is given a dedicated row, and Visual Studio (a Windows-centric IDE) is described in detail, with multiple references. There is no mention of Linux-native deployment tools or workflows (such as Bash scripts, SCP, rsync, or Linux package managers), nor are there any Linux-specific examples or parity for Linux users. Visual Studio Code is mentioned, but only in the context of .NET and GitHub, not as a cross-platform deployment tool. The documentation does not provide Linux command-line examples or highlight Linux deployment scenarios.
Recommendations
- Add Linux-native deployment examples, such as using Bash scripts, SCP, rsync, or SFTP for deploying to Azure App Service.
- Include references to Linux package managers or automation tools (e.g., Ansible, Chef, Puppet) for deployment.
- Provide parity in documentation for Linux users by including step-by-step guides or examples using common Linux shells and tools.
- Highlight cross-platform tools (such as Azure CLI and Visual Studio Code) more prominently, with explicit Linux usage instructions and screenshots.
- Balance the coverage of Visual Studio and PowerShell with equivalent open-source or Linux-friendly tools and workflows.