Planetary Computer

The documentation exclusively describes role assignment using the Azure portal (a graphical interface most commonly used on Windows), with no mention of CLI, PowerShell, or cross-platform command-line alternatives. There are no Linux/macOS-specific instructions or examples, and the workflow assumes use of the GUI, which is typically associated with Windows environments.

• Add Azure CLI examples for assigning RBAC roles, which work across Windows, Linux, and macOS.
• Include PowerShell examples for users who prefer scripting, but ensure CLI instructions are presented first or alongside.
• Explicitly mention that the Azure portal is accessible from any OS via a web browser, and clarify any OS-specific limitations if present.
• Provide links to cross-platform documentation for managing RBAC via command-line tools.

The documentation exclusively describes RBAC management using the Azure portal GUI, which is primarily a Windows-centric tool. There are no examples or instructions for performing these tasks via cross-platform command-line tools like Azure CLI or PowerShell, nor are Linux/macOS workflows mentioned. This creates friction for users on non-Windows platforms who may prefer or require CLI-based management.

• Add instructions for assigning RBAC roles using Azure CLI, which is cross-platform and works on Linux/macOS.
• Include PowerShell examples, but ensure Azure CLI examples are presented first or alongside for parity.
• Explicitly mention that the Azure portal is web-based and accessible from any OS, but provide CLI alternatives for automation and scripting.
• Where screenshots are used, clarify that the portal is not Windows-specific.

The documentation presents both PowerShell (Windows-centric) and Bash (Linux/macOS-centric) examples for assigning a managed identity, but the PowerShell section appears first and includes instructions referencing Windows tools (Notepad) and patterns (PowerShell script execution). The Bash section is present and reasonably complete, but references to Bash environments (WSL) suggest a Windows-first mindset. There is a slight preference for Windows tools and workflows throughout.

• Alternate the order of PowerShell and Bash sections, or present Bash first to avoid implicit Windows prioritization.
• In Bash instructions, mention native Linux/macOS environments before WSL, e.g., 'Run the script using your terminal on Linux or macOS, or via WSL on Windows.'
• For text editors, recommend platform-appropriate editors (e.g., nano, gedit for Linux; TextEdit for macOS) alongside Notepad/VS Code.
• Clarify that both scripts are functionally equivalent and can be used on any platform with Azure CLI installed.
• Consider a unified section for prerequisites, noting cross-platform compatibility explicitly.

The documentation presents both PowerShell (Windows-centric) and Bash examples, but the PowerShell section appears first and is more detailed in its instructions (e.g., saving and running the script). Windows-specific tools (Notepad) are mentioned before cross-platform editors. The Bash section references running scripts via WSL, implicitly assuming a Windows host for Bash usage, and does not mention native Linux/macOS environments.

• Alternate the order of PowerShell and Bash sections, or present Bash first to avoid implicit Windows prioritization.
• Explicitly mention that Bash instructions apply to native Linux and macOS terminals, not just WSL.
• Include Linux/macOS-native text editors (e.g., nano, vim, gedit) in the 'Save the script' instructions for Bash.
• Avoid referencing Windows-specific tools (Notepad, Notepad++) before cross-platform or Linux/macOS alternatives.
• Clarify that Azure CLI works identically on Linux/macOS and provide links to installation instructions for those platforms.