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 26-50 of 51 flagged pages
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 →
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 a Windows-centric tool. There are no examples using Azure CLI, Bash, or other cross-platform tools. The focus on PowerShell commands and lack of Linux/macOS alternatives or parity demonstrates a clear Windows bias.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available on Linux/macOS, and clarify if the examples are compatible.
- Provide Bash script samples or instructions for common Linux workflows.
- Reorder or balance examples so that Windows and Linux approaches are presented equally, rather than Windows/PowerShell first or exclusively.
- Include notes on prerequisites for both Windows and Linux environments (e.g., installation of Azure CLI, PowerShell Core, required modules).
Create Pull Request
Lighthouse
Monitor delegation changes in your managing tenant
...ticles/lighthouse/how-to/monitor-delegation-changes.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides detailed PowerShell scripts and examples for monitoring delegation changes in Azure Lighthouse, with only brief Azure CLI coverage for role assignment. The main workflow for querying and reporting on delegation changes is shown exclusively in Azure PowerShell, with no equivalent Bash, Python, or cross-platform REST API example. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other scripting environments.
Recommendations
- Provide a full Bash or Python example for querying the Tenant Activity Log using Azure CLI and/or REST API calls.
- Include cross-platform instructions for authentication and token acquisition (e.g., using az CLI, MSAL libraries, or direct REST API calls).
- Explicitly note PowerShell requirements and offer alternatives for non-Windows environments.
- Where possible, show Azure CLI and REST API examples alongside PowerShell, especially for critical workflows like activity log querying.
Lighthouse
Deploy Azure Policy to delegated subscriptions at scale
...lob/main/articles/lighthouse/how-to/policy-at-scale.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively uses PowerShell for all code examples and deployment instructions, without providing equivalent Azure CLI, Bash, or cross-platform alternatives. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools. The use of PowerShell cmdlets and patterns is pervasive throughout the guide, and no mention is made of Linux-friendly workflows.
Recommendations
- Add equivalent Azure CLI examples for each PowerShell script and command.
- Explicitly mention that PowerShell Core is cross-platform, and provide installation guidance for Linux/macOS users if PowerShell is required.
- Include Bash or shell script alternatives where possible, especially for querying and deploying resources.
- Clarify tool requirements at the start of the article, and link to cross-platform installation guides.
- Consider reordering examples so that Azure CLI or platform-neutral approaches are shown first or alongside PowerShell.
Medium Priority
View Details →
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 provided. The 'Next steps' section lists Azure CLI and PowerShell, but the main body only details PowerShell usage, and PowerShell is mentioned before CLI. There are no Linux/macOS-specific examples or guidance, which may create friction for users on those platforms.
Recommendations
- Include Azure CLI examples alongside PowerShell for key operations such as creating registration definitions and assignments.
- Reference REST API methods for platform-agnostic automation.
- Ensure that CLI examples are given equal prominence to PowerShell, and avoid listing Windows tools first unless they are required.
- Add notes or links to cross-platform tooling guidance for Linux/macOS users.
Lighthouse
Monitor delegated resources at scale
...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
Medium Priority
View Details →
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.
Lighthouse
Onboard all subscriptions in a management group
...articles/lighthouse/how-to/onboard-management-group.md
Medium Priority
View Details →
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.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page on Azure Lighthouse architecture demonstrates a moderate Windows bias. PowerShell is referenced as the primary example for creating registration definitions, and Azure PowerShell is mentioned before Azure CLI or other cross-platform tools. While Azure CLI is referenced in the 'Next steps' section, the main body of the documentation prioritizes PowerShell, which is more commonly associated with Windows environments. No explicit Linux/macOS examples or workflows are provided.
Recommendations
- Include Azure CLI examples alongside PowerShell for key operations such as creating registration definitions and assignments.
- Clarify that both Azure PowerShell and Azure CLI are cross-platform, and provide links or code snippets for both.
- Consider adding a brief section or callout for Linux/macOS users, highlighting any platform-specific considerations or confirming parity.
- Ensure that references to management tools do not implicitly suggest Windows-only workflows.
Lighthouse
Monitor delegated resources at scale
...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the section about registering resource providers in the managing tenant. The only provided automation example uses Azure PowerShell, with no mention of Azure CLI or REST API alternatives, which are more cross-platform and commonly used on Linux/macOS. The documentation also refers to PowerShell before any other tool, and does not provide Linux/macOS-specific guidance for these steps.
Recommendations
- Add Azure CLI examples alongside PowerShell for resource provider registration and service principal creation.
- Explicitly mention that Azure CLI and REST API can be used on Linux/macOS for all automation steps.
- Where PowerShell is referenced, provide equivalent commands for other platforms or link to cross-platform documentation.
- Clarify that the Azure portal and Resource Manager templates are platform-agnostic, and highlight their use for Linux/macOS users.
Lighthouse
Onboard all subscriptions in a management group
...articles/lighthouse/how-to/onboard-management-group.md
Medium Priority
View Details →
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 ARM template instructions. This creates friction for Linux/macOS users who may not use PowerShell, and the example is presented as the sole method for this critical step.
Recommendations
- Add Azure CLI (az policy assignment create) instructions for assigning the policy at the management group level.
- Provide Bash or cross-platform scripting examples where possible.
- Clarify that PowerShell is one option and link to documentation for other methods (e.g., Azure Portal, ARM templates, REST API).
- Consider presenting CLI or cross-platform examples before or alongside PowerShell to avoid Windows-first impression.
Lighthouse
Monitor delegation changes in your managing tenant
...ticles/lighthouse/how-to/monitor-delegation-changes.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation provides detailed PowerShell scripts for querying delegation changes, but does not offer equivalent examples using Bash, shell scripting, or cross-platform tools. While Azure CLI is mentioned for role assignment, the main workflow for querying and reporting is PowerShell-centric, which may create friction for Linux/macOS users. PowerShell examples are shown first and in greater detail, with no alternative Linux-native scripting guidance.
Recommendations
- Provide equivalent Bash or shell script examples for querying the Tenant Activity Log using Azure CLI and REST API calls.
- Highlight cross-platform approaches, such as using Python or other language SDKs, for automation tasks.
- Clarify that PowerShell Core is available cross-platform, but also offer guidance for users who prefer native Linux/macOS tools.
- Ensure that Azure CLI examples are as detailed as PowerShell ones, especially for querying and reporting delegation changes.
Lighthouse
Deploy Azure Policy to delegated subscriptions at scale
...lob/main/articles/lighthouse/how-to/policy-at-scale.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively provides PowerShell examples and references Azure PowerShell cmdlets for all steps, without mentioning or providing equivalent instructions for Azure CLI, Bash, or other cross-platform tools. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native shell environments.
Recommendations
- Add equivalent Azure CLI examples for all major steps (querying Resource Graph, deploying ARM templates, validating policy, and cleanup).
- Explicitly mention that PowerShell is available cross-platform, but provide installation guidance for Linux/macOS if PowerShell is required.
- Where possible, show both PowerShell and Azure CLI/Bash examples side-by-side, or link to CLI documentation.
- Clarify tool prerequisites for non-Windows users at the start of the document.
Medium Priority
View Details →
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 shown inline. Windows tooling (PowerShell cmdlets) is mentioned before Linux-friendly alternatives, and there are no explicit Linux/macOS instructions or examples for onboarding or resource management tasks.
Recommendations
- Add explicit Azure CLI examples for creating registration definitions and assignments alongside PowerShell examples.
- Reference REST API methods for resource creation and management to ensure cross-platform accessibility.
- Ensure that CLI and API instructions are presented before or alongside PowerShell examples, not after.
- Include notes or links for Linux/macOS users on how to install and use Azure CLI for these tasks.
Lighthouse
Monitor delegated resources at scale
...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
Medium Priority
View Details →
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 in the managing tenant, where only Azure PowerShell commands are provided. There is no mention of equivalent Azure CLI or Bash examples, nor are Linux/macOS automation patterns discussed. Windows tools and PowerShell are referenced exclusively and before any cross-platform alternatives, which may create friction for Linux/macOS users.
Recommendations
- Provide Azure CLI examples alongside PowerShell for resource provider registration and service principal creation.
- Explicitly mention that Azure CLI and Bash can be used for automation tasks, and link to relevant documentation.
- Reorder examples or provide both Windows and Linux/macOS instructions in parallel, ensuring parity.
- Clarify which steps are platform-agnostic and which require specific OS tools, offering alternatives where possible.
Lighthouse
Monitor delegation changes in your managing tenant
...ticles/lighthouse/how-to/monitor-delegation-changes.md
Medium Priority
View Details →
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 shown for querying delegation changes, with a lengthy, complex 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 examples are PowerShell-only. There is no guidance for Linux/macOS users on how to perform these tasks outside of PowerShell, nor are alternative tools or scripts referenced.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for querying the Tenant Activity Log and reporting delegation changes, ensuring Linux/macOS users can follow along without PowerShell.
- Explicitly note cross-platform options and clarify which commands/tools work on all platforms.
- Reference REST API usage directly with curl or other cross-platform tools, not just via PowerShell.
- Consider reordering examples so that Azure CLI or platform-neutral approaches are presented first or alongside PowerShell.
Lighthouse
Deploy Azure Policy to delegated subscriptions at scale
...lob/main/articles/lighthouse/how-to/policy-at-scale.md
Medium Priority
View Details →
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 and instructions, without mentioning or providing alternatives for Linux/macOS users (such as Azure CLI or Bash). Windows-centric tools and patterns are referenced throughout, and no Linux/macOS shell or cross-platform instructions are given. This creates friction for users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI (az) examples alongside PowerShell commands for all major steps.
- Explicitly mention that Azure PowerShell is available cross-platform, but clarify installation and usage differences for Linux/macOS.
- Include Bash shell script examples where appropriate, especially for loops and resource queries.
- Add a section on platform prerequisites, clarifying support for Linux/macOS and how to set up the required tools.
- Reorder examples or alternate between Windows and Linux/macOS instructions to avoid Windows-first bias.
Lighthouse
Onboard all subscriptions in a management group
...articles/lighthouse/how-to/onboard-management-group.md
Medium Priority
View Details →
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 equivalent CLI (az), Bash, or Linux/macOS instructions. This creates friction for users on non-Windows platforms, as PowerShell is not the default or preferred tool for many Linux/macOS administrators. The documentation also introduces the PowerShell example before mentioning any alternatives, and does not clarify cross-platform options.
Recommendations
- Add equivalent Azure CLI (az) commands for policy assignment, which are natively supported on Linux/macOS.
- Explicitly state that PowerShell is cross-platform, or link to instructions for installing PowerShell on Linux/macOS if PowerShell must be used.
- Present CLI and PowerShell examples side-by-side, or indicate which tools are available for each platform.
- Include Bash script examples where appropriate, especially for tasks like file editing or deployment.
Medium Priority
View Details →
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-specific instructions or examples, and the use of PowerShell may implicitly favor Windows users. The Azure portal instructions are platform-neutral, but command-line guidance leans toward Windows-first patterns.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily used on Windows.
- Include notes or examples for Linux users, such as using Bash or referencing shell environments.
- Clarify that Cloud Shell supports both PowerShell and Bash, and provide guidance for selecting the preferred shell.
- Avoid implying PowerShell is the default or preferred method unless there is a technical reason.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides step-by-step instructions for removing delegations in Azure Lighthouse, with examples for both PowerShell and Azure CLI. However, the PowerShell example is presented before the Azure CLI example, and there is no mention of Linux-specific tools or shell environments. The use of PowerShell (which is traditionally associated with Windows) as the first example and lack of explicit Linux guidance may indicate a subtle Windows bias.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and commonly used on Linux.
- Explicitly mention that both PowerShell and Azure CLI are available on Linux, macOS, and Windows, and provide guidance for running commands in Bash or other Linux shells.
- Include screenshots or instructions for using the Azure portal on non-Windows platforms if relevant.
- Add notes or tips for Linux users, such as using Bash aliases or integrating with Linux automation tools.
- Ensure terminology and instructions do not assume a Windows environment (e.g., avoid references to Windows-specific shell behaviors or file paths).
Lighthouse
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/concepts/cross-tenant-management-experience.md
...hthouse/concepts/cross-tenant-management-experience.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias, primarily in the 'APIs and management tool support' section, where Azure PowerShell is mentioned before Azure CLI, and the PowerShell example is more detailed. There are no Linux-specific examples or tools referenced, and the documentation does not mention Linux shell equivalents (e.g., Bash) or provide parity in command-line examples. However, the page does mention managing both Windows and Linux machines with Azure Arc, which helps mitigate bias.
Recommendations
- Provide Linux/Bash shell examples alongside PowerShell examples, especially for common management tasks.
- Mention Azure CLI before or alongside Azure PowerShell to avoid 'Windows first' ordering.
- Include references to Linux-native tools or workflows where relevant (e.g., Bash scripts, SSH, cloud-init).
- Clarify that Azure CLI is cross-platform and suitable for Linux users.
- Add explicit examples or links for managing Linux resources, not just mentioning their existence.
Lighthouse
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/remove-delegation.md
...b/main/articles/lighthouse/how-to/remove-delegation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents PowerShell instructions before Azure CLI examples for removing delegations, which may suggest a Windows-first approach. PowerShell is a Windows-centric tool, and its prominence can indicate bias, especially if not balanced with Linux-friendly alternatives. However, Azure CLI instructions are also provided, and no exclusive Windows tools or patterns are mentioned. Portal instructions are platform-neutral.
Recommendations
- Present Azure CLI examples before PowerShell examples to prioritize cross-platform tools.
- Explicitly mention that Azure CLI works natively on Linux and macOS, while PowerShell may require additional setup.
- Add Bash script examples where appropriate to further support Linux users.
- Clarify that all portal instructions are platform-agnostic and accessible from any OS.
- Review other documentation pages for similar ordering or tool selection biases.
Lighthouse
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/remove-delegation.md
...b/main/articles/lighthouse/how-to/remove-delegation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents PowerShell instructions before Azure CLI examples in the 'Service providers' section, and refers to PowerShell-specific commands and patterns. While Azure CLI examples are included, there is a subtle preference for Windows/PowerShell tooling, which may be less familiar or accessible to Linux users. No Linux-specific shell examples (e.g., bash scripts) or explicit mention of Linux environments are provided.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for Linux users where relevant.
- Include bash script examples or usage notes for Linux environments, such as how to run these commands in a Linux shell.
- Avoid language that assumes use of PowerShell or Windows tools as the default; clarify that both PowerShell and CLI are supported across platforms.
Lighthouse
Cross-tenant management experiences
...hthouse/concepts/cross-tenant-management-experience.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for cross-tenant management, but PowerShell is mentioned first and in more detail, with a specific cmdlet highlighted. While Azure CLI is also referenced, the order and emphasis may subtly favor Windows users. No Linux-specific tools or examples are missing, and the CLI coverage ensures Linux/macOS users can complete all tasks. No Windows-only tools or patterns are used outside PowerShell.
Recommendations
- Present Azure CLI and PowerShell examples in parallel, or alternate which is shown first.
- Explicitly state that both CLI and PowerShell are cross-platform, and highlight CLI as a first-class option for Linux/macOS users.
- Where possible, provide example commands for both CLI and PowerShell in the same section.
- Add a brief note clarifying that all management tasks can be performed from Linux/macOS using Azure CLI.
Lighthouse
Cross-tenant management experiences
...hthouse/concepts/cross-tenant-management-experience.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for cross-tenant management, but PowerShell is mentioned first and in more detail. There is a slight tendency to reference Windows-centric tools (PowerShell) before cross-platform alternatives (CLI), which may create minor friction for Linux/macOS users. However, Linux and non-Windows scenarios (e.g., Azure Arc for Linux servers, AKS, Azure CLI) are referenced throughout, and no critical functionality is Windows-only.
Recommendations
- Present Azure CLI and PowerShell examples in parallel, or alternate which is shown first.
- Explicitly state that both CLI and PowerShell are cross-platform and provide links to installation/use on Linux/macOS.
- Where PowerShell cmdlets are referenced, ensure equivalent CLI commands are also provided and described.
- Add a brief note clarifying that all management tasks can be performed from Linux/macOS using Azure CLI and REST APIs.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides step-by-step instructions for removing delegations using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is presented before the Azure CLI example, and PowerShell is typically associated with Windows environments. There are no explicit Linux/macOS-only instructions or examples, and the documentation does not mention platform-specific considerations for running these commands. However, both Azure CLI and PowerShell Core are cross-platform, and the examples given can be executed on Linux/macOS with appropriate installations.
Recommendations
- Explicitly mention that both Azure CLI and PowerShell Core are available on Linux and macOS, and provide installation links.
- Alternate the order of examples, sometimes showing Azure CLI before PowerShell to avoid implicit Windows-first bias.
- Add a brief note clarifying that all command-line examples work on Linux/macOS as well as Windows.
- If there are platform-specific caveats (e.g., authentication, environment setup), include those details.
Lighthouse
Cross-tenant management experiences
...hthouse/concepts/cross-tenant-management-experience.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by mentioning Azure PowerShell before Azure CLI in the APIs and management tool support section, and by providing a PowerShell-specific example (Get-AzSubscription) with more detail than the equivalent Azure CLI command. No Linux/macOS-specific tools or examples are given, but Azure CLI is referenced and supported. No critical tasks are Windows-only, and most examples are cross-platform or generic.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side, or alternate which is shown first.
- Provide explicit Linux/macOS usage notes or examples where relevant, especially for command-line tasks.
- Clarify that Azure CLI is fully supported on Linux/macOS and link to installation guides for non-Windows platforms.
- Avoid giving more detail or emphasis to PowerShell commands than to CLI equivalents.