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 1426-1450 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-r-deploy-configure-certificates-vpn-encryption.md
...dge-pro-r-deploy-configure-certificates-vpn-encryption.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing BitLocker for encryption-at-rest, which is a Windows-specific technology. There are no mentions of Linux-based encryption tools or workflows, nor are there any Linux-specific instructions or examples for certificate management, VPN configuration, or encryption. The documentation assumes the use of Windows-native tools and does not provide parity for Linux users.
Recommendations
- Include references to Linux-compatible encryption-at-rest solutions or clarify if BitLocker is the only supported method for this device.
- Provide examples or guidance for generating and managing certificates using Linux tools (e.g., OpenSSL) alongside any Windows-based instructions.
- Offer VPN configuration steps or troubleshooting tips relevant to Linux clients, if supported.
- Explicitly state any platform limitations or requirements, so Linux users are aware of what is or isn't supported.
- Where possible, use cross-platform terminology and avoid assuming the use of Windows-only technologies.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-bring-your-own-certificates.md
...ticles/databox/data-box-bring-your-own-certificates.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides detailed, step-by-step instructions for importing certificates on Windows clients, including screenshots and explicit UI navigation. There are no equivalent instructions or examples for Linux or macOS clients, nor is there any mention of alternative certificate import methods for non-Windows systems. This creates a Windows-first bias and leaves Linux users without guidance.
Recommendations
- Add a section with instructions for importing certificates on Linux clients, including common distributions (e.g., Ubuntu, CentOS) and relevant commands (such as using update-ca-certificates or trust anchor).
- Include a brief note or section for macOS users, describing how to import certificates using Keychain Access.
- Where possible, provide cross-platform command-line examples (e.g., using openssl or certutil) in addition to GUI-based instructions.
- Explicitly state that the process may differ on non-Windows systems and link to relevant official documentation for Linux and macOS certificate management.
- Ensure that screenshots and step-by-step guides are balanced between platforms, or at least acknowledge the absence and encourage community contributions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-deploy-export-ordered.md
...in//articles/databox/data-box-deploy-export-ordered.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through the exclusive mention of Windows tools (Robocopy, PowerShell script) and the absence of Linux equivalents or examples. Specifically, Robocopy is suggested for applying ACLs, and a PowerShell script is provided for XML generation, with no mention of Linux-native alternatives or cross-platform instructions. There are no explicit Linux command-line examples or references to Linux tools for data copy, ACL handling, or XML file generation.
Recommendations
- Provide equivalent Linux tools and commands alongside Windows-specific ones. For example, suggest using 'rsync' or 'cp --preserve' for ACLs on Linux, in addition to Robocopy.
- Offer a Bash or Python script for XML file generation, or clarify if the PowerShell script can be run cross-platform (e.g., with PowerShell Core on Linux).
- Include explicit Linux examples or instructions wherever file operations, scripting, or data copy are discussed.
- Clarify OS support and parity in prerequisites, and link to documentation on using Data Box with Linux hosts.
- Where screenshots or UI steps are shown, note any differences or additional steps for Linux users if applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-disk-deploy-upload-verify.md
...articles/databox/data-box-disk-deploy-upload-verify.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing Microsoft Azure Storage Explorer (a GUI tool primarily used on Windows) for data verification, and by not providing any command-line or Linux-native methods (such as Azure CLI, azcopy, or Linux file system tools) for verifying data upload. There are no examples or instructions tailored for Linux users, and no mention of Linux-compatible tools or workflows.
Recommendations
- Add examples using Azure CLI (az storage blob list, az storage file list, etc.) to verify data upload, which work cross-platform.
- Include instructions for using azcopy, a cross-platform command-line tool, to list and verify blobs/files in the storage account.
- Mention that Azure Storage Explorer is available on Linux and macOS, and provide installation links for those platforms.
- Provide sample shell commands (e.g., using curl or wget) to check for the presence of files in Azure Storage from Linux.
- Ensure that all GUI-based instructions are supplemented with equivalent command-line steps for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-disk-security.md
.../blob/main//articles/databox/data-box-disk-security.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing BitLocker (a Windows-native encryption tool) for disk encryption, without mentioning Linux-compatible alternatives or providing guidance for Linux users. There are no examples or instructions for managing or unlocking Data Box Disks on Linux systems, nor is there mention of cross-platform unlock tools or procedures.
Recommendations
- Include information about using Data Box Disk with Linux systems, such as supported unlock tools or procedures for Linux.
- Mention Linux-compatible disk encryption and decryption tools, or clarify if BitLocker-encrypted disks can be accessed from Linux (and how).
- Provide explicit Linux command-line examples or references alongside any Windows/Powershell instructions.
- Clarify cross-platform compatibility in the requirements and quickstart documentation, ensuring Linux users are equally supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-disk-troubleshoot.md
...b/main//articles/databox/data-box-disk-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-style drive letters (e.g., D:\, E:\) and file paths, and by including a sample error referencing a PowerShell script (.ps1). There are no Linux or cross-platform path examples, nor is there any mention of Linux tools or workflows for validation or log access.
Recommendations
- Include Linux-style path examples (e.g., /mnt/databoxdiskimport/logs) alongside Windows paths.
- Mention how to access the logs and run the validation tool on Linux systems, if supported.
- Provide sample error logs that reference Linux file types or scripts (e.g., .sh files) in addition to Windows-specific ones.
- Clarify any platform-specific requirements or limitations for the validation tool.
- If the tool is Windows-only, explicitly state this and provide guidance for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-troubleshoot.md
...s/blob/main//articles/databox/data-box-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides troubleshooting guidance for Azure Data Box devices but lacks explicit examples or instructions tailored for Linux users. While SMB/NFS shares are mentioned (which are cross-platform), all operational instructions reference the device's web UI and generic share access, without any command-line examples. There are no Linux-specific tools, commands, or workflows shown, and the only OS-specific mention is a note that symbolic links aren't allowed in Linux, which is presented as a restriction rather than guidance. No PowerShell or Windows-only tools are explicitly referenced, but the absence of Linux parity in examples and the general pattern of not addressing Linux workflows suggests a subtle Windows-first bias.
Recommendations
- Add explicit Linux command-line examples for common troubleshooting steps, such as mounting SMB/NFS shares, renaming files/folders, and checking file alignment.
- Include references to Linux tools (e.g., smbclient, mount, find, mv) alongside any Windows tools or UI instructions.
- When describing error resolution steps, provide both Windows and Linux workflows in parallel, ensuring Linux users are equally supported.
- Clarify any OS-specific limitations (such as symbolic link handling) with actionable guidance for Linux users.
- Consider including a section or appendix specifically for Linux users, summarizing best practices and troubleshooting tips relevant to their environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/ddos-protection/ddos-protection-reference-architectures.md
...-protection/ddos-protection-reference-architectures.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias in its reference architectures for virtual machine workloads. Windows is explicitly mentioned and linked in architecture descriptions and reference links, while Linux is only mentioned in passing (e.g., 'Windows/Linux' in section headers) without any Linux-specific examples, diagrams, or links. There are no Linux-focused reference architectures or guidance, and all detailed examples and links point to Windows VM scenarios.
Recommendations
- Provide parallel Linux-focused reference architectures and diagrams, similar to those given for Windows (e.g., 'Linux N-tier application on Azure').
- Include links to Linux VM reference architectures and documentation, not just Windows.
- Ensure that examples, descriptions, and best practices are presented for both Windows and Linux workloads, or use neutral language and examples that apply equally to both.
- If certain features or architectures are Windows-specific, explicitly state this and provide Linux alternatives where possible.
- Review all sections for implicit prioritization of Windows and ensure Linux is given equal prominence and detail.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/ddos-protection/manage-ddos-ip-protection-template.md
.../ddos-protection/manage-ddos-ip-protection-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for managing resources, but PowerShell is consistently listed before CLI in all code tabs and output sections. This ordering implicitly prioritizes Windows/PowerShell users. There are no Linux-specific tools, shell, or OS-specific instructions, but the 'PowerShell first' pattern may signal a subtle Windows bias.
Recommendations
- Alternate the order of PowerShell and CLI tabs or present CLI examples first, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that both PowerShell and CLI commands can be run in Azure Cloud Shell, which is available on all platforms.
- Consider including Bash shell script snippets or references to Linux terminal usage where appropriate.
- Add a note clarifying that Azure CLI commands are fully supported on Linux, macOS, and Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/device-builders/how-to-install-micro-agent-for-edge.md
...device-builders/how-to-install-micro-agent-for-edge.md
Medium Priority
View Details →
Detected Bias Types
Missing Windows Example
Linux Only
Summary
The documentation exclusively provides installation and usage instructions for Debian/Ubuntu-based Linux distributions, with no mention of Windows or Windows-specific tools, commands, or examples. All package management, service validation, and operational steps are Linux-centric, indicating a bias toward Linux and a lack of Windows parity.
Recommendations
- Add equivalent instructions for installing and configuring the Defender for IoT micro agent on Windows-based Edge devices, if supported.
- Include PowerShell or Command Prompt examples for Windows, covering repository setup, installation, service management, and validation.
- Mention Windows prerequisites and any differences in the installation or authentication process.
- If Windows is not supported, explicitly state this early in the documentation to clarify the intended audience.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/device-builders/tutorial-create-micro-agent-module-twin.md
...ce-builders/tutorial-create-micro-agent-module-twin.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on using the Azure Portal UI for creating and verifying the DefenderIotMicroAgent module twin, without providing any command-line examples. There are no references to Windows-specific tools or PowerShell, but there is also a lack of parity for Linux users: no CLI (Azure CLI, Bash, or PowerShell) instructions are provided, which could disadvantage users who prefer or require non-GUI, cross-platform workflows.
Recommendations
- Add Azure CLI examples for creating and verifying module twins, ensuring commands work on both Linux and Windows.
- If applicable, provide PowerShell and Bash script examples for automation.
- Explicitly mention that the portal steps are OS-agnostic, but highlight CLI alternatives for users on Linux or headless environments.
- Include links to relevant Azure CLI documentation for managing IoT Hub module twins.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/device-builders/concept-event-aggregation.md
...r-for-iot/device-builders/concept-event-aggregation.md
Medium Priority
View Details →
Detected Bias Types
Missing Windows Example
Linux Heavy
Summary
The documentation page focuses almost exclusively on Linux (and to a lesser extent, Eclipse ThreadX) in its event collection descriptions and examples. Most event types, parameters, and collector behaviors are described only for Linux, with Windows mentioned only in passing (e.g., as an example OS version string). There are no Windows-specific examples, tools, or instructions, and several collectors are explicitly marked as 'Linux only' or describe Linux-specific concepts (e.g., inotify masks, PIDs, UTMP, PAM).
Recommendations
- Add equivalent Windows event collection details where supported, including which collectors are available on Windows and what data is collected.
- Provide Windows-specific examples and parameter descriptions (e.g., Windows process IDs, event log sources, file system monitoring methods).
- Clarify in each collector section whether the feature is Linux-only, Windows-only, or cross-platform, and provide parity where possible.
- If certain collectors are not available on Windows, explicitly state this and, if possible, provide guidance or alternatives for Windows users.
- Include Windows terminology and tools (such as Event Viewer, Windows Security Log, etc.) where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/api/sensor-inventory-apis.md
...der-for-iot/organizations/api/sensor-inventory-apis.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias primarily in the ordering and enumeration of supported operating systems, where Windows versions are listed first and in exhaustive detail, while Linux and Mac OS are mentioned only once and without further breakdown. There are no Linux-specific examples, tools, or patterns, but the documentation does not use Windows-only command-line tools (e.g., PowerShell); instead, it uses cURL, which is cross-platform. However, the focus on Windows in supported values and the context of Microsoft Defender for IoT may implicitly prioritize Windows environments.
Recommendations
- List supported operating systems in alphabetical order or group by platform (e.g., Windows, Linux, Mac OS, Unix) to avoid the perception of prioritizing Windows.
- Provide more granularity for Linux and Mac OS versions if possible, similar to the detailed breakdown for Windows.
- Include explicit statements or examples that demonstrate parity of support for Linux and Mac OS environments.
- If there are platform-specific considerations (e.g., authentication, API usage), document them for both Windows and Linux.
- Consider adding example API calls or usage notes relevant to Linux environments, such as using wget or other common Linux tools, if appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/concept-sentinel-integration.md
...-for-iot/organizations/concept-sentinel-integration.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page is heavily focused on Microsoft Sentinel and Defender for IoT, both of which are Microsoft (and thus Windows-centric) tools. There are no explicit examples or instructions for Linux environments, nor are any Linux-native tools, commands, or workflows mentioned. All examples, queries, and integrations are described solely in the context of the Microsoft ecosystem, implicitly assuming a Windows-based SOC environment.
Recommendations
- Include examples or guidance for integrating Defender for IoT data with SIEM/SOAR solutions commonly used in Linux environments (e.g., Splunk, ELK Stack).
- Provide sample scripts or command-line instructions for Linux (e.g., using Bash, curl, or Python) to query or process Defender for IoT data.
- Mention or link to any available APIs or data export options that would allow Linux-based tools to ingest or interact with Defender for IoT and Sentinel data.
- Clarify whether the described integrations and playbooks can be triggered or managed from non-Windows environments, and provide instructions if so.
- Add a section comparing Microsoft Sentinel with other SIEM/SOAR solutions, including those commonly deployed on Linux, and describe how Defender for IoT can interoperate with them.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-center/enable-api-analysis-linting.md
...in//articles/api-center/enable-api-analysis-linting.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell syntax for Azure CLI commands, but consistently lists Bash first and then PowerShell, which is a positive sign for parity. However, there is a subtle Windows bias in the use of Visual Studio Code (a cross-platform tool but often associated with Windows) and the Azure Functions extension, and in the use of PowerShell-specific syntax in all CLI examples. The documentation does not provide Linux-specific troubleshooting, nor does it mention Linux-native tools or editors. All portal-based instructions assume the Azure Portal web UI, which is platform-neutral. There are no exclusive Windows tools, but the presence of PowerShell syntax throughout and the lack of explicit Linux-native guidance (such as using Vim, nano, or Linux package managers) suggest a mild Windows/PowerShell bias.
Recommendations
- Explicitly state that Visual Studio Code and the Azure Functions extension are fully supported on Linux and macOS, and provide links to installation instructions for those platforms.
- Add Linux-native editor alternatives (e.g., Vim, nano) for editing YAML files, or at least mention that any editor can be used.
- Include troubleshooting steps or notes for common Linux-specific issues (such as file permissions or dependency installation).
- Where PowerShell syntax is provided, ensure that Bash syntax is equally prominent and clarify which is which.
- Consider including at least one example of running the function app locally on Linux, or mention that all steps are cross-platform.
- If referencing the Azure CLI, note that it is fully supported on Linux and provide a link to Linux installation instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/how-to-import-device-information.md
...-iot/organizations/how-to-import-device-information.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is generally neutral in its main content, focusing on CSV-based imports via the OT sensor UI, which is platform-agnostic. However, in the 'Next steps' section, it specifically links to a page about detecting Windows workstations and servers with a local script, with no mention of Linux or cross-platform alternatives. There are no Linux-specific examples, tools, or guidance, and Windows is mentioned first and exclusively in the endpoint detection context.
Recommendations
- Add references or links to documentation for detecting Linux endpoints or devices, if supported.
- Provide parity in 'Next steps' by including Linux/macOS detection or management guides alongside the Windows example.
- If scripts or automation are discussed elsewhere, ensure examples are provided for both Windows (PowerShell, CMD) and Linux (Bash, shell scripts).
- Review related documentation to ensure Linux and other non-Windows platforms are equally represented where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/amazon-bedrock-passthrough-llm-api.md
...s/api-management/amazon-bedrock-passthrough-llm-api.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides only .NET/C# code examples and references to the Azure portal, with no mention of Linux-specific tools, CLI, or cross-platform SDKs. There are no Linux shell, Python, or curl examples, and the workflow assumes use of the Azure portal (which is web-based but often associated with Windows-centric workflows). The only SDK example is in C#, which is most popular on Windows, and there is no guidance for Linux users or those using other languages/platforms.
Recommendations
- Add equivalent examples using Python (with boto3 and requests), which is widely used on Linux and cross-platform.
- Provide a curl example for making API calls, demonstrating how to interact with the API from a Linux shell.
- Include instructions for using Azure CLI and/or Azure PowerShell for relevant steps, and present CLI examples before or alongside portal-based instructions.
- Mention that the .NET SDK and code samples are cross-platform, and provide explicit instructions for running them on Linux/macOS.
- Add troubleshooting notes or tips for Linux users, such as environment variable configuration or package installation.
- Consider including a table or section comparing cross-platform SDKs (e.g., .NET, Python, Java, Node.js) for interacting with Amazon Bedrock via Azure API Management.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/includes/ilo-remote-install-hpe.md
...r-iot/organizations/includes/ilo-remote-install-hpe.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides a step-by-step GUI-based installation process for iLO but does not mention or provide examples for performing the same installation from Linux environments or using Linux command-line tools. The instructions implicitly assume a Windows-like workflow (e.g., mounting ISOs via GUI), and there is no discussion of Linux alternatives or parity.
Recommendations
- Add instructions or examples for performing the iLO installation using Linux systems, such as mounting ISOs via command-line tools (e.g., using 'mount' or 'dd').
- Include references to Linux-compatible remote management tools or CLI utilities that can interact with iLO.
- If the iLO web interface is OS-agnostic, explicitly state that the process works equally on Linux, macOS, and Windows, and mention any browser or tool compatibility considerations.
- Provide parity in troubleshooting or alternative steps for users who may not have access to Windows environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/manage-subscriptions-enterprise.md
...r-iot/organizations/manage-subscriptions-enterprise.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references Microsoft 365 admin center, Microsoft Defender XDR, and other Microsoft portals for all management tasks, with no mention of Linux or cross-platform command-line tools, APIs, or alternative workflows. There are no examples or instructions for Linux users, nor is there any discussion of parity for non-Windows environments.
Recommendations
- Include instructions or references for managing EIoT monitoring via cross-platform tools such as REST APIs, CLI tools (e.g., Azure CLI, Microsoft Graph CLI), or PowerShell Core (which is cross-platform) with explicit Linux/macOS usage examples.
- Add notes or sections clarifying whether the described portals and tools are accessible from Linux/macOS browsers and if there are any limitations.
- Provide sample scripts or command-line instructions for Linux environments where applicable, especially for license management and device inventory tasks.
- Explicitly state platform requirements and offer guidance for users operating outside the Windows ecosystem.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-center/includes/configure-managed-identity-kv-secret-user.md
.../includes/configure-managed-identity-kv-secret-user.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell examples are labeled as 'Formatted for PowerShell' and are always presented immediately after the Bash examples. There is no explicit mention of Linux or macOS, and the PowerShell examples may suggest a Windows-first approach. However, both platforms are represented, and no examples are missing for Linux users.
Recommendations
- Explicitly label Bash examples as suitable for Linux/macOS and PowerShell examples as suitable for Windows.
- Present both Bash and PowerShell examples in parallel tabs or sections, rather than sequentially, to avoid the impression of prioritizing one platform.
- Add a short introductory note clarifying that the Azure CLI works on all platforms and that users should choose the example matching their shell environment.
- Ensure that any references to shell-specific syntax (e.g., variable assignment, string manipulation) are explained or linked to relevant documentation for both Bash and PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-center/set-up-api-center-arm-template.md
.../articles/api-center/set-up-api-center-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the ARM template, but PowerShell (a Windows-centric tool) is given equal prominence to the cross-platform Azure CLI. There is no mention of Linux-specific shell usage or examples (e.g., bash), and PowerShell is presented as a primary alternative rather than as a secondary or optional tool. The documentation does not clarify that Azure CLI is cross-platform and more native to Linux environments, nor does it provide any Linux-specific context or troubleshooting.
Recommendations
- Explicitly state that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is more common on Windows.
- Present Azure CLI examples first, as it is the most cross-platform tool, and consider making PowerShell examples secondary or in a collapsible/optional section.
- Add a note or section for Linux/macOS users, confirming that the Azure CLI commands can be run in bash or other Unix shells.
- If PowerShell is included, clarify that it is available on Linux but may require additional setup, and provide links or guidance for Linux PowerShell installation if relevant.
- Consider including troubleshooting tips or environment preparation steps specific to Linux (e.g., file permissions, package installation).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-center/includes/configure-managed-identity-apim-reader.md
...ter/includes/configure-managed-identity-apim-reader.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell examples are labeled and formatted specifically for Windows users. The PowerShell examples are always presented immediately after the Bash examples, which may suggest a slight Windows-first orientation. However, there are no Linux-specific tools or workflows missing, and both platforms are covered. There is no exclusive use of Windows tools, but the explicit PowerShell formatting and labeling could be seen as a bias toward Windows users.
Recommendations
- Clearly label Bash examples as 'Linux/macOS' and PowerShell examples as 'Windows' to make parity explicit.
- Present both Bash and PowerShell examples side-by-side or in tabs, rather than always listing Bash first, to avoid a perceived ordering bias.
- Include a brief note at the top of the CLI section explaining that both Linux/macOS (Bash) and Windows (PowerShell) are supported, and users should choose the example matching their environment.
- Ensure that any platform-specific nuances (such as line continuation characters or variable syntax) are explained for both environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/ot-deploy/update-device-inventory.md
...iot/organizations/ot-deploy/update-device-inventory.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page references a Windows-specific tool (Windows Management Instrumentation - WMI) to enhance device data visibility, without mentioning equivalent tools or methods for Linux-based devices. There are no examples or instructions for enhancing visibility for non-Windows endpoints, which may leave Linux users without guidance.
Recommendations
- Include instructions or references for enhancing device visibility for Linux-based devices, such as using SSH, SNMP, or other relevant Linux-native tools.
- If no direct Linux equivalent exists, explicitly state this and suggest alternative approaches for Linux environments.
- Ensure that examples and enhancement steps are platform-agnostic or provide parallel guidance for both Windows and Linux endpoints.
- Review other documentation in the series for similar bias and address Linux parity throughout.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/references-work-with-defender-for-iot-cli-commands.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/references-work-with-defender-for-iot-cli-commands.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing Windows tools (PuTTY) first and specifically mentioning them, while Mac/Linux equivalents are less detailed or omitted. The guidance for accessing the CLI prioritizes Windows users and tools, with only a brief mention of Mac (Terminal) and no explicit mention of Linux (e.g., GNOME Terminal, Konsole, or SSH command line). There are no PowerShell-specific examples or commands, but the pattern of mentioning Windows tools and order of presentation suggests a subtle preference.
Recommendations
- Explicitly mention Linux systems and provide examples for accessing the CLI from Linux (e.g., 'On a Linux system, use Terminal or the ssh command').
- List all platforms (Windows, Mac, Linux) together and in a neutral order, or rotate the order to avoid implicit prioritization.
- Include common Linux terminal emulators (e.g., GNOME Terminal, Konsole) and the standard ssh command in the instructions.
- Avoid naming Windows tools (like PuTTY) exclusively; if tools are mentioned, provide equivalents for all major platforms.
- Consider a table or bullet list showing how to access the CLI from Windows, Mac, and Linux, with example commands for each.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/api-management-howto-deploy-multi-region.md
...management/api-management-howto-deploy-multi-region.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page provides step-by-step instructions and command-line examples for managing Azure API Management multi-region deployments. While it includes Azure CLI commands (which are cross-platform), it references Azure PowerShell as an alternative but does not provide explicit Linux/bash shell examples or mention Linux tooling. The only command-line examples shown are for Azure CLI, and PowerShell is mentioned after CLI, which is an improvement over 'Windows-first' bias but still lacks Linux-specific context or examples. There are no references to Windows-only tools, but the absence of bash or Linux shell examples and the lack of explicit mention of Linux environments suggest a subtle bias.
Recommendations
- Include explicit bash/Linux shell examples where relevant, especially for scripting or automation scenarios.
- When mentioning Azure PowerShell, clarify that it is available cross-platform, or provide both PowerShell and bash equivalents for common tasks.
- Add notes or examples for Linux users, such as how to install or use the Azure CLI and PowerShell on Linux.
- Ensure that screenshots and UI references do not assume a Windows environment (e.g., file paths, shell prompts).
- Where possible, provide parity in command-line examples for both PowerShell and bash to serve both Windows and Linux users equally.