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 1401-1425 of 2121 flagged pages
App Service
Enable integration with an Azure virtual network
...icles/app-service/configure-vnet-integration-enable.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling virtual network integration, but the PowerShell section is significantly longer and more detailed. PowerShell is a Windows-centric tool, and the documentation does not mention Linux/macOS equivalents for advanced configuration steps (such as subnet delegation and resource property updates). The CLI example is brief and lacks parity with the PowerShell walkthrough. The order of presentation also places PowerShell after CLI, but the CLI section is minimal compared to the PowerShell section.
Recommendations
- Expand the Azure CLI section to include advanced configuration steps currently only shown in PowerShell (e.g., subnet delegation, resource property updates).
- Explicitly mention that Azure CLI is cross-platform and provide equivalent CLI commands for all PowerShell steps.
- Add notes or links for Linux/macOS users, clarifying that all CLI commands work on those platforms.
- Consider reordering or balancing the detail between CLI and PowerShell sections to avoid implying PowerShell is the preferred or only way.
Create Pull Request
App Service
Migrate Docker Compose to sidecars
...es/app-service/migrate-sidecar-multi-container-apps.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a notable Windows bias. The script-based migration is exclusively presented as a PowerShell script, with no Bash or Linux shell alternative. PowerShell is listed as a prerequisite, and decoding the base64 Docker Compose configuration is demonstrated only with PowerShell. No Linux/macOS shell examples (e.g., Bash, sh) are provided, and Windows tools/patterns appear first and exclusively in critical steps.
Recommendations
- Provide Bash or shell script equivalents for the migration script, or clarify if the PowerShell script runs cross-platform (e.g., with PowerShell Core).
- Add Linux/macOS shell commands for base64 decoding (e.g., `echo <base64value> | base64 -d`).
- List prerequisites for both Windows and Linux/macOS environments, mentioning alternatives to PowerShell.
- Ensure all critical steps have examples for both Windows and Linux/macOS users.
- If the migration script is Windows-only, offer a manual Bash workflow or a cross-platform script.
App Service
Migrate from gateway-based to regional virtual network integration
.../app-service/migrate-gateway-based-vnet-integration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, with PowerShell examples present for every step and shown alongside CLI and portal instructions. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows, and the documentation does not mention or provide Linux/macOS-specific shell examples (e.g., Bash scripts). In all code sections, PowerShell is given equal prominence to CLI, but no Linux-native tools or patterns are referenced. The documentation does not explicitly state that all steps can be performed on Linux/macOS, which may cause friction for non-Windows users.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
- Add Bash shell script examples for key steps, especially for users who prefer native Linux tooling.
- Clarify that Azure PowerShell commands require PowerShell Core for cross-platform use, and provide installation guidance for Linux/macOS if PowerShell is needed.
- Consider listing Azure CLI (cross-platform) examples before PowerShell to reduce perceived Windows-first bias.
- Add a note or section on platform compatibility for all command-line instructions.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page for Kudu service overview demonstrates a mild Windows bias. Several features and examples reference Windows-specific tools (IIS diagnostic dumps, IIS processes, site extensions, deployment webhooks for Windows apps) without mentioning Linux equivalents or clarifying their applicability to Linux-based App Service plans. There are no explicit Linux/macOS examples or references to Linux-specific deployment scenarios.
Recommendations
- Clarify which Kudu features are available for Linux-based App Service plans (e.g., process management, diagnostic dumps, site extensions).
- Add examples or notes for Linux users, such as how to access logs, manage processes, or deploy using Kudu on Linux.
- Explicitly state any feature limitations or differences between Windows and Linux App Service environments.
- Include links to Linux-specific Kudu documentation or community resources if available.
App Service
Fix HTTP 502 and HTTP 503 Errors
...articles/app-service/troubleshoot-http-502-http-503.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references PowerShell as the primary CLI for managing Azure resources and highlights Windows-centric tools such as ProcDump and DOS commands in the Kudu debug console. There are no explicit Linux or macOS command-line examples, nor are Linux troubleshooting tools or shell commands mentioned. The guidance for collecting data and debugging is oriented toward Windows users, with no parity for Linux/macOS users.
Recommendations
- Include Azure CLI examples alongside PowerShell for managing and restarting apps, as Azure CLI is cross-platform.
- Mention Linux/macOS equivalents for memory dump collection (e.g., using gcore, lsof, or other native tools) and provide instructions for these platforms.
- Clarify that the Kudu debug console supports both PowerShell and Bash, and provide Bash command examples.
- Reference cross-platform diagnostic tools and workflows where possible.
- Add explicit notes or sections for Linux/macOS users to ensure parity in troubleshooting steps.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for programmatic management of access restrictions, but PowerShell examples are given equal or greater prominence, including in advanced scenarios. PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) may create friction for Linux/macOS users. In some advanced sections (e.g., multi-source rules, restricting access to Azure Front Door), only PowerShell examples are shown, with no corresponding Azure CLI or REST API example. However, the main programmatic sections do include Azure CLI, ARM, and Bicep options, which are platform-neutral.
Recommendations
- Ensure every PowerShell example is paired with an Azure CLI example, especially in advanced scenarios (e.g., multi-source rules, Azure Front Door restrictions).
- Consider providing REST API or SDK examples for maximum cross-platform parity.
- When presenting code examples, show Azure CLI first, as it is cross-platform, or alternate the order to avoid implicit Windows-first bias.
- Explicitly state that Azure CLI is available on Windows, Linux, and macOS, and link to installation instructions for non-Windows platforms.
- Review screenshots and UI instructions to ensure they do not reference Windows-only features or terminology.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell-based command-line examples and referencing the Az PowerShell module for all CLI operations. No Azure CLI (bash/sh) or Linux/macOS-specific instructions are given, and PowerShell is presented as the only automation option. This creates friction for Linux/macOS users who typically use Azure CLI or bash scripts.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, including listing, restoring, and managing deleted apps.
- Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
- Reorder sections so that cross-platform methods (Azure portal, Azure CLI) are presented before Windows-specific tools like PowerShell.
- Include notes clarifying that PowerShell Core is available on Linux/macOS, but recommend Azure CLI for native shell users.
App Service
Hybrid Connections in Azure App Service
...articles/app-service/app-service-hybrid-connections.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Windows and Linux instructions for installing and managing the Hybrid Connection Manager, but there is a clear Windows-first bias. Windows instructions and tools (such as the GUI and PowerShell commands) are described first and in greater detail, with Linux often relegated to CLI-only instructions. Some troubleshooting steps and examples (e.g., using PowerShell's Test-NetConnection) are Windows-specific, and GUI management is only available on Windows. The legacy Hybrid Connection Manager is only available for Windows. While Linux is supported, the experience is less feature-rich and sometimes less clearly documented.
Recommendations
- Present Windows and Linux instructions in parallel or with equal prominence, rather than always listing Windows first.
- Provide Linux-native troubleshooting commands (e.g., using nc, curl, or telnet) alongside PowerShell examples.
- Expand Linux CLI documentation with more detailed examples, screenshots, and step-by-step guidance similar to the Windows GUI sections.
- Clarify feature parity and limitations for Linux users up front, and provide workarounds or alternatives where GUI features are missing.
- Where possible, offer cross-platform tools or scripts, or reference third-party GUI options for Linux.
- Ensure all critical management and troubleshooting tasks can be performed on Linux and are documented.
App Service
Use Key Vault References as App Settings
...ticles/app-service/app-service-key-vault-references.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key configuration steps, but consistently includes PowerShell commands alongside CLI commands. PowerShell is a Windows-centric tool, and its presence may signal a Windows-first approach. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell examples are given equal prominence to CLI, which is cross-platform but still less familiar to many Linux users. No Linux-specific tools, patterns, or troubleshooting steps are mentioned.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add explicit Bash shell examples for steps involving environment variables and command substitution.
- Note that PowerShell examples are primarily for Windows users, and provide equivalent Bash commands where possible.
- Include troubleshooting steps or notes relevant to Linux/macOS environments, especially regarding networking and managed identity propagation.
- Review the order of examples, listing CLI/Bash first, then PowerShell, to reduce perceived Windows-first bias.
App Service
Disable Basic Authentication for Deployment
...n/articles/app-service/configure-basic-auth-disable.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools and deployment methods (such as Web Deploy and Visual Studio) are referenced throughout, often without explicit mention of Linux/macOS alternatives or parity. Windows tools (Web Deploy, Visual Studio) are described as primary deployment methods, and troubleshooting sections reference Windows agents and requirements. While Azure CLI examples are provided (which are cross-platform), there is little explicit guidance for Linux/macOS users regarding alternative tools, troubleshooting, or platform-specific caveats.
Recommendations
- Add explicit notes or sections for Linux/macOS users, including troubleshooting steps for common deployment scenarios.
- Reference cross-platform deployment tools (such as Kudu, zip deploy, or SCP/SFTP for FTP alternatives) where appropriate.
- When mentioning Visual Studio or Web Deploy, provide parity examples for VS Code, JetBrains IDEs, or CLI-based workflows.
- Clarify agent requirements and behaviors for both Windows and Linux in Azure Pipelines, including links to relevant documentation.
- Ensure that examples and screenshots are balanced between Windows and Linux/macOS environments.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by focusing on Windows-specific deployment patterns, tools, and examples. It references Visual Studio and Windows file paths, and provides instructions for accessing .NET Framework versions using Windows tools (Kudu, CMD, PowerShell) without mentioning Linux equivalents or providing Linux-specific examples. There is no guidance for Linux-based App Service environments, and the documentation assumes the use of Windows containers and infrastructure.
Recommendations
- Add explicit instructions and examples for configuring ASP.NET apps on Linux-based App Service environments.
- Include Linux shell commands (e.g., bash) for listing installed .NET runtimes in Linux containers.
- Clarify which steps apply to Windows App Service plans and which to Linux, and provide parity for both.
- Mention deployment tools and workflows commonly used on Linux (e.g., VS Code, CLI, GitHub Actions) alongside Visual Studio.
- Provide guidance for accessing diagnostic logs and environment variables in Linux containers.
App Service
Customize Sign-ins and Sign-outs
...vice/configure-authentication-customize-sign-in-out.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation generally presents platform-neutral guidance, but shows notable Windows bias in the 'Server level (Windows apps only)' section. It exclusively describes IIS and web.config-based authorization for Windows apps, with no equivalent Linux guidance. Windows-specific tools (Kudu, web.config) are mentioned, and Linux users are told these options are unavailable, but no Linux alternatives or patterns are provided. Elsewhere, examples and CLI commands are platform-neutral.
Recommendations
- Add equivalent Linux guidance for server-level authorization, such as how to configure access controls for Linux-based App Service (e.g., using .htaccess for Apache, nginx config, or application-level middleware).
- Explicitly state recommended patterns for Linux apps where Windows/IIS features are unavailable.
- Where Windows-specific tools are mentioned (Kudu, web.config), provide Linux alternatives or clarify how Linux users should approach the same tasks.
- Consider reordering or labeling sections to avoid presenting Windows-only solutions as the default or primary approach.
App Service
Configure Sign in with Apple (Preview)
...app-service/configure-authentication-provider-apple.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
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 does not offer equivalent examples for Linux/macOS users (e.g., using Python, OpenSSL, or Node.js). No mention is made of Linux tools or cross-platform alternatives, and the example is presented as the primary method.
Recommendations
- Add code examples for generating the JWT client secret using cross-platform languages/tools such as Python (PyJWT), Node.js (jsonwebtoken), or OpenSSL command-line.
- Explicitly mention that the JWT can be generated on any platform and provide links or references to Linux/macOS-friendly libraries and tools.
- Reorder or supplement the documentation so that Windows-specific examples are not presented as the only or primary method.
- Include a brief section listing popular cross-platform JWT libraries and their usage.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides parity for Azure CLI and PowerShell, but several critical features (default documents, virtual directory mapping, handler mappings) are explicitly Windows-only, with no Linux equivalents or workarounds. PowerShell examples are extensive and detailed, while Linux-specific notes and examples are minimal. Windows terminology and tooling (IIS, D:\home paths, applicationHost.config) are referenced without Linux alternatives. Some sections (e.g., bulk editing) clarify PowerShell limitations, but overall, Linux users may find gaps for advanced configuration.
Recommendations
- Explicitly state Windows-only limitations at the start of affected sections.
- Provide Linux-specific guidance or workarounds for features like default documents, virtual directory mapping, and handler mappings, or clarify if not supported.
- Add more Linux-focused examples, especially for advanced scenarios.
- Balance PowerShell and CLI coverage, and highlight cross-platform tools where possible.
- Reference Linux file paths and configuration patterns when discussing directory mapping and handler mappings.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page presents several signs of Windows bias. Windows-specific instructions, examples, and references (such as PowerShell commands, Windows base images, and Windows file paths) are frequently shown first or exclusively, especially in sections not clearly separated by OS pivots. PowerShell examples are provided alongside Bash, but sometimes Windows-centric tools and patterns (like C:\home, IIS, .NET Framework, and Windows Server images) are discussed in more detail than their Linux equivalents. Some advanced configuration and diagnostic sections are more detailed for Windows containers, while Linux sections are less comprehensive or refer out to external resources.
Recommendations
- Ensure all examples and instructions are provided for both Windows and Linux, with equal detail and clarity.
- When showing command-line examples, present Bash and PowerShell commands side-by-side, or alternate which is shown first.
- Expand Linux-specific sections to match the depth of Windows sections, especially for advanced configuration, diagnostics, and troubleshooting.
- Avoid referencing Windows tools or patterns (e.g., C:\home, IIS, .NET Framework) without providing Linux equivalents (e.g., /home, Apache/Nginx, .NET Core).
- Where pivots are used, ensure parity in content and examples between Windows and Linux pivots.
- Add more Linux container base image recommendations and troubleshooting guides.
- Review and update links and references to ensure Linux users have direct access to relevant resources.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Windows and Linux instructions for most core tasks, but there is a notable Windows-first bias in several sections. Windows-specific tools (IISNode, web.config) are discussed in detail, while Linux equivalents are less emphasized or omitted. PowerShell is referenced for Application Insights instrumentation, with no Linux CLI alternative. Some troubleshooting and configuration examples are Windows-only, and Windows instructions often precede Linux ones.
Recommendations
- Ensure Linux instructions/examples are presented with equal prominence and detail as Windows ones, ideally side-by-side or with clear pivots.
- For Application Insights instrumentation, provide Azure CLI or Bash instructions for Linux users, not just PowerShell.
- Expand troubleshooting sections to include Linux-specific issues and solutions, similar to the Windows web.config guidance.
- Where Windows tools (IISNode, web.config) are discussed, add or link to Linux container equivalents (e.g., PM2, startup scripts, nginx/apache config if relevant).
- Review all examples to ensure Linux users are not required to infer steps from Windows-centric instructions.
App Service
SSH Access for Linux and Windows Containers
...ticles/app-service/configure-linux-open-ssh-session.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page presents Windows container SSH access first and describes it as requiring no modifications, while Linux containers require additional configuration. Windows instructions focus on browser-based SSH only and do not mention command-line or PowerShell access, whereas Linux containers get detailed Azure CLI and SSH client instructions. There are no PowerShell examples or explicit Windows command-line instructions, but the overall structure and order prioritize Windows information and tools.
Recommendations
- Provide parity in SSH access instructions for Windows containers, including command-line or PowerShell examples if supported.
- Clarify whether command-line SSH access to Windows containers is possible, and if not, explain the limitation explicitly.
- Present Linux and Windows sections in parallel, with equivalent detail and example types for both platforms.
- Add troubleshooting and tool usage examples for Windows users, such as using PuTTY or PowerShell, if applicable.
App Service
Configure Data Sources for Tomcat, JBoss, or Java SE Apps
...es/app-service/configure-language-java-data-sources.md
Medium 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 relies heavily on PowerShell scripts and Windows-specific file paths and tools, while the Linux section uses shell scripts and standard Linux utilities. Windows instructions are more verbose and detailed, with explicit PowerShell examples and references to Windows environment variables and directories. The Linux instructions, while present and functional, are sometimes less detailed and appear after the Windows instructions in some sections. There is a notable reliance on Windows-specific tooling (PowerShell, Windows paths) and the Windows configuration steps are described in greater detail.
Recommendations
- Ensure Linux and Windows instructions are presented with equal detail and clarity.
- Provide Linux shell script equivalents for all PowerShell examples, especially for tasks like XML transformation and file manipulation.
- Where possible, present Linux examples first or side-by-side with Windows examples to avoid implicit prioritization.
- Avoid assuming familiarity with Windows tools; provide cross-platform alternatives or highlight platform-specific steps clearly.
- Expand Linux sections to match the step-by-step detail of Windows instructions, including troubleshooting and edge cases.
App Service
Secure Your Domain with TLS/SSL
...ob/main/articles/app-service/configure-ssl-bindings.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides automation examples only for Azure CLI and PowerShell, with the PowerShell example shown in code and highlighted, while the Azure CLI is referenced only via a link. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is traditionally associated with Windows. The documentation does not mention Linux-specific tools or workflows, and the automation section prioritizes PowerShell, which may create friction for Linux/macOS users.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users in the automation section.
- Show Azure CLI code snippets directly in the documentation, not just as a link.
- Ensure that instructions and screenshots do not assume Windows-only environments.
- Include notes or sections on Linux-specific certificate handling (e.g., .pfx conversion, OpenSSL usage).
- Balance the order of examples so that CLI and Bash appear before or alongside PowerShell.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (IIS, Certreq.exe, PowerShell) are mentioned for certificate export and automation, with PowerShell examples provided alongside Azure CLI. Windows scenarios (such as using IIS/Certreq.exe) are described in detail, while Linux/macOS equivalents (such as using OpenSSL) are present but less emphasized. In automation and FAQ sections, Windows container support is highlighted before Linux, and PowerShell scripts are referenced without Linux shell equivalents. Some steps and links point to Windows-only documentation.
Recommendations
- Provide explicit Linux/macOS examples for certificate export and management, such as using OpenSSL and native shell commands.
- Include bash/shell script automation examples alongside PowerShell for tasks like certificate binding.
- Reference Linux/macOS documentation for certificate management, not just Windows (IIS/Certreq.exe).
- Clarify platform support in FAQ answers, and avoid listing Windows scenarios first unless they are more widely supported.
- Ensure parity in screenshots and step-by-step instructions for Linux/macOS users where applicable.
App Service
Authentication Types by Deployment Methods
...in/articles/app-service/deploy-authentication-types.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page lists deployment methods and authentication types for Azure App Service. It gives prominent placement to Windows-centric tools such as Azure PowerShell and Visual Studio, and references PowerShell scripts and migration assistants specifically for Windows. While cross-platform tools like Azure CLI and Visual Studio Code are included, Windows tools are often listed before their Linux equivalents, and PowerShell is highlighted separately. There are no explicit Linux/macOS examples or mentions of Linux-specific deployment patterns.
Recommendations
- Add explicit examples for Linux/macOS users, such as Bash scripts or Linux shell commands for deployment.
- Include references to Linux-native tools (e.g., SSH, SCP, rsync) where applicable.
- Balance the order of presentation so that cross-platform tools (Azure CLI, VS Code) are listed before or alongside Windows-specific tools.
- Provide guidance or links for deploying from Linux/macOS environments, especially for authentication scenarios.
- Clarify which tools are cross-platform and which are Windows-only in the documentation table.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (Visual Studio, WinSCP) are mentioned before cross-platform or Linux-native alternatives. PowerShell examples are provided alongside Azure CLI, but there are no explicit Linux shell (e.g., Bash, sftp, lftp) examples. The troubleshooting and connection instructions reference Windows-oriented clients and documentation (WinSCP), and do not mention Linux FTP/FTPS clients or workflows. Linux/macOS users may need to infer how to adapt instructions for their platforms.
Recommendations
- Include explicit Linux/macOS FTP/FTPS client examples (e.g., lftp, FileZilla, curl, sftp) in deployment steps.
- List cross-platform tools first, or provide parity in tool recommendations (e.g., mention FileZilla before WinSCP/Visual Studio).
- Provide Bash or shell command examples for retrieving endpoints and configuring FTPS, not just Azure CLI and PowerShell.
- Add troubleshooting steps relevant to Linux/macOS environments, such as firewall configuration or client-specific settings.
- Reference documentation for Linux FTP/FTPS clients in passive mode connection instructions.
App Service
Deploy From a Local Git Repository
...ocs/blob/main/articles/app-service/deploy-local-git.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell instructions, but PowerShell examples are detailed and assume use of a local PowerShell terminal, which is most common on Windows. The PowerShell section is given equal prominence to CLI, but CLI instructions are less detailed (e.g., no explicit mention of remote creation). Some troubleshooting examples reference Windows-specific errors (e.g., native modules lacking Windows binaries). The Git Credential Manager dialog is mentioned, which is primarily a Windows tool. There is no explicit mention of Linux/macOS equivalents for credential management or terminal usage, and PowerShell is not natively available on Linux/macOS. The order of examples sometimes puts Windows-centric tools first.
Recommendations
- Add explicit instructions for Linux/macOS users, such as using Bash/zsh terminals and credential management alternatives.
- Clarify that PowerShell commands can be run on Linux/macOS only if PowerShell Core is installed, and provide Bash equivalents where possible.
- Mention platform-specific differences in troubleshooting (e.g., native modules for Linux/macOS).
- Ensure Azure CLI examples are as detailed as PowerShell examples, including remote creation and configuration steps.
- Reference cross-platform credential managers or provide guidance for Linux/macOS authentication flows.
App Service
Configure CI/CD with Azure Pipelines
...ob/main/articles/app-service/deploy-azure-pipelines.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific deployment methods (Web Deploy) are described in detail, with explicit instructions to use Windows agents for these scenarios. Windows agent images are shown first or exclusively in some YAML examples, and troubleshooting focuses on Windows-specific errors. There is limited coverage of Linux/macOS alternatives, especially for deployment methods that are Windows-only, and Linux agent usage is not consistently illustrated in parity with Windows.
Recommendations
- Clearly indicate which deployment methods are Windows-only and provide Linux/macOS alternatives where possible.
- Include Linux/macOS agent examples for all major deployment scenarios, not just for generic cases.
- Present agent selection (windows-latest, ubuntu-latest) side-by-side in code samples, or alternate which is shown first.
- Offer troubleshooting guidance for Linux/macOS agents, not just Windows.
- For Web Deploy, suggest alternative deployment strategies for Linux/macOS users (e.g., ZIP deploy, FTP, or container-based approaches).
- Add explicit notes or tables summarizing which features/tasks require Windows and which are cross-platform.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides parity between Azure Portal, Azure CLI, and Azure PowerShell for all major operations. However, there is a notable Windows bias: PowerShell examples are always included and often shown after CLI, but never mention Linux shell equivalents (e.g., Bash scripts). Troubleshooting and advanced configuration sections reference Windows-specific concepts (Web.config, D:\ paths, IIS applicationInitialization), which are not applicable to Linux-based apps. The documentation also uses Windows file paths and references to Visual Studio, further reinforcing a Windows-centric approach. There is no mention of Linux-specific deployment or troubleshooting patterns, and auto swap is explicitly stated as unsupported for Linux web apps, but no alternative is suggested.
Recommendations
- Add Bash or shell script examples for common operations, especially for Linux users.
- Clarify which features (such as auto swap) are not supported on Linux, and suggest Linux alternatives or workarounds.
- Include troubleshooting steps and log file locations for Linux-based App Service environments.
- Reference Linux configuration files (e.g., appsettings.json, environment variables) where appropriate, in addition to Web.config.
- Avoid using Windows file paths (e.g., D:\home\LogFiles) exclusively; mention Linux equivalents.
- Provide guidance for deploying from Linux tools/editors (e.g., VS Code, Git CLI) alongside Visual Studio.