Lighthouse

32
Total Pages
24
Linux-Friendly Pages
8
Pages with Bias
25.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

51 issues found
Showing 1-25 of 51 flagged pages
Lighthouse Azure Lighthouse architecture ...blob/main/articles/lighthouse/concepts/architecture.md
High Priority View Details →
Scanned: 2026-01-11 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 primarily referencing Azure PowerShell for resource creation and management tasks, mentioning PowerShell cmdlets before Azure CLI, and lacking explicit Linux-oriented examples or guidance. The instructions and examples are tailored to users familiar with Windows tools, with no parity for Linux shell commands or workflows.
Recommendations
  • Provide equivalent Azure CLI examples alongside PowerShell instructions, especially for resource creation and management tasks.
  • Explicitly mention that Azure CLI can be used on Linux and macOS, and provide sample commands for those platforms.
  • Ensure that references to management tools do not prioritize Windows tools; present CLI and PowerShell options together.
  • Add a section or tip for Linux/macOS users, highlighting cross-platform support and any platform-specific considerations.
GitHub Create Pull Request
Lighthouse Cross-tenant management experiences ...hthouse/concepts/cross-tenant-management-experience.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the 'APIs and management tool support' section, Azure PowerShell is mentioned before Azure CLI, and the only explicit command example given is for PowerShell (Get-AzSubscription), with the CLI example following. No Linux-specific tools or examples are provided, and there is no mention of Bash or shell scripting. The documentation refers to 'Windows Server or Linux machines' in Azure Arc, but does not provide parity in examples or instructions for Linux environments. No Linux-specific troubleshooting or management patterns are discussed.
Recommendations
  • Provide Linux/Bash command examples alongside or before PowerShell examples, especially for common tasks.
  • Include references to Linux-native tools (e.g., Bash, SSH, cloud-init) where relevant.
  • Ensure that management tool sections mention cross-platform compatibility and highlight Linux usage patterns.
  • Add troubleshooting and automation examples for Linux VMs, not just Windows.
  • Explicitly state when instructions or features apply equally to Linux and Windows, or note any differences.
GitHub Create Pull Request
Lighthouse Monitor delegated resources at scale ...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for resource provider registration, mentioning PowerShell as a primary automation tool, and omitting equivalent Linux/CLI instructions. There are no Bash, Azure CLI, or cross-platform automation examples, and PowerShell is referenced before any other tool, reinforcing a Windows-centric approach.
Recommendations
  • Include Azure CLI (az) examples alongside PowerShell for resource provider registration and other automation tasks.
  • Provide Bash script equivalents for common operations, especially those relevant to Linux users.
  • Explicitly mention cross-platform options for automation accounts and scripting, clarifying that PowerShell Core and Azure CLI are available on Linux and macOS.
  • Reorder examples or provide parallel instructions so that Windows and Linux approaches are presented with equal prominence.
  • Add notes or links to documentation for using Azure Monitor and Log Analytics from Linux environments.
GitHub Create Pull Request
Lighthouse Monitor delegation changes in your managing tenant ...ticles/lighthouse/how-to/monitor-delegation-changes.md
High Priority View Details →
Scanned: 2026-01-11 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 providing detailed PowerShell scripts for querying delegation changes, referencing PowerShell first in code examples, and not offering equivalent Linux/bash scripting examples. While Azure CLI is briefly mentioned for role assignment, the main workflow and automation are shown only in PowerShell, which is primarily a Windows tool. There are no bash, shell, or Python examples for Linux users, and the sample script for querying activity logs is exclusively in PowerShell.
Recommendations
  • Provide equivalent bash or Python scripts for querying delegation changes using REST API calls, suitable for Linux environments.
  • Include Azure CLI examples for all major operations, especially for querying activity logs, not just for role assignment.
  • Present code samples in a cross-platform manner, e.g., side-by-side PowerShell and bash/Python examples.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or clarify platform requirements for scripts.
  • Reference Linux tools and patterns where appropriate, such as using curl, jq, or az CLI for automation.
GitHub Create Pull Request
Lighthouse Onboard all subscriptions in a management group ...articles/lighthouse/how-to/onboard-management-group.md
High Priority View Details →
Scanned: 2026-01-11 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, with no equivalent example for Azure CLI, Bash, or other cross-platform tools. This creates a bias toward Windows users and may hinder Linux or macOS users who prefer or require non-PowerShell solutions. Additionally, the PowerShell example is presented as the primary (and only) automation method, reinforcing a Windows-first approach.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell scripts shown, especially for policy assignment and deployment steps.
  • Explicitly mention that both PowerShell and Azure CLI can be used for these operations, and provide links to relevant Azure CLI documentation.
  • Consider including Bash script examples or instructions for use in Linux/macOS environments.
  • Where possible, use cross-platform terminology and avoid implying that PowerShell is the default or only automation tool.
  • Add a table or section comparing PowerShell and Azure CLI commands for common tasks in the onboarding process.
GitHub Create Pull Request
Lighthouse Onboard a customer to Azure Lighthouse ...ob/main/articles/lighthouse/how-to/onboard-customer.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. While it does provide both Azure CLI and Azure PowerShell examples for deployment and confirmation steps, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is not clearly marked as cross-platform. Additionally, references to using the Azure portal (which is platform-agnostic but often associated with Windows workflows) are frequent. There is no mention of Linux-specific shell scripting, nor are there examples using Bash or other Linux-native tools. The troubleshooting and process steps do not address Linux-specific considerations, and PowerShell is presented as a primary automation option without clarifying its cross-platform support.
Recommendations
  • Explicitly mention that Azure CLI and PowerShell are available on Linux and macOS, and provide guidance for installing and using them on those platforms.
  • Add Bash shell script examples for deployment and confirmation steps, especially for users who prefer native Linux tools.
  • Clarify that Azure PowerShell is cross-platform, and provide links or instructions for installing it on Linux.
  • Include troubleshooting tips relevant to Linux environments, such as file permissions or shell differences.
  • Ensure that references to the Azure portal do not imply a Windows-only experience, and mention browser compatibility on Linux.
  • Consider adding a section comparing automation options for Windows and Linux users, highlighting parity and differences.
GitHub Create Pull Request
Lighthouse Deploy Azure Policy to delegated subscriptions at scale ...lob/main/articles/lighthouse/how-to/policy-at-scale.md
High Priority View Details →
Scanned: 2026-01-11 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 for all examples and instructions, which is primarily a Windows-centric tool. There are no examples using Bash, Azure CLI, or other cross-platform tools, nor is there any mention of Linux or macOS workflows. The use of PowerShell cmdlets and patterns (e.g., Select-AzSubscription, New-AzSubscriptionDeployment) reinforces a Windows-first approach and may alienate users on Linux or macOS who prefer Bash or Azure CLI.
Recommendations
  • Provide equivalent examples using Azure CLI (az commands) and Bash scripts alongside PowerShell examples.
  • Explicitly mention that the process can be performed on Linux/macOS and link to relevant cross-platform tooling.
  • Add a section comparing PowerShell and Azure CLI approaches for deploying policies at scale.
  • Avoid assuming PowerShell as the default and clarify prerequisites for each platform.
  • Reference documentation for installing and using Azure CLI on Linux/macOS.
GitHub Create Pull Request
Lighthouse Cross-tenant management experiences ...hthouse/concepts/cross-tenant-management-experience.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias, primarily in the order and emphasis of tooling. Azure PowerShell (a Windows-centric tool) is mentioned before Azure CLI, and the only explicit command example is for PowerShell. Windows Server is mentioned before Linux in hybrid management scenarios. There is no explicit Linux shell example, and Windows terminology/tools are referenced more frequently or earlier than their Linux equivalents.
Recommendations
  • Present Azure CLI examples before or alongside Azure PowerShell examples, and include explicit Linux shell usage where relevant.
  • When listing supported operating systems (e.g., for Azure Arc-enabled servers), mention Linux before or alongside Windows Server.
  • Provide balanced examples for both Windows and Linux environments, especially in hybrid management scenarios.
  • Avoid defaulting to Windows-centric terminology (e.g., PowerShell cmdlets) and ensure parity with Linux tools and workflows.
  • Add explicit Linux shell command examples where management tasks are discussed.
GitHub Create Pull Request
Lighthouse Monitor delegated resources at scale ...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
High 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 providing only Azure PowerShell examples for key resource provider registration tasks, mentioning PowerShell as the sole automation method, and omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux users. The instructions and code samples focus exclusively on Windows-centric tooling and scripting, with no mention of Linux-native alternatives or cross-platform approaches.
Recommendations
  • Add Azure CLI examples alongside PowerShell for resource provider registration and other automation tasks.
  • Explicitly mention that Azure CLI and Bash can be used on Linux and macOS, and provide sample commands.
  • When listing automation options, present cross-platform tools (Azure CLI, REST API) before or alongside PowerShell.
  • Include notes or links to documentation for Linux users, ensuring parity in guidance for both Windows and Linux environments.
  • Review all code samples and ensure that for every PowerShell example, a CLI/Bash equivalent is provided.
GitHub Create Pull Request
Lighthouse Onboard a customer to Azure Lighthouse ...ob/main/articles/lighthouse/how-to/onboard-customer.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. While Azure CLI is included (which is cross-platform), Azure PowerShell is given equal prominence and is featured in all example sections. There are no explicit Linux shell (bash) or automation examples, and no mention of Linux-specific tools or workflows. The instructions for command-line deployment and verification are presented as Azure CLI and PowerShell tabs, but PowerShell is a Windows-centric tool, and there is no parity for native Linux shell scripting or automation. Additionally, references to 'Cloud Shell' do not clarify that it is available on both Windows and Linux, and the documentation does not provide any bash or shell script equivalents.
Recommendations
  • Add bash shell script examples for template deployment and verification, using Azure CLI commands, to demonstrate Linux-native workflows.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Explicitly mention that Cloud Shell is available on both Windows and Linux, and provide instructions for accessing it from Linux environments.
  • Consider including automation examples using bash scripting for common onboarding tasks.
  • Review references to PowerShell and ensure they are balanced with Linux-native alternatives where possible.
GitHub Create Pull Request
Lighthouse Azure Lighthouse architecture ...blob/main/articles/lighthouse/concepts/architecture.md
High 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 primarily referencing Azure PowerShell for resource creation and management tasks, with specific cmdlets mentioned and no equivalent Azure CLI or REST API examples provided inline. PowerShell is a Windows-centric tool, and its usage is described before mentioning Azure CLI in the 'Next steps' section. There are no Linux-specific examples or guidance, and the documentation does not address cross-platform usage patterns directly.
Recommendations
  • Include Azure CLI examples alongside PowerShell examples for all resource creation and management tasks, especially for registration definition and assignment.
  • Explicitly mention REST API options and provide sample requests for users who prefer platform-agnostic approaches.
  • Ensure that references to management tools are balanced, listing Azure CLI before or alongside PowerShell where appropriate.
  • Add notes or sections highlighting cross-platform compatibility and usage, including instructions for Linux and macOS users.
  • Review and update onboarding instructions to show both PowerShell and CLI workflows in parallel.
GitHub Create Pull Request
Lighthouse Monitor delegation changes in your managing tenant ...ticles/lighthouse/how-to/monitor-delegation-changes.md
High 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 providing detailed PowerShell scripts for querying delegation changes and referencing Windows-centric tools and patterns. While Azure CLI is mentioned for role assignment, all advanced scripting and automation examples are exclusively given in PowerShell, with no equivalent Bash or Linux shell scripts. There is no guidance for Linux users on how to perform the same monitoring tasks outside of PowerShell, and the PowerShell script is presented first and in greater detail.
Recommendations
  • Provide equivalent Bash or shell script examples for querying delegation changes using REST API calls with curl or az CLI, suitable for Linux environments.
  • Ensure that Azure CLI examples are as detailed and comprehensive as PowerShell examples, especially for advanced automation tasks.
  • Explicitly mention cross-platform compatibility and provide instructions for both Windows and Linux users.
  • Consider including sample scripts in Python or other cross-platform languages for automation.
  • Reorder examples so that Azure CLI or platform-neutral solutions are presented before or alongside PowerShell scripts.
GitHub Create Pull Request
Lighthouse Onboard all subscriptions in a management group ...articles/lighthouse/how-to/onboard-management-group.md
High Priority View Details →
Scanned: 2026-01-10 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, with no equivalent CLI (az), Bash, or Linux-native instructions. The use of PowerShell as the sole automation example assumes a Windows environment or familiarity with PowerShell, which may disadvantage Linux or cross-platform users. There is no mention of Azure CLI or other cross-platform tools, and the PowerShell example is presented as the primary (and only) method.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, especially for policy assignment and deployment.
  • Explicitly mention that PowerShell Core is cross-platform, or clarify if the script requires Windows PowerShell.
  • Provide Bash or shell script examples where appropriate, or at least reference how Linux/macOS users can perform the same tasks.
  • When listing automation options (e.g., Logic Apps, scripts), avoid assuming PowerShell is the default and present CLI or REST API alternatives.
  • Consider a 'Choose your platform' section or table that shows how to perform key steps using PowerShell, Azure CLI, and REST API.
GitHub Create Pull Request
Lighthouse Deploy Azure Policy to delegated subscriptions at scale ...lob/main/articles/lighthouse/how-to/policy-at-scale.md
High 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 exclusively uses PowerShell for all examples and instructions, which is primarily associated with Windows environments. There are no examples or guidance for using Azure CLI, Bash, or other Linux-native tools. The use of PowerShell cmdlets and patterns is pervasive, and there is no mention of Linux or cross-platform alternatives, which may hinder accessibility for users on Linux or macOS.
Recommendations
  • Provide equivalent examples using Azure CLI commands, which are natively supported on Linux and macOS.
  • Add notes or sections indicating how to perform these tasks in Bash or other shell environments.
  • Clarify that PowerShell Core is cross-platform, but also explicitly support and document Linux-native workflows.
  • Ensure that tool recommendations and examples do not assume a Windows-first environment; present cross-platform options side-by-side.
  • Include troubleshooting or setup guidance for Linux users where necessary (e.g., installing Azure CLI, authentication differences).
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/concepts/architecture.md ...blob/main/articles/lighthouse/concepts/architecture.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 primarily referencing Azure PowerShell for resource creation and management, with no explicit examples or instructions for Linux users or alternative tools. PowerShell commands are mentioned before Azure CLI, and there are no bash or Linux-specific examples, which may disadvantage users on non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI examples alongside PowerShell instructions, especially for resource creation and onboarding steps.
  • Include explicit references to cross-platform tools (e.g., bash, Azure CLI) in relevant sections, not just in 'Next steps'.
  • Add sample commands for Linux/macOS environments where appropriate.
  • Clarify that both PowerShell and CLI are supported and provide links to both sets of documentation in all relevant contexts.
  • Avoid assuming PowerShell as the default tool for resource management; present CLI and PowerShell options in parallel.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/monitor-delegation-changes.md ...ticles/lighthouse/how-to/monitor-delegation-changes.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 shell examples. PowerShell is presented first in all code sections, and the main sample script is exclusively PowerShell-based. Although Azure CLI commands are briefly mentioned for role assignment, all advanced scripting and automation guidance is Windows-centric, with no Linux-native alternatives or cross-platform scripting shown.
Recommendations
  • Provide equivalent Bash or shell script examples for querying the Tenant Activity Log using REST API calls, leveraging curl/jq or Azure CLI.
  • Present Azure CLI examples before or alongside PowerShell, especially for common tasks like role assignment and log querying.
  • Explicitly mention cross-platform compatibility for all scripts and tools, and clarify when a script is Windows-only.
  • Offer downloadable sample scripts for Linux/macOS environments, or link to GitHub repositories with both PowerShell and Bash versions.
  • Add guidance for running these tasks in Linux-based Azure Cloud Shell, including any differences in authentication or environment setup.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/onboard-management-group.md ...articles/lighthouse/how-to/onboard-management-group.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only a PowerShell example for assigning the policy, with no equivalent examples for Linux/macOS users (such as Azure CLI or Bash). The use of PowerShell is presented as the default method, which may disadvantage users on non-Windows platforms. There is no mention of cross-platform alternatives or parity in tooling.
Recommendations
  • Add Azure CLI and/or Bash examples for assigning the policy, alongside the PowerShell example.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
  • Where possible, use cross-platform tools or scripts in examples, or provide parallel instructions for both PowerShell and CLI.
  • Clarify that PowerShell is not required and that users can choose their preferred platform/tooling.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/monitor-at-scale.md ...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by providing only Azure PowerShell examples for resource provider registration, referencing PowerShell as the sole automation tool, and omitting equivalent instructions for Linux users (such as Azure CLI or Bash). Windows-centric tools and patterns are mentioned exclusively or before cross-platform alternatives, and there are no Linux-specific or cross-platform code samples for key tasks.
Recommendations
  • Provide Azure CLI and Bash script examples alongside PowerShell commands for resource provider registration and workspace creation.
  • Explicitly mention that automation tasks can be performed on Linux/macOS using Azure CLI, not just PowerShell.
  • Add links to cross-platform documentation and tools where available.
  • Ensure that references to management tools (e.g., automation accounts, scripting) include both Windows and Linux options.
  • Review all code samples and ensure parity between Windows and Linux environments for all major tasks.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/onboard-customer.md ...ob/main/articles/lighthouse/how-to/onboard-customer.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides onboarding instructions for Azure Lighthouse using the Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, PowerShell examples and references are prominent and presented alongside CLI, but there is no mention of Linux-specific patterns, shell scripting, or alternative Linux-native tools. The documentation refers to 'PowerShell' and 'Azure PowerShell' throughout, and troubleshooting steps do not include Linux-specific guidance or command-line alternatives beyond Azure CLI. The order of presentation often lists Azure PowerShell before Azure CLI, and there are no explicit Linux shell (bash/zsh) examples or references to Linux package managers or environments.
Recommendations
  • Add explicit Linux shell (bash/zsh) examples for template deployment, such as using curl, wget, jq, or scripting with az CLI.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide installation instructions for Linux environments.
  • Include troubleshooting steps relevant to Linux environments, such as checking az CLI installation, permissions, and environment variables.
  • When listing command-line options, present Azure CLI before PowerShell to avoid implicit Windows-first ordering.
  • Reference Linux-native automation tools (e.g., cron jobs, shell scripts) for ongoing management and onboarding automation.
  • Add notes or links about using Azure Cloud Shell, which is accessible from any OS and supports both bash and PowerShell.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/policy-at-scale.md ...lob/main/articles/lighthouse/how-to/policy-at-scale.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 for all examples and instructions, which is primarily associated with Windows environments. There are no equivalent examples using Azure CLI, Bash, or other cross-platform tools commonly used on Linux or macOS. The use of PowerShell cmdlets (e.g., Get-AzSubscription, New-AzSubscriptionDeployment) and the lack of mention of Linux-native workflows or tools indicate a strong Windows bias. This may hinder accessibility for users who primarily work in Linux or macOS environments.
Recommendations
  • Provide equivalent examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell usage is required.
  • Include Bash script examples for querying and deploying policies, or reference how to adapt the workflow for Bash/CLI users.
  • Add a section comparing PowerShell and Azure CLI approaches, highlighting platform compatibility.
  • Ensure that tool recommendations and instructions are not exclusively focused on Windows environments.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/concepts/architecture.md ...blob/main/articles/lighthouse/concepts/architecture.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 primarily referencing Azure PowerShell for resource creation and management tasks, mentioning PowerShell cmdlets before Azure CLI, and lacking explicit Linux or cross-platform examples. Windows-centric tools and patterns are referenced without equivalent Linux-focused guidance, which may disadvantage users on non-Windows platforms.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples, especially for resource creation and management tasks.
  • Explicitly mention that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS, and provide installation links for each platform.
  • Include sample commands and workflows using Azure CLI to ensure Linux users have clear guidance.
  • Avoid referencing Windows-specific tools or patterns exclusively; ensure parity in documentation for all supported platforms.
  • Add notes or sections highlighting cross-platform compatibility and best practices for Linux users.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/monitor-at-scale.md ...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 bias toward Windows environments by providing PowerShell-only examples for key tasks (such as registering resource providers), referencing Azure PowerShell as a primary automation method, and omitting equivalent instructions for Linux users (such as Bash/CLI or shell scripting). Windows tools and patterns are mentioned exclusively or before any Linux alternatives, and there is no mention of cross-platform command-line tools like Azure CLI or Bash scripts.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all PowerShell commands, especially for resource provider registration and workspace creation.
  • Explicitly mention that automation can be performed from Linux/macOS environments using Azure CLI or REST APIs, not just PowerShell.
  • Include Bash or shell script examples alongside PowerShell where automation is discussed.
  • Reorder sections or examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside Windows-specific tools.
  • Add notes or tips for Linux users regarding prerequisites and environment setup for Azure automation.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/monitor-delegation-changes.md ...ticles/lighthouse/how-to/monitor-delegation-changes.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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, referencing PowerShell first in code samples, and omitting equivalent Linux/bash examples for advanced scripting tasks. While Azure CLI is briefly mentioned for role assignment, all complex automation and querying is shown only in PowerShell, which is primarily a Windows tool. There are no bash, shell, or Python examples for Linux users, nor guidance for running these tasks natively on Linux.
Recommendations
  • Provide equivalent bash or shell script examples for querying the Tenant Activity Log using REST API calls, suitable for Linux environments.
  • Include Python sample scripts for automation, as Python is cross-platform and widely used on Linux.
  • When listing code samples, present Azure CLI and bash examples before or alongside PowerShell, rather than after.
  • Explicitly mention how Linux users can perform these tasks, including authentication and token acquisition, using native tools.
  • Clarify that PowerShell Core is cross-platform, but provide installation and usage notes for Linux if PowerShell scripts are retained.
  • Add guidance for running scripts in Azure Cloud Shell, which supports both bash and PowerShell, to emphasize platform neutrality.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/onboard-management-group.md ...articles/lighthouse/how-to/onboard-management-group.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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, with no equivalent Azure CLI, Bash, or Linux-native instructions. The use of PowerShell as the sole automation example suggests a Windows-centric approach, and there is no mention of Linux tools or cross-platform alternatives for policy assignment.
Recommendations
  • Add Azure CLI examples for policy assignment, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash script samples for deploying the policy and parameters file.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell must be used.
  • Provide guidance or links for Linux users on installing required tools and running the deployment commands.
  • Ensure that automation instructions (e.g., for Logic Apps) clarify platform independence and do not assume a Windows environment.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/onboard-customer.md ...ob/main/articles/lighthouse/how-to/onboard-customer.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides onboarding instructions for Azure Lighthouse with examples and tooling references for Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is typically associated with Windows environments, and its examples are given equal prominence. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there any explicit Linux-oriented instructions or troubleshooting steps. The documentation does not reference Linux tools or patterns, and the order of presentation often places Azure PowerShell examples before or alongside CLI, which may reinforce a Windows-centric workflow. No explicit Linux shell examples (such as Bash scripts or usage in native Linux environments) are provided.
Recommendations
  • Add explicit Bash shell examples for template deployment and verification, demonstrating usage in native Linux environments.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any platform-specific caveats if relevant.
  • Include troubleshooting steps or notes for common issues encountered on Linux (e.g., file permissions, path formats, environment variables).
  • Consider reordering examples to present Azure CLI (cross-platform) before Azure PowerShell (Windows-centric), or explicitly state platform parity.
  • Reference Linux-native tools (such as curl, jq, or shell scripting) where appropriate for automation or template manipulation.
  • Add a note or section highlighting cross-platform support and best practices for Linux users.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →