← Back to Dashboard
48
Pages Scanned
7
Pages Flagged
48
Changed Pages
14.6%
% Pages Flagged

Scan Information

Started At: 2026-01-22 00:00:10

Finished At: 2026-01-22 00:26:24

Status: completed

Target Repo: Azure Management

Current Phase: discovery

Files Queued: 48

Files Completed: 48

Problematic Pages

7 issues found
Lighthouse Azure Lighthouse architecture ...blob/main/articles/lighthouse/concepts/architecture.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 for Azure Lighthouse architecture demonstrates a moderate Windows bias. PowerShell is referenced as the primary example for creating registration definitions, with no equivalent Azure CLI or REST API example shown. The mention of PowerShell commands occurs before any reference to cross-platform tools, and Linux/macOS users are not provided with explicit guidance or examples for their platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell for key tasks such as creating registration definitions and assignments.
  • Reference REST API methods where appropriate, with links to documentation.
  • When listing tools, mention cross-platform options (Azure CLI, REST API) before or alongside PowerShell.
  • Clarify that PowerShell is available cross-platform, but also provide CLI syntax for parity.
  • Include a note or section for Linux/macOS users to ensure inclusivity.
GitHub Create Pull Request
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 instructions for all major tasks, but PowerShell examples are given equal prominence and detail as CLI, and environment variable examples for proxy configuration use Windows syntax ($Env:...) before Linux/macOS (export ...). There are no explicit Linux/macOS-specific troubleshooting steps or notes, and the documentation does not mention platform-specific caveats for Linux users. All examples are generic, but the PowerShell examples and syntax may be less familiar to Linux/macOS users, and the CLI examples do not clarify platform differences.
Recommendations
  • Explicitly state that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
  • Provide Linux/macOS-specific environment variable examples before or alongside Windows/PowerShell syntax, especially for proxy configuration.
  • Add troubleshooting notes or links for common Linux/macOS issues (e.g., permissions, shell differences, proxy configuration nuances).
  • Clarify that PowerShell examples are primarily for Windows users, and recommend CLI for Linux/macOS.
  • Consider providing Bash script snippets for Linux/macOS users where relevant.
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 example for registering the Microsoft.Insights resource provider using PowerShell only, with no equivalent Azure CLI or cross-platform instructions. PowerShell is primarily a Windows tool, and presenting it as the sole 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 examples for registering the Microsoft.Insights resource provider, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • When listing tools for workspace creation, present Azure CLI and Bicep before or alongside PowerShell to avoid Windows-first ordering.
  • Include notes or links to platform-agnostic methods wherever possible, especially for automation steps.
  • Clarify that PowerShell examples are one option and provide alternatives for non-Windows environments.
GitHub Create Pull Request
Lighthouse Deploy Azure Policy to delegated subscriptions at scale ...lob/main/articles/lighthouse/how-to/policy-at-scale.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation exclusively uses PowerShell cmdlets and scripts for all examples and procedures, with no mention of cross-platform alternatives such as Azure CLI, Bash, or Cloud Shell. This creates friction for Linux/macOS users who may not have access to or prefer not to use PowerShell. Additionally, the use of PowerShell is assumed throughout, and Windows-centric tools are referenced without parity for Linux environments.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell scripts and commands.
  • Mention that Azure CLI and Cloud Shell are cross-platform options and link to relevant documentation.
  • Clarify prerequisites for PowerShell usage on non-Windows platforms, or recommend installing PowerShell Core if needed.
  • Order examples so that cross-platform tools (Azure CLI, Cloud Shell) are shown first or alongside PowerShell.
  • Explicitly state that all procedures can be performed from Linux/macOS using Azure CLI or PowerShell Core.
GitHub Create Pull Request
Lighthouse Monitor delegation changes in your managing tenant ...ticles/lighthouse/how-to/monitor-delegation-changes.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 both PowerShell and Azure CLI examples for assigning roles, but the only end-to-end automation script for querying and reporting on delegation changes is given in Azure PowerShell. There is no equivalent Bash, Python, or cross-platform script, and the PowerShell script is presented as the primary (and only) automation solution. This creates friction for Linux/macOS users who may not have or want to use PowerShell.
Recommendations
  • Provide a Bash or Python script example for querying the Tenant Activity Log using the Azure CLI and/or REST API, covering the same reporting functionality as the PowerShell script.
  • Explicitly mention that the PowerShell script can be run cross-platform with PowerShell Core, or provide guidance for Linux/macOS users on how to set up the required environment.
  • Where possible, present CLI and PowerShell examples side by side for all automation tasks, not just role assignment.
  • Link to or provide sample code for using the Azure SDKs (e.g., Python, Node.js) to query the activity log, for users who prefer those languages.
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 REST API examples. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other cross-platform tools. The example is presented as the sole method, and PowerShell is mentioned first and exclusively.
Recommendations
  • Add equivalent Azure CLI and/or REST API examples for assigning the policy and creating remediation tasks.
  • Include Bash scripting examples where appropriate.
  • Clarify that PowerShell is one option and mention cross-platform alternatives.
  • Consider reordering examples so that cross-platform tools are presented alongside or before Windows-specific tools.
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 (cross-platform) and Azure PowerShell (Windows-centric) instructions in parallel throughout, but in several places, PowerShell examples are given equal prominence, and some shell commands (such as variable assignment and output) use PowerShell syntax that is not portable to Linux/macOS. The final example for using kubectl is shown as a PowerShell code block, and variable assignment in PowerShell is shown before or alongside Bash, which may confuse Linux/macOS users. However, Azure CLI is available for all platforms and is shown in all critical steps, so Linux/macOS users can complete the workflow.
Recommendations
  • Ensure that all shell commands (especially those using kubectl, variable assignment, and token extraction) are shown in Bash syntax when targeting cross-platform users, and clearly mark PowerShell examples as Windows-only.
  • Show Bash/Linux/macOS examples first, or provide tabs for Bash, PowerShell, and Azure CLI where appropriate.
  • In sections where PowerShell is used for variable assignment or token extraction, provide equivalent Bash commands for Linux/macOS users.
  • For kubectl usage, use generic shell code blocks or provide both Bash and PowerShell examples.
  • Clarify that Azure PowerShell instructions are intended for Windows users, and encourage Linux/macOS users to use Azure CLI and Bash.
GitHub Create Pull Request