← Back to Dashboard
11
Pages Scanned
4
Pages Flagged
11
Changed Pages
36.4%
% Pages Flagged

Scan Information

Started At: 2026-01-18 00:00:39

Finished At: 2026-01-18 00:02:31

Status: completed

Target Repo: Azure Management

Current Phase: discovery

Files Queued: 11

Files Completed: 11

Problematic Pages

4 issues found
Azure Arc Simplify network configuration requirements with Azure Arc gateway (preview) ...zure-arc/kubernetes/arc-gateway-simplify-networking.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 both Azure CLI and Azure PowerShell examples for all major steps, but the PowerShell examples are given equal prominence to CLI, and in some cases, environment variable setup for PowerShell uses Windows syntax only. There are no explicit Linux/macOS shell examples for PowerShell, and the CLI examples do not clarify Linux/macOS specifics (e.g., shell differences, proxy environment variable nuances). The documentation does not mention Linux-specific tools or patterns, and PowerShell is not natively available on most Linux/macOS systems, potentially creating friction for non-Windows users.
Recommendations
  • Add explicit Linux/macOS shell examples for environment variable setup (e.g., export commands for Bash/Zsh, especially in PowerShell sections).
  • Clarify that Azure CLI commands are cross-platform and provide notes on any OS-specific differences (such as proxy configuration nuances).
  • Where PowerShell is used, mention that PowerShell Core is available on Linux/macOS, and provide equivalent Linux/macOS syntax if relevant.
  • Consider listing Azure CLI examples before PowerShell, as CLI is the default and most widely used cross-platform tool.
  • Add a short section or note on prerequisites for Linux/macOS users (e.g., installing Azure CLI, PowerShell Core).
GitHub Create Pull Request
Lighthouse Monitor delegated resources at scale ...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides a critical resource registration example only in PowerShell, with no equivalent Azure CLI or Bash example. PowerShell is primarily a Windows tool, and presenting it as the sole automation method creates friction for Linux/macOS users. Additionally, PowerShell is mentioned before other cross-platform tools in the workspace creation section.
Recommendations
  • Add Azure CLI and/or Bash examples for registering the Microsoft.Insights resource provider, alongside the PowerShell example.
  • Explicitly mention that PowerShell Core is available cross-platform, or link to documentation on using PowerShell on Linux/macOS if PowerShell must be used.
  • When listing automation options (Azure portal, PowerShell, Azure CLI, Bicep, ARM templates), rotate the order or clarify cross-platform support to avoid Windows-first perception.
GitHub Create Pull Request
Lighthouse Onboard all subscriptions in a management group ...articles/lighthouse/how-to/onboard-management-group.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation provides only a PowerShell example for assigning the policy to a management group, with no equivalent Azure CLI, Bash, or ARM template deployment examples. This creates friction for Linux/macOS users who may not use PowerShell as their primary automation tool. The example is presented as the sole method, implicitly prioritizing Windows/PowerShell workflows.
Recommendations
  • Add Azure CLI examples for policy assignment at the management group level.
  • Include Bash or ARM template deployment instructions for cross-platform parity.
  • Present PowerShell and cross-platform examples side-by-side, or clarify that multiple options exist.
  • Explicitly mention that the process can be completed using Azure CLI, REST API, or ARM templates, and link to relevant documentation.
GitHub Create Pull Request
Azure Arc Use cluster connect to securely connect to Azure Arc-enabled Kubernetes clusters. .../main/articles/azure-arc/kubernetes/cluster-connect.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ minor_shell_inconsistency
Summary
The documentation provides both Azure CLI (Bash/sh) and Azure PowerShell examples in parallel, but PowerShell examples are shown in full detail, including variable assignment and token extraction, which may be more familiar to Windows users. In some places, PowerShell syntax is used for kubectl commands (e.g., variable assignment and token extraction), and the final kubectl example is shown as a PowerShell command, even though kubectl is cross-platform. There is a slight tendency to show PowerShell examples and syntax, which may create minor friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Ensure all kubectl examples use standard shell syntax (Bash/sh) in CLI sections and PowerShell syntax only in PowerShell sections.
  • In the 'Access your cluster from a client device' section, provide both Bash and PowerShell examples for kubectl commands, or default to Bash syntax since kubectl is cross-platform.
  • Clarify that Azure CLI and kubectl commands work on Linux/macOS and Windows equally, and provide explicit instructions for Linux/macOS users where variable assignment or token extraction differs.
  • Consider listing CLI (Bash/sh) examples before PowerShell examples, or side-by-side, to avoid implicit Windows-first ordering.
GitHub Create Pull Request