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 51-75 of 2121 flagged pages
App Service
Node.js Best Practices and Troubleshooting
...rvice-web-nodejs-best-practices-and-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation is heavily focused on Windows-specific tooling and patterns, particularly IIS and iisnode, which are not available on Linux. All configuration examples and troubleshooting steps reference Windows concepts (e.g., web.config, named pipes, Win32 error codes, DLLs, d:\home\LogFiles), and there are no Linux equivalents or cross-platform alternatives provided. The documentation assumes the use of node.exe and does not mention node on Linux or App Service Linux environments.
Recommendations
- Add equivalent guidance for Node.js apps running on Linux-based Azure App Service (e.g., using PM2, Nginx, or Kestrel).
- Provide Linux-specific troubleshooting steps and log file locations.
- Include configuration examples for Linux environments (e.g., environment variables, process managers, startup scripts).
- Mention differences between Windows and Linux App Service environments and clarify which instructions apply to each.
- Avoid assuming the presence of Windows-only concepts (web.config, named pipes, Win32 errors) and offer alternatives for Linux.
- Balance examples and recommendations between Windows and Linux to ensure parity.
Create Pull Request
App Service
Configure Sign in with Apple (Preview)
...app-service/configure-authentication-provider-apple.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation provides a code example for generating the Apple client secret JWT using C# and the Microsoft.IdentityModel.Tokens NuGet package, which is Windows-centric and assumes a .NET development environment. There are no equivalent examples or guidance for Linux or cross-platform environments (e.g., using OpenSSL, Python, or Node.js). The documentation also references application settings and configuration in a way that may be more familiar to Windows/Azure users, without acknowledging Linux-native workflows.
Recommendations
- Provide equivalent code samples for generating the client secret JWT using cross-platform tools such as Python (with PyJWT), Node.js (with jsonwebtoken), or OpenSSL command-line utilities.
- Explicitly mention that the JWT signing step can be performed on any OS and provide links or examples for Linux/macOS users.
- Avoid referencing only Windows-specific libraries or tools (such as Microsoft.IdentityModel.Tokens) without alternatives.
- Include a section or callout for Linux users, outlining the steps and tools they can use to accomplish the same tasks.
- Ensure that application setting configuration instructions are OS-agnostic or provide Linux-specific guidance where relevant.
App Service
App Service Managed Certificate (ASMC) Changes – July 28, 2025
...e/app-service-managed-certificate-changes-july-2025.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing a PowerShell script for identifying impacted Traffic Manager endpoints, with no equivalent Bash, Azure CLI, or Linux-native example. Instructions for running the script assume a Windows environment (PowerShell), and there is no mention of Linux or cross-platform alternatives. The mitigation steps reference REST API and Azure CLI for certificate management, but the only resource discovery example is PowerShell-based, which may disadvantage Linux users.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for identifying impacted Traffic Manager endpoints, ensuring Linux and macOS users can follow the guidance without requiring PowerShell.
- Explicitly mention cross-platform options and clarify which steps are OS-agnostic (e.g., Azure CLI, REST API).
- Add notes or links to Linux installation and usage instructions for Azure CLI and scripting tools.
- Where PowerShell is referenced, offer alternative commands or scripts for Bash/zsh environments.
- Review all examples and ensure parity between Windows and Linux, especially for resource discovery and automation tasks.
App Service
Tutorial: ASP.NET app with Azure SQL Database
...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio on Windows. All instructions, screenshots, and tooling references assume the user is on Windows, with no mention of Linux or cross-platform alternatives. Examples use PowerShell and Visual Studio-specific features, and Azure App Service (Windows) is selected by default, with no guidance for Linux-based App Service or development workflows. There are no Linux or CLI-based examples, and tools like SQL Server Object Explorer and Package Manager Console are exclusive to Visual Studio on Windows.
Recommendations
- Add instructions and examples for deploying ASP.NET apps to Azure App Service (Linux), including relevant screenshots and steps.
- Provide equivalent workflows using cross-platform tools such as Visual Studio Code, Azure CLI, and .NET CLI.
- Include SQL database management steps using Azure CLI, az sql commands, or Data Studio, rather than only Visual Studio and PowerShell.
- Present both Windows and Linux options for each step, or clearly indicate platform-specific instructions.
- Mention and link to documentation for developing and deploying from macOS and Linux environments.
- Offer guidance for using cross-platform editors and tools (e.g., VS Code, JetBrains Rider) where possible.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. Many features (default documents, virtual directory mapping, handler mappings) are explicitly stated as Windows-only, with no Linux alternatives or workarounds suggested. Examples and terminology (such as IIS, D:\home paths, and PowerShell cmdlets) are Windows-centric. In sections where both Windows and Linux are supported, Windows-specific patterns (like .NET config files) are mentioned first or exclusively. There is a lack of Linux-specific examples or explanations for equivalent functionality, especially for advanced configuration scenarios.
Recommendations
- Clearly indicate feature parity and limitations for Linux and Windows throughout the documentation, especially at the start of each section.
- For Windows-only features (default documents, handler mappings, virtual directories), suggest Linux alternatives or provide guidance for achieving similar outcomes (e.g., using startup commands, web server config files like nginx.conf, or Dockerfile ENTRYPOINT/CMD for custom containers).
- Add Linux-specific examples and command-line patterns where applicable, such as showing how to configure environment variables, default documents, or directory mappings in Linux-based App Service apps.
- Avoid using Windows-centric terminology (IIS, D:\home paths) without Linux equivalents or explanations.
- Where PowerShell is used, provide Bash or shell script equivalents for Linux users, especially for bulk editing and advanced configuration.
- Consider reordering sections or examples so that Linux and cross-platform approaches are presented before or alongside Windows-specific instructions.
App Service
Manage App Service Certificates
...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 demonstrates a Windows bias by providing Azure PowerShell examples and mentioning PowerShell in the FAQ, while not offering equivalent Linux-specific or Bash examples. The ordering of examples places Azure CLI (cross-platform) before PowerShell, but there is no explicit mention of Linux-specific certificate management patterns or tools. The instructions and screenshots are portal-centric and do not address platform-specific nuances for Linux users. There are no references to Linux-native certificate handling (e.g., OpenSSL, Linux file permissions) or troubleshooting steps for Linux environments.
Recommendations
- Add Linux-specific examples for certificate export and management, such as using OpenSSL to handle .pfx files after export.
- Include troubleshooting steps or notes relevant to Linux environments (e.g., file permissions, certificate import paths).
- Provide parity in FAQ and guidance for common Linux issues, not just PowerShell-centric problems.
- Explicitly state that Azure CLI commands are cross-platform and provide sample Bash scripts for Linux users.
- Where PowerShell is mentioned, also mention Bash or other Linux-native tools to ensure equal visibility.
App Service
Disable Basic Authentication for Deployment
...n/articles/app-service/configure-basic-auth-disable.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. It references Windows-centric deployment tools and patterns (FTP, Web Deploy, Visual Studio, MSBuild) without providing Linux-specific equivalents or examples. The monitoring section only mentions FTP and Web Deploy, both traditionally Windows-heavy. The deployment table and troubleshooting notes prioritize Visual Studio and Web Deploy, with additional detail for Windows agents, while Linux agents are mentioned only in passing. There are no explicit Linux/Powershell/Bash command examples for deployment, troubleshooting, or monitoring, and no mention of Linux-native deployment tools (e.g., rsync, SCP, SFTP) or workflows.
Recommendations
- Add Linux-specific deployment examples, such as using SFTP, SCP, or rsync, and clarify how disabling basic authentication affects these methods.
- Include troubleshooting and monitoring instructions for Linux-native tools and workflows.
- Provide parity in deployment tables, listing both Windows and Linux agent behaviors and requirements.
- Reference cross-platform deployment tools (e.g., Git, Azure CLI) with explicit examples for both Windows and Linux environments.
- Clarify whether disabling basic authentication impacts Linux users differently, and provide guidance for Linux-based CI/CD pipelines.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by explicitly stating that gateway-required virtual network integration only works for Windows plans and cannot be used from a Linux app. All examples and troubleshooting steps reference Windows tools (e.g., PowerShell's Test-NetConnection, netstat -aon), with no Linux equivalents provided. There are no Linux-specific instructions or parity in examples, and the documentation does not mention how to perform similar actions on Linux-based environments.
Recommendations
- Clearly state early in the document that gateway-required virtual network integration is not supported for Linux apps, and provide a prominent link to Linux-supported alternatives (such as regional VNet integration).
- Wherever Windows-specific tools or commands are mentioned (e.g., PowerShell, netstat), provide equivalent Linux commands (e.g., curl, nc, ss, netstat) and examples.
- In troubleshooting sections, include Linux-based diagnostic steps and tools for network connectivity and DNS resolution (e.g., using dig, nslookup, or ping on Linux).
- Add a comparison table or section summarizing feature support for Windows and Linux, with clear guidance for Linux users.
- Ensure that all portal-based instructions are clearly marked as OS-agnostic or, if there are differences, provide Linux-specific guidance.
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 environment variables and file paths. The Windows section is longer and more tool-specific (PowerShell, Windows paths), while the Linux section is shorter, relies on shell scripts, and omits some details (e.g., no equivalent to the PowerShell script for copying Tomcat and performing transforms). Windows tools and patterns (PowerShell, .cmd files, Windows environment variables) are emphasized, and Linux instructions are sometimes less explicit or detailed.
Recommendations
- Provide Linux shell script equivalents for all Windows PowerShell examples, including copying Tomcat directories and performing XSL transforms.
- Ensure Linux instructions are as detailed as Windows instructions, including troubleshooting steps and environment variable usage.
- Mention Linux tools (e.g., bash, sh, xsltproc) before or alongside Windows tools, not after.
- Include explicit Linux file paths and environment variable usage in all relevant examples.
- Add parity in startup script examples: show a full Linux startup script that performs the same steps as the Windows PowerShell script.
- Clarify any platform-specific limitations or differences at the beginning of each section.
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 Azure CLI commands and Linux SSH client usage. In contrast, Windows containers are only mentioned briefly, with no equivalent CLI or PowerShell examples, and it is stated that SSH via Azure CLI is not supported for Windows containers. The Linux workflow is described in detail and illustrated with screenshots and command outputs, while Windows is covered superficially.
Recommendations
- Add equivalent step-by-step instructions for opening SSH sessions to Windows containers, including any supported tooling (e.g., PowerShell, Windows SSH clients, or browser-based SSH).
- Clarify whether PowerShell or other Windows-native tools can be used for SSH access, and provide examples if possible.
- If SSH via Azure CLI is not supported for Windows containers, explicitly state alternative methods and provide guidance.
- Include screenshots or sample outputs for Windows container SSH sessions to match the Linux documentation depth.
- Ensure both Linux and Windows sections have parity in detail, examples, and troubleshooting tips.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific content and examples (such as PowerShell commands, Windows parent images, IIS/.NET Framework details, and Windows file paths) are often presented first or in greater detail than Linux equivalents. Some sections (e.g., customizing container memory, compute cores, health ping behavior) provide Windows-specific instructions and examples, while Linux equivalents are missing or less detailed. PowerShell commands are frequently included alongside Bash, but Linux-native tools and patterns are less emphasized. Windows tooling (Kudu, C:\home, IIS, .NET Framework) is referenced more extensively than Linux alternatives.
Recommendations
- Ensure all configuration sections (e.g., memory limits, CPU cores, health ping behavior) include Linux-specific instructions and examples where applicable.
- Present Linux and Windows examples side-by-side, or alternate which platform is shown first to avoid implicit prioritization.
- Expand Linux-specific content to match the detail provided for Windows (e.g., supported parent images, troubleshooting, diagnostic logs).
- Include Linux-native commands and patterns (such as systemctl, journalctl, or Linux file paths) where relevant, not just Bash/az CLI.
- Clarify platform differences explicitly, and provide parity in troubleshooting and advanced configuration guidance for both platforms.
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 in Azure App Service. All runtime version discovery and file system examples use Windows paths and tools (CMD, PowerShell, Kudu), with no mention of Linux equivalents or how to perform similar tasks in a Linux App Service environment. There are no Linux-specific instructions or examples, and Windows tools and patterns are always presented first and exclusively.
Recommendations
- Add parallel instructions and examples for Linux-based App Service plans, including how to check .NET runtime versions and file locations on Linux.
- Include Linux shell (bash) commands and file paths where appropriate, alongside Windows CMD/PowerShell examples.
- Clarify in each section whether the instructions apply to Windows, Linux, or both, and provide links to Linux-specific documentation if available.
- Mention and demonstrate how to use Kudu or SSH for Linux App Service environments, if applicable.
- Ensure that deployment and configuration guidance covers both Windows and Linux hosting scenarios for ASP.NET apps.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias by presenting Windows-specific instructions and tooling (such as Visual Studio and Kudu) before Linux equivalents. Windows tools and patterns (Kudu, PowerShell, Visual Studio publish) are mentioned prominently, while Linux alternatives are introduced later or in separate pivots. Some sections, such as deployment and runtime version inspection, emphasize Windows workflows and tools, with Linux instructions provided as secondary or alternative options. There is also a reliance on Windows-centric terminology and examples, such as referencing CMD/PowerShell and Visual Studio, which may not be as relevant for Linux users.
Recommendations
- Ensure that Linux instructions and examples are presented with equal prominence and detail as Windows ones, possibly alternating the order or combining them where appropriate.
- Provide Linux-native tooling and workflow examples (such as VS Code, CLI, or container-based deployment) alongside Visual Studio and Kudu references.
- Avoid Windows-centric terminology when describing generic concepts; use platform-neutral language where possible.
- Where Windows-specific tools are mentioned (e.g., Kudu, PowerShell), explicitly note Linux alternatives or clarify platform limitations.
- Review all examples to ensure Linux parity, including build automation, environment variable access, and troubleshooting steps.
- Consider adding a summary table or section comparing Windows and Linux workflows for common tasks.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. Windows-specific instructions, tools, and troubleshooting steps (e.g., IISNode, web.config, PowerShell) are often presented before or in more detail than their Linux equivalents. Some sections, such as Application Insights instrumentation, reference PowerShell for setup without mentioning Linux alternatives. Troubleshooting and configuration for Windows (e.g., web.config) are more extensive, while Linux sections are sometimes less detailed or refer to external includes. The use of Windows terminology and tools (IISNode, web.config, PowerShell) is more prominent than Linux-native equivalents.
Recommendations
- Ensure that Linux examples and instructions are presented with equal prominence and detail as Windows ones, especially in troubleshooting and configuration sections.
- Where PowerShell or Windows tools are referenced (e.g., for Application Insights instrumentation), provide equivalent Bash/Azure CLI/Linux-native instructions.
- Expand Linux troubleshooting guidance to match the depth provided for Windows (e.g., common errors, configuration files, deployment issues).
- When mentioning Windows tools (IISNode, web.config), explicitly state the Linux alternatives (e.g., PM2, startup scripts) and provide links or examples.
- Review the order of presentation so that Windows and Linux content are balanced, or Linux is not consistently presented after Windows.
App Service
Secure Your Domain with TLS/SSL
...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 providing PowerShell automation examples but omitting equivalent Linux shell (Bash/Azure CLI) scripts. The 'Automate with scripts' section lists PowerShell after Azure CLI, but only PowerShell code is shown inline, with no Bash or Linux-specific automation guidance. There is also a lack of Linux-specific tooling or workflow examples throughout the page, and no mention of Linux certificate management patterns (e.g., PEM files, OpenSSL usage).
Recommendations
- Add Bash/Azure CLI script examples inline, not just as links, to match the PowerShell coverage.
- Include Linux-specific certificate upload and management instructions, such as handling PEM files or using OpenSSL.
- Provide parity in automation examples by showing both PowerShell and Bash/CLI workflows side-by-side.
- Explicitly mention platform differences where relevant (e.g., certificate file formats, command-line tools).
- Reference Linux documentation or guides for common tasks such as certificate generation and binding.
App Service
Authentication Types by Deployment Methods
...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 moderate Windows bias. Windows-centric tools such as Azure PowerShell and Visual Studio are prominently featured, with dedicated sections and multiple reference links. Visual Studio (Windows-only) is listed before Visual Studio Code (cross-platform), and PowerShell is highlighted as a primary deployment method. There are no explicit Linux-specific deployment tools or examples (e.g., Bash scripts, Linux CLI workflows, or references to Linux-native editors). The documentation does not provide parity for Linux users in terms of examples, tooling, or workflow guidance.
Recommendations
- Add explicit examples and guidance for Linux users, such as Bash scripts or Linux shell commands for deployment.
- Include references to Linux-native editors (e.g., Vim, Emacs) or IDEs (e.g., JetBrains Rider) where relevant.
- Provide parity in documentation for Visual Studio Code by listing it before or alongside Visual Studio, and clarify its cross-platform nature.
- Mention and link to Linux-specific deployment workflows (e.g., using SCP, rsync, or Linux-based CI/CD pipelines).
- Ensure that all PowerShell examples are accompanied by equivalent Bash or shell script examples.
- Highlight the cross-platform nature of Azure CLI and provide Linux installation and usage instructions.
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
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-based examples (e.g., Web Deploy) are presented without Linux equivalents, and Windows agent images are used or referenced first in key sections. Windows-specific deployment tools (Web Deploy, IIS/iisnode) are discussed in detail, while Linux deployment methods are less emphasized or omitted. Some error messages and troubleshooting sections focus on Windows agents, and Linux alternatives are not always provided or explained.
Recommendations
- Provide equivalent Linux deployment examples for all Windows-specific scenarios, especially for Web Deploy (or clarify Linux alternatives such as zip deploy, FTP, or container-based deployment).
- When mentioning agent specifications, list both 'ubuntu-latest' and 'windows-latest' together, or alternate their order to avoid Windows-first bias.
- Include troubleshooting and FAQ sections for common Linux agent issues, not just Windows agent errors.
- Expand documentation on Linux deployment tools and patterns, such as using Kudu REST API, container-based deployments, or native Linux build and deploy workflows.
- Clarify which tasks and deployment methods are cross-platform, and explicitly state limitations or alternatives for Linux users.
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 and code examples first and in greater detail. It focuses heavily on Windows certificate stores, provides C# and Java examples for Windows, and references Windows-specific tools and environment variables. Linux instructions and examples are less detailed, with only C# examples given for Linux containers and other languages (Node.js, PHP, Python, Java) are deferred to external documentation. There is minimal parity in example depth and guidance for Linux users.
Recommendations
- Provide Linux-specific code examples for popular languages (Node.js, Python, Java, PHP) directly in the documentation, not just C#.
- Balance the order of presentation: introduce Linux and Windows approaches side-by-side or in parallel tabs, rather than Windows-first.
- Expand explanations of Linux certificate handling, including common patterns (e.g., using OpenSSL, environment variables, file permissions).
- Reference Linux tools and commands (such as openssl, chmod, etc.) where appropriate.
- Clarify differences and similarities in certificate management between Windows and Linux, including troubleshooting tips for both platforms.
- Add explicit guidance for Linux users outside containers (e.g., App Service on Linux), not just container scenarios.
App Service
Enable integration with an Azure virtual network
...icles/app-service/configure-vnet-integration-enable.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for enabling virtual network integration in Azure App Service. However, the PowerShell section is significantly more detailed, with step-by-step parameter preparation, delegation checks, and resource updates. PowerShell is a Windows-centric tool, and its prominence (with more granular instructions and notes) suggests a bias toward Windows users. There are no Linux shell (bash) examples, nor are Linux-specific tools or patterns mentioned. The CLI example is brief and lacks the depth of the PowerShell walkthrough.
Recommendations
- Expand the Azure CLI section to include step-by-step instructions comparable to the PowerShell section, including parameter preparation, delegation checks, and resource updates.
- Add bash shell examples for Linux users, demonstrating equivalent operations using Azure CLI.
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, but provide parity in example depth and troubleshooting notes for CLI users.
- Include troubleshooting steps or common issues for Linux environments, if applicable.
- Avoid assuming PowerShell as the default automation tool by balancing documentation coverage for CLI and shell scripting.
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, but does not include any Linux- or macOS-specific shell examples (e.g., Bash scripting, curl, or FTP command-line usage). Azure PowerShell is highlighted as an option for several tasks, which is primarily a Windows-centric tool, and it is listed alongside Azure CLI without clarifying cross-platform differences. There are no explicit Linux tool examples, and the only mention of Linux shells is a brief note about escaping the dollar sign in Bash, rather than providing a full example. The documentation implicitly prioritizes Windows tooling and patterns.
Recommendations
- Add explicit Bash (Linux/macOS) shell examples for relevant commands, especially for tasks like retrieving credentials or deploying via FTP/S.
- Include examples using common Linux command-line tools (e.g., curl, lftp, git) for deployment and credential management.
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, while Azure PowerShell is more commonly used on Windows.
- Where PowerShell is mentioned, provide equivalent Bash or shell script examples for parity.
- Consider a 'Linux/macOS' tab alongside 'Azure CLI', 'Azure PowerShell', and 'Azure portal' for each example section.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by prioritizing Windows-centric tools and examples. FTP/S client recommendations list Visual Studio and WinSCP (both Windows-focused) before cross-platform or Linux-native options. Troubleshooting and connection examples reference WinSCP documentation, and there are no explicit Linux command-line or tool examples (e.g., lftp, FileZilla, or Linux CLI usage). PowerShell is given its own tab for endpoint retrieval and configuration, but there is no mention of Linux shell equivalents or scripts. No Linux-specific troubleshooting or guidance is provided.
Recommendations
- Add explicit Linux examples for connecting to FTP/S endpoints using common Linux tools (e.g., lftp, curl, ncftp, or FileZilla).
- Include Linux shell (bash) command-line examples for retrieving publishing profiles and configuring FTPS state, in addition to Azure CLI and PowerShell.
- List cross-platform or Linux-native FTP clients (such as FileZilla, lftp, or GNOME Files) alongside or before Windows-specific tools.
- Provide troubleshooting steps and links relevant to Linux environments (e.g., firewall configuration, passive mode setup, permissions).
- Balance the order of examples and tool recommendations so that Linux and cross-platform options are not always listed after or subordinate to Windows/PowerShell.
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
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure portal, but PowerShell is given a dedicated section with detailed steps, and references to Windows-specific tooling (e.g., Git Credential Manager, MSBuild, node-gyp errors on Windows) are present. There is a subtle Windows-first bias in troubleshooting and deployment steps, with more attention to Windows-specific issues and tools, and PowerShell is presented as a primary automation method alongside CLI, which is cross-platform. There are no explicit Linux-specific examples or troubleshooting notes, and some error messages reference Windows build issues without mentioning Linux equivalents.
Recommendations
- Add explicit Linux/macOS terminal examples and troubleshooting notes, such as common errors with native modules on Linux.
- Mention cross-platform alternatives to Windows tools (e.g., credential managers for Linux/macOS).
- Balance troubleshooting by including Linux-specific issues (e.g., permissions, case sensitivity, native build tool errors).
- Clarify that Azure CLI and Git commands work identically on Linux/macOS, and provide sample commands run in Bash/zsh.
- When referencing build errors (e.g., node-gyp), note that similar issues may occur on Linux/macOS and link to relevant resources.
- Avoid assuming PowerShell is available or preferred; highlight Bash/zsh usage where appropriate.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific paths and tools (e.g., Kudu UI, PowerShell) are mentioned first or exclusively in several places. The Kudu UI ZIP deploy is noted as unavailable for Linux, but no equivalent Linux-native UI or workflow is described. PowerShell examples are provided, but Linux shell equivalents are not, and some features are marked as 'not supported' in PowerShell without clarifying Linux alternatives. Windows paths and terminology (e.g., D:\home\site\wwwroot) are often listed before Linux equivalents. There is limited discussion of Linux-specific deployment nuances or troubleshooting.
Recommendations
- Provide Linux-specific deployment UI or workflow examples where Kudu UI is unavailable.
- Ensure Linux paths and terminology are presented with equal prominence to Windows paths.
- Where PowerShell is used, offer equivalent Bash or shell script examples for Linux users.
- Clarify which features and tools are supported on Linux and provide alternatives or workarounds for unsupported scenarios.
- Add troubleshooting and best practices sections for Linux deployments, especially where behavior differs from Windows.
- Review the order of presentation to avoid listing Windows tools and paths before Linux equivalents unless contextually necessary.
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 demonstrates a moderate Windows bias, particularly in the .NET and Python sections. Windows-centric tools like Visual Studio and Azure PowerShell are listed first or exclusively, while Linux alternatives (such as CLI or VS Code on Linux) are often secondary or missing. The 'Next step' callout exclusively promotes an ASP.NET (Windows-centric) workflow, and some sections (e.g., Python) default to Windows tabs in their quickstart links. Linux-specific instructions and parity for tools are less visible or absent in several stacks.
Recommendations
- Ensure all stacks provide both Windows and Linux examples for each action, especially in quickstart and deployment guides.
- List cross-platform tools (e.g., VS Code, CLI) before Windows-only tools (e.g., Visual Studio, PowerShell) to avoid implicit prioritization.
- Add Linux-specific deployment and management instructions where only Windows or PowerShell examples are given.
- Balance the 'Next step' callout to include a Linux-based workflow or a neutral, cross-platform option.
- Audit tab defaults and pivots to ensure Linux is equally represented and easily discoverable.
- Where Windows tools are mentioned (e.g., Visual Studio, PowerShell), explicitly mention Linux equivalents (e.g., VS Code, Bash, Azure CLI).
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While Azure CLI examples (cross-platform) are provided alongside Azure PowerShell and portal instructions, several features and troubleshooting steps reference Windows-specific tools, patterns, or configuration files (such as Web.config and IIS applicationInitialization). PowerShell examples are given equal prominence to CLI, and some advanced warm-up and troubleshooting scenarios rely on Windows-centric concepts. There is limited mention of Linux-specific deployment patterns, and some features (like auto swap) are explicitly unavailable for Linux-based web apps, but this is only noted in passing.
Recommendations
- Add explicit Linux-specific examples or notes where behaviors differ, especially for warm-up, swap, and troubleshooting steps.
- Provide alternative configuration guidance for Linux-based web apps and containers (e.g., how to specify warm-up actions without Web.config).
- Clarify which features are unavailable or behave differently on Linux, and suggest workarounds or alternatives.
- Where PowerShell is referenced, ensure Bash or shell script equivalents are also provided for parity.
- Highlight cross-platform deployment tools (such as Git, CI/CD pipelines) with examples for both Windows and Linux environments.
- Consider reordering examples so that CLI (cross-platform) instructions appear before PowerShell, or group them by OS context.