13764
Pages Scanned
63
Pages Flagged
13764
Changed Pages
0.5%
% Pages Flagged
Scan Information
Started At: 2025-12-15 00:00:10
Finished At: 2025-12-15 15:11:49
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 13764
Files Completed: 13764
Problematic Pages
63 issues found
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-private-link.md
...nager/management/relocation/relocation-private-link.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page references PowerShell before Azure CLI when describing how to create a Private Link Service, which may suggest a Windows-first or PowerShell-heavy bias. There are no explicit Linux-specific examples or mentions of Bash, and no guidance for Linux users is provided. The documentation does not mention or link to Bash scripts or Cloud Shell, which are common for cross-platform parity.
Recommendations
- List Azure CLI before PowerShell to avoid suggesting a Windows-first workflow.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows.
- Provide Bash script examples or reference the Azure Cloud Shell for cross-platform instructions.
- Ensure that all command-line examples are available in both PowerShell and Bash/Azure CLI formats.
- Add a note clarifying that both PowerShell and Azure CLI are supported on multiple platforms.
Create Pull Request
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/api-center-portal-user-sign-in.md
.../api-center/includes/api-center-portal-user-sign-in.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively references the Azure portal (a web-based GUI) and does not mention or provide examples for command-line or cross-platform tools such as Azure CLI or Azure PowerShell. There are no Linux-specific instructions or parity for users who may prefer or require non-GUI, scriptable, or Linux-native workflows. The guidance implicitly assumes a Windows-centric or GUI-first workflow.
Recommendations
- Add instructions for assigning roles using Azure CLI (az role assignment), which is cross-platform and commonly used on Linux.
- Include Azure PowerShell examples for users who prefer scripting, but ensure Azure CLI examples are given equal or higher prominence.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, but provide alternatives for users who prefer or require command-line tools.
- Where possible, provide links to documentation for both Azure CLI and PowerShell role assignment methods.
- Consider adding a section or note for Linux/macOS users, highlighting cross-platform tools and workflows.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-oauth2.md
...articles/api-management/api-management-howto-oauth2.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a strong Windows and Microsoft ecosystem bias. All examples and step-by-step instructions are centered exclusively around Microsoft Entra ID (Azure AD) as the OAuth 2.0 provider, and all configuration is performed via the Azure Portal, a web interface tightly coupled with the Azure platform. There are no examples or guidance for using non-Microsoft OAuth 2.0 providers, nor are there any command-line examples (e.g., using curl, bash, or cross-platform CLI tools). There is also no mention of Linux-specific tools, patterns, or alternative workflows, and the documentation assumes the use of the Azure Portal UI, which is most familiar to Windows users. The documentation does not provide parity for Linux or open-source environments.
Recommendations
- Add examples and instructions for configuring OAuth 2.0 with non-Microsoft providers (e.g., Auth0, Okta, Keycloak, or generic OAuth 2.0 servers).
- Provide command-line examples using cross-platform tools (e.g., Azure CLI, curl, httpie) for registering applications and configuring OAuth 2.0, in addition to or instead of portal-based instructions.
- Include Linux/macOS-specific notes or workflows where relevant, such as using environment variables, configuration files, or CLI tools.
- Present generic OAuth 2.0 concepts and flows before Microsoft-specific implementations, to reduce the 'windows_first' bias.
- Where possible, show how to accomplish tasks without relying solely on the Azure Portal UI, to support automation and cross-platform scripting.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/cache-vnet-migration.md
...articles/azure-cache-for-redis/cache-vnet-migration.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets (Export/Import-AzRedisCache) and AzCopy without mentioning Linux equivalents or CLI alternatives. PowerShell is presented as the primary automation tool for migration steps, and no Linux shell or cross-platform examples are provided. The documentation does not offer parity for Linux users, omitting az CLI, Bash, or platform-agnostic instructions.
Recommendations
- For every PowerShell cmdlet mentioned, provide equivalent Azure CLI (az) commands and/or Bash examples.
- When referencing AzCopy, clarify that it is cross-platform and provide example commands for both Windows (CMD/PowerShell) and Linux (Bash).
- Add explicit instructions or links for performing migration steps on Linux, including exporting/importing RDB files using az CLI or REST API.
- Avoid listing PowerShell or Windows tools first; instead, present cross-platform or platform-agnostic options before platform-specific ones.
- Include notes or callouts to highlight any platform-specific limitations or differences.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-best-practice-reference.md
...s/durable/durable-functions-best-practice-reference.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation shows mild Windows bias, primarily through the explicit mention of PowerShell as a language to tune for performance, and by referencing Windows-centric tools such as Visual Studio and the Roslyn Analyzer. PowerShell is listed alongside JavaScript and Python, but no equivalent Linux shell or scripting language (e.g., Bash) is mentioned. Diagnostic and development tools like Visual Studio are referenced before cross-platform alternatives. There are no explicit Linux examples or Linux-specific tools mentioned.
Recommendations
- Include Linux shell (e.g., Bash) or cross-platform scripting examples or references, especially in sections discussing language-specific tuning.
- When mentioning Visual Studio, also mention cross-platform editors like Visual Studio Code (with relevant extensions) and CLI tools.
- List cross-platform or Linux-first tools and workflows alongside or before Windows-specific ones.
- If PowerShell is mentioned, consider also referencing Bash or other Linux-native scripting environments for parity.
- Add explicit examples or notes for Linux users where applicable, especially in diagnostics and development workflow sections.
Unknown
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
missing_linux_example
windows_tools
Summary
The documentation provides an example using the Azure PowerShell cmdlet (New-AzApiManagementUser) for adding users, but does not offer equivalent examples for Linux users (e.g., using Azure CLI or REST API). The only programmatic tool mentioned is PowerShell, which is Windows-centric, and there are no Linux-first or cross-platform command-line examples.
Recommendations
- Add equivalent examples using Azure CLI (az apim user create) for adding users, as Azure CLI is cross-platform and widely used on Linux.
- Mention and provide examples for using the Azure REST API to add users, which is platform-agnostic.
- When referencing Azure tools, list Azure CLI and REST API before or alongside PowerShell to avoid Windows-first bias.
- Explicitly state that all operations can be performed from any OS using cross-platform tools, and provide links to relevant documentation for Linux/macOS users.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/deploy-zerto-disaster-recovery.md
...rticles/azure-vmware/deploy-zerto-disaster-recovery.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. The Zerto Cloud Appliance (ZCA) is described as a Windows-only VM, and its components (ZVM and VRA) are specified as Windows services. Windows tooling is highlighted for recovery to Azure Native IaaS VMs, with no mention of Linux alternatives or parity for these components. The documentation provides more detail for Windows-based components and scenarios, while Linux-based components (ZVMA, vRA) are described but lack practical examples or installation guidance. There are no Linux command-line or configuration examples, and Windows tools/patterns are mentioned before Linux equivalents in the ZCA section.
Recommendations
- Provide Linux-based examples and installation instructions for Zerto components where applicable, especially for ZVMA and vRA.
- Clarify whether Linux alternatives exist for ZCA functionality, or explicitly state if Windows is required for certain scenarios.
- Ensure parity in troubleshooting and log collection instructions for both Windows and Linux appliances.
- Include sample workflows or commands for Linux environments alongside Windows examples, especially for deployment, configuration, and log collection.
- Balance the order and detail of Windows and Linux component descriptions to avoid the perception of Windows-first bias.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/overview-ccws.md
...re-docs/blob/main/articles/cyclecloud/overview-ccws.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing Visual Studio Code (a Microsoft tool popular on Windows) as an access method before mentioning SSH, omitting Linux-specific access patterns or examples, and lacking any explicit Linux command-line instructions or references to Linux tools commonly used in HPC environments. The deployment instructions focus on Azure CLI and GUI, without showing Linux shell commands or Linux-native workflow examples.
Recommendations
- Include explicit Linux command-line examples for accessing the sign-in node (e.g., SSH from Linux/macOS terminals).
- Mention Linux-native editors (e.g., Vim, Emacs, Nano) as alternatives to Visual Studio Code for cluster access.
- Provide Linux shell workflow examples for cluster management and job submission.
- Clarify that Azure CLI is cross-platform and show usage from Linux/macOS terminals.
- Add references to Linux tools and patterns commonly used in Slurm/HPC environments.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-virtual-machine-overview.md
...nline/azure-stack-edge-gpu-virtual-machine-overview.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific examples and tools (such as PowerShell and password reset extensions) are mentioned before or more prominently than their Linux equivalents. The workflow and management sections focus on PowerShell and Windows-centric patterns, with Linux examples either missing or referenced only as alternatives. There is a lack of parity in Linux-specific instructions, tools, and troubleshooting guidance.
Recommendations
- Ensure that Linux examples and instructions are provided alongside Windows ones, with equal detail and prominence.
- Include Linux-specific management tools and workflows (e.g., Bash, SSH, Linux password reset methods) in relevant sections.
- Avoid listing Windows methods or tools before Linux equivalents; present both together or alternate their order.
- Expand extension documentation to cover Linux scenarios, such as password reset or custom script extensions for Linux VMs.
- Review linked articles to confirm Linux parity in step-by-step guides and troubleshooting.
- Add explicit notes or tables comparing Windows and Linux VM management tasks, highlighting any differences or limitations.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/sap-change-data-capture-debug-shir-logs.md
...ata-factory/sap-change-data-capture-debug-shir-logs.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively references the Microsoft Integration Runtime Configuration Manager, which is a Windows GUI tool, and provides instructions and screenshots for its use. There are no examples or instructions for performing the same logging or diagnostics tasks on Linux systems, nor is there mention of Linux command-line alternatives or parity.
Recommendations
- Add instructions for sending logs using command-line tools or scripts available on Linux.
- Clarify whether the self-hosted integration runtime supports Linux, and if so, provide equivalent steps for Linux environments.
- Include screenshots or terminal examples for Linux users.
- Mention any limitations or differences in diagnostics/log collection between Windows and Linux platforms.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-heavy-deploy-copy-data-via-nfs.md
...les/databox/data-box-heavy-deploy-copy-data-via-nfs.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. UNC paths (Windows format) are presented as the primary example for accessing shares, with no mention of Linux NFS mount paths in the main table. Windows tools like Robocopy are referenced first, and Linux alternatives are described as 'similar to Robocopy.' Linux-specific instructions and examples are present but appear after Windows-centric terminology and patterns. There is no explicit PowerShell usage, but the overall structure and terminology favor Windows conventions.
Recommendations
- Add NFS mount path examples alongside UNC paths in the share access table, clearly indicating Linux usage.
- Present Linux copy tools (rsync, cp, etc.) before or alongside Windows tools, rather than as alternatives to Robocopy.
- Use platform-neutral terminology when describing shares and access paths (e.g., 'NFS path' instead of only 'UNC path').
- Include explicit Linux and macOS examples in all relevant sections, not just as addendums.
- Clarify that both Windows and Linux are supported equally, and structure examples so that neither platform is implied as primary.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-parameters-variables.md
...articles/data-factory/concepts-parameters-variables.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page provides links to tutorials that focus exclusively on PowerShell, which is primarily a Windows tool. There are no examples or references to Linux-native tools (such as Bash or Azure CLI), nor are there alternative instructions for Linux/macOS users. This creates a bias toward Windows users and may hinder Linux users from following the tutorials.
Recommendations
- Add equivalent examples and tutorials using Azure CLI and/or Bash scripts, which are cross-platform and familiar to Linux users.
- When linking to tutorials, provide both PowerShell and Azure CLI/Bash versions, or clearly indicate which platforms are supported.
- Explicitly mention that PowerShell Core is cross-platform if that is the intended tool, and provide installation instructions for Linux/macOS if relevant.
- Review related content and ensure that Linux users have a clear path to achieve the same outcomes as Windows users.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/ssis-azure-files-file-shares.md
.../articles/data-factory/ssis-azure-files-file-shares.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows authentication, Windows-style environment variables (%TEMP%), and UNC paths. There are no examples or instructions for Linux environments, such as Linux authentication methods, Linux file paths, or cross-platform considerations. All examples and guidance assume a Windows-centric deployment and usage pattern.
Recommendations
- Include examples for Linux environments, such as using /tmp for temporary files and Linux-style file paths.
- Describe how to connect to file shares from Linux-based SSIS IR nodes, if supported, including authentication methods other than Windows authentication.
- Clarify whether Azure-SSIS IR supports Linux nodes and, if not, explicitly state this limitation.
- Provide parity in instructions for both Windows and Linux users, or note platform restrictions where applicable.
- Reference Linux tools and patterns (e.g., mounting SMB shares with mount.cifs, using environment variables like $TMPDIR) alongside Windows equivalents.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data.md
...docs/blob/main/articles/data-factory/transform-data.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation generally maintains platform neutrality, especially for HDInsight activities, which explicitly mention both Windows and Linux clusters. However, there is a subtle Windows bias: SQL Server (a Windows-centric database) is the only on-premises database mentioned for stored procedures, and the only tutorial linked at the end is for Spark using PowerShell, with no Linux shell or cross-platform alternatives. The custom activity section highlights .NET (a Microsoft technology) as the main extensibility path, which may reinforce a Windows-centric approach.
Recommendations
- Add equivalent Linux/bash examples or tutorials alongside PowerShell-based ones, especially in the 'Related content' section.
- Mention cross-platform alternatives (e.g., PostgreSQL, MySQL) or clarify support for Linux-based SQL engines in the stored procedure activity.
- Provide Python or bash scripting examples for orchestration, not just .NET or PowerShell.
- Clarify that custom activities can be implemented in other languages and environments, not only .NET, to encourage Linux-native development.
- Ensure that any references to tools or environments (e.g., SQL Server, PowerShell) are balanced with Linux/open-source equivalents where possible.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-monitoring-built-in-monitor.md
...les/backup/backup-azure-monitoring-built-in-monitor.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-centric backup tools (DPM, MABS, MARS) and providing navigation examples and links that are specific to Windows Server backup management. There are no explicit Linux examples, nor are Linux backup agents or scenarios mentioned. The documentation also references Windows tools and patterns before any Linux equivalents (if any), and omits Linux-specific guidance.
Recommendations
- Include explicit examples and navigation for monitoring Linux-based backup workloads, such as Azure Backup for Linux VMs or Azure Backup Agent for Linux.
- Mention Linux backup agents and supported scenarios alongside Windows tools like DPM, MABS, and MARS.
- Provide parity in documentation by adding Linux-specific notes, screenshots, or links where only Windows examples are currently given.
- Ensure that references to backup items, jobs, and monitoring cover both Windows and Linux environments equally, or clarify any platform-specific limitations.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-manager-for-agri/concepts-ingest-weather-data.md
.../data-manager-for-agri/concepts-ingest-weather-data.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates bias towards Windows environments by providing only Azure PowerShell (ARMClient) command examples, which are typically used on Windows. There is no mention of Linux-compatible tools (such as curl, az CLI, or bash scripts), nor are Linux-specific instructions or examples provided. This may hinder Linux users from easily following the documentation.
Recommendations
- Include equivalent Linux command examples using tools like curl, az CLI, or bash scripts.
- Explicitly mention cross-platform alternatives to ARMClient and Azure PowerShell.
- Provide guidance on installing and using the required tools on both Windows and Linux.
- Ensure that all code snippets are platform-agnostic or provide separate sections for Windows and Linux usage.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-vmcli.md
...s/blob/main/articles/devtest-labs/devtest-lab-vmcli.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page exhibits a Windows-first bias by presenting Windows VM creation as the initial example, referencing Windows images and tools before Linux equivalents, and providing specific PowerShell guidance. Linux examples and tools are included, but are introduced after Windows, and the artifact examples are predominantly Linux-focused only in one section. The guidance for escaping characters in Cloud Shell is more detailed for PowerShell than Bash, and the sample output for artifacts references a Windows artifact.
Recommendations
- Alternate the order of Windows and Linux examples, or present both side-by-side to ensure parity.
- Include Linux VM creation as the first or equally prominent example, with clear references to popular Linux images.
- Provide equivalent detail for Bash and Linux tooling as is given for PowerShell and Windows tools.
- Ensure artifact examples and sample outputs include both Windows and Linux artifacts.
- Explicitly mention Linux remote connection methods (e.g., SSH) before or alongside Windows methods (e.g., RDP), and provide links to Linux documentation where appropriate.
- Review and balance references to Windows-specific images, tools, and patterns throughout the documentation.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/bastion/quickstart-developer.md
...ocs/blob/main/articles/bastion/quickstart-developer.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits a mild Windows bias. While it mentions both Windows and Linux VMs in prerequisites, Windows is consistently listed first (e.g., port 3389 before 22, 'Quickstart: Create a Windows VM' before Linux). Keyboard shortcut examples are only provided for Windows VMs, with no equivalent guidance for Linux desktop environments. There are no Linux-specific connection or troubleshooting examples, and the only keyboard shortcuts discussed are for Windows. There is also an implicit assumption of familiarity with Windows tools and patterns.
Recommendations
- Alternate the order of Windows and Linux references (e.g., sometimes list Linux first).
- Provide Linux desktop environment shortcut examples (e.g., how to send Ctrl+Alt+Del or open a terminal in GNOME/KDE via Bastion).
- Include screenshots or notes about connecting to Linux VMs and what users should expect (e.g., SSH session, desktop environment).
- Add troubleshooting tips or notes for Linux users (e.g., handling clipboard, keyboard mapping issues in Linux sessions).
- Ensure parity in example links and documentation coverage for both Windows and Linux VM scenarios.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-use-cases.md
...articles/databox-gateway/data-box-gateway-use-cases.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily by providing explicit instructions and links for using Azure PowerShell to set blob tiers, without mentioning or providing equivalent Linux/Unix CLI examples (such as Azure CLI or REST API). The mention of SMB protocol for data transfer is presented before NFS, which is more commonly used on Linux systems. There are no examples or guidance tailored to Linux users, and the tooling references (PowerShell) are Windows-centric.
Recommendations
- Include Azure CLI examples for setting blob tiers and managing lifecycle policies, alongside or before PowerShell instructions.
- Explicitly mention NFS as a supported protocol for Linux environments, and provide sample commands for mounting and transferring data using NFS.
- Add guidance for Linux users on how to interact with Data Box Gateway, including shell commands and scripts.
- Reference REST API methods for blob management to ensure cross-platform accessibility.
- Ensure that protocol and tooling references are balanced between Windows and Linux, or presented in a neutral order.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/certificates-and-key-vault.md
...ervices-extended-support/certificates-and-key-vault.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as a primary method for creating Key Vaults, requiring certificates in .PFX format (commonly used in Windows environments), and mentioning Visual Studio as a deployment tool. There are no examples or instructions for Linux users (e.g., using Azure CLI or OpenSSL), nor are Linux certificate formats (such as PEM) discussed. The order of presentation also places Windows-centric tools and formats before any cross-platform alternatives.
Recommendations
- Add instructions and examples for creating and uploading certificates using Azure CLI, which is cross-platform.
- Include guidance for converting or using certificate formats commonly used in Linux (e.g., PEM, CRT) and how to convert them to .PFX if required.
- Provide sample commands for certificate management using OpenSSL, a standard Linux tool.
- Mention Linux-friendly deployment options (e.g., Azure CLI, VS Code) alongside PowerShell and Visual Studio.
- Ensure that references to Windows tools and formats are balanced with equivalent Linux options, and avoid presenting Windows methods first unless they are truly the most universal.
Unknown
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_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is exclusively focused on configuring traffic mirroring using Hyper-V vSwitch, a Windows-specific virtualization technology. All examples and instructions use Windows tools (PowerShell, Hyper-V Manager), and there are no references to Linux virtualization platforms (e.g., KVM, libvirt, Open vSwitch) or equivalent Linux commands. The documentation assumes a Windows environment throughout, with no mention of Linux alternatives or cross-platform considerations.
Recommendations
- Add equivalent instructions for popular Linux virtualization platforms (e.g., KVM/QEMU, libvirt, Open vSwitch) for traffic mirroring.
- Provide Linux command-line examples (e.g., using virsh, ovs-vsctl) alongside PowerShell examples.
- Include a section comparing Hyper-V vSwitch with Linux alternatives, and guidance for users on Linux hosts.
- Clarify in the prerequisites or introduction that the guide is Windows-specific, or provide links to Linux-focused documentation.
- Where possible, use platform-neutral terminology and highlight cross-platform best practices for traffic mirroring.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-cli-python.md
...azure-stack-edge-gpu-deploy-virtual-machine-cli-python.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use Windows PowerShell, Windows paths, and Windows-specific tools (such as certutil.exe and Notepad). There are no Linux or cross-platform equivalents provided for certificate conversion, host file editing, environment variable setting, or Python execution. The workflow and sample outputs are exclusively shown in a Windows context, and instructions for installing Azure CLI are only given for Windows. Linux users are not provided with guidance or examples for performing these tasks on their platform.
Recommendations
- Provide Linux equivalents for all command-line examples, including certificate conversion (e.g., using openssl), editing the hosts file (e.g., using nano or vi), and setting environment variables (e.g., export in bash).
- Include sample outputs from Linux terminals alongside Windows/PowerShell outputs.
- Add instructions for installing Azure CLI and Python dependencies on Linux (e.g., using apt, yum, or pip).
- Mention cross-platform tools (e.g., Azure Storage Explorer, AzCopy) and clarify their availability on Linux.
- Avoid using Windows-specific paths and tools in generic instructions; use platform-agnostic language or provide both Windows and Linux variants.
- Explicitly state that the procedure is cross-platform, and highlight any platform-specific caveats or requirements.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/provider-hana.md
...e-docs/blob/main/articles/sap/monitor/provider-hana.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing PowerShell in the prerequisites and providing a quickstart link for PowerShell, without mentioning or providing equivalent Linux CLI or Bash examples. The ordering of quickstart links places the Azure portal (commonly used on Windows) and PowerShell before any Linux or cross-platform alternatives. There are no Linux-specific instructions, CLI commands, or examples provided, and no mention of Linux tools or patterns for configuration.
Recommendations
- Add equivalent quickstart links and instructions for Azure CLI (az), which is cross-platform and commonly used on Linux.
- Include Bash shell examples for relevant steps, especially for scripting or automation.
- Explicitly mention Linux compatibility and provide guidance for Linux users, such as using the Azure portal from Linux browsers or configuring SAP HANA provider via CLI.
- Ensure that references to PowerShell are balanced with references to Azure CLI or Bash where possible.
- Review and update screenshots and instructions to avoid assumptions of a Windows environment.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-prerequisites.md
...in/articles/expressroute/expressroute-prerequisites.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page shows Windows bias by referencing Azure PowerShell commands as a prerequisite for ExpressRoute Direct enrollment, without mentioning Azure CLI or Bash alternatives. There are no Linux-specific instructions or examples, and the only tooling referenced for setup is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Add Azure CLI (az) command examples alongside or in place of PowerShell commands for subscription enrollment and other setup steps.
- Explicitly mention that Azure CLI is available on Linux, macOS, and Windows, and provide links to relevant CLI documentation.
- Where PowerShell is referenced, clarify if cross-platform PowerShell Core is supported, or provide Bash script equivalents.
- Review all procedural steps to ensure Linux users are not excluded and that parity exists in instructions and tooling references.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/develop/threat-modeling-tool-releases-73511101.md
...rity/develop/threat-modeling-tool-releases-73511101.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively references Windows operating systems, Windows-specific installation patterns (ClickOnce, Windows Menu shortcuts), and does not mention Linux or provide any Linux equivalents or examples. All system requirements and troubleshooting steps are Windows-centric, with no acknowledgment of Linux compatibility or instructions.
Recommendations
- Explicitly state if the tool is Windows-only, or provide information about Linux compatibility if available.
- If Linux is supported, add installation instructions and troubleshooting steps for Linux users.
- Mention Linux system requirements and equivalents to Windows-specific features (e.g., desktop shortcuts, installation methods).
- Provide parity in examples and guidance for both Windows and Linux users, or clearly indicate platform limitations.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-deploy-portal-policy.md
...les/firewall/tutorial-firewall-deploy-portal-policy.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server for the test virtual machine, referencing Remote Desktop (RDP) and Microsoft Edge for testing, and omitting any Linux-based examples or alternatives. There are no instructions for deploying or testing with a Linux VM, nor guidance for connecting via SSH or using Linux-native tools. The only non-portal alternative mentioned is Azure PowerShell, with no mention of Azure CLI or Bash scripting.
Recommendations
- Provide parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the test subnet, including relevant configuration steps.
- Include examples for connecting to the Linux VM using SSH, and for testing outbound connectivity using Linux tools such as curl or wget.
- Mention and provide Azure CLI equivalents for all Azure PowerShell or portal steps, ensuring cross-platform parity.
- When referencing test procedures (e.g., browsing to Google), specify how to perform these actions on both Windows and Linux VMs.
- Avoid assuming the use of Windows-only tools (e.g., Remote Desktop, Microsoft Edge) and offer alternatives for Linux environments.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/how-to/migrate-from-automanage-best-practices.md
...olicy/how-to/migrate-from-automanage-best-practices.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and features (such as Windows Admin Center and Antimalware for Windows) are highlighted with dedicated sections and examples, while Linux equivalents are either mentioned later, less prominently, or omitted. Several policy and extension examples are Windows-specific, and there is a lack of parity in Linux-focused guidance or examples. PowerShell and Windows-centric management patterns are referenced, with little to no mention of Linux command-line tools or workflows.
Recommendations
- Add equivalent Linux management examples and sections, such as using SSH, Linux-specific extensions, or Azure CLI commands for Linux.
- Ensure that for every Windows-specific tool or extension (e.g., Windows Admin Center, Antimalware for Windows), the Linux equivalent (if available) is mentioned with equal prominence and detail.
- Provide Linux-first or at least parallel examples in sections where policies or extensions are described (e.g., show both Windows and Linux policy assignment for Change Tracking, Antimalware, Update Manager, etc.).
- Avoid using only Windows-centric language (e.g., 'manage files without PowerShell') and instead reference cross-platform or Linux-native tools where appropriate.
- Include links to Linux-specific documentation and best practices alongside Windows references.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sentinel/best-practices-data.md
...ocs/blob/main/articles/sentinel/best-practices-data.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and patterns (e.g., Windows Event Forwarding, PowerShell, .NET) are mentioned more frequently and often before Linux equivalents. Some sections provide detailed Windows solutions while Linux solutions are less elaborated or missing. PowerShell is suggested for custom log collection without a Linux scripting equivalent. In several tables, Windows tools are listed as default or primary, with Linux alternatives appearing later or not at all.
Recommendations
- Ensure Linux and Windows solutions are presented with equal detail and prominence in all tables and sections.
- When suggesting PowerShell for custom log collection, also provide equivalent Linux scripting options (e.g., Bash, Python).
- Avoid listing Windows tools (e.g., Windows Event Forwarding) as the default or only solution when Linux alternatives exist; mention both together.
- Expand Linux-specific examples and guidance, especially for custom log collection, enrichment, and agentless scenarios.
- Review and balance the order of presentation so Linux and Windows solutions alternate or are grouped together, rather than consistently leading with Windows.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-cli.md
...articles/storage/blobs/storage-quickstart-blobs-cli.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation generally uses cross-platform Azure CLI commands, but there is a notable Windows bias in the AzCopy section, where only a Windows-style file path ('C:\myDirectory\myFile.txt') is shown in the example. No Linux/macOS path example is provided, and the AzCopy example does not mention or show Linux usage. Additionally, the first and only explicit file path example for AzCopy is Windows-style, which may confuse Linux/macOS users.
Recommendations
- Provide both Windows and Linux/macOS path examples in AzCopy commands, e.g., 'C:\myDirectory\myFile.txt' and '~/myDirectory/myFile.txt'.
- Explicitly state that AzCopy is available on all major platforms and show how to install/use it on Linux/macOS.
- Wherever file paths are shown, clarify the syntax differences for each OS.
- Consider alternating the order of examples or providing tabs for Windows, Linux, and macOS to ensure parity.
- Add a note or section confirming that all shown CLI commands work equally on Linux, macOS, and Windows.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-run-hive.md
...insight/domain-joined/apache-domain-joined-run-hive.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based tools and workflows, such as Excel and ODBC drivers, for testing Apache Ranger policies. All step-by-step instructions and screenshots are centered around Microsoft Excel and Windows authentication dialogs, with no mention of Linux alternatives (e.g., using Beeline, Hive CLI, or Linux-based ODBC/JDBC clients). The prerequisites require Microsoft Office products, and the testing procedures assume a Windows environment. Linux methods for connecting to Hive and validating Ranger policies are only referenced in the 'Next steps' section, not in the main workflow.
Recommendations
- Add parallel instructions for testing Ranger policies using Linux tools such as Beeline, Hive CLI, or command-line JDBC/ODBC clients.
- Include examples of connecting to Hive from a Linux workstation, demonstrating how to authenticate and query with different users.
- Provide sample commands and expected outputs for Linux-based validation of Ranger policies.
- Balance screenshots and step-by-step guides between Windows and Linux environments.
- Mention open-source alternatives to Excel (e.g., LibreOffice, csvkit) for data import and analysis.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub-device-update/device-update-error-codes.md
...les/iot-hub-device-update/device-update-error-codes.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias primarily through the exclusive use and mention of Delivery Optimization (DO), a Windows-specific component, for update delivery. Error codes and troubleshooting are centered around DO, with no mention of Linux equivalents (such as wget, curl, or apt-based mechanisms) or examples for Linux-based IoT devices. The decoding of error codes references Windows-style error handling (errno, hex codes) without Linux-specific context or examples. There are no Linux/POSIX tool references, and the documentation implicitly assumes a Windows environment for update delivery.
Recommendations
- Include Linux-specific error codes and troubleshooting steps for common Linux update mechanisms (e.g., curl, wget, apt, rpm).
- Provide examples of how to decode and interpret error codes on Linux-based devices, referencing Linux/POSIX error handling.
- Mention and document alternative update delivery agents or methods for Linux devices, if supported.
- Ensure parity by listing Linux tools and patterns alongside Windows tools (e.g., Delivery Optimization), or clarify platform-specific applicability.
- Add explicit notes about platform support and differences in update delivery and error handling between Windows and Linux.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/upgrade-to-data-lake-storage-gen2.md
...les/storage/blobs/upgrade-to-data-lake-storage-gen2.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific tools (AzCopy, PowerShell commands) and patterns (mentioning the Windows Azure Storage Blob driver for Hadoop) before their cross-platform or Linux equivalents. Examples and guidance for Linux or bash usage are missing, and the order of tool mentions (PowerShell before Azure CLI) suggests a Windows-first approach. There are no explicit Linux or bash command examples, nor is there mention of Linux-specific tooling or patterns.
Recommendations
- Provide explicit Linux/bash command examples alongside PowerShell, especially for SDK and CLI usage.
- Mention cross-platform tools (e.g., Azure CLI, AzCopy) with equal prominence and clarify their availability on Linux.
- Include references to Linux-specific drivers or patterns for Hadoop workloads, not just the Windows Azure Storage Blob driver.
- Ensure that documentation for command-line operations is balanced between Windows and Linux, with parallel examples.
- Add notes or sections on how Linux users can perform equivalent operations, including installation and usage of tools.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-setup-lab-gpu-1.md
...b/main/articles/lab-services/how-to-setup-lab-gpu-1.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 consistently presenting Windows instructions and tools (such as Control Panel and Task Manager) before Linux equivalents, providing more detailed steps and screenshots for Windows, and referencing Windows-specific validation methods. Linux instructions are often relegated to links or brief notes, with no screenshots or step-by-step guidance provided directly in the document.
Recommendations
- Present Linux and Windows instructions in parallel sections or tables, ensuring equal prominence and detail.
- Include Linux-specific screenshots (e.g., nvidia-smi output, relevant desktop environment tools) for driver validation and GPU monitoring.
- Provide explicit, step-by-step Linux instructions for driver installation and validation, rather than only linking to external pages.
- Mention common Linux tools for GPU monitoring (such as nvidia-smi, watch -n1 nvidia-smi, or GNOME System Monitor) alongside Windows tools like Task Manager.
- Avoid always listing Windows instructions first; alternate or present both together to avoid implicit prioritization.
- Ensure that all examples and validation steps have Linux equivalents, not just references.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-explorers.md
...blob/main/articles/storage/common/storage-explorers.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page lists Microsoft client tools for Azure Storage, but it shows a Windows bias by prioritizing Windows tools (e.g., Visual Studio Cloud Explorer is Windows-only and listed without Linux/macOS equivalents). The table includes platform support, but Windows is mentioned first, and there are no Linux-specific tools or examples. The focus is on Microsoft tools, which are predominantly Windows-centric, with limited cross-platform parity.
Recommendations
- Include Linux-specific client tools or CLI examples (e.g., Azure CLI, azcopy) for managing Azure Storage.
- Provide parity by listing cross-platform alternatives before or alongside Windows-only tools.
- Add usage examples for Linux and macOS environments, such as command-line instructions.
- Highlight third-party tools that offer strong Linux support.
- Clearly indicate platform limitations and suggest alternatives for non-Windows users.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-cloud-tiering-overview.md
.../storage/file-sync/file-sync-cloud-tiering-overview.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is heavily Windows-centric: it only references Windows Server (e.g., NTFS, Windows Server 2016, Event Viewer), uses Windows-specific tools and terminology (e.g., PowerShell cmdlets, Event Viewer, NTFS attributes), and does not mention Linux or provide any Linux-specific guidance or examples. There is no discussion of how Azure File Sync or cloud tiering would operate on Linux systems, nor are there any Linux commands or troubleshooting steps.
Recommendations
- Explicitly state platform support at the beginning of the article (e.g., clarify if Azure File Sync is Windows-only or if there is any Linux support).
- If Linux is supported, provide equivalent Linux examples, commands, and troubleshooting steps (e.g., how to check file attributes, monitor disk space, or view logs on Linux).
- Mention Linux file systems and attributes where relevant (e.g., how tiered files are represented on ext4/xfs, if supported).
- If Azure File Sync is not supported on Linux, add a clear note to that effect to avoid confusion for cross-platform administrators.
- Avoid using only Windows-specific terminology (e.g., NTFS, Event Viewer, PowerShell) without at least referencing Linux equivalents or alternatives.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-scale-out-for-migration.md
...ain/articles/migrate/how-to-scale-out-for-migration.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily biased towards Windows environments. All instructions and examples assume the appliance is deployed on Windows Server (2019/2022), with exclusive use of PowerShell scripts for installation and configuration. Windows-specific tools (CertUtil, IIS, registry edits) are referenced, and there are no Linux equivalents or alternative instructions for deploying or managing the appliance on Linux systems. The documentation does not mention Linux support or provide parity for Linux administrators.
Recommendations
- Explicitly state platform requirements and whether Linux is supported or not at the beginning of the documentation.
- If Linux is supported, provide equivalent instructions for deploying the appliance on Linux, including shell script examples and Linux-specific prerequisites.
- Offer alternative commands for checksum validation (e.g., sha256sum for Linux) alongside CertUtil.
- Clarify whether PowerShell scripts can run on Linux (via PowerShell Core), and provide guidance for Linux environments if possible.
- Mention IIS alternatives for Linux (such as Apache or Nginx) if relevant, or clarify that IIS is a hard requirement.
- Provide troubleshooting and log file locations for Linux, if supported.
- Ensure parity in examples and screenshots for both Windows and Linux environments, or explicitly state the lack of Linux support.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/network-watcher/network-watcher-create.md
...ain/articles/network-watcher/network-watcher-create.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as a primary automation method alongside Azure CLI, with detailed instructions and links for installing PowerShell locally. PowerShell examples and terminology (cmdlets, modules) are prominent, and Windows-centric tools (PowerShell, references to installing PowerShell) are mentioned before or in preference to Linux-native alternatives. The Azure CLI is included and cross-platform, but there is no explicit mention of Linux-specific environments, shell patterns, or considerations. The documentation does not provide Linux shell (bash/zsh) examples, nor does it discuss Linux package managers or installation nuances for CLI tools.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide Linux-specific installation instructions (e.g., apt, yum, zypper).
- Include bash/zsh shell examples for Azure CLI commands, demonstrating usage in native Linux environments.
- Clarify that PowerShell is available on Linux and macOS, and provide links or instructions for installing PowerShell on those platforms.
- Add notes or sections highlighting differences or considerations when running commands on Linux vs. Windows (e.g., environment variables, file paths, shell syntax).
- Ensure that CLI examples are not implicitly Windows-centric (e.g., avoid referencing Windows-only features or patterns unless cross-platform).
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/monitoring-high-churn.md
...b/main/articles/site-recovery/monitoring-high-churn.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation presents Windows-specific monitoring tools (Resource Monitor, Performance Monitor) with detailed step-by-step instructions and screenshots, while Linux tools (iotop, iostat) are mentioned briefly without equivalent detail or visual aids. Windows tools are described first and more extensively, indicating a Windows-first and Windows-tools bias. There is a lack of parity in example depth and guidance for Linux users.
Recommendations
- Provide step-by-step instructions for Linux tools (iotop, iostat), similar to those given for Windows tools.
- Include screenshots or sample outputs for Linux monitoring tools to match the visual aids provided for Windows.
- Mention Linux tools before or alongside Windows tools to avoid Windows-first ordering.
- Expand the list of Linux tools (e.g., atop, dstat, sar) to match the breadth of Windows tool coverage.
- Add links to official documentation or tutorials for Linux monitoring tools, similar to the Windows Performance Monitor link.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-vmm-network-mapping.md
.../articles/site-recovery/hyper-v-vmm-network-mapping.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Hyper-V and System Center Virtual Machine Manager (VMM), which are Windows-centric virtualization and management tools. There are no examples or mentions of Linux-based hypervisors (such as KVM or Xen), nor are there any Linux command-line or tool references. The workflow and terminology are tailored to Windows environments, and Linux equivalents are not discussed.
Recommendations
- Include guidance or references for Linux-based hypervisors (e.g., KVM, Xen) where supported by Azure Site Recovery.
- Provide parallel examples or notes for environments managed by Linux tools (such as oVirt or OpenStack) if applicable.
- Clarify in the introduction that the instructions are specific to Hyper-V/VMM, and link to Linux/other hypervisor documentation if available.
- If Azure Site Recovery does not support Linux-based hypervisors for this scenario, explicitly state this limitation to avoid confusion.
- Add a comparison table or section outlining differences in network mapping setup between Windows (Hyper-V/VMM) and Linux-based virtualization platforms, if supported.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/new-relic/manage.md
...ob/main/articles/partner-solutions/new-relic/manage.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
The documentation exhibits Windows bias, particularly in the 'Monitor App Services using the New Relic agent' section, where it explicitly states that App Service extensions are only supported for app services running on Windows, and that Linux-based App Services are not displayed or supported. There are no Linux-specific instructions, examples, or parity notes elsewhere. The documentation also generally assumes use of the Azure Portal GUI, which is platform-agnostic, but when OS is mentioned, Windows is prioritized or exclusively supported.
Recommendations
- Add explicit documentation or guidance for monitoring Linux-based App Services, or clearly state roadmap/limitations if not supported.
- Where features are Windows-only, provide alternative Linux monitoring approaches or link to relevant Linux documentation.
- Ensure examples and instructions are balanced between Windows and Linux environments, especially for agent installation and management.
- If Linux support is unavailable for certain features, highlight this early in the documentation and suggest alternative solutions for Linux users.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage-actions/storage-tasks/storage-task-quickstart-arm.md
...e-actions/storage-tasks/storage-task-quickstart-arm.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell before Azure CLI in deployment method links, providing both Azure CLI and PowerShell examples for resource cleanup but omitting Linux-specific shell examples (such as Bash), and generally referencing Windows-centric tools (PowerShell) without highlighting Linux alternatives or parity. The deployment instructions and examples do not address Linux-specific usage patterns or provide explicit Bash examples, which may disadvantage Linux users.
Recommendations
- Ensure that Azure CLI (cross-platform) examples are presented before or alongside PowerShell examples, as CLI is more commonly used on Linux.
- Include explicit Bash shell examples for resource group deletion and other commands, demonstrating usage in a Linux environment.
- When referencing deployment methods, provide equal visibility to Azure CLI, Bash, and REST API, not just PowerShell.
- Add notes or sections clarifying cross-platform compatibility and any OS-specific considerations.
- Avoid language or ordering that implies PowerShell is the default or preferred method, unless justified by usage statistics.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-cache-for-redis/includes/cache-delete-resource-group.md
...ache-for-redis/includes/cache-delete-resource-group.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation only provides instructions for deleting Azure resource groups using the Azure portal, which is a graphical interface most commonly accessed from Windows environments. There are no examples or references to command-line methods such as Azure CLI or PowerShell, which would be relevant for Linux users. The lack of Linux-specific or cross-platform instructions creates a Windows-centric bias.
Recommendations
- Add examples for deleting resource groups using Azure CLI (az group delete), which is available on Linux, macOS, and Windows.
- Include PowerShell examples, but ensure they are presented alongside CLI examples for parity.
- Explicitly mention that the Azure portal can be accessed from any OS, and clarify that command-line options are available for automation and scripting.
- Provide links to official documentation for both Azure CLI and PowerShell resource group deletion commands.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/access-tokens.md
...ob/main/articles/active-directory-b2c/access-tokens.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation mentions Microsoft PowerShell as an example HTTP client for testing the POST request, but does not mention or provide examples for Linux or cross-platform tools such as curl or HTTPie. No Linux-specific or cross-platform command-line examples are provided, and the only tool explicitly referenced is PowerShell.
Recommendations
- Add equivalent examples using curl or HTTPie, which are commonly available on Linux and macOS, alongside the PowerShell mention.
- Explicitly state that any HTTP client can be used, and provide at least one cross-platform example.
- Avoid referencing only Windows-specific tools; instead, provide parity by mentioning both Windows and Linux/macOS tools when suggesting ways to test HTTP requests.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/configure-firewall.md
...cs/blob/main/articles/event-grid/configure-firewall.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring IP firewall rules for Azure Event Grid topics or domains. However, the PowerShell section is given equal prominence to the CLI section, and PowerShell is a Windows-centric tool. There are no explicit Linux shell (bash) or scripting examples, nor is there mention of Linux-specific tools or patterns. The documentation does not clarify cross-platform compatibility for PowerShell, nor does it provide guidance for Linux users who may not use PowerShell.
Recommendations
- Add explicit bash shell examples for all CLI commands, showing variable assignment and usage in a Linux shell context.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Add a note about PowerShell Core being available on Linux and macOS, or clarify that the PowerShell examples are for Windows unless otherwise specified.
- Consider providing links to installation instructions for Azure CLI and PowerShell on Linux.
- If possible, add troubleshooting or usage tips specific to Linux environments (e.g., handling environment variables, authentication).
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/common-issues/staging-resources.md
...articles/cyclecloud/common-issues/staging-resources.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses on Azure CycleCloud resource staging issues but only references the Azure portal (a GUI tool commonly used on Windows) for checking Storage Account settings. There are no CLI examples (such as Azure CLI or PowerShell) for checking or modifying permissions, nor are Linux-specific workflows or tools mentioned. This may disadvantage Linux users who prefer command-line operations.
Recommendations
- Add Azure CLI examples for checking and modifying Storage Account permissions and hierarchical namespace settings.
- Include PowerShell examples only alongside equivalent Azure CLI commands, not exclusively.
- Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide platform-agnostic instructions.
- Reference documentation for both GUI (Azure portal) and CLI methods, ensuring parity for Linux users.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/enable-tls-azure-monitor-sap-solutions.md
.../sap/monitor/enable-tls-azure-monitor-sap-solutions.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation does not provide any platform-specific examples or instructions, but it references only the Microsoft Trusted Root Program for certificate authorities, which is primarily Windows-centric. There are no explicit Linux or cross-platform certificate authority references, nor are there examples for Linux environments. The documentation implicitly assumes a Windows-first environment by focusing on Microsoft certificate authority requirements.
Recommendations
- Include references to widely used Linux certificate authorities and how to verify certificates on Linux systems.
- Provide examples or instructions for managing certificates on both Windows and Linux platforms.
- Clarify whether certificates from non-Microsoft (but widely trusted) root programs are supported, and if so, how to use them.
- Add guidance for Linux administrators on how to prepare and upload certificates, including relevant command-line examples.
- Explicitly state cross-platform compatibility and any platform-specific prerequisites or steps.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/encryption-scope-overview.md
...in/articles/storage/blobs/encryption-scope-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page shows mild Windows bias in the 'Disabling an encryption scope' section, where PowerShell is mentioned before CLI when linking to Azure Key Vault soft-delete documentation. No Linux-specific tools or examples are provided, and PowerShell is referenced as the first option, which may suggest a preference for Windows environments.
Recommendations
- When referencing command-line tools, mention cross-platform options (such as Azure CLI) before or alongside PowerShell.
- Provide explicit examples or links for both PowerShell and CLI in parallel, clarifying that Azure CLI is cross-platform and suitable for Linux and macOS users.
- Avoid implying that PowerShell is the default or primary tool, especially in cross-platform documentation.
- Consider including Bash or Azure CLI script examples where relevant, to ensure Linux parity.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-quickstart-kafka-enabled-event-hubs.md
...hubs/event-hubs-quickstart-kafka-enabled-event-hubs.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by explicitly requiring the creation of a Windows virtual machine and referencing Windows-specific configuration steps. There are no instructions or examples for Linux or cross-platform environments, and all setup steps (including managed identity configuration) are described only for Windows VMs. The prerequisites and walkthroughs omit Linux equivalents or mention them after Windows, if at all.
Recommendations
- Add instructions for creating and configuring a Linux virtual machine, including managed identity setup.
- Provide cross-platform examples for installing prerequisites (JDK, Maven, Git) on both Windows and Linux.
- Reference Azure documentation for configuring managed identities on Linux VMs alongside Windows.
- Ensure command-line examples use syntax compatible with both Windows (cmd/PowerShell) and Linux (bash/sh).
- Explicitly state that the quickstart works on both Windows and Linux, and provide parity in screenshots and walkthroughs.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-container-lease.md
...articles/storage/blobs/storage-blob-container-lease.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation is focused exclusively on .NET and C# examples, which are most commonly associated with Windows development environments. There are no examples or guidance for using equivalent tools or libraries on Linux, nor is there mention of cross-platform considerations, such as running .NET code on Linux or using alternative languages/tools popular in Linux environments. The documentation implicitly assumes a Windows/.NET-centric workflow.
Recommendations
- Add explicit guidance or examples for running .NET code on Linux, including any platform-specific setup steps.
- Mention and link to cross-platform .NET (Core/6/7+) usage, and clarify that the .NET SDK and Azure Storage client libraries are supported on Linux and macOS as well as Windows.
- Provide alternative code samples or references for popular Linux scripting environments (e.g., Bash with Azure CLI, Python with Azure SDK) for managing container leases.
- Include a section on platform compatibility and any differences or considerations when running the code on Linux versus Windows.
- Avoid language that implicitly ties .NET development to Windows; highlight .NET's cross-platform capabilities.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-deploy-portal.md
...n/articles/firewall/tutorial-firewall-deploy-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively uses Windows Server as the example operating system for the test virtual machine, and all testing instructions (such as remote desktop and browser usage) assume a Windows environment. There are no Linux equivalents or alternative instructions provided, and the only OS image suggested is Windows Server 2019 Datacenter. This creates a bias toward Windows users and may hinder Linux users from following the tutorial.
Recommendations
- Provide parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu Server) in the test subnet, including relevant configuration steps.
- Include Linux-specific testing instructions, such as using SSH for remote access and using browsers or command-line tools (curl, wget) to test outbound connectivity.
- Mention Linux as an option when creating the VM, and provide guidance on configuring DNS and firewall rules for Linux environments.
- Where remote desktop (RDP) is referenced, add instructions for connecting via SSH for Linux VMs.
- Ensure screenshots and examples are OS-agnostic or provide both Windows and Linux variants.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/events/events-disable-delete-workspace.md
...lthcare-apis/events/events-disable-delete-workspace.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation provides only Azure Portal (GUI) instructions and does not include any command-line examples. There is no mention of cross-platform CLI tools (such as Azure CLI or Azure PowerShell), nor are there any Linux-specific instructions. This implicitly favors Windows users, as GUI workflows are often associated with Windows environments, and omits parity for Linux users who may prefer or require CLI-based operations.
Recommendations
- Add Azure CLI examples for deleting event subscriptions and workspaces, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- If relevant, include Azure PowerShell examples, but ensure Azure CLI examples are presented first or alongside them.
- Explicitly mention that the operations can be performed using CLI tools on Linux, and provide links to relevant CLI documentation.
- Clarify that the Azure Portal is accessible from any OS, but also provide non-GUI alternatives for automation and scripting.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/how-to-provision-devices-at-scale-linux-tpm.md
...ot-edge/how-to-provision-devices-at-scale-linux-tpm.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is focused on Linux devices but introduces a Windows bias in the virtual TPM scenario by exclusively recommending Hyper-V (a Windows-only virtualization tool) and requiring a Windows development machine for simulated TPM testing. The instructions for creating a Linux VM with a simulated TPM are entirely based on Hyper-V, with no mention of Linux-native virtualization alternatives (e.g., KVM, QEMU, VirtualBox). The Windows/Hyper-V methodology is presented as one of two main approaches, and its prerequisites and steps are described before any Linux-native alternatives, which are absent.
Recommendations
- Add instructions for creating a Linux VM with a simulated TPM using Linux-native virtualization tools such as KVM, QEMU, or VirtualBox.
- Provide parity in examples and tooling for both Windows and Linux environments, ensuring that Linux users are not required to use Windows/Hyper-V for simulated TPM scenarios.
- Clearly indicate platform-specific requirements and offer alternative workflows for Linux-only users.
- Consider reordering or parallelizing instructions so that Linux-native options are presented alongside Windows/Hyper-V, rather than Windows-first.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-hub/monitor-iot-hub.md
...ure-docs/blob/main/articles/iot-hub/monitor-iot-hub.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page exhibits a mild Windows bias. In the SDK version examples, only Windows platforms are shown (e.g., Node.js on Windows, .NET on Windows), with no Linux or cross-platform examples. Additionally, the .NET SDK (commonly associated with Windows) is highlighted, and the only Event Hubs client sample linked is for .NET. There are no explicit Linux or cross-platform command-line or tool examples, nor are Linux-specific tools or environments mentioned. However, the majority of the content is platform-agnostic, focusing on Azure portal usage and Kusto queries.
Recommendations
- Include SDK version examples for Linux and macOS platforms (e.g., Node.js on Ubuntu, Python on macOS) to demonstrate cross-platform support.
- When referencing Event Hubs client samples, provide links to samples in other languages/platforms (e.g., Python, Java, Node.js) in addition to .NET.
- Explicitly mention that the Azure portal and Azure Monitor features are available and supported on all major operating systems.
- Where relevant, add command-line examples using cross-platform tools such as Azure CLI or Azure PowerShell (with notes on cross-platform compatibility), and provide equivalent instructions for Linux environments.
- Ensure that screenshots and instructions do not imply a Windows-only environment (e.g., avoid showing only Windows file paths or UI elements if possible).
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-edge/includes/iot-edge-clean-up-cloud-resources.md
...iot-edge/includes/iot-edge-clean-up-cloud-resources.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation only describes deleting Azure resources via the Azure portal, which is a graphical interface commonly associated with Windows workflows. There are no examples or instructions for performing the same actions using cross-platform tools such as the Azure CLI or Azure PowerShell, which are available on Linux and macOS as well. This can be interpreted as a subtle Windows bias, as Linux users often prefer or require command-line instructions.
Recommendations
- Add Azure CLI examples for deleting resource groups and resources, as the CLI is cross-platform and widely used on Linux.
- If relevant, include Azure PowerShell examples, but ensure they are presented after CLI examples or clearly marked as optional.
- Explicitly mention that the Azure portal is accessible from any OS, but provide parity with command-line instructions for Linux users.
- Consider adding a section titled 'Delete resources using Azure CLI' with step-by-step commands.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/how-to-manage-lab-plans.md
.../main/articles/lab-services/how-to-manage-lab-plans.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes managing lab plans via the Azure portal, which is a web-based GUI. There are no command-line examples, and no mention of platform-specific tools. However, the Azure portal experience is typically more familiar to Windows users, and there is no coverage of managing lab plans using cross-platform tools such as Azure CLI, which are commonly used on Linux and macOS. This omission may disadvantage Linux users who prefer or require command-line workflows.
Recommendations
- Add examples for managing lab plans using Azure CLI, which is available on Windows, Linux, and macOS.
- Include PowerShell examples only if parity is maintained with Azure CLI or Bash.
- Explicitly mention that the Azure portal is accessible from any OS, but provide alternative instructions for users who prefer command-line or automation approaches.
- Link to documentation for Azure CLI and REST API methods for lab plan management.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/storage-explorer/vs-azure-tools-storage-explorer-accessibility.md
...lorer/vs-azure-tools-storage-explorer-accessibility.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation demonstrates bias by explicitly stating that screen readers are not supported on Linux, while recommending options for Windows and Mac. Additionally, Windows is listed first in the platform table. There are no Linux-specific accessibility recommendations, tools, or keyboard shortcut differences discussed, and the guidance assumes parity or omits Linux where support is lacking.
Recommendations
- Investigate and document any available Linux screen readers (e.g., Orca), even if not officially supported, and provide guidance or caveats for Linux users.
- Clarify if keyboard shortcuts differ on Linux, and explicitly state any known issues or limitations.
- List platforms in alphabetical order or rotate the order to avoid implicit prioritization.
- Provide Linux-specific accessibility tips or workarounds, or link to relevant community resources.
- Regularly review Linux support and update the documentation as support improves.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/includes/event-generator-app.md
...icles/stream-analytics/includes/event-generator-app.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation demonstrates a bias towards Windows by only providing instructions and examples for running the TelcoGenerator application using a Windows executable (.exe) and Windows command prompt syntax. There are no examples or guidance for running the event generator on Linux or macOS, nor are alternative cross-platform tools or methods mentioned.
Recommendations
- Provide instructions for running the TelcoGenerator application on Linux and macOS, if possible (e.g., via Mono, .NET Core, or an alternative cross-platform tool).
- Include Linux/macOS command-line examples (e.g., using bash/terminal) alongside the Windows command prompt example.
- If the TelcoGenerator tool is Windows-only, suggest equivalent open-source or cross-platform event generator tools for Linux/macOS users.
- Explicitly state platform requirements and provide guidance for users on non-Windows systems.
- Consider providing a Docker container or script that can be run on any platform to generate the sample data.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/job-config-json.md
...blob/main/articles/stream-analytics/job-config-json.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page consistently references Visual Studio Code as the tool for creating and managing Azure Stream Analytics jobs, without mentioning or providing examples for alternative editors or command-line tools commonly used on Linux. There are no explicit Linux-specific instructions or examples, and the workflow is described solely in the context of Visual Studio Code, which, while cross-platform, is often associated with Windows environments. No PowerShell or Windows command-line tools are mentioned, but the lack of Linux-specific guidance or parity is notable.
Recommendations
- Explicitly state that Visual Studio Code is available on Linux, macOS, and Windows to clarify cross-platform support.
- Provide alternative instructions or examples using common Linux tools (e.g., Vim, Emacs, nano, or command-line JSON editors) for editing JobConfig.json.
- Include CLI-based workflows (e.g., using Azure CLI or Bash scripts) for creating and managing Stream Analytics jobs, in addition to Visual Studio Code.
- Add a section or note highlighting Linux compatibility and any platform-specific considerations for users not on Windows.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/migrate-tutorial-on-premises-azure.md
...es/site-recovery/migrate-tutorial-on-premises-azure.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation focuses on migration scenarios for VMware VMs, Hyper-V VMs, and physical servers, but does not provide explicit examples or guidance for Linux-specific migration workflows. The order of presentation (VMware, then Hyper-V, then physical servers) may implicitly prioritize Windows-centric environments, and there are no Linux command-line or tool references, nor examples for Linux-only migration cases.
Recommendations
- Add explicit examples and guidance for migrating Linux servers, including common Linux distributions.
- Include references to Linux command-line tools and scripts for preparing machines for migration.
- Provide parity in step-by-step instructions for both Windows and Linux environments, ensuring Linux administrators have clear, actionable guidance.
- Mention Linux-specific considerations (e.g., handling of SSH keys, filesystems, or services) in migration scenarios.
- Balance the order of presentation so that Linux migration options are not implicitly deprioritized.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/devops-tutorial.md
...s/blob/main/articles/sap/automation/devops-tutorial.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation does not provide explicit examples or instructions for Linux environments, nor does it mention Linux tools or shell commands. It implicitly assumes a Windows-centric approach by referencing Azure DevOps Services pipelines and self-hosted agents without clarifying cross-platform compatibility or providing Linux-specific guidance. There is also no mention of Linux-based self-hosted agents or how to configure them, which may lead users to assume a Windows-first bias.
Recommendations
- Add explicit instructions or examples for setting up and running pipelines using Linux-based self-hosted agents.
- Clarify that the SAP Deployment Automation Framework and Azure DevOps pipelines are cross-platform, if applicable, and provide guidance for both Windows and Linux environments.
- Include Linux shell command examples where relevant (e.g., for agent setup, file manipulation, or troubleshooting).
- Mention any Linux-specific prerequisites or considerations, such as required packages or permissions.
- Ensure screenshots and UI references are not exclusively from Windows environments, or provide Linux equivalents if differences exist.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/includes/oracle-dnfs.md
...in/articles/azure-netapp-files/includes/oracle-dnfs.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples or guidance. However, given the context (Oracle dNFS deployments, which are predominantly on Linux/UNIX systems), the absence of explicit Linux examples or references may leave Linux administrators without clear, actionable steps. There is no evidence of explicit Windows bias (e.g., Windows/Powershell examples, Windows tools, or Windows-first ordering), but the lack of Linux-specific guidance in a Linux-centric scenario is a notable omission.
Recommendations
- Add explicit Linux examples or references for Oracle dNFS patching, as most Oracle dNFS deployments occur on Linux/UNIX systems.
- Clarify any platform-specific steps or considerations, especially for Linux environments.
- If Windows is not supported or relevant for Oracle dNFS, state this clearly to avoid confusion.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/cost-management-error-codes.md
...anagement-billing/costs/cost-management-error-codes.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides troubleshooting steps for Azure Cost Management errors but does not include any platform-specific examples or instructions. However, where examples of client tools or scripts could be relevant (such as API usage, Power BI integration, or portal actions), only Power BI is mentioned as a tool for data retrieval, which is primarily a Windows application. There are no Linux-specific tools, CLI examples, or cross-platform alternatives referenced, nor is there any mention of using Azure CLI, Bash, or other Linux-friendly approaches. The documentation implicitly assumes a Windows-centric workflow by omitting Linux parity.
Recommendations
- Include examples using Azure CLI (az) commands for troubleshooting, alongside any portal or API instructions.
- Reference cross-platform data analysis tools (such as Jupyter Notebooks, pandas, or open-source BI tools) in addition to Power BI.
- Provide sample API calls using curl or httpie, which are commonly used on Linux and macOS.
- Explicitly state that the troubleshooting steps apply regardless of operating system, and highlight any platform-specific considerations.
- If scripts or automation are discussed, offer both PowerShell and Bash script examples.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/events/events-enable-diagnostic-settings.md
...hcare-apis/events/events-enable-diagnostic-settings.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also does not include any Linux- or cross-platform command-line examples. The absence of CLI (e.g., Azure CLI, Bash) or Linux-specific guidance may disadvantage Linux users, especially if Windows or PowerShell is the default in related documentation.
Recommendations
- Add explicit Azure CLI examples for enabling diagnostic settings, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- If PowerShell or Windows-specific tools are referenced in related documentation, ensure parity by including equivalent Bash or CLI commands.
- Clarify in the documentation that the steps can be performed from any OS via the Azure Portal, and provide links to CLI documentation for automation scenarios.
- Consider adding a section or note about cross-platform compatibility and how to perform these tasks from Linux environments.