Lighthouse

64
Total Pages
56
Linux-Friendly Pages
8
Pages with Bias
12.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

25 issues found
Showing 1-25 of 25 flagged pages
Lighthouse Deploy Azure Policy to delegated subscriptions at scale ...lob/main/articles/lighthouse/how-to/policy-at-scale.md
Medium Priority View Details →
Scanned: 2026-01-22 00:00
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 →
Scanned: 2026-01-22 00:00
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 →
Scanned: 2026-01-22 00:00
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
Lighthouse Azure Lighthouse architecture ...blob/main/articles/lighthouse/concepts/architecture.md
Medium Priority View Details →
Scanned: 2026-01-22 00:00
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
Lighthouse Monitor delegated resources at scale ...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
Medium Priority View Details →
Scanned: 2026-01-22 00:00
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 Azure Lighthouse architecture ...blob/main/articles/lighthouse/concepts/architecture.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias by referencing Azure PowerShell commands and patterns exclusively when discussing resource creation and onboarding, without providing equivalent Azure CLI or REST API examples. Windows-centric tools (PowerShell) are mentioned first and in detail, while Linux/macOS-friendly alternatives are only referenced generically in the 'Next steps' section. This may create friction for users on non-Windows platforms who prefer or require CLI or API-based workflows.
Recommendations
  • Provide Azure CLI examples alongside PowerShell for all resource creation and onboarding steps.
  • Explicitly mention REST API methods where applicable, with links to documentation.
  • Ensure that Linux/macOS users are given clear, step-by-step instructions using cross-platform tools.
  • Where PowerShell is referenced, add a note or section showing the equivalent CLI commands.
  • Review all code samples and tool recommendations for platform neutrality.
GitHub Create Pull Request
Lighthouse Monitor delegation changes in your managing tenant ...ticles/lighthouse/how-to/monitor-delegation-changes.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell scripts for querying delegation changes, with no equivalent Bash or Linux-native scripting examples. While Azure CLI commands are included for role assignment, the main automation and reporting workflow is presented only in PowerShell, which is primarily a Windows tool. There is no mention of how to perform the same query using Bash, Python, or other cross-platform tools, nor are Linux/macOS-specific considerations discussed.
Recommendations
  • Provide equivalent Bash or Python scripts for querying the Tenant Activity Log, using curl or the Azure CLI to make REST API calls.
  • Explicitly state that PowerShell Core is available cross-platform, and provide instructions for installing it on Linux/macOS if PowerShell is required.
  • Include Linux/macOS-specific authentication and environment setup steps, such as using az login and environment variables.
  • Reorder examples so that Azure CLI or REST API methods are presented before or alongside PowerShell, emphasizing cross-platform compatibility.
GitHub Create Pull Request
Lighthouse Monitor delegated resources at scale ...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the section on registering resource providers, where only Azure PowerShell commands are provided. There is no mention of equivalent Azure CLI or REST API methods, which are more platform-neutral and commonly used on Linux/macOS. Additionally, the documentation references PowerShell before any other automation or scripting tools, and does not offer Linux/macOS-specific guidance or examples.
Recommendations
  • Provide Azure CLI examples alongside PowerShell commands for resource provider registration and other automation tasks.
  • Explicitly mention that Azure CLI and REST API can be used from Linux/macOS and provide sample commands.
  • Reorder examples or add parallel examples so that Windows and Linux/macOS users see their options equally.
  • Reference cross-platform tools and scripting patterns (e.g., bash, shell scripts) where appropriate.
  • Add a note clarifying that all tasks can be performed from any OS using Azure CLI, REST API, or portal.
GitHub Create Pull Request
Lighthouse Onboard a customer to Azure Lighthouse ...ob/main/articles/lighthouse/how-to/onboard-customer.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, but PowerShell examples are given equal prominence to CLI, and are included throughout. There is no mention of Linux/macOS-specific shell environments (e.g., Bash), nor are there any examples using native Linux tools or scripting patterns. The documentation refers to 'Azure PowerShell' and 'Azure CLI' as cross-platform, but does not clarify that PowerShell is available on Linux/macOS, nor does it provide any Linux/macOS-specific guidance or troubleshooting. The ordering of examples sometimes places PowerShell after CLI, but both are presented as primary options, with no explicit Linux-first or parity focus. No Windows-only tools (e.g., cmd.exe, Windows-only GUIs) are referenced, but the lack of Linux/macOS-specific context or examples may create friction for non-Windows users.
Recommendations
  • Explicitly state that both Azure CLI and Azure PowerShell are cross-platform and available on Linux/macOS.
  • Add Bash shell examples for template deployment and resource management, especially for Linux/macOS users.
  • Include troubleshooting steps or notes relevant to Linux/macOS environments (e.g., file paths, permissions, shell differences).
  • Clarify that Azure PowerShell can be used on Linux/macOS, and link to installation guides for those platforms.
  • Consider ordering CLI/Bash examples before PowerShell to better reflect typical Linux/macOS user workflows.
  • Add a section or callout for Linux/macOS users, highlighting any differences or considerations.
GitHub Create Pull Request
Lighthouse Onboard all subscriptions in a management group ...articles/lighthouse/how-to/onboard-management-group.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only a PowerShell example for assigning the policy at the management group level, with no mention of Azure CLI, Bash, or other cross-platform alternatives. This creates friction for Linux and macOS users who may not have access to PowerShell or prefer native tools. The rest of the documentation is platform-neutral, but the critical deployment step is Windows-biased.
Recommendations
  • Add equivalent Azure CLI example for assigning the policy, e.g., using 'az deployment mg create'.
  • Explicitly mention that PowerShell is available cross-platform, but provide Bash/CLI syntax for parity.
  • Consider listing CLI/Bash examples before or alongside PowerShell to avoid Windows-first impression.
  • Clarify any prerequisites for Linux/macOS users (e.g., installing Azure CLI or PowerShell Core).
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 →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all examples, with no mention of Azure CLI, Bash, or cross-platform alternatives. All code samples are in PowerShell, which is most commonly used on Windows, and there are no equivalent instructions or examples for Linux/macOS users. The documentation also references Windows-centric patterns (e.g., PowerShell pipelines, cmdlet naming conventions) without noting how Linux users can achieve the same tasks.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all major steps, including querying Resource Graph, deploying policies, validating deployment, and cleaning up resources.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and clarify any differences or prerequisites for running these scripts cross-platform.
  • Add Bash script examples or at least CLI commands to ensure Linux/macOS users can follow the documentation without friction.
  • Reorder or parallelize examples so that Linux/macOS-friendly approaches (CLI, Bash) are presented alongside PowerShell, not only after or below it.
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell commands and Azure PowerShell modules for all examples, with no mention of Bash, Azure CLI, or Linux/macOS-specific workflows. All code samples and deployment instructions assume the use of PowerShell, which is traditionally a Windows-centric tool, although it is available on Linux/macOS. There are no alternative examples or guidance for users who prefer Bash or Azure CLI, and Windows/PowerShell patterns are presented first and exclusively.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for querying, deploying, validating, and cleaning up policies.
  • Include Bash shell script samples for Linux/macOS users.
  • Explicitly mention cross-platform compatibility of PowerShell, and provide installation/setup links for PowerShell on Linux/macOS.
  • Where possible, note any differences or limitations when running these commands on Linux/macOS.
  • Present Azure CLI and Bash examples alongside PowerShell, or at least link to relevant cross-platform documentation.
GitHub Create Pull Request
Lighthouse Onboard all subscriptions in a management group ...articles/lighthouse/how-to/onboard-management-group.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 at the management group level, without mentioning or providing equivalent Azure CLI, Bash, or REST API examples. This creates friction for Linux/macOS users who may not use PowerShell as their primary automation tool. The example is labeled as 'azurepowershell-interactive', reinforcing a Windows-centric approach.
Recommendations
  • Add Azure CLI and/or REST API examples for policy assignment, ensuring cross-platform compatibility.
  • Explicitly mention that PowerShell is available on Linux/macOS, but provide alternatives for users who prefer native tools.
  • Present examples for multiple platforms side-by-side or in parallel, rather than only PowerShell.
  • Clarify any platform-specific requirements or limitations for each method.
GitHub Create Pull Request
Lighthouse Azure Lighthouse architecture ...blob/main/articles/lighthouse/concepts/architecture.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page 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 provided inline. Windows-centric tools (PowerShell cmdlets) are mentioned first and exclusively in the main workflow, while Linux-friendly alternatives (Azure CLI, REST API) are only referenced in the 'Next steps' section and not shown in context. This may create friction for Linux/macOS users who prefer CLI or scripting over PowerShell.
Recommendations
  • Provide Azure CLI examples alongside PowerShell for key tasks such as creating registration definitions and assignments.
  • Explicitly mention REST API options for automation and cross-platform parity.
  • Ensure that CLI and PowerShell examples are presented together, or alternate which is shown first.
  • Add a note clarifying that all operations can be performed using CLI, PowerShell, or REST API, with links to relevant documentation.
GitHub Create Pull Request
Lighthouse Monitor delegated resources at scale ...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, particularly in the section on registering resource providers, where only Azure PowerShell commands are provided. There are no CLI or Bash examples, and PowerShell is referenced as the primary automation tool. This may create friction for Linux/macOS users who prefer Azure CLI or Bash scripting. Additionally, Windows-centric tools and patterns are mentioned before any cross-platform alternatives.
Recommendations
  • Provide equivalent Azure CLI commands for resource provider registration and service principal creation.
  • Include Bash scripting examples alongside PowerShell for automation tasks.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
  • Add notes clarifying tool compatibility across operating systems.
GitHub Create Pull Request
Lighthouse Monitor delegation changes in your managing tenant ...ticles/lighthouse/how-to/monitor-delegation-changes.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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. PowerShell is the primary scripting language used for querying delegation changes, with a detailed PowerShell script provided and no equivalent Bash or cross-platform shell example. While Azure CLI is mentioned for role assignment, all advanced querying and reporting is shown only in PowerShell, which is most commonly used on Windows. There is no guidance or sample for Linux/macOS users who may prefer Bash, Python, or other cross-platform tools.
Recommendations
  • Provide equivalent Bash or Python scripts for querying the Tenant Activity Log using REST API and Azure CLI, suitable for Linux/macOS environments.
  • Explicitly mention that PowerShell Core is available cross-platform, and clarify any Windows-specific dependencies.
  • Show Azure CLI examples for querying and reporting, not just for role assignment.
  • Reorder examples so that cross-platform tools (Azure CLI, Bash, Python) are presented before or alongside PowerShell.
  • Add notes or links to cross-platform scripting resources for Azure.
GitHub Create Pull Request
Lighthouse Azure Lighthouse architecture ...blob/main/articles/lighthouse/concepts/architecture.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell commands and patterns exclusively when describing how to create registration definitions, without mentioning Azure CLI equivalents or providing Linux/macOS-friendly examples. PowerShell is a Windows-centric tool, and its usage is described before any mention of cross-platform alternatives. The 'Next steps' section lists Azure CLI, but only after PowerShell, and the main instructional content focuses on PowerShell.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all resource creation and management tasks.
  • Explicitly mention that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS, and provide parity in examples.
  • Where PowerShell commands are referenced, add equivalent Azure CLI commands and links.
  • Consider listing Azure CLI before or alongside PowerShell in 'Next steps' and instructional sections.
GitHub Create Pull Request
Lighthouse Monitor delegated resources at scale ...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the critical section for registering resource providers in the managing tenant. Only Azure PowerShell commands are provided, with no mention of Azure CLI or Bash alternatives. The use of PowerShell is presented as the sole automation method, and Windows-centric tools are referenced before any cross-platform options. Linux/macOS users are left without direct guidance for completing essential steps, requiring them to seek workarounds or translate PowerShell to CLI commands themselves.
Recommendations
  • Provide equivalent Azure CLI commands for resource provider registration and service principal creation.
  • Explicitly mention that Azure CLI and Bash can be used on Linux/macOS, and link to relevant documentation.
  • Where PowerShell is referenced, offer cross-platform alternatives or note platform compatibility.
  • Reorder examples so that cross-platform tools (Azure CLI) are shown before or alongside PowerShell.
  • Add a note clarifying that all steps can be performed on Linux/macOS and provide links to those instructions.
GitHub Create Pull Request
Lighthouse Onboard all subscriptions in a management group ...articles/lighthouse/how-to/onboard-management-group.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only a PowerShell example for assigning the policy to a management group, with no equivalent example for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). The use of PowerShell is presented as the default method, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI and/or Bash examples for assigning the policy and creating remediation tasks.
  • Include REST API instructions for cross-platform automation.
  • Explicitly state that PowerShell is one of several options and link to cross-platform alternatives.
  • Reorder examples or provide parallel instructions for both Windows and Linux/macOS users.
GitHub Create Pull Request
Lighthouse Cross-tenant management experiences ...hthouse/concepts/cross-tenant-management-experience.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing Azure PowerShell and its cmdlets before Azure CLI, and by mentioning Windows tools (PowerShell) as a primary management option. While Linux-compatible tools (Azure CLI, REST API) are also referenced, examples and tool mentions tend to lead with Windows-centric options. No explicit Linux/macOS examples or parity notes are given, and there are no Linux-specific troubleshooting or usage notes.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Include explicit notes or examples for Linux/macOS users, especially for command-line operations.
  • Clarify that all management operations can be performed equally from Linux/macOS environments using Azure CLI and REST API.
  • Where PowerShell is referenced, provide equivalent Azure CLI commands and usage patterns.
  • Add troubleshooting notes for Linux/macOS environments where relevant (e.g., authentication, environment setup).
GitHub Create Pull Request
Lighthouse Remove access to a delegation ...b/main/articles/lighthouse/how-to/remove-delegation.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for removing delegations, but PowerShell (commonly associated with Windows) is presented before Azure CLI. There are no explicit Linux/macOS examples or mentions of platform-specific considerations, and the Azure portal instructions are platform-neutral. The CLI example does use 'az', which is cross-platform, but the ordering and prominence of PowerShell may subtly favor Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide installation links for each platform.
  • Add a note clarifying that the Azure portal and Azure CLI instructions work identically on Linux and macOS.
  • If any platform-specific issues exist (e.g., authentication differences), call them out.
GitHub Create Pull Request
Lighthouse Remove access to a delegation ...b/main/articles/lighthouse/how-to/remove-delegation.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell instructions before Azure CLI examples in the 'Service providers' section, and references PowerShell-specific commands. While Azure CLI is covered, there are no explicit Linux/macOS-specific notes or examples, and the PowerShell example may implicitly favor Windows users. No Linux-only tools or shell examples are provided.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit Windows-first bias.
  • Add explicit notes confirming that Azure CLI commands work on Linux/macOS and provide any necessary platform-specific instructions.
  • Include bash or shell script examples for common Linux workflows where appropriate.
  • Clarify that Cloud Shell is cross-platform and highlight its use for both Windows and Linux/macOS users.
GitHub Create Pull Request
Lighthouse Onboard a customer to Azure Lighthouse ...ob/main/articles/lighthouse/how-to/onboard-customer.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and verification tasks, but PowerShell examples are always presented after CLI and before any mention of Linux-specific shell usage. There is no explicit mention of Linux/macOS shell environments (e.g., Bash), nor are there examples using native Linux tools or patterns. The documentation refers to 'Azure PowerShell' and 'Azure CLI' as cross-platform, but does not clarify that both are available on Linux/macOS. There is a slight Windows bias in the ordering and in the lack of explicit Linux/macOS context, but all tasks can be completed on Linux/macOS using Azure CLI or PowerShell Core.
Recommendations
  • Explicitly state that Azure CLI and Azure PowerShell Core are available and supported on Linux/macOS, not just Windows.
  • Add Bash shell examples for common tasks, or clarify that Azure CLI commands are intended for Bash/Unix shells as well as PowerShell.
  • Where PowerShell is mentioned, clarify that PowerShell Core is cross-platform and available on Linux/macOS.
  • Include a note or section for Linux/macOS users, confirming parity and listing any platform-specific considerations.
  • Consider alternating the order of CLI and PowerShell examples, or grouping them together as 'cross-platform'.
GitHub Create Pull Request
Lighthouse Cross-tenant management experiences ...hthouse/concepts/cross-tenant-management-experience.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references both Azure PowerShell and Azure CLI for cross-tenant management, listing PowerShell first and providing a more detailed example for PowerShell. While Linux is mentioned in the context of Azure Arc, there are no explicit Linux/macOS-specific examples or tool recommendations. The documentation focuses on Azure portal, PowerShell, and CLI, which are available cross-platform, but the ordering and emphasis slightly favor Windows tools.
Recommendations
  • Provide explicit examples for Linux/macOS users, such as bash shell commands or instructions for using Azure CLI on Linux.
  • Ensure parity in example detail between PowerShell and CLI, and consider listing CLI first or equally.
  • Mention that Azure CLI is cross-platform and highlight any Linux/macOS-specific considerations.
  • Include notes or links for installing and using Azure CLI and PowerShell on Linux/macOS.
  • Where management tools are referenced, clarify their availability and usage on non-Windows platforms.
GitHub Create Pull Request
Lighthouse Cross-tenant management experiences ...hthouse/concepts/cross-tenant-management-experience.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page shows mild Windows bias in the 'APIs and management tool support' section, where Azure PowerShell (a Windows-centric tool) is mentioned before Azure CLI, and PowerShell-specific cmdlets are described in detail. There are no Linux/macOS-specific examples or explicit parity notes, though Azure CLI (cross-platform) is referenced. No critical tasks appear to be Windows-only, and most scenarios are described in a platform-neutral way.
Recommendations
  • Present Azure CLI examples before or alongside Azure PowerShell examples, as CLI is cross-platform.
  • Explicitly state that Azure CLI and REST API are fully supported on Linux/macOS.
  • Add notes or examples for Linux/macOS users where relevant, especially in sections discussing management tools.
  • Avoid implying PowerShell is the default or primary tool for cross-tenant management tasks.
GitHub Create Pull Request