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 51-75 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-heavy-deploy-copy-data.md
...n//articles/databox/data-box-heavy-deploy-copy-data.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows connection and copy instructions before Linux, providing detailed examples and screenshots for Windows (including use of Robocopy and File Explorer), and omitting equivalent Linux copy tool examples (such as rsync or cp for SMB). The only Linux SMB example is a single mount command, and there is no detailed walkthrough or output sample for Linux users. The primary file copy tool discussed is Robocopy, a Windows-specific utility, with no mention of Linux alternatives for SMB data transfer.
Recommendations
- Provide Linux SMB copy examples using common tools such as smbclient, mount.cifs, rsync, or cp, including command syntax and sample output.
- Include Linux screenshots or terminal output to parallel the detailed Windows walkthrough.
- List Linux instructions and examples alongside Windows, or in a parallel structure, rather than after or as an afterthought.
- Mention and explain Linux-native tools for performance copying (e.g., rsync with SMB/CIFS mounts) and discuss tuning options analogous to the Robocopy parameters.
- Reference troubleshooting steps and log file viewing on Linux systems, not just Windows (e.g., using less, cat, or tail).
- Ensure that all steps (connecting, copying, verifying, troubleshooting) have Linux parity in detail and clarity.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-limits.md
...re-docs/blob/main//articles/databox/data-box-limits.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by repeatedly referencing Windows-specific behaviors and limitations (such as ReFS metadata, SMB protocol, and case-insensitivity), without providing equivalent details or guidance for Linux users. There are no Linux-specific examples, caveats, or tool mentions, and the documentation assumes a Windows environment as the default context.
Recommendations
- Include explicit guidance for Linux users, such as how Data Box interacts with Linux file systems (e.g., ext4, XFS) and any relevant caveats.
- Provide examples or notes on using Data Box with Linux-based SMB/NFS clients, including any known limitations or differences.
- Clarify whether the listed limitations (e.g., case-insensitivity, ReFS metadata) apply only to Windows or also to Linux environments, and describe Linux-specific behaviors where applicable.
- Mention Linux tools or commands (e.g., rsync, cp, mount) alongside Windows tools where relevant.
- Add a section or table comparing Windows and Linux interoperability, especially for file naming, protocol support, and client connection limits.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-heavy-migrate-spo.md
...b/main//articles/databox/data-box-heavy-migrate-spo.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing instructions and links for creating and using Windows VMs, mounting Azure file shares on Windows, and using Windows-based tools (SharePoint Migration Tool). There are no examples or guidance for performing these steps on Linux systems, nor are Linux equivalents mentioned.
Recommendations
- Provide parallel instructions for Linux users, including how to create a Linux VM in Azure.
- Add steps for mounting Azure file shares on Linux (e.g., using SMB and the mount command).
- Clarify whether the SharePoint Migration Tool is available for Linux, and if not, suggest alternative migration approaches for Linux environments.
- Ensure that links to mounting file shares and VM creation include both Windows and Linux documentation.
- Explicitly state OS requirements or limitations for the SharePoint Migration Tool early in the document.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-disk-deploy-set-up.md
.../main//articles/databox/data-box-disk-deploy-set-up.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and tool downloads are often presented before Linux equivalents, and PowerShell/Command Prompt examples are detailed and prominent. Windows-specific tools (e.g., DataBoxDiskUnlock.exe) are emphasized, and some sections (such as troubleshooting and validation) provide more detail or imagery for Windows than for Linux. Linux instructions are present and fairly comprehensive, but sometimes appear after Windows steps or require more manual setup (e.g., installing dependencies, using third-party tools like SEDUtil).
Recommendations
- Present Windows and Linux instructions in parallel or with equal prominence, avoiding 'Windows first' ordering where possible.
- Ensure all examples, screenshots, and troubleshooting steps are equally detailed for both Windows and Linux.
- Where a tool or step is Windows-specific, clearly indicate the Linux equivalent (or vice versa) in the same section.
- Provide direct download links and setup instructions for Linux tools as prominently as for Windows.
- Avoid assuming PowerShell/Command Prompt as the default; include Bash or shell examples alongside.
- If third-party tools are required for Linux (e.g., SEDUtil), consider providing pre-packaged scripts or containers to simplify the process.
- Review all sections for parity in detail, imagery, and step-by-step guidance between platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-heavy-deploy-copy-data-via-rest.md
...es/databox/data-box-heavy-deploy-copy-data-via-rest.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and workflows (such as PowerShell and the Windows Server UI) are described in greater detail and appear before Linux equivalents. Certificate import instructions are more detailed for Windows, with Linux guidance being more generic and less step-by-step. In AzCopy usage examples, both Windows and Linux commands are provided, but Windows is often listed second. The overall tone and structure favor Windows environments, with more explicit instructions and screenshots for Windows users.
Recommendations
- Provide equally detailed, step-by-step instructions for Linux certificate import, including command-line examples for common distributions (e.g., Ubuntu, CentOS, RHEL).
- Include screenshots or terminal output for Linux steps, similar to the Windows UI screenshots.
- When listing OS-specific instructions or examples, alternate the order or present Linux first in some sections to avoid the impression of Windows primacy.
- Expand on Linux troubleshooting and verification steps, ensuring parity with Windows guidance.
- Where possible, use cross-platform tools and commands, and clearly indicate any OS-specific differences.
- Consider adding a table or section summarizing OS-specific steps for quick reference.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-overview.md
...-docs/blob/main//articles/databox/data-box-overview.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page for Azure Data Box demonstrates a subtle Windows bias. It references Windows-centric tools (e.g., SharePoint Migration Tool, Azure File Sync, SQL Server, Hyper-V) and partner solutions that are primarily Windows-focused. There are no explicit Linux or cross-platform command-line examples, nor are Linux-specific tools or workflows mentioned. The documentation assumes familiarity with Windows environments and omits guidance or examples for Linux users, such as mounting SMB shares or copying data from Linux systems.
Recommendations
- Add explicit examples and instructions for Linux environments, such as how to mount Data Box SMB shares on Linux using smbclient or mount.cifs, and how to copy data using Linux-native tools (e.g., rsync, cp, scp).
- Mention Linux-compatible partner solutions and backup tools, and clarify which third-party integrations support Linux workloads.
- Balance references to Windows tools (e.g., SharePoint Migration Tool, Azure File Sync) with Linux equivalents or alternatives, such as using HDFS or NFS exports.
- Include a section or callout for cross-platform compatibility, highlighting supported operating systems and any OS-specific considerations.
- Where possible, provide step-by-step workflows for both Windows and Linux environments, especially for common tasks like data copy, device setup, and troubleshooting.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-quickstart-portal.md
...b/main//articles/databox/data-box-quickstart-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by mentioning Windows tools (Robocopy) first, providing a link only for Robocopy, and generally prioritizing Windows terminology and patterns. Linux/Unix tools (cp, rsync) are mentioned only as alternatives, with no detailed examples or links. There are no explicit Linux command-line examples, and the documentation assumes familiarity with Windows file sharing paths (\\<IP>\ShareName) without providing equivalent NFS mount instructions for Linux users.
Recommendations
- Provide explicit Linux/Unix command-line examples for copying data (e.g., using cp, rsync, or NFS mount commands).
- Include links to documentation for Linux/Unix tools (e.g., rsync manual, NFS documentation), similar to the Robocopy link for Windows.
- Present Windows and Linux instructions in parallel, rather than listing Windows first or exclusively.
- Clarify SMB vs NFS usage, and provide guidance for mounting NFS shares on Linux.
- Use neutral language (e.g., 'host computer' instead of 'Windows host') and avoid assuming the user is on Windows.
- Add troubleshooting tips or references for common Linux issues (e.g., permissions, SELinux, firewall) when connecting to Data Box shares.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-heavy-quickstart-portal.md
...//articles/databox/data-box-heavy-quickstart-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows evidence of Windows bias, particularly in the 'Copy data' section where Windows/SMB and the Windows tool Robocopy are mentioned first and in detail, while Linux/NFS is only briefly referenced with generic commands (cp/rsync) and less guidance. There are no Linux-specific examples for connecting to SMB shares, and the documentation generally assumes familiarity with Windows tools and patterns.
Recommendations
- Provide Linux-specific examples for copying data to SMB shares, such as using smbclient, mount.cifs, or rsync with SMB.
- List Linux/NFS options before or alongside Windows/SMB options to avoid 'windows_first' ordering.
- Include explicit command-line examples for Linux users, such as mounting SMB shares or using rsync over SMB.
- Mention common Linux file copy tools (e.g., scp, rsync, cp) with example commands for both NFS and SMB scenarios.
- Clarify any differences in authentication or share access between Windows and Linux hosts.
- Ensure parity in troubleshooting steps and guidance for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-troubleshoot-rest.md
...b/main//articles/databox/data-box-troubleshoot-rest.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows-specific troubleshooting steps and tools before their Linux equivalents, especially in the AzCopy section. Windows paths and tools are often mentioned first, and some recommendations (such as syncing time with time.windows.com) are Windows-centric. There are also more detailed or explicit instructions for Windows users, while Linux guidance is sometimes less prominent or appears later.
Recommendations
- Present Linux and Windows instructions in parallel or in a unified table, rather than in separate sections with Windows first.
- Ensure that Linux examples and troubleshooting steps are as detailed and explicit as their Windows counterparts.
- Mention cross-platform tools and paths together, or alternate the order in which they are presented.
- When referencing system-level requirements (such as NTP servers), provide Linux-appropriate defaults (e.g., pool.ntp.org) alongside Windows ones.
- Avoid using Windows-specific terminology (e.g., 'system’s certificate store') without clarifying the Linux equivalent.
- Where possible, provide shell command examples for Linux (not just environment variable settings), and ensure parity with any PowerShell or Windows command examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-troubleshoot-share-access.md
...articles/databox/data-box-troubleshoot-share-access.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All troubleshooting steps, command-line examples, and UI screenshots are Windows-specific. Only Windows tools (e.g., net use, Event Viewer, Local Security Policy, Registry Editor) are referenced, with no mention of Linux or macOS equivalents. There are no Linux command examples or instructions for connecting to SMB shares or troubleshooting from non-Windows systems.
Recommendations
- Add equivalent Linux (and optionally macOS) troubleshooting steps for connecting to SMB shares, such as using the smbclient or mount.cifs commands.
- Provide Linux command-line examples for connecting to SMB shares and handling authentication errors.
- Include instructions for checking and modifying SMB client settings on Linux (e.g., editing /etc/samba/smb.conf, using smbclient debug output).
- Mention relevant Linux log files (e.g., /var/log/syslog, /var/log/samba/) for troubleshooting authentication and connection issues.
- Where group policy or registry changes are discussed, note the equivalent configuration files or settings on Linux, or clarify if not applicable.
- Add screenshots or terminal output from Linux environments where appropriate.
- Explicitly state if certain troubleshooting steps are only applicable to Windows, and provide alternatives for other platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/mqtt-topic-spaces.md
...cs/blob/main//articles/event-grid/mqtt-topic-spaces.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows/Powershell bias by providing special character escaping guidance and examples only for PowerShell, without mentioning or providing equivalent instructions for Linux shells (such as Bash or Zsh). The escaping section is labeled 'based on the shell being used,' but only PowerShell is covered, and no Linux or cross-platform shell examples are given.
Recommendations
- Add explicit examples for escaping special characters (such as $ and |) in common Linux shells (e.g., Bash, Zsh) alongside the existing PowerShell examples.
- Rephrase the note to mention both Windows and Linux shells, or provide a table comparing escaping requirements for PowerShell, Bash, and other popular shells.
- Ensure that all command-line instructions (such as Azure CLI examples) are tested and shown to work on both Windows and Linux, and note any differences.
- Consider including a general cross-platform section or a link to shell-specific guidance for users on different operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/ddos-protection/ddos-protection-overview.md
...//articles/ddos-protection/ddos-protection-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by specifically referencing Azure PowerShell for enabling DDoS IP Protection, without mentioning or linking to equivalent CLI (cross-platform) or Linux-native instructions. There are no Linux or Bash examples, and the only command-line example provided is for PowerShell, which is primarily a Windows tool. This may give the impression that Windows or PowerShell is the preferred or only supported environment for managing DDoS IP Protection.
Recommendations
- Include equivalent instructions and quickstart links for enabling DDoS IP Protection using the Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
- When referencing command-line tools, mention both PowerShell and Azure CLI options, and provide parity in documentation structure and detail.
- Avoid presenting Windows-specific tools or workflows before cross-platform alternatives, or present them together to avoid perceived prioritization.
- Explicitly state that all features are available and supported on Linux and macOS, and provide examples or screenshots where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-logs.md
...zure-docs/blob/main//articles/databox/data-box-logs.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily through the exclusive use of Windows-centric terminology, log samples, and account names (e.g., WIN-DATABOXADMIN, NT AUTHORITY, use of backslashes in file paths). There are no explicit Linux or cross-platform command-line examples, nor are Linux-specific tools or log formats discussed. The audit log sample is clearly from a Windows event log, and there is no mention of Linux authentication, file system conventions, or how logs might differ on Linux clients. While the documentation mentions SMB and NFS protocols, it does not provide parity in examples or troubleshooting steps for Linux environments.
Recommendations
- Include Linux-specific examples for accessing and interpreting logs, such as sample audit logs from NFS clients or Linux authentication events.
- Provide file path examples using both Windows (backslash) and Linux (forward slash) conventions.
- Mention and demonstrate how to access Data Box shares and logs from Linux systems, including sample commands (e.g., using mount, smbclient, or NFS utilities).
- Clarify any differences in log formats or error messages when using Linux clients versus Windows clients.
- Add troubleshooting steps and references for common Linux issues, such as permissions, character encoding, or mounting shares.
- Ensure that any scripts or tools referenced (e.g., CRC checksum tool) are demonstrated in both Windows and Linux environments, with usage instructions for each.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-powershell-based-configuration.md
...ine/azure-stack-edge-powershell-based-configuration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All automation and scripting examples are provided exclusively in PowerShell, and the prerequisites specify Windows 10/Server and PowerShell 5.1 or later. There are no Linux or cross-platform CLI examples, nor is there any mention of Linux support or alternatives for non-Windows users. The documentation assumes the use of Windows tools and patterns throughout.
Recommendations
- Explicitly state whether Linux (or macOS) clients are supported for device provisioning and configuration. If not, clarify this limitation early in the documentation.
- If Linux is supported, provide equivalent instructions and examples using cross-platform tools such as Azure CLI, Bash scripts, or PowerShell Core (pwsh) on Linux.
- If the PowerShell module is compatible with PowerShell Core (pwsh) on Linux/macOS, add installation and usage instructions for those platforms.
- Include a section on how to perform common tasks (e.g., importing modules, running commands, handling JSON files) on Linux, using either PowerShell Core or native Linux tools.
- Where possible, use cross-platform command-line examples (e.g., Azure CLI) in addition to or instead of Windows-specific PowerShell cmdlets.
- Review and update prerequisites to mention supported operating systems beyond Windows, if applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/device-builders/release-notes.md
...cles/defender-for-iot/device-builders/release-notes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page shows a mild Windows bias, particularly in the 'March 2024' update, where both Azure CLI and PowerShell commands are mentioned for automating firmware analysis workflows. PowerShell is a Windows-centric tool, and its mention alongside Azure CLI (which is cross-platform) may suggest a Windows-first approach. There are no explicit Linux shell (bash) examples or references to Linux-native tools, and no Linux-specific command-line instructions are provided. However, the rest of the documentation does mention Linux distributions and features relevant to Linux devices, indicating some cross-platform awareness.
Recommendations
- Include Linux shell (bash) command examples alongside or before PowerShell examples when describing automation or CLI workflows.
- When referencing automation tools, clarify the cross-platform availability of Azure CLI and provide explicit instructions for Linux users.
- If PowerShell is mentioned, note that PowerShell Core is available on Linux, or provide equivalent bash commands/scripts.
- Ensure that any screenshots or UI references do not assume a Windows environment unless the feature is genuinely Windows-only.
- Audit linked tutorials and guides to ensure Linux parity in step-by-step instructions and troubleshooting sections.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/best-practices/certificate-requirements.md
...ganizations/best-practices/certificate-requirements.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 Explorer as the reason for specific file extensions (.crt, .key) and does not mention Linux tools or workflows. There are no Linux-specific examples or guidance, and file format explanations are framed in terms of Windows compatibility.
Recommendations
- Include explanations or examples relevant to Linux environments, such as referencing common Linux tools (e.g., OpenSSL, file managers) for certificate handling.
- Clarify that .crt and .key extensions are also widely used and recognized in Linux systems, not just for Windows Explorer compatibility.
- Provide sample commands for certificate generation and validation using cross-platform tools like OpenSSL.
- Avoid framing file format requirements solely in terms of Windows compatibility; instead, describe them in a platform-neutral way.
- Add a section or note about how to manage and use these certificate files on Linux systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/appliance-catalog/virtual-sensor-hyper-v.md
...anizations/appliance-catalog/virtual-sensor-hyper-v.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is exclusively focused on deploying the OT sensor VM using Microsoft Hyper-V on Windows, with all instructions, prerequisites, and terminology tailored to Windows environments. There are no references to Linux-based hypervisors (such as KVM, QEMU, or VirtualBox), nor are there any Linux command-line or tool examples. The only hypervisor mentioned is Hyper-V, and all steps assume use of Windows tools and UI patterns.
Recommendations
- Add parallel instructions for deploying the OT sensor VM on common Linux hypervisors (e.g., KVM/QEMU, VirtualBox, VMware Workstation/ESXi).
- Include Linux-specific prerequisites, such as package requirements and links to Linux hypervisor documentation.
- Provide example commands or UI steps for creating and configuring VMs on Linux platforms.
- Clearly indicate in the introduction that this page is Hyper-V/Windows-specific, and cross-link to Linux/other hypervisor deployment guides if available.
- Ensure parity in detail and clarity between Windows and Linux deployment instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/best-practices/traffic-mirroring-methods.md
...anizations/best-practices/traffic-mirroring-methods.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. While it covers general network mirroring concepts (SPAN, RSPAN, TAP, ERSPAN) that are cross-platform, when discussing virtual switch mirroring, it only provides detailed references for ESXi (VMware) and Hyper-V (a Windows technology). Hyper-V is mentioned alongside ESXi, but there is no mention of Linux-based virtualization platforms (such as KVM, Open vSwitch, or Linux bridges), nor are there any Linux-specific examples or tools referenced. The documentation also lacks Linux command-line or configuration examples, focusing instead on vendor-specific (often Windows-centric) solutions.
Recommendations
- Add examples and references for configuring traffic mirroring on Linux-based virtualization platforms, such as KVM, Open vSwitch, or Linux bridges.
- Include Linux command-line examples for setting up port mirroring (e.g., using 'tc', 'iptables', or 'ip' commands) where appropriate.
- Mention Linux-compatible TAP and aggregation solutions, and provide links to their documentation.
- Ensure that when listing virtualization platforms, Linux-based solutions are included and not only Windows-centric (Hyper-V) or proprietary (ESXi) options.
- Where vendor-specific features are discussed (e.g., Hyper-V, ESXi), provide parity by referencing open-source or Linux-native alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/configure-active-monitoring.md
...r-for-iot/organizations/configure-active-monitoring.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows Endpoint Monitoring (specifically WMI events) as the primary method for active monitoring, without mentioning or providing examples for Linux-based monitoring approaches or tools. Only Windows-specific tools and workflows are referenced, and there are no Linux equivalents or cross-platform guidance.
Recommendations
- Include examples and instructions for configuring active monitoring on Linux-based OT devices or networks.
- Mention and describe Linux-compatible monitoring methods (e.g., syslog, SNMP, or Linux audit logs) alongside Windows methods.
- Ensure that references to Windows tools (like WMI) are balanced with Linux alternatives, and provide links or documentation for both.
- Rephrase sections to avoid Windows-first ordering; present both Windows and Linux options together where possible.
- Add a section or table comparing active monitoring capabilities and configuration steps for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/getting-started.md
...cles/defender-for-iot/organizations/getting-started.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Microsoft and Azure ecosystems, referencing Microsoft 365 admin center, Azure portal, and related tools exclusively. There are no examples, instructions, or references for Linux or cross-platform environments. All procedures assume the user is operating within a Windows-centric or Microsoft cloud environment, with no mention of Linux-based management, CLI tools, or alternative platforms.
Recommendations
- Include instructions for onboarding and managing OT sensors from Linux environments, such as using Azure CLI or REST APIs from Linux terminals.
- Provide examples or references for cross-platform tools (e.g., Azure CLI, PowerShell Core on Linux) where applicable.
- Explicitly mention platform requirements and, if possible, offer parity for Linux users in setup and management steps.
- Add troubleshooting or FAQ sections addressing common issues for Linux users or those not using Windows/Microsoft 365 environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/active-directory-b2c/view-audit-logs.md
...main//articles/active-directory-b2c/view-audit-logs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell script for programmatically accessing audit logs, with no equivalent example for Linux or cross-platform environments (such as Bash, curl, or Python). The use of PowerShell and references to Azure Cloud Shell (which supports PowerShell by default) further reinforce a Windows-centric approach. There is no mention of Linux command-line tools or scripts, nor are there instructions for users on non-Windows platforms.
Recommendations
- Provide a Bash/curl example for accessing the Microsoft Graph API and downloading audit logs, suitable for Linux and macOS users.
- Include a cross-platform example using a language like Python (with the requests library) to demonstrate API access.
- Explicitly mention that the API can be accessed from any platform and provide guidance for users on Linux or macOS.
- Reference Azure Cloud Shell's Bash environment as well as PowerShell, and clarify that both can be used.
- Where possible, use neutral, platform-agnostic language and avoid implying that PowerShell is the only or primary method.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/includes/active-monitoring-protocols.md
.../organizations/includes/active-monitoring-protocols.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page lists 'Windows event scans' as the first and only example of endpoint monitoring, specifically referencing WMI and a Windows-specific configuration link. There are no Linux or cross-platform monitoring examples or references, and only Windows tools and patterns are mentioned.
Recommendations
- Include examples of active monitoring for Linux endpoints, such as using syslog, auditd, or other Linux-native protocols.
- Provide configuration links or documentation for Linux endpoint monitoring alongside Windows examples.
- Reorganize the table or content to present Windows and Linux options with equal prominence, or group them under a more neutral heading such as 'Endpoint event scans'.
- Mention cross-platform or protocol-agnostic monitoring methods if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/includes/self-signed-certificate.md
...-iot/organizations/includes/self-signed-certificate.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows UI elements (such as Windows Explorer, Certificate Export Wizard), using Windows-specific terminology and workflows, and omitting any Linux or cross-platform command-line examples for certificate export or conversion.
Recommendations
- Include equivalent instructions for Linux users, such as using OpenSSL commands to export and convert certificates.
- Mention Linux file managers or command-line tools alongside Windows Explorer.
- Provide screenshots or step-by-step guides for both Windows and Linux environments.
- Avoid assuming the user is on Windows; use neutral language and clarify when steps are OS-specific.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/manage-users-overview.md
...efender-for-iot/organizations/manage-users-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell as the only command-line example for role assignment, referencing Microsoft Entra ID (formerly Azure AD) and Active Directory exclusively for identity management, and omitting any mention of Linux-native tools or workflows. There are no Linux command-line examples or references to Linux user management patterns, and Windows-centric terminology and tools are presented as the default or only option.
Recommendations
- Include equivalent Linux command-line examples (e.g., using Azure CLI on Linux) for user and role management tasks.
- Mention and document how Linux administrators can interact with Defender for IoT, such as through REST APIs, Azure CLI, or other cross-platform tools.
- Reference LDAP and SSO solutions that are common in Linux environments (e.g., OpenLDAP, SSSD, Kerberos) alongside Active Directory.
- Avoid presenting PowerShell or Windows tools as the only or primary method; provide parity in example order and depth for Linux tools.
- Clarify whether on-premises sensors run on Linux and, if so, provide guidance for managing local users via Linux-native commands or interfaces.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/defender-for-iot/organizations/networking-requirements.md
...ender-for-iot/organizations/networking-requirements.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page lists networking requirements for Microsoft Defender for IoT and includes a table of protocols and ports. While the majority of protocols are cross-platform (SSH, HTTPS, SNMP, Syslog, etc.), there is a notable Windows bias: WMI (a Windows-specific monitoring protocol) is mentioned explicitly, with a link to a Windows endpoint monitoring guide, but there is no equivalent mention or guidance for Linux endpoint monitoring. Additionally, LDAP/Active Directory is referenced, which is more common in Windows environments, and appears before more platform-neutral protocols like SNMP or Syslog. There are no Linux-specific monitoring tools or examples provided.
Recommendations
- Add examples or references for Linux endpoint monitoring, such as using SSH, SNMP, or syslog for Linux hosts.
- If WMI is included for Windows, provide parity by mentioning or linking to equivalent Linux monitoring setup (e.g., using SSH, auditd, or other Linux-native tools).
- Reorder the list of protocols so that platform-neutral or cross-platform protocols (SNMP, Syslog, LDAP) are not overshadowed by Windows-specific ones.
- Clarify in the documentation whether Linux endpoints are supported for monitoring, and if so, provide explicit instructions or links.
- Where Active Directory is mentioned, note alternatives for organizations using Linux-based directory services (e.g., OpenLDAP).