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 1551-1575 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-api-version.md
...es/app-service/configure-authentication-api-version.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page exclusively uses Azure CLI commands and portal instructions, with no mention of platform-specific tools or shell environments (such as PowerShell or Bash). However, there is a subtle bias in that all command-line examples use the Azure CLI in a way that is most familiar to Windows users (e.g., backslash line continuations), and there are no explicit Linux/Bash shell examples or notes about cross-platform usage. There are also no references to Linux-specific tools, patterns, or considerations, and no mention of how to perform these actions outside the Azure CLI or portal (e.g., via REST with curl, or using Bash scripting).
Recommendations
- Add explicit Bash/Linux shell examples, including line continuations with backslashes and/or semicolons as appropriate.
- Clarify that Azure CLI commands are cross-platform, and provide notes or examples for running them in Bash/Linux environments (e.g., using \ for line continuation in Bash, or using single-line commands).
- Include alternative instructions for performing API calls using curl or other common Linux tools, especially for the REST API examples.
- If any PowerShell-specific instructions are relevant, provide equivalent Bash/Linux commands.
- Add a note about the cross-platform nature of Azure CLI and how to install/use it on Linux, or link to the Linux installation guide.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-github-actions/deploy-github-actions-openid-connect.md
...github-actions/deploy-github-actions-openid-connect.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides cross-platform deployment examples for various languages, with most workflows running on Ubuntu (Linux). However, the ASP.NET (not Core) example exclusively uses 'windows-latest' runners and Windows-specific tools (NuGet, MSBuild), and it is presented before the Java, Node.js, and Python examples. There is no equivalent Linux-based example for classic ASP.NET, which may disadvantage Linux users or those seeking parity.
Recommendations
- Provide a Linux-based example for deploying ASP.NET applications, if technically feasible (e.g., using Mono or .NET Core for compatible projects).
- Clearly explain why Windows runners are required for certain workloads (such as classic ASP.NET) and suggest alternatives or workarounds for Linux users.
- Ensure that for each language or framework, both Windows and Linux deployment options are documented where possible.
- Consider reordering or grouping examples so that Windows-specific workflows are not always presented before Linux ones, or explicitly call out platform requirements in headings.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/deploy-zip-azure-portal-1.md
...ncludes/quickstart-python/deploy-zip-azure-portal-1.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation uses UI navigation steps that are generic but implicitly reflect a Windows-centric perspective by referencing the Azure portal's left toolbar and settings structure, which may be more familiar to Windows users. There are no examples or instructions for performing the same configuration via Linux-friendly methods, such as Azure CLI, Bash, or ARM templates, nor is there mention of command-line alternatives.
Recommendations
- Add equivalent instructions for configuring application settings using Azure CLI and Bash, which are commonly used on Linux.
- Provide examples of how to set application settings via ARM templates or REST API for cross-platform parity.
- Explicitly mention that the Azure portal UI is the same across platforms, or clarify any differences if they exist.
- Include a section or links for command-line and automation options to ensure Linux and macOS users are equally supported.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/remove-resource-group-visual-studio-code-2.md
...t-python/remove-resource-group-visual-studio-code-2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation describes a resource deletion process using a graphical user interface with right-click actions, which is a pattern most commonly associated with Windows environments. There are no equivalent instructions or examples for Linux users, such as command-line alternatives or references to cross-platform tools.
Recommendations
- Include command-line instructions (e.g., using Azure CLI or Bash) for deleting a resource group, which are accessible and familiar to Linux users.
- Avoid describing only GUI-based workflows; provide parity with terminal-based methods.
- Explicitly mention that the instructions apply to the Azure Portal (if that's the case), and offer alternatives for users who prefer or require non-GUI approaches.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/stream-logs-azure-portal-1.md
...cludes/quickstart-python/stream-logs-azure-portal-1.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation describes enabling streaming logs in Azure App Service exclusively through the Azure portal UI, which is a cross-platform method, but it does not mention or provide examples for command-line alternatives (such as Azure CLI or PowerShell). There is no explicit Windows-only tool or command, but the omission of CLI examples (which are often used on Linux) and the lack of mention of Linux-specific considerations may disadvantage Linux users.
Recommendations
- Add Azure CLI examples for enabling streaming logs, as CLI is widely used on Linux.
- If PowerShell examples are provided elsewhere, ensure equivalent Azure CLI or Bash examples are also included.
- Mention any Linux-specific considerations for App Service logging, if applicable.
- Structure the documentation so that cross-platform (CLI, REST API) methods are presented alongside or before platform-specific UI instructions.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/deploy-zip-curl-commands.md
...includes/quickstart-python/deploy-zip-curl-commands.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Bash and PowerShell examples, but the instructions for accessing the Kudu Environment are written in a way that assumes the user is using the Azure portal UI, which is more familiar to Windows users. Additionally, the PowerShell example is given equal prominence, and the note about username quoting specifically addresses PowerShell behavior, suggesting a Windows-centric perspective.
Recommendations
- Include explicit instructions for accessing the Kudu Environment from Linux/macOS terminals, such as using the Azure CLI or direct URL access, not just the Azure portal UI.
- Add notes or troubleshooting tips relevant to Bash/Linux users, similar to the PowerShell-specific note.
- Consider listing the Bash example before the PowerShell example to avoid implicit prioritization of Windows environments.
- Mention any platform-specific prerequisites or differences in behavior between Bash and PowerShell to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/stream-logs-visual-studio-code-1.md
.../quickstart-python/stream-logs-visual-studio-code-1.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references the Azure Tools for VS Code extension, which is commonly used on Windows, and does not provide any alternative instructions or examples for enabling streaming logs via Linux command-line tools or native Azure CLI commands. There is no mention of Linux-specific workflows or tools.
Recommendations
- Add instructions for enabling streaming logs using the Azure CLI, which is cross-platform and commonly used on Linux.
- Include examples for enabling streaming logs via the Azure portal, which is OS-agnostic.
- Explicitly mention that the VS Code extension is available on all platforms, if applicable, or provide alternatives for Linux users.
- Ensure that documentation covers both GUI and command-line approaches to accommodate users on different operating systems.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-dotnet-storage-managed-identity/introduction.md
...torial-dotnet-storage-managed-identity/introduction.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both PowerShell and Azure CLI examples for scripting tasks, but PowerShell (a Windows-centric tool) is consistently listed before Azure CLI in all code example tabs. There are no explicit Linux shell or bash examples, and the PowerShell examples may not be directly usable on Linux systems. The portal instructions are platform-agnostic, but scripting guidance is Windows-first.
Recommendations
- Alternate the order of PowerShell and Azure CLI tabs, or list Azure CLI first to reflect its cross-platform nature.
- Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell examples may require PowerShell Core on non-Windows systems.
- Add bash shell examples where appropriate, especially for common scripting tasks.
- Clarify in the prerequisites or introduction that all tasks can be performed from Linux, macOS, or Windows using Azure CLI, and provide links to installation instructions for each OS.
- Where PowerShell is used, specify if the script is compatible with PowerShell Core (cross-platform) or only Windows PowerShell.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/deploy-local-git-azure-portal-4.md
...-nodejs-mongodb-app/deploy-local-git-azure-portal-4.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation references 'FTPS credentials' and describes deployment steps without providing platform-specific guidance. FTPS is often associated with Windows tools, and there are no examples or instructions for Linux users or alternative tools commonly used on Linux (such as command-line FTP clients or scp/rsync). The lack of Linux-specific examples or mention of cross-platform tools suggests a subtle Windows bias.
Recommendations
- Include explicit instructions or examples for deploying code using common Linux tools (e.g., lftp, curl, or command-line git).
- Mention cross-platform deployment methods and tools, ensuring both Windows and Linux users are addressed.
- If FTPS is required, provide example commands for both Windows (e.g., FileZilla, WinSCP) and Linux (e.g., lftp, curl).
- Clarify that the credentials can be used with any standard FTPS or Git client, and link to relevant documentation for both platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-dotnetcore-sqldb-app/deploy-from-local-git-azure-portal-2.md
...core-sqldb-app/deploy-from-local-git-azure-portal-2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides UI navigation steps that are generic, but it implicitly assumes a Windows-style interface (e.g., 'menu on the left side', 'top menu bar') without clarifying if the experience is the same on Linux or cross-platform environments. There are no examples or notes for Linux users, nor is there mention of command-line alternatives that might be more familiar to Linux users.
Recommendations
- Clarify if the UI steps are identical across Windows, Linux, and Mac platforms, or note any differences.
- Include command-line instructions (e.g., using Azure CLI) as an alternative to GUI steps, which is often preferred by Linux users.
- Explicitly mention platform parity or provide screenshots/examples for both Windows and Linux environments.
- Add a note or section addressing any platform-specific considerations for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-dotnetcore-sqldb-app/deploy-from-local-git-azure-portal-3.md
...core-sqldb-app/deploy-from-local-git-azure-portal-3.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation does not provide any platform-specific examples or commands, but it implicitly assumes a Windows-centric workflow by referencing the 'Git prompt' without clarifying cross-platform usage. There are no explicit Linux or macOS instructions or examples, and no mention of platform-specific tools or differences.
Recommendations
- Add explicit instructions or examples for both Windows (e.g., Command Prompt, PowerShell) and Linux/macOS (e.g., Bash terminal) when describing how to use the credentials.
- Clarify that the Git prompt and authentication process are similar across platforms, or note any differences if they exist.
- Provide sample git commands for both Windows and Linux/macOS environments to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/build-settings-azure-portal-1.md
...al-nodejs-mongodb-app/build-settings-azure-portal-1.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation describes navigation steps using the Azure portal UI, which is generally cross-platform. However, there is an implicit Windows-first bias as there are no references to Linux-specific workflows, CLI commands, or alternative methods that Linux users might prefer. There are no examples or instructions for performing the same task using the Azure CLI, Bash, or other non-Windows tools.
Recommendations
- Add equivalent instructions for configuring application settings using the Azure CLI, which is platform-agnostic and commonly used on Linux.
- Include Bash or shell command examples for Linux users.
- Explicitly state that the Azure portal steps are the same across operating systems, or provide links to documentation for Linux/macOS users.
- Consider adding a section titled 'Using the Azure CLI' or 'Command-line Instructions' to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-php-mysql-app/azure-portal-stream-diagnostic-logs-1.md
...php-mysql-app/azure-portal-stream-diagnostic-logs-1.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides instructions that are tailored to the Azure App Service interface without specifying platform differences, but the steps and terminology (such as 'File System' logging) are more commonly associated with Windows-based App Service plans. There is no mention of Linux-specific logging options or differences, nor are Linux examples provided.
Recommendations
- Explicitly state whether the instructions apply to both Windows and Linux App Service plans.
- If there are differences in logging configuration or terminology for Linux-based App Service, provide parallel instructions or note the differences.
- Include examples or screenshots for both Windows and Linux App Service environments.
- Mention any Linux-specific logging options (such as Docker logs or Linux file system paths) if applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-python-postgresql-app/deploy-local-git-azure-portal-3.md
...thon-postgresql-app/deploy-local-git-azure-portal-3.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation refers to copying the 'Git Clone Uri' for later use but does not provide any example commands or instructions for setting up the Git remote. There is no explicit mention of Windows tools, but the lack of Linux-specific or cross-platform instructions/examples (such as terminal commands for adding a Git remote) suggests a bias by omission, as it assumes a generic or possibly Windows-centric workflow.
Recommendations
- Add explicit cross-platform instructions for setting up a Git remote, including both Windows (Command Prompt/PowerShell) and Linux/macOS (bash) command examples.
- Where possible, provide screenshots or terminal snippets for both environments.
- Clarify that the instructions apply to all platforms, or specify any platform-specific steps if necessary.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-up.md
...docs/blob/main/articles/app-service/manage-scale-up.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing 'Azure App Service on Windows pricing' and omitting any mention of Linux-based App Service plans or their pricing/features. There are no Linux-specific instructions, screenshots, or links, and the terminology and examples assume a Windows environment.
Recommendations
- Include references and links to Azure App Service on Linux pricing and documentation alongside Windows equivalents.
- Add notes clarifying differences (if any) in scaling workflows or available features between Windows and Linux App Service plans.
- Provide screenshots and examples for both Windows and Linux App Service environments.
- Ensure that all feature comparisons and limitations are presented for both Windows and Linux tiers, or clearly state if a feature is Windows-only.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/routine-maintenance.md
.../blob/main/articles/app-service/routine-maintenance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing 'local cache for Windows apps' as a mitigation for cold starts, without mentioning an equivalent for Linux apps or clarifying Linux support. No Linux-specific examples, tools, or guidance are provided, and the only platform-specific advice is Windows-focused.
Recommendations
- When mentioning features like local cache, clarify whether similar functionality exists for Linux apps, and provide links or documentation for Linux equivalents if available.
- Include examples or notes for both Windows and Linux App Service plans when discussing mitigation strategies, such as cold start reduction.
- Review all platform-specific recommendations to ensure Linux parity, or explicitly state if a feature is Windows-only.
- Consider adding a section or FAQ entry addressing any differences in maintenance experience or preparation steps for Linux-based App Service plans.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is generally cross-platform and avoids explicit Windows-only tooling or examples. However, there is a subtle Windows bias in the troubleshooting section, where only the Windows-specific command ('ipconfig /flushdns') is mentioned for clearing the DNS cache. No equivalent Linux or macOS instructions are provided, and the Windows method is given as the sole example. There are no PowerShell scripts, Windows tools, or patterns otherwise, but the omission of Linux/macOS parity in this instance constitutes a minor bias.
Recommendations
- When mentioning DNS cache clearing, provide equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo service nscd restart') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
- Wherever OS-specific troubleshooting steps are given, include instructions for all major platforms (Windows, Linux, macOS) to ensure parity.
- Consider adding a short table or note with DNS cache clearing commands for each OS in the troubleshooting section.
- Review other troubleshooting or automation sections for similar implicit Windows-first assumptions, and add cross-platform guidance as needed.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/create-app-service-visual-studio-code-2.md
...tart-python/create-app-service-visual-studio-code-2.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides instructions that are generic but implicitly assume a Windows environment by referencing VS Code UI patterns and terminology commonly associated with Windows users. There are no Linux-specific instructions or clarifications, and no mention of alternative workflows or considerations for Linux users.
Recommendations
- Explicitly mention that the instructions apply to all platforms (Windows, Linux, macOS) if true.
- Include notes or screenshots showing the process on Linux (and macOS) to ensure parity.
- Highlight any differences in UI or behavior that Linux users might encounter.
- If there are command-line alternatives (e.g., using Azure CLI), provide those as well for users who may not use VS Code or prefer terminal workflows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is generally platform-neutral but contains a subtle Windows bias. Specifically, when discussing clearing the DNS cache, only the Windows command (`ipconfig /flushdns`) is mentioned, with no equivalent instructions for Linux or macOS. No PowerShell-specific commands or Windows-only tools are otherwise present, and the rest of the instructions are portal-based and cross-platform.
Recommendations
- When providing troubleshooting steps such as clearing the DNS cache, include equivalent commands for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo resolvectl flush-caches`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
- Review other troubleshooting or automation sections to ensure parity in examples and instructions for Linux and macOS users.
- If scripting or CLI automation is discussed, ensure that examples are provided for Bash (Linux/macOS) as well as PowerShell/Command Prompt (Windows), or clarify when instructions are cross-platform.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-apm.md
...in/articles/app-service/configure-language-java-apm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally provides parity between Linux and Windows, offering separate sections and examples for both platforms. However, there are subtle signs of Windows bias: in the Application Insights section, the Windows-specific app setting (XDT_MicrosoftApplicationInsights_Java=1) is mentioned, and the use of the Kudu console (a Windows-centric tool) is specified for Windows, while SSH is used for Linux. In some cases, the Windows instructions reference tools or patterns (like Kudu) before or instead of Linux equivalents. The ordering of tabs sometimes places Windows before Linux, and the documentation occasionally assumes familiarity with Windows tools.
Recommendations
- Ensure that Linux and Windows instructions are presented with equal prominence and in a consistent order (e.g., always Linux first or alphabetical).
- Where a Windows-specific tool (like Kudu) is mentioned, provide a brief explanation or a Linux equivalent (e.g., SSH, SFTP, or Azure CLI).
- Clarify when certain app settings or environment variables are Windows-only, and provide Linux alternatives or explicitly state when not needed.
- Review all examples and ensure that both Linux and Windows users have clear, step-by-step guidance using tools native to their platform.
- Consider adding a summary table comparing platform-specific steps for quick reference.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation-terraform.md
...articles/app-service/environment/creation-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell tab is presented alongside the CLI tab without explicit Linux/bash examples. PowerShell is a Windows-centric tool, and its inclusion as a primary verification method can indicate a Windows bias, especially since no bash or Linux-native shell examples are given. The CLI examples use variable assignment syntax compatible with bash, but there is no explicit mention or guidance for Linux/macOS users, nor are there instructions for running these commands in a Linux environment.
Recommendations
- Explicitly state that the Azure CLI examples use bash syntax and are suitable for Linux/macOS as well as Windows (with WSL or Git Bash).
- Add a dedicated 'Bash' or 'Linux/macOS' tab or section to clarify usage on non-Windows platforms.
- Provide guidance for running Azure CLI commands in native Linux/macOS terminals.
- If PowerShell is included, clarify that it is primarily for Windows users, and provide parity by ensuring bash/Linux examples are equally visible and complete.
- Mention cross-platform compatibility of Terraform and Azure CLI, and link to platform-specific installation guides where appropriate.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-dotnet-storage-managed-identity/introduction.md
...torial-dotnet-storage-managed-identity/introduction.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both PowerShell and Azure CLI examples, but consistently lists PowerShell (a Windows-centric tool) before Azure CLI (cross-platform) in all code example tabs. There is no explicit mention of Linux or Bash, and no Linux-specific guidance or screenshots. The use of PowerShell as the first scripting example and the reference to Visual Studio (a Windows-preferred IDE) for enabling managed identity further reinforce a subtle Windows-first bias.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash shell context where appropriate.
- Include Linux/Bash-specific notes or screenshots where UI differences exist.
- Reference cross-platform editors (such as VS Code) alongside Visual Studio when discussing development environments.
- Consider adding a short section or note highlighting parity and any differences for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-github-actions/deploy-github-actions-service-principal.md
...hub-actions/deploy-github-actions-service-principal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides cross-platform deployment examples for multiple languages, with most workflows running on Ubuntu (Linux). However, the ASP.NET (not Core) example is Windows-specific, using 'runs-on: windows-latest' and Windows-only tools (NuGet, MSBuild) without mentioning or providing Linux alternatives. Additionally, the ASP.NET section appears before Java, Node.js, and Python, potentially reinforcing a Windows-first impression for .NET developers.
Recommendations
- Provide a Linux-based example for ASP.NET (if feasible), or explicitly state that classic ASP.NET requires Windows runners due to MSBuild and NuGet dependencies.
- Add a note clarifying platform requirements for each stack, especially where Windows is mandatory.
- Where possible, mention cross-platform alternatives to Windows tools (e.g., dotnet CLI for .NET Core/5+).
- Ensure that the order of sections does not imply Windows is the default or preferred platform for all stacks.
- Consider adding a summary table indicating OS compatibility for each language/framework example.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/create-app-service-visual-studio-code-1.md
...tart-python/create-app-service-visual-studio-code-1.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references the Azure Tools for VS Code extension, which is primarily a GUI tool often associated with Windows workflows. There are no mentions of equivalent command-line or Linux-native approaches, nor are there alternative instructions for users on Linux or macOS.
Recommendations
- Include instructions for accessing Azure resources using command-line tools such as Azure CLI, which are cross-platform.
- Mention how to install and use Azure Tools for VS Code on Linux and macOS, or provide alternative workflows for those platforms.
- Provide parity by linking to documentation for both GUI and CLI-based Azure management.
- Clarify that the instructions apply to all platforms, or specify any platform-specific steps if necessary.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/routine-maintenance.md
.../blob/main/articles/app-service/routine-maintenance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by referencing 'local cache for Windows apps' as a mitigation for cold starts, without mentioning an equivalent feature or guidance for Linux-based App Service apps. No Linux-specific tools, patterns, or examples are provided, and the only OS-specific advice is for Windows.
Recommendations
- Include equivalent guidance or features for Linux-based App Service apps, such as caching strategies or startup optimizations.
- When mentioning OS-specific features (e.g., local cache for Windows), explicitly state whether there is a Linux equivalent or provide alternative recommendations for Linux users.
- Add examples or notes that address both Windows and Linux scenarios where relevant, ensuring parity in operational guidance.