Document Details
Azure Secure Isolation Guidance
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
windows_tools
⚠️
powershell_heavy
⚠️
missing_linux_example
Summary:
The documentation exhibits a Windows-centric bias in several areas. Windows technologies, tools, and terminology are frequently mentioned first or exclusively (e.g., Hyper-V, BitLocker, Windows Firewall, Windows Server, RDP, PowerShell), with Linux equivalents either mentioned later, in passing, or omitted. Example commands and operational guidance often reference Windows or PowerShell, with Linux/CLI alternatives less prominent or missing. This can make the documentation less accessible or actionable for Linux-focused users.
Recommendations:
- Ensure all operational guidance, examples, and tool references are provided for both Windows and Linux platforms, with parity in detail and order of presentation.
- When describing Azure features (e.g., VM provisioning, disk encryption, remote access), always include both Windows and Linux workflows, including CLI and SSH examples, not just PowerShell or RDP.
- Avoid using Windows-specific terminology as the default; instead, use platform-neutral language or explicitly mention both platforms (e.g., 'Windows Firewall and Linux iptables').
- In tables or lists, alternate the order of Windows and Linux entries or present them side-by-side.
- Where Windows tools or technologies are referenced (e.g., BitLocker, Hyper-V, Windows Firewall), ensure Linux equivalents (e.g., dm-crypt, KVM, iptables/firewalld) are also described with equal depth.
- Provide links to Linux-specific Azure documentation alongside Windows links.
- Review all examples and ensure that for every PowerShell or Windows-centric example, a Linux/CLI/SSH equivalent is present.
Create pull request