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 1701-1725 of 2121 flagged pages
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 GitHub Codespaces and .NET, but does not provide any explicit Windows-specific commands or tools. However, it lacks any mention of Linux-specific workflows, terminal commands, or deployment patterns outside of the Codespaces/Azure CLI context. There are no PowerShell or Windows-only tools, but the absence of Linux-native examples (such as local development on Linux, or using Linux package managers) and the focus on .NET (which is cross-platform but often associated with Windows) may make the documentation less approachable for Linux users who do not use Codespaces.
Recommendations
- Add explicit instructions for running the sample app locally on Linux (e.g., Ubuntu), including installation of .NET SDK and any dependencies.
- Provide terminal commands for both Windows (PowerShell/CMD) and Linux (bash) where relevant, especially for deployment and running the app.
- Mention how to use local development environments outside of Codespaces, including Linux and macOS.
- Clarify that all commands are cross-platform, or provide platform-specific notes if any step differs between Windows and Linux.
- Include troubleshooting tips for common Linux-specific issues (e.g., file permissions, port conflicts, .NET installation).
Create Pull Request
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 overt Windows-specific tools and commands, but it demonstrates subtle Windows bias by omitting explicit Linux instructions or considerations. It assumes the use of GitHub Codespaces (cloud-based, cross-platform) and Azure CLI (cross-platform), but does not provide any Linux-specific guidance or troubleshooting. There are no PowerShell or Windows-only commands, but the lack of Linux-specific notes or parity checks (such as file path differences, environment variable handling, or local development outside Codespaces) may disadvantage Linux users.
Recommendations
- Add a section or notes about running the sample locally on Linux (e.g., Ubuntu), including any prerequisites or differences in environment setup.
- Explicitly mention that all CLI commands (azd, az, dotnet) are cross-platform, and provide troubleshooting tips for common Linux issues (such as permissions, firewall, or dependency installation).
- Include examples or screenshots from Linux environments, not just browser-based Codespaces.
- If any steps differ on Linux (such as file permissions or case sensitivity), call these out in the instructions.
- Encourage feedback from Linux users to further improve parity and documentation completeness.
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 provides only Azure CLI and Azure Portal instructions, with no mention of platform-specific command-line environments (such as PowerShell or Bash). However, there is a subtle Windows bias in that all instructions and examples assume use of the Azure CLI, which is cross-platform but often associated with Windows environments, and there is no explicit mention of Linux or Bash-specific workflows. There are no examples or guidance for Linux users regarding environment variables, file paths, or shell commands, and no mention of using Bash or Linux-native tools. The documentation also refers to the Azure Portal UI, which is platform-agnostic, but omits any Linux-specific considerations or examples.
Recommendations
- Add explicit Bash shell examples for Linux users, especially for commands involving file creation, editing, and environment variable management.
- Include notes or examples for setting environment variables in both Windows (set/PowerShell) and Linux (export/Bash) environments.
- Clarify that the Azure CLI commands work cross-platform and provide any Linux-specific installation or usage notes where relevant.
- Where file paths or file operations are mentioned (e.g., creating authsettings.json), provide both Windows and Linux command-line examples (e.g., using echo/cat/touch).
- If referencing the Azure CLI, briefly mention that it is available on Windows, Linux, and macOS, and link to platform-specific installation guides.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-assess-net.md
...ticles/app-service/app-service-migration-assess-net.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page discusses assessing .NET web apps for migration to Azure App Service but implicitly assumes a Windows environment by referencing ASP.NET (commonly associated with Windows/IIS) and does not mention Linux-based .NET app scenarios or provide Linux-specific guidance or examples. There are no references to Linux tools, patterns, or cross-platform considerations, and all linked resources appear to focus on traditional Windows-based ASP.NET applications.
Recommendations
- Explicitly mention support for .NET Core/.NET 5+ web apps running on Linux, and clarify if the assessment process applies equally to Linux-hosted apps.
- Include examples or references for assessing .NET apps deployed on Linux (e.g., using Kestrel, Nginx, Apache).
- Add documentation links or sections addressing migration and assessment of Linux-hosted .NET web apps.
- Clarify any differences in assessment or migration steps between Windows and Linux environments.
- Ensure parity in tool recommendations and instructions for both Windows and Linux users.
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
Windows First
Missing Linux Example
Summary
The documentation page presents Windows container SSH access first and describes it as requiring no modifications, while Linux custom containers require additional steps and configuration. The Windows section lacks command-line or PowerShell examples, but the Linux section provides detailed Azure CLI and SSH command-line instructions. There are no PowerShell or Windows CLI examples for Windows containers, and the Linux section is more comprehensive in terms of actionable steps. However, the ordering and initial focus on Windows, as well as the lack of parity in example depth, indicate a mild 'windows_first' and 'missing_linux_example' bias.
Recommendations
- Provide equivalent command-line or PowerShell instructions for connecting to Windows containers, if supported, or clearly state the limitations.
- Ensure that both Windows and Linux sections have similar depth and actionable steps, or explain why certain features are only available on one platform.
- Consider presenting Linux and Windows instructions in parallel or in a more balanced order to avoid the perception of platform preference.
- If browser-based SSH is the only option for Windows containers, explicitly state this and provide troubleshooting or advanced usage tips similar to those given for Linux.
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 single example for clearing the DNS cache, specifically referencing the Windows command 'ipconfig /flushdns', without mentioning equivalent commands for Linux or macOS. No PowerShell scripts or Windows-specific tools are otherwise present, but the troubleshooting section assumes a Windows environment by default.
Recommendations
- When mentioning 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 all troubleshooting steps and ensure that platform-agnostic or cross-platform guidance is provided wherever possible.
- If automation or scripting is discussed, provide both PowerShell (Windows) and Bash (Linux/macOS) examples.
- Explicitly state when a step or tool is platform-specific, and offer alternatives for other platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/integrate-with-application-gateway.md
...vice/environment/integrate-with-application-gateway.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides step-by-step instructions for integrating an ILB App Service Environment with Azure Application Gateway, but it exhibits subtle Windows bias. Specifically, when validating DNS resolution, the only example shown is from a 'command prompt', which implies Windows usage. There are no explicit Linux or cross-platform CLI examples (e.g., using dig or nslookup on Linux/macOS), and no mention of Linux tools or terminal usage. The documentation also references the Azure portal and GUI workflows exclusively, which are platform-agnostic but may implicitly favor Windows users who are more accustomed to GUI-based workflows.
Recommendations
- Include explicit Linux/macOS command-line examples for DNS validation (e.g., show both Windows 'nslookup' and Linux 'dig' or 'nslookup' commands).
- When referencing 'command prompt', clarify that the steps apply to both Windows Command Prompt and Linux/macOS terminal, or provide parallel instructions.
- Add Azure CLI or PowerShell command examples for key steps (where possible), and ensure both Windows and Linux CLI usage is covered.
- Use neutral language such as 'terminal' or 'shell' instead of 'command prompt' to avoid implying a Windows-only environment.
- Consider including a section or callout for Linux users, highlighting any differences or additional steps relevant to non-Windows platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/networking.md
...ob/main/articles/app-service/environment/networking.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references both Windows and Linux support in App Service Environment, but provides detailed example calculations and operational notes only for Windows Containers. There are no equivalent examples or subnet sizing guidance for Linux Containers. Additionally, Windows-specific SKUs and behaviors are mentioned first or exclusively in several places, while Linux equivalents are not discussed.
Recommendations
- Add equivalent example calculations and subnet sizing guidance for Linux Containers, including any differences in IP address usage or scaling behavior.
- When mentioning Windows-specific SKUs or behaviors (e.g., I1v2 Windows), also mention Linux SKUs or note if there are no differences.
- Provide parity in operational notes and caveats for both Windows and Linux container scenarios.
- Ensure that any platform-specific requirements or exceptions are clearly labeled as such, and that Linux users are not left to infer their requirements from Windows examples.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-python-pivot.md
...ent-apps/deploy-intelligent-apps-linux-python-pivot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias by referencing Windows first in the sample app quickstart link (with 'tabs=flask,windows,azure-cli,...') and not providing explicit Linux-specific or cross-platform deployment instructions. There are no PowerShell-specific commands or Windows-only tools, but the absence of Linux/macOS terminal examples or explicit parity in setup steps may disadvantage Linux users.
Recommendations
- Ensure that all quickstart and setup links include Linux/macOS tabs or examples alongside Windows, or default to cross-platform instructions.
- Explicitly mention that all CLI commands (such as 'pip install', environment variable setup, etc.) work on Linux/macOS, and provide any necessary differences (e.g., environment variable syntax).
- Add a section or note clarifying how to perform environment variable configuration and deployment from Linux/macOS terminals, not just via the Azure portal.
- Wherever possible, use cross-platform language and avoid implying Windows as the default environment.
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
Missing Linux Example
Windows First
Summary
The documentation provides instructions using the Azure portal UI, which is platform-agnostic, but does not mention or provide examples for enabling streaming logs via command-line tools commonly used on Linux (such as Azure CLI or Bash scripts). There is an implicit Windows-first bias as the absence of CLI examples can disadvantage Linux users who may prefer or require non-GUI methods.
Recommendations
- Add equivalent instructions for enabling streaming logs using the Azure CLI (az webapp log config) with example commands.
- Include Bash script examples for automating the process, if applicable.
- Explicitly mention that the steps apply to both Windows and Linux App Service plans, or clarify any differences.
- Provide links to relevant documentation for both Windows and Linux users.
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 deployment examples for multiple languages and frameworks, with most workflows running on Ubuntu (Linux) runners. However, the ASP.NET (classic) example is the only one that uses a Windows runner and Windows-specific tools (NuGet, MSBuild), and it is presented before the Java, Node.js, and Python examples, which all use Linux runners. There is no Linux-based alternative provided for ASP.NET, and the documentation does not clarify that ASP.NET Core can be built and deployed cross-platform, while classic ASP.NET is Windows-only.
Recommendations
- Explicitly state that classic ASP.NET requires Windows runners due to framework limitations, and clarify that ASP.NET Core is cross-platform.
- If possible, provide guidance or links for porting classic ASP.NET apps to .NET Core to enable Linux-based CI/CD.
- Consider reordering the examples or grouping them by platform requirements, so that Linux-first examples are not visually deprioritized.
- For each example, add a note on why a particular runner (windows-latest or ubuntu-latest) is used, making platform dependencies explicit.
- Where Windows-specific tools are used (NuGet, MSBuild), clarify their necessity and provide Linux alternatives or explanations if none exist.
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-centric workflow by referencing the Azure Tools extension for VS Code without mentioning platform differences or providing Linux-specific guidance. There are no examples or notes about using the extension on Linux, nor are alternative Linux-native tools or command-line options discussed.
Recommendations
- Explicitly state that the Azure Tools extension for VS Code is cross-platform and works on Windows, Linux, and macOS.
- Include screenshots or notes indicating any platform-specific differences in the UI or installation process.
- Provide alternative instructions or references for users who prefer command-line tools (e.g., Azure CLI) on Linux.
- Mention any prerequisites or troubleshooting steps that may be relevant for Linux users (such as dependencies or permissions).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/deploy-zip-file.md
...-service/includes/quickstart-python/deploy-zip-file.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows instructions and tools (7-Zip) before Linux/macOS equivalents and specifically recommends a third-party Windows tool while using built-in utilities for Linux/macOS. However, both platforms are covered in parallel for most steps, and CLI/cURL examples are cross-platform.
Recommendations
- Present macOS/Linux and Windows instructions in parallel or in alphabetical order to avoid implicit prioritization.
- For creating ZIP files, mention built-in Windows options (such as right-click > Send to > Compressed (zipped) folder) before or alongside third-party tools like 7-Zip.
- Explicitly note that the Azure CLI and cURL commands are cross-platform, and provide any necessary platform-specific flags or considerations.
- Ensure screenshots and instructions for credential retrieval and other portal actions are not overly Windows-centric (e.g., avoid Windows-only UI references or terminology).
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 only describes enabling streaming logs using the Azure Tools for VS Code extension, which is a GUI tool commonly associated with Windows environments. There are no examples or instructions for enabling streaming logs via command-line tools or methods commonly used on Linux systems.
Recommendations
- Add instructions for enabling streaming logs using the Azure CLI, which is cross-platform and widely used on Linux.
- Provide examples for enabling streaming logs via the Azure Portal, which is platform-agnostic.
- Explicitly mention that the VS Code extension is available on multiple platforms, if applicable, or clarify any platform limitations.
- Include screenshots or command snippets for both Windows and Linux environments to ensure parity.
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 Tools
Missing Linux Example
Summary
The documentation describes deleting a resource group using a right-click context menu, which is a GUI pattern most commonly associated with Windows environments. There is no mention of equivalent command-line methods (such as Azure CLI or PowerShell), nor are Linux or cross-platform approaches provided.
Recommendations
- Include instructions for deleting a resource group using the Azure CLI (az group delete), which works across Windows, Linux, and macOS.
- If referencing GUI actions, clarify that the instructions apply to the Azure Portal (web-based) rather than a Windows-specific application.
- Provide PowerShell and Bash examples for users who prefer command-line interfaces.
- Ensure that all examples and instructions are platform-neutral or provide parity between Windows and Linux where possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-connect-msi-azure-database/code-sql-mi.md
...des/tutorial-connect-msi-azure-database/code-sql-mi.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation consistently uses Microsoft SQL Server client libraries and ODBC drivers (e.g., 'ODBC Driver 18 for SQL Server') that are traditionally associated with Windows environments. There is no mention of Linux-specific drivers, installation instructions, or troubleshooting for Linux environments. The documentation does not provide guidance for Linux users regarding driver installation, environment variable setup, or potential cross-platform issues.
Recommendations
- Explicitly mention that the ODBC Driver 18 for SQL Server is available for Linux and provide installation instructions for common Linux distributions (e.g., apt-get/yum commands).
- Include troubleshooting tips or notes for Linux users, such as driver path issues or required dependencies.
- Clarify that the code samples are cross-platform, or provide any necessary adjustments for Linux environments (e.g., case sensitivity, environment variable conventions).
- Reference official Microsoft documentation for installing SQL Server drivers on Linux.
- If any features or authentication methods are Windows-only, clearly state this and suggest alternatives for Linux where possible.
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 explanatory note is specific to PowerShell and appears before the PowerShell code block. There is no equivalent Linux-specific guidance or troubleshooting note, and the instructions for accessing Kudu are written in a way that assumes familiarity with the Azure Portal GUI, which is more commonly used on Windows.
Recommendations
- Add Linux-specific notes or troubleshooting tips, such as handling authentication or file permissions in Bash.
- Provide CLI-based instructions for accessing the Kudu environment (e.g., using Azure CLI), not just through the Azure Portal GUI.
- Ensure that explanatory notes are balanced between platforms, not only highlighting PowerShell-specific issues.
- Consider reordering or parallelizing the presentation so that Bash and PowerShell examples and notes are given equal prominence.
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
Missing Linux Example
Windows First
Summary
The documentation provides step-by-step instructions that implicitly assume a graphical user interface (GUI) similar to Windows, without clarifying if the steps are applicable to Linux environments or providing alternative instructions for Linux users. There is no mention of Linux-specific tools, terminal commands, or differences in workflow, which may leave Linux users uncertain about how to proceed.
Recommendations
- Clarify whether the instructions apply to both Windows and Linux environments, especially if the Azure Portal UI is identical across platforms.
- If there are differences for Linux users (such as CLI alternatives or different navigation), provide equivalent Linux instructions or command-line examples.
- Explicitly mention that the steps are performed in the Azure Portal, which is web-based and cross-platform, to reassure non-Windows users.
- Include links or references to Linux command-line deployment options (e.g., using Azure CLI or Git on Linux) for users who prefer or require non-GUI workflows.
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 in the Azure portal without referencing any platform-specific tools. However, it implicitly assumes a GUI workflow common to Windows users and does not mention or provide examples for Linux command-line alternatives (e.g., using Azure CLI or Bash scripting), which may be preferred by Linux users.
Recommendations
- Add equivalent instructions for configuring application settings using the Azure CLI, which is cross-platform and commonly used on Linux.
- Provide Bash script examples for automating configuration changes.
- Explicitly mention that the Azure portal steps are platform-agnostic, but offer links or references to command-line alternatives for Linux users.
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 First
Summary
The documentation provides generic instructions for deploying code using Git credentials but does not include any platform-specific examples. However, it implicitly assumes a Windows-centric workflow by omitting Linux-specific guidance, such as command-line examples for Git operations or FTPS usage on Linux. There is also no mention of Linux tools or terminal commands, which may leave Linux users without clear instructions.
Recommendations
- Add explicit Linux command-line examples for pushing code to the remote Git repository (e.g., using git push from a Linux terminal).
- Include FTPS client usage examples for Linux (e.g., lftp, curl, or FileZilla on Linux).
- Ensure that instructions and screenshots, if any, are not Windows-specific, or provide Linux equivalents.
- Clearly state that the process is cross-platform and provide parity in examples for both Windows and Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-python-postgresql-app/deploy-zip-azure-portal-1.md
...ial-python-postgresql-app/deploy-zip-azure-portal-1.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references the Azure portal UI, which is a cross-platform web interface, but does not provide any command-line examples. There is no mention of Linux-native tools (such as Azure CLI in Bash) or command-line alternatives, which may disadvantage Linux users who prefer or require CLI workflows.
Recommendations
- Add equivalent instructions using the Azure CLI (az webapp config appsettings set ...) with examples in Bash.
- Explicitly mention that the Azure portal is platform-agnostic, but provide links or examples for both Windows (PowerShell) and Linux (Bash) command-line workflows.
- Ensure future documentation includes parity between GUI and CLI instructions, catering to both Windows and Linux users.
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
Missing Linux Example
Windows First
Summary
The documentation references copying the Git Clone Uri but does not provide any example commands or workflows for setting up a Git remote. There are no explicit Windows-only tools or commands, but the absence of any Linux-specific instructions or parity examples (such as Linux shell commands) suggests a potential bias by omission. The documentation assumes a generic workflow but does not ensure Linux users are equally supported.
Recommendations
- Add explicit example commands for setting up a Git remote on both Windows (e.g., PowerShell or Command Prompt) and Linux (e.g., Bash).
- If referencing any tools or commands in future steps, ensure both Windows and Linux equivalents are provided side-by-side.
- Clarify that the instructions are platform-agnostic, or specify any platform-specific steps where necessary.
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
Missing Linux Example
Windows Tools
Summary
The documentation only describes enabling application logging via the Azure Portal UI, which is primarily a Windows-centric workflow. There are no examples or instructions for enabling logging using Linux-native tools, command-line interfaces, or configuration files, which are common in Linux environments.
Recommendations
- Add instructions for enabling application logging using the Azure CLI and/or Azure PowerShell, making sure to include both Bash and PowerShell examples.
- Provide guidance for configuring logging in Linux-based App Service environments, such as using configuration files or environment variables.
- Explicitly mention any differences in logging behavior or setup between Windows and Linux App Service plans.
- Include screenshots or terminal commands relevant to Linux users where appropriate.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-apple.md
...app-service/configure-authentication-provider-apple.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides only a C# example using the Microsoft.IdentityModel.Tokens NuGet package for generating the client secret JWT, which is a Windows/.NET-centric approach. There are no examples or references for generating the JWT using common Linux tools (such as OpenSSL, Python, or Node.js), nor are cross-platform command-line instructions provided. The documentation implicitly assumes a Windows/.NET development environment.
Recommendations
- Add examples for generating the client secret JWT using cross-platform tools such as OpenSSL, Python (e.g., PyJWT), or Node.js (e.g., jsonwebtoken).
- Include command-line instructions that work on Linux/macOS as well as Windows.
- Reference open-source, platform-agnostic libraries for JWT creation and signing.
- Explicitly mention that the process can be completed on any OS and provide links or code samples for non-Windows environments.
- Consider reordering or supplementing the C#/.NET example with a Linux-first or cross-platform example to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-key-vault-references.md
...ticles/app-service/app-service-key-vault-references.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring Key Vault references, but PowerShell examples are consistently presented immediately after the CLI, and no Linux shell-specific (e.g., Bash) or cross-platform scripting examples are given. The use of PowerShell, which is traditionally associated with Windows, may create a perception of Windows bias, especially as Linux users may expect Bash or shell script examples. However, the CLI examples are cross-platform, which mitigates some of the bias.
Recommendations
- Explicitly note that Azure CLI commands are cross-platform and suitable for Linux, macOS, and Windows.
- Where PowerShell is shown, consider also providing Bash or shell script equivalents for Linux users, especially for scripting scenarios involving variables or more complex logic.
- In tabbed code blocks, consider listing Bash or Azure CLI first (or clarify that CLI is cross-platform), and PowerShell second, to avoid the impression of Windows-first bias.
- Add a brief section or note clarifying that all management operations can be performed from Linux environments using the Azure CLI.
- If there are any platform-specific caveats (e.g., for Linux App Service), highlight them clearly and provide Linux-specific troubleshooting steps or examples where relevant.