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 976-1000 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/includes/email-resource-management-azurecli-powershell.md
...ludes/email-resource-management-azurecli-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily biased toward Windows and PowerShell. All code samples are written in PowerShell, and the instructions assume the use of PowerShell as the scripting environment. Prerequisite installation links and checks are Windows-specific, and there are no Bash or Linux shell equivalents provided. This makes it difficult for Linux or macOS users to follow the guide without significant adaptation.
Recommendations
- Provide equivalent Bash shell scripts for all PowerShell code samples, using standard Bash syntax and tools (e.g., variable assignment, loops, error handling).
- Include installation instructions and prerequisite checks for Azure CLI and PowerShell on Linux and macOS, not just Windows.
- When referencing command-line tools, clarify cross-platform compatibility and provide links to Linux/macOS installation guides.
- Consider using the Azure CLI directly in examples, as it is cross-platform, and avoid wrapping all commands in PowerShell unless necessary.
- Add a section or callouts for Linux/macOS users, highlighting any differences or additional steps required.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/email-resource-management.md
...nication-services/samples/email-resource-management.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell commands for resource cleanup without equivalent Bash or Linux shell examples. PowerShell is featured prominently, and there are no explicit Linux or cross-platform command-line instructions for deleting resources, especially for Email and Domain resources. The structure and included examples prioritize Windows tooling and workflows.
Recommendations
- Provide Bash/Azure CLI examples for all resource cleanup steps, not just for Communication Services but also for Email and Domain resources.
- Ensure that for every PowerShell command, there is a corresponding Azure CLI or Bash command that can be run on Linux/macOS.
- Reorganize the documentation so that cross-platform (CLI) examples are presented before or alongside PowerShell examples, rather than after.
- Clearly indicate which commands are platform-specific and offer guidance for users on Linux/macOS.
- Consider adding a table or section summarizing all available commands by platform (PowerShell, Azure CLI, Bash) for easy reference.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/includes/email-resource-management-powershell.md
...mples/includes/email-resource-management-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All examples and automation scripts are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or cross-platform alternatives. The prerequisites and instructions assume a Windows environment (e.g., checking PowerShell installation via 'powershell -command'), and only Windows/PowerShell tools and cmdlets are referenced throughout. There is no guidance for Linux or macOS users, nor any indication that the steps can be performed using other tools or shells.
Recommendations
- Add equivalent Azure CLI (az) examples for all major steps, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Explicitly mention that Azure PowerShell can be installed and used on Linux and macOS, and provide installation instructions or links for those platforms.
- Provide Bash shell script examples or at least command-line equivalents for common tasks (e.g., authentication, resource creation, DNS record management).
- In the prerequisites, include instructions for checking/installing PowerShell Core (pwsh) on Linux/macOS, or suggest Azure CLI as an alternative.
- Clearly state at the beginning that the guide is PowerShell-focused, and offer links to cross-platform or Linux/macOS-specific documentation if available.
- Where possible, use neutral language (e.g., 'terminal' instead of 'command prompt'), and avoid assuming a Windows environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/includes/ui-maui.md
...les/communication-services/samples/includes/ui-maui.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tooling and workflows. For Android, it references Visual Studio on Mac/Windows and specifically mentions the need for GitBash or Windows Subsystem for Linux (WSL) to run shell scripts on Windows, but does not provide explicit instructions for running the sample on native Linux environments. There are no Linux-specific instructions or parity for Linux users, and the documentation assumes Visual Studio as the primary IDE, which is not natively available on Linux.
Recommendations
- Add explicit instructions for running the sample on native Linux environments, including supported IDEs (such as VS Code) and command-line steps.
- Provide Linux-specific prerequisites, such as required packages or dependencies.
- Include examples of running shell scripts on Linux, not just via WSL or GitBash on Windows.
- Clarify which steps are cross-platform and which are Windows- or Mac-specific.
- Mention alternative tools or workflows for Linux users where Visual Studio is not available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/email-detect-sensitive-content.md
...ion-services/samples/email-detect-sensitive-content.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by referencing Windows-specific tools and patterns before cross-platform or Linux alternatives. For example, the .NET installation check uses a Windows registry query, and console examples mention 'cmd' and 'PowerShell' before 'Bash'. There are no Linux-specific instructions or examples for verifying .NET installation or environment setup, and no explicit Linux/macOS guidance is provided for environment variables or terminal usage.
Recommendations
- Provide equivalent Linux/macOS commands for checking .NET installation (e.g., 'dotnet --list-sdks' or 'which dotnet').
- List 'Bash' or 'terminal' before or alongside 'cmd' and 'PowerShell' when referencing console windows.
- Include explicit instructions for setting environment variables on Linux/macOS (e.g., 'export LANGUAGE_KEY=...').
- Ensure screenshots and navigation steps are not Windows-centric, or clarify that the Azure Portal UI is cross-platform.
- Wherever possible, use cross-platform language and avoid Windows-specific terminology unless necessary.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/chat-app-teams-embed.md
...mmunication-services/tutorials/chat-app-teams-embed.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Microsoft-centric tools and workflows (e.g., Visual Studio Code, Microsoft Teams Toolkit, Azure Functions) without mentioning or providing guidance for Linux or cross-platform development environments. There are no examples or instructions for Linux users, and all tool recommendations and screenshots are based on Windows-centric tooling.
Recommendations
- Include explicit instructions or notes for Linux and macOS users, such as how to install and use the Teams Toolkit and Azure Functions on those platforms.
- Provide terminal/command-line examples that work on Linux (e.g., using bash instead of only referencing Visual Studio Code UI).
- Mention alternative editors (e.g., VS Code on Linux, or other editors) and clarify that the toolkit is cross-platform where applicable.
- Add screenshots or descriptions that reflect Linux environments where possible.
- Ensure that any references to deployment, local testing, or backend setup include steps or caveats for Linux users (e.g., running Azure Functions locally on Linux).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/includes/twilio-to-acs-chat-csharp-tutorial.md
...torials/includes/twilio-to-acs-chat-csharp-tutorial.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the prerequisites and setup sections. It instructs users to install Visual Studio (a Windows-centric IDE) and provides only PowerShell/dotnet CLI commands for package installation, without mentioning or demonstrating Linux-friendly alternatives (such as VS Code, Linux package managers, or Bash commands). There are no explicit Linux or cross-platform setup instructions, and no mention of Linux-specific considerations or tools.
Recommendations
- Include installation instructions for Linux and macOS users, such as using VS Code or JetBrains Rider as alternatives to Visual Studio.
- Provide package installation examples using Bash (e.g., 'dotnet add package ...' in a Bash shell) and clarify that the .NET CLI works cross-platform.
- Mention that Azure CLI and .NET SDK are available on Linux/macOS, and provide links or notes for installing them on those platforms.
- Add a note clarifying that all code samples are platform-agnostic, and explicitly state any platform-specific requirements or differences.
- Where PowerShell is used, provide equivalent Bash commands or clarify that the command can be run in any terminal with the .NET CLI installed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/building-app-start.md
...communication-services/tutorials/building-app-start.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing setup instructions and examples primarily for Windows users. It references Windows-specific tools and paths (e.g., PowerShell commands, C:\ paths), and links to Windows-focused setup guides. There are no equivalent instructions or examples for Linux or macOS users, and the workflow assumes familiarity with Windows conventions.
Recommendations
- Provide parallel setup instructions for Linux and macOS, including terminal commands for nvm and Node.js installation on those platforms.
- Include example shell commands (bash/zsh) alongside PowerShell commands, and clarify which commands are cross-platform.
- Use platform-agnostic file paths in examples, or provide both Windows (C:\Users\...) and Unix-style (~/ or /home/user/...) paths.
- Link to official nvm and Node.js installation guides for Linux and macOS, not just Windows.
- Mention that Visual Studio Code and the Azure extensions are available on all major platforms, and provide any platform-specific installation tips.
- Ensure screenshots and instructions for deploying or running commands in the terminal are not exclusively Windows-focused.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/includes/twilio-to-acs-video-webjs-tutorial.md
...torials/includes/twilio-to-acs-video-webjs-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias primarily in the prerequisites and resource management sections. It references Windows-specific instructions and links (e.g., 'Install Azure CLI on Windows', resource creation/cleanup with '?tabs=windows'), and omits equivalent Linux/macOS guidance. There are no PowerShell-heavy examples, but Linux and macOS users are not provided parity in setup or cleanup instructions.
Recommendations
- Provide platform-agnostic or multi-platform instructions for installing Azure CLI, including links for Linux and macOS.
- When referencing resource creation or cleanup, avoid using Windows-specific query parameters (e.g., '?tabs=windows') or provide equivalent Linux/macOS tabs.
- Explicitly mention that all code examples (npm, JavaScript, etc.) are cross-platform unless otherwise noted.
- Add a note or section clarifying any platform-specific differences or requirements, especially for setup steps.
- Ensure all quickstart and how-to links either default to a neutral platform or offer clear tabs for Windows, Linux, and macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/includes/twilio-to-acs-chat-android-tutorial.md
...orials/includes/twilio-to-acs-chat-android-tutorial.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by requiring Visual Studio (a Windows-centric IDE) as a prerequisite, providing only PowerShell examples for package installation, and omitting any Linux or cross-platform alternatives for setup and tooling. All command-line instructions are shown in PowerShell, and there is no mention of Linux-compatible editors or package managers. The guide assumes a Windows development environment throughout.
Recommendations
- Add instructions for installing the .NET SDK and the Azure Communication Services Chat SDK using cross-platform tools (e.g., dotnet CLI) and show examples in Bash as well as PowerShell.
- Mention and provide links to cross-platform IDEs/editors such as VS Code, JetBrains Rider, or simply the .NET CLI, instead of only Visual Studio.
- Clarify that the SDK and all code samples are cross-platform and can be used on Linux and macOS, not just Windows.
- Where PowerShell is used for commands, provide equivalent Bash/zsh commands for Linux/macOS users.
- Explicitly state platform compatibility in the prerequisites section and avoid language that implies Windows is required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communications-gateway/connect-teams-direct-routing.md
...communications-gateway/connect-teams-direct-routing.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell parameters and the Teams Admin Center UI (which is primarily Windows-centric) for configuration. There are no Linux-specific examples, CLI commands, or cross-platform instructions. The documentation assumes the use of Microsoft 365 admin tools and PowerShell, which are more accessible and commonly used on Windows systems, and does not mention or provide parity for Linux-based administration.
Recommendations
- Provide equivalent instructions using cross-platform tools such as Azure CLI, Microsoft Graph API, or generic REST API calls where possible.
- Include explicit Linux/macOS command-line examples, such as using Bash, curl, or other standard tools for DNS verification and API interaction.
- Clarify whether PowerShell Core (pwsh), which is cross-platform, can be used, and provide examples for both Windows PowerShell and PowerShell Core.
- Reference and link to any available Linux-compatible admin tools or portals, and note any limitations or differences.
- Ensure that all steps that mention PowerShell or Windows-specific tools are accompanied by Linux/macOS alternatives or a statement about cross-platform compatibility.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communications-gateway/prepare-for-live-traffic-teams-direct-routing.md
...teway/prepare-for-live-traffic-teams-direct-routing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation assumes and requires the use of PowerShell for configuration changes to Microsoft Teams Direct Routing, with no mention of cross-platform alternatives or Linux/macOS-compatible tools. There are no examples or guidance for users who may be operating from non-Windows environments, and the documentation implicitly assumes a Windows-centric workflow.
Recommendations
- Provide equivalent instructions and examples using cross-platform tools such as Azure CLI, Microsoft Graph API, or Teams PowerShell Core (which is available on Linux/macOS).
- Explicitly mention that PowerShell Core can be used on Linux and macOS, and provide installation and usage instructions for those platforms.
- Where possible, include bash or shell script examples alongside PowerShell, or clarify when a step is Windows-specific.
- Review all prerequisite steps and ensure that none require Windows-only tools, or provide alternatives where necessary.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communications-gateway/manage-enterprise-teams-direct-routing.md
...ions-gateway/manage-enterprise-teams-direct-routing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing PowerShell for critical configuration steps (e.g., setting PSTN gateways for voice routes), without mentioning or providing equivalent Linux/macOS-compatible alternatives. The only command-line example is a PowerShell command, and there is no discussion of cross-platform tools or how to perform these steps on non-Windows systems. The documentation assumes the use of the Microsoft 365 Admin Center and PowerShell, both of which are traditionally Windows-centric, and does not address Linux or macOS users' needs.
Recommendations
- Provide equivalent instructions and examples for Linux and macOS users, such as using Microsoft Teams PowerShell on those platforms (which is supported via PowerShell Core).
- Explicitly mention that PowerShell Core can be installed and used on Linux/macOS, and provide installation instructions or links.
- Clarify whether all required cmdlets (e.g., Set-CsOnlineVoiceRoute) are available and supported on non-Windows platforms.
- If any steps require Windows-only tools or interfaces, clearly state this limitation and suggest workarounds or alternatives for Linux/macOS users.
- Include example commands or scripts using cross-platform tools where possible, and avoid assuming a Windows environment by default.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communications-gateway/connect-operator-connect.md
...les/communications-gateway/connect-operator-connect.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments, specifically PowerShell. All command-line instructions are given exclusively in PowerShell, with no mention of Linux or cross-platform alternatives (such as Azure CLI, Bash, or Cloud Shell). The steps assume the user is running PowerShell on Windows, including instructions to 'Open PowerShell as an admin' and module installation via Install-Module. There are no Linux or macOS equivalents, and no mention of how to perform these tasks on non-Windows systems. This may exclude or confuse users working from Linux or macOS environments.
Recommendations
- Provide equivalent instructions using Azure CLI and/or Bash scripts, which are cross-platform and supported on Linux and macOS.
- Mention that PowerShell Core is available on Linux and macOS, and provide any necessary prerequisites or differences for those platforms.
- Explicitly state whether the steps can be performed in Azure Cloud Shell, which is accessible from any OS and supports both PowerShell and Bash.
- For module installation and admin rights, clarify how to perform these steps on Linux/macOS (e.g., using sudo, or installing modules in user scope).
- Where possible, offer both PowerShell and Azure CLI examples side by side, or link to platform-specific guides.
- Add a note at the beginning of the document clarifying OS requirements and available cross-platform options.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/confidential-computing/guest-attestation-confidential-vms.md
...ential-computing/guest-attestation-confidential-vms.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Claims
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias. While it is generally platform-neutral in its descriptions, the sample JSON web token and claims focus on Windows-specific fields (such as 'x-ms-azurevm-is-windows': true and 'x-ms-azurevm-ostype': 'Windows'), and there are no explicit Linux or cross-platform examples. No Linux-specific claims or scenarios are shown, and there are no Linux command-line or code examples. The documentation does not mention Linux tools or patterns, nor does it provide parity in example outputs or API usage for Linux environments.
Recommendations
- Include example JSON web tokens for Linux-based confidential VMs, highlighting relevant claims (e.g., 'x-ms-azurevm-ostype': 'Linux').
- Add explicit statements clarifying that the APIs and attestation flows are supported on both Windows and Linux confidential VMs.
- Provide example code snippets or command-line usage for both Windows (e.g., PowerShell) and Linux (e.g., Bash), or clarify that the APIs are OS-agnostic.
- Document any differences in claims or attestation flows between Windows and Linux confidential VMs.
- Ensure diagrams and scenario descriptions mention both Windows and Linux workloads where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/confidential-computing/quick-create-confidential-vm-azure-cli.md
...al-computing/quick-create-confidential-vm-azure-cli.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows and PowerShell in the sections related to customer-managed keys and disk encryption set configuration. Several steps use PowerShell scripting and Windows-specific tools (e.g., Microsoft Graph PowerShell SDK) without providing equivalent Bash or Linux-native alternatives, despite the overall focus on Azure CLI and the fact that confidential VMs are often Linux-based. Some commands mix Azure CLI and PowerShell, which may confuse Linux users or those working in Bash environments. The attestation section is Linux-focused, but earlier critical steps lack Linux parity.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell-based steps, especially for Azure AD and Microsoft Graph operations.
- Avoid using PowerShell-specific constructs (e.g., Out-String, ConvertFrom-Json, $variable assignment) in CLI-focused documentation unless a Linux/Bash alternative is also shown.
- Clearly indicate when a step is Windows-only or provide both Windows (PowerShell) and Linux (Bash) instructions side-by-side.
- For steps requiring Microsoft Graph, link to or provide instructions for using the Microsoft Graph CLI or REST API from Bash.
- Ensure that all scripting examples are runnable in Azure Cloud Shell (Bash) or on a typical Linux system, or provide explicit guidance for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/confidential-computing/quick-create-portal.md
...articles/confidential-computing/quick-create-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation generally presents a cross-platform approach but exhibits subtle Windows bias. Windows terminology and tools (e.g., PowerShell, RDP) are mentioned alongside or before Linux equivalents. The Linux VM workflow is described, but there is a lack of detailed Linux-specific post-deployment instructions (e.g., installing the OE SDK on Linux), while explicit links are provided for Windows. Some instructions and notes reference Windows tools (PowerShell, WSL) and provide more guidance for Windows users.
Recommendations
- Provide explicit, step-by-step instructions or links for installing the OE SDK on Linux, similar to the Windows guidance.
- When referencing tools for connecting to VMs, mention Linux-native tools first (e.g., Bash/Terminal), then Windows options.
- Ensure parity in post-deployment steps for both Linux and Windows, including troubleshooting and next steps.
- Avoid listing Windows authentication ports (RDP) before or without Linux equivalents; present both equally.
- Where possible, include Linux-first examples and clarify any differences in workflow or requirements.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/confidential-computing/quick-create-confidential-vm-portal.md
...ntial-computing/quick-create-confidential-vm-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation exhibits some Windows bias, particularly in the use of PowerShell for prerequisite steps (service principal creation), the mention of Windows-specific tools (PuTTY) as the primary SSH client example, and the ordering of Windows connection instructions before Linux. Linux alternatives are present but often secondary or less detailed.
Recommendations
- Provide Azure CLI and/or Bash equivalents for all PowerShell commands, especially for service principal and key creation steps.
- When referencing SSH clients, mention native OpenSSH (available by default on most Linux/macOS systems) before or alongside PuTTY, and clarify that PuTTY is primarily needed on Windows.
- In connection instructions, present Linux and Windows methods in parallel or in a neutral order, rather than listing Windows first.
- Ensure that all steps and examples are provided for both Windows and Linux users, with equal detail and prominence.
- Where possible, link to both Windows and Linux documentation for further actions (e.g., connecting, key creation) rather than only one.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/confidential-computing/virtual-tpms-in-azure-confidential-vm.md
...ial-computing/virtual-tpms-in-azure-confidential-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific TPM documentation, tools, and concepts exclusively. All links and examples point to Windows TPM documentation, and there are no Linux-specific instructions, examples, or references. The language and resources assume a Windows-centric audience, omitting Linux usage patterns or guidance.
Recommendations
- Include references to Linux TPM documentation and tools, such as tpm2-tools and relevant Linux kernel modules.
- Provide examples or links for managing and attesting vTPMs on Linux-based Azure confidential VMs.
- Balance references to Windows and Linux by mentioning both platforms when discussing TPM usage, configuration, and attestation.
- Add a section or callout specifically addressing Linux users, outlining any differences or additional steps required for vTPM usage on Linux confidential VMs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/connectors/connectors-create-api-db2.md
...main//articles/connectors/connectors-create-api-db2.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias. Windows is mentioned before Linux/UNIX in several places, such as in the description of supported platforms ("IBM DB2 for Windows running in Azure virtualization") and in username length notes ("DB2 for Windows accepts a 30-byte string" after Linux/UNIX). The authentication options for on-premises connections list 'Windows (Kerberos)' as a choice, but do not mention Linux authentication mechanisms or Kerberos on Linux. There are no Linux-specific examples or guidance for connecting to DB2 on Linux, and the documentation does not address Linux-specific gateway installation or troubleshooting. All screenshots and UI flows are platform-neutral, but the text and examples lean toward Windows environments.
Recommendations
- Ensure Linux/UNIX is mentioned alongside Windows, and not after or as an afterthought, in all lists and explanations (e.g., 'DB2 for Linux, UNIX, or Windows' instead of 'DB2 for Windows').
- Provide explicit examples and guidance for connecting to DB2 running on Linux/UNIX, including any differences in connection strings, authentication, or gateway setup.
- If authentication mechanisms differ on Linux (e.g., Kerberos configuration), document those steps or link to relevant Linux-specific resources.
- Where username length or other properties differ by platform, list Linux/UNIX first or present all platforms in a neutral order.
- Consider including troubleshooting tips or notes for common Linux/UNIX deployment scenarios, such as SELinux, firewall, or package dependencies for the on-premises data gateway.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/connectors/connectors-create-api-sqlazure.md
.../articles/connectors/connectors-create-api-sqlazure.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific environments (such as App Service Environment v3 'Windows plans only'), mentioning Windows Authentication as an option for on-premises SQL Server connections, and omitting any explicit guidance or examples for Linux-based environments or authentication mechanisms. There are no examples or instructions for Linux users, and Windows terminology and tools are mentioned without Linux equivalents.
Recommendations
- Provide explicit guidance and examples for connecting from Linux-based environments, including connection string formats and authentication options relevant to Linux.
- Clarify whether features (such as built-in connectors or authentication types) are available or supported on Linux-based App Service plans, and document any differences.
- Include Linux authentication options (such as Kerberos, if supported) or clarify their absence.
- When referencing Windows Authentication or Windows plans, also mention Linux alternatives or note if they are not available.
- Add examples or notes for Linux users where only Windows-specific instructions are given (e.g., for on-premises data gateway installation or authentication).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-web-table.md
...lob/main//articles/data-factory/connector-web-table.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively recommending Microsoft Excel (2016/2013) and Power Query/Power BI—Windows-centric tools—for extracting the table index from an HTML page. There are no examples or instructions for achieving the same task on Linux or macOS platforms, nor are cross-platform or open-source alternatives mentioned. This may hinder users on non-Windows systems from following the documentation effectively.
Recommendations
- Provide alternative instructions for extracting the table index using cross-platform or Linux-native tools, such as Python scripts with BeautifulSoup or pandas, or command-line utilities like curl and pup.
- Include at least one example using open-source tools available on Linux/macOS (e.g., a Python snippet that loads the HTML and prints table indices).
- When listing tools or methods, mention cross-platform or Linux options before or alongside Windows-specific tools.
- Add a note clarifying that the described method is Windows-specific and suggest alternatives for other operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/energy-data-services/how-to-convert-segy-to-zgy.md
...les/energy-data-services/how-to-convert-segy-to-zgy.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing primarily on Windows-centric tools and workflows. Postman, a GUI desktop app popular on Windows, is presented as the primary method for API interaction, with cURL mentioned only as an alternative. There are no explicit Linux or cross-platform command-line examples for API calls (e.g., using curl or httpie directly). The SDUTIL tool is described as a Python utility, which is cross-platform, but the setup and usage instructions do not clarify Linux-specific steps or considerations. There is no mention of Linux package managers, shell differences, or alternative Linux-native tools. The documentation assumes a GUI workflow and does not provide parity for headless or CLI-first Linux environments.
Recommendations
- Provide explicit cURL or httpie command-line examples alongside or before Postman instructions, ensuring parity for Linux and headless users.
- Clarify that SDUTIL is cross-platform and provide installation instructions for both Windows and Linux (e.g., pip install, dependencies, permissions).
- Include Linux-specific notes for file paths, shell commands, and environment variable setting (e.g., export vs. set).
- Mention and demonstrate how to perform all API interactions using CLI tools available on Linux, not just via Postman.
- Where screenshots are used, consider including terminal-based examples or text-based walkthroughs for Linux users.
- Explicitly state that all workflows are supported on Linux and provide troubleshooting or environment setup tips for common Linux distributions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/confidential-computing/quick-create-confidential-vm-arm.md
...idential-computing/quick-create-confidential-vm-arm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by requiring PowerShell for variable assignment and scripting, referencing PowerShell installation in the prerequisites, and using Windows-specific tools and patterns (e.g., PowerShell cmdlets, backtick line continuations). Windows parameter file examples are presented before Linux ones, and some instructions (such as those involving Microsoft Graph SDK) are PowerShell-centric. There is minimal guidance for Linux shell users, and Linux command-line patterns are not shown.
Recommendations
- Provide all variable assignment and scripting examples in both PowerShell and Bash syntax, clearly labeling each.
- In prerequisites, mention both PowerShell and Bash (or native Linux shell) as supported environments for Azure CLI.
- For every PowerShell-specific command or pattern (e.g., variable assignment, line continuation), provide the equivalent Bash/Linux shell version.
- When referencing tools like Microsoft Graph SDK, clarify if there are cross-platform alternatives or CLI equivalents, and provide those where possible.
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid 'windows_first' bias.
- Review all code snippets for Windows-specific conventions (e.g., backticks for line continuation, use of ConvertFrom-Json) and provide Linux alternatives (e.g., jq for JSON parsing).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/connectors/integrate-ims-apps-ibm-mainframe.md
...rticles/connectors/integrate-ims-apps-ibm-mainframe.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-based tools (Host Integration Server Designer, which requires .NET Framework 4.8), and does not mention or provide alternatives for Linux or cross-platform environments. All setup and tooling instructions assume a Windows environment, with no guidance for Linux or macOS users. There are no Linux-specific examples or parity in tool recommendations.
Recommendations
- Provide information on whether the Host Integration Server Designer or equivalent tools are available for Linux or macOS, or clarify if they are Windows-only.
- If the tooling is Windows-only, suggest workarounds for Linux users, such as using a Windows VM, Docker container, or cloud-hosted environment.
- Include explicit statements about platform support in the prerequisites section.
- Offer Linux/macOS-compatible alternatives where possible, or document the limitations for non-Windows users.
- If possible, provide example workflows or instructions that can be followed from Linux or macOS environments, especially for uploading HIDX files or interacting with Azure Logic Apps.