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 201-225 of 2121 flagged pages
App Service
Configure Data Sources for Tomcat, JBoss, or Java SE Apps
...es/app-service/configure-language-java-data-sources.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides detailed, step-by-step instructions for configuring Tomcat data sources on Windows, including PowerShell scripts and Windows-specific file paths and tools. In contrast, Linux instructions are less detailed, rely on general shell scripting, and assume familiarity with Linux package management and file conventions. Windows examples use PowerShell and CMD, while Linux examples use shell scripts and package managers but with less explanation. Windows configuration patterns (copying Tomcat, setting CATALINA_BASE, using PowerShell for XSLT) are described in depth, whereas Linux relies on generic startup scripts and XSLT tools. The documentation also presents Windows instructions after Linux, but the Windows section is longer and more tool-specific.
Recommendations
- Provide equally detailed Linux examples, including sample startup scripts for common distributions (e.g., Ubuntu, Alpine), with explicit instructions for copying Tomcat, setting environment variables, and performing XSLT transforms.
- Include Linux-specific troubleshooting tips and common pitfalls, similar to the Windows section.
- Offer parity in tool recommendations: for example, suggest Linux equivalents for PowerShell tasks (such as using Bash, xmlstarlet, or xsltproc for XML transforms).
- Clarify file paths and conventions for Linux (e.g., where to place configuration files, how to set environment variables persistently).
- Add a comparison table showing Windows and Linux steps side-by-side for common tasks.
- Ensure that Linux instructions are as discoverable and comprehensive as Windows instructions, with explicit code samples and explanations.
Create Pull Request
App Service
SSH Access for Linux and Windows Containers
...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 and troubleshooting. In contrast, Windows containers are only mentioned briefly, with no equivalent command-line or tool-based examples for SSH access. The documentation focuses on Linux tools and patterns, and omits Windows-specific guidance or parity in SSH access methods.
Recommendations
- Add equivalent step-by-step instructions for opening SSH sessions to Windows containers, including any available command-line tools or PowerShell examples.
- Clarify whether SSH access to Windows containers is possible via Azure CLI, PowerShell, or other tools, and provide examples if supported.
- If SSH access for Windows containers is only available via browser, explicitly state this limitation and offer troubleshooting or alternative remote access methods for Windows.
- Ensure that both Linux and Windows container sections have parity in detail, examples, and troubleshooting guidance.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. Windows instructions and tools (e.g., IISNode, web.config, PowerShell) are often mentioned first or exclusively, with Linux equivalents sometimes relegated to later sections or missing entirely. Some troubleshooting and configuration steps are detailed for Windows but only briefly referenced or omitted for Linux. PowerShell is referenced for instrumentation, but Bash or Linux-native alternatives are not provided. Windows-specific tools and patterns (IISNode, web.config) are described in detail, while Linux alternatives (e.g., Nginx, .htaccess, or container startup scripts) are not covered.
Recommendations
- Ensure that Linux instructions/examples are presented alongside or before Windows equivalents, especially in introductory and troubleshooting sections.
- Provide Linux-native alternatives for all Windows-specific tools and patterns (e.g., discuss Nginx or container startup scripts in place of IISNode/web.config).
- Include Bash or Azure CLI examples for instrumentation and configuration tasks where PowerShell is referenced.
- Expand troubleshooting guidance for Linux deployments to match the detail provided for Windows (e.g., common errors, configuration file issues).
- Add explicit parity checks to ensure every Windows example or tool has a Linux counterpart, and vice versa.
App Service
Configure Managed Instance on Azure App Service (Preview)
...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 Windows-centric, focusing exclusively on Windows Server 2022 as the operating system for Managed Instance on Azure App Service. All configuration script examples use PowerShell (.ps1), with explicit statements that only PowerShell is supported. Features such as registry key configuration, MSI installation, and RDP/Bastion access are all Windows-specific. There are no Linux equivalents or examples, and no mention of Linux tooling, shell scripts, or Linux-based configuration patterns.
Recommendations
- Clearly state in the introduction and FAQ that Managed Instance on Azure App Service is Windows-only, and direct Linux users to alternative offerings (such as Linux App Service plans or Azure Container Apps).
- If Linux support is planned, provide equivalent examples using Bash scripts, Linux storage mount patterns (e.g., NFS), and Linux configuration tools.
- Where possible, mention cross-platform alternatives for configuration, storage, and remote access (e.g., SSH for Linux, Bash for scripting).
- Add a comparison table or section that outlines feature parity and differences between Windows and Linux App Service plans.
- Explicitly call out limitations for non-Windows workloads to prevent confusion for users seeking Linux support.
App Service
Use TLS/SSL Certificates in App Code
...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, code samples, and certificate store usage before Linux equivalents. Windows certificate store access is described in detail for C# and Java, while Linux instructions are limited and deferred to later sections. Non-Windows languages (Node.js, PHP, Python) are not given direct examples, and users are referred to external documentation. Windows tools and patterns (certificate store, environment variables, FTPS, user profile loading) are emphasized, with Linux alternatives mentioned only briefly or generically.
Recommendations
- Provide Linux examples alongside Windows examples, especially for popular languages (Node.js, Python, Java, PHP) rather than referring users to external documentation.
- Present Linux and Windows instructions in parallel, or use tabs to avoid Windows-first ordering.
- Include Linux-specific tools and patterns (e.g., OpenSSL, file permissions, environment variables) where appropriate.
- Expand code samples for Linux environments, including direct access to certificate files in multiple languages.
- Clarify differences in certificate management between Windows and Linux, and offer troubleshooting tips for both platforms.
- Avoid assuming Windows as the default hosting environment; mention Linux parity in introductory sections.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Windows tools (IIS, Certreq.exe) are mentioned for certificate export, and PowerShell examples are provided alongside Azure CLI, but there are no Linux-specific command line examples or references to Linux certificate management tools. Windows scenarios (e.g., Windows container apps for outbound calls with private CA certificates) are explicitly called out, while Linux equivalents are not discussed. The order of examples and FAQs tends to mention Windows or PowerShell before Linux or cross-platform alternatives.
Recommendations
- Add explicit Linux certificate export instructions, e.g., using OpenSSL for both certificate request and export, and clarify steps for Linux users.
- Provide Linux-specific examples for automating certificate binding, such as Bash scripts or references to Azure CLI usage on Linux.
- When mentioning Windows tools (IIS, Certreq.exe), also mention Linux alternatives or clarify platform applicability.
- Ensure parity in FAQ answers by discussing Linux container scenarios and limitations where relevant.
- When listing automation options, present Azure CLI (cross-platform) before PowerShell, and clarify that both work on Linux and Windows.
- Add notes or links for Linux users regarding certificate management and troubleshooting in App Service.
App Service
Configure CI/CD with Azure Pipelines
...ob/main/articles/app-service/deploy-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific deployment methods (such as Web Deploy) are described in detail, with explicit instructions to use Windows agents and references to IIS and web.config. Linux deployment options are mentioned but not explored with equivalent depth, and some examples default to Windows agents or tools. There are no Linux-specific deployment method examples, and troubleshooting focuses on Windows agent scenarios. The order of presentation often puts Windows-related options and terminology first.
Recommendations
- Provide equivalent Linux deployment examples, especially for advanced scenarios (e.g., using Kudu, FTP, or ZIP deploy on Linux agents).
- Add troubleshooting guidance for Linux agents, such as common issues with Linux-based deployments.
- Clarify which deployment methods are cross-platform and which are Windows-only, ideally in a comparison table.
- Include Linux-first or Linux-specific examples for popular frameworks (Node.js, Python, Java) and deployment patterns.
- Balance references to Windows tools (Web Deploy, IIS, web.config) with Linux alternatives (nginx, Apache, environment variables, etc.).
- Explicitly state agent OS requirements for each deployment method at the top of relevant sections.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure portal, but consistently lists Azure PowerShell (a Windows-centric tool) as a primary method alongside Azure CLI. PowerShell examples are given equal prominence to CLI, even though PowerShell is less commonly used on Linux. There is no mention of Linux-specific tools or workflows (such as Bash scripts or Linux-native credential management patterns), and the only shell-specific advice is a brief note about escaping the dollar sign in Bash. The documentation does not provide any Linux-first or Linux-only examples, and the ordering of examples sometimes places PowerShell before CLI, reinforcing a Windows-centric approach.
Recommendations
- Add explicit Linux/Bash examples for credential management, such as using Bash scripts to interact with Azure CLI.
- Clarify that Azure PowerShell is primarily a Windows tool and suggest Azure CLI as the preferred cross-platform method.
- Reorder examples to present Azure CLI before Azure PowerShell, emphasizing CLI as the default for cross-platform usage.
- Include notes or sections on Linux-specific considerations, such as file permissions, shell environments, or integration with Linux automation tools.
- Mention that Azure CLI is available natively on Linux and macOS, and provide installation links or guidance for those platforms.
App Service
Configure continuous deployment
...n/articles/app-service/deploy-continuous-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias. The 'External Git' section explicitly mentions 'For Windows apps,' suggesting that manual continuous deployment setup is primarily for Windows, with no mention of Linux or cross-platform scenarios. References to Kudu (a Windows-centric deployment engine) and basic authentication patterns are present, but there are no Linux-specific deployment examples, tools, or troubleshooting steps. The documentation does not provide parity for Linux App Service environments, nor does it clarify differences in deployment for Linux vs. Windows App Service.
Recommendations
- Add explicit instructions and examples for configuring continuous deployment to Linux-based App Service apps, including any platform-specific considerations.
- Clarify whether manual setup via 'External Git' is supported for Linux apps and provide guidance if so.
- Include troubleshooting steps and links relevant to Linux deployments, such as SSH-based deployment, Linux build environments, or differences in authentication.
- Where Kudu or Windows-specific tools are mentioned, note Linux alternatives or cross-platform compatibility.
- Ensure screenshots and UI instructions are applicable to both Windows and Linux App Service apps, or clearly indicate any differences.
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 examples are given equal prominence to Azure CLI, and Windows-specific FTP clients (Visual Studio, WinSCP) are mentioned first or exclusively. There are no explicit Linux command-line FTP client examples (e.g., lftp, curl, ftp), nor are Linux desktop tools (e.g., FileZilla) highlighted. Troubleshooting and connection instructions reference Windows patterns and tools, with little guidance for Linux users.
Recommendations
- Add explicit Linux command-line FTP/S examples using standard tools like lftp, curl, or ftp.
- Include Linux desktop FTP client recommendations (e.g., FileZilla, GNOME Files).
- Ensure that tool lists (FTP clients) mention cross-platform and Linux-first options before or alongside Windows tools.
- Provide troubleshooting steps and port/firewall guidance for Linux environments (e.g., iptables, ufw).
- Balance PowerShell and CLI examples by clarifying that Azure CLI works on Linux/macOS and showing Linux shell usage.
- Add screenshots or walkthroughs for Linux users where relevant (e.g., connecting via FileZilla).
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell for all operations, but PowerShell is given equal prominence to CLI, and Windows-specific tools and configuration patterns (such as Web.config and applicationInitialization) are referenced without Linux equivalents. Troubleshooting and warm-up instructions rely on Windows file paths (D:\home\LogFiles) and IIS/Web.config, with no mention of Linux alternatives. There is no coverage of Linux-specific deployment slot behaviors, nor are Linux-native configuration files or troubleshooting paths discussed.
Recommendations
- Add explicit notes and examples for Linux users, especially for web apps on Linux and Web App for Containers, including any differences in deployment slot behavior.
- Provide Linux-native configuration and troubleshooting instructions (e.g., mention log file locations for Linux, alternatives to Web.config/applicationInitialization for warm-up).
- Clarify which features (such as auto swap, custom warm-up) are not supported on Linux, and suggest Linux-friendly alternatives or workarounds.
- Include bash scripting examples alongside PowerShell, and reference Linux tools (such as curl, jq) where appropriate.
- Where Windows-specific patterns (Web.config, IIS) are mentioned, add equivalent instructions for Linux stacks (e.g., startup scripts, environment variables, nginx/apache config).
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for configuring Traffic Manager and App Service Environments. There are no equivalent CLI (az), Bash, or Linux-oriented instructions. The only automation and scripting method shown is PowerShell, which is primarily associated with Windows environments. Additionally, references to Azure Resource Manager Traffic Manager support are PowerShell-centric, and no mention is made of Linux tools or cross-platform alternatives.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, showing how to create and configure Traffic Manager profiles and endpoints using Bash or shell scripts.
- Include notes or sections indicating that all steps can be performed from Linux, macOS, or Windows, and provide links to cross-platform tooling.
- Reference documentation for both PowerShell and Azure CLI, making clear that users can choose their preferred environment.
- Where screenshots or console outputs are shown, consider including examples from Linux terminals (e.g., using dig/nslookup in Bash) as well as Windows.
- Avoid language that implies PowerShell is the default or only option; present it as one of several supported methods.
App Service
Certificates in App Service Environment
...icles/app-service/environment/overview-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several areas. The per-app private client certificate method is explicitly limited to Windows code apps, with no Linux equivalent or workaround described. All example commands for certificate verification and creation use PowerShell, and the Kudu console instructions are Windows-specific. There are no Linux shell or cross-platform examples for these scenarios. The documentation does mention that the recommended Root Certificate API method works for both Windows and Linux, but when it comes to practical, step-by-step instructions and code samples, only Windows tools and workflows are provided.
Recommendations
- Provide equivalent instructions and examples for Linux-based apps, especially for certificate verification and creation (e.g., using Bash, OpenSSL, or Linux-native tools).
- Clarify whether there is any supported method for per-app root certificate configuration on Linux, or explicitly state the limitation and suggest alternatives.
- Where PowerShell is used for certificate creation or verification, offer OpenSSL or Bash alternatives for Linux users.
- In the Kudu console section, mention how Linux users can access the certificate store and verify installation.
- Review all step-by-step instructions to ensure parity for both Windows and Linux environments, or clearly document any platform-specific limitations.
App Service
Deploy From a Local Git Repository
...ocs/blob/main/articles/app-service/deploy-local-git.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions, but PowerShell is given its own dedicated section and is referenced multiple times, which may imply a Windows-centric workflow. The troubleshooting section includes errors and solutions specific to Windows environments (e.g., native module binary distribution for Windows). There is mention of the Git Credential Manager dialog, which is primarily a Windows tool, without equivalent Linux credential management guidance. No explicit Linux shell or tool examples are provided beyond basic Bash commands, and PowerShell instructions are presented before portal instructions, potentially prioritizing Windows workflows.
Recommendations
- Add explicit Linux shell instructions and examples, especially for credential management and troubleshooting (e.g., handling SSH keys, credential prompts in Linux/Mac).
- Mention cross-platform alternatives to Git Credential Manager, such as using SSH keys or credential helpers available on Linux/Mac.
- Balance PowerShell and CLI examples by providing Bash or zsh equivalents for all steps, and clarify which commands are cross-platform.
- In troubleshooting, include Linux-specific error messages and solutions, such as file permission issues or case sensitivity problems.
- Avoid assuming the use of Windows tools (e.g., Git Credential Manager) and provide parity for Linux/Mac users in all workflow steps.
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 paths and behaviors are mentioned first and in more detail (e.g., 'D:\home\site\wwwroot' before Linux '/home/site/wwwroot'). The Kudu UI workflow is described as unavailable for Linux, but no Linux-specific alternatives are shown in detail. PowerShell examples are provided for most deployment scenarios, but Linux shell equivalents (e.g., Bash scripts) are not given for PowerShell-only features. The use of Windows-centric terminology (e.g., 'Advanced Tools', 'Kudu', 'D:\home\site\scripts') is prevalent, and Linux-specific deployment nuances are not covered. In some cases, features are marked as 'not supported' in PowerShell, but no Linux-native alternatives (such as SCP, rsync, or SFTP) are suggested.
Recommendations
- Present Linux paths and behaviors before or alongside Windows equivalents, especially in introductory sections.
- For UI-based deployment, provide step-by-step alternatives for Linux users (such as FTP, SFTP, or direct API usage), not just a brief mention.
- Where PowerShell examples are given, add equivalent Bash or shell script examples for Linux users.
- Discuss Linux-specific deployment tools and patterns (e.g., SCP, rsync, SFTP) where relevant, especially when PowerShell is not supported.
- Clarify differences in deployment experience between Windows and Linux App Service, including limitations and workarounds.
- Use neutral terminology and avoid Windows-centric language where possible (e.g., refer to 'file system paths' rather than 'D:\home\site\wwwroot').
App Service
Getting started with Azure App Service
...docs/blob/main/articles/app-service/getting-started.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the .NET and Python sections. Windows-centric tools (Visual Studio, Azure PowerShell) are listed before Linux alternatives, and PowerShell is included as a primary option for .NET app creation. Python quickstart links default to 'windows' tabs, and Linux-specific instructions are less prominent or absent in some places. The 'Next step' call-to-action also directs users to an ASP.NET (Windows-first) workflow.
Recommendations
- Ensure Linux CLI and cross-platform tools are listed before or alongside Windows-specific options in all quickstart tables.
- Provide explicit Linux examples and instructions for all stacks, especially .NET and Python, including bash/terminal commands and Linux-based IDE workflows.
- Avoid defaulting to Windows tabs or instructions in quickstart links; use neutral or Linux-first pivots where possible.
- Include Azure CLI and other cross-platform deployment options as primary choices, not secondary to PowerShell.
- Balance references to Visual Studio with Visual Studio Code and other cross-platform editors.
- Review 'Next step' actions to ensure they are not Windows/.NET-centric unless contextually appropriate.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell is heavily featured as a primary automation tool, with multiple dedicated sections and examples. Windows-centric tools and patterns (PowerShell cmdlets) are presented before or in addition to cross-platform alternatives. There is no mention of Linux-specific shell scripting (e.g., Bash), nor are there examples using Linux-native tools for token retrieval or resource management. The CLI examples use Azure CLI, which is cross-platform, but scripting examples and automation are PowerShell-heavy, and there are no Bash or Linux shell equivalents provided. This may disadvantage Linux users or those working in non-Windows environments.
Recommendations
- Add Bash and Linux shell scripting examples for all scenarios where PowerShell is used, especially for token retrieval and resource management.
- Explicitly mention cross-platform compatibility for Azure CLI commands and provide sample usage in Linux environments.
- Where PowerShell is referenced, provide equivalent Bash/Unix shell commands, especially for automation tasks.
- Include notes or sections on using managed identities from Linux-based environments, including troubleshooting and environment variable usage.
- Ensure that examples and instructions do not assume a Windows environment by default, and clarify platform-specific differences where relevant.
App Service
Create an App by Using a Terraform Template
...n/articles/app-service/provision-resource-terraform.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits mild Windows bias in several areas. In the prerequisites, Windows and PowerShell configuration options are listed before Linux equivalents, and Windows-specific tooling (PowerShell, Visual Studio Code) is emphasized. While both Linux and Windows Terraform templates are provided, the overall structure and ordering tend to foreground Windows approaches and tools, with Linux options presented as alternatives rather than defaults.
Recommendations
- List Linux/Bash configuration options before Windows/PowerShell options in the prerequisites to avoid implicit prioritization.
- Provide explicit parity in tooling recommendations, such as mentioning Linux-native editors (e.g., Vim, Nano) alongside Visual Studio Code.
- Ensure that Linux examples and instructions are given equal prominence and detail as Windows examples throughout the documentation.
- Where possible, avoid grouping Windows and PowerShell together as the default or first-listed options.
- Add notes or guidance for users working on Linux systems, including troubleshooting and environment setup tips.
App Service
Per-App Scaling for High-Density Hosting
...blob/main/articles/app-service/manage-scale-per-app.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by providing only PowerShell examples for per-app scaling, with no equivalent examples for Linux users (such as Azure CLI or Bash). The use of PowerShell cmdlets and parameters assumes a Windows-centric workflow, and there is no mention of Linux-native tools or cross-platform scripting options.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands to support Linux and cross-platform users.
- Include Bash scripting examples where appropriate, especially for configuring app settings.
- Explicitly mention that per-app scaling can be managed from any platform using Azure CLI or ARM templates, not just PowerShell.
- Consider reordering or presenting PowerShell and CLI examples side-by-side to avoid implying Windows-first workflows.
- Clarify that ARM templates are platform-agnostic and can be used from any OS.
App Service
Securely connect .NET apps to Azure SQL Database using Managed Identity
...icles/app-service/tutorial-connect-msi-sql-database.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows/Visual Studio workflows, providing PowerShell and Windows-centric instructions, and omitting explicit Linux/macOS development and tooling examples. Visual Studio for Windows is described in detail, while Linux/macOS users are only briefly referenced via Azure CLI or Visual Studio Code, with no equivalent depth or troubleshooting guidance. PowerShell and Windows tools are used for database access and package management, and there are no explicit Bash or cross-platform alternatives for key steps.
Recommendations
- Provide explicit Linux/macOS development environment setup instructions, including common editors (e.g., VS Code, JetBrains Rider) and terminal workflows.
- Offer Bash or cross-platform (e.g., sqlcmd via Docker, Azure Data Studio) alternatives for database access and management, not just PowerShell.
- Include package management instructions using dotnet CLI (dotnet add package ...) in addition to or instead of PowerShell-based NuGet commands.
- Ensure all code and command-line examples are presented for both Windows and Linux/macOS environments, or clearly indicate cross-platform compatibility.
- Balance the order of presentation so that Windows and Linux/macOS instructions are given equal prominence, or group them under clear tabs/sections.
- Add troubleshooting tips or notes relevant to Linux/macOS users, especially for authentication, connectivity, and tooling differences.
App Service
Supported platforms and file types
...includes/webjobs-create/webjobs-supported-platforms.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation lists Windows hosting options before Linux, and Windows-specific file types (.exe, .cmd, .bat, .ps1) are mentioned first and in more detail than Linux equivalents. PowerShell scripts are called out separately, while Bash scripts are grouped with other scripting languages. There is a stronger emphasis on Windows tools and patterns, with Linux examples and tools mentioned only after Windows ones.
Recommendations
- List Linux hosting options and file types before or alongside Windows equivalents to avoid implicit prioritization.
- Provide equal detail for Linux tools (e.g., highlight Bash scripts and Linux executables explicitly, not just as part of a list).
- Include examples or notes for Linux-specific patterns, such as shell scripts (.sh), and mention Linux command-line tools where relevant.
- Avoid grouping Linux scripting under 'other scripting languages' while calling out Windows/PowerShell scripts separately.
- Consider adding a table or section that clearly shows parity between Windows and Linux supported file types and patterns.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/webjobs-create/webjob-types.md
...es/app-service/includes/webjobs-create/webjob-types.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation lists Windows file types and tools (cmd, bat, exe, PowerShell) in detail and provides multiple examples for Windows scenarios, while Linux sections only mention *.sh* scripts and give fewer, less varied examples. Windows tools and patterns (cmd, PowerShell) are described explicitly, whereas Linux equivalents (bash, shell, etc.) are not. The order of presentation also places Windows before Linux.
Recommendations
- Expand Linux sections to list more supported file types (e.g., *.py*, *.pl*, *.rb*, *.js*, *.jar*) and explicitly mention runtimes/tools (bash, python, node, java, etc.).
- Provide Linux-specific examples similar to the Windows ones, showing how to use different script types and runtimes.
- Balance the order of presentation so that Linux and Windows are treated equally, or alternate which platform is listed first.
- Explicitly mention the installed runtimes/tools for Linux, as is done for Windows.
- Clarify any differences in support between platforms, and ensure parity where possible.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific paths (e.g., %HOME%, D:\home\site\wwwroot) and terminology are used throughout, often without equivalent Linux examples or explanations. Tools and workflows such as Kudu DebugConsole and FTP uploads reference Windows-style paths and methods first or exclusively. References to Azure PowerShell are prominent, with no mention of Linux shell scripting or Bash alternatives. Examples and instructions for file exclusion and backup filtering use Windows paths and conventions, with no Linux equivalents provided. Although some sections mention Linux (e.g., backup content under /home), the overall documentation assumes Windows as the default environment and omits Linux-specific guidance.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, especially for file paths, backup filters, and upload methods.
- Include Bash or shell script samples for backup automation, not just Azure PowerShell.
- Clarify platform-specific differences in backup behavior, file locations, and tooling (e.g., Kudu DebugConsole usage on Linux, alternative upload methods).
- Use neutral or dual-platform terminology and examples (e.g., show both %HOME% and /home paths, D:\home\site\wwwroot and /home/site/wwwroot).
- Ensure that references to tools (FTP, Kudu, etc.) include Linux-compatible alternatives and instructions.
App Service
Migrate Docker Compose to sidecars
...es/app-service/migrate-sidecar-multi-container-apps.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by requiring PowerShell for both script-based and manual migration steps, providing only PowerShell script examples, and referencing PowerShell-specific tooling for tasks like base64 decoding. No Linux shell (bash) or cross-platform alternatives are provided, and Windows tools/patterns are mentioned before any Linux equivalents (which are absent).
Recommendations
- Provide equivalent bash shell script examples for Linux and macOS users, especially for tasks like base64 decoding.
- Offer a cross-platform migration script (e.g., in bash or Python) or clarify how Linux users can adapt the PowerShell script.
- List prerequisites in a cross-platform manner, mentioning bash/zsh as alternatives to PowerShell.
- Explicitly state which steps require PowerShell and how to perform them on Linux/macOS.
- Include notes or links to Linux/macOS documentation for Azure CLI and Docker usage.
- Ensure all code snippets have Linux/macOS equivalents where possible.
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits Windows bias primarily in its coverage of Hybrid Connections, where only Windows Server is mentioned as a supported platform for the Hybrid Connection Manager, with no reference to Linux support or alternatives. Additionally, the gateway-required virtual network integration feature is explicitly limited to Windows plans, and this limitation is described before any Linux options are discussed. There are no examples or instructions for Linux users in these sections, and Windows-centric tools and patterns are referenced without Linux parity.
Recommendations
- Explicitly state whether Hybrid Connection Manager is available for Linux, and provide installation/configuration instructions for Linux if supported.
- For gateway-required virtual network integration, clarify Linux limitations and suggest alternative approaches for Linux users.
- Where Windows-only features are described, add equivalent Linux guidance or alternatives, or clearly call out platform limitations.
- Include Linux-specific examples and tooling references alongside Windows examples to ensure parity.
- Review all sections for implicit Windows-first language and rephrase to be platform-neutral where possible.