Planetary Computer
42
Total Pages
30
Linux-Friendly Pages
12
Pages with Bias
28.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
32 issues found
Showing 26-32 of 32 flagged pages
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/get-started-planetary-computer.md
...s/planetary-computer/get-started-planetary-computer.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows/Azure portal-first bias: all deployment and management instructions are given via the Azure web portal, with no mention of command-line alternatives (such as Azure CLI or Bicep), which are commonly used on Linux and cross-platform environments. There are no PowerShell-specific examples, but the lack of Linux/CLI parity is notable. No Linux tools, shell commands, or platform-agnostic automation methods are referenced, and the workflow assumes a GUI-first approach typical of Windows users.
Recommendations
- Add parallel instructions for deploying and managing GeoCatalog resources using Azure CLI and/or Bicep, including example commands.
- Include examples of interacting with the service via REST API using curl or similar cross-platform tools.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide links to CLI installation/setup guides.
- Where screenshots are shown of the Azure portal, consider also providing CLI output or code snippets to ensure parity.
- Highlight any platform-specific requirements or limitations, if any, and provide workarounds.
Create Pull Request
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/api-tutorial.md
.../blob/main/articles/planetary-computer/api-tutorial.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by recommending Azure Machine Learning Virtual Machine and Visual Studio Code (VS Code) as primary environments, both of which are commonly used on Windows. The only explicit CLI authentication example uses the Azure CLI, but there is no mention of Linux-specific environments, nor are there any examples or troubleshooting tips for Linux users. There are no PowerShell-specific commands, but the lack of Linux/macOS parity in environment setup and tool recommendations is notable.
Recommendations
- Explicitly mention that the tutorial is compatible with Linux and macOS environments, not just Windows.
- Provide example commands for setting up the environment on Linux (e.g., using apt or yum to install Azure CLI, Python, and pip).
- Include alternative recommendations for running Jupyter notebooks, such as JupyterLab or command-line Jupyter, which are cross-platform.
- Add troubleshooting notes for common Linux/macOS issues (e.g., Azure CLI authentication, file permissions).
- Clarify that Visual Studio Code is available on all platforms, and provide instructions for installing it on Linux/macOS.
- Consider including a table or section comparing setup steps for Windows, Linux, and macOS users.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/get-collection-sas-token.md
...rticles/planetary-computer/get-collection-sas-token.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation uses AzureCliCredential from the azure.identity Python library, which relies on the Azure CLI being authenticated. While Azure CLI is cross-platform, the documentation does not mention Linux or macOS compatibility, nor does it provide any guidance for Linux users. There are no explicit PowerShell or Windows-only commands, but the lack of Linux-specific notes or alternative authentication methods (such as environment variables or managed identity) may leave Linux users uncertain. The documentation implicitly assumes the user is familiar with Windows-centric tooling.
Recommendations
- Explicitly mention that Azure CLI and the example code are cross-platform and work on Linux, macOS, and Windows.
- Provide a note or section for Linux/macOS users, including any prerequisites or differences in Azure CLI installation or authentication.
- Offer alternative authentication methods (e.g., DefaultAzureCredential, environment variables, managed identity) that may be more common in Linux environments.
- Include troubleshooting tips for common issues encountered on Linux (e.g., Azure CLI not found, authentication issues).
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/deploy-geocatalog-resource.md
...icles/planetary-computer/deploy-geocatalog-resource.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by exclusively referencing the Azure portal (a web GUI) and Azure REST API via Azure Cloud Shell/Bash, but does not provide explicit Linux-native or cross-platform command-line examples outside of the Azure ecosystem. There are no references to PowerShell, but the instructions assume use of the Azure portal (which is platform-agnostic but often associated with Windows workflows) and Azure Cloud Shell (which is available on all platforms but not the same as a local Linux shell). There are no examples for deploying via local Linux shell, nor are there any mentions of Linux-specific tools or workflows.
Recommendations
- Add explicit instructions and examples for deploying a GeoCatalog resource using the Azure CLI from a local Linux shell, not just via Cloud Shell.
- Clarify that the Azure portal and Azure CLI are cross-platform, and provide guidance for both Windows and Linux users.
- If PowerShell is not required, explicitly state that Bash examples are suitable for Linux/macOS/WSL users.
- Include troubleshooting tips or prerequisites specific to Linux environments (e.g., installing Azure CLI on Ubuntu).
- Ensure screenshots and step-by-step instructions do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements or file paths).
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/set-up-ingestion-credentials-managed-identity.md
...puter/set-up-ingestion-credentials-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses the Azure Portal (a web-based GUI) for all configuration steps and does not provide any command-line examples. There are no references to cross-platform CLI tools (such as Azure CLI or Azure PowerShell), nor are there any Linux-specific instructions or examples. The absence of CLI instructions implicitly favors Windows users, as the Azure Portal experience is often more familiar or accessible to them, and omits parity for Linux users who may prefer or require command-line automation.
Recommendations
- Add equivalent Azure CLI commands for each step (creating managed identities, assigning roles, associating identities, configuring ingestion sources). The Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Where relevant, provide Azure PowerShell examples as an alternative, but always include Azure CLI as the primary or at least as a parallel option.
- Explicitly mention that all steps can be performed via CLI and provide links to relevant Azure CLI documentation.
- Include a section or callout for Linux/macOS users, highlighting that all operations can be performed from their platforms using the CLI.
- Ensure screenshots or instructions do not assume a Windows environment (e.g., avoid referencing Windows-specific file paths or UI conventions).
Planetary Computer
Assign Managed Identity to GeoCatalog in Microsoft Planetary Computer Pro via the CLI
...omputer/assign-managed-identity-geocatalog-resource.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents both PowerShell (Windows) and Bash (Linux/macOS) examples, but the PowerShell tab and instructions are shown first. The script saving instructions reference Notepad (Windows tool) before Notepad++ (Windows) and VS Code (cross-platform), and the Bash instructions mention running via WSL (Windows Subsystem for Linux) before other Bash environments, subtly prioritizing Windows workflows. There is no missing Linux example, but the ordering and tool references show a mild Windows bias.
Recommendations
- Present Bash and PowerShell tabs in alphabetical or neutral order, or randomize which is shown first.
- In script saving instructions, mention cross-platform editors (e.g., VS Code, Sublime Text) before Windows-specific ones.
- For Bash, recommend native Linux/macOS terminals first, then mention WSL as an option for Windows users.
- Ensure all instructions are equally detailed and platform-neutral where possible.
Planetary Computer
Assign Managed Identity to GeoCatalog in Microsoft Planetary Computer Pro via the CLI
...omputer/assign-managed-identity-geocatalog-resource.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents both PowerShell (Windows) and Bash (Linux/macOS) examples for assigning a managed identity, but the PowerShell tab and instructions are listed first. The script-saving instructions reference Notepad (Windows) before VS Code, and the Bash instructions mention Notepad++ (Windows) before VS Code. The Bash section suggests running scripts via WSL, which is a Windows-centric pattern, rather than directly referencing native Linux/macOS terminals. There is a slight preference for Windows tools and workflows throughout.
Recommendations
- Alternate the order of PowerShell and Bash tabs or present Bash first to avoid implicit prioritization of Windows.
- In script-saving instructions, mention cross-platform editors (e.g., VS Code, nano, vim) before Windows-specific editors like Notepad or Notepad++.
- In Bash instructions, recommend running scripts directly in native Linux/macOS terminals, not just via WSL.
- Add explicit notes that both scripts work on macOS and Linux, and clarify any platform-specific differences if present.
- Consider adding a table or section summarizing platform compatibility and prerequisites for each environment.