Scan Details - Linux-first Docs for Azure

Communication Services Automate email resource management ...nication-services/samples/email-resource-management.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides resource management automation examples primarily using PowerShell, with PowerShell commands shown for deleting Email Communication Services and Domain resources. While an Azure CLI example is given for deleting a Communication Services resource, equivalent CLI commands for Email and Domain resources are missing. The organization and examples favor Windows/PowerShell users, creating friction for Linux/macOS users who may not have access to PowerShell or its Azure modules.

Recommendations

Add Azure CLI examples for deleting Email Communication Services and Domain resources, ensuring parity with PowerShell commands.
Clearly indicate which commands are platform-specific and provide alternative instructions for Linux/macOS users.
Reorganize examples so that cross-platform tools (Azure CLI, Python SDK) are presented before or alongside PowerShell examples.
Consider including sample scripts for resource cleanup in Python or Bash where possible.

Create Pull Request

Firewall Deploy Azure Firewall with Availability Zones ...ticles/firewall/deploy-availability-zone-powershell.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation provides only Azure PowerShell examples for deploying Azure Firewall with Availability Zones, without any equivalent examples for Azure CLI, ARM templates, or Bicep. This creates friction for Linux/macOS users, who typically use Azure CLI or template-based deployments rather than PowerShell. The exclusive use of PowerShell commands and lack of cross-platform guidance is a notable bias.

Recommendations

Add Azure CLI examples for deploying Azure Firewall with Availability Zones, as Azure CLI is cross-platform and widely used on Linux/macOS.
Include ARM template and/or Bicep deployment examples to provide platform-agnostic, infrastructure-as-code options.
Clearly indicate that PowerShell is just one of several supported methods and link to documentation for other deployment approaches.
Consider reordering or presenting examples for CLI and templates before or alongside PowerShell to signal equal support.

Create Pull Request

Sap Exchange Online Integration for Email-Outbound from SAP ABAP Platform | Microsoft Docs ...oads/exchange-online-integration-sap-email-outbound.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first

Summary

The documentation page demonstrates a moderate Windows bias. PowerShell is the only automation example provided for configuring Entra ID and Exchange Online, and Exchange Admin Center/Cloud Shell instructions are Windows-centric. Linux alternatives for scripting or CLI-based configuration are not mentioned, and PowerShell is referenced as a prerequisite for automation. Additionally, Windows/PowerShell tools are mentioned before any generic or cross-platform alternatives, and Linux-specific guidance is missing for key steps.

Recommendations

Provide equivalent automation examples using cross-platform tools such as Azure CLI, Microsoft Graph API, or Bash scripts for Linux/macOS users.
Clarify whether PowerShell 7.x is required or if the steps can be performed using Azure CLI or REST API calls, which are available on Linux/macOS.
Include notes or links to Linux/macOS-compatible methods for accessing Exchange Online and Entra ID (e.g., using browser-based portals, Azure CLI, or Graph API).
Explicitly state which steps are platform-agnostic and which require Windows-specific tools, and offer alternatives where possible.
Add a brief section or callout for Linux/macOS users, outlining any differences or additional steps needed.

Create Pull Request

Sentinel Manage custom content with repository connections ...cs/blob/main/articles/sentinel/ci-cd-custom-content.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page for managing custom content with repository connections in Microsoft Sentinel demonstrates a notable Windows bias. PowerShell scripts and utilities are referenced as the primary or sole tooling for converting and exporting content types (analytic rules, automation rules, playbooks, etc.), with minimal or no mention of Linux/macOS equivalents. In several cases, PowerShell is listed before Azure CLI, and some content types lack any non-Windows export/conversion guidance. There are no Bash, shell, or cross-platform examples provided, and the workflow customization section refers to PowerShell deployment scripts without alternatives.

Recommendations

Provide equivalent Azure CLI, Bash, or cross-platform examples for all major tasks, especially for exporting and converting content.
When referencing scripts or utilities, indicate platform compatibility and offer alternatives for Linux/macOS users.
List Azure CLI or other cross-platform tools before PowerShell when both are supported.
Expand documentation to include instructions for Linux/macOS environments, such as using shell scripts or Docker containers for automation.
Clarify which steps are Windows-specific and which are platform-agnostic.

Create Pull Request

Data Factory Source control ...docs/blob/main/articles/data-factory/source-control.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ powershell_heavy

Summary

The documentation page for Azure Data Factory source control is generally cross-platform and focuses on Git integration via Azure Repos and GitHub, both of which are platform-agnostic. However, there are several mentions of using PowerShell and the SDK for publishing changes directly to the Data Factory service, with no equivalent Linux/macOS CLI examples or references to Azure CLI. This may create friction for non-Windows users who do not use PowerShell.

Recommendations

Where PowerShell is mentioned for interacting with Data Factory (e.g., publishing changes, updating repoConfiguration), add equivalent Azure CLI or REST API examples and links.
Explicitly state that PowerShell is not required and provide guidance for Linux/macOS users on how to perform these actions using platform-agnostic tools.
Add a short section or note on cross-platform tooling for Data Factory automation, highlighting Azure CLI and REST API usage.

Create Pull Request

Storage SMB File Shares in Azure Files ...blob/main/articles/storage/files/files-smb-protocol.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation provides extensive PowerShell and Windows-specific guidance, especially for advanced SMB configuration (e.g., enabling SMB Multichannel on older OSes, setting encryption ciphers), but does not offer equivalent Linux/macOS client configuration examples. While Azure CLI examples are present (which are cross-platform), client-side instructions for Linux/macOS (such as how to configure SMB encryption or multichannel support) are missing. Windows terminology and tools (e.g., PowerShell, registry edits, Set-SmbClientConfiguration) are referenced exclusively or before any Linux alternatives.

Recommendations

Add Linux and macOS client configuration examples for SMB Multichannel and SMB encryption settings, including how to check and enable these features using smb.conf or relevant tools.
Where PowerShell or Windows registry edits are shown, provide analogous steps for Linux/macOS (or explicitly state if not supported).
When referencing client-side configuration (e.g., setting encryption ciphers), include commands for Linux (e.g., using mount.cifs options or smb.conf parameters).
Balance the order of examples so that Linux/macOS are not always listed after Windows, especially in sections not inherently Windows-specific.
Clarify any features that are Windows-only, and explicitly note if equivalent Linux/macOS functionality is unavailable.

Create Pull Request

VPN Gateway Create site-to-site high bandwidth tunnels in the Azure portal ...cles/vpn-gateway/site-to-site-high-bandwidth-tunnel.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page demonstrates a notable Windows bias in its Azure CLI instructions, specifically by providing only PowerShell examples for critical configuration steps (such as enabling FastPath and PrivateLinkFastPath on ExpressRoute connections). There are no equivalent Azure CLI (cross-platform) or Bash examples for these operations, and PowerShell commands are presented first and exclusively. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Bash/CLI workflows.

Recommendations

Provide Azure CLI (az) command equivalents for all PowerShell-based configuration steps, especially for enabling FastPath and PrivateLinkFastPath on ExpressRoute connections.
Clearly indicate when a step can be performed in the Azure portal, PowerShell, or CLI, and offer parity in instructions.
Add notes or links for Linux/macOS users on how to accomplish the same tasks without PowerShell.
Consider reordering examples so that cross-platform (CLI/portal) instructions are presented before or alongside PowerShell.

Create Pull Request

Storage Improve SMB Azure File Share Performance ...cs/blob/main/articles/storage/files/smb-performance.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both Windows and Linux guidance for SMB Multichannel, including explicit Linux kernel and mount command examples. However, Windows tools (robocopy, diskspd.exe) and PowerShell commands are used exclusively for performance testing and configuration verification, with no Linux equivalents or parity in example tooling. Windows configuration and verification steps are described in greater detail and appear before Linux examples. Feature registration instructions are given only for Azure Portal and Azure PowerShell, with no mention of Azure CLI or ARM templates, which are cross-platform.

Recommendations

Add Linux equivalents for performance testing, such as using fio or dd for load generation and performance measurement.
Provide Linux commands for verifying SMB Multichannel configuration and status (e.g., using smbstatus, dmesg, or reviewing mount options).
Include Azure CLI or ARM template instructions for feature registration, not just Azure PowerShell, to improve cross-platform accessibility.
Balance the order of Windows and Linux sections/examples so Linux is not always presented after Windows.
Reference Linux documentation for SMB Multichannel alongside Windows documentation in the 'Next steps' section.

Create Pull Request

Sentinel This file is auto-generated . Do not edit manually. Changes will be overwritten. ...b/main/articles/sentinel/includes/connector-details.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation for Microsoft Sentinel data connectors is largely cross-platform, but there are several instances where Windows-specific tools, patterns, or terminology are mentioned before their Linux equivalents, or where Windows is implicitly prioritized. For example, connectors such as 'IIS Logs of Microsoft Exchange Servers', 'Microsoft Active-Directory Domain Controllers Security Event Logs', and 'Windows DNS Events via AMA' focus on Windows event sources and reference Windows agents. Additionally, some sections refer to 'Windows machines' or 'Windows agent' without always providing Linux alternatives or mentioning Linux parity, even when the underlying Azure Monitor Agent supports both platforms.

Recommendations

Wherever possible, clarify when connectors or agents are cross-platform (e.g., Azure Monitor Agent supports both Windows and Linux) and provide explicit instructions or notes for Linux/macOS users.
When listing event sources or log types (e.g., IIS, Windows Event Logs), consider also mentioning common Linux equivalents (e.g., Apache/Nginx logs, Syslog) and linking to relevant connectors.
Avoid using 'Windows machines' or 'Windows agent' as the default terminology in generic sections—use 'machines' or 'agents' and specify platform differences only where necessary.
For connectors that are Windows-specific by necessity (e.g., IIS logs, Windows Firewall), clearly label them as such to set user expectations.
Ensure that any prerequisites or setup steps referencing PowerShell, Windows Event Viewer, or other Windows tools also provide Linux/CLI alternatives where applicable.

Create Pull Request

Container Apps Tutorial: Enable Azure Container Apps on Azure Arc-enabled Kubernetes ...in/articles/container-apps/azure-arc-enable-cluster.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both Azure CLI (bash) and PowerShell examples for every step, but consistently presents PowerShell as a first-class option alongside bash. There are no Linux/macOS-specific instructions or troubleshooting notes, and PowerShell examples are shown in parallel with bash, which may suggest a Windows-centric approach. However, all commands are cross-platform (Azure CLI and kubectl), and Linux users can follow the bash examples without issue.

Recommendations

Clarify that PowerShell examples are intended for Windows users, and bash/Azure CLI examples are for Linux/macOS.
Consider labeling tabs as 'Linux/macOS (bash)' and 'Windows (PowerShell)' for greater clarity.
Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, base64 flags differences).
Ensure that any tool or command with platform-specific behavior is explained for both environments.

Create Pull Request

App Service Configure Managed Instance on Azure App Service (Preview) ...ain/articles/app-service/configure-managed-instance.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ windows_only_feature ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

This documentation is focused exclusively on configuring Managed Instance on Azure App Service, which is a Windows-only feature. All examples, configuration scripts, and tooling references (e.g., PowerShell, MSI installers, Windows Registry, RDP) are specific to Windows environments. There are no Linux/macOS equivalents or examples, and the documentation makes clear that only Windows Server 2022 is supported. The configuration scripts must be PowerShell (.ps1), and all customization patterns are Windows-centric.

Recommendations

No Linux parity recommendations are needed, as this feature is intentionally Windows-only.
Consider adding a clear upfront note or callout stating that Managed Instance on Azure App Service is Windows-only and not available for Linux workloads, to prevent confusion for cross-platform users.
If a Linux equivalent is planned in the future, provide roadmap or guidance for Linux users.

Create Pull Request

Azure Cache For Redis Configure active geo-replication for Enterprise Azure Cache for Redis instances ...cache-for-redis/cache-how-to-active-geo-replication.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for configuring active geo-replication, but PowerShell examples are given equal prominence and detail as CLI, and the section order presents CLI first. There is no evidence of exclusive use of Windows tools or missing Linux/macOS examples, as Azure CLI is fully cross-platform. No Windows-only tools or patterns are referenced, and all steps can be completed from Linux/macOS using Azure CLI. However, the inclusion of PowerShell examples may be less relevant for Linux/macOS users, as PowerShell is less commonly used on those platforms.

Recommendations

Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
Optionally, add a note that PowerShell is available on Linux/macOS, but CLI is more commonly used.
Consider showing CLI examples first and marking PowerShell as 'for Windows users or those who prefer PowerShell'.
Ensure screenshots and portal instructions do not assume Windows-specific UI elements.

Create Pull Request

Scan Information

Problematic Pages