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 1726-1750 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-file-based.md
...les/app-service/configure-authentication-file-based.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a file path example using a Windows path (C:\home\site\wwwroot) first, and only later mentions the Linux equivalent, without providing a Linux-specific example in the main steps. The note about Linux support is secondary and less detailed, and there are no Linux/POSIX shell or tooling examples.
Recommendations
- Provide Linux file path examples alongside or before Windows examples in all instructions.
- Explicitly show both Windows and Linux file paths in step-by-step instructions, not just in notes.
- Clarify any platform-specific behaviors or limitations in the main instructional flow, not only in notes.
- Include Linux/POSIX shell commands or references where relevant, ensuring parity with any Windows-specific instructions.
- Consider using platform-agnostic language (e.g., 'the root of your project (deployed to C:\home\site\wwwroot on Windows or /home/site/wwwroot on Linux)') throughout the documentation.
Create Pull Request
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
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for managing access restrictions, but PowerShell examples are featured prominently and sometimes appear before CLI examples. There are no explicit Linux shell (bash) or platform-specific examples, but the use of PowerShell commands and terminology may be more familiar to Windows users. The documentation does not mention or provide examples for Linux-native tools or workflows outside of the Azure CLI, which is cross-platform. There is a slight Windows bias due to the prominence and ordering of PowerShell examples.
Recommendations
- Ensure that Azure CLI examples are always presented before or alongside PowerShell examples, as CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that both Azure CLI and PowerShell are available in Cloud Shell, which is accessible from any OS.
- Where possible, provide bash shell script examples for common tasks, especially for scenarios where scripting is shown (e.g., multi-source rules).
- Clarify that all programmatic examples (CLI, ARM, Bicep) are platform-agnostic, and highlight this in introductory sections.
- Avoid assuming PowerShell as the default scripting language; balance with bash or sh examples where appropriate.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-plan-manage.md
...b/main/articles/app-service/app-service-plan-manage.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows by omitting any command-line or scripting examples for either Windows or Linux, but when OS is mentioned, Windows is referenced first (e.g., 'Windows to Linux'). There are no examples or guidance for managing App Service plans using Linux-native tools or CLI, nor is there parity in mentioning Linux-specific considerations or workflows.
Recommendations
- Add explicit examples for managing App Service plans using the Azure CLI (az), which is cross-platform and works on both Windows and Linux.
- Where OS types are mentioned, alternate the order (e.g., 'Linux or Windows') or clarify that both are supported equally.
- Include screenshots or instructions for Linux users, such as using the Azure CLI in a Bash shell or Cloud Shell.
- If PowerShell or Windows-specific tools are referenced in other sections, ensure equivalent Linux/Bash examples are provided.
- Highlight any differences or considerations specific to Linux App Service plans, if applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-linux-open-ssh-session.md
...ticles/app-service/configure-linux-open-ssh-session.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides detailed, step-by-step SSH access instructions and CLI examples exclusively for Linux containers, while Windows containers are only mentioned briefly and lack equivalent technical guidance. The Windows section states that SSH is supported via the browser but does not explain how to use SSH from the command line or provide any PowerShell or Windows-native SSH client examples. Additionally, the Windows container information is presented before the Linux section, but without technical depth.
Recommendations
- Add equivalent command-line SSH access instructions for Windows containers, including examples using PowerShell and Windows-native SSH clients.
- Provide explicit examples for connecting to Windows containers via SSH from both Windows and Linux clients, ensuring parity in technical depth.
- Clarify any limitations or differences in SSH support between Linux and Windows containers, and offer workarounds or alternatives where possible.
- Consider presenting Linux and Windows instructions in parallel (side-by-side or with clear pivots) to avoid the perception of prioritizing one platform over the other.
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 provides a troubleshooting step for clearing the DNS cache that only mentions the Windows-specific command (`ipconfig /flushdns`) and does not provide equivalent instructions for Linux or macOS users. No Linux or cross-platform alternatives are mentioned in this context, which may cause confusion or exclusion for non-Windows users.
Recommendations
- When providing troubleshooting steps that involve OS-specific commands (such as clearing DNS cache), include equivalent commands for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo /etc/init.d/nscd restart`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
- Wherever possible, use cross-platform language and examples, or explicitly mention steps for all major operating systems.
- Review the documentation for other subtle Windows-first assumptions, such as screenshots, terminology, or tool references, and ensure Linux/macOS parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-security.md
...ticles/app-service/configure-language-java-security.md
Medium Priority
View Details →
Detected Bias Types
Linux First
Missing Windows Example
Summary
The documentation page demonstrates a Linux-first bias in the sections related to Java key store and certificate management. It provides detailed instructions and examples specifically for Linux environments (e.g., file paths, SSH access, keytool usage), while omitting equivalent instructions or examples for Windows-based App Service environments. There are no PowerShell or Windows-specific tools or patterns mentioned, and Windows scenarios are not addressed in parallel with Linux ones.
Recommendations
- Add equivalent instructions for managing Java key stores and certificates on Windows-based App Service, including file paths, environment variables, and any differences in certificate handling.
- Provide examples for accessing and managing certificates using Windows tools (such as PowerShell or CMD), and document how to use the Java keytool on Windows App Service environments.
- Explicitly state any differences or limitations between Linux and Windows App Service environments regarding Java security configuration.
- Ensure that all sections that provide Linux-specific guidance also include Windows-specific guidance where applicable, or clearly indicate if a feature is Linux-only.
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 present and detailed, which can be seen as a Windows-centric approach. The Azure CLI examples are present and listed first, but there is no explicit mention of Linux or macOS environments, nor are there any Bash-specific or cross-platform shell instructions beyond Azure CLI. The PowerShell examples use Windows-style variable assignment and commands, which may not be directly usable on Linux/macOS without PowerShell Core. There are no references to Linux tools or workflows.
Recommendations
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and provide Bash shell examples where appropriate.
- Clarify that PowerShell examples require PowerShell Core for cross-platform compatibility, or provide Bash equivalents.
- Add a note or section for Linux/macOS users, highlighting any differences or confirming parity.
- Ensure that any variable assignment or scripting examples are shown in both Bash and PowerShell syntax, or use cross-platform syntax where possible.
- Consider including a table or tabbed interface for 'Bash', 'PowerShell', and 'Azure CLI' to make parity clear.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-configure-credentials.md
...n/articles/app-service/deploy-configure-credentials.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides command-line examples only for Azure CLI and Azure PowerShell, with no explicit Linux shell or cross-platform command examples (e.g., Bash, curl, sftp, or scp). The only scripting tool mentioned besides the portal is Azure PowerShell, which is primarily a Windows-centric tool, and there are no Linux-native tool examples for interacting with FTP/S or Git endpoints. Additionally, the documentation references escaping the dollar sign in Bash, but does not provide a concrete Bash example.
Recommendations
- Add explicit Bash/shell command examples for common tasks, such as using curl, sftp, or scp for FTP/S deployment, and git commands for local Git deployment.
- Include cross-platform notes and examples, especially for credential usage in Linux/macOS environments.
- When referencing PowerShell, provide equivalent Bash or Linux-native command alternatives where possible.
- Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and provide sample commands in a Linux shell context.
- Add troubleshooting tips or examples for Linux users, such as handling file permissions or credential storage.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-intelligent-apps-dotnet-to-azure-sql.md
...service/deploy-intelligent-apps-dotnet-to-azure-sql.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a subtle Windows bias by referencing UI actions such as 'Right click' and 'click Save' when adding files, which are more familiar to Windows users and Visual Studio users. There are no explicit Linux or cross-platform command-line instructions for these steps, and no mention of Linux-specific tools or editors. Additionally, there are no terminal-based or CLI-based examples for creating files or managing the app, which would help Linux users. The documentation does not provide parity for Linux users in these areas, despite the topic being relevant for cross-platform .NET development.
Recommendations
- Provide equivalent command-line instructions (e.g., using 'touch' and a text editor like 'nano' or 'vim') for creating and editing files, alongside the UI-based instructions.
- Avoid UI/IDE-specific language like 'Right click' and 'click Save' as the only method; instead, offer both GUI and CLI alternatives.
- Explicitly mention that the steps can be performed on Linux, macOS, and Windows, and provide examples or notes for each where relevant.
- Reference cross-platform tools (such as VS Code, dotnet CLI, Azure CLI) and show their usage in addition to or instead of Windows-centric tools.
- Where possible, use screenshots or code snippets that are not specific to a single OS, or provide alternatives for each major OS.
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 deployment examples for multiple platforms. However, the ASP.NET (classic) example is the only one that exclusively uses Windows runners and Windows-specific tools (NuGet, MSBuild), and it appears before the Linux/Ubuntu-based .NET Core example. All other language examples use Ubuntu runners and cross-platform tools. This ordering and tooling choice introduces a subtle Windows bias, especially for .NET developers.
Recommendations
- Provide a Linux/Ubuntu-based example for ASP.NET (classic) if possible, or clarify that Windows is required and explain why.
- Reorder the .NET Core and ASP.NET tabs so that the cross-platform .NET Core example appears first, emphasizing modern, cross-platform development.
- Where Windows-specific tools are required, explicitly state the reason and, if possible, suggest cross-platform alternatives or workarounds.
- Ensure parity in runner environments and tooling across all language examples to avoid implying Windows is the default or preferred environment.
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
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 often presented before CLI, and advanced scenarios (such as multi-source rules and Azure Front Door restrictions) are shown only with PowerShell. There are no explicit Linux shell or Bash script examples outside of Azure CLI, and PowerShell is a Windows-centric tool, which may disadvantage Linux users. However, the presence of Azure CLI examples (which are cross-platform) mitigates this bias somewhat.
Recommendations
- Ensure that for every PowerShell example, an equivalent Azure CLI example is provided, especially in advanced scenarios (e.g., multi-source rules, Azure Front Door restrictions).
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux users.
- Where possible, include Bash script snippets or notes for Linux users, especially for tasks that may require scripting or automation.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide links to installation instructions for non-Windows platforms.
- Review advanced scenario sections to ensure parity between PowerShell and CLI coverage.
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 contains a minor Windows bias: in the troubleshooting section, only the Windows-specific command (ipconfig /flushdns) is mentioned for clearing the DNS cache, with no equivalent Linux or macOS instructions. No other OS-specific tools or patterns are referenced, and the rest of the guide is platform-neutral.
Recommendations
- When suggesting DNS cache clearing, 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').
- Wherever OS-specific troubleshooting steps are provided, ensure parity by listing commands for all major platforms (Windows, Linux, macOS) or linking to relevant cross-platform documentation.
- Consider a short note or table summarizing DNS cache clearing for different operating systems to improve accessibility for non-Windows users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-cleanup.md
...main/articles/app-service/includes/tutorial-cleanup.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation only describes how to delete resources using the Azure portal, which is a graphical interface commonly associated with Windows environments. There are no command-line examples provided for Linux users, such as using Azure CLI or Bash scripts, nor is there mention of PowerShell or Windows-specific tools, but the lack of Linux/CLI parity is notable.
Recommendations
- Add Azure CLI command-line examples for deleting the resource group, suitable for Linux/macOS/Windows terminals.
- Include Bash script snippets for automation scenarios.
- Explicitly mention that the Azure portal is cross-platform, but provide parity with CLI instructions for users who prefer or require non-GUI workflows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
...service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation assumes a development environment based on .NET and Azure App Service, with all examples and instructions tailored to ASP.NET Core and related Microsoft tooling. There are no explicit instructions or examples for Linux-based development environments, non-Windows shells, or alternative deployment methods outside of Azure-centric workflows. The use of GitHub Codespaces (which is cross-platform) mitigates some bias, but the overall focus is on Windows/Microsoft technologies, and there is no mention of Linux-specific considerations or parity.
Recommendations
- Add explicit instructions for running the sample app and commands in a Linux shell (e.g., bash) and clarify that the dotnet CLI and azd work cross-platform.
- Include notes or examples for deploying to Azure App Service from Linux or macOS environments, such as using Azure CLI in bash or zsh.
- Mention that the development and deployment steps are platform-agnostic where applicable, and highlight any differences or prerequisites for Linux users (e.g., installing .NET SDK on Ubuntu).
- If any step is Windows-specific (such as using Visual Studio or Windows-only tools), provide equivalent steps for Linux (e.g., using VS Code, nano/vim, or command-line git).
- Clarify that Azure App Service supports both Windows and Linux hosting, and provide links or notes for Linux-specific hosting scenarios.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-secure-domain-certificate.md
...cles/app-service/tutorial-secure-domain-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally platform-neutral, focusing on Azure Portal UI steps. However, in the troubleshooting section, the only example given for clearing the DNS cache is the Windows-specific 'ipconfig /flushdns' command. There is no mention of how to perform this action on Linux or macOS, nor are alternative commands or instructions provided for non-Windows users.
Recommendations
- When providing command-line troubleshooting steps (such as clearing 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').
- If referencing OS-specific tools or commands, present them in a cross-platform table or list, or explicitly mention all major platforms.
- Review documentation for other subtle Windows-first assumptions, such as screenshots or terminology, and ensure parity for Linux and macOS users where relevant.
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 or PowerShell bias in its main instructions. However, in the troubleshooting section, the only example given for clearing the DNS cache is the Windows-specific 'ipconfig /flushdns' command. There is no mention of the equivalent commands for Linux or macOS, nor are any Linux-specific tools or patterns referenced elsewhere on the page.
Recommendations
- When providing troubleshooting steps involving system commands (such as clearing 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 the documentation for other subtle platform-specific references and ensure parity by including cross-platform instructions or notes.
- Consider adding a brief note or table in troubleshooting sections that lists common DNS cache flush commands for Windows, Linux, and macOS.
- Continue to avoid platform-specific screenshots or UI references unless absolutely necessary, and if used, provide alternatives or clarifications for other platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-microsoft-graph-as-app/introduction.md
...cludes/tutorial-microsoft-graph-as-app/introduction.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI scripts for granting Microsoft Graph permissions to a managed identity, but the PowerShell example is presented first and in greater detail, which may suggest a preference for Windows-centric tooling. There is no explicit Linux example or mention of Linux-specific considerations, although the Azure CLI example is cross-platform.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more accessible to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reassure non-Windows users.
- Add Bash shell examples or clarify that the Azure CLI script is intended for Bash (Linux/macOS) environments.
- If PowerShell is included, consider also including Bash or shell script equivalents for any non-Azure CLI steps.
- Review the language throughout the documentation to ensure it does not assume a Windows environment or tooling.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-secure-domain-certificate.md
...cles/app-service/tutorial-secure-domain-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally platform-neutral, focusing on Azure Portal UI steps. However, in the troubleshooting section for clearing DNS cache, only the Windows-specific command (`ipconfig /flushdns`) is mentioned, with no equivalent instructions for Linux or macOS. This presents a subtle 'windows_first' and 'missing_linux_example' bias.
Recommendations
- Include equivalent DNS cache clearing instructions 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`).
- When providing OS-specific troubleshooting steps, present all major platforms together or in a tabbed/sectioned format to ensure parity.
- Review other troubleshooting or command-line instructions to ensure cross-platform coverage.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-cleanup.md
...main/articles/app-service/includes/tutorial-cleanup.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation describes resource cleanup using the Azure portal, which is platform-agnostic, but omits command-line examples. There are no CLI (Azure CLI, Bash, or PowerShell) instructions provided, which is a missed opportunity for Linux parity. Historically, Azure docs often provide PowerShell examples first or exclusively, but in this case, neither PowerShell nor Bash/Azure CLI examples are present. However, the lack of any CLI example can be seen as a subtle bias, as Windows users are more likely to use the portal, while Linux users often prefer CLI.
Recommendations
- Add Azure CLI and/or Bash command examples for deleting the resource group, such as 'az group delete --name <resource-group-name>'.
- If providing PowerShell examples, ensure Bash/Azure CLI equivalents are given with equal prominence.
- Explicitly mention that the portal instructions apply equally to all platforms, but provide CLI alternatives for users who prefer automation or non-GUI workflows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
...service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes a development environment (GitHub Codespaces) that is cross-platform, but all examples, tools, and workflows are specific to .NET and Azure App Service, which are traditionally more Windows-centric. There are no explicit Linux or cross-platform command-line examples, nor any mention of Linux-specific tools, deployment patterns, or troubleshooting. The workflow assumes familiarity with .NET and Azure-centric tools, with no alternative instructions for Linux-native environments or non-Windows editors/terminals.
Recommendations
- Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and clarify any OS-specific requirements.
- Include example commands for common Linux shells (e.g., bash/zsh) where relevant, especially for deployment or environment variable configuration.
- If using GitHub Codespaces, note that it runs on Linux by default, and provide troubleshooting tips for local Linux development.
- Add a section or callout for developers working on Linux locally (outside Codespaces), including how to install .NET SDK, run the app, and deploy using CLI tools.
- Ensure that all instructions (such as opening the browser, copying URLs, or running dotnet commands) are clear for users on Linux and macOS as well as Windows.
- If any step is different on Linux (e.g., environment variable syntax, file paths), provide the Linux equivalent.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-cleanup.md
...main/articles/app-service/includes/tutorial-cleanup.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation only describes how to delete resources using the Azure portal, which is a GUI-based approach commonly associated with Windows workflows. There are no command-line examples (such as Azure CLI or Bash) that would be more familiar to Linux users, nor is there mention of Powershell or Windows-specific tools, but the lack of Linux-friendly instructions constitutes a subtle Windows-first bias.
Recommendations
- Add Azure CLI command-line examples for deleting the resource group (e.g., `az group delete --name <resource-group-name>`), which can be run on both Windows and Linux.
- Include Bash and/or PowerShell script examples for automation.
- Explicitly mention that the Azure portal is cross-platform, but provide parity by showing both GUI and CLI methods.
- Ensure that screenshots and instructions do not assume a Windows environment (e.g., avoid showing Windows-only UI elements or terminology).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-configure-tls-mutual-auth.md
...p-service/app-service-web-configure-tls-mutual-auth.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a 'windows_first' bias by providing detailed ASP.NET and ASP.NET Web Forms (Windows-centric) code samples before other platforms, and by referencing the HttpRequest.ClientCertificate property, which is specific to Windows/IIS environments. There are no explicit Linux command-line examples (e.g., using curl or OpenSSL to test mutual TLS), nor is there mention of Linux-specific tools or patterns for certificate management or validation. The focus is on Azure portal, Azure CLI, Bicep, and ARM templates for configuration, which are cross-platform, but the application code samples prioritize Windows/.NET technologies.
Recommendations
- Add Linux command-line examples (e.g., using curl or OpenSSL) to demonstrate how to test mutual TLS authentication from a Linux environment.
- Include a section or note on how to access and validate client certificates in common Linux web servers (e.g., Nginx, Apache) when running on App Service for Linux.
- Provide parity in code sample ordering by rotating or randomizing the order of language/framework examples, or by starting with a cross-platform language (e.g., Node.js or Python) rather than Windows/.NET.
- Mention any Linux-specific considerations or troubleshooting steps for mutual TLS in Azure App Service, especially for App Service for Linux.
- Reference cross-platform certificate management tools (e.g., OpenSSL) alongside Windows-specific APIs or tools.
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 OS-specific instructions, but there is a notable instance of Windows bias: when instructing users to clear the DNS cache, only the Windows command ('ipconfig /flushdns') is mentioned, with no equivalent Linux or macOS instructions. No PowerShell-specific scripts or Windows-only tools are referenced elsewhere, and the portal-based workflow is platform-agnostic.
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 any automation or scripting sections to ensure that examples are not limited to Windows batch or PowerShell, and provide Bash or cross-platform alternatives if applicable.
- Continue to avoid referencing Windows-only tools or patterns unless absolutely necessary, and always provide parity for Linux/macOS users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-agent-web-app-semantic-kernel-foundry-dotnet.md
...torial-ai-agent-web-app-semantic-kernel-foundry-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation avoids explicit Windows-only tools and PowerShell, but it exhibits subtle Windows bias by omitting any mention of Linux-specific development environments, deployment patterns, or troubleshooting. The use of GitHub Codespaces (which is cross-platform) and Bash commands is positive, but there is no discussion of running or deploying the app on a local Linux machine, nor are there instructions for Linux users who may not use Codespaces. The documentation assumes Azure CLI and .NET CLI are available, but doesn't address installation or environment setup on Linux, nor does it mention WSL or Linux-native workflows. All screenshots and UI references are Azure-centric, with no nod to Linux desktop environments or terminal conventions.
Recommendations
- Add a section or notes on how to set up the development environment on a local Linux machine, including .NET SDK and Azure CLI installation instructions for Linux.
- Explicitly state that all CLI commands work on Linux, macOS, and Windows, and provide troubleshooting tips for common Linux-specific issues (e.g., permissions, port usage).
- Include at least one example of running the sample app outside Codespaces, such as on Ubuntu or another popular Linux distribution.
- Mention that the Azure CLI and .NET CLI are cross-platform, and provide links to Linux installation guides.
- If screenshots of terminals are included, show at least one from a Linux terminal emulator.
- Clarify that the instructions do not require Windows or PowerShell, and highlight any differences (if any) for Linux users.
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
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all programmatic tasks, but PowerShell is given equal or greater prominence, including in advanced scenarios and inline code blocks. PowerShell is a Windows-centric tool, and its inclusion as a primary example can be seen as a Windows bias, especially since Linux-native scripting options (such as Bash or shell scripts) are not explicitly mentioned. Additionally, in some advanced scenario sections, PowerShell examples are shown before or without equivalent CLI examples, reinforcing a 'windows_first' pattern.
Recommendations
- Ensure that for every PowerShell example, an equivalent Azure CLI example is provided, especially in advanced scenario sections (e.g., multi-source rules, Azure Front Door filtering).
- Where possible, provide Bash/shell script snippets for common Linux workflows, or clarify that Azure CLI commands can be run natively on Linux/macOS.
- In introductory and advanced sections, present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more native to Linux environments.
- Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and consider linking to guidance on installing and using Azure CLI on Linux.
- Avoid assuming the use of PowerShell in narrative text; instead, refer to 'your preferred scripting environment' or similar inclusive language.