Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page provides both Windows (PowerShell) and Linux (CLI) references for enabling encryption features, but there is a consistent pattern of listing Windows/PowerShell examples and links before Linux/CLI equivalents. Some references, such as to the Cryptography API: Next Generation, are Windows-specific. The main walkthroughs and 'Next steps' sections repeatedly mention PowerShell before CLI, and some deep links for advanced features (e.g., automatic key rotation) point to Windows/PowerShell guides first. There is no outright omission of Linux instructions, but the ordering and tool emphasis suggest a Windows-centric approach.
Recommendations
- Alternate the order of Windows and Linux examples and links throughout the documentation, or present them side-by-side.
- Provide equal prominence and detail for both Azure PowerShell and Azure CLI instructions, ensuring Linux users do not need to scroll past Windows content to find relevant guidance.
- Where referencing platform-specific cryptography APIs (e.g., CNG for Windows), also mention Linux equivalents (e.g., dm-crypt, cryptsetup) or clarify their relevance.
- Ensure that deep links for advanced features (e.g., automatic key rotation) are available for both PowerShell and CLI, and referenced equally.
- Consider adding explicit callouts or sections for Linux/macOS users where workflows or tooling differ.
Create Pull Request