The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for managing AKS authorized IP ranges, but consistently lists the Azure CLI example first. There are no explicit Windows-only tools or patterns, and no critical steps are exclusive to Windows. The use of PowerShell is present but not dominant, and Linux/macOS users are not blocked from completing any tasks.

• Continue listing Azure CLI examples first, as they are cross-platform, but clarify explicitly that Azure CLI works on Linux/macOS/Windows and Azure PowerShell is primarily for Windows.
• Add a note for Linux/macOS users that PowerShell Core is available cross-platform, but Azure CLI is recommended for native shell compatibility.
• Where possible, provide Bash-only examples for common Linux/macOS usage patterns (e.g., using curl instead of dig for IP retrieval).
• Ensure troubleshooting and connectivity instructions mention Linux/macOS tools (e.g., how to find public IP with curl or wget).