Energy Data Services
53
Total Pages
41
Linux-Friendly Pages
12
Pages with Bias
22.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
31 issues found
Showing 1-25 of 31 flagged pages
Energy Data Services
Tutorial: Use sdutil to load data into Seismic Store
...s/energy-data-services/tutorial-seismic-ddms-sdutil.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by listing Windows prerequisites and instructions before Linux and Mac equivalents, referencing Windows-specific tools (Microsoft C++ Build Tools, WSL), and using Windows-centric terminology and patterns (e.g., 'activate' command path, 'apt-get' for WSL). Some installation and configuration steps are more detailed for Windows, and Linux/Mac instructions are less prominent or missing in places. There is also a lack of explicit Linux or Mac command-line examples in some sections, and the use of PowerShell/Windows paths is prioritized.
Recommendations
- Present Linux and Mac instructions before or alongside Windows instructions, not after.
- Provide equivalent Linux/Mac commands for all steps, especially for environment setup and activation.
- Avoid referencing Windows-specific tools (e.g., Microsoft C++ Build Tools, WSL) without mentioning Linux/Mac alternatives in equal detail.
- Include Linux/Mac-specific troubleshooting notes and examples where Windows notes are given.
- Ensure all code examples use platform-agnostic paths and commands, or provide platform-specific variants.
- Clarify when commands or steps differ between platforms, and provide explicit instructions for each.
Create Pull Request
Energy Data Services
Tutorial: Use sdutil to load data into Seismic Store
...s/energy-data-services/tutorial-seismic-ddms-sdutil.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by listing Windows prerequisites and instructions before Linux and Mac equivalents, referencing Windows-specific tools (Microsoft C++ Build Tools, WSL), and providing more detailed instructions for Windows environments. Some commands and environment setup steps are described with Windows paths or terminology first, and there is limited coverage of Linux-specific package managers and shell environments. There are also places where Linux/Mac instructions are less detailed or missing, such as virtual environment activation and package installation nuances.
Recommendations
- Present Linux, Mac, and Windows instructions in parallel, or start with a neutral/OS-agnostic approach.
- Provide equal detail for Linux/Mac prerequisites, including common package managers (apt, yum, homebrew) and C++ build tool installation.
- Include explicit Linux/Mac command examples for all steps, such as activating virtual environments and installing dependencies.
- Avoid referencing Windows Subsystem for Linux (WSL) as the default Linux environment for Windows users; instead, treat native Linux and WSL as separate cases.
- Where possible, use generic shell commands and avoid Windows path conventions unless specifically needed.
- Add troubleshooting and FAQ sections for Linux/Mac users, similar to those provided for Windows.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/tutorial-seismic-ddms-sdutil.md
...s/energy-data-services/tutorial-seismic-ddms-sdutil.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias by listing Windows prerequisites and instructions before Linux and Mac equivalents, referencing Windows-specific tools (Microsoft C++ Build Tools, WSL), and providing more detailed setup instructions for Windows environments. Some commands and environment variable instructions are tailored to Windows (e.g., activation path), and Linux/Mac alternatives are mentioned only as secondary options. There is also a lack of Linux-specific troubleshooting and examples, and some instructions (such as package manager usage) are ambiguous or less detailed for Linux/Mac users.
Recommendations
- Present prerequisites and setup instructions for Linux, Mac, and Windows in parallel, rather than listing Windows first.
- Provide equally detailed examples and troubleshooting steps for Linux and Mac environments.
- Avoid referencing Windows-specific tools (e.g., Microsoft C++ Build Tools, WSL) without offering clear Linux/Mac alternatives.
- Ensure all command-line examples use cross-platform syntax, or provide separate commands for each OS where necessary.
- Clarify package manager instructions for Linux and Mac (e.g., apt-get vs. homebrew) and avoid suggesting manual installation of apt-get on Mac.
- Include Linux/Mac-specific notes for environment variable setup, file paths, and permissions.
- Add explicit Linux/Mac examples for common tasks, such as activating virtual environments and running the tool.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/tutorial-seismic-ddms-sdutil.md
...s/energy-data-services/tutorial-seismic-ddms-sdutil.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a Windows bias by listing Windows prerequisites first, referencing Windows-specific tools (Microsoft C++ Build Tools, WSL), and providing activation commands and package manager instructions for Windows before Linux. Some instructions (such as virtual environment activation) are shown for Windows first, and Linux alternatives are mentioned secondarily or as notes. There is also reliance on Windows-centric terminology and tools, with less detailed guidance for Linux users. Examples and usage instructions are mostly generic, but the initial setup and environment configuration favor Windows.
Recommendations
- Present Linux and Windows instructions in parallel, or start with Linux to balance the order.
- Provide equally detailed setup instructions for Linux, including C++ build tools and package manager commands.
- Avoid referencing Windows Subsystem for Linux (WSL) as a primary Linux environment; treat native Linux equally.
- Ensure all example commands (such as activating virtual environments) are shown for both platforms, not just Windows first.
- Include troubleshooting notes and tips for Linux users, similar to those provided for Windows.
- Reference cross-platform tools and patterns before platform-specific ones.
- Add explicit Linux usage examples where only Windows or generic examples are given.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/overview-microsoft-energy-data-services.md
...ta-services/overview-microsoft-energy-data-services.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias towards Microsoft and Windows-centric tools and workflows. It exclusively mentions Microsoft products (SharePoint, Synapse, Power BI, Entra ID) for integration and extensibility, with no mention of Linux-based tools, open-source alternatives, or cross-platform command-line examples. The documentation assumes the use of the Microsoft ecosystem, which is more common on Windows, and does not provide parity for Linux users.
Recommendations
- Include examples and references to cross-platform or Linux-native tools for data ingestion, transformation, and visualization (e.g., Apache NiFi, Jupyter, Grafana).
- Mention compatibility with open-source identity providers or authentication mechanisms commonly used on Linux.
- Provide command-line examples for both Windows (PowerShell) and Linux (Bash) in future quickstart or how-to guides.
- Highlight integration possibilities with non-Microsoft applications and services to demonstrate platform openness.
- Clarify whether the platform supports Linux-based workflows and tools, and provide documentation or links for Linux users.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/tutorial-seismic-ddms-sdutil.md
...s/energy-data-services/tutorial-seismic-ddms-sdutil.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by listing Windows prerequisites and tools first, referencing Windows-specific tools (e.g., Microsoft C++ Build Tools, WSL), and providing activation commands for Windows before Linux. Some instructions and notes are tailored to Windows or WSL users, and there is a lack of parity in detailed Linux/Mac-specific guidance, especially regarding package management and environment setup.
Recommendations
- List Linux and Mac prerequisites before or alongside Windows, not after.
- Provide Linux and Mac equivalents for all Windows-specific tools and commands (e.g., recommend GCC or Clang for C++ build tools on Linux, and clarify how to install dependencies using native package managers).
- Avoid referencing WSL as the primary Linux environment for Windows users; instead, treat native Linux and WSL as separate, equally valid platforms.
- Ensure all command examples (such as activating virtual environments) are shown for all platforms, and not just Windows first.
- Expand on Linux/Mac installation steps, including common package manager commands (apt, yum, brew) and troubleshooting tips.
- Where possible, use cross-platform commands and avoid Windows-centric paths or syntax.
- Add explicit sections or callouts for Linux/Mac users wherever there are differences in workflow or tooling.
Energy Data Services
Tutorial: Use sdutil to load data into Seismic Store
...s/energy-data-services/tutorial-seismic-ddms-sdutil.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows is consistently listed first in prerequisites and activation instructions, and Windows-specific tools (such as Microsoft C++ Build Tools and WSL) are mentioned. Some commands and installation steps are tailored for Windows or WSL, with less detail or clarity for native Linux/macOS users. Powershell/Windows command syntax is shown before or instead of Linux equivalents in some places. There are also references to using 'apt-get' on Mac via Homebrew or manual installation, which may confuse non-Windows users.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, not after.
- Provide explicit, native Linux and macOS installation and activation commands, not just for WSL.
- Avoid suggesting Windows Subsystem for Linux (WSL) as the primary Linux experience; treat native Linux equally.
- List Linux/macOS prerequisites and tools with the same level of detail as Windows (e.g., mention build-essential for Linux).
- Where commands differ, show both Windows and Linux/macOS versions side by side.
- Clarify package manager instructions for macOS (e.g., use 'brew' for Homebrew, not 'apt-get').
- Add troubleshooting notes specific to Linux/macOS environments.
Energy Data Services
Tutorial: Use sdutil to load data into Seismic Store
...s/energy-data-services/tutorial-seismic-ddms-sdutil.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows prerequisites and instructions are listed first, with explicit references to Windows-specific tools (e.g., Microsoft C++ Build Tools, WSL). Some installation and activation commands are Windows-centric or provide more detail for Windows users. Linux and macOS instructions are present but less detailed, and some examples (such as activating virtual environments) are more explicit for Windows. There is also a suggestion to use WSL for Windows users, which may confuse the distinction between native Linux and Windows environments.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, rather than always listing Windows first.
- Provide equally detailed installation steps for Linux and macOS (e.g., mention required build tools for Linux, not just for macOS).
- Avoid suggesting WSL as a Linux environment for Windows users unless necessary, and clarify when native Linux instructions apply.
- For virtual environment activation, provide the exact command for all platforms (e.g., 'source sdutilenv/bin/activate' for Linux/macOS, 'sdutilenv/Scripts/activate' for Windows) in a clear, parallel format.
- Ensure all code examples use platform-agnostic syntax where possible, or provide both Windows and Linux/macOS variants.
- Include troubleshooting and FAQ sections relevant to Linux/macOS users, not just Windows.
Energy Data Services
Deploy Geospatial Consumption Zone on top of Azure Data Manager for Energy using Azure portal
...includes/how-to/how-to-deploy-gcz/deploy-gcz-on-aks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Unix Shell and Windows PowerShell examples for variable definition and file creation, ensuring cross-platform coverage. However, Windows PowerShell examples are given equal prominence and detail as Unix Shell, and in some cases, PowerShell-specific file creation methods (Out-File) are used. The documentation does not show a clear preference for Windows, but the inclusion of PowerShell examples throughout may be interpreted as a slight Windows bias, especially since the Unix Shell examples use more standard cross-platform tools (cat, nano), while PowerShell examples use Windows-specific idioms.
Recommendations
- Ensure that all command examples are tested and work on both Linux/macOS and Windows environments.
- Consider adding explicit notes about cross-platform compatibility, especially for file creation and editing commands (e.g., recommend VS Code or Notepad++ for Windows users who may not have nano).
- Where possible, use commands and tools that are available on both platforms (e.g., suggest using VS Code or other cross-platform editors instead of nano for file editing).
- Clarify that Azure Cloud Shell supports both Bash and PowerShell, and users can choose their preferred shell.
- If possible, provide a single set of commands that work in both environments, or highlight differences only where necessary.
Energy Data Services
Tutorial: Use Reservoir DDMS websocket endpoints to work with reservoir data
...rgy-data-services/tutorial-reservoir-ddms-websocket.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation introduces the tutorial by stating that the APIs are used 'in PowerShell', which suggests a Windows-centric approach and may imply that PowerShell is required. However, all subsequent command examples use Bash syntax and Docker, which are cross-platform. There are no explicit Linux examples or mentions of Linux-specific tools or patterns, and the initial framing may discourage Linux users.
Recommendations
- Remove or rephrase the introductory statement to avoid implying PowerShell is required. For example, say 'Use Reservoir Domain Data Management Services (DDMS) APIs from your command line' instead of 'in PowerShell'.
- Explicitly state that the tutorial works on both Windows (with WSL or native Docker) and Linux/macOS environments.
- Add a note clarifying that the Bash commands are compatible with Linux, macOS, and Windows (with WSL, Git Bash, or similar).
- If PowerShell usage is intended, provide equivalent Linux shell examples or clarify cross-platform usage.
- Consider including a section or appendix with Linux-specific troubleshooting or environment setup tips.
Energy Data Services
Deploy Geospatial Consumption Zone on top of Azure Data Manager for Energy using Azure portal
...includes/how-to/how-to-deploy-gcz/deploy-gcz-on-aks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Unix Shell and Windows PowerShell examples for variable definition and file creation, ensuring both platforms are covered. However, Windows PowerShell examples are given equal prominence and detail as Unix Shell, and in some cases, the PowerShell examples are slightly more elaborate (e.g., use of Out-File for YAML creation). The documentation does not show exclusive Windows bias, but the structure (side-by-side tabs) and the explicit PowerShell scripting for file generation may be more familiar to Windows users. There is no evidence of missing Linux examples or exclusive mention of Windows tools, but the order of presentation sometimes puts Windows first (e.g., in the prerequisites, Azure Cloud Shell is mentioned before Azure CLI, but both are cross-platform).
Recommendations
- Ensure that all examples are equally detailed and tested on both platforms.
- Consider providing a brief note on how to use the scripts in WSL (Windows Subsystem for Linux) or Git Bash for Windows users who prefer Unix Shell.
- Where possible, use platform-neutral commands (e.g., Azure CLI, kubectl, helm) and minimize reliance on platform-specific scripting for file generation.
- Explicitly state that both Unix Shell and PowerShell examples are equivalent and users can choose based on their environment.
- If possible, provide a downloadable sample configuration file to avoid scripting differences.
Energy Data Services
Tutorial: Use Reservoir DDMS websocket endpoints to work with reservoir data
...rgy-data-services/tutorial-reservoir-ddms-websocket.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation introduces the tutorial as using Reservoir DDMS APIs in PowerShell, suggesting a Windows-centric approach. While the actual commands are Bash/Docker-based and cross-platform, the initial framing and variable syntax ($VAR) are more familiar to Windows/PowerShell users. There are no explicit Linux examples or mentions of Linux-specific patterns, and the documentation does not clarify cross-platform compatibility or provide Linux shell alternatives.
Recommendations
- Clarify that the tutorial works on both Windows and Linux, and provide explicit instructions for each platform if differences exist.
- Replace or supplement PowerShell variable syntax ($VAR) with POSIX shell syntax (e.g., VAR=value) for Linux users, or explain both.
- Avoid framing the tutorial as PowerShell-centric unless truly required; use neutral language such as 'command line' or 'terminal'.
- Add a note or section on platform compatibility, including any prerequisites or differences for Linux and macOS users.
- If any steps require Windows-specific tools, provide Linux alternatives or mention cross-platform equivalents.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/includes/how-to/how-to-deploy-gcz/deploy-gcz-on-aks.md
...includes/how-to/how-to-deploy-gcz/deploy-gcz-on-aks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Unix Shell and Windows PowerShell examples for all relevant steps, ensuring parity in instructions. However, the PowerShell examples are given equal prominence and detail as the Unix Shell examples, which can be interpreted as 'powershell_heavy' bias. Additionally, the documentation lists the Windows PowerShell tab before the Unix Shell tab in some sections, indicating a 'windows_first' bias. There are no missing Linux examples, and no exclusive mention of Windows-only tools or patterns.
Recommendations
- Ensure that Unix Shell (Linux/macOS) examples are listed before Windows PowerShell examples, as Linux is the primary OS for most cloud-native and Kubernetes operations.
- Explicitly mention that all steps are applicable to Linux/macOS environments and clarify any OS-specific differences, especially for file creation and text editing commands.
- Consider providing additional context or troubleshooting tips for Linux users, such as alternatives to 'nano' (e.g., 'vim', 'gedit') and handling file permissions.
- Review tab ordering and default tab selection to prioritize Linux/macOS instructions, reflecting the most common deployment environments for AKS and Helm.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/tutorial-reservoir-ddms-websocket.md
...rgy-data-services/tutorial-reservoir-ddms-websocket.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation introduces the tutorial as using Reservoir DDMS APIs in PowerShell, which is a Windows-centric shell. All variable assignment examples use PowerShell syntax (e.g., $VAR='value'), and the introductory text frames the workflow in terms of PowerShell usage. There are no Linux shell (bash) equivalents for variable assignment, nor is there any mention of Linux-specific patterns or tools, despite the rest of the workflow using Docker commands that are cross-platform.
Recommendations
- Provide Linux/bash equivalents for variable assignment (e.g., export VAR='value') alongside PowerShell examples.
- Clarify that the Docker commands work on both Windows and Linux, and offer any platform-specific notes if needed.
- Avoid framing the tutorial as PowerShell-only; instead, present it as cross-platform and show both PowerShell and bash syntax where relevant.
- Explicitly mention that users can use their preferred shell (PowerShell, bash, etc.) and provide guidance for both environments.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/tutorial-reservoir-ddms-websocket.md
...rgy-data-services/tutorial-reservoir-ddms-websocket.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation introduces the tutorial as using Reservoir DDMS APIs in PowerShell, suggesting a Windows-centric approach. Variable assignment examples use PowerShell syntax (e.g., $VAR='value'), which is not standard on Linux/macOS shells. There are no Linux shell (bash) equivalents for variable assignment, and PowerShell is mentioned before any cross-platform alternatives. However, the main workflow uses Docker commands, which are cross-platform.
Recommendations
- Replace PowerShell variable assignment examples with bash syntax (e.g., VAR='value') or provide both PowerShell and bash examples.
- Clarify that the tutorial is cross-platform and works on Linux/macOS as well as Windows.
- If PowerShell is required, explain how to run PowerShell on Linux/macOS, or provide bash alternatives.
- Avoid mentioning PowerShell exclusively in the introduction; use more neutral language like 'command line' or 'terminal'.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/includes/how-to/how-to-deploy-gcz/deploy-gcz-on-aks.md
...includes/how-to/how-to-deploy-gcz/deploy-gcz-on-aks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Unix Shell and Windows PowerShell examples for all variable definitions and file creation steps. However, Windows PowerShell examples are given equal prominence and detail as Unix Shell, rather than being secondary or referenced as alternatives. The structure (tabbed sections for both shells) is balanced, but the use of PowerShell-specific constructs (e.g., Out-File, heredoc syntax) and explicit PowerShell tabs throughout indicates a strong focus on Windows parity, possibly at the expense of Linux-first conventions. There is no evidence of missing Linux examples, but the documentation does not prioritize Linux or Unix shell usage, which is more common in cloud-native and Kubernetes environments.
Recommendations
- Consider making Unix Shell examples the default or primary example, with PowerShell as a secondary tab or alternative, reflecting the prevalence of Linux in cloud-native deployments.
- Add a short note explaining which example to use based on the user's operating system, and recommend Unix Shell for most Kubernetes/Azure CLI workflows.
- Where possible, use cross-platform commands and avoid PowerShell-specific constructs unless strictly necessary.
- Highlight any differences or limitations when using PowerShell versus Unix Shell, especially for file manipulation and environment variable handling.
- Ensure that all steps (including file editing and command-line operations) are equally clear for Linux users, and avoid implying that Windows is the default platform.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/how-to-integrate-osdu-service-logs-with-azure-monitor.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/how-to-integrate-osdu-service-logs-with-azure-monitor.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes integration and log analysis using Azure Portal UI and Azure-native tools (Log Analytics Workspace, KQL), with no mention of command-line or scripting options for Linux users (such as Azure CLI, Bash, or REST API). There are no PowerShell or Windows-specific commands, but the absence of Linux-friendly examples or cross-platform CLI instructions creates an implicit bias toward Windows/GUI workflows.
Recommendations
- Add Azure CLI examples for enabling diagnostic settings and querying logs, which work cross-platform (Windows, Linux, macOS).
- Include sample Bash scripts or REST API calls for automating log export and analysis.
- Mention that all Azure Portal features are accessible from any OS with a browser, but provide parity for users who prefer or require CLI/scripted workflows.
- If screenshots are used, consider including at least one from a Linux environment or clarify that the UI is OS-agnostic.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/how-to-deploy-gcz.md
...ain/articles/energy-data-services/how-to-deploy-gcz.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation presents deployment options for AKS (Azure Kubernetes Service) and Windows, but does not mention or provide instructions for deploying the GCZ service on Linux (outside of AKS). The 'Windows' deployment option is specifically called out for development/testing, but there is no equivalent guidance for Linux environments, which are common for development and testing. This creates a Windows-first impression and omits Linux parity.
Recommendations
- Add a section or pivot for deploying the GCZ service on Linux (e.g., Ubuntu) for development and testing, similar to the Windows option.
- If the service can run on Linux, provide step-by-step instructions or reference scripts for Linux-based deployment.
- Ensure that any scripts, commands, or tooling mentioned for Windows (such as PowerShell or Windows-specific paths) have Linux equivalents (e.g., Bash scripts, Linux file paths).
- Explicitly mention Linux as a supported platform for development/testing if applicable, or clarify if there are technical limitations.
- Review included files (e.g., deploy-gcz-on-windows.md) to ensure Linux users are not excluded from development/test scenarios.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/how-to-convert-segy-to-zgy.md
...les/energy-data-services/how-to-convert-segy-to-zgy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias by focusing exclusively on Postman (a GUI tool most commonly used on Windows) for API interactions, and by not providing explicit Linux command-line examples for key steps such as file uploads or API calls. While the use of bash scripts and Python-based sdutil suggests some cross-platform intent, there are no Linux-specific instructions or examples, and the initial setup and workflow are described primarily through GUI-based tools rather than CLI alternatives that are more common in Linux environments.
Recommendations
- Provide explicit Linux command-line examples for all API interactions, especially for uploading files and making API calls (e.g., using curl or httpie).
- Include instructions for installing and using Postman on Linux, or suggest alternative CLI tools for Linux users.
- When referencing scripts (such as prepare-records.sh), clarify any OS-specific dependencies or steps, and provide troubleshooting tips for Linux environments.
- Ensure that all steps that can be performed via CLI (such as sdutil commands or curl requests) are documented with equivalent Linux shell commands and not just GUI screenshots.
- Add a section or callouts highlighting any differences or considerations for Linux users, such as file path conventions or required dependencies.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/how-to-manage-data-security-and-encryption.md
...services/how-to-manage-data-security-and-encryption.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a bias towards Windows by exclusively referencing the Azure Portal (a web GUI) and not providing any command-line examples. There are no examples using cross-platform tools such as Azure CLI, Azure PowerShell, or REST APIs, which are commonly used on Linux and macOS. The documentation implicitly assumes a GUI/Windows-centric workflow, omitting Linux-friendly automation or scripting options.
Recommendations
- Add step-by-step instructions using Azure CLI for all key management and configuration tasks, as Azure CLI is cross-platform and widely used on Linux.
- Include PowerShell examples as an alternative, but ensure CLI examples are presented first or alongside PowerShell to avoid Windows-first bias.
- Provide REST API examples for advanced users who may want to automate these tasks from any OS.
- Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and provide links to relevant CLI or API documentation.
- Where screenshots are used, consider including terminal output or code snippets to complement GUI steps.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/how-to-convert-segy-to-ovds.md
...es/energy-data-services/how-to-convert-segy-to-ovds.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias towards Windows environments by focusing exclusively on GUI tools (Postman desktop app) and Python-based utilities (sdutil) without providing explicit Linux command-line examples or mentioning Linux-native tools. The instructions assume the use of desktop applications and do not address Linux-specific installation or usage considerations. There is no mention of Linux package managers, shell commands, or alternative workflows that are common in Linux environments.
Recommendations
- Provide explicit Linux command-line examples for each step, such as using curl or wget for API calls and file uploads.
- Include instructions for installing and running Postman and sdutil on Linux, including any dependencies or package manager commands (e.g., apt, yum, snap).
- Mention and demonstrate how to use native Linux tools (e.g., curl, jq) as alternatives to Postman for API interactions.
- Clarify that sdutil and Postman are cross-platform, and provide troubleshooting tips for Linux users (e.g., permissions, environment variables).
- Add a section or callouts for Linux users, highlighting any differences or additional steps required on Linux systems.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/how-to-deploy-gcz.md
...ain/articles/energy-data-services/how-to-deploy-gcz.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides deployment instructions for Azure Kubernetes Service (AKS) and Windows, but does not mention or provide instructions for deploying the GCZ service on Linux (outside of AKS). The 'Windows' deployment option is presented as the only non-AKS alternative, with no equivalent Linux instructions for development or testing environments. This creates a Windows-first impression and omits Linux users who may wish to deploy locally or outside Kubernetes.
Recommendations
- Add a section or pivot for deploying the GCZ service on Linux (e.g., Ubuntu), including step-by-step instructions or a link to a Linux deployment guide.
- Wherever a 'Windows' deployment is mentioned, also mention 'Linux' as a supported platform if possible, or clarify platform limitations.
- If there are scripts or tools provided for Windows (e.g., PowerShell), provide equivalent Bash or shell scripts for Linux users.
- Explicitly state platform support and any limitations for each deployment option to help users on all major operating systems.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/how-to-convert-segy-to-zgy.md
...les/energy-data-services/how-to-convert-segy-to-zgy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (Postman desktop app) and providing screenshots and instructions that assume a Windows environment. There are no explicit Linux-specific instructions, examples, or screenshots, and setup steps for tools like Postman and sdutil do not address Linux installation or usage. The documentation does not mention or show parity for Linux users, such as using Postman on Linux, or provide Linux command-line alternatives or troubleshooting.
Recommendations
- Include explicit instructions and screenshots for installing and using Postman on Linux, or clarify that Postman is cross-platform.
- Provide Linux-specific setup notes for sdutil, including installation steps and any OS-specific dependencies.
- When referencing tools, avoid language that implies Windows is the default (e.g., 'Download and install the Postman desktop app' could be 'Download and install the Postman desktop app for your OS').
- Add troubleshooting tips or notes for common Linux issues (e.g., permissions, Python environment setup for sdutil).
- Where screenshots are shown, consider including at least one from a Linux environment or clarify that the UI is the same across platforms.
- Explicitly state that all command-line examples (bash scripts, sdutil commands) are valid on Linux and provide any necessary adjustments for Windows users if needed.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/how-to-integrate-elastic-logs-with-azure-monitor.md
...es/how-to-integrate-elastic-logs-with-azure-monitor.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes GUI-based steps using the Azure Portal and does not provide any command-line examples for enabling diagnostic settings or downloading logs. There are no references to Windows-specific tools (such as PowerShell), but the instructions implicitly assume use of the Azure Portal, which is most commonly accessed from Windows environments. There are no CLI (az), PowerShell, or Linux shell examples, nor is there mention of how to perform these tasks from Linux or cross-platform environments.
Recommendations
- Add equivalent command-line instructions using Azure CLI (az), which is cross-platform and works on Linux, macOS, and Windows.
- Include examples for downloading logs using az storage blob commands or other cross-platform tools (e.g., curl, wget, or Azure Storage Explorer).
- Explicitly mention that all steps can be performed from any OS, and provide links to CLI documentation for users who prefer or require non-GUI workflows.
- If PowerShell examples are added, ensure that Bash/Linux shell equivalents are also provided.
Energy Data Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/energy-data-services/how-to-manage-users.md
...n/articles/energy-data-services/how-to-manage-users.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation consistently instructs users to run commands in 'Azure Cloud Shell', which by default is a Bash environment but is tightly integrated with Azure and often associated with Windows-centric workflows. There are no explicit PowerShell or Windows command examples, but the documentation does not mention or provide guidance for running these commands in a generic Linux/macOS terminal or on-premises shell. The screenshots and instructions focus exclusively on Azure/Microsoft tools and environments, with no mention of Linux-native authentication or CLI workflows outside of Azure's ecosystem.
Recommendations
- Explicitly state that the curl commands can be run from any Bash-compatible shell on Linux, macOS, or Windows (with WSL or Git Bash), not just Azure Cloud Shell.
- Provide examples or notes for running the commands in native Linux/macOS terminals, including any prerequisites (e.g., curl installation, environment variable setup).
- If authentication steps differ for Linux/macOS (e.g., using Azure CLI on Linux), include those instructions or references.
- Avoid implying that Azure Cloud Shell is the only or primary environment for these operations; mention alternatives such as local terminals.
- If screenshots are necessary, consider including examples from both Windows and Linux environments to demonstrate cross-platform compatibility.