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 1101-1125 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate.md
...main/articles/app-service/configure-ssl-certificate.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented alongside Azure CLI for automation, but no explicit Linux shell or bash scripting examples are provided. Windows tools (IIS, Certreq.exe) are mentioned for certificate export, but Linux equivalents are not. In the FAQ, certain features are noted as 'Windows container apps only' without clarifying Linux support or alternatives. While OpenSSL is mentioned (which is cross-platform), the overall pattern is to mention Windows tools and patterns first, with limited Linux-specific guidance.
Recommendations
- When mentioning certificate export using IIS or Certreq.exe, also provide equivalent Linux commands (e.g., using OpenSSL or certutil) for users who generated CSRs on Linux.
- In automation sections, provide bash scripting examples or reference Linux shell usage in addition to Azure CLI and PowerShell.
- In the FAQ, clarify Linux support for features currently described as 'Windows container apps only', and provide alternatives or workarounds for Linux users where possible.
- When listing tools or workflows, avoid listing Windows-specific tools first or exclusively; ensure Linux and cross-platform tools are given equal prominence.
- Consider adding a table or section summarizing certificate management workflows for both Windows and Linux environments.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-inbound-outbound-ips.md
.../articles/app-service/overview-inbound-outbound-ips.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI, but there are no explicit Linux shell or Bash alternatives for PowerShell commands. The outbound IPv6 support section specifically notes that outbound IPv6 is only available for Windows apps, with Linux apps limited to IPv4. In command examples, PowerShell is presented as an alternative to Azure CLI, but not vice versa, and there is no mention of Linux-specific tools or workflows. The documentation does not provide parity in examples or explanations for Linux users, especially in areas where Windows-specific features or limitations are discussed first or exclusively.
Recommendations
- For every PowerShell example, provide an equivalent Bash or Linux shell example, or clarify when one is not applicable.
- Explicitly mention when a feature is Windows-only and, where possible, provide Linux alternatives or workarounds.
- In sections discussing command-line access, clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- When listing command examples, alternate the order (e.g., show Azure CLI before PowerShell, or group by platform).
- Add notes or links for Linux users where features are not available, and suggest best practices or alternatives.
- Include Linux-specific troubleshooting or testing steps (e.g., using dig instead of nslookup, or curl commands for both platforms).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by prioritizing Windows terminology and tools. Windows and PowerShell are mentioned or exemplified before Linux equivalents, and PowerShell scripting is given equal prominence to Azure CLI without Linux shell examples. There is no explicit Linux shell (bash) scripting example, and the automation section does not clarify cross-platform usage. The portal instructions and screenshots are Windows-centric, and Linux-specific guidance is minimal or secondary.
Recommendations
- Provide explicit bash/Linux shell scripting examples alongside Azure CLI and PowerShell, clarifying cross-platform compatibility.
- When listing commands or tools, present Linux and Windows options together or alternate their order to avoid Windows-first bias.
- Include screenshots or instructions for the Azure portal as accessed from Linux/macOS browsers, or clarify that the portal is platform-agnostic.
- Expand the automation section to show how to use scripting on Linux (e.g., bash scripts), not just PowerShell.
- Where PowerShell is mentioned, clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Add a note or section highlighting any differences or considerations for Linux users, especially regarding deployment and automation.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate.md
...main/articles/app-service/configure-ssl-certificate.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it is generally cross-platform in its language, it provides explicit instructions and links for Windows tools (IIS, Certreq.exe) and PowerShell, and references to Windows-specific certificate management. Linux equivalents (such as certutil, keytool, or OpenSSL on Linux) are not mentioned when Windows tools are. In automation and scripting sections, PowerShell is given equal or greater prominence than Azure CLI, and no bash or Linux-native scripting examples are provided. This could make the documentation less accessible or clear for Linux users.
Recommendations
- When referencing certificate export or management tools, provide Linux equivalents (e.g., mention how to export a certificate using OpenSSL or keytool on Linux, not just IIS or Certreq.exe).
- In automation sections, always provide Azure CLI/bash examples before or alongside PowerShell, and clarify which examples are cross-platform.
- Explicitly state when a tool or process is Windows-only, and offer alternative instructions for Linux/macOS users.
- Add a section or callout for Linux users on how to generate, merge, and export certificates using common Linux tools.
- Review FAQ and troubleshooting sections for OS-specific limitations, and clarify when features are Windows-only or have different behaviors on Linux.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by prioritizing Windows terminology, tools, and examples. Azure PowerShell (a Windows-centric tool) is given a dedicated section, while Linux-specific automation (e.g., Bash scripting) is not mentioned. The Azure CLI examples are platform-neutral, but there are no explicit Linux shell or container deployment examples. The documentation refers to the Azure portal UI, which is the same across platforms, but does not provide parity for Linux-native workflows or tools.
Recommendations
- Add explicit Linux shell (Bash) script examples for automating Premium V4 app creation and scaling, in addition to Azure CLI.
- Include examples or references for deploying custom Linux containers, since Premium V4 supports them on Linux.
- Balance the automation section by providing both Azure PowerShell and Bash/CLI script examples, or clarify that Azure CLI commands work cross-platform.
- Mention Linux-native tools or workflows (such as using SSH, SCP, or Docker) where relevant, especially for custom container scenarios.
- Ensure that any references to Windows-specific features or limitations are matched with Linux equivalents or clarifications.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows-specific information and tools first, providing PowerShell automation examples without equivalent Bash/Linux shell scripts, and referencing Windows patterns and terminology more prominently. Linux-specific instructions and parity in scripting examples are lacking, and the documentation sometimes assumes a Windows-centric workflow.
Recommendations
- Provide Linux shell (Bash) script examples alongside PowerShell for automation tasks, especially in the 'Automate with scripts' section.
- Ensure that Linux-specific instructions are given equal prominence and detail as Windows instructions, especially in sections about availability and deployment.
- When referencing tools or workflows (e.g., Azure PowerShell), also mention and provide examples for their Linux/CLI equivalents.
- Avoid presenting Windows information or tools before Linux equivalents unless there is a technical reason; consider grouping instructions by platform or providing parallel examples.
- Clarify any differences in feature support or behavior between Windows and Linux explicitly, and ensure both are covered in troubleshooting and error-handling sections.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/overview-certificates.md
...icles/app-service/environment/overview-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. It provides only PowerShell commands for certificate management and testing, references Windows-specific certificate stores (Cert:\LocalMachine\Root), and explicitly states that private client certificates are only supported from custom code in Windows code apps. There are no Linux or cross-platform examples, and Linux scenarios are not addressed.
Recommendations
- Provide equivalent Linux/Bash examples for certificate creation (e.g., using openssl) and certificate management.
- Clarify support for Linux-based App Service apps, including any limitations or alternative approaches.
- Include instructions for accessing and managing certificates on Linux-based workers (e.g., using Kudu Bash console, Linux file paths).
- Mention Linux tools (such as openssl) alongside PowerShell, and avoid presenting Windows tools first or exclusively.
- Explicitly state platform limitations at the beginning of relevant sections, and offer guidance or workarounds for Linux users where possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/getting-started.md
...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 demonstrates some Windows bias, particularly in the .NET and Python sections. For .NET, Windows tools like Visual Studio and Azure PowerShell are listed before cross-platform or Linux-native options. In the Python section, most quickstart links default to 'windows' tabs, and Linux-specific instructions are not highlighted or are less visible. Azure PowerShell, a Windows-centric tool, is promoted alongside or before CLI options. Linux-specific tools and workflows are less emphasized or missing in some stacks (e.g., .NET).
Recommendations
- In .NET sections, list cross-platform tools (e.g., Visual Studio Code, CLI) before Windows-only tools (e.g., Visual Studio, Azure PowerShell).
- Ensure that Linux and cross-platform CLI examples are present and prominent for all stacks, especially .NET and Python.
- For Python, provide explicit Linux/macOS quickstart tabs and links, not just 'windows' defaults.
- Where Azure PowerShell is mentioned, also mention Azure CLI as an equal or preferred cross-platform alternative.
- Add or highlight Linux-native workflows and tools (e.g., Bash, Linux package managers) where appropriate.
- Review all quickstart and tutorial links to ensure Linux parity and visibility, not just as an afterthought or in a secondary position.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-customize-sign-in-out.md
...vice/configure-authentication-customize-sign-in-out.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in the 'Server level (Windows apps only)' section, where it provides detailed instructions for configuring authorization using IIS and web.config, which are exclusive to Windows. There is no equivalent example or guidance for Linux-based App Service apps. Additionally, the section is presented before any mention of Linux alternatives, and no Linux-native tools or configuration patterns are discussed.
Recommendations
- Add a parallel section for Linux-based App Service apps, providing equivalent guidance for configuring authorization (e.g., using middleware in common frameworks like Node.js, Python, or .NET Core).
- Explicitly state that Linux apps require different approaches and link to relevant documentation or examples for Linux environments.
- Where possible, present Windows and Linux options side-by-side to avoid the perception of Windows as the default or preferred platform.
- Include sample code or configuration for popular Linux web servers (e.g., Nginx, Apache) or application-level authorization patterns.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-ip-restrictions.md
...in/articles/app-service/app-service-ip-restrictions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured heavily in code examples, often before or alongside Azure CLI, and is the only scripting language shown for advanced scenarios (e.g., multi-source rules, Azure Front Door filtering). There are no Linux shell (bash) or cross-platform scripting examples outside of Azure CLI, and the PowerShell examples are not explicitly marked as cross-platform (i.e., using PowerShell Core). While the Azure CLI is included, the advanced and inline scripting guidance favors PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Provide bash (Linux shell) script examples for all scenarios where PowerShell is shown, especially for advanced use cases like multi-source rules and HTTP header filtering.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Where PowerShell is used, specify if the commands are compatible with PowerShell Core (cross-platform) or only Windows PowerShell.
- In advanced scenarios, ensure that Azure CLI and bash examples are given equal prominence to PowerShell.
- Consider including a note or table summarizing which management tools are available on which platforms.
- Avoid presenting PowerShell examples before Azure CLI or bash unless there is a technical reason to do so.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-local-git.md
...ocs/blob/main/articles/app-service/deploy-local-git.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) instructions, but the PowerShell section is more detailed and assumes use of a local PowerShell terminal. There are references to Windows-specific issues (e.g., native modules lacking Windows binaries) and tools (PowerShell, Git Credential Manager dialog). There is no explicit mention or example of using Linux-specific shells or tools, and the troubleshooting section references Windows-specific errors without Linux equivalents.
Recommendations
- Add explicit Linux/macOS terminal examples alongside PowerShell, especially for steps like changing directories and running commands.
- Clarify that Azure CLI commands can be run in Bash, Zsh, or other Unix shells, and provide sample commands in those contexts.
- Include troubleshooting notes for common Linux/macOS issues (e.g., SSH key permissions, credential manager differences).
- Avoid assuming the presence of the Git Credential Manager dialog, which is Windows-specific; mention alternatives for Linux/macOS.
- Balance error message examples to include those commonly encountered on Linux/macOS.
- Where PowerShell is mentioned, also mention Bash or other common Linux shells as alternatives.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-github-actions/deploy-github-actions-publish-profile.md
...ithub-actions/deploy-github-actions-publish-profile.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides cross-platform deployment examples for most stacks, but the ASP.NET (classic) section exclusively uses a Windows runner and Windows-specific tools (NuGet, MSBuild) without offering Linux alternatives or parity. All other stacks (ASP.NET Core, Java, Tomcat, Node.js, Python) use Ubuntu runners and standard, cross-platform tooling. The ASP.NET section is both Windows-first and Windows-only, lacking Linux-based workflow examples.
Recommendations
- Add a Linux-based (ubuntu-latest) workflow example for ASP.NET (classic), using Mono and cross-platform equivalents of NuGet and MSBuild where possible.
- Explicitly state in the ASP.NET section why a Windows runner is required (if so), or provide guidance for Linux users.
- Reorder or clearly label sections to avoid implying Windows is the default or only supported environment for .NET workloads.
- Where Windows-specific tools are used, mention if cross-platform alternatives exist or provide links to relevant documentation.
- Ensure parity in example depth and clarity between Windows and Linux workflows for all stacks.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-dotnet-sqldatabase.md
...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 and Visual Studio on Windows. All instructions, screenshots, and tooling references assume the user is on Windows, using Visual Studio, and deploying to Azure App Service (Windows). There are no examples or guidance for Linux users, alternative IDEs, or command-line workflows. PowerShell and Windows-specific tools (e.g., Package Manager Console, SQL Server Object Explorer) are used exclusively, with no mention of cross-platform or Linux alternatives.
Recommendations
- Provide parallel instructions for Linux users, including how to use VS Code or the .NET CLI for project management, publishing, and database migrations.
- Include examples using Azure CLI and Bash for tasks such as database creation, managed identity configuration, and deployment.
- Show how to deploy to Azure App Service (Linux) and highlight any differences or considerations.
- Reference cross-platform tools (e.g., Azure Data Studio, sqlcmd for Linux/macOS) instead of or in addition to Windows-only tools like SQL Server Object Explorer.
- Add notes or sections for Mac users, especially regarding prerequisites and environment setup.
- Ensure screenshots and UI instructions are not exclusively tied to Visual Studio on Windows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-nodejs.md
...main/articles/app-service/configure-language-nodejs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation generally provides parity between Windows and Linux for most configuration tasks, using Azure CLI examples for both. However, there is a subtle Windows bias: Windows instructions and tools (such as IISNode, web.config, and PowerShell references) are often mentioned first or in more detail, and some troubleshooting and monitoring steps reference Windows-specific tools or patterns (e.g., web.config, PowerShell) without always providing equivalent Linux guidance. The Application Insights section references PowerShell for instrumentation but does not mention a Linux/CLI alternative. The troubleshooting section for Windows is more detailed than for Linux.
Recommendations
- Ensure that for every Windows-specific tool or configuration (e.g., web.config, IISNode, PowerShell), an equivalent Linux/container approach is described with equal detail and prominence.
- When listing platform pivots, alternate the order or present Linux first in some sections to avoid the impression of Windows primacy.
- In the Application Insights section, provide explicit CLI or Linux-native instructions for enabling instrumentation, not just PowerShell.
- Expand Linux troubleshooting guidance to match the depth provided for Windows (e.g., what to do if the app doesn't start, common container issues, etc.).
- Where possible, avoid referencing Windows-only tools (like web.config or IISNode) without clear Linux/container alternatives or explanations.
- Audit for any remaining sections where Windows is the default or first-mentioned platform, and balance with Linux-first or cross-platform-neutral language.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/routine-maintenance-downtime.md
...n/articles/app-service/routine-maintenance-downtime.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 providing detailed explanations and tooling references for Windows (such as IIS Application Initialization and .NET Core stdout logging), mentioning Windows-specific features and modules first, and only briefly mentioning Linux equivalents (e.g., WEBSITE_WARMUP_PATH) without comparable detail or examples. There are no Linux command-line or configuration examples, and Linux-specific patterns are not discussed in depth.
Recommendations
- Provide Linux-specific examples and configuration steps alongside Windows examples, especially for features like application initialization and logging.
- Mention Linux and Windows options together, or alternate which platform is presented first in each section.
- Include references to Linux-native tools and patterns (e.g., systemd, NGINX, Apache, or Linux startup scripts) where relevant.
- Expand on the use of WEBSITE_WARMUP_PATH for Linux, including example configurations and best practices.
- Offer parity in troubleshooting/logging guidance for Linux (e.g., stdout/stderr log collection, integration with Linux logging systems).
- Ensure that all features and recommendations are clearly marked as Windows-only, Linux-only, or cross-platform, and provide alternatives where possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/powershell-continuous-deployment-github.md
...ice/scripts/powershell-continuous-deployment-github.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses PowerShell for all examples and instructions, assumes the use of Azure PowerShell (a Windows-centric tool), and does not provide any equivalent Bash, CLI, or Linux-native examples. All command references and cleanup instructions are PowerShell-specific, with no mention of cross-platform alternatives or Linux workflows.
Recommendations
- Provide equivalent examples using Azure CLI (az) with Bash syntax, which is cross-platform and widely used on Linux and macOS.
- Include a section or tabbed examples for both PowerShell and Bash/Azure CLI to ensure parity for Linux users.
- Mention installation and usage instructions for Azure CLI alongside Azure PowerShell.
- Reference Linux/macOS compatible tools and workflows where appropriate, not just Windows/PowerShell.
- Ensure that cleanup and deployment steps are shown for both PowerShell and Bash environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-php.md
...ob/main/articles/app-service/configure-language-php.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation generally provides parity between Windows and Linux instructions via platform pivots. However, there are several areas where Windows-specific tools (e.g., KuduScript, directory paths, DLLs) are mentioned or explained in more detail, and Windows instructions or concepts are presented first. Some sections (such as custom deployment scripts and Composer automation) are much more detailed for Windows, with Linux equivalents either missing or less explicit.
Recommendations
- Ensure that all examples and instructions provided for Windows (such as custom deployment scripts, Composer automation, and enabling extensions) have equally detailed Linux equivalents.
- Avoid presenting Windows instructions or tools first by default; alternate the order or clarify that both platforms are equally supported.
- Where Windows-specific tools (like KuduScript) are mentioned, provide Linux-native alternatives or clarify their applicability to Linux environments.
- For sections that discuss directory structures or file extensions (e.g., .dll vs .so, d:\ paths vs /home/site), explicitly note the Linux equivalents and provide parallel examples.
- Expand the Linux 'Run Composer' and 'Run Bower, Gulp, or Grunt' sections to match the detail and step-by-step guidance given for Windows.
- Review all troubleshooting and advanced configuration sections to ensure Linux users are not left with less actionable guidance.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/webjobs-create/webjob-types.md
...es/app-service/includes/webjobs-create/webjob-types.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation lists Windows file types and tools (cmd, bat, exe, PowerShell) in detail and first, while Linux support is described more generically and with fewer examples. Windows-specific tools and patterns are named explicitly, whereas Linux examples are minimal and lack parity in detail.
Recommendations
- Provide a more comprehensive list of supported file types for Linux, similar to the Windows section (e.g., include *.py*, *.pl*, *.php*, *.rb*, etc. if supported).
- List Linux examples with the same level of detail as Windows, including explicit mentions of runtimes and file types.
- Avoid listing Windows tools and patterns (cmd, PowerShell) before Linux equivalents; consider parallel structure or a neutral order.
- Include example scenarios for Linux containers similar to those given for Windows containers (e.g., mention Java, .jar, .war, etc. if supported).
- Clarify if runtimes for Linux file types are pre-installed, as is stated for Windows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/networking-features.md
.../blob/main/articles/app-service/networking-features.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exhibits a Windows bias primarily in the 'Hybrid Connections' section, where the only supported relay agent (Hybrid Connection Manager) is specified as requiring 'Windows Server 2012 or newer.' There are no Linux equivalents or instructions for Linux-based environments. Additionally, the 'Gateway-required virtual network integration' feature is stated as 'limited to App Service Windows plans,' with no Linux alternative or parity discussed. Throughout the document, there are no platform-specific command-line examples, but when platform limitations are mentioned, Windows is prioritized or exclusively supported.
Recommendations
- Provide explicit information about Linux support or alternatives for Hybrid Connections (e.g., clarify if a Linux agent exists or is planned, or suggest alternative connectivity options for Linux-based apps).
- For features limited to Windows (such as gateway-required VNet integration), clearly state the lack of Linux support and, if possible, provide workarounds or alternative approaches for Linux users.
- Where platform-specific tools or agents are required, include parity tables or cross-platform guidance to help Linux users achieve similar functionality.
- Consider adding Linux-focused examples or notes throughout the documentation to ensure equal clarity for both Windows and Linux deployment scenarios.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/monitor-app-service.md
.../blob/main/articles/app-service/monitor-app-service.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing Windows-centric tools (such as Visual Studio and PowerShell) and patterns, while not providing equivalent emphasis or examples for Linux users. For example, Visual Studio integration is mentioned for Application Insights, but no mention is made of Linux-friendly tools or editors. The page states that Azure activity logs can be queried using PowerShell, REST API, CLI, or portal, but PowerShell is listed before CLI, which is more cross-platform. There are no explicit Linux-specific examples or notes, and no mention of Linux-native tools or workflows.
Recommendations
- When mentioning development tool integration (e.g., Application Insights with Visual Studio), also mention popular Linux-friendly editors (such as VS Code) and their integration.
- When listing command-line options (PowerShell, CLI, REST API), list Azure CLI before PowerShell, or mention both equally, to reflect cross-platform parity.
- Provide explicit Linux examples or notes where relevant, such as how to access logs or monitor services from a Linux environment.
- Reference Linux-native troubleshooting or monitoring tools (such as tail, grep, journalctl) where appropriate, especially in sections discussing log streaming or diagnostics.
- Include links or references to Linux-specific documentation or guides for App Service monitoring.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-backup.md
...e-docs/blob/main/articles/app-service/manage-backup.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. File paths and environment variables are presented in Windows format (e.g., %HOME%, D:\home\site\wwwroot), and instructions for file exclusion reference Windows-style paths. The use of Kudu DebugConsole and FTP is described with Windows-centric paths. There is no mention of Linux shell commands or Linux-specific tools for managing files, and PowerShell is referenced as an automation option alongside Azure CLI, but no Linux shell scripting examples are provided. While the content does acknowledge Linux apps in some tables, practical examples and instructions are consistently Windows-first or Windows-only.
Recommendations
- Provide Linux-equivalent file paths (e.g., /home/site/wwwroot) alongside Windows paths in all examples and instructions.
- Include Linux shell (bash) commands for file operations, such as creating and uploading the _backup.filter file, in addition to or instead of Windows-centric instructions.
- Mention and demonstrate the use of Linux-native tools (e.g., SCP, SFTP, curl) for file uploads and management.
- When referencing environment variables, include both Windows (%HOME%) and Linux ($HOME) syntax.
- Offer automation examples using bash scripts, not just PowerShell, to ensure parity for Linux users.
- Clarify when instructions or features are OS-specific, and ensure that Linux users are not left to infer the correct procedure.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-local-cache.md
...blob/main/articles/app-service/overview-local-cache.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows-centric bias by referencing Windows file paths (e.g., D:\home), using Windows terminology and tools (such as Kudu/SCM), and omitting Linux-specific examples or equivalents. The documentation describes behaviors and settings primarily in the context of Windows-based App Service environments, with only brief mentions of Linux or containerized scenarios, and does not provide Linux command-line examples or clarify differences for Linux users.
Recommendations
- Provide parallel Linux examples and file paths (e.g., /home/site) alongside Windows paths.
- Explicitly describe how local cache works (or does not work) on Linux-based App Service plans, including any differences in behavior, paths, or configuration.
- Include Linux command-line examples (e.g., using Bash) for checking folder sizes or environment variables, not just references to Windows tools or extensions.
- Clarify the availability and configuration of local cache or its alternatives (such as App Cache) for Linux and containerized environments, with links to relevant documentation.
- Where features are not supported on Linux, provide clear guidance and alternatives for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-webjobs.md
...ocs/blob/main/articles/app-service/overview-webjobs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. Windows platforms and tools are mentioned first in lists (e.g., 'Windows code' before 'Linux code'), and deployment via Visual Studio (a primarily Windows tool) is highlighted with no equivalent Linux IDE example. File/script type support lists Windows executables and scripts before Bash and other cross-platform options. There are no explicit Linux-focused deployment or development examples, and the 'Develop WebJobs using Visual Studio' link reinforces a Windows-centric workflow.
Recommendations
- Alternate the order of platform mentions (e.g., list Linux and Windows options interchangeably or alphabetically).
- Include Linux-focused deployment and development examples, such as using VS Code, the Azure CLI, or direct Bash scripting.
- Highlight cross-platform tools (e.g., VS Code, GitHub Actions, Azure CLI) equally with Visual Studio.
- Provide explicit Linux-based workflows or tutorials, such as deploying from a Linux environment or using Bash scripts.
- Add links or references to Linux-friendly documentation or guides alongside Windows/Visual Studio resources.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/powershell-deploy-local-git.md
...les/app-service/scripts/powershell-deploy-local-git.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses PowerShell for all examples and instructions, which is primarily associated with Windows environments. There are no equivalent examples or guidance for Linux or cross-platform shells (such as Bash or Azure CLI). The tooling and workflow described are Windows-centric, and Linux users are not provided with alternative commands or approaches.
Recommendations
- Provide equivalent Bash or Azure CLI examples alongside PowerShell scripts to ensure Linux users can follow the documentation.
- Explicitly mention cross-platform compatibility where possible, and clarify if any steps are Windows-specific.
- Include references to Linux tools and workflows (e.g., using Bash, sh, or Azure CLI) in addition to PowerShell.
- Structure the documentation so that Windows and Linux instructions are given equal prominence, or provide tabs/switchers for different platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/powershell-monitor.md
...ain/articles/app-service/scripts/powershell-monitor.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses PowerShell for all examples, commands, and explanations, implicitly assuming a Windows environment. There are no Bash, CLI, or Linux-native examples or references. The focus on PowerShell and the absence of Linux alternatives or cross-platform guidance demonstrates a clear Windows bias.
Recommendations
- Provide equivalent Azure CLI (az) or Bash script examples alongside PowerShell scripts to support Linux and macOS users.
- Mention that PowerShell Core is cross-platform, or clarify if the instructions are specific to Windows PowerShell.
- Include references or links to Linux/macOS setup guides for Azure CLI or PowerShell Core.
- Reorder or supplement content so that both Windows and Linux approaches are presented equally, rather than prioritizing Windows tools.
- Add a section or note on how to perform the same tasks using the Azure Portal or REST API for maximum cross-platform compatibility.