Governance
496
Total Pages
410
Linux-Friendly Pages
86
Pages with Bias
17.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
186 issues found
Showing 176-186 of 186 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples, but lists PowerShell (a Windows-centric tool) immediately after CLI and before any mention of Linux-specific alternatives. There is no explicit Linux/macOS example or mention of platform differences. However, Azure CLI is cross-platform and presented first, which mitigates bias somewhat. No Windows-only tools or patterns are used, and the Portal instructions are platform-neutral.
Recommendations
- Explicitly state that Azure CLI works on Linux/macOS and Windows.
- Add a note clarifying that PowerShell Core is available cross-platform, or link to installation instructions for Linux/macOS.
- Consider adding a bash shell example (even if it simply calls Azure CLI) to reinforce Linux parity.
- If relevant, mention any platform-specific caveats for running the commands.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is traditionally Windows-centric, and its inclusion as a primary example can indicate a Windows bias. Additionally, the PowerShell example is given equal prominence to the CLI, and is listed before the Portal, which may reinforce Windows-first patterns. No explicit Linux/macOS examples or notes are provided, and there is no mention of shell scripting or Linux-specific usage.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and provide explicit shell/bash examples where appropriate.
- Add notes or sections highlighting usage on Linux/macOS, such as running Azure CLI commands in bash/zsh.
- Consider listing cross-platform tools (Azure CLI) before Windows-centric tools (PowerShell) to reinforce platform neutrality.
- If PowerShell is shown, mention that PowerShell Core is available on Linux/macOS, or provide a Linux/macOS PowerShell example.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric) and the absence of Linux/macOS-specific shell examples (such as Bash or shell scripting) indicate a mild Windows bias. Additionally, the PowerShell example is given equal prominence to the CLI, which may suggest a preference for Windows tooling. No explicit Linux/macOS examples or notes are provided.
Recommendations
- Add explicit Bash/shell examples for Linux/macOS users, demonstrating equivalent queries using Azure CLI.
- Clarify that Azure CLI commands work identically on Linux/macOS and Windows.
- Consider mentioning cross-platform compatibility for both CLI and PowerShell (if using PowerShell Core).
- If PowerShell is required, specify whether PowerShell Core is supported on Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, with PowerShell (a Windows-centric tool) given equal prominence as CLI. The PowerShell example is presented immediately after the CLI example, and no explicit Linux/macOS shell examples (e.g., Bash) are provided. However, the Azure CLI example is cross-platform and shown first, mitigating some bias. No Windows-only tools or patterns are used, and the portal instructions are platform-agnostic.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
- Consider adding explicit Bash or shell examples for Linux/macOS users, especially if there are nuances (e.g., quoting, environment setup).
- Note any platform-specific prerequisites for CLI or PowerShell usage.
- If PowerShell is mentioned, clarify that PowerShell Core is available cross-platform, or provide links to installation instructions for Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Azure CLI and Azure PowerShell examples, with PowerShell (a Windows-centric tool) given equal prominence to Azure CLI. There is no explicit Linux shell example (e.g., Bash), nor any mention of Linux-specific usage patterns. The ordering places Azure CLI first, which is cross-platform, but the inclusion of PowerShell as a primary tab may suggest a Windows bias. No Linux/macOS-specific issues are discussed, but the lack of explicit Linux shell examples may create minor friction for non-Windows users.
Recommendations
- Add explicit Bash shell examples for running Azure CLI commands on Linux/macOS.
- Clarify that Azure CLI works natively on Linux/macOS and provide installation/use instructions if not already present elsewhere.
- Consider de-emphasizing PowerShell unless Windows-specific functionality is required.
- Add notes or tabs for Linux/macOS users to ensure parity and clarity.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell is given equal prominence and is called out explicitly, which may indicate a slight Windows bias. The CLI examples are cross-platform, but PowerShell is primarily a Windows tool (though available on Linux, it's less commonly used there). The ordering of examples (CLI first, then PowerShell) is good for parity, but the explicit PowerShell tab and syntax may still signal a Windows-centric approach.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it for Linux/macOS users.
- Add explicit notes that PowerShell is available on Linux/macOS, but CLI is preferred for those platforms.
- Consider adding bash script examples or usage patterns for Linux users, especially for automation.
- If PowerShell is required for any functionality, document equivalent Linux-native alternatives or workarounds.
- Ensure that CLI examples are tested and work as expected on Linux/macOS shells.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but the PowerShell example is given its own dedicated tab, which is a Windows-centric tool. The CLI example is cross-platform, but PowerShell is highlighted as an equal alternative, which may suggest a Windows-first approach. No Linux/macOS-specific instructions or notes are given, and there is no mention of shell-specific considerations for Linux users (e.g., escaping characters in Bash).
Recommendations
- Add explicit notes clarifying that Azure CLI works on Linux/macOS and Windows, and provide any necessary shell-specific guidance (such as escaping $ characters in Bash).
- Consider providing a Bash-specific example or a note about how to run the CLI command in Bash, especially regarding escaping characters.
- If PowerShell is mentioned, clarify that PowerShell Core is available cross-platform, or link to installation instructions for Linux/macOS users.
- Ensure that examples do not assume Windows as the default environment.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples, but lists Azure PowerShell (a Windows-centric tool) as a primary tab alongside CLI. There is no explicit Linux or macOS example, but the CLI example is cross-platform. PowerShell is shown as a first-class option, which may suggest a Windows bias, especially since no Bash or Linux shell example is given.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
- Add explicit Bash or shell examples for Linux/macOS users, if any platform-specific steps exist.
- Consider listing Azure CLI before PowerShell to emphasize cross-platform support.
- Add a note about platform compatibility for each tool.
Governance
Azure Machine Configuration prerequisites
...chine-configuration/overview/02-setup-prerequisites.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing Windows validation tools first, referencing PowerShell DSC for both Windows and Linux, and providing links to Azure PowerShell before Azure CLI. Linux tools (Chef InSpec) are mentioned, but PowerShell DSC is emphasized as the primary validation tool for both platforms. There is no explicit omission of Linux-specific deployment instructions, but Windows-centric terminology and ordering may create friction for Linux users.
Recommendations
- Present Linux and Windows examples/tools in parallel or alternate order to avoid Windows-first perception.
- Include explicit Linux/macOS deployment instructions and examples, especially for managed identity and extension installation.
- Highlight native Linux configuration management tools (e.g., Ansible, native shell scripts) if supported, or clarify why PowerShell DSC is used on Linux.
- Provide Azure CLI examples before or alongside Azure PowerShell, as CLI is cross-platform.
- Clarify any platform-specific limitations or differences in agent behavior.
Governance
View Machine Configuration Compliance Reporting
...rnance/machine-configuration/how-to/view-compliance.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page provides a generally cross-platform overview of Azure Machine Configuration compliance reporting, but there is a mild Windows bias. PowerShell is the only shell-specific example referenced (Get-AzGuestConfigurationAssignment), and Windows-centric tooling (PowerShell cmdlet) is listed before Linux/macOS equivalents in the programmatic access table. CLI examples (az CLI) are present, but no Bash or Linux-specific shell examples are shown. The documentation does not explicitly mention Linux/macOS compatibility or provide parity in example commands for those platforms.
Recommendations
- Add explicit Bash or shell examples for Linux/macOS users alongside PowerShell examples.
- Clarify that az CLI and REST API are cross-platform and provide example usage on Linux/macOS.
- List Linux/macOS tools (az CLI, REST API) before or alongside PowerShell cmdlets in tables and references.
- Include screenshots or walkthroughs from Linux/macOS environments where applicable.
- State platform compatibility for each tool or API referenced.
Governance
How to sign machine configuration packages
...ration/how-to/develop-custom-package/6-sign-package.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias: Windows/Powershell examples and instructions are presented first, with detailed PowerShell scripts and references to Windows certificate stores. Linux instructions are present but less detailed and still use PowerShell for some steps, which is less common for Linux users. Windows tools and patterns (certificate stores, PowerShell cmdlets) are mentioned before their Linux equivalents, and Azure Policy examples reference Windows resources first.
Recommendations
- Present Linux and Windows instructions in parallel or alternate order to avoid Windows-first bias.
- Provide Linux-native command-line examples (e.g., using OpenSSL for certificate management) instead of PowerShell for Linux steps.
- Expand Linux sections to include more detail on certificate/key management, installation, and verification using standard Linux tools.
- Reference Linux-specific Azure Policy templates and documentation where available.
- Clarify when PowerShell is required on Linux and suggest alternatives if possible.