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 1451-1475 of 2121 flagged pages
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. There is a notable emphasis on Windows-centric tools and patterns: Azure PowerShell and Visual Studio (both Windows-first), and migration tools with PowerShell scripts are highlighted. Visual Studio Code is mentioned, but most developer tool examples (Visual Studio, PowerShell) are Windows-oriented. Linux/macOS equivalents (e.g., Bash, cross-platform CLI usage, JetBrains IDEs) are not referenced, and Windows tools are often listed before cross-platform alternatives.
Recommendations
- Add explicit Linux/macOS instructions and examples for each deployment method, especially for CLI and scripting scenarios.
- Include references to cross-platform IDEs (e.g., JetBrains Rider, Eclipse) and their Azure deployment integrations.
- Provide Bash or shell script examples alongside PowerShell for automation tasks.
- Clarify which tools and methods are cross-platform and which are Windows-only.
- Reorder examples to present cross-platform tools (Azure CLI, VS Code) before Windows-only tools (PowerShell, Visual Studio).
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only Azure PowerShell examples for configuring Traffic Manager and App Service Environments, with no CLI, Bash, or Linux/macOS-specific instructions. The reliance on PowerShell and lack of cross-platform alternatives creates friction for Linux/macOS users.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works natively on Linux/macOS.
- Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used.
- Provide Bash script snippets or guidance for DNS lookups and domain management tasks.
- Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page is generally cross-platform, but the 'Hybrid Connections' section introduces Windows bias by requiring the installation of Hybrid Connection Manager on a Windows Server host, with no mention of Linux or macOS alternatives. There are no command-line or configuration examples, but the only explicit tooling requirement is Windows-based. No PowerShell-heavy or Windows-first ordering is present, and most features are described in a platform-neutral way.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, or provide alternative instructions for non-Windows environments.
- Explicitly mention platform support for all tools and features, especially when a feature is Windows-only.
- If possible, provide Linux/macOS equivalents or workarounds for Hybrid Connections.
- Add a note about platform limitations in the relevant sections.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page presents a notable Windows bias, especially in the 'Managed Instance on Azure App Service' section, which is exclusively for Windows web apps and highlights Windows-specific features (PowerShell, RDP, IIS, .NET Framework). There are no equivalent Linux examples, tools, or parity features discussed, and Windows capabilities are described in detail without mentioning Linux alternatives or limitations in other sections.
Recommendations
- Add a parallel section describing Linux-specific hosting options, features, and limitations in App Service plans.
- Include examples or references for Linux-based configuration, such as Bash scripts, Linux networking, and diagnostic tools.
- Clearly indicate which features are Windows-only and provide links to Linux documentation where applicable.
- Ensure that links to pricing and feature tables include both Windows and Linux details, not just Windows.
- Consider presenting OS options (Windows, Linux) equally in introductory and feature comparison sections.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools, environment variable paths, and configuration patterns are frequently mentioned first or exclusively (e.g., references to D:\home, applicationHost.config, IIS, Web Deploy/MSDeploy, and Windows-only environment variables). Many examples and descriptions use Windows conventions, with Linux equivalents sometimes omitted or mentioned secondarily. Some sections, such as TLS/SSL certificate paths and build automation, focus heavily on Windows (Kudu) before Linux (Oryx), and certain settings are only described for Windows environments.
Recommendations
- Ensure all environment variable examples and descriptions include both Windows and Linux/macOS equivalents, especially for file paths and system variables.
- Present Linux and Windows options side-by-side, or use tabs for platform-specific instructions, rather than listing Windows first or exclusively.
- Add Linux/macOS-specific examples for deployment, build automation, and configuration, including references to Linux tools and conventions.
- Clarify which settings are platform-specific and provide parity where possible, or explicitly state when a feature is Windows-only.
- Avoid referencing Windows-only tools (e.g., MSDeploy, applicationHost.config, IIS) without mentioning Linux alternatives or noting their absence.
App Service
Securely connect .NET apps to Azure SQL Database using Managed Identity
...icles/app-service/tutorial-connect-msi-sql-database.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows/PowerShell tooling is emphasized in critical steps (e.g., granting SQL permissions), and Visual Studio for Windows is described first and in greater detail than cross-platform alternatives. Linux/macOS users are expected to adapt Windows-centric instructions, especially for database permission tasks, with no explicit Linux/macOS SQL tooling guidance provided.
Recommendations
- Provide explicit Linux/macOS alternatives for database permission steps, such as using sqlcmd on Linux or Azure Data Studio.
- Reorder sections to present cross-platform tools (Visual Studio Code, Azure CLI) before or alongside Windows-specific tools.
- Include examples for running sqlcmd on Linux/macOS, and clarify any platform-specific differences.
- Add notes or links to cross-platform database management tools.
- Ensure all CLI and code samples are platform-neutral or have variants for major OSes.
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 OpenSSL, Python, or Node.js). There is no mention of Linux command-line tools or cross-platform libraries, and the only concrete example is tailored for Windows/.NET developers.
Recommendations
- Add examples for generating the JWT client secret using common Linux/macOS tools, such as OpenSSL, Python (PyJWT), or Node.js (jsonwebtoken).
- Mention cross-platform libraries and provide links or sample commands for Linux/macOS environments.
- Clarify that the process is not limited to Windows and .NET, and explicitly state that any platform/language capable of signing JWTs with ES256 can be used.
- Provide step-by-step instructions or scripts for Linux users to generate the JWT from the .p8 file.
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 generally aims for cross-platform parity, providing both Windows and Linux instructions for installing and using Hybrid Connection Manager. However, there is a notable Windows-first bias: Windows instructions, tools, and screenshots are often presented before Linux equivalents. Some troubleshooting and connectivity test examples use PowerShell commands without offering Linux alternatives. The GUI for Hybrid Connection Manager is only available on Windows, with Linux users limited to CLI usage. Some sections (e.g., legacy manager, upgrade process) are Windows-centric or lack Linux-specific details.
Recommendations
- Provide Linux command-line equivalents for all PowerShell examples (e.g., use 'nc', 'telnet', or 'curl' for connectivity tests).
- When listing instructions or examples, alternate the order or present both Windows and Linux commands side by side to avoid Windows-first bias.
- Clarify in all relevant sections when features (like the GUI) are Windows-only, and offer enhanced CLI guidance or scripts for Linux users.
- Include more Linux-specific troubleshooting steps and examples, especially for network connectivity and service management.
- Ensure parity in upgrade instructions, such as providing explicit Linux upgrade commands or automation scripts.
- Where possible, provide screenshots or terminal output examples from Linux environments, not just Windows GUIs.
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, only PowerShell examples are shown before CLI, and multi-source rule examples are exclusively PowerShell. No Linux-specific tools or shell examples (e.g., Bash) are provided, and there is no explicit mention of platform compatibility for the CLI or PowerShell commands.
Recommendations
- Ensure that Azure CLI examples are always provided alongside PowerShell, especially for advanced scenarios (e.g., multi-source rules, Front Door integration).
- Where PowerShell is used, clarify that Azure CLI is cross-platform and provide equivalent CLI commands.
- Consider including Bash shell script examples for common tasks to improve Linux parity.
- Explicitly state platform compatibility for each tool (e.g., 'Azure CLI is available on Windows, Linux, and macOS; PowerShell examples require PowerShell Core on Linux/macOS').
- If a feature is only available via PowerShell, note this limitation and suggest alternatives for Linux/macOS users.
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 instructions. There are no equivalent examples for Linux/macOS users (such as Azure CLI or Bash), and PowerShell is referenced as the sole automation tool. This creates friction for users on non-Windows platforms, as they must either install PowerShell Core or translate commands themselves. The portal instructions are platform-neutral, but all scripting and automation guidance is Windows-centric.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that PowerShell Core is available on Linux/macOS, but provide CLI/Bash alternatives for parity.
- Reorder sections so that platform-neutral or cross-platform solutions (like Azure CLI) are presented before or alongside PowerShell.
- Include notes or links to documentation for Linux/macOS users on how to install and use PowerShell Core if needed.
App Service
App Service Managed Certificate (ASMC) Changes – July 28, 2025
...e/app-service-managed-certificate-changes-july-2025.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias in its guidance for identifying impacted Traffic Manager endpoints. The only script-based example for resource identification is a PowerShell script, with no equivalent Bash, Azure CLI, or cross-platform alternative provided. Instructions for running the script assume PowerShell usage, which is native to Windows and less common on Linux/macOS. The rest of the documentation uses platform-neutral tools (Azure Resource Graph, REST API, Azure CLI), but the initial troubleshooting workflow is Windows-centric.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for identifying impacted Traffic Manager endpoints, ensuring Linux/macOS users have a native option.
- Explicitly mention that PowerShell Core is available cross-platform, and provide installation instructions for Linux/macOS if PowerShell must be used.
- When listing script-based solutions, present Azure CLI or Bash examples before or alongside PowerShell to avoid Windows-first bias.
- Include notes or links to platform-agnostic alternatives wherever Windows-specific tooling is referenced.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Several features and configuration options are described as available only for Windows apps (default documents, virtual directory mapping, handler mappings). Examples for these features use Windows-centric paths and tools (IIS, PowerShell, Windows file paths). In sections where features are Windows-only, there is little or no mention of Linux alternatives or explicit guidance for Linux users. In general sections, Windows-specific terminology and examples (such as PowerShell) are presented alongside cross-platform CLI, but Windows-only features are described first and in more detail.
Recommendations
- Clearly indicate Windows-only features at the start of each relevant section, and provide links or notes about Linux equivalents or workarounds where possible.
- For features not available on Linux (e.g., default documents, handler mappings), add a brief explanation of how Linux apps handle these scenarios, or clarify that these settings are not applicable.
- Where possible, provide Linux-specific examples or highlight differences in configuration between Windows and Linux (e.g., file paths, environment variable handling).
- Consider reordering sections so that cross-platform or Linux-first options are presented before Windows-only features.
- Add explicit guidance for Linux users in sections that currently only mention Windows tools or patterns.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Windows-specific instructions, examples, and tooling (PowerShell, Windows Server images, IIS, .NET Framework) are often presented first or in greater detail. PowerShell commands are provided alongside Bash, but Windows-centric concepts (e.g., C:\home, IIS, machine keys, registry settings) are explained more thoroughly. Some advanced configuration sections (memory, CPU, health ping) are detailed only for Windows containers, with no Linux equivalents. Linux sections are present and reasonably detailed, but parity is inconsistent, and some features (e.g., multi-container, persistent storage) are described with Windows-first terminology or examples.
Recommendations
- Ensure that all configuration examples (e.g., memory limits, CPU core limits, health ping behavior) are provided for both Windows and Linux containers, or explicitly state platform limitations.
- Present Linux and Windows examples side-by-side or in parallel sections, rather than Windows-first.
- Expand Linux-specific guidance for advanced scenarios (e.g., persistent storage, diagnostic logs, environment variable injection) to match the depth of Windows sections.
- Avoid Windows-centric terminology (e.g., C:\home) in Linux sections; use platform-appropriate paths and clarify differences.
- Where PowerShell is shown, ensure equivalent Bash or shell examples are always present and shown first or equally.
- Highlight platform-specific limitations and features clearly, so Linux/macOS users know what is and isn't supported.
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 tools (e.g., startup.cmd, %HOME%, %LOCAL_EXPANDED%), while Linux instructions use standard shell scripting and package managers. Windows examples are often more verbose and detailed, with explicit PowerShell code, whereas Linux instructions are more concise and use generic shell commands. In some sections, Windows instructions (especially PowerShell) are presented before Linux equivalents, and there is more focus on Windows-specific patterns and tooling.
Recommendations
- Provide equivalent Bash shell scripts for Linux wherever PowerShell scripts are shown for Windows.
- Ensure that Linux instructions are as detailed and explicit as Windows instructions, including step-by-step guides and troubleshooting tips.
- Where possible, present Linux and Windows instructions side-by-side, or in parallel tabs, to avoid implicit prioritization.
- Avoid using Windows-specific terminology (e.g., %HOME%, startup.cmd) without Linux equivalents or explanations.
- Include more Linux/macOS-specific examples for configuration, especially for advanced scenarios.
- Add explicit notes on how to adapt Windows-centric steps (e.g., PowerShell scripts) for Linux environments.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. It assumes the use of Windows-based App Service instances and tools, especially in sections about runtime inspection and deployment. Examples and instructions for listing .NET Framework versions rely on Windows file paths and Kudu's CMD/PowerShell consoles, with no Linux equivalents provided. The Visual Studio publishing workflow is emphasized, and Linux-specific deployment or configuration patterns are not addressed.
Recommendations
- Include equivalent instructions and examples for Linux-based App Service instances, such as how to inspect installed .NET runtimes in Linux containers.
- Mention and demonstrate Linux-friendly tools (e.g., Bash, Linux file paths) alongside Windows tools like CMD/PowerShell.
- Clarify when instructions are Windows-specific and provide links or references to Linux guidance where appropriate.
- Highlight cross-platform deployment options (e.g., Azure CLI, GitHub Actions) and show parity in examples.
- Add notes or sections for common Linux/macOS developer workflows, especially for those not using Visual Studio.
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 most core tasks, but Windows examples and tooling (IISNode, web.config, PowerShell) are often mentioned first or exclusively. Some sections, such as Application Insights instrumentation, reference PowerShell for setup without a Linux CLI or Bash equivalent. Troubleshooting and error messages focus on Windows-specific files (web.config), while Linux equivalents are referenced only via includes. The overall structure and order tend to prioritize Windows scenarios, with Linux-specific guidance sometimes relegated to later sections or pivots.
Recommendations
- Ensure Linux/Bash equivalents are provided for all PowerShell or Windows-specific instructions, especially for instrumentation and troubleshooting.
- Present Windows and Linux examples in parallel, or alternate which platform appears first in each section to avoid implicit prioritization.
- Expand troubleshooting guidance for Linux, including common errors and configuration files (e.g., nginx.conf, robots.txt) analogous to web.config.
- Where Windows tools (IISNode, web.config) are discussed, provide clear Linux alternatives or explanations.
- Review all included links and references to ensure Linux users have direct access to relevant resources, not just Windows-centric samples.
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 SSH access for both Linux and Windows containers, but there is a notable bias toward Windows in several areas. The Windows section is presented first, and it mentions that no modifications are needed for Windows containers, while Linux containers require additional configuration. The Windows section lacks command-line examples and only references browser-based SSH, whereas the Linux section provides detailed Azure CLI and SSH command examples. There are no PowerShell or Windows command-line examples for Windows containers, and no mention of Windows-native SSH clients or tools.
Recommendations
- Provide parity by including Windows command-line examples (e.g., PowerShell, Windows SSH client) for opening SSH sessions to Windows containers.
- Mention Windows-native SSH tools (such as PuTTY, Windows OpenSSH) and how to use them in the context of App Service containers.
- Present Linux and Windows instructions side-by-side or in a more balanced order, rather than Windows-first.
- Clarify whether SSH access via Azure CLI or other tools is possible for Windows containers, and if not, explain the limitations.
- Add troubleshooting and configuration guidance for Windows containers similar to what is provided for Linux.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows-specific instructions, examples, and code samples are presented first and in greater detail, especially for certificate access via the Windows certificate store. Linux equivalents are either presented later, are less detailed, or are deferred to external documentation. Non-Windows languages (Node.js, PHP, Python, Java) are not given direct Linux examples, and the use of Windows tools and patterns (certificate store, environment variables, file paths) is emphasized throughout.
Recommendations
- Provide Linux-specific code samples for popular languages (Node.js, PHP, Python, Java) directly in the documentation, not just C#.
- Present Windows and Linux instructions/examples in parallel or in clearly separated sections, rather than Windows-first.
- Include more detailed guidance for Linux users, such as how to access certificates from file paths in various languages.
- Reference Linux tools and patterns (e.g., OpenSSL, Linux environment variables) where appropriate.
- Ensure parity in troubleshooting and advanced scenarios for both platforms.
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 instructions for enabling virtual network integration. However, the PowerShell section is significantly more detailed, with step-by-step parameter preparation, delegation checks, and resource updates, while the CLI section is limited to a single command. PowerShell is primarily a Windows-centric tool, and its prominence and detail suggest a Windows-first bias. There are no Linux/macOS-specific instructions or troubleshooting notes, and the CLI example is not as comprehensive as the PowerShell walkthrough.
Recommendations
- Expand the Azure CLI section to include detailed, step-by-step instructions equivalent to the PowerShell section, covering subnet delegation checks and resource updates.
- Add troubleshooting notes or tips for Linux/macOS users, such as handling permissions or context switching in CLI.
- Consider including Bash or shell script examples for common Linux workflows.
- Ensure parity in detail and guidance between CLI and PowerShell sections, so Linux/macOS users are not disadvantaged.
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 First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for RBAC assignment, but PowerShell is mentioned separately and with its own tab, which may suggest a slight Windows bias. In the certificate export section, Windows tools (IIS, Certreq.exe) are mentioned as alternatives to OpenSSL, but Linux/macOS equivalents (such as certutil or keytool) are not referenced. The FAQ and automation sections reference PowerShell scripts alongside CLI, but do not mention Bash or Linux-native scripting. Windows-specific scenarios (e.g., outbound calls using private CA client certificates) are called out, while Linux container scenarios are not discussed. Overall, Linux users can complete all tasks, but Windows tools and patterns are more visible and sometimes referenced first.
Recommendations
- Add Linux/macOS-native examples for certificate export (e.g., using OpenSSL on Bash, or mentioning keytool for Java apps).
- Include Bash script examples for automation alongside PowerShell and Azure CLI.
- When referencing Windows tools (IIS, Certreq.exe), also mention Linux/macOS alternatives or clarify that OpenSSL is cross-platform.
- Ensure that container scenarios for Linux are discussed where relevant, especially in FAQ sections.
- Present Azure CLI examples before PowerShell, or group them together to avoid Windows-first impression.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure portal, but does not include explicit Linux/macOS shell examples or mention platform-specific differences. PowerShell is referenced as a primary automation tool, and examples are often shown for PowerShell even when it cannot perform certain tasks. There is no mention of Linux-specific tools or workflows, and the order of examples often places PowerShell before CLI, which may suggest a Windows-first approach.
Recommendations
- Add explicit Linux/macOS shell examples for relevant commands, especially for credential management and Git usage.
- Clarify that Azure CLI is cross-platform and provide Bash-specific usage notes, such as escaping characters in shell environments.
- Reorder examples to present Azure CLI (cross-platform) before PowerShell, or group by platform.
- Mention platform-specific considerations, such as differences in credential storage or command-line usage on Linux/macOS.
- Include troubleshooting tips for Linux/macOS users, especially around Git authentication and shell escaping.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell for all major operations. However, there is a notable bias toward Windows and PowerShell: PowerShell examples are given equal prominence to CLI, and several advanced configuration and troubleshooting sections reference Windows-specific tools and patterns (e.g., Web.config, applicationInitialization, D:\home\LogFiles). There are no explicit Linux/macOS shell examples, and some features (like auto swap) are called out as unsupported on Linux, but without Linux alternatives or workarounds. The troubleshooting section references Windows file paths and IIS concepts, which are not applicable to Linux environments.
Recommendations
- Add explicit Linux/macOS shell examples (e.g., Bash, zsh) for CLI commands, including environment-specific notes where needed.
- Clarify which features are unavailable on Linux and suggest alternative workflows or mitigations for Linux users.
- Where troubleshooting references Windows paths or IIS/Web.config, provide Linux equivalents or clarify that these steps are Windows-only.
- Consider reordering examples so that cross-platform CLI commands are shown before PowerShell, or mark PowerShell as Windows-specific.
- Add notes or links to Linux-specific documentation for deployment, configuration, and troubleshooting.
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 page exhibits a moderate Windows bias. Windows-specific deployment methods (Web Deploy, IIS, web.config, iisnode) are described in detail, with explicit instructions and error messages for Windows agents. Linux deployment is mentioned, but Windows examples and agent specifications (e.g., 'windows-latest') are often shown first or exclusively for certain scenarios. There is a lack of parity in examples for Linux/macOS, especially for advanced deployment methods like Web Deploy, which are Windows-only. Some sections (e.g., troubleshooting, FAQs) focus on Windows agent issues without Linux equivalents.
Recommendations
- Provide equivalent Linux/macOS examples for all deployment scenarios, especially for advanced tasks.
- Clearly indicate when a feature is Windows-only and suggest Linux/macOS alternatives (e.g., ZIP deploy, FTP, or container-based deployment).
- Balance agent specification examples (show 'ubuntu-latest' and 'windows-latest' side by side where possible).
- Include troubleshooting and FAQ sections for Linux/macOS agents.
- Avoid referencing Windows tools (IIS, web.config, iisnode) without mentioning Linux alternatives or clarifying their platform specificity.
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 first or exclusively as FTP clients, and PowerShell is given equal prominence to Azure CLI for command-line operations. There are no explicit Linux/macOS shell examples (e.g., using lftp, curl, or FileZilla), nor are Linux-specific troubleshooting steps or tool recommendations provided. This may create friction for Linux/macOS users who are unfamiliar with Windows tools or PowerShell.
Recommendations
- Add Linux/macOS shell examples for command-line operations (e.g., using curl, lftp, or standard FTP clients).
- Mention cross-platform FTP clients such as FileZilla and provide usage instructions.
- List Linux/macOS tools before or alongside Windows tools to avoid Windows-first bias.
- Include troubleshooting steps relevant to Linux/macOS environments (e.g., firewall configuration, permissions).
- Provide sample commands for connecting via FTP/S from Linux/macOS terminals.
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 primarily a Windows tool. The troubleshooting section references Windows-specific errors (e.g., native modules lacking Windows binaries), and the PowerShell workflow is described before the portal workflow. There are no explicit Linux/macOS shell examples for PowerShell steps, and no mention of Linux-specific issues or parity for PowerShell commands on non-Windows platforms.
Recommendations
- Add explicit Bash/zsh shell examples for all steps, especially those currently shown only in PowerShell.
- Clarify that Azure PowerShell can be used cross-platform and provide instructions for installing/running it on Linux/macOS.
- Include troubleshooting notes for Linux/macOS-specific deployment errors (e.g., native modules lacking Linux binaries).
- Ensure that CLI (Bash) examples are shown first or equally with PowerShell, and that all workflows are covered for both platforms.
- Mention alternative tools (e.g., Bash, zsh, fish) where PowerShell is referenced, and provide equivalent commands.