Scan Details - Linux-first Docs for Azure

API Management Use Managed Identities in Azure API Management | Microsoft Docs ...t/api-management-howto-use-managed-service-identity.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 provides detailed examples for Azure PowerShell and the Azure Portal, both of which are most commonly used on Windows. There are no CLI (az) or Bash examples, nor any mention of Linux/macOS-specific workflows. PowerShell is featured as the only command-line automation method, and its installation instructions are referenced, which may be confusing or less accessible for Linux/macOS users. The ARM template examples are cross-platform, but the lack of Azure CLI or Bash scripting creates friction for non-Windows users.

Recommendations

Add equivalent Azure CLI (az) examples for all PowerShell workflows, including creating and updating managed identities.
Explicitly mention that Azure CLI and Bash can be used on Linux/macOS and provide links to relevant guides.
Reorder sections so that cross-platform methods (ARM templates, Azure CLI) are presented before or alongside PowerShell.
Clarify that PowerShell is available on Linux/macOS, but provide CLI alternatives for users who prefer native tools.
Include notes or links for Linux/macOS users regarding prerequisites and environment setup.

Create Pull Request

Backup Delete a Microsoft Azure Recovery Services Vault ...blob/main/articles/backup/backup-azure-delete-vault.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 exhibits a notable Windows bias. PowerShell is the primary automation example, with extensive PowerShell cmdlets and scripts provided, and explicit instructions for installing PowerShell 7. Windows-specific backup management tools (MARS, MABS, DPM) are referenced throughout, with GUI instructions for their consoles. The ARMClient tool is suggested for advanced deletion, but its installation is described only via Chocolatey (a Windows package manager), and usage examples are Windows-centric. The Azure CLI section is brief, limited in scope, and notes that CLI support is incomplete. There are no Bash, Linux-native, or macOS-specific examples or guidance for users who do not use Windows or PowerShell.

Recommendations

Provide equivalent Bash/Azure CLI scripts for all major operations, especially for deleting backup items and vaults.
Clarify how to perform all steps on Linux/macOS, including how to install and use ARMClient on those platforms (e.g., via .NET Core or as a cross-platform tool).
Mention and prioritize cross-platform tools (like Azure CLI) before Windows-specific tools, or at least present them in parallel.
Add guidance for managing Recovery Services vaults using the Azure Portal and Azure CLI for all supported backup types, not just Azure VMs.
Where PowerShell is used, clarify that PowerShell Core (v7+) is cross-platform, and provide installation instructions for Linux/macOS.
If certain features are Windows-only (e.g., MARS, MABS, DPM), clearly state this and suggest alternatives for Linux/macOS users.

Create Pull Request

Azure Resource Manager Relocate Azure Backup to Another Region ...rce-manager/management/relocation/relocation-backup.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides some OS-specific guidance, but Windows examples and instructions are generally mentioned before Linux equivalents. PowerShell/Azure PowerShell is referenced for scripting, but there are no explicit Bash or Linux CLI script examples. Linux instructions are limited to generic statements like 'refer to distributor guidance,' and there are no concrete Linux command examples for tasks such as certificate updates or agent configuration. This may create friction for Linux users, especially those less familiar with Azure's Windows-centric tooling.

Recommendations

Provide explicit Linux/Bash/CLI command examples alongside or before PowerShell examples, especially for scripting bulk VM protection.
Include concrete steps or references for updating certificates and CRLs on popular Linux distributions (e.g., Ubuntu, RHEL).
Clarify agent installation and configuration steps for Linux-based on-premises VMs, not just Windows (e.g., for MARS or alternatives).
When listing OS-specific instructions, alternate the order or group them together to avoid always listing Windows first.
Where possible, provide parity in screenshots and UI walkthroughs for both Windows and Linux environments.

Create Pull Request

Virtual Network Manager What is IP address management (IPAM) in Azure Virtual Network Manager? ...rtual-network-manager/concept-ip-address-management.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides Azure CLI examples but uses backtick (`) line continuations and variable assignment syntax (e.g., $ipamAllocation) that are specific to PowerShell/Windows environments. This can confuse Linux/macOS users, as the CLI syntax shown is not directly portable to bash or sh shells. No bash/zsh-native examples or notes are provided.

Recommendations

Provide Azure CLI examples using both PowerShell (Windows) and bash/zsh (Linux/macOS) syntax, especially for variable assignment and line continuation.
Add a note clarifying that the current examples use PowerShell syntax and provide equivalent bash syntax (e.g., use \ for line continuation and export or plain variable assignment).
Ensure that any scripts or commands are tested in both Windows and Linux/macOS shells.
Consider including a tabbed interface or callout for 'Windows (PowerShell)' and 'Linux/macOS (bash)' examples.

Create Pull Request

Synapse Analytics Known issues ...s/blob/main/articles/synapse-analytics/known-issues.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 is generally cross-platform and does not focus on OS-specific tools for most issues. However, there is a notable bias in the 'Storage access issues due to authorization header being too long' section, where only a PowerShell command (Get-AzAccessToken) is provided to check token length, with no equivalent Bash, Azure CLI, or cross-platform example. Additionally, Windows tools (SSMS/ADS) are mentioned for client restarts, and Windows-style path separators (backslashes) are referenced in deployment troubleshooting. These collectively indicate a moderate Windows/PowerShell bias.

Recommendations

Provide equivalent Azure CLI or Bash examples for PowerShell commands, especially for checking token length (e.g., using 'az account get-access-token').
When referencing tools like SSMS/ADS, mention cross-platform alternatives (e.g., Azure Data Studio is cross-platform; clarify this).
When discussing file paths and escape characters, clarify platform differences and provide examples for both Windows (backslash) and Linux/macOS (forward slash).
Review all code snippets and instructions to ensure parity for Linux/macOS users, especially in troubleshooting steps.

Create Pull Request

Storage Resize an Azure Elastic SAN and its volumes ...ain/articles/storage/elastic-san/elastic-san-expand.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 PowerShell and Azure CLI examples for all tasks, ensuring cross-platform command-line parity. However, PowerShell examples are consistently presented before Azure CLI, which may subtly prioritize Windows users. There are no examples or references to Linux/macOS-specific tools or shell environments, but the CLI examples are cross-platform. No critical tasks are Windows-only.

Recommendations

Alternate the order of PowerShell and Azure CLI tabs or present Azure CLI examples first to avoid implicit Windows prioritization.
Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
Consider including bash/zsh variable syntax in CLI examples to further reinforce cross-platform usage.
Add a short note clarifying that PowerShell is available cross-platform, but CLI is often the default on Linux/macOS.

Create Pull Request

Storage Manage Customer-Managed Keys - Azure Elastic SAN ...tic-san/elastic-san-encryption-manage-customer-keys.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ none

Summary

The documentation provides both Azure PowerShell and Azure CLI examples for all key management operations. Azure CLI is fully cross-platform and the examples are not Windows-specific. There are no references to Windows-only tools, patterns, or workflows, and no ordering bias (e.g., Windows-first) that would disadvantage Linux/macOS users.

Recommendations

No changes required. Both PowerShell and Azure CLI are supported and documented. Azure CLI is cross-platform and suitable for Linux/macOS users.
Continue to ensure that all future examples include Azure CLI commands and avoid reliance on Windows-only tools.

Create Pull Request

Storage Blob Storage feature support in Azure storage accounts ...e/blobs/storage-feature-support-in-storage-accounts.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation lists both Azure CLI and PowerShell command support for Blob Storage, but only explicitly mentions PowerShell (a Windows-centric tool) in the feature tables. There is no explicit mention of Linux/macOS equivalents for PowerShell commands, and PowerShell is listed before Blobfuse (a Linux tool) in the tables. However, Azure CLI (cross-platform) and Blobfuse (Linux) are also included, and no examples are given, so the bias is minor.

Recommendations

Clarify that PowerShell commands are primarily for Windows and provide links or notes for Linux/macOS alternatives (e.g., Azure CLI, REST API, or cross-platform PowerShell Core).
List cross-platform tools (Azure CLI, Blobfuse) before Windows-centric tools (PowerShell) in feature tables to avoid the impression of Windows-first bias.
Add a brief note in the documentation introduction about tool parity and platform support, ensuring Linux/macOS users know their options.
Where possible, provide example commands for both Windows (PowerShell) and Linux/macOS (CLI, Bash, etc.) in related documentation.

Create Pull Request

Scan Information

Problematic Pages