Healthcare Apis

246
Total Pages
187
Linux-Friendly Pages
59
Pages with Bias
24.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

302 issues found
Showing 176-200 of 302 flagged pages
Healthcare Apis Learn how to configure Azure Storage to de-identify documents with the de-identification service .../healthcare-apis/deidentification/configure-storage.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation uses PowerShell syntax and variable assignment throughout, which is native to Windows and less familiar to Linux/macOS users. All command examples are shown in PowerShell, with no Bash or cross-platform shell alternatives. The tutorial explicitly states 'we're using PowerShell' and does not provide Linux/macOS-specific guidance, even though Azure CLI is cross-platform.
Recommendations
  • Provide Bash equivalents for all PowerShell commands, using standard shell variable assignment and command substitution.
  • Clarify that Azure CLI works on Linux/macOS and Windows, and encourage users to use their preferred shell.
  • Add a note or section for Linux/macOS users, highlighting any differences in syntax or environment setup.
  • Avoid PowerShell-specific constructs (e.g., $Variable, $(...)) in main examples, or present both PowerShell and Bash side-by-side.
GitHub Create Pull Request
Healthcare Apis De-identify multiple documents with the de-identification service in python ...pis/deidentification/quickstart-asynchronous-python.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively using PowerShell syntax for Azure CLI commands, both in setup and resource management steps. There are no Bash or Linux/macOS shell examples, and PowerShell is explicitly mentioned as the terminal of choice. This may create friction for Linux/macOS users who typically use Bash or other shells, as variable assignment and command substitution differ between PowerShell and Bash. The Python SDK and curl examples are cross-platform, but all Azure CLI instructions are PowerShell-centric.
Recommendations
  • Provide Bash equivalents for all Azure CLI command examples, especially for variable assignment and command substitution.
  • Explicitly state that Azure CLI commands can be run from any shell, and clarify differences in syntax for variable assignment and command substitution.
  • Avoid stating 'we're using PowerShell' unless both PowerShell and Bash examples are provided.
  • Add a section or callout for Linux/macOS users, highlighting any differences or providing tailored instructions.
GitHub Create Pull Request
Healthcare Apis Register a client application for the DICOM service in Microsoft Entra ID ...es/healthcare-apis/dicom/dicom-register-application.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively mentioning PowerShell and the New-SelfSignedCertificate command for creating self-signed certificates. There are no equivalent instructions or examples for Linux/macOS users, such as using OpenSSL. This omission may hinder non-Windows users from completing certificate-related steps without external research.
Recommendations
  • Add instructions for creating self-signed certificates on Linux/macOS using OpenSSL (e.g., openssl req -x509 ...).
  • Include cross-platform command examples or reference platform-agnostic tools.
  • Explicitly state that certificate creation can be performed on any OS and provide links to relevant Linux/macOS documentation.
GitHub Create Pull Request
Healthcare Apis Configure Azure RBAC for the DICOM service - Azure Health Data Services ...es/healthcare-apis/dicom/dicom-configure-azure-rbac.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Azure PowerShell for creating custom roles, without mentioning or providing examples for Linux/macOS alternatives such as Azure CLI or REST API. No Linux-specific instructions or parity are offered, and the only automation/tooling guidance is Windows-centric.
Recommendations
  • Add instructions and examples for creating custom roles using Azure CLI, which is cross-platform.
  • Reference REST API methods for role creation for platform-agnostic automation.
  • Clearly indicate that PowerShell is available on Linux/macOS, or provide links to installation guides for non-Windows users.
  • Present CLI and REST options alongside PowerShell, not after or as an afterthought.
GitHub Create Pull Request
Healthcare Apis Use Microsoft Entra External ID to grant access to the FHIR service in Azure Health Data Services .../healthcare-apis/fhir/azure-entra-external-id-setup.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides deployment instructions using PowerShell and Azure CLI, with explicit recommendations to run PowerShell locally in Visual Studio Code—a Windows-centric workflow. PowerShell examples are shown first in each code tab, and there are no Linux/macOS-specific instructions or examples for local environments. The use of Azure Cloud Shell and Azure CLI does provide cross-platform options, but the local workflow is biased toward Windows users. There is no mention of Linux/macOS-specific shell environments, nor troubleshooting for those platforms.
Recommendations
  • Add explicit instructions for running Azure CLI and Bash scripts locally on Linux and macOS, including any prerequisites or differences in environment setup.
  • Mention that Azure CLI is cross-platform and can be installed on Linux/macOS, with links to installation guides for those platforms.
  • Provide examples of running deployment scripts in Bash or zsh on Linux/macOS, and clarify that PowerShell Core is available on Linux/macOS if users prefer PowerShell.
  • Include troubleshooting tips for common issues encountered on Linux/macOS (e.g., file permissions, environment variables, authentication).
  • Reorder code tabs so that Azure CLI (cross-platform) is shown before PowerShell, or present both equally.
GitHub Create Pull Request
Healthcare Apis Configure export settings in FHIR service - Azure Health Data Services ...articles/healthcare-apis/fhir/configure-export-data.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the section on configuring Azure Storage networking for secure export. Only PowerShell commands are provided for critical configuration steps, with no equivalent Bash, Azure CLI, or cross-platform instructions. The use of PowerShell and references to installing PowerShell modules assume a Windows environment, and Windows-centric tools are mentioned exclusively. There are no Linux/macOS alternatives or examples, and Windows tooling is presented as the default approach.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, as Azure CLI is cross-platform and works on Linux/macOS.
  • Include Bash script examples for Linux users where scripting is required.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation instructions.
  • Reorder examples to present cross-platform (Azure CLI) instructions before or alongside PowerShell.
  • Add notes clarifying platform compatibility for all command-line instructions.
GitHub Create Pull Request
Healthcare Apis Configure import settings in the FHIR service - Azure Health Data Services ...articles/healthcare-apis/fhir/configure-import-data.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the section on configuring Azure Storage networking. Only PowerShell commands are provided for critical configuration steps, with no equivalent Bash, Azure CLI, or cross-platform alternatives. The use of PowerShell modules and commands assumes a Windows environment, and Windows tooling is mentioned exclusively. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, especially for storage account network rule configuration.
  • Include Bash shell examples where appropriate.
  • Explicitly mention cross-platform options (e.g., PowerShell Core, Azure CLI) and clarify which commands work on Linux/macOS.
  • Reorder examples so that cross-platform tools (Azure CLI) are shown first or alongside PowerShell.
  • Add a note about installing PowerShell Core on Linux/macOS if PowerShell is required.
GitHub Create Pull Request
Healthcare Apis Get started with the FHIR service in Azure Health Data Services ...articles/healthcare-apis/fhir/get-started-with-fhir.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation repeatedly lists PowerShell as a primary automation option alongside Azure CLI and REST API, and often mentions it first. There is a notable emphasis on PowerShell throughout, with no explicit mention of Linux/macOS shell equivalents (e.g., Bash), nor are Linux-specific patterns or tools highlighted. While cURL and REST Client are mentioned for CRUD operations, the overall scripting guidance leans toward Windows-centric tooling and workflows.
Recommendations
  • Explicitly mention Bash and Linux/macOS shell usage where PowerShell is referenced.
  • Provide example commands/scripts for Linux/macOS environments, especially for Azure CLI and REST API usage.
  • Ensure that sample scripts in referenced GitHub repositories include Linux/macOS compatible versions.
  • When listing tools or approaches, alternate the order (e.g., Azure CLI before PowerShell) or group them neutrally.
  • Add a note clarifying cross-platform compatibility for all tools and scripts.
GitHub Create Pull Request
Healthcare Apis Access Azure Health Data Services with cURL .../blob/main/articles/healthcare-apis/fhir/using-curl.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias by presenting PowerShell as the primary prerequisite and example environment, listing PowerShell tools and modules before CLI/Bash alternatives, and referencing Windows-centric tools (e.g., Git Bash for Windows). Linux/macOS equivalents are not explicitly mentioned, and PowerShell examples are shown first in each section.
Recommendations
  • Explicitly mention Bash/zsh as supported shells for Linux/macOS users in prerequisites.
  • Provide installation instructions for Azure CLI and cURL on Linux/macOS, not just Windows.
  • Show Bash examples first or alternate the order with PowerShell to avoid 'Windows first' bias.
  • Avoid recommending Windows-specific tools (e.g., Git Bash) as the default for Bash shells; mention native Bash on Linux/macOS.
  • Clarify that all CLI examples work natively on Linux/macOS terminals.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., environment variable syntax differences).
GitHub Create Pull Request
Healthcare Apis SMART on FHIR - Azure Health Data Services ...ob/main/articles/healthcare-apis/fhir/smart-on-fhir.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples use PowerShell syntax, and there are no equivalent bash or Linux/macOS shell commands provided. The instructions for cloning repositories, running scripts, and configuring secrets are presented exclusively in PowerShell, which may create friction for Linux/macOS users. Additionally, the examples and tooling references (e.g., dotnet user-secrets) are presented with Windows-centric patterns first, with no mention of cross-platform alternatives or explicit Linux/macOS guidance.
Recommendations
  • Provide bash/zsh equivalents for all PowerShell commands, especially for cloning repositories, encoding URLs, and running dotnet commands.
  • Explicitly state that the .NET SDK and dotnet CLI are cross-platform, and provide instructions for installing and running on Linux/macOS.
  • Add notes or sections for Linux/macOS users, including any differences in file paths, environment variables, or permissions.
  • Where PowerShell is used for scripting (e.g., base64 encoding), offer a bash/openssl alternative.
  • Consider reordering examples so that cross-platform or OS-neutral instructions are given before Windows-specific ones.
GitHub Create Pull Request
Healthcare Apis Introduction to Azure Health Data Services ...es/healthcare-apis/health-data-services-get-started.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation frequently references PowerShell and .NET SDK as primary tools for managing Azure Health Data Services, with examples and instructions for client registration and access token retrieval often mentioning PowerShell before Azure CLI or other cross-platform tools. There is a notable emphasis on Windows-centric tooling and patterns, with limited explicit mention of Linux/macOS alternatives or parity in examples.
Recommendations
  • Provide explicit Linux/macOS examples alongside PowerShell, such as Bash scripts and Azure CLI commands.
  • Ensure that cross-platform tools (e.g., Azure CLI, cURL, Python) are mentioned before or alongside Windows-specific tools.
  • Add screenshots and instructions for Linux/macOS environments where relevant.
  • Clarify that all operations can be performed on Linux/macOS and provide links to platform-specific guides.
  • Avoid listing Windows tools (PowerShell, .NET SDK) as the default or only option for critical tasks.
GitHub Create Pull Request
Healthcare Apis Choose a deployment method for the MedTech service - Azure Health Data Services ...n/articles/healthcare-apis/iot/deploy-choose-method.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias by consistently referencing Azure PowerShell (a Windows-centric tool) alongside Azure CLI for deployment methods, and by listing PowerShell before CLI in all relevant sections. There are no explicit Linux/macOS examples or mentions of platform-specific considerations, and the use of the 'Deploy to Azure' button relies on the Azure portal, which is cross-platform but often associated with Windows workflows. No Linux-specific tools or shell examples are provided.
Recommendations
  • Provide explicit Linux/macOS shell examples (e.g., Bash) for Azure CLI commands.
  • Clarify that Azure CLI is fully supported on Linux/macOS and can be used independently of PowerShell.
  • Where PowerShell is mentioned, add equivalent Bash or shell script examples for cross-platform parity.
  • Consider listing Azure CLI before PowerShell to reflect its cross-platform nature.
  • Add a note about platform compatibility for each deployment method.
GitHub Create Pull Request
Healthcare Apis Register a client application in Microsoft Entra ID for the Azure Health Data Services .../main/articles/healthcare-apis/register-application.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the section on creating self-signed certificates, where only the PowerShell command 'New-SelfSignedCertificate' is mentioned. No Linux or cross-platform alternatives (such as OpenSSL) are provided. The rest of the instructions are Azure portal-based and platform-neutral, but the certificate creation step could create friction for Linux/macOS users.
Recommendations
  • Include Linux/macOS instructions for creating self-signed certificates, such as using OpenSSL.
  • Provide cross-platform command examples side-by-side (e.g., PowerShell for Windows, OpenSSL for Linux/macOS).
  • Explicitly state that certificate creation can be performed on any OS and link to relevant documentation for each platform.
  • Avoid implying that PowerShell is the only or primary method for certificate creation.
GitHub Create Pull Request
Healthcare Apis Deploy the MedTech service using an Azure Resource Manager template - Azure Health Data Services ...in/articles/healthcare-apis/iot/deploy-arm-template.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes deploying the MedTech service via the Azure portal and the 'Deploy to Azure' button, with all screenshots and instructions referencing the graphical portal interface. There are no examples or guidance for deploying the ARM template using command-line tools such as Azure CLI, PowerShell, or Bash, nor are there instructions for Linux/macOS users. This creates a subtle bias toward Windows users, who are more likely to use the portal and PowerShell, while Linux users may prefer CLI or automation approaches.
Recommendations
  • Add step-by-step instructions for deploying the ARM template using Azure CLI (az deployment group create) and Bash, with example commands.
  • Include PowerShell deployment instructions for parity, but ensure CLI/Bash examples are presented alongside or before PowerShell.
  • Provide notes on cross-platform compatibility and clarify that the Azure portal is accessible from any OS/browser.
  • Add screenshots or terminal output examples for CLI/Bash deployments.
  • Explicitly mention that all deployment methods work on Windows, Linux, and macOS.
GitHub Create Pull Request
Healthcare Apis Receive device messages through Azure IoT Hub - Azure Health Data Services ...healthcare-apis/iot/device-messages-through-iot-hub.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively instructs users to use Visual Studio Code with the Azure IoT Tools extension for device creation and message sending, without mentioning or providing alternatives for Linux/macOS users (such as Azure CLI, IoT CLI, or other cross-platform tools). There are no examples or instructions for performing these steps outside of Visual Studio Code, which is more commonly used on Windows. No PowerShell-specific bias is present, but the lack of Linux-native or CLI-based examples creates friction for non-Windows users.
Recommendations
  • Add instructions and examples for using Azure CLI or Azure IoT CLI to create devices and send messages to IoT Hub, which work natively on Linux/macOS.
  • Explicitly mention that Visual Studio Code and the Azure IoT Tools extension are available on Linux/macOS, and provide installation guidance for those platforms.
  • Provide alternative workflows for device management and message sending using REST APIs or other cross-platform tools.
  • Reorder or supplement examples so that CLI-based or REST API methods are presented alongside or before GUI-based (VS Code) methods.
GitHub Create Pull Request
Healthcare Apis Azure Health Data Services known issues ...ocs/blob/main/articles/healthcare-apis/known-issues.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides a detailed PowerShell-based workaround for configuring the storage account for export, using Windows-centric tools (PowerShell, Az Module) and syntax. No equivalent Linux/macOS CLI (e.g., Azure CLI) instructions are provided, nor is there mention of cross-platform alternatives. The workaround is presented only in PowerShell, implying Windows as the default environment.
Recommendations
  • Add Azure CLI (az) command examples for configuring the storage account, which work on Linux, macOS, and Windows.
  • Explicitly state that the workaround can be performed on any OS, and provide guidance for installing required tools on Linux/macOS.
  • Present cross-platform examples first or side-by-side with PowerShell, to avoid implying Windows as the default.
  • Reference official Azure CLI documentation for resource configuration tasks.
GitHub Create Pull Request
Healthcare Apis What is the workspace? - Azure Health Data Services ...ob/main/articles/healthcare-apis/workspace-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions PowerShell as a deployment option and lists it first among deployment tools, which may suggest a Windows-centric approach. There are no explicit Linux/macOS examples or references to Bash, shell scripts, or Linux-specific tooling. The documentation does mention 'CLI' and 'Terraform', which are cross-platform, but does not provide parity in examples or highlight Linux usage.
Recommendations
  • Explicitly mention Bash/shell scripting as a deployment option alongside PowerShell.
  • Provide example commands for both Windows (PowerShell) and Linux/macOS (Bash/CLI) environments.
  • Clarify that Azure CLI and Terraform are cross-platform and provide links or examples for Linux/macOS users.
  • Avoid listing PowerShell first unless it is the most common or recommended tool for all platforms.
  • Add a section or note for Linux/macOS users to ensure inclusivity.
GitHub Create Pull Request
Healthcare Apis Release notes for 2021 Azure Health Data Services monthly releases ...ob/main/articles/healthcare-apis/release-notes-2021.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell scripts and tools for deployment and configuration, with no mention of Linux/macOS equivalents or cross-platform alternatives. Windows-centric tooling is referenced (PowerShell, ARM templates) without explicit Linux parity, and there are no examples or instructions for Linux/macOS users. This creates friction for non-Windows users attempting to automate or deploy Azure Health Data Services.
Recommendations
  • Provide Bash/CLI script examples alongside PowerShell, or clarify cross-platform compatibility.
  • Explicitly mention Linux/macOS support for deployment scripts and tools.
  • Add references to Linux-native tools and workflows (e.g., Azure CLI usage from Bash).
  • Ensure documentation links to cross-platform instructions where available.
GitHub Create Pull Request
Healthcare Apis Deploy Azure Health Data Services FHIR service using ARM template ...re-apis/fhir/fhir-service-resource-manager-template.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as the first option in all code tabs and deployment instructions, and Windows-centric tools (PowerShell, Visual Studio Code, Git Bash for Windows) are mentioned before Linux-native alternatives. While Azure CLI is provided as a cross-platform alternative, the examples and instructions often assume a Windows environment, such as using backslashes in file paths and referencing PowerShell as a local shell for CLI usage.
Recommendations
  • Alternate the order of PowerShell and CLI tabs so that CLI (Linux/macOS friendly) is shown first in some sections.
  • Use forward slashes in CLI file path examples, or provide both Windows and Linux/macOS variants.
  • Explicitly mention Linux/macOS shells (e.g., Bash, Zsh) as supported environments for Azure CLI, not just Git Bash for Windows.
  • Clarify that Visual Studio Code is cross-platform and suggest other editors for Linux/macOS users.
  • Add troubleshooting notes or tips for Linux/macOS users where behaviors may differ (e.g., environment variables, file paths).
GitHub Create Pull Request
Healthcare Apis Find identity object IDs for authentication in Azure API for FHIR ...re-apis/azure-api-for-fhir/find-identity-object-ids.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently presents Microsoft Graph PowerShell examples before Azure CLI examples, and PowerShell is a Windows-centric tool. There are no explicit Linux/macOS shell examples, and the PowerShell commands are not cross-platform by default. While Azure CLI is cross-platform and included, the ordering and emphasis may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Explicitly note that Azure CLI commands work on Windows, Linux, and macOS.
  • Clarify that Microsoft Graph PowerShell is available on all platforms, or provide alternative commands for Linux/macOS if not.
  • Consider adding Bash or shell script examples where relevant.
  • Add a note about prerequisites for each tool, including installation links for all platforms.
GitHub Create Pull Request
Healthcare Apis Configure Azure RBAC for the DICOM service - Azure Health Data Services ...es/healthcare-apis/dicom/dicom-configure-azure-rbac.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Azure PowerShell for creating custom roles, without mentioning or providing equivalent instructions for Linux/macOS users (e.g., Azure CLI or REST API). No Linux/macOS-specific tools or examples are provided, and the only automation path described is via PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Add instructions and examples for creating custom roles using Azure CLI, which is cross-platform.
  • Reference REST API methods for role creation for users who prefer scripting outside PowerShell.
  • Explicitly state that Azure PowerShell is available on Linux/macOS, or provide links to installation guides for non-Windows platforms.
  • Present examples for both PowerShell and CLI side-by-side to ensure parity.
GitHub Create Pull Request
Healthcare Apis What is the workspace? - Azure Health Data Services ...ob/main/articles/healthcare-apis/workspace-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions PowerShell as a deployment option and lists it first among deployment tools, which may imply a Windows-centric approach. There are no explicit Linux/macOS-specific examples or mentions of Bash, shell scripts, or Linux-native tools. The lack of cross-platform command examples and the prioritization of PowerShell can create friction for Linux/macOS users.
Recommendations
  • Provide explicit examples for Linux/macOS users, such as Bash or shell script equivalents for workspace provisioning and deployment.
  • List deployment tools in a neutral or alphabetical order (e.g., CLI, PowerShell, Terraform, .NET SDK) to avoid implying preference.
  • Clarify that Azure CLI and Terraform are cross-platform and provide sample commands for both Windows (PowerShell) and Linux/macOS (Bash).
  • Add notes or links to platform-specific guidance for Linux/macOS users where relevant.
GitHub Create Pull Request
Healthcare Apis Private link for Azure API for FHIR ...care-apis/azure-api-for-fhir/configure-private-link.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it mentions that Azure CLI and PowerShell can be used to create private endpoints, the examples and walkthroughs are focused on the Azure portal (which is cross-platform but often Windows-centric in screenshots and usage patterns). In troubleshooting, command-line examples use Windows command prompts (e.g., 'C:\Users\testuser>nslookup'), and instructions for VM access specify RDP (Remote Desktop Protocol), which is primarily a Windows method, without mentioning SSH or Linux alternatives. There are no explicit Linux/macOS command-line examples, nor are Linux tools or workflows discussed.
Recommendations
  • Include Linux/macOS equivalents for command-line examples, such as showing 'nslookup' or 'dig' usage in a bash shell.
  • Mention SSH as an alternative to RDP for VM access, especially for Linux VMs.
  • Provide explicit Azure CLI examples for key tasks, and clarify that CLI works cross-platform.
  • Ensure screenshots and instructions are not Windows-centric (e.g., avoid showing Windows file paths or prompts exclusively).
  • Add notes or sections for Linux/macOS users where workflows or tools differ.
GitHub Create Pull Request
Healthcare Apis Configure Azure RBAC role for the FHIR service in Azure Health Data Services .../main/articles/healthcare-apis/configure-azure-rbac.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While the main instructions focus on using the Azure portal (which is cross-platform), the only CLI tool mentioned for creating custom roles is Azure PowerShell, with no reference to Azure CLI or other Linux-friendly alternatives. The link for custom role creation points specifically to a PowerShell-based guide, and PowerShell is a Windows-centric tool (despite its cross-platform availability, it is still less common on Linux/macOS). No Linux-specific tools or examples are provided, and PowerShell is mentioned before any alternatives.
Recommendations
  • Add instructions and examples for creating custom roles using Azure CLI, which is natively supported on Linux/macOS.
  • Include explicit mention of cross-platform tools and clarify that PowerShell is available on Linux/macOS, but Azure CLI may be preferred for those environments.
  • Provide parity in documentation by listing Azure CLI instructions before or alongside PowerShell, especially for tasks like custom role creation.
  • Consider adding screenshots or terminal examples from Linux/macOS environments.
GitHub Create Pull Request
Healthcare Apis Configure local role-based access control (local RBAC) for Azure API for FHIR ...thcare-apis/azure-api-for-fhir/configure-local-rbac.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell and Azure CLI examples for creating service principals, but the PowerShell example is presented first and uses Windows-centric tools. There is no explicit mention of Linux/macOS compatibility for PowerShell commands, nor are there bash-specific CLI examples or notes about running CLI commands in Linux/macOS environments. The instructions and screenshots reference the Azure portal, which is cross-platform, but scripting guidance is biased toward Windows users.
Recommendations
  • Add explicit bash shell examples for Azure CLI commands, including variable assignment and command usage in Linux/macOS.
  • Clarify that Azure CLI commands work cross-platform and provide notes or examples for Linux/macOS users.
  • Mention that PowerShell Core is available on Linux/macOS, or recommend using Azure CLI for those platforms.
  • Present CLI examples before PowerShell examples, or side-by-side, to avoid Windows-first bias.
  • Add troubleshooting notes for common issues on Linux/macOS (e.g., authentication, environment setup).
GitHub Create Pull Request
← Previous Page 8 of 13 Next →