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 76-100 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/manage-users-portal.md
.../defender-for-iot/organizations/manage-users-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell as the only command-line example for role assignment, without mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI or Bash). The structure and links prioritize the Azure portal and PowerShell, which are more familiar to Windows users, and do not offer parity for Linux-based workflows.
Recommendations
- Include Azure CLI examples alongside Azure PowerShell for all command-line instructions, as Azure CLI is cross-platform and widely used on Linux.
- When referencing command-line tools, mention both PowerShell and CLI options, and provide links to both sets of instructions.
- Ensure that any screenshots or walkthroughs that are not platform-specific clarify that the steps are the same regardless of OS, or provide notes for Linux/macOS users where differences exist.
- Add a section or note explicitly stating that all management tasks can be performed from Linux, macOS, or Windows, and link to relevant cross-platform documentation.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/ot-deploy/create-ssl-certificates.md
...iot/organizations/ot-deploy/create-ssl-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing certificate management and import instructions exclusively through Windows GUI tools (e.g., Certificate Export Wizard, Certificate Import Wizard, Windows file explorer, and editing the Windows hosts file). There are no equivalent Linux CLI or GUI instructions for certificate export/import or hosts file editing, and Windows paths and terminology are used throughout.
Recommendations
- Add parallel Linux instructions for exporting and importing certificates using common tools (e.g., openssl, update-ca-certificates, certutil, or manual copying to /etc/ssl/certs).
- Include Linux file paths (e.g., /etc/hosts) and editors (e.g., nano, vi) when describing hosts file modifications.
- Provide screenshots or CLI examples for Linux environments alongside Windows examples.
- Avoid assuming the use of Windows GUI tools; offer command-line alternatives that work cross-platform.
- When referencing file explorers or wizards, clarify that these are Windows-specific and provide Linux equivalents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/ot-virtual-appliances.md
...efender-for-iot/organizations/ot-virtual-appliances.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Microsoft Hyper-V (a Windows-centric hypervisor) alongside VMware ESXi as the only explicitly supported hypervisors, with dedicated links and guidance for both. Linux-native hypervisors such as KVM or Xen are not mentioned, nor are there any Linux-specific deployment examples or references. The documentation also references Windows tools (Hyper-V) before mentioning or omitting Linux alternatives, and does not provide parity in examples or guidance for Linux-based environments.
Recommendations
- Explicitly mention support (or lack thereof) for popular Linux hypervisors such as KVM/QEMU and Xen, and provide guidance or links for deploying on these platforms if supported.
- Include Linux-focused deployment examples or walkthroughs, such as creating and configuring VMs using virsh, virt-manager, or other Linux-native tools.
- Balance the order of hypervisor/tool mentions so that Linux and Windows options are presented equally, or clarify the reasoning for any prioritization.
- If Linux hypervisors are not supported, clearly state this in the documentation to avoid ambiguity.
- Provide troubleshooting or configuration notes relevant to Linux environments (e.g., setting promiscuous mode on Linux bridges, configuring SR-IOV on Linux hosts).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-center/synchronize-api-management-apis.md
...articles/api-center/synchronize-api-management-apis.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it claims Azure CLI commands can be run in both PowerShell and bash, the only explicit shell distinction is between PowerShell and bash variable syntax, and no actual Linux-specific (bash) examples are provided. The mention of PowerShell precedes bash, and there is no demonstration of Linux-native tools or workflows. The documentation does not provide parity in examples or instructions for Linux users.
Recommendations
- Provide explicit bash/Linux shell command examples alongside PowerShell examples, especially where variable syntax or command usage differs.
- When referencing shells, list bash (Linux) before or alongside PowerShell to avoid Windows-first ordering.
- Include notes or sections on any Linux-specific prerequisites, such as package dependencies or environment setup.
- Ensure screenshots and UI references are platform-agnostic or include Linux desktop/browser examples where relevant.
- Audit included content (e.g., reusable includes) to ensure they do not assume a Windows environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/api-management-howto-ca-certificates.md
...api-management/api-management-howto-ca-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI-based example for uploading a CA certificate, with no equivalent Azure CLI, Bash, or Linux-native instructions. The use of PowerShell and lack of Linux/Unix examples or tools suggests a Windows-centric approach.
Recommendations
- Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash or shell script examples for certificate management tasks where applicable.
- Explicitly mention that the PowerShell command can be run on Linux/Mac using PowerShell Core, or provide alternative commands for those platforms.
- Ensure parity in documentation by listing Linux-friendly tools and methods alongside Windows/PowerShell options.
- Consider reordering or supplementing instructions so that cross-platform or platform-agnostic methods (such as REST API or Azure CLI) are presented before or alongside Windows-specific tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/api-management-revisions.md
...n//articles/api-management/api-management-revisions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets (e.g., New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) as the only command-line automation examples, without mentioning or providing equivalent Azure CLI or REST API commands that are cross-platform and commonly used on Linux/macOS. There are no Linux-specific instructions or examples, and the documentation assumes use of Windows tooling for automation.
Recommendations
- Provide equivalent Azure CLI commands alongside PowerShell cmdlets for all automation tasks (e.g., setting a revision as current, updating change logs).
- Include REST API examples where appropriate, as these are platform-agnostic.
- Explicitly mention that PowerShell examples are for Windows and offer alternatives for Linux/macOS users.
- Consider reordering examples to present cross-platform tools (Azure CLI, REST API) before or alongside Windows-specific tools.
- Add a section or note highlighting cross-platform management options for Azure API Management.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/api-management-configuration-repository-git.md
...agement/api-management-configuration-repository-git.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 tools (Git Bash from Git for Windows, Visual Studio Immediate Window) and providing detailed instructions using these tools, while not offering equivalent Linux or cross-platform alternatives. There are no Linux-specific examples or mentions of common Linux tools (e.g., native bash, URL encoding via Linux utilities), and the guidance for encoding passwords is tied to Visual Studio, a Windows-centric IDE.
Recommendations
- Provide explicit Linux/macOS examples for cloning the repository, such as using the native terminal/bash.
- Offer cross-platform methods for URL encoding passwords, such as using Python, Node.js, or command-line tools like 'printf' or 'jq', instead of relying solely on Visual Studio.
- When mentioning tools, list cross-platform or Linux-native options alongside Windows tools (e.g., 'You can use Git Bash, a Linux/macOS terminal, or any Git tool you are familiar with').
- Avoid referencing Windows-specific UI elements (like Visual Studio Immediate Window) without providing platform-agnostic alternatives.
- Ensure that any troubleshooting steps or advanced commands are demonstrated in both Windows and Linux contexts.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/api-management-role-based-access-control.md
...management/api-management-role-based-access-control.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 only PowerShell examples for creating custom roles, referencing Azure PowerShell prominently, and omitting equivalent Azure CLI or cross-platform scripting examples. While Azure CLI and REST API are mentioned as alternatives for role assignment, no concrete examples are provided for these tools, and the only code sample is in PowerShell. This may disadvantage Linux or macOS users who are more likely to use Azure CLI or scripting languages other than PowerShell.
Recommendations
- Provide equivalent Azure CLI examples alongside PowerShell code samples for all major operations, especially for creating and assigning custom roles.
- Explicitly mention that all operations can be performed using Azure CLI and REST API, and link to relevant documentation or include sample commands.
- Consider including Bash or cross-platform scripting examples where appropriate.
- Ensure that references to tools and workflows do not assume a Windows environment or PowerShell as the default.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/api-management-howto-mutual-certificates.md
...management/api-management-howto-mutual-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by providing only PowerShell examples for command-line operations (such as disabling certificate chain validation), without offering equivalent instructions for Linux environments (e.g., Azure CLI, Bash, or REST API with curl). The exclusive use of PowerShell cmdlets and the absence of Linux-native tooling or examples may hinder users working on non-Windows platforms.
Recommendations
- Provide equivalent examples using Azure CLI commands for all PowerShell cmdlets shown, especially for operations like disabling certificate chain validation.
- Include REST API examples using curl or HTTPie to demonstrate cross-platform approaches.
- Explicitly mention that PowerShell examples can be run on Linux and macOS via PowerShell Core, or provide Bash script alternatives.
- Add a section or callout for Linux/macOS users, highlighting any platform-specific considerations or differences.
- Ensure that all tooling and examples are presented in a platform-neutral order, or alternate between Windows and Linux-first presentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/export-rest-mcp-server.md
...ain//articles/api-management/export-rest-mcp-server.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing Visual Studio Code (VS Code) and GitHub Copilot for testing and interacting with the MCP server, without mentioning or providing examples for Linux-native tools or command-line alternatives. The workflow assumes the use of the Azure Portal (a web UI), VS Code (which is cross-platform but often associated with Windows), and does not provide any Linux shell, curl, or CLI-based examples for interacting with the MCP server. There is also a lack of parity in tool recommendations, as only Windows-centric or Microsoft ecosystem tools are highlighted.
Recommendations
- Provide equivalent examples using Linux-native tools such as curl, httpie, or wget to demonstrate how to interact with the MCP server endpoints.
- Include instructions for using the Azure CLI or REST API directly from a Linux shell to configure or test the MCP server.
- Mention and provide examples for editing configuration files (such as mcp.json) using standard Linux text editors (e.g., nano, vim) in addition to VS Code.
- Explicitly state that all steps can be performed on Linux, and highlight any cross-platform compatibility considerations.
- List alternative open-source or cross-platform MCP client tools, if available, and show how to use them on Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/breaking-changes/api-version-retirement-sep-2023.md
...nt/breaking-changes/api-version-retirement-sep-2023.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for checking and updating tool versions, but PowerShell (a Windows-centric tool) is given equal prominence to the cross-platform Azure CLI. PowerShell-specific commands and update instructions are detailed, and links to PowerShell documentation are included. There is no mention of Linux-specific shell commands or package managers (e.g., apt, yum, Homebrew) for updating the Azure CLI or PowerShell, nor are there examples for Linux/macOS environments. The documentation implicitly assumes familiarity with Windows/PowerShell tooling.
Recommendations
- Provide explicit Linux/macOS instructions for updating Azure CLI and Azure PowerShell, including common package manager commands (e.g., apt-get, yum, brew).
- Clarify that Azure CLI is cross-platform and provide shell command examples for bash/zsh users.
- When listing tools, mention cross-platform options (like Azure CLI) before Windows-centric ones (like PowerShell), or group them by platform.
- Include example commands for both Windows (PowerShell) and Linux/macOS (bash) where relevant.
- Link to platform-specific installation/update guides for both CLI and PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/applications.md
...ocs/blob/main//articles/api-management/applications.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a clear Windows bias. All command-line examples are provided exclusively in PowerShell, with no equivalent Bash, curl, or cross-platform scripting examples. The use of Azure PowerShell and references to the Azure portal (a web UI, but often associated with Windows-centric workflows) further reinforce this bias. There are no Linux-native or cross-platform command-line instructions, and the PowerShell examples are presented as the default and only way to perform key tasks.
Recommendations
- Provide equivalent Bash/curl examples for token generation and API calls, ensuring Linux and macOS users can follow along without PowerShell.
- Clearly indicate that the Azure portal is web-based and accessible from any OS, to avoid the impression of Windows exclusivity.
- Wherever PowerShell scripts are given, add corresponding Bash/curl or Python examples side-by-side.
- Review all prerequisite and tool references to ensure they are not Windows-specific, or provide Linux alternatives where necessary.
- Explicitly mention cross-platform compatibility in relevant sections to reassure non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/api-management-howto-log-event-hubs.md
.../api-management/api-management-howto-log-event-hubs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page provides command-line examples only for Azure PowerShell, with no mention of Azure CLI or Bash/shell scripting alternatives. PowerShell is a Windows-centric tool (though cross-platform, it is still less common on Linux than Bash or Azure CLI). The absence of Azure CLI or Linux-native command examples may hinder Linux users or those who prefer cross-platform tooling.
Recommendations
- Add Azure CLI examples alongside PowerShell for all logger creation and management steps.
- Explicitly mention that PowerShell examples can be run on Linux/macOS, or provide Bash equivalents where possible.
- Include guidance or links for using REST API calls with curl or similar Linux-native tools.
- Ensure that all code tabs (PowerShell, Bicep, ARM) are supplemented with Azure CLI and/or Bash tabs where relevant.
- Review the documentation for any other Windows-first assumptions and clarify cross-platform compatibility.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/api-management-howto-use-managed-service-identity.md
...t/api-management-howto-use-managed-service-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, referencing PowerShell installation, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell approach is presented before any mention of ARM templates, and there is no guidance for users on Linux or macOS systems. No Linux-specific tools, shell commands, or cross-platform scripting options are discussed.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- When introducing command-line options, present both PowerShell and Azure CLI alternatives, or at least mention that both are supported.
- Include explicit instructions or notes for Linux/macOS users, such as how to install and use Azure CLI or run ARM template deployments from Bash.
- Avoid referencing only Windows-specific tools (like PowerShell) in installation instructions; provide parity for Bash/CLI environments.
- Consider reordering sections so that cross-platform solutions (Azure CLI, ARM templates) are not always presented after Windows-centric ones.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/tutorial-cyberark.md
...es/defender-for-iot/organizations/tutorial-cyberark.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows file paths (e.g., 'c:\Program Files\PrivateArk\Server\dbparam.xml'), Windows-centric tools (Server Central Administration with 'Stop Traffic Light'), and omitting any Linux/Unix equivalents or instructions. There are no examples or guidance for configuring CyberArk or Defender for IoT integration on Linux-based systems, despite the fact that many OT/IoT environments may use Linux appliances.
Recommendations
- Provide parallel Linux/Unix instructions for configuring CyberArk and Defender for IoT, including file paths (e.g., '/opt/PrivateArk/Server/dbparam.xml') and service management commands (e.g., using systemctl or service commands instead of GUI tools).
- Include CLI examples for both Windows (cmd/PowerShell) and Linux (bash) when referencing file modifications or service restarts.
- Explicitly state platform requirements or limitations if the integration is only supported on Windows, or clarify cross-platform support.
- When referencing configuration files or directories, provide both Windows and Linux/Unix paths where applicable.
- Add screenshots or descriptions of Linux-based management interfaces if available, or note differences in workflow.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/developer-portal-basic-authentication.md
...pi-management/developer-portal-basic-authentication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page provides a PowerShell cmdlet (New-AzApiManagementUser) as the only example of a command-line tool for adding users, without mentioning or providing equivalent examples for Linux/macOS users (such as Azure CLI or REST API). This suggests a bias towards Windows tooling and omits cross-platform alternatives.
Recommendations
- Include Azure CLI examples for adding users to Azure API Management, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Mention and provide REST API examples for user management, which are platform-agnostic.
- When referencing PowerShell, clarify that it is available cross-platform, or provide both Windows PowerShell and Bash/Azure CLI examples side by side.
- Review the documentation for other places where only Windows-centric tools or workflows are referenced and add Linux/macOS alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/quickstart-arm-template.md
...in//articles/api-management/quickstart-arm-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page primarily demonstrates ARM template deployment using the Azure Portal and briefly mentions Azure PowerShell, Azure CLI, and REST API as alternatives. However, it does not provide any command-line examples for Linux users (e.g., Azure CLI on Bash), and references to Azure PowerShell precede those to Azure CLI, which is more cross-platform. There are no explicit Linux or Bash shell examples, and the workflow is oriented around the Azure Portal, which is platform-agnostic but often associated with Windows-centric workflows.
Recommendations
- Add explicit Azure CLI examples for deploying ARM templates, using Bash syntax, to ensure Linux parity.
- When listing alternative deployment methods, mention Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux.
- Include sample commands for both Azure CLI and Azure PowerShell in relevant sections, ideally in tabbed code blocks for easy comparison.
- Reference Linux and macOS environments explicitly where appropriate, and clarify that all command-line steps are cross-platform unless otherwise noted.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/traffic-mirroring/configure-mirror-hyper-v.md
...izations/traffic-mirroring/configure-mirror-hyper-v.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is exclusively focused on configuring traffic mirroring using Hyper-V, a Windows-only virtualization platform. All examples and instructions use Windows tools (PowerShell, Hyper-V Manager) and Microsoft-specific features (NDIS Capture Extensions). There are no references to Linux, cross-platform virtualization solutions (e.g., KVM, VMware, VirtualBox), or equivalent Linux commands and tools. This creates a strong Windows bias, making the documentation inaccessible to users on Linux or other platforms.
Recommendations
- Add a section or parallel documentation for configuring traffic mirroring using popular Linux hypervisors such as KVM/QEMU, libvirt, or VMware ESXi.
- Provide equivalent Linux command-line examples (e.g., using virsh, nmcli, or ip commands) for creating virtual switches, attaching interfaces, and configuring port mirroring.
- Mention that Hyper-V is a Windows-only solution at the beginning, and provide links or references to Linux-based alternatives for users on other platforms.
- Include a comparison table or guidance for users to select the appropriate virtualization and mirroring method based on their operating system.
- Ensure that future documentation for cross-platform products includes parity in examples and instructions for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/deployment-environments/how-to-configure-azure-developer-cli-deployment-environments.md
...-configure-azure-developer-cli-deployment-environments.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the installation instructions for the Azure Developer CLI. The only command-line installation example provided uses PowerShell, with no mention of Linux/macOS installation methods or shell commands. This omission may hinder Linux/macOS users, as they are not given clear guidance for their platforms. Additionally, the PowerShell example is presented before any mention of cross-platform support, reinforcing a Windows-first perspective.
Recommendations
- Provide explicit installation instructions for Linux and macOS, including bash/zsh commands (e.g., using curl or package managers like apt, yum, or Homebrew).
- Add tabs or sections for each supported platform (Windows, Linux, macOS) in the installation instructions, ensuring parity.
- Avoid presenting only PowerShell scripts; always include equivalent bash commands where possible.
- Clearly state cross-platform support at the beginning of installation/setup sections.
- Where screenshots or UI steps are shown, clarify if they are platform-specific or provide alternatives for other platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/deployment-environments/how-to-configure-extensibility-model-custom-image.md
...s/how-to-configure-extensibility-model-custom-image.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in several key areas: all quickstart scripting examples for building and pushing custom container images use PowerShell scripts (.ps1) and PowerShell syntax, with no equivalent Bash or shell script examples for Linux/macOS users. The instructions explicitly mention the need for 'Docker Desktop', a tool primarily associated with Windows and macOS, rather than platform-agnostic Docker Engine. There are no Linux-specific instructions or examples for building and pushing images, nor are cross-platform alternatives provided alongside the PowerShell examples. This may hinder Linux users or those working in non-Windows environments.
Recommendations
- Provide equivalent Bash/shell script examples for all PowerShell (.ps1) script usage, especially for building and pushing images.
- Explicitly mention support for Linux/macOS and clarify that Docker Engine (not just Docker Desktop) is supported.
- Wherever a PowerShell command is shown, include a tabbed or side-by-side Bash alternative.
- Avoid assuming the use of Windows-specific tools (like Docker Desktop) as the default; mention platform-agnostic options first.
- Add a 'Prerequisites' note clarifying cross-platform compatibility and listing required tools for both Windows and Linux/macOS.
- Audit referenced scripts/repos to ensure they provide both .ps1 and .sh (or platform-neutral) automation options.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/import-api-from-oas.md
...b/main//articles/api-management/import-api-from-oas.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to the cross-platform CLI. There is no mention of Linux-specific tools, shell environments, or workflows, and PowerShell is referenced as a primary automation method. The prerequisites and examples do not clarify that Azure CLI is fully cross-platform or suggest Linux-specific considerations, and the PowerShell example assumes a Windows context.
Recommendations
- Clarify that Azure CLI is fully cross-platform and works natively on Linux, macOS, and Windows.
- Explicitly mention that PowerShell Core (pwsh) is available on Linux and macOS, or clarify if only Windows PowerShell is supported.
- Add bash/zsh shell script examples for the Azure CLI commands to demonstrate Linux-native workflows.
- Include a note or section on using the Azure CLI in Linux environments, such as installing the CLI on Ubuntu or using it in a Docker container.
- If PowerShell is included, specify when to use PowerShell Core vs. Windows PowerShell, and provide parity for Linux users.
- Avoid implying that PowerShell is the default or preferred automation tool unless it is truly cross-platform and equally supported on Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/developer-portal-self-host.md
.../articles/api-management/developer-portal-self-host.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias, particularly in the section on uploading static files to Azure Blob Storage. It explicitly instructs users to 'Open Windows Command Prompt, PowerShell, or other command shell,' listing Windows environments first and not mentioning Linux or macOS shells by name. No Linux- or macOS-specific instructions or examples are provided, and there is no mention of platform-specific considerations for those environments. The rest of the guide uses cross-platform tools (Git, Node.js, Azure CLI) and generic shell commands, but the explicit Windows-first language and lack of Linux/macOS parity in the upload step stand out.
Recommendations
- Replace 'Open Windows Command Prompt, PowerShell, or other command shell.' with 'Open your preferred command shell (such as Windows Command Prompt, PowerShell, Bash, or Terminal on Linux/macOS).' to acknowledge non-Windows environments.
- Wherever possible, provide explicit instructions or notes for Linux and macOS users, especially in steps involving the command line.
- Consider including example commands or screenshots from both Windows and Linux/macOS shells to demonstrate true cross-platform support.
- Review the rest of the documentation for any subtle Windows-first language or assumptions and update to be more inclusive of all platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/deployment-environments/quickstart-create-dev-center-project-azure-resource-manager.md
...start-create-dev-center-project-azure-resource-manager.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (cross-platform) or Bash examples. The code blocks and instructions are tailored to PowerShell, which is most familiar to Windows users. While the text briefly mentions that Azure CLI can be used, no CLI or Linux-native instructions are provided, and PowerShell is presented as the default method.
Recommendations
- Add equivalent Azure CLI (az deployment) examples for all deployment scenarios, including both default and custom parameter usage.
- Include Bash shell instructions for Linux/macOS users, or clarify that the Azure Cloud Shell supports both Bash and PowerShell.
- Present Azure CLI and PowerShell examples side-by-side or in tabs, and avoid implying that PowerShell is the primary or only method.
- Explicitly mention cross-platform compatibility and provide guidance for users on Linux/macOS.
- Review and update any references to tools or workflows that are Windows-specific to ensure parity for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/configure-authentication-customize-sign-in-out.md
...vice/configure-authentication-customize-sign-in-out.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the 'Server level (Windows apps only)' section, where it provides detailed instructions for configuring authorization using IIS and web.config, which are exclusive to Windows. There is no equivalent example or guidance for Linux-based App Service apps, nor is there mention of how to achieve similar authorization controls on Linux. Additionally, the section is labeled 'Windows apps only', but Linux alternatives are not discussed, leaving a gap for Linux users.
Recommendations
- Provide equivalent guidance for Linux-based App Service apps, such as using .htaccess for Apache, nginx configuration, or middleware-based authorization in popular frameworks (Node.js, Python, etc.).
- Explicitly mention how Linux users can implement similar authorization controls, or link to relevant documentation.
- Ensure that examples and instructions for command-line tools (such as Azure CLI) are presented in a cross-platform manner, and clarify that they work on both Windows and Linux.
- Where a feature is Windows-only, offer a workaround or alternative for Linux users, or clearly state the limitation and suggest next steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/manage-backup.md
...-docs/blob/main//articles/app-service/manage-backup.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: file paths and examples use Windows conventions (e.g., %HOME%, D:\home\site\wwwroot), instructions reference Windows-specific tools (such as Kudu DebugConsole and FTP with Windows paths), and there is a lack of explicit Linux or cross-platform command-line examples. While Linux is mentioned in passing (e.g., /home directory), practical guidance and examples are Windows-centric, and Linux equivalents are not provided or are mentioned only after Windows.
Recommendations
- Provide parallel Linux examples for file paths and operations (e.g., show /home/site/wwwroot alongside D:\home\site\wwwroot).
- When referencing tools like Kudu or FTP, clarify usage for both Windows and Linux environments, including path differences.
- Include Linux shell commands (e.g., using SCP, SFTP, or Linux CLI tools) for uploading files and managing backups.
- Use neutral or dual-platform environment variables and path formats in examples and explanations.
- Ensure that all instructions and troubleshooting steps are equally applicable to both Windows and Linux App Service environments, or clearly indicate any platform-specific differences.