The documentation provides both Azure CLI and Azure PowerShell examples for all Azure resource operations, with tabs for each. However, Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) may create a perception of Windows bias. Additionally, PowerShell examples are given equal prominence to CLI, which is less common for Linux/macOS users. There are no explicit Linux/macOS examples or mentions of platform-specific considerations for those environments, but the core workflow is cross-platform via Azure CLI and Helm. No critical steps are Windows-only, and Linux/macOS users can follow the CLI instructions without issue.

• Clarify that Azure CLI is fully supported on Linux/macOS and is the recommended approach for those platforms.
• Consider making Azure CLI the default or first tab, as it is cross-platform, with PowerShell as a secondary option.
• Add a brief note in the prerequisites section stating that Azure PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
• Explicitly mention that all bash/Helm/kubectl commands are platform-agnostic and work on Linux/macOS/Windows.
• If possible, add a short section or callout for Linux/macOS users to reinforce parity and clarify any minor differences (e.g., installation paths, shell usage).