Bias Analysis
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-specific tools (such as PowerShell cmdlets) and listing them before or alongside cross-platform CLI options. The only explicit example of a platform-specific tool is the PowerShell cmdlet for Guest Configuration assignment retrieval, which is mentioned in the API/programmatic access table. There are no explicit Linux-only examples or tools, and the documentation does not provide parity for Linux-native commands or workflows (e.g., Bash, shell scripts, or Linux-specific management tools). All UI and API instructions are platform-neutral, but the programmatic access section leans toward Windows by highlighting PowerShell.
Recommendations
- Add Linux-native command examples (e.g., Bash, shell scripts, or Linux management tools) for retrieving compliance data.
- Provide parity in programmatic access documentation by including Linux-specific workflows, such as using curl with REST APIs or az CLI commands in Bash.
- When listing tools or references, avoid putting Windows/PowerShell options first; instead, group CLI and REST API options before platform-specific tools.
- Explicitly mention cross-platform compatibility for all CLI and API tools, and provide usage examples for both Windows and Linux environments.
- Consider adding a section or note clarifying that all compliance reporting features are available and supported on both Windows and Linux machines.
Create Pull Request