← Back to Dashboard
24
Pages Scanned
9
Pages Flagged
24
Changed Pages
37.5%
% Pages Flagged

Scan Information

Started At: 2026-01-13 21:56:57

Finished At: 2026-01-13 23:13:36

Status: completed

Target Repo: Azure

Current Phase: discovery

Files Queued: 24

Files Completed: 24

Problematic Pages

9 issues found
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 operational examples and tooling. All command-line instructions for configuring ExpressRoute connections and enabling FastPath/PrivateLinkFastPath are provided exclusively using Azure PowerShell, with no equivalent Azure CLI or Bash examples. PowerShell is a Windows-centric tool, and presenting only PowerShell commands creates friction for Linux/macOS users. Additionally, Windows tools and patterns are mentioned first and exclusively in the configuration sections, and there is no guidance or parity for Linux-native workflows.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, especially for connection configuration and attribute toggling.
  • Include Bash script examples or generic REST API calls for cross-platform automation.
  • Explicitly mention that Azure CLI is supported on Linux/macOS and link to relevant CLI documentation.
  • Reorder examples so that cross-platform tools (Azure CLI, Bash) are shown first or alongside PowerShell.
  • Add notes clarifying that PowerShell commands can be run on Linux/macOS, but CLI/Bash alternatives are recommended for native environments.
GitHub Create Pull Request
App Service Configure Premium v4 Tier ...s/app-service/app-service-configure-premium-v4-tier.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation shows a moderate Windows bias. Windows-specific information and tools (such as Azure PowerShell) are mentioned before Linux equivalents, and PowerShell scripting is given equal prominence to Azure CLI, despite CLI being more cross-platform. The 'Automate with scripts' section provides both Azure CLI and PowerShell examples, but PowerShell is a Windows-centric tool. In the 'Premium v4 availability' section, the Windows SKU example is shown before Linux. However, Linux-specific instructions are present where relevant, and Azure CLI examples are provided.
Recommendations
  • Present Linux and Windows examples in parallel or with equal prominence, rather than listing Windows first.
  • Clarify that Azure CLI is cross-platform and recommend it as the default automation tool for Linux/macOS users.
  • Where PowerShell is shown, explicitly mention that it is primarily for Windows users and provide Bash or shell script equivalents for Linux/macOS.
  • In the 'Premium v4 availability' section, consider listing Linux and Windows commands together or in a neutral order.
  • Add explicit notes or links for Linux/macOS users where UI or tool differences may exist.
GitHub Create Pull Request
Migrate Set up agent-based dependency analysis in Azure Migrate ...es/migrate/how-to-create-group-machine-dependencies.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 generally presents Windows instructions and tools first, with more detailed, step-by-step guidance for Windows (including GUI and automation options), while Linux instructions are more terse and lack equivalent detail. Windows tools and workflows (e.g., double-click installers, Configuration Manager) are mentioned and linked, but Linux equivalents (such as package managers or automation scripts) are not. This creates friction for Linux users, who must infer steps or seek external resources.
Recommendations
  • Provide Linux installation instructions with equivalent detail to Windows, including common automation methods (e.g., using package managers like apt/yum, or shell scripts).
  • List Linux and Windows instructions in parallel or in separate, clearly labeled sections, rather than always presenting Windows first.
  • Include links to Linux-specific documentation for agent installation, troubleshooting, and supported distributions.
  • Mention and provide examples for Linux automation and configuration management tools (e.g., Ansible, shell scripts) where Windows tools like Configuration Manager are referenced.
  • Ensure screenshots and UI references are relevant for both platforms, or clarify when steps are platform-specific.
GitHub Create Pull Request
Storage Create multiple Azure Elastic SAN volumes in a batch ...storage/elastic-san/elastic-san-batch-create-sample.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation exclusively provides a PowerShell script for batch-creating Azure Elastic SAN volumes, assumes use of Windows-style file paths, and does not mention or provide any examples for Bash, Azure CLI, or cross-platform scripting. There is no guidance for Linux or macOS users.
Recommendations
  • Add equivalent Bash or Azure CLI script examples for Linux/macOS users.
  • Use cross-platform file path examples or clarify that file paths should be adapted for the user's OS.
  • Explicitly state that the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, if applicable.
  • Mention prerequisites and installation steps for non-Windows environments.
GitHub Create Pull Request
Storage Delete an Azure Elastic SAN ...ain/articles/storage/elastic-san/elastic-san-delete.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation shows a moderate Windows bias. Windows/Powershell examples and scripts are consistently presented before their Linux/Azure CLI equivalents. The 'Disconnect volumes from clients' section provides a PowerShell script for Windows and a Python script for Linux, but the Windows instructions and parameters are listed first. In all resource deletion sections, PowerShell tabs precede Azure CLI tabs, and there are no Bash or native Linux shell examples. The overall structure and ordering favor Windows users and tools.
Recommendations
  • Present Azure CLI (cross-platform) examples before or alongside PowerShell examples.
  • Alternate the order of Windows and Linux sections, or combine them where possible.
  • Add Bash or shell script examples for Linux users where appropriate.
  • Standardize parameter naming and descriptions across platforms for clarity.
  • Explicitly mention that Azure CLI works on all platforms, and link to installation guides for Linux/macOS.
GitHub Create Pull Request
API Management VNet configuration settings | Azure API Management ...n/articles/api-management/virtual-network-reference.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_specific_section
Summary
The documentation is largely platform-neutral, focusing on Azure networking concepts and requirements. However, there are a few sections that reference Windows-specific infrastructure and tools, such as KMS activation for Windows VMs and Windows Update/Defender endpoints. There is also a mention of PowerShell in the context of management endpoints, but no explicit Linux/macOS alternatives or command-line examples are provided. These references are mostly in the context of supporting Windows VMs within the VNet, not for API Management itself.
Recommendations
  • Clarify that Windows-specific sections (KMS, Windows Update/Defender) are only relevant if Windows VMs are present, and provide equivalent guidance for Linux VMs if applicable (e.g., mention Linux activation or update endpoints if needed).
  • Where PowerShell is mentioned (e.g., 'Management endpoint for Azure portal and PowerShell'), add a note about cross-platform alternatives such as Azure CLI or REST API, or link to relevant documentation.
  • Ensure that any command-line or tool references include Linux/macOS equivalents or explicitly state if only Windows is supported.
  • If there are no Linux-specific requirements, explicitly state that the rest of the configuration is platform-agnostic.
GitHub Create Pull Request
Storage Azure Elastic SAN configuration best practices ...cles/storage/elastic-san/elastic-san-best-practices.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation demonstrates a mild Windows bias. Windows-specific tools (PowerShell, Registry Editor, iSCSI Initiator app) are often mentioned first or in more detail, and Windows command-line examples (PowerShell) are provided before Linux equivalents. However, Linux guidance and commands are also present and generally complete, allowing Linux users to follow along, though sometimes with less detail or prominence.
Recommendations
  • Present Linux and Windows examples in parallel or alternate the order to avoid always listing Windows first.
  • Provide equal detail for Linux tools and workflows (e.g., mention Linux equivalents to the iSCSI Initiator app and Registry Editor, such as using iscsiadm and editing config files).
  • Where possible, link to Linux-specific documentation for advanced configuration, similar to the Windows MPIO reference.
  • Clarify that all recommendations apply equally to Linux and Windows unless otherwise noted.
  • Add more screenshots or step-by-step instructions for Linux where only Windows visuals are provided.
GitHub Create Pull Request
Migrate Support for VMware vSphere migration in Azure Migrate ...les/migrate/migrate-support-matrix-vmware-migration.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation exhibits mild Windows bias. PowerShell is the only CLI tool mentioned for scripting or automation, and Windows-specific tools and firewall instructions are often referenced before or instead of Linux equivalents. While Linux support is generally well-documented, Linux automation options (e.g., Bash, CLI) are not mentioned, and some instructions (like configuring the appliance or connecting after migration) give more detail for Windows scenarios or list them first.
Recommendations
  • Include Bash/CLI examples or references for Linux/macOS users wherever PowerShell is mentioned, such as for deploying the appliance or automating replication.
  • When listing post-migration connection steps, provide Linux instructions before or alongside Windows, not after.
  • Mention Linux-native tools (e.g., iptables, firewalld) for firewall configuration, not just Windows Firewall.
  • Where automation or scripting is referenced, clarify cross-platform options (e.g., Azure CLI, Bash scripts) and provide links or examples.
  • Ensure that all sections referencing Windows tools or patterns have Linux/macOS equivalents or explicit notes if not applicable.
GitHub Create Pull Request
Storage Connect Azure Elastic SAN to Azure Kubernetes over iSCSI ...rticles/storage/elastic-san/elastic-san-connect-aks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation shows a mild Windows bias by listing Azure PowerShell as the first method to retrieve volume information, and providing a PowerShell example before the Azure CLI example. It also refers to 'install the latest Azure PowerShell module' alongside Azure CLI in prerequisites, and uses the term 'Azure PowerShell command' explicitly. However, Azure CLI examples are present, and the rest of the workflow uses cross-platform tools (kubectl, YAML manifests).
Recommendations
  • List Azure CLI examples before Azure PowerShell examples, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
  • Clarify that both Azure CLI and PowerShell are supported, and consider grouping their usage together rather than leading with PowerShell.
  • Explicitly mention that all steps after volume information retrieval are OS-agnostic.
  • If possible, provide bash/zsh shell command examples for common tasks, or note that Azure CLI is recommended for Linux/macOS users.
GitHub Create Pull Request