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 1176-1200 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/identity-scenarios.md
...s/blob/main/articles/app-service/identity-scenarios.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 Microsoft-centric authentication libraries (MSAL, Microsoft.Identity.Web) and ASP.NET Core, which are most commonly associated with Windows development environments. There is repeated mention of Visual Studio and IDE integration, but no mention of Linux development tools, frameworks, or parity in local development scenarios. No Linux-specific examples, tools, or workflows are provided, and the documentation implicitly assumes a Windows/Visual Studio/ASP.NET Core context for advanced scenarios.
Recommendations
- Include examples and guidance for Linux-based development environments, such as using VS Code, JetBrains Rider, or command-line workflows.
- Highlight cross-platform compatibility of authentication libraries and provide explicit instructions for Linux and macOS users.
- Mention and link to documentation for configuring authentication in popular Linux web frameworks (e.g., Node.js/Express, Python/Flask or Django, Java/Spring Boot) when discussing code-based solutions.
- Clarify that App Service authentication features are available regardless of the underlying OS and provide parity tables or notes where features differ.
- Add local development setup instructions for Linux (and macOS) environments, including how to achieve single sign-on or local testing without Visual Studio.
Create Pull Request
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 a Windows bias by referencing Windows file paths (e.g., D:\home\site\wwwroot) before Linux equivalents, using Windows-style path separators in examples, and omitting explicit Linux/Bash command examples or Linux-specific instructions. The focus is on Windows deployment patterns and tools, with minimal mention of Linux environments beyond brief parenthetical notes.
Recommendations
- Provide Linux-specific examples alongside Windows ones, including file paths (e.g., /home/site/wwwroot) and deployment instructions.
- Use platform-agnostic path notation or show both Windows and Linux paths in all relevant sections.
- Include Bash or Linux shell command examples where Azure CLI is used, and clarify any differences in behavior or requirements between Windows and Linux App Service environments.
- Explicitly mention Linux deployment nuances, such as directory permissions or differences in mounting ZIP packages.
- Ensure troubleshooting and WebJob deployment sections address both Windows and Linux scenarios equally.
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 examples reference Windows file paths and tools (Kudu CMD/PowerShell), with no mention of Linux equivalents or how to perform similar tasks in a Linux App Service environment. Visual Studio (a Windows-centric tool) is referenced as the primary publishing method, and there are no Linux shell or cross-platform examples for key tasks.
Recommendations
- Add equivalent instructions and examples for Linux-based App Service plans, including how to check .NET runtime versions and access environment variables in Linux containers.
- Provide Linux shell (bash) commands where CMD/PowerShell commands are shown, or clarify when steps are Windows-only.
- Mention and demonstrate cross-platform deployment tools (such as Azure CLI, GitHub Actions, or VS Code) alongside Visual Studio.
- Clearly indicate which instructions apply only to Windows App Service plans and provide links or sections for Linux-specific guidance.
- Include examples of accessing diagnostic logs and configuring app settings in Linux environments.
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
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it provides Azure CLI and PowerShell instructions (which are cross-platform), it consistently lists PowerShell after CLI and includes a PowerShell-specific example. In the FTP client recommendations, Windows-centric tools (Visual Studio, WinSCP) are mentioned first, with only Cyberduck as a cross-platform option. There are no explicit Linux command-line FTP client examples (such as lftp, ncftp, or the standard ftp/sftp commands), nor are Linux desktop tools (like FileZilla or Nautilus) mentioned. No Linux shell (bash) scripting examples are provided for automation, and troubleshooting references (e.g., WinSCP documentation) are Windows-focused.
Recommendations
- Include Linux-native FTP/S client examples (e.g., lftp, ncftp, FileZilla) alongside or before Windows tools.
- Add sample Linux shell (bash) commands for connecting and uploading via FTP/S.
- When listing tools, alternate or balance the order (e.g., mention FileZilla and Cyberduck before WinSCP and Visual Studio).
- Provide troubleshooting links or examples relevant to Linux users (e.g., command-line FTP troubleshooting, FileZilla documentation).
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Consider including a section or callout specifically for Linux/macOS users, highlighting any OS-specific considerations.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-local-git.md
...ocs/blob/main/articles/app-service/deploy-local-git.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. PowerShell is presented as a primary method alongside Azure CLI and portal, with detailed PowerShell-specific instructions and terminology. There are several references to 'local PowerShell terminal' and Windows-specific tools (e.g., Git Credential Manager dialog, MSBuild, node-gyp errors referencing Windows). There is a lack of explicit Linux/macOS terminal or shell examples, and troubleshooting sections reference Windows-specific errors and build tools before mentioning cross-platform equivalents.
Recommendations
- Add explicit Linux/macOS terminal instructions and examples, especially where PowerShell is referenced (e.g., 'In a local terminal' instead of 'In a local PowerShell terminal').
- Include Bash or shell command alternatives for PowerShell cmdlets, or clarify which commands are cross-platform.
- When mentioning tools like Git Credential Manager or MSBuild, also mention their Linux/macOS equivalents or note their cross-platform availability.
- In troubleshooting, provide error messages and solutions relevant to Linux/macOS environments (e.g., native module build errors on Linux, authentication dialogs on macOS).
- Ensure that CLI examples are presented before or alongside PowerShell, and avoid assuming Windows as the default environment.
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows examples and terminology (such as IISNode, web.config, and PowerShell) are often presented first or exclusively, while Linux equivalents are sometimes less detailed or appear later. Some troubleshooting and configuration sections focus on Windows-specific tools or patterns (e.g., web.config, IISNode) without always providing Linux alternatives or parity in explanation. The Application Insights instrumentation section references PowerShell for automation but does not mention Bash or Linux CLI alternatives.
Recommendations
- Ensure that for every Windows-specific example (such as web.config, IISNode, or PowerShell instructions), a Linux equivalent (e.g., nginx config, PM2, Bash/CLI instructions) is provided with equal prominence and detail.
- Alternate the order of Windows and Linux pivots or present both platforms side-by-side to avoid the perception of Windows-first bias.
- Where PowerShell is mentioned for automation (e.g., enabling Application Insights), provide Bash or Azure CLI examples for Linux users.
- Expand troubleshooting sections to include Linux-specific issues and solutions, not just Windows (e.g., what to do if the app fails to start due to missing startup commands or permissions in Linux containers).
- When referencing tools like IISNode or web.config, clarify that these are Windows-only and provide explicit Linux alternatives (such as PM2 configuration or startup command guidance).
- Review all sections for parity in depth and clarity between Windows and Linux instructions, especially in advanced configuration and debugging scenarios.
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 provides both Linux and Windows sections for most tasks, but there are several areas where Windows tools, patterns, or instructions are mentioned first or exclusively. Windows-specific tools such as Kudu and FTPS are referenced without always providing Linux-native alternatives. Some instructions (e.g., process explorer in Kudu, Debug Console) are Windows-centric, and there is a tendency to mention Windows or its configuration options before Linux equivalents. In a few places, Linux-specific details are marked as 'Linux only' rather than providing parity for both platforms.
Recommendations
- Ensure that for every Windows-specific tool or workflow (such as Kudu, FTPS, Debug Console), an equivalent Linux-native approach is described, or explicitly state if not available.
- When listing instructions or configuration options, alternate the order or present Linux and Windows in parallel, rather than always listing Windows first.
- Provide Linux-native file transfer and diagnostic tools (e.g., SCP, SFTP, rsync) as alternatives to FTPS for downloading files like JFR recordings.
- Where possible, avoid language that implies Windows is the default or primary platform (e.g., 'On Windows, you can...'), and instead use neutral phrasing or present both platforms equally.
- Expand on Linux troubleshooting and management tools, such as using SSH, Linux package managers, and command-line utilities, to match the depth of Windows/Kudu coverage.
- Review all examples and ensure that both Linux and Windows users have clear, actionable instructions for all major workflows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-run-package.md
...s/blob/main/articles/app-service/deploy-run-package.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias by referencing Windows file paths (e.g., D:\home\site\wwwroot) before Linux equivalents, focusing on Windows directory structures, and omitting explicit Linux/Bash command examples or Linux-specific instructions. The use of backslashes in paths and references to Windows-style directories are prevalent, while Linux paths are mentioned only in passing. There are no Linux-specific troubleshooting notes or parity in deployment instructions.
Recommendations
- Provide Linux-specific examples alongside Windows ones, including explicit Linux file paths (e.g., /home/site/wwwroot) and directory structures.
- Include Bash or Linux shell command examples where appropriate, especially for manual deployment steps.
- Ensure all path references are given in both Windows and Linux formats, not just as a parenthetical note.
- Add troubleshooting notes relevant to Linux environments, such as file permission issues or differences in mounting behavior.
- Review all instructions and ensure that Linux users are given equal clarity and guidance as Windows users.
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 First
Windows Tools
Powershell Heavy
Summary
The documentation generally provides parity between Linux and Windows for most APM configuration steps, but there are subtle signs of Windows bias. In several places, Windows-specific tools (like the Kudu console) are mentioned for Windows, while SSH is used for Linux. In the Application Insights section, the Windows example includes an extra app setting (XDT_MicrosoftApplicationInsights_Java=1) not explained for Linux. The order of presentation sometimes places Windows before Linux, and references to Windows tools and patterns are more explicit. There are no missing Linux examples, but the documentation assumes familiarity with Windows-specific tooling and sometimes provides more detailed steps for Windows.
Recommendations
- Ensure that all platform-specific steps are equally detailed for both Linux and Windows, including explanations for any extra app settings or environment variables.
- When referencing platform-specific tools (like Kudu for Windows), provide equivalent Linux alternatives or clarify if not applicable.
- Present Linux and Windows instructions in a consistent order (e.g., Linux first if targeting OSS audiences, or alternate order in sections).
- Explain any differences in environment variables or app settings between platforms, so Linux users are not left wondering about missing options.
- Where possible, use cross-platform tools or commands (e.g., Azure CLI, FTP, or zip deployment) instead of platform-specific consoles.
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 PowerShell scripting and Windows-specific file paths and tools (e.g., PowerShell, %HOME%, %LOCAL_EXPANDED%). The Linux instructions are present and generally sufficient, but the Windows configuration is described with more step-by-step detail and custom scripting. Additionally, Windows-specific tools and patterns (PowerShell, .cmd files) are emphasized, and in some sections, the Windows approach is described before the Linux equivalent.
Recommendations
- Ensure Linux and Windows instructions are equally detailed, especially for advanced scenarios (e.g., custom Tomcat configuration).
- Provide Linux shell script examples with the same level of detail as the Windows PowerShell scripts, including error handling and step-by-step explanations.
- Where possible, present Linux and Windows instructions in parallel or side-by-side, rather than Windows-first.
- Avoid assuming PowerShell as the default scripting language; offer Bash or sh alternatives for Linux users.
- Clarify when a tool or pattern is Windows-only and suggest the closest Linux equivalent.
- Review for any missing Linux-specific troubleshooting or automation tips that are present for Windows.
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and patterns (such as IISNode, web.config, and PowerShell) are mentioned prominently, sometimes before or in more detail than their Linux equivalents. Windows examples or explanations often precede Linux ones, and some advanced configuration or troubleshooting steps are only detailed for Windows (e.g., web.config troubleshooting), with Linux sections being more generic or referring to includes. PowerShell is referenced for Application Insights instrumentation, with no equivalent Bash/Azure CLI example for Linux. Some sections (like custom deployment scripts) are more detailed for Linux, but overall, Windows concepts and tools are more deeply integrated and explained.
Recommendations
- Ensure Linux and Windows instructions/examples are presented with equal prominence and detail, ideally side-by-side or in parallel sections.
- For every PowerShell or Windows tool reference (e.g., web.config, IISNode), provide the Linux/container equivalent (e.g., startup scripts, PM2, nginx/apache config, etc.), or explicitly state when there is no equivalent.
- Add Bash/Azure CLI examples for Application Insights instrumentation on Linux, not just PowerShell.
- Expand troubleshooting and advanced configuration sections for Linux to match the depth provided for Windows (e.g., what to do if the app does not start, common misconfigurations, etc.).
- When referencing tools like IISNode or web.config, clarify their scope (Windows-only) and provide links or guidance for Linux users.
- Review the order of presentation so that Linux and Windows are treated equally, or alternate which platform is presented first in each section.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-app-service-certificate.md
...s/app-service/configure-ssl-app-service-certificate.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, but does not include any Linux-specific or bash-native examples beyond Azure CLI. The PowerShell example is given its own section, and there is a FAQ entry specifically about PowerShell. There are no references to Linux tools, OpenSSL, or Linux-native certificate management patterns. The documentation assumes use of the Azure Portal or Azure CLI/PowerShell, which are cross-platform, but does not address Linux-specific workflows or mention Linux certificate stores.
Recommendations
- Add explicit bash/Linux shell examples for certificate export and handling, such as using OpenSSL to inspect or convert the .pfx file.
- Include notes or examples for importing certificates into common Linux web servers (e.g., Apache, Nginx) after export.
- Balance the PowerShell examples with equivalent bash or Linux-native commands where possible.
- Mention Linux certificate stores and how to use the exported .pfx file with them.
- In FAQs and troubleshooting, include Linux-specific scenarios and not just PowerShell-centric issues.
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
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by featuring PowerShell automation prominently, mentioning it before (and more visibly than) Azure CLI, and not providing Linux-specific or cross-platform command-line examples. The automation section gives a direct PowerShell script embed, while the Azure CLI is only linked. There are no Linux shell or bash examples, and no mention of Linux tools or workflows for certificate management or upload.
Recommendations
- Provide explicit Linux/bash command-line examples alongside or before PowerShell, especially in automation sections.
- Embed Azure CLI examples directly in the documentation, not just as links, and ensure parity with PowerShell scripts.
- Include references to Linux-native tools (such as OpenSSL for certificate management) where relevant.
- Ensure that language in the documentation is platform-neutral unless a step is truly OS-specific.
- Add a section or callouts for Linux/macOS users, clarifying any differences in workflow or tooling.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-php.md
...ob/main/articles/app-service/configure-language-php.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation generally provides parity between Windows and Linux by using platform pivots, but there are several sections where Windows-specific tools, patterns, and instructions are emphasized or provided exclusively. Notably, the 'Run Composer' and 'Run Bower, Gulp, or Grunt' sections are only present for Windows, relying on KuduScript and deployment script customization, with no Linux equivalents or guidance. Some instructions (e.g., changing the site root) use Windows paths and tools first, and Windows-specific details (like .dll extensions, directory structures, and KuduScript) are described in more detail or earlier than their Linux counterparts. In some cases, Linux instructions are less detailed or missing for common tasks.
Recommendations
- Add Linux equivalents for 'Run Composer', 'Run Bower, Gulp, or Grunt', and custom deployment script automation, including examples of how to achieve similar automation using Oryx hooks or custom scripts.
- Ensure that for every Windows-specific tool or pattern (e.g., KuduScript, .dll, Windows directory paths), a Linux equivalent (.so, Linux paths, SSH/Bash instructions) is provided with equal detail and prominence.
- Where possible, present Windows and Linux instructions side-by-side or in parallel pivots, and avoid placing Windows instructions or tools first unless there is a clear reason.
- Expand the Linux sections to include more detailed, step-by-step guidance for tasks that are described in detail for Windows (e.g., custom deployment automation, enabling extensions, changing site root).
- Review for any missing Linux examples or references, especially for automation and deployment customization, and add them to ensure parity.
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 demonstrates a Windows bias in several ways: Windows tools and workflows (IIS, Certreq.exe, PowerShell) are mentioned explicitly, sometimes without Linux equivalents or with Windows methods listed first. PowerShell is given as a primary automation example alongside Azure CLI, but Linux-native certificate management tools (beyond OpenSSL) and Linux-specific workflows are not covered. The documentation assumes familiarity with Windows concepts and tools, and Linux users may find gaps in guidance for common certificate management tasks.
Recommendations
- Provide Linux-native examples for certificate request and export, such as using OpenSSL for both certificate generation and export, and detail how to perform these tasks on Linux systems.
- When mentioning Windows tools (IIS, Certreq.exe), also mention Linux equivalents (e.g., OpenSSL, certbot) and provide links or brief instructions.
- In automation sections, include Bash scripting or Linux CLI examples alongside PowerShell, and clarify any OS-specific differences.
- Avoid listing Windows tools or workflows before Linux equivalents; instead, present both options in parallel or in OS-specific tabs.
- Clarify any App Service features or limitations that differ between Windows and Linux hosting plans, especially in the FAQ and outbound certificate usage sections.
- Expand the FAQ to address common Linux scenarios, such as managing certificates on Linux-based App Service plans or containers.
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
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for enabling virtual network integration, but the PowerShell section is significantly more detailed, with step-by-step parameter preparation, validation, and configuration commands. There are no Linux-specific shell (e.g., Bash) or cross-platform scripting examples, and PowerShell (traditionally associated with Windows) is given a prominent, detailed section. The CLI example is brief and lacks the depth of the PowerShell instructions, which may disadvantage Linux users or those preferring Bash scripting.
Recommendations
- Expand the Azure CLI section to include step-by-step instructions equivalent to the PowerShell section, covering parameter validation, subnet delegation, and integration.
- Provide Bash shell script examples for common tasks, especially for subnet delegation and resource manipulation, to improve parity for Linux users.
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, to encourage non-Windows users.
- If possible, add guidance or links for using ARM templates or Bicep for infrastructure-as-code scenarios, which are platform-agnostic.
- Avoid assuming PowerShell as the default scripting environment; present CLI or Bash examples first or in parallel with PowerShell.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-zip.md
...zure-docs/blob/main/articles/app-service/deploy-zip.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific paths (e.g., D:\home\site\wwwroot) are mentioned before Linux equivalents, and the Kudu UI ZIP deploy method is explicitly unavailable for Linux. The use of PowerShell is presented as a primary method alongside Azure CLI, but PowerShell support is missing for several scenarios (with only CLI and API alternatives given). There is also a reliance on Azure portal navigation (Advanced Tools/Kudu), which is more familiar to Windows users. Linux-specific deployment nuances and parity in tooling are not fully addressed.
Recommendations
- Present Linux and Windows paths and behaviors in parallel, not with Windows first.
- Clearly indicate when features are Windows-only and provide equivalent Linux workflows or alternatives, with step-by-step instructions.
- Where PowerShell is not supported, provide Bash or shell script equivalents, especially for Linux users.
- Include more Linux-centric examples and troubleshooting tips, such as using SCP, SFTP, or Linux-native tools for file transfer.
- Clarify differences in Kudu UI and API availability between Windows and Linux, and link to Linux-specific documentation where appropriate.
- Avoid defaulting to Windows terminology (e.g., drive letters, backslashes) in general explanations.
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, language-specific examples (C#, Java) for accessing certificates in Windows environments and referencing Windows certificate stores and tools. Linux guidance is less prominent, with Linux-specific code examples appearing later and only for C#. Other languages (Node.js, PHP, Python, Java) are not covered for Linux, and users are directed to external documentation. Windows tools and patterns (certificate store, environment variables, user profile settings) are discussed in depth, while Linux equivalents are less thoroughly explained.
Recommendations
- Provide Linux examples for all major supported languages (Node.js, Python, Java, PHP), not just C#.
- Present Linux and Windows guidance in parallel or with equal prominence, rather than leading with Windows.
- Include Linux-specific tools and patterns (e.g., OpenSSL, Linux file permissions, environment variable usage) where appropriate.
- Where Windows-specific settings or tools are discussed (e.g., certificate store, user profile), provide Linux equivalents or clearly state when they are not applicable.
- Avoid referencing only Windows certificate stores; explain Linux certificate handling (e.g., file-based, OpenSSL integration) in similar detail.
- Ensure that all code samples and instructions are available for both platforms, or explicitly state any platform limitations.
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
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prominently featuring Windows-centric tools (such as Visual Studio, Azure PowerShell, and the App Service migration assistant for PowerShell scripts) and referencing them before or more frequently than cross-platform or Linux-native equivalents. There is a lack of explicit Linux or bash examples, and Linux-friendly tools or workflows (such as deploying from a Linux shell, using SCP/SFTP, or Linux-native editors) are not mentioned. The documentation assumes familiarity with Windows tools and does not provide parity for Linux users.
Recommendations
- Include explicit Linux/bash command examples alongside PowerShell and Windows tool references.
- Mention and link to Linux-native deployment workflows (e.g., using SCP/SFTP, rsync, or bash scripts for deployment).
- Provide parity in documentation for Linux-based editors and IDEs (e.g., JetBrains Rider, Eclipse, or command-line git workflows) alongside Visual Studio.
- Clarify which tools and methods are cross-platform and which are Windows-only, and suggest alternatives for Linux users where appropriate.
- Add references to Linux-specific documentation or quickstarts for deploying to Azure App Service.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-best-practices.md
...lob/main/articles/app-service/deploy-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. Kudu is described first as a Windows tool, with Linux support mentioned secondarily. FTP and WebDeploy (Windows-centric tools) are listed as primary deployment mechanisms, with no mention of Linux equivalents like SFTP or rsync. There are no explicit Linux shell or command-line examples, and the language-specific sections do not address Linux-specific deployment caveats or tools. While there is a GitHub Actions example that runs on Ubuntu, the overall framing and tool references favor Windows environments.
Recommendations
- Present Kudu's Linux and Windows behaviors equally, or mention Linux support first where relevant.
- Include Linux-native deployment mechanisms (e.g., SFTP, rsync) alongside FTP and WebDeploy.
- Add Linux shell (bash) examples for common deployment tasks, not just Azure CLI or YAML.
- In language-specific sections, note any differences or best practices for Linux App Service plans.
- Where possible, avoid listing Windows tools or patterns before their Linux equivalents, or present both together.
- Clarify when instructions or tools are cross-platform, and provide links to Linux-specific documentation where available.
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 from IIS servers, and make extensive use of Windows-specific tools such as PowerShell scripts and MSI installers. There is no mention of Linux-based .NET hosting environments (e.g., Apache, Nginx, Kestrel on Linux), nor are there migration paths or tools described for Linux-origin .NET apps. The documentation also references Windows containers but omits Linux container scenarios.
Recommendations
- Add guidance and examples for migrating .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel) to Azure App Service.
- Include Linux-based migration tools or scripts, or clarify if such tools are not available.
- Provide parity in documentation by listing Linux migration scenarios and tools alongside Windows ones, not just Windows-first.
- If PowerShell scripts are provided, also offer Bash or cross-platform CLI equivalents where possible.
- Mention and document migration to Linux-based App Service plans, not just Windows-based ones.
- Clarify any limitations or differences in migration support between Windows and Linux environments.
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 hosted on IIS web servers within VMware environments, which are Windows-centric technologies. There are no references to Linux-based hosting (e.g., Kestrel, Apache, Nginx) or examples for discovering .NET apps running on Linux. All discovery capabilities and dashboards are described in the context of Windows (IIS), and no Linux equivalents or instructions are provided.
Recommendations
- Include information about discovering .NET web apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx).
- Provide parallel examples or instructions for Linux-based environments, including any differences in discovery steps or tooling.
- Mention whether Azure Migrate supports Linux-hosted .NET apps, and if not, clarify this limitation explicitly.
- Add references or links to resources for migrating or discovering .NET apps on Linux, if available.
- Ensure future documentation covers both Windows and Linux scenarios equally, or clearly states platform limitations.
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 page demonstrates a mild Windows bias. While both Azure CLI and Azure PowerShell examples are provided, PowerShell (a Windows-centric tool) is given equal prominence to the cross-platform Azure CLI, and no Linux-native scripting or shell examples (e.g., Bash) are shown. In the section on SKU availability, the 'Windows' example is listed before the 'Linux' example. The instructions and screenshots focus on the Azure Portal UI, which is platform-agnostic, but scripting automation leans toward Windows tools.
Recommendations
- Provide explicit Bash shell script examples for Linux users, especially in the automation section.
- When listing platform-specific commands (such as SKU availability), alternate the order or present Linux and Windows examples side by side.
- Clarify that Azure CLI commands are cross-platform and can be run on Windows, macOS, and Linux.
- If referencing PowerShell, mention that PowerShell Core is available cross-platform, or provide Bash equivalents.
- Consider including a table summarizing commands for both Windows (PowerShell) and Linux (Bash/CLI) 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 shows a Windows bias by presenting Windows-specific information and tools first, such as mentioning Windows SKU availability before Linux, and including Azure PowerShell examples (which are primarily used on Windows) without equivalent Bash or Linux shell script examples. The automation section provides both Azure CLI and PowerShell, but the PowerShell example is not accompanied by a Linux-native scripting example. The portal instructions and screenshots are Windows-centric, and there is no mention of Linux-specific considerations or UI differences. Additionally, the documentation does not provide parity in examples or guidance for Linux users, especially for scripting and automation.
Recommendations
- Present Linux and Windows options in parallel, or alternate which comes first to avoid 'windows_first' bias.
- Provide Bash or shell script examples alongside PowerShell for automation tasks.
- Include screenshots or notes for both Windows and Linux portal experiences if they differ.
- Explicitly mention any Linux-specific considerations, such as differences in deployment, configuration, or tool usage.
- Ensure that all command-line examples (especially for automation) are cross-platform or have equivalents for both Windows and Linux users.
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 several forms of Windows bias. Windows installation and GUI instructions are consistently presented before Linux equivalents, and some troubleshooting steps (such as using PowerShell's Test-NetConnection) are only shown for Windows. Windows-specific tools and patterns (e.g., GUI, MSI installer, PowerShell commands) are described in detail, while Linux alternatives are sometimes less detailed or omitted (e.g., no Linux equivalent for Test-NetConnection, no Linux GUI). Some instructions and troubleshooting steps lack Linux-specific guidance or examples.
Recommendations
- Present Linux and Windows instructions in parallel or alternate which comes first to avoid 'windows_first' bias.
- For every PowerShell or Windows-specific command (e.g., Test-NetConnection), provide an equivalent Linux command (e.g., nc, curl, or telnet) and example.
- Where a GUI is not available on Linux, offer equivalent CLI workflows and highlight any feature gaps.
- Ensure troubleshooting sections include Linux-specific tools and commands for connectivity and DNS checks (e.g., use 'nc', 'dig', or 'host').
- Expand Linux installation and usage instructions to match the detail level of Windows instructions.
- Explicitly note any feature parity gaps (such as lack of GUI on Linux) and, where possible, provide workarounds or roadmap information.