App Service
806
Total Pages
669
Linux-Friendly Pages
137
Pages with Bias
17.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
247 issues found
Showing 51-75 of 247 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-key-vault-references.md
...ticles/app-service/app-service-key-vault-references.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 configuration tasks, but PowerShell examples are always presented immediately after CLI, and there is no mention of Linux-specific tools or shell environments (e.g., Bash, zsh). The CLI examples are generic, but the PowerShell examples reinforce a Windows-centric approach. There are no explicit Linux shell script examples, nor is there discussion of Linux-specific patterns or troubleshooting steps. The troubleshooting and portal navigation instructions do not mention platform differences, but the overall example set leans toward Windows/PowerShell usage.
Recommendations
- Add explicit Bash/zsh shell examples for configuration tasks alongside Azure CLI and PowerShell.
- Clarify that Azure CLI commands work cross-platform and provide shell-specific notes for Linux users.
- Include troubleshooting steps or notes relevant to Linux environments, such as file permissions or environment variable handling.
- Avoid presenting PowerShell examples immediately after CLI by alternating or grouping examples by platform.
- Reference Linux tools or patterns where appropriate, such as using environment variables in Bash scripts.
Create Pull Request
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 page demonstrates Windows bias by presenting Windows-specific information and tools first, such as SKU availability for Windows before Linux, and PowerShell examples alongside Azure CLI. The Azure portal (a Windows-centric tool) is emphasized for configuration steps, and there are no Linux shell or automation examples (e.g., Bash scripts). Linux-specific patterns, such as using Bash or Linux-native tools, are missing, and the documentation does not mention Linux container limitations until after Windows details.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which comes first to avoid implicit prioritization.
- Include Bash script examples for automation, especially for Linux users, alongside Azure CLI and PowerShell.
- Clarify when instructions or features differ for Linux and Windows, and provide explicit Linux container guidance.
- Add references to Linux-native tools and workflows (e.g., using SSH, Bash, or Linux package managers) where relevant.
- Ensure that all examples (CLI, scripting, portal) are equally applicable to Linux environments, and note any platform-specific limitations up front.
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 toward Windows and PowerShell. All command-line examples are provided exclusively using PowerShell cmdlets (Az PowerShell module), with no mention of Azure CLI, Bash, or cross-platform alternatives. The only non-portal method described is PowerShell, which is primarily associated with Windows environments. There is no guidance for Linux or macOS users, nor are there references to tools or workflows common on those platforms.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available cross-platform, or provide instructions for installing and using PowerShell on Linux/macOS if PowerShell is required.
- Reorder sections or provide parallel instructions so that Azure CLI and PowerShell are presented with equal prominence.
- Include Bash script examples or references to REST API usage for advanced users who may not use PowerShell.
- Clearly indicate any platform-specific limitations or requirements for the tools being used.
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 Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation is heavily focused on Windows-based hosting using IIS and iisnode, with exclusive references to Windows concepts, tools, and configuration files (such as web.config, named pipes, Win32 error codes, and DLLs). There are no Linux or cross-platform examples, and troubleshooting steps, file paths, and error codes are all Windows-specific. Linux equivalents, tools, or deployment patterns are not mentioned or provided.
Recommendations
- Add sections or examples for running Node.js on Azure App Service for Linux, including configuration and troubleshooting steps relevant to Linux-based environments.
- Provide Linux/Unix equivalents for file paths, error logs, and process management (e.g., referencing /var/log or using PM2 instead of iisnode).
- Include examples using Linux-native tools and patterns (such as systemd, Nginx/Apache reverse proxy, or environment variables) alongside or before Windows/IIS-specific ones.
- Clarify early in the document that the guidance is specific to Windows-based App Service plans, and link to Linux-specific documentation if available.
- Balance the use of Windows-centric terminology (like Win32 error codes, DLLs, web.config) with Linux alternatives (such as exit codes, .env files, or JSON-based configuration).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation contains a minor Windows bias. The only explicit OS-specific command mentioned is for clearing the DNS cache, where only the Windows 'ipconfig /flushdns' command is provided. No equivalent Linux or macOS commands are given. Additionally, the troubleshooting section references Windows first and omits parity for other platforms. There are no PowerShell-heavy sections or exclusive use of Windows tools elsewhere, but the lack of Linux/macOS examples is a notable omission.
Recommendations
- When providing OS-specific troubleshooting commands (such as clearing DNS cache), include equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
- Wherever Windows-specific tools or patterns are mentioned, ensure Linux and macOS equivalents are also referenced, or clarify that the instructions are cross-platform.
- Review the documentation for any other implicit Windows-first assumptions and add clarifying notes or alternative steps for non-Windows users.
- Consider adding a short section or callout noting that all steps can be performed from any OS, and link to platform-specific DNS troubleshooting guides if needed.
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias in the 'Server level (Windows apps only)' section, where IIS and web.config-based authorization is described exclusively for Windows apps, with no Linux equivalent or alternative provided. Windows-specific tools (IIS, web.config) are mentioned, and Linux is only referenced to state that it is unsupported for these features, without offering guidance for Linux users.
Recommendations
- Provide equivalent authorization guidance for Linux-based App Service apps, such as using middleware, configuration files (e.g., appsettings.json), or code samples for popular frameworks (Node.js, Python, .NET Core).
- Include Linux-specific examples and tools where relevant, or link to external resources for Linux authorization patterns.
- When describing platform-specific features, present both Windows and Linux options side-by-side, or clearly direct Linux users to alternative solutions.
- Avoid language that simply states Linux is unsupported; instead, offer actionable alternatives or workarounds for Linux users.
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 provides detailed C#/.NET examples and references to Windows-centric frameworks (ASP.NET, .NET Core, Microsoft.Identity.Web) before mentioning alternatives for other languages. There are no explicit Linux shell, Python, or Node.js code examples, and the only non-.NET examples are brief mentions (PHP, Java) without code. There is no discussion of accessing headers or decoding claims in Linux-native tools or languages, nor any mention of Linux-specific patterns or shell commands.
Recommendations
- Add code examples for popular Linux-first languages such as Python (Flask/Django), Node.js (Express), or Ruby, showing how to access and decode the claims headers.
- Include shell/command-line examples (e.g., using curl and jq) to demonstrate how to inspect or decode the X-MS-CLIENT-PRINCIPAL header.
- Present non-Windows examples (e.g., Python, Node.js) before or alongside .NET/C# examples to avoid a Windows-first impression.
- Expand the 'Framework-specific alternatives' section with concrete code snippets for Linux-prevalent stacks.
- Clarify that the approach is cross-platform and that all examples are equally applicable on Linux and Windows hosts.
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 Windows bias by referencing Azure Storage Explorer with Windows-specific instructions and tabs, and by omitting Linux alternatives or parity in tooling and examples. There are no Linux-specific instructions or mentions of Linux-compatible tools for uploading files or generating SAS tokens. The documentation also references GUI-based workflows (Azure portal, Storage Explorer) that are more common on Windows, without CLI or Linux-native alternatives.
Recommendations
- Include instructions for uploading package files and generating SAS tokens using cross-platform tools such as Azure CLI, azcopy, or REST API, with explicit Linux command examples.
- Add Linux-specific tabs or sections alongside Windows instructions when referencing Azure Storage Explorer, or clarify cross-platform compatibility.
- Mention and provide examples for Linux users on how to perform key operations (file upload, SAS generation) without relying on Windows-only tools.
- Ensure that all referenced tools and workflows are available and documented for both Windows and Linux environments, or provide alternatives where necessary.
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 Only
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. Gateway-required virtual network integration is explicitly stated to only work for Windows plans, with Linux apps excluded. All troubleshooting and connectivity examples use Windows tools (e.g., PowerShell's Test-NetConnection, netstat), with no mention of Linux equivalents. There are no Linux-specific instructions, examples, or troubleshooting steps, and Windows terminology and tools are used exclusively throughout.
Recommendations
- Clearly state Linux alternatives and limitations at the top of the document, including guidance for Linux users.
- Provide Linux-specific troubleshooting steps and tool equivalents (e.g., use 'nc', 'telnet', or 'ss' for connectivity checks instead of Test-NetConnection and netstat).
- Where features are Windows-only, link to Linux-compatible alternatives (such as regional virtual network integration) and provide migration guidance.
- Include examples and screenshots from Linux environments where possible.
- Ensure parity in documentation structure, so Linux users can easily find relevant information and steps.
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 exclusively referencing Windows-based deployment and configuration patterns, such as Visual Studio publishing, Kudu (CMD/PowerShell), and Windows filesystem paths. There are no Linux-specific examples or instructions, and Windows tools and workflows are mentioned first and exclusively, leaving Linux users without guidance for equivalent tasks.
Recommendations
- Add Linux-specific examples for listing .NET Framework versions, such as using SSH or Linux-based diagnostic tools in App Service Linux environments.
- Include instructions for accessing Kudu or equivalent diagnostic consoles in Linux-based App Service plans.
- Provide guidance for deploying ASP.NET apps from Linux development environments (e.g., using VS Code, CLI, or Git from Linux).
- Mention differences in environment variable access and configuration between Windows and Linux App Service plans.
- Clarify which instructions apply only to Windows App Service and provide parallel steps for Linux where possible.
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 CLI examples for connecting to Linux containers via SSH, including command-line usage, troubleshooting, and sample output. In contrast, Windows containers are only mentioned briefly, with no equivalent CLI or PowerShell examples, and it is stated that SSH sessions through Azure CLI are not supported for Windows. The documentation focuses on Linux tools and workflows, with no Windows-specific command-line instructions or parity in example depth.
Recommendations
- Add equivalent step-by-step instructions for connecting to Windows containers, including any supported command-line or PowerShell workflows.
- If Azure CLI is not supported for Windows containers, clarify alternative methods (such as PowerShell, RDP, or other remote tools) and provide examples.
- Include troubleshooting steps and sample output for Windows container SSH sessions, similar to the Linux section.
- Ensure that both Linux and Windows sections have comparable detail and actionable guidance for administrators.
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
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits a Windows-first bias: Windows instructions and tools (such as Visual Studio and Kudu) are mentioned before Linux equivalents, and Windows-specific patterns (like using CMD/PowerShell in Kudu) are described in detail. Visual Studio is presented as the default publishing tool, with Linux container deployment discussed as an alternative. Linux instructions are present but often follow Windows sections, and some tooling (Kudu, Visual Studio) is Windows-centric.
Recommendations
- Present Windows and Linux instructions in parallel, giving equal prominence to both platforms.
- Include Linux-native tooling and workflows (such as VS Code, CLI, or GitHub Actions) alongside Visual Studio and Kudu.
- Where possible, avoid assuming Visual Studio as the default publishing tool; mention cross-platform alternatives.
- Expand Linux sections to match the detail and clarity of Windows sections, especially for build, deployment, and diagnostics.
- Ensure that introductory and summary content does not prioritize Windows over Linux, and avoid language that frames Linux as secondary.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/app-service-app-service-environment-geo-distributed-scale.md
...-service-app-service-environment-geo-distributed-scale.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples for configuring Azure Traffic Manager and App Service Environments. There are no CLI, Bash, or Linux-oriented instructions, and Windows/PowerShell tooling is referenced first and exclusively. This may hinder Linux users or those preferring cross-platform tools.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands to support Linux and macOS users.
- Include Bash script snippets or instructions where relevant.
- Explicitly mention that both PowerShell and CLI approaches are supported and provide links to cross-platform tooling.
- Reorganize sections so that cross-platform options (e.g., Azure CLI) are presented before or alongside PowerShell.
- Add notes or callouts for Linux/macOS users regarding tool installation and usage.
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 Windows and Linux instructions, but there are subtle signs of Windows bias. Windows-specific tools (e.g., Kudu console) are mentioned for file operations, while Linux relies on SSH. In some cases, Windows-specific settings (such as 'XDT_MicrosoftApplicationInsights_Java=1') are included, and Windows instructions sometimes appear before or are more detailed than Linux equivalents. There is also a tendency to reference Windows-centric patterns (like Kudu) without offering Linux alternatives (e.g., SCP, SFTP, or Azure CLI for file uploads).
Recommendations
- For file operations, mention Linux-native tools (SCP, SFTP, Azure CLI) alongside SSH, not just SSH for Linux and Kudu for Windows.
- Ensure that Linux instructions are as detailed as Windows ones, especially regarding environment variables and agent configuration.
- When introducing platform-specific settings (like 'XDT_MicrosoftApplicationInsights_Java=1'), explain their Linux equivalents or clarify if not needed.
- Avoid Windows-first ordering in examples and instructions; present Linux and Windows in parallel or alternate which comes first.
- Where possible, provide cross-platform CLI instructions and avoid referencing Windows-only tools unless absolutely necessary.
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 page demonstrates a moderate Windows bias. Windows-specific tools (IISNode, web.config) and troubleshooting steps are described in detail, while their Linux equivalents are either omitted or referenced less prominently. Windows instructions and examples often appear before Linux ones, and PowerShell is mentioned for Application Insights instrumentation, with no Linux CLI or Bash alternative. Some sections (e.g., troubleshooting, web.config) are Windows-only, with Linux equivalents missing or relegated to includes. The overall structure and depth of Windows content exceeds that of Linux.
Recommendations
- Ensure Linux instructions/examples are presented with equal prominence and detail as Windows, including troubleshooting and configuration steps.
- Provide Linux/Bash alternatives for PowerShell instructions, especially for instrumentation and automation tasks.
- Include explicit Linux equivalents for Windows-specific tools (e.g., IISNode, web.config), or clarify when they are not needed on Linux.
- Avoid presenting Windows instructions before Linux ones; use parallel structure or combine where possible.
- Expand Linux troubleshooting guidance to match the detail provided for Windows.
- Where platform-specific includes are used, summarize their content or link to them directly for parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-data-sources.md
...es/app-service/configure-language-java-data-sources.md
High Priority
View Details →
Detected Bias Types
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 patterns (e.g., startup.cmd, configure.ps1, use of %HOME%, %LOCAL_EXPANDED%, and Windows environment variables). The Linux instructions are more concise and rely on standard shell scripting and package installation, but lack the depth and step-by-step guidance found in the Windows examples. The Windows configuration uses PowerShell and Windows batch files, while the Linux configuration uses shell scripts and standard Linux tools, but the Windows approach is described with more explicit detail and troubleshooting steps. Additionally, Windows-specific tools and patterns (PowerShell, batch files, Windows environment variables) are emphasized, and the Windows section appears before the Linux section in the shared server-level resources area.
Recommendations
- Expand the Linux section to provide equally detailed, step-by-step instructions, including troubleshooting tips and example scripts for common scenarios.
- Provide Linux equivalents for all Windows-specific tools and patterns (e.g., show how to automate configuration with Bash scripts, use environment variables, and manage ephemeral file changes).
- Ensure that Linux instructions appear before or alongside Windows instructions in each section to avoid implicit prioritization.
- Include example startup scripts for Linux that match the complexity and completeness of the Windows PowerShell scripts.
- Add more guidance on managing Tomcat/JBoss configuration files in Linux, including handling ephemeral storage and persistent configuration.
- Where possible, use cross-platform tools and patterns (e.g., Azure CLI, environment variables) in examples to reduce platform-specific bias.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-security.md
...ticles/app-service/configure-language-java-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page generally presents security configuration for Java apps on Azure App Service in a cross-platform manner, but there is evidence of Windows bias. Windows concepts and settings (such as Application Settings for disabling features) are mentioned before Linux equivalents, and Linux-specific instructions (such as Java key store management and SSH access) are isolated to a separate section near the end. There are no explicit Linux command-line examples (e.g., bash, Linux CLI), and Windows-centric terminology (like 'Application Setting') is used throughout. Linux tools and patterns (such as environment variable injection, keytool usage) are only briefly covered and not given parity in example depth.
Recommendations
- Provide Linux-specific examples earlier in the documentation, not just in a dedicated section at the end.
- Include Linux command-line examples (e.g., bash scripts, Azure CLI on Linux) alongside any Windows or portal instructions.
- When mentioning configuration via 'Application Settings', clarify how this maps to Linux environments and containers.
- Offer parity in troubleshooting and debugging instructions for both Windows and Linux (e.g., Powershell vs. SSH/bash).
- Explicitly state when instructions apply to both Windows and Linux, or provide side-by-side examples for each platform.
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page generally maintains parity between Windows and Linux, using zone pivots to separate platform-specific instructions. However, there are several signs of Windows bias: Windows instructions and examples often appear before Linux ones, especially in sections like 'Show the PHP version', 'Set the PHP version', and 'Change the site root'. Windows-specific tools and paths (e.g., KuduScript, d:\home\site, .dll extensions) are referenced in detail, sometimes with more step-by-step guidance than their Linux equivalents. The Windows deployment automation section is more elaborate, while the Linux section is more concise and refers out to external documentation (Oryx). Some examples, such as enabling diagnostic logs, are more detailed for Windows. There is also a heavier reliance on Windows-centric terminology and tools (e.g., Advanced Tools, KuduScript, .dll files) before mentioning Linux alternatives (.so files, NGINX config).
Recommendations
- Ensure Linux instructions and examples are given equal prominence and detail as Windows, possibly by alternating the order or providing a summary table for both platforms.
- Where Windows-specific tools (e.g., KuduScript, Advanced Tools) are mentioned, provide equivalent Linux tooling or clarify Linux alternatives (e.g., Oryx, SSH, Bash).
- Expand Linux sections to include step-by-step guidance matching the detail given for Windows, especially for deployment automation and troubleshooting.
- Avoid Windows-first ordering in sections; consider starting with Linux or providing a neutral introduction before platform pivots.
- Where file paths or extension types are discussed (.dll vs .so), provide parallel examples and clarify compatibility requirements for both platforms.
- Ensure troubleshooting and diagnostic sections include Linux-specific guidance and examples, not just references to external documentation.
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 demonstrates Windows bias by prioritizing PowerShell automation, referencing Azure PowerShell scripts directly, and lacking Linux-specific command-line examples (such as Bash or Azure CLI). While Azure CLI is mentioned, no direct CLI code samples are provided, and the scripting section features only PowerShell code. There are no references to Linux tools or workflows for certificate management, nor are Linux-specific file formats or commands discussed.
Recommendations
- Add direct Azure CLI code samples for certificate binding alongside PowerShell examples.
- Include Linux/Bash workflows for uploading and managing certificates, such as using OpenSSL to generate or convert certificates.
- Reference Linux-specific documentation or guides for certificate management and automation.
- Ensure that scripting and automation sections present both Windows (PowerShell) and Linux (CLI/Bash) options equally and in parallel.
- Mention relevant Linux tools (e.g., OpenSSL, keytool) when discussing certificate formats and uploads.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-managed-instance.md
...ain/articles/app-service/configure-managed-instance.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows-specific features and tooling. All configuration script examples use PowerShell (.ps1), and only Windows Installer (MSI), COM registration, IIS configuration, and registry keys are discussed. Storage mounts reference drive letters and UNC paths, which are Windows-centric. RDP and Bastion access are described solely for Windows environments. There is no mention of Linux equivalents, nor any examples or guidance for Linux-based managed instances.
Recommendations
- Add explicit notes clarifying that Managed Instance on Azure App Service is currently Windows-only, or provide Linux support details if available.
- Where possible, provide parity for Linux: include Bash or shell script examples, discuss Linux configuration patterns (e.g., .sh scripts, systemd services), and describe Linux storage mount conventions (e.g., mounting NFS or SMB shares to /mnt).
- If registry key adapters are Windows-only, clarify this and suggest Linux alternatives (such as environment variables or config files).
- For remote access, mention SSH as the Linux equivalent to RDP/Bastion and provide guidance if/when Linux support is available.
- Review FAQ and examples to ensure Linux users are not misled or excluded; add sections or links for Linux scenarios if/when supported.
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 examples for configuring virtual network integration, but the PowerShell section is significantly more detailed, with step-by-step instructions and multiple code blocks. PowerShell is a Windows-centric tool, and its prominence (with more elaborate guidance) suggests a bias toward Windows users. There are no Linux shell (bash) examples, nor is there mention of Linux-specific tooling or patterns. The ordering also places PowerShell after CLI, but the depth of PowerShell coverage is greater.
Recommendations
- Add equivalent step-by-step instructions for Azure CLI, matching the detail provided for PowerShell.
- Include bash shell examples for Linux users, especially for subnet delegation and resource configuration.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- If possible, provide links or references to Linux-specific guidance or troubleshooting.
- Balance the depth of coverage between PowerShell and CLI to ensure Linux parity.
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 page demonstrates a Windows bias by presenting Windows-specific instructions, examples, and code samples first and in greater detail. Windows certificate store usage is explained thoroughly with C# and Java code, while Linux examples are limited to C# file loading and lack parity in other languages. References to Windows tools and patterns (certificate store, environment variables, user profile loading) are frequent, while Linux equivalents are only briefly mentioned or deferred to external documentation. Non-Windows languages (Node.js, PHP, Python, Java) are not given direct Linux examples.
Recommendations
- Provide Linux-first or parallel examples for all major languages (C#, Java, Node.js, PHP, Python) showing how to load certificates from files or environment variables.
- Expand Linux-specific instructions, including how to use certificate files and environment variables in common Linux application stacks.
- Add explicit Linux code samples for Java, Node.js, PHP, and Python, not just C#.
- Balance explanations of certificate storage and access patterns between Windows and Linux, including container scenarios.
- Reference Linux tools and patterns (e.g., OpenSSL, file permissions, environment variables) alongside Windows tools.
- Ensure that instructions for setting app settings and accessing certificates are equally clear for Linux environments.
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 bias toward Windows-centric tools and workflows. Windows tools such as Azure PowerShell, Visual Studio, and migration assistants are featured prominently, often with dedicated rows and references. Visual Studio (Windows-only) is listed before Visual Studio Code (cross-platform), and PowerShell is given its own section. There is a lack of explicit Linux or cross-platform CLI examples, and no mention of Linux-specific deployment tools or workflows (e.g., Bash scripts, SCP, rsync, or Linux package managers). The documentation does not provide parity for Linux users in terms of examples or tool recommendations.
Recommendations
- Add explicit Linux deployment examples, such as using Bash scripts, SCP, rsync, or Linux-based CI/CD tools.
- Include references to cross-platform editors and tools (e.g., VS Code, JetBrains IDEs) before or alongside Windows-only tools like Visual Studio.
- Provide Azure CLI examples using Bash or Zsh shells, and clarify that Azure CLI is cross-platform.
- Mention Linux-native authentication workflows and how they integrate with Azure App Service.
- Balance the documentation by listing cross-platform or Linux-first tools and workflows before or alongside Windows-centric ones.
- Add guidance for deploying from Linux environments, including troubleshooting and best practices.
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 exhibits mild Windows bias by referencing Windows-specific deployment mechanisms (Kudu as a separate process in Windows App Service, WebDeploy, FTP) before mentioning their Linux equivalents. The description of Kudu emphasizes its Windows implementation first and only briefly notes its Linux container role. WebDeploy is a Windows-centric tool, and no Linux-native alternatives (such as rsync, SCP, or SFTP) are discussed. There are no explicit Linux shell or command-line examples for deployment, and the language-specific sections (Java, Node, .NET) do not provide Linux-specific deployment guidance or examples. The only explicit Linux reference is in the GitHub Actions workflow (runs-on: ubuntu-latest), but this is generic and not discussed as a parity point.
Recommendations
- Provide Linux-native deployment examples, such as using SCP, rsync, or SFTP, alongside FTP/WebDeploy.
- Clarify Kudu's role and implementation in Linux App Service before or alongside the Windows description.
- Mention Linux equivalents or alternatives to WebDeploy for file-based deployments.
- Include explicit Linux shell command examples for common deployment tasks.
- Add guidance for troubleshooting and diagnostics using Linux tools or logs, not just Azure portal navigation.
- Ensure language-specific sections (Java, Node, .NET) include Linux deployment caveats or best practices where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-configure-credentials.md
...n/articles/app-service/deploy-configure-credentials.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, with PowerShell (a Windows-centric tool) given equal prominence to CLI. There are no explicit Linux shell (bash) or cross-platform scripting examples, and PowerShell is mentioned as an alternative for most actions. The documentation does not mention Linux-specific tools or patterns, nor does it provide guidance for Linux users beyond a brief note about escaping the dollar sign in Bash. The structure presents Azure CLI first, but PowerShell is always present as a parallel option, which may reinforce a Windows-centric workflow.
Recommendations
- Add explicit bash shell examples for common tasks, such as using curl or other Linux-native tools where appropriate.
- Include notes or sections on using these commands in Linux/macOS environments, including installation and authentication differences.
- Clarify that Azure CLI is cross-platform and provide guidance for using it in Linux environments.
- Where PowerShell is not supported (e.g., user-scope credential creation), provide Linux-native alternatives or clarify the CLI method is recommended for Linux users.
- Add troubleshooting tips for Linux users, such as handling file permissions, environment variables, and shell-specific issues.
- Consider mentioning or linking to documentation for deploying from Linux-based CI/CD pipelines.