Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1451-1475 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/how-to-deploy-self-hosted-gateway-container-apps.md
...nt/how-to-deploy-self-hosted-gateway-container-apps.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell is always presented second, and there is no explicit mention of Linux or macOS environments. The use of PowerShell tabs and syntax may implicitly favor Windows users, and there are no Linux-specific troubleshooting tips or references to Linux tools. However, the CLI commands themselves are cross-platform, and Bash examples are present throughout.
Recommendations
- Explicitly mention that all CLI commands work on Linux, macOS, and Windows, and that Bash examples are suitable for Linux/macOS users.
- Consider presenting Bash (Linux/macOS) examples first, or clarify that Bash is the default for non-Windows platforms.
- Add a note or section about running Azure CLI in native Linux/macOS terminals, including any prerequisites or differences (e.g., installation, authentication).
- Include troubleshooting tips or references for common Linux/macOS issues (e.g., permissions, environment variables).
- Where PowerShell is referenced, clarify that it is primarily for Windows users, and that Bash is recommended for Linux/macOS.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/grpc-api.md
...re-docs/blob/main//articles/api-management/grpc-api.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page does not provide any OS-specific command-line examples, but in the section 'Call gRPC services with .NET', it only references .NET-based tutorials, which are most commonly associated with Windows environments. There are no examples or references for Linux or cross-platform command-line tools (such as grpcurl or grpc_cli), nor are there instructions for calling gRPC services from non-Windows environments. Additionally, the absence of Linux/macOS-specific guidance or parity in example tooling may lead to a perception of Windows/.NET bias.
Recommendations
- Add examples or references for calling gRPC services using cross-platform tools such as grpcurl or grpc_cli, which are commonly used on Linux and macOS.
- Include instructions or links for using gRPC in other popular languages and environments (e.g., Python, Go, Java) to demonstrate cross-platform support.
- Explicitly mention that the steps are platform-agnostic where applicable, or provide OS-specific notes if there are differences.
- If referencing .NET, also provide equivalent examples or links for Linux/macOS users, such as using .NET Core on Linux or alternative clients.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/deployment-environments/how-to-configure-managed-identity.md
...ment-environments/how-to-configure-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all configuration steps and does not provide any command-line examples. There are no references to Windows-specific tools like PowerShell, but the absence of CLI (az CLI, Bash, etc.) instructions means Linux and cross-platform users are not equally supported. The documentation implicitly assumes a GUI-first workflow, which is more common in Windows environments.
Recommendations
- Add equivalent step-by-step instructions using the Azure CLI (az) for all major tasks, such as assigning managed identities and roles.
- Include CLI examples in Bash syntax to ensure Linux and macOS users can follow along without relying on the Azure portal.
- Where possible, provide PowerShell and Bash/az CLI code snippets side-by-side to demonstrate parity.
- Explicitly state that all tasks can be performed via CLI and provide links to relevant CLI documentation.
- Consider including automation scripts or templates (e.g., ARM, Bicep, Terraform) for advanced users on any platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/deployment-environments/includes/custom-image-manual-build.md
...ent-environments/includes/custom-image-manual-build.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation links to Docker Desktop, which is primarily a Windows and Mac tool, rather than referencing Docker Engine installation instructions for Linux. There are no Linux-specific instructions or examples, and the installation link may mislead Linux users.
Recommendations
- Provide a link to Docker Engine installation instructions for Linux (e.g., https://docs.docker.com/engine/install/).
- Clarify that Docker Desktop is for Windows and Mac, and provide equivalent guidance for Linux users.
- Include a note or section for Linux users to ensure parity and inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/concept-dev-box-concepts.md
...lob/main//articles/dev-box/concept-dev-box-concepts.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page for Microsoft Dev Box primarily references Windows environments, notably stating that Dev Box supports only client editions of Windows 10 and Windows 11. There are no examples, mentions, or guidance for Linux-based development environments, tools, or workflows. The documentation implicitly assumes a Windows-centric development model, omitting Linux alternatives or parity.
Recommendations
- Explicitly state whether Linux-based dev boxes are supported or planned, and provide guidance for Linux users if available.
- If Linux support is not available, clarify this limitation early in the documentation to set expectations for cross-platform developers.
- If Linux support is available or planned, add equivalent examples, workflows, and references for Linux environments (e.g., using Ubuntu images, Linux-based tooling, shell scripts).
- Include a comparison table or section outlining OS support and feature parity between Windows and Linux dev boxes.
- Mention cross-platform considerations for development teams that use both Windows and Linux, and provide links to relevant resources.
Azure Docs
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 for most steps. However, in the troubleshooting section ('Test the DNS resolution'), only a Windows-specific command ('ipconfig /flushdns') is provided for clearing the DNS cache, with no equivalent instructions for Linux or macOS users. This constitutes a 'windows_first' and 'missing_linux_example' bias.
Recommendations
- When providing troubleshooting steps that involve OS-specific commands (such as clearing the DNS cache), include equivalent 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').
- Consider using language such as 'On Windows...' and 'On Linux...' to make it clear that instructions are platform-specific, and provide parity for all major platforms.
- Review the documentation for any other subtle Windows-first assumptions, and ensure that all users, regardless of OS, have the information they need to succeed.
Azure Docs
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 provides both PowerShell and Azure CLI examples, but consistently presents PowerShell (a Windows-centric tool) before Azure CLI (which is cross-platform and more common on Linux/macOS). There are no explicit Linux shell (bash) or scripting examples, and no mention of Linux-specific tools or workflows. The PowerShell examples are detailed and prominent, which may signal a preference for Windows environments.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash-specific usage notes if relevant.
- Where possible, add bash script equivalents or highlight usage in a Linux shell environment.
- Consider adding a section or callout for Linux users, clarifying any OS-specific prerequisites or differences.
- Avoid assuming Visual Studio (a Windows tool) as the default development environment; mention cross-platform alternatives like VS Code.
Azure Docs
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 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). This omission may disadvantage Linux users who prefer or require non-GUI methods.
Recommendations
- Add equivalent instructions for enabling streaming logs using the Azure CLI, including example commands.
- Explicitly mention that the steps apply regardless of the underlying OS, or clarify any differences for Linux-based App Service plans.
- Provide Bash shell examples alongside any PowerShell or Windows-specific instructions if added in the future.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/protect-with-ddos-protection.md
...rticles/api-management/protect-with-ddos-protection.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by referencing only the Azure Portal (a GUI tool commonly used on Windows) and linking to a PowerShell-based guide for enabling DDoS IP Protection. There are no CLI (az CLI), Bash, or Linux-native instructions or examples provided for enabling or managing DDoS Protection, which may disadvantage Linux or cross-platform users.
Recommendations
- Add equivalent instructions using Azure CLI (az CLI), which is cross-platform and commonly used on Linux and macOS.
- Provide Bash script examples for automation scenarios.
- When referencing PowerShell-based guides, also link to or include steps for az CLI or REST API.
- Clarify that the Azure Portal is web-based and accessible from any OS, but supplement with command-line alternatives for parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/private-endpoint.md
...blob/main//articles/api-management/private-endpoint.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a web UI that is platform-agnostic but often associated with Windows workflows) and the Azure CLI, but does not provide any explicit PowerShell or Windows-only command-line examples. However, it also does not provide any Linux-specific instructions or examples, such as using bash scripting, Linux-native tools, or screenshots from Linux environments. The only command-line example is an Azure CLI command, which is cross-platform, but there is no mention of Linux shell usage or parity checks. The DNS validation step suggests using 'nslookup' or 'dig', which are available on both Windows and Linux, but no explicit Linux context or examples are provided. There are no references to Windows-only tools, but the documentation implicitly assumes a Windows-centric workflow by not acknowledging Linux environments or providing Linux-specific guidance.
Recommendations
- Include explicit Linux shell (bash) examples for Azure CLI commands, showing both Windows (cmd/PowerShell) and Linux (bash) syntax where differences exist.
- Add Linux-specific instructions or notes for steps such as DNS validation, e.g., using 'dig' or 'host' on Linux, and clarify installation if needed.
- Provide screenshots or terminal output examples from both Windows and Linux environments to demonstrate parity.
- Where the Azure portal is referenced, clarify that it is platform-agnostic and accessible from any OS.
- If PowerShell examples are added in the future, ensure equivalent bash/Linux examples are also provided.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/set-backend-service-policy.md
.../articles/api-management/set-backend-service-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Windows-specific tools (PowerShell) for backend management and omits equivalent Linux/CLI instructions. No Linux or cross-platform command-line examples are provided, and the only tool explicitly mentioned for scripting is PowerShell.
Recommendations
- Add Azure CLI examples for managing backend entities, as Azure CLI is cross-platform and widely used on Linux.
- Mention and provide links to Bash or shell scripting alternatives where PowerShell is referenced.
- Ensure that management instructions and automation examples are provided for both Windows (PowerShell) and Linux (Azure CLI/Bash) environments.
- Review all tool references to ensure parity and avoid implying that Windows tools are the primary or only option.
Azure Docs
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 references the Windows file path (C:\home\site\wwwroot) first and provides more detailed guidance for Windows users, while Linux-specific instructions are limited to a note about absolute paths. There are no Linux-specific examples or screenshots, and the primary example uses a Windows-style path.
Recommendations
- Provide both Windows and Linux file path examples side by side when referencing file locations (e.g., 'C:\home\site\wwwroot\auth.json' for Windows and '/home/site/wwwroot/auth.json' for Linux).
- Include explicit Linux instructions and examples in the main steps, not just in a note.
- Add a table or section summarizing platform differences for configuration file paths.
- Consider including screenshots or command-line examples for both Windows and Linux environments.
- Avoid assuming Windows as the default by mentioning both platforms equally in all relevant sections.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/configure-authentication-provider-aad.md
...s/app-service/configure-authentication-provider-aad.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a 'Windows-first' bias by exclusively referencing the Azure portal UI and Azure-specific workflows without mentioning or providing parity for Linux command-line tools or cross-platform automation (e.g., Azure CLI, Bicep, ARM templates, or scripting via Bash). There are no examples or instructions for configuring authentication using Linux-native tools or environments. The documentation also lacks explicit Linux or cross-platform command-line examples, focusing entirely on portal-based, GUI-driven steps that are platform-agnostic in appearance but implicitly favor Windows users due to the Azure ecosystem's historical alignment with Windows.
Recommendations
- Add equivalent command-line instructions using Azure CLI (az), which is cross-platform and commonly used in Linux environments, for all major configuration steps (e.g., app registration, authentication provider setup, permission assignment).
- Include examples of automating configuration via ARM/Bicep templates or REST API calls, with sample Bash scripts for Linux users.
- Explicitly mention that all steps can be performed from any OS, and provide links or notes for Linux/macOS users where UI or tool differences may exist.
- Where application settings are referenced, show how to set them using CLI or scripting, not just through the Azure portal.
- Add a section or callout highlighting Linux/macOS developer workflows and tools for managing Microsoft Entra authentication in App Service/Azure Functions.
Azure Docs
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 without addressing platform differences or providing guidance for Linux users. It assumes familiarity with VS Code's interface, which may differ slightly across operating systems, and does not mention installation or troubleshooting steps specific to Linux.
Recommendations
- Include instructions or notes for installing and accessing the Azure Tools extension on Linux (and macOS), highlighting any platform-specific differences.
- Add screenshots or descriptions that clarify any UI differences on Linux.
- Mention how to verify extension installation from the command line, which is often preferred by Linux users.
- Ensure that troubleshooting steps cover all supported platforms, not just Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/includes/quickstart-python/remove-resource-group-azure-portal-2.md
...ckstart-python/remove-resource-group-azure-portal-2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation refers to a UI action ('Delete resource group' button) without specifying platform, but the phrasing and context suggest a Windows-centric approach. There is no mention of equivalent CLI commands or Linux-native workflows, which may leave Linux users without clear guidance.
Recommendations
- Include instructions for deleting a resource group using cross-platform CLI tools such as Azure CLI or Azure PowerShell.
- Provide explicit Linux shell command examples alongside any UI or Windows-specific instructions.
- Clarify that the instructions apply to all platforms if the UI is web-based, or specify platform differences if relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/resources-kudu.md
...docs/blob/main//articles/app-service/resources-kudu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page for Kudu service overview references Windows-specific tools and features (such as IIS diagnostic dumps, IIS processes, and deployment webhooks for Windows apps) without mentioning Linux equivalents or clarifying Linux support. There are no Linux-specific examples or references, and the documentation implicitly assumes a Windows environment in several feature descriptions.
Recommendations
- Explicitly mention Linux support where applicable, such as describing how Kudu interacts with Linux-based App Service plans.
- Provide examples or notes about Linux equivalents for features like diagnostic dumps and process management (e.g., how to access logs or manage processes on Linux-based App Service instances).
- Clarify which features are Windows-only and which are cross-platform, ideally grouping or labeling them accordingly.
- Add Linux-specific documentation links or references, such as how to use the Kudu console or REST API on Linux App Service.
- Ensure parity in feature descriptions and examples for both Windows and Linux environments.
Azure Docs
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 exclusively references the Azure portal UI, which is a web-based tool commonly associated with Windows-centric workflows. There are no examples or instructions for performing the same configuration using command-line tools (such as Azure CLI or Bash scripts), which are more commonly used in Linux environments. This omission may disadvantage Linux users or those who prefer CLI-based workflows.
Recommendations
- Add equivalent instructions for configuring application settings using the Azure CLI, with example commands.
- Include Bash shell examples alongside any PowerShell or portal-based instructions.
- Explicitly mention that the steps apply equally to both Windows and Linux-hosted web apps, or clarify any differences.
- Provide links to documentation for automating configuration via scripts for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/quickstart-custom-container.md
...n//articles/app-service/quickstart-custom-container.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents Windows-based pivots (including Visual Studio, PowerShell, and CLI) before their Linux equivalents, and includes a dedicated PowerShell section for Windows but not for Linux. This ordering and tooling emphasis may signal a Windows-centric bias.
Recommendations
- Reorder pivots or group Windows and Linux options together to avoid always presenting Windows first.
- Provide parity for Linux users by including Linux-specific command-line examples (e.g., Bash, shell scripts) where PowerShell is used for Windows.
- Ensure that Linux tools and workflows (such as common Linux editors or shell environments) are given equal prominence and are not only referenced after Windows tools.
- Explicitly state that both Windows and Linux are supported, and highlight any differences or similarities in workflows.
Azure Docs
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 platform-specific examples for multiple languages. However, in the ASP.NET section, the only example given runs on Windows ('runs-on: windows-latest') and uses Windows-specific tools such as MSBuild and NuGet, with Windows-style paths (e.g., '.\SampleWebApplication.sln'). There is no equivalent Linux-based example for ASP.NET, while all other language examples (ASP.NET Core, Java, Tomcat, Node.js, Python) use 'ubuntu-latest' and cross-platform tooling. This creates a Windows-first and Windows-tools bias for ASP.NET workloads.
Recommendations
- Add a Linux-based (e.g., 'runs-on: ubuntu-latest') example for ASP.NET, using cross-platform tools such as 'dotnet build' instead of MSBuild, and ensure paths use POSIX style.
- If MSBuild is required, clarify if and how it can be used on Linux (e.g., via Mono or .NET SDK), or provide guidance for cross-platform builds.
- For NuGet, show how to restore packages using the 'dotnet' CLI, which is cross-platform, instead of the Windows-only 'nuget' tool.
- Explicitly mention platform compatibility and provide parity in examples for both Windows and Linux where possible, especially for .NET workloads.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/includes/tutorial-php-mysql-app/azure-portal-get-connection-string-3.md
...-php-mysql-app/azure-portal-get-connection-string-3.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation instructs users to copy a connection string and paste it into a text file, implicitly assuming the use of a GUI and a text editor, which are more commonly associated with Windows workflows. There are no examples or instructions for Linux users, such as using terminal commands or Linux-native editors.
Recommendations
- Provide explicit instructions for both Windows and Linux users, such as how to copy the connection string using keyboard shortcuts or terminal commands.
- Include examples for saving the connection string using common Linux text editors (e.g., nano, vim) or command-line tools (e.g., echo, cat).
- Avoid assuming the presence of a GUI or default text editor; mention alternatives for headless or terminal-only environments.
- Clarify that the steps apply to all platforms, and offer platform-specific notes where workflows differ.
Azure Docs
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 terminology and navigation patterns that are familiar to Windows users (e.g., 'left toolbar', 'Settings' header), and does not provide any examples or guidance for Linux users or command-line alternatives. There is no mention of Linux tools or cross-platform CLI approaches.
Recommendations
- Include equivalent instructions using Azure CLI and/or Azure PowerShell, with explicit cross-platform notes.
- Add screenshots or descriptions that clarify the UI is the same across platforms, or highlight any differences for Linux/macOS users.
- Mention that the Azure portal is web-based and accessible from any OS, to avoid implying a Windows-only workflow.
- Provide links to documentation for configuring application settings via CLI or ARM templates for automation and Linux parity.
Azure Docs
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 platform-specific examples for multiple stacks. However, for the ASP.NET (classic) tab, only a Windows-based workflow is provided, using Windows-specific tools (NuGet, MSBuild) and the 'windows-latest' runner. There is no Linux alternative or guidance for building and deploying ASP.NET (classic) apps from Linux. All other stacks (ASP.NET Core, Java, Tomcat, Node.js, Python) use 'ubuntu-latest' runners and cross-platform tools, but the ASP.NET (classic) section is Windows-only and Windows-first.
Recommendations
- Add a Linux-based example for ASP.NET (classic) if possible, or explicitly state that only Windows runners are supported for this stack.
- If ASP.NET (classic) cannot be built on Linux, clarify this limitation in the documentation.
- Wherever possible, provide both Windows and Linux examples side by side for parity.
- Consider mentioning cross-platform alternatives to Windows tools (e.g., Mono for MSBuild, if feasible) or explain why they are not recommended.
- Ensure that the order of presentation does not always favor Windows-first; alternate or group by cross-platform compatibility.
Azure Docs
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 uses UI navigation patterns and terminology that are typical of Windows applications (e.g., 'menu on the left side', 'top menu bar'), and does not provide any guidance or examples for Linux users, such as command-line alternatives or references to Linux tooling.
Recommendations
- Include equivalent instructions for Linux users, such as how to perform these actions using the Azure CLI or other cross-platform tools.
- Avoid using UI navigation language that assumes a Windows-style interface; clarify if the instructions apply to both Windows and Linux environments.
- Provide screenshots or examples from both Windows and Linux perspectives if the UI differs.
- Mention any differences in workflow or available features between Windows and Linux App Service plans.
Azure Docs
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-specific tools (7-Zip) for creating ZIP files and lists Windows instructions before macOS/Linux equivalents. While Linux/macOS instructions are present, the Windows tool is mentioned by name and illustrated with a screenshot, whereas the Linux/macOS section only references the built-in 'zip' utility. There is no PowerShell-heavy content or missing Linux examples, but the ordering and tool emphasis show a mild Windows bias.
Recommendations
- Present platform instructions in parallel or in a neutral order (e.g., list macOS/Linux first sometimes, or group all OSes together).
- For Windows, mention both built-in options (e.g., right-click 'Send to > Compressed (zipped) folder') and third-party tools like 7-Zip, to avoid implying 7-Zip is required.
- For Linux/macOS, consider including a screenshot or more detailed instructions, similar to the Windows section, to ensure parity.
- Explicitly state that the Azure CLI and cURL commands work cross-platform, and provide any OS-specific notes if needed.
- Where possible, use language that does not prioritize one OS over others (e.g., 'On Windows, macOS, or Linux, you can create a ZIP file using...').
Azure Docs
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 and actions in the Azure portal using terminology and UI patterns that are familiar to Windows users, with no mention of Linux command-line alternatives or cross-platform CLI/automation options. There are no examples or instructions for performing the same configuration using Linux tools or the Azure CLI.
Recommendations
- Add equivalent instructions for configuring application settings using the Azure CLI, which is cross-platform.
- Include examples of how to perform the same task using PowerShell (if relevant) and Bash, highlighting cross-platform compatibility.
- Explicitly mention that the Azure portal is accessible from any OS, and provide links to CLI documentation for users who prefer terminal-based workflows.