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 1-25 of 32 flagged pages
Planetary Computer
Managing User Access in Microsoft Planetary Computer Pro
...blob/main/articles/planetary-computer/manage-access.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exclusively describes user and RBAC management using the Azure portal, which is a graphical tool most commonly used on Windows. There are no examples or instructions for performing these tasks via command-line interfaces such as Azure CLI, PowerShell, or Bash, nor is there mention of Linux-specific workflows or tools. The documentation implicitly assumes use of the Azure portal (often associated with Windows environments) and does not provide parity for Linux users who may prefer CLI or automation.
Recommendations
- Add equivalent instructions for managing RBAC roles using Azure CLI, with example commands that work on Linux and macOS.
- Include PowerShell examples as a secondary option, but ensure CLI/Bash examples are present and given equal prominence.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows environments using CLI tools.
- Provide links to cross-platform documentation for Azure CLI and REST API methods for RBAC management.
- Consider adding a section comparing portal-based and CLI-based workflows, highlighting cross-platform compatibility.
Create Pull Request
Planetary Computer
Managing User Access in Microsoft Planetary Computer Pro
...blob/main/articles/planetary-computer/manage-access.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure portal (a GUI tool most commonly used on Windows), omitting any command-line examples (such as Azure CLI or PowerShell for Windows, or Bash for Linux). No Linux-specific tools, patterns, or examples are provided. The workflow assumes use of the Azure portal, which is more familiar to Windows users, and does not mention cross-platform alternatives or parity.
Recommendations
- Add Azure CLI examples for assigning RBAC roles, which work on both Windows and Linux.
- Include PowerShell examples for Windows users and Bash examples for Linux users, ensuring parity.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, but also provide command-line alternatives.
- Reference Linux-friendly tools and workflows where appropriate, such as using Bash scripts for automation.
- Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid Windows-specific UI elements or terminology).
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/application-authentication.md
...icles/planetary-computer/application-authentication.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Azure portal (which is most commonly used on Windows), providing links and pivots for configuring managed identities specifically for Windows VMs, and omitting explicit Linux or cross-platform command-line examples (e.g., no Linux VM instructions, no Bash or shell script samples, no mention of Linux-specific tooling). The only CLI example given is generic and does not clarify platform compatibility. There is no mention of Linux desktop tools or workflows, and screenshots are all from the Azure portal UI, which is most familiar to Windows users.
Recommendations
- Add explicit instructions and examples for configuring managed identities on Linux VMs, including links to Linux-specific documentation and pivots.
- Provide CLI examples using Bash or shell scripts, and clarify that the az CLI works cross-platform.
- Include screenshots or walkthroughs for Linux environments (e.g., Azure portal accessed from Linux, or using SSH/CLI tools).
- Mention Linux desktop tools or workflows where relevant (e.g., using QGIS on Linux, authenticating from Linux containers).
- Where links reference Windows-specific pivots, also include or prioritize Linux pivots.
- State clearly that all authentication steps and tools (Azure CLI, Python SDK) are cross-platform, and highlight any platform-specific caveats.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/assign-managed-identity-geocatalog-resource.md
...omputer/assign-managed-identity-geocatalog-resource.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page presents both PowerShell (Windows) and Bash (Linux/macOS) examples for assigning a managed identity, but exhibits subtle Windows bias. The PowerShell tab and instructions are listed first, and Windows-centric tools (Notepad, Notepad++) are mentioned before Linux-native editors. Bash instructions reference running scripts via WSL, implicitly assuming a Windows environment for Bash users. There is no mention of Linux-specific editors (e.g., nano, vim) or native Linux terminal environments.
Recommendations
- Alternate the order of PowerShell and Bash tabs or present both equally to avoid implicit prioritization.
- Mention Linux-native text editors (e.g., nano, vim, gedit) alongside Notepad/VS Code for script editing.
- Clarify that Bash scripts can be run natively on Linux/macOS, not just via WSL on Windows.
- Include instructions for running Bash scripts in standard Linux/macOS terminals, not only WSL.
- Avoid assuming Windows as the default environment for Bash users.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/application-authentication.md
...icles/planetary-computer/application-authentication.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Azure portal and its GUI workflows (which are most familiar to Windows users), linking to instructions that default to Windows VM pivots, and omitting explicit Linux or cross-platform CLI examples for key authentication and RBAC steps. There are no PowerShell-heavy sections, but Linux-specific guidance and parity in examples are lacking.
Recommendations
- Provide explicit Linux examples for VM managed identity configuration, e.g., reference the Linux VM pivot in Azure docs and show CLI commands for Linux environments.
- Include cross-platform CLI (az CLI) workflows for RBAC assignment and managed identity setup, not just Azure portal screenshots.
- Mention and link to Linux and macOS documentation wherever VM/container setup is discussed, ensuring parity in instructions.
- Clarify that all CLI commands (e.g., az login --identity) work on Linux, macOS, and Windows, and provide sample shell commands for Linux.
- Add notes or sections for Linux administrators, especially for on-premises or non-Azure environments, to ensure inclusivity.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/build-applications-with-planetary-computer-pro.md
...uter/build-applications-with-planetary-computer-pro.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing ESRI ArcGIS Pro (a Windows-only GIS application) as the example for desktop GIS integration, without mentioning or providing guidance for Linux-compatible GIS tools such as QGIS. No Linux or cross-platform examples are provided for GIS connectivity, and the only desktop workflow described is Windows-centric. Additionally, the related content and integration sections prioritize Windows tools and do not address Linux alternatives.
Recommendations
- Include examples and instructions for integrating with popular cross-platform or Linux-native GIS applications such as QGIS.
- Provide sample workflows or connection guides for Linux users, ensuring parity with the ArcGIS Pro (Windows) guidance.
- Explicitly mention support for non-Windows environments in all relevant sections, especially in GIS connectivity.
- Add related content links for Linux and cross-platform tools, not just Windows-based applications.
- Where possible, use generic or cross-platform terminology and avoid assuming the use of Windows-only software.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/set-up-ingestion-credentials-sas-tokens.md
...ry-computer/set-up-ingestion-credentials-sas-tokens.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure portal (web UI) and Azure Storage Explorer (a GUI tool with a strong Windows association) for obtaining SAS tokens, without mentioning or providing examples for Linux-native or CLI-based workflows. The API example relies on Azure CLI authentication but does not clarify cross-platform compatibility or provide Linux-specific guidance. There are no command-line examples (e.g., using az CLI or Bash scripts) for Linux users, and no mention of Linux tools or patterns.
Recommendations
- Add explicit examples for obtaining SAS tokens using the Azure CLI (az storage container generate-sas) with command-line instructions suitable for Linux/macOS environments.
- Clarify that Azure CLI and the Python SDK are cross-platform, and provide any necessary setup steps for Linux users (e.g., package installation, authentication).
- Mention and provide examples for using Bash or shell scripting to automate SAS token generation and ingestion source creation.
- If referencing Azure Storage Explorer, note its cross-platform availability and provide installation instructions for Linux.
- Ensure screenshots and UI instructions are supplemented with equivalent CLI or code-based workflows for users who do not use Windows or GUIs.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/api-tutorial.md
.../blob/main/articles/planetary-computer/api-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by recommending Windows-centric tools and environments (Azure Machine Learning VM, Visual Studio Code) as primary options, and by relying on the Azure CLI for authentication without mentioning cross-platform or Linux-specific alternatives. There are no explicit Linux or macOS setup instructions, and no mention of Linux-native authentication methods or terminal usage, despite the tutorial being Jupyter/Python-based and thus inherently cross-platform.
Recommendations
- Explicitly mention that the tutorial works on Linux and macOS, not just Windows.
- Provide example instructions for installing and using Azure CLI on Linux and macOS.
- Include alternative authentication options (such as Azure Identity's DefaultAzureCredential, device code login, or environment variables) that work well on all platforms.
- Suggest Linux-friendly environments (e.g., JupyterLab on Ubuntu, Anaconda, or cloud-based Jupyter services) alongside Windows tools.
- Clarify that Visual Studio Code and Jupyter Notebooks are available on Linux and macOS, and provide links or setup steps for those platforms.
- Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, package installation).
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/application-authentication.md
...icles/planetary-computer/application-authentication.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific Azure portal pivots (e.g., 'qs-configure-portal-windows-vm'), providing screenshots and instructions only for the Azure portal (which is platform-agnostic but often assumes a Windows workflow), and omitting explicit Linux or cross-platform command-line examples (e.g., no Bash or Linux-specific CLI instructions). There are no PowerShell examples, but the absence of Linux/Unix-specific guidance or parity in examples and links constitutes a subtle bias.
Recommendations
- Include explicit Linux/Unix command-line examples (e.g., Bash scripts for az CLI usage, environment variable configuration).
- When linking to Azure documentation, use platform-neutral or include both Windows and Linux pivots (e.g., provide links for configuring managed identities on both Windows and Linux VMs).
- Add screenshots or instructions for using the Azure CLI and/or REST API, which are cross-platform, alongside Azure portal steps.
- Clarify that all CLI commands (such as 'az login') work on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
- Where environment variables are referenced, show both Windows (set) and Linux (export) syntax.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/assign-managed-identity-geocatalog-resource.md
...omputer/assign-managed-identity-geocatalog-resource.md
High 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 section is listed first and is more detailed in its instructions. The script-saving instructions reference Notepad (a Windows tool) before Notepad++ (which, while cross-platform, is more common on Windows), and VS Code (cross-platform) is mentioned in both. The Bash section also suggests running the script via WSL, which is a Windows-specific Linux environment, rather than mentioning native Linux or macOS terminals. There is a subtle prioritization of Windows tools and workflows.
Recommendations
- Alternate the order of PowerShell and Bash sections or default to Bash first to avoid implicit Windows prioritization.
- In script-saving instructions, mention cross-platform editors (e.g., VS Code, nano, vim) before or alongside Windows-specific editors like Notepad.
- In the Bash section, recommend running the script in any Bash environment (Linux, macOS, or WSL) rather than only mentioning WSL.
- Ensure parity in the level of detail and troubleshooting tips between PowerShell and Bash sections.
- Explicitly state that both Windows and Linux/macOS users are supported equally, and provide links to Bash setup instructions for non-Windows platforms if needed.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/set-up-ingestion-credentials-sas-tokens.md
...ry-computer/set-up-ingestion-credentials-sas-tokens.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure portal (a web UI, but often associated with Windows-centric workflows), and Azure Storage Explorer (which, while cross-platform, is often positioned as a Windows tool). The API example relies on Azure CLI authentication (AzureCliCredential), which is available on Linux but is most commonly used and documented in Windows environments. There are no explicit Linux shell (bash) or cross-platform CLI examples, nor are there instructions for obtaining SAS tokens using Linux-native tools or workflows. No PowerShell-specific code is present, but the absence of Linux-specific guidance or parity is notable.
Recommendations
- Add explicit Linux shell (bash) examples for obtaining SAS tokens, such as using the Azure CLI (az storage container generate-sas) with bash commands.
- Clarify that Azure CLI and Azure Storage Explorer are cross-platform, and provide installation and usage instructions for Linux.
- Include a section or callout for Linux/macOS users, highlighting any differences or prerequisites.
- Provide CLI-based alternatives to UI steps, especially for headless or server environments.
- Ensure screenshots and instructions are not Windows-centric (e.g., avoid showing only Windows UI elements if possible).
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/build-applications-with-planetary-computer-pro.md
...uter/build-applications-with-planetary-computer-pro.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing ESRI ArcGIS Pro—a Windows-only GIS application—as the example for desktop GIS integration. There are no examples or mentions of Linux-compatible GIS tools (such as QGIS), nor are there any Linux-specific instructions or parity in tooling. The only detailed workflow for connecting to desktop GIS is for a Windows application, and no Linux alternatives are discussed or even acknowledged.
Recommendations
- Add examples and instructions for integrating Planetary Computer Pro with cross-platform or Linux-native GIS applications, such as QGIS.
- Include sample workflows or connection guides for Linux users, ensuring parity with the ArcGIS Pro (Windows) example.
- When listing supported GIS tools, mention both Windows and Linux-compatible options, and avoid presenting Windows tools exclusively or first.
- If possible, provide code snippets or configuration steps that are platform-agnostic or explicitly show both Windows and Linux variants.
- Acknowledge the diversity of development environments (Windows, Linux, macOS) in the documentation introduction and throughout relevant sections.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/create-connection-arc-gis-pro.md
...es/planetary-computer/create-connection-arc-gis-pro.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on ArcGIS Pro, a Windows-only desktop application, and all configuration steps, screenshots, and tool references are specific to the Windows environment. There are no examples or guidance for Linux users, nor are any cross-platform or command-line alternatives provided. The workflow assumes the use of Windows GUI tools and does not mention Linux-compatible GIS tools or methods.
Recommendations
- Provide equivalent instructions for Linux users, such as using ArcGIS Pro alternatives (e.g., QGIS) or command-line tools (e.g., GDAL, ogr2ogr) to access Microsoft Planetary Computer Pro GeoCatalog data.
- Include examples of how to authenticate and connect to the GeoCatalog using open-source, cross-platform tools and libraries (e.g., Python scripts with pystac-client, requests, or Azure SDKs).
- Add a section or callout that explicitly states the platform limitations of ArcGIS Pro and suggests Linux-compatible workflows for similar tasks.
- Where possible, provide CLI-based instructions (e.g., using az CLI, curl, or Python) for authentication and data access, which can be run on any OS.
- Mention and link to documentation for Linux-friendly GIS tools and how they can be configured to access the same data sources.
Planetary Computer
Managing User Access in Microsoft Planetary Computer Pro
...blob/main/articles/planetary-computer/manage-access.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively describes user and RBAC management through the Azure portal, a GUI tool most commonly used on Windows. There are no CLI, PowerShell, Bash, or cross-platform command examples provided, nor are Linux/macOS-specific workflows mentioned. The screenshots and step-by-step instructions assume use of the Azure portal, which is typically accessed from Windows environments and may not be optimal for Linux users. No mention is made of Azure CLI, REST API, or automation options that are platform-neutral.
Recommendations
- Add instructions for managing RBAC roles using Azure CLI, which is cross-platform and works on Linux/macOS.
- Include examples for using REST API or ARM templates for role assignment, enabling automation and parity for non-Windows users.
- Explicitly mention that the Azure portal is web-based and can be accessed from any OS, but provide alternatives for users who prefer command-line or scriptable solutions.
- Provide links to Azure CLI and PowerShell documentation, and show equivalent steps for both where possible.
Planetary Computer
Managing User Access in Microsoft Planetary Computer Pro
...blob/main/articles/planetary-computer/manage-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes role assignment using the Azure portal GUI, which is most commonly accessed on Windows. There are no examples or instructions for performing RBAC assignments via CLI tools (such as Azure CLI or PowerShell), nor are Linux/macOS-specific workflows or screenshots provided. This creates friction for Linux/macOS users who may prefer or require command-line or cross-platform approaches.
Recommendations
- Add instructions and examples for assigning RBAC roles using Azure CLI, which is cross-platform and works on Linux/macOS.
- Include PowerShell examples only if accompanied by Bash/Azure CLI equivalents.
- Clarify that the Azure portal is web-based and accessible from any OS, but provide parity for users who prefer CLI or automation.
- Add notes or links to documentation for Linux/macOS users on installing and using Azure CLI.
Planetary Computer
Assign Managed Identity to GeoCatalog in Microsoft Planetary Computer Pro via the CLI
...omputer/assign-managed-identity-geocatalog-resource.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents both PowerShell (Windows) and Bash (Linux/macOS) examples for assigning a managed identity via Azure CLI, but Windows/PowerShell is listed first and receives slightly more detailed instructions (e.g., explicit mention of Notepad as a text editor, which is Windows-specific). The Bash instructions mention Notepad++ and VS Code, but also reference running scripts via WSL, implying a Windows context for Bash usage. There is a subtle preference for Windows tools and patterns in the ordering and examples.
Recommendations
- Alternate the order of PowerShell and Bash sections, or present them side-by-side to avoid implicit prioritization.
- Use cross-platform text editor examples (e.g., VS Code, nano, vim) and avoid Windows-specific editors like Notepad unless equally mentioning Linux/macOS equivalents.
- Clarify that Bash instructions can be run natively on Linux/macOS, not just via WSL on Windows.
- Add explicit notes about platform compatibility for each script, ensuring Linux/macOS users are addressed directly.
- Consider including a table or summary comparing the steps for both platforms to reinforce parity.
Planetary Computer
Application Authentication in Microsoft Planetary Computer Pro
...icles/planetary-computer/application-authentication.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure portal and managed identity configuration steps that are primarily oriented toward Windows environments. The links and examples for configuring managed identities on Azure VMs use the Windows portal pivot, and there are no explicit Linux or cross-platform CLI or shell examples for common authentication or RBAC tasks. The documentation does not provide PowerShell-heavy examples, but it does omit Linux-specific guidance and examples, such as using Azure CLI on Linux, configuring managed identities on Linux VMs, or using Linux-native tools for authentication.
Recommendations
- Add explicit examples for configuring managed identities and RBAC on Linux VMs, including Azure CLI commands and Linux portal pivots.
- Include Linux-specific instructions or screenshots where relevant, especially for steps that differ from Windows.
- Provide cross-platform CLI examples (bash, zsh) for authentication and token acquisition, not just Python or portal-based workflows.
- Reference documentation for Linux VM managed identity configuration alongside Windows VM links.
- Clarify that Azure CLI and SDKs work on Linux, macOS, and Windows, and provide parity in example commands.
Planetary Computer
Assign Managed Identity to GeoCatalog in Microsoft Planetary Computer Pro via the CLI
...omputer/assign-managed-identity-geocatalog-resource.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents both PowerShell (Windows-centric) and Bash examples for assigning a managed identity, but PowerShell is listed first and instructions reference Windows tools and editors (Notepad, VS Code, Notepad++) before Linux alternatives. The Bash instructions mention running the script via WSL, which is a Windows subsystem for Linux, rather than native Linux environments. There is a subtle prioritization of Windows workflows and tools.
Recommendations
- Alternate the order of PowerShell and Bash examples, or present them side-by-side to avoid implicit prioritization.
- Include references to native Linux text editors (e.g., nano, vim, gedit) alongside Notepad/VS Code/Notepad++.
- In Bash instructions, mention running scripts in native Linux environments (e.g., Ubuntu, CentOS) in addition to WSL.
- Clarify that both scripts can be run on MacOS and Linux, not just Windows.
- Add notes about installing Azure CLI on Linux and MacOS, if relevant.
Planetary Computer
Application Authentication in Microsoft Planetary Computer Pro
...icles/planetary-computer/application-authentication.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure portal workflows and screenshots, which are primarily Windows-centric, and by omitting explicit Linux or cross-platform command-line examples (e.g., PowerShell, Bash, or Linux-specific instructions). The only CLI example given is 'az login --identity', which is cross-platform, but there are no Linux-specific setup or troubleshooting notes, nor are Linux tools or patterns mentioned. The documentation also references Azure portal UI steps before any CLI or code-based alternatives, which are more common in Linux environments.
Recommendations
- Add explicit Linux/Bash command-line examples for authentication and RBAC configuration, such as using Azure CLI in Bash or shell scripts.
- Include instructions for configuring managed identities and service principals using cross-platform tools (e.g., Azure CLI, Terraform) with Linux-specific notes.
- Provide screenshots or walkthroughs for Linux environments (e.g., Ubuntu terminal) in addition to Azure portal UI.
- Mention and document troubleshooting steps or environment variable configuration for Linux systems.
- Clarify that all CLI commands (e.g., 'az login') work on Linux, macOS, and Windows, and provide platform-specific caveats if any.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/assign-managed-identity-geocatalog-resource.md
...omputer/assign-managed-identity-geocatalog-resource.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page presents both PowerShell (Windows-centric) and Bash (Linux/macOS-centric) examples for assigning a managed identity, but PowerShell is listed first and instructions for saving/running scripts reference Windows tools (Notepad, Notepad++), with Bash instructions suggesting WSL (Windows Subsystem for Linux) as the Bash environment. This ordering and tool selection subtly prioritize Windows workflows and environments.
Recommendations
- Alternate the order of PowerShell and Bash tabs or present Bash first to avoid implicit prioritization of Windows.
- In Bash instructions, recommend native Linux/macOS terminals and editors (e.g., nano, vim, gedit) alongside VS Code, rather than Notepad++ or WSL.
- Explicitly mention that Bash instructions apply to Linux and macOS environments, not just WSL.
- Provide guidance for running Bash scripts on native Linux/macOS systems, not just within Windows.
- Ensure parity in tool recommendations: suggest cross-platform editors (e.g., VS Code, Sublime Text) for both PowerShell and Bash.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/manage-access.md
...blob/main/articles/planetary-computer/manage-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by exclusively describing RBAC management through the Azure portal GUI, which is most commonly accessed via Windows environments. There are no examples or instructions for command-line management using cross-platform tools such as Azure CLI or Azure PowerShell, nor are there any Linux-specific workflows or screenshots. This omits guidance for users on Linux or those preferring automation and scripting.
Recommendations
- Add step-by-step instructions for assigning RBAC roles using the Azure CLI, which is cross-platform and widely used on Linux.
- Include examples for managing access via Azure PowerShell, noting its availability on Linux and macOS as well.
- Provide command-line snippets alongside GUI instructions to ensure parity for users on non-Windows platforms.
- Include screenshots or terminal output from Linux environments where relevant.
- Explicitly state that all management tasks can be performed from Linux, macOS, or Windows, and link to relevant cross-platform tool documentation.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/manage-access.md
...blob/main/articles/planetary-computer/manage-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively describing role assignment via the Azure Portal GUI, which is most commonly accessed from Windows environments. There are no command-line examples (such as Azure CLI or PowerShell), and no mention of Linux-native tools or workflows. This omission leaves out users who prefer or require Linux-based or cross-platform command-line management.
Recommendations
- Add Azure CLI examples for assigning RBAC roles, as the CLI is cross-platform and widely used on Linux.
- If relevant, include PowerShell examples, but ensure they are accompanied by Azure CLI equivalents.
- Explicitly mention that the Azure Portal can be accessed from any OS, including Linux and macOS, to avoid the impression of Windows exclusivity.
- Provide links to documentation for managing RBAC via command line, scripting, or automation, which are common in Linux environments.
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 for authentication. While Azure CLI is cross-platform, the documentation does not mention this, nor does it provide any guidance for Linux or macOS users. There are no explicit Windows-only commands, but the lack of platform-specific notes or alternative authentication methods (such as environment variables or managed identity) may implicitly favor users familiar with Windows or the Azure CLI, which is more commonly pre-installed or documented for Windows environments.
Recommendations
- Explicitly state that Azure CLI is cross-platform and provide installation instructions or a link for Linux/macOS users.
- Mention alternative authentication methods (e.g., DefaultAzureCredential, environment variables, managed identity) that work across platforms.
- Add a note clarifying that the Python code works on Windows, Linux, and macOS as long as the Azure CLI is installed and authenticated.
- Include troubleshooting tips for common Linux/macOS issues with Azure CLI authentication.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/manage-access.md
...blob/main/articles/planetary-computer/manage-access.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively describes managing user access via the Azure Portal GUI, with no mention of command-line tools or automation options. There are no examples for command-line interfaces such as Azure CLI, PowerShell, or Bash, nor any Linux-specific instructions. The overall approach assumes a graphical, point-and-click workflow, which is more common in Windows environments and less typical for Linux users who often prefer CLI-based management.
Recommendations
- Add step-by-step instructions for assigning RBAC roles using the Azure CLI (az role assignment), including example commands.
- If relevant, provide PowerShell examples, but ensure that Azure CLI (cross-platform) examples are presented first or alongside.
- Explicitly mention that all CLI instructions work on Linux, macOS, and Windows.
- Include a section comparing GUI and CLI approaches, highlighting the benefits of automation and scripting for Linux users.
- Link to official Azure CLI documentation for managing RBAC and user access.
Planetary Computer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/planetary-computer/bulk-ingestion-api.md
...main/articles/planetary-computer/bulk-ingestion-api.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation assumes the use of Azure CLI and AzureCliCredential for authentication, which are primarily Windows-centric tools and patterns. There are no explicit Linux or cross-platform command-line examples (e.g., Bash, Linux authentication alternatives), and no mention of Linux-specific considerations or parity. All code and instructions are platform-agnostic Python, but the authentication and tooling context is Azure CLI, which is more familiar to Windows/PowerShell users. No Linux-first or Linux-alternative authentication flows are described.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide installation instructions for Linux and macOS, not just a link to the Azure CLI docs.
- Include alternative authentication methods suitable for Linux environments, such as using environment variables with service principal credentials (AZURE_CLIENT_ID, AZURE_TENANT_ID, AZURE_CLIENT_SECRET) and show example code.
- Add a note or section on running the workflow in a Linux shell (Bash), including any differences in environment setup or permissions.
- Where possible, provide both Windows (PowerShell/CMD) and Linux (Bash) command-line snippets for prerequisite steps (e.g., installing Python, Azure CLI).
- Clarify that all Python code is cross-platform, but highlight any OS-specific caveats if they exist.