Healthcare Apis

490
Total Pages
455
Linux-Friendly Pages
35
Pages with Bias
7.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

66 issues found
Showing 26-50 of 66 flagged pages
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-11 06:20
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-specific examples or references to Bash, shell scripting, or Linux-native tools. The lack of Linux/macOS examples or parity in tooling references may create friction for non-Windows users.
Recommendations
  • Explicitly mention Bash, shell scripting, or Linux/macOS CLI usage alongside PowerShell.
  • Provide example deployment commands for both PowerShell and Bash/CLI.
  • Clarify that Azure CLI and Terraform are cross-platform and provide links or notes for Linux/macOS installation and usage.
  • Avoid listing PowerShell first unless it is the most common or recommended approach for all platforms.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions using the PowerShell command 'New-SelfSignedCertificate' to create a self-signed certificate for testing, but does not provide equivalent instructions or examples for Linux/macOS users (e.g., using OpenSSL). No other explicit Windows bias is present, but the omission of Linux/macOS alternatives creates friction for non-Windows users.
Recommendations
  • Add instructions or examples for creating self-signed certificates on Linux/macOS using OpenSSL (e.g., 'openssl req -x509 ...').
  • Clarify that the PowerShell example is for Windows, and provide platform-agnostic guidance or links to relevant Linux/macOS documentation.
  • Consider including a table or section listing common certificate creation tools for all major platforms.
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-11 06:20
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 both Azure PowerShell and Azure CLI as options for creating private endpoints, the only explicit command-line examples shown (nslookup output, VM access instructions) use Windows conventions (e.g., C:\Users\testuser>, RDP instructions). There are no Linux/macOS-specific instructions or screenshots, and remote access is described only via RDP, which is Windows-centric. The CLI and PowerShell links are present, but the page itself does not provide parity in examples or troubleshooting for Linux/macOS users.
Recommendations
  • Include Linux/macOS command-line examples alongside Windows ones (e.g., show nslookup output from a Bash shell).
  • Describe how to access VMs using SSH for Linux/macOS, not just RDP.
  • Add screenshots or instructions for Azure CLI usage in Linux/macOS environments.
  • Explicitly mention that all steps can be performed from Linux/macOS, and provide guidance for common differences (e.g., file paths, remote access tools).
GitHub Create Pull Request
Healthcare Apis Configure customer-managed keys for Azure API for FHIR ...thcare-apis/azure-api-for-fhir/customer-managed-key.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently, both as a primary automation example and as the only script shown for ARM template deployment. The PowerShell section appears before the Azure CLI section, and PowerShell is referenced in the metadata. No Linux/macOS-specific shell examples (e.g., Bash) are provided, and the CLI example is not shown first. The ARM template deployment is only demonstrated with PowerShell, omitting az CLI or Bash alternatives.
Recommendations
  • Add Bash or az CLI deployment examples for ARM templates alongside PowerShell.
  • Present Azure CLI examples before PowerShell, or at least equally.
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS).
  • Include notes or examples for Linux/macOS users where relevant.
  • Balance metadata and tracking tags to reflect CLI and cross-platform tooling, not just PowerShell.
GitHub Create Pull Request
Healthcare Apis Register a resource app in Microsoft Entra ID - Azure API for FHIR ...-api-for-fhir/register-resource-azure-ad-client-app.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell as the primary method for registering a resource application, mentioning it before the Azure CLI alternative. The use of PowerShell (a Windows-centric tool) and the ordering of examples may create friction for Linux/macOS users, although an Azure CLI example is provided as a workaround.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Explicitly state that both PowerShell and Azure CLI are supported on Windows, Linux, and macOS.
  • Add a note clarifying that Azure CLI is recommended for non-Windows platforms.
  • Consider including bash or shell script examples where appropriate.
  • Avoid language or ordering that implies PowerShell is the default or preferred method.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page references Azure PowerShell as the only method for creating custom roles, without mentioning or providing equivalent instructions for Azure CLI or other cross-platform tools. There are no Linux/macOS-specific examples or guidance, and PowerShell is a Windows-centric tool, which may create friction for non-Windows users.
Recommendations
  • Add instructions for creating custom roles using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include examples or links for role assignment using Azure CLI and REST API, not just PowerShell.
  • Explicitly mention that Azure CLI can be used on Linux/macOS, and provide parity in examples.
  • Where PowerShell is referenced, add a note or section for Linux/macOS users with alternative commands.
GitHub Create Pull Request
Healthcare Apis SMART on FHIR - Azure API for FHIR ...es/healthcare-apis/azure-api-for-fhir/smart-on-fhir.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 are provided in PowerShell, with no equivalent bash or Linux/macOS shell commands. Git usage and .NET commands are shown in PowerShell syntax, and there are no explicit instructions or notes for Linux/macOS users. This may create friction for non-Windows users attempting to follow the tutorial.
Recommendations
  • Provide bash/zsh equivalents for all PowerShell scripts and commands, especially for reply URL encoding and .NET user-secrets usage.
  • Add notes or sections clarifying cross-platform compatibility for .NET SDK and app launcher steps.
  • Explicitly mention Linux/macOS prerequisites and any required package installations.
  • Show git commands in a generic shell format or clarify that they work on all platforms.
  • Consider reordering examples or providing parallel instructions for Windows and Linux/macOS users.
GitHub Create Pull Request
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell syntax and variable assignment patterns throughout all Azure CLI examples, implicitly favoring Windows environments. There are no Bash or Linux/macOS shell equivalents provided, and the tutorial states 'we're using PowerShell' without offering alternatives. This creates friction for Linux and macOS users who may be unfamiliar with PowerShell conventions or syntax.
Recommendations
  • Provide parallel Bash examples for all CLI commands and variable assignments.
  • Clarify that Azure CLI works cross-platform and show how to run commands in Bash/zsh/fish shells.
  • Avoid PowerShell-specific variable assignment (e.g., $Variable = ...) in generic CLI documentation; use POSIX shell syntax (e.g., VARIABLE=...) where possible.
  • Explicitly mention that the tutorial applies to Linux/macOS and Windows, and link to platform-specific guidance if available.
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-11 06:20
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 all Azure CLI and scripting examples, including variable assignment and command chaining. There are no equivalent Bash or Linux shell examples for key steps such as resource creation, variable assignment, and cleanup. The tutorial states 'open your terminal of choice' but then proceeds with PowerShell throughout, which may create friction for Linux/macOS users unfamiliar with PowerShell conventions.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell examples, especially for Azure CLI commands and variable assignments.
  • Explicitly state which examples are for PowerShell and which are for Bash, and present both side-by-side where possible.
  • Clarify any platform-specific requirements or differences in command syntax (e.g., variable assignment, command substitution).
  • Ensure that Linux/macOS users can follow the tutorial without needing to install or use PowerShell.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias towards Windows by exclusively referencing Azure PowerShell for creating custom roles, without mentioning or providing examples for equivalent Linux/macOS tools (such as Azure CLI or REST API). No Linux/macOS-specific instructions or parity examples are given, and the only automation path described is via PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Include instructions and examples for creating custom roles using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for role management, providing links or sample requests.
  • Ensure screenshots and UI instructions are platform-neutral or clarify any platform-specific differences.
  • Add a note that PowerShell is available on Linux/macOS, or provide alternative commands for those platforms.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation repeatedly references Azure PowerShell as a primary deployment tool alongside Azure CLI, and lists PowerShell before CLI in multiple sections. There are no explicit Linux/macOS-specific examples or guidance, and the use of PowerShell may imply a Windows-centric approach, especially for users unfamiliar with PowerShell on non-Windows platforms. No Linux-specific tools, shell scripts, or OS-specific considerations are mentioned.
Recommendations
  • Provide explicit Linux/macOS examples for Azure CLI usage, including shell commands and environment notes.
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS, and consider listing CLI before PowerShell in relevant sections.
  • Add notes or links about installing and using Azure PowerShell on Linux/macOS, or suggest CLI as the default for non-Windows users.
  • Include troubleshooting tips or prerequisites for Linux/macOS environments where relevant.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides PowerShell-only examples for configuring Azure Storage networking rules, with no equivalent CLI or Bash instructions for Linux/macOS users. The use of PowerShell and references to installing PowerShell modules create friction for non-Windows users, as there are no alternative commands or guidance for Linux/macOS environments.
Recommendations
  • Add Azure CLI or Bash examples alongside PowerShell commands for configuring storage account network rules.
  • Provide guidance on how Linux/macOS users can perform the same configuration steps, including installation instructions for required tools.
  • Explicitly mention cross-platform alternatives where PowerShell is referenced, and clarify which steps can be completed in the Azure Portal versus command line.
  • Consider reordering examples so that cross-platform tools (e.g., Azure CLI) are shown before or alongside PowerShell.
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-11 06:20
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, particularly in the section on securing the FHIR service's import operation. PowerShell is the only CLI tool shown for configuring Azure Storage networking, with no equivalent Bash, Azure CLI, or cross-platform instructions. Windows-centric tools and patterns (PowerShell modules, commands) are mentioned exclusively, and Linux/macOS users are not provided with alternative commands or guidance. The PowerShell example appears before any mention of other methods, and no parity is offered for non-Windows environments.
Recommendations
  • Provide Azure CLI and/or Bash examples alongside PowerShell commands for configuring storage account networking and permissions.
  • Explicitly state that PowerShell commands can be run on Linux/macOS (if true), or offer guidance for installing PowerShell Core cross-platform.
  • Add notes or links for Linux/macOS users on how to perform equivalent tasks using their native tools.
  • Reorder examples to present cross-platform or Azure CLI instructions first, or at least in parallel with PowerShell.
  • Include troubleshooting tips for common issues faced by Linux/macOS users (e.g., authentication, module installation).
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-11 06:20
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, especially in the SMART on FHIR Proxy section. All command-line examples use PowerShell syntax, and there are no equivalent bash or Linux/macOS instructions. The instructions for generating reply URLs, cloning repositories, configuring secrets, and running the app are all presented in PowerShell, which may create friction for Linux/macOS users. Additionally, Windows-centric tools and patterns (PowerShell, dotnet user-secrets) are mentioned exclusively, with no guidance for alternative platforms.
Recommendations
  • Provide bash/zsh equivalents for all PowerShell scripts and commands, especially for reply URL generation and repository operations.
  • Explicitly mention cross-platform compatibility for .NET SDK and app launcher, and provide instructions for running on Linux/macOS.
  • Add notes or sections for Linux/macOS users, including how to install prerequisites and handle configuration (e.g., environment variables instead of user-secrets).
  • Reorder examples so that platform-neutral or Linux/macOS instructions are presented alongside or before Windows-specific ones.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently presents PowerShell examples first and recommends running scripts in PowerShell locally using Visual Studio Code, which is a Windows-centric workflow. While Azure CLI examples are provided (which are cross-platform), there is no explicit mention or guidance for Linux/macOS environments, such as running scripts in native Linux terminals or using Bash. The documentation also references Azure Cloud Shell, which is cross-platform, but the local instructions and tooling are Windows-focused. No Linux-specific tools, shell environments, or troubleshooting notes are provided.
Recommendations
  • Explicitly mention that Azure CLI commands can be run natively on Linux/macOS terminals, not just in Azure Cloud Shell.
  • Provide Bash script examples or note that the CLI commands work in Bash and Zsh shells.
  • Include guidance for installing and using Azure CLI on Linux/macOS, and clarify that Visual Studio Code is available cross-platform.
  • Avoid recommending PowerShell locally as the default; present CLI and Bash examples first or in parallel.
  • Add troubleshooting notes or tips for Linux/macOS users where workflows or UI may differ.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented first throughout, and instructions reference running code in PowerShell locally, Visual Studio Code, or Azure Cloud Shell before mentioning CLI alternatives. The CLI instructions also suggest using Git Bash (from Git for Windows) as an example Bash shell, which is a Windows-centric recommendation. There is no explicit mention of Linux/macOS environments or shell options, and the CLI example uses Windows-style path separators ('src\templates\fhirtemplate.json'), which may confuse Linux/macOS users.
Recommendations
  • Alternate the order of PowerShell and CLI sections, or present CLI instructions first to balance visibility.
  • Explicitly mention Linux/macOS compatibility in CLI instructions and recommend native Bash or Terminal environments.
  • Use POSIX-style path separators ('/') in CLI examples, or provide both Windows and Linux/macOS variants.
  • Include notes or troubleshooting tips for Linux/macOS users, especially regarding file paths and shell environments.
  • Reference cross-platform tools and environments (e.g., native Bash, zsh, Terminal) instead of only Windows-centric options like Git Bash.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation repeatedly lists PowerShell as a primary scripting option alongside Azure CLI and REST API, but does not provide explicit Linux/macOS-specific examples or mention Bash scripting. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. While Azure CLI and cURL are mentioned, examples and instructions are not tailored for Linux environments, and Windows tools/patterns are referenced first in most cases.
Recommendations
  • Provide explicit Bash and Linux/macOS terminal examples for all CLI/scripted steps.
  • List Azure CLI and cURL before PowerShell when describing cross-platform options.
  • Clarify that Azure CLI and cURL work natively on Linux/macOS and provide installation guidance if needed.
  • Include sample scripts or commands for Linux/macOS environments in the referenced GitHub samples.
  • Mention that PowerShell Core is cross-platform, but highlight native Linux tools where appropriate.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes deployment using the Azure portal and the 'Deploy to Azure' button, which is primarily accessed via a web browser. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there any instructions for deploying via Linux/macOS tools or environments. All screenshots and instructions reference the Azure portal UI, which is platform-agnostic but typically associated with Windows workflows. There is no mention of Linux-specific deployment methods or parity for users who prefer command-line automation.
Recommendations
  • Add instructions for deploying the ARM template using Azure CLI, including example commands for Linux/macOS.
  • Include PowerShell examples if relevant, but ensure Azure CLI/Bash examples are presented alongside or before them.
  • Explicitly mention that the Azure portal is accessible from any OS and clarify platform requirements if any exist.
  • Provide guidance for headless/server environments where browser access may not be available.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing Visual Studio Code and the Azure IoT Tools extension for device creation and message sending, without mentioning or providing examples for Linux/macOS alternatives or CLI-based workflows. The tutorial assumes the use of a graphical interface common on Windows, and does not discuss cross-platform command-line tools (such as Azure CLI or Azure IoT CLI) that are available on Linux/macOS. There are no explicit PowerShell examples, but the reliance on VS Code and its extensions is more typical of Windows setups. No Linux-specific instructions, screenshots, or troubleshooting are provided.
Recommendations
  • Add instructions and examples for using Azure CLI and Azure IoT CLI to create devices and send messages, which work on Linux/macOS.
  • Include screenshots or terminal commands for Linux/macOS environments.
  • Mention that Visual Studio Code and Azure IoT Tools are cross-platform, and provide installation guidance for Linux/macOS.
  • Provide troubleshooting tips for Linux/macOS users (e.g., permissions, dependencies).
  • Consider listing CLI-based steps before or alongside GUI-based steps to ensure parity.
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-11 06:20
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 workaround for configuring the storage account for FHIR export using only PowerShell commands and the Az PowerShell module, which are Windows-centric tools. There are no equivalent instructions or examples for Linux/macOS users (e.g., using Azure CLI or Bash), nor is there mention of cross-platform alternatives. The PowerShell example is presented as the sole solution, creating friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI commands for configuring the storage account for export, as Azure CLI is cross-platform and works on Linux/macOS.
  • Explicitly mention that the workaround can be performed on any OS using Azure CLI, and provide step-by-step Bash examples.
  • If PowerShell is required, clarify how Linux/macOS users can install and use PowerShell Core, or link to relevant instructions.
  • Present cross-platform solutions first or side-by-side with Windows-specific ones to avoid Windows-first bias.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates mild Windows bias in the section about creating self-signed certificates, where only the PowerShell command 'New-SelfSignedCertificate' is mentioned as a tool for certificate creation. No Linux or cross-platform alternatives (such as OpenSSL) are referenced. The rest of the guide is based on Azure Portal UI, which is platform-agnostic, but the certificate creation step could create friction for Linux/macOS users.
Recommendations
  • Include instructions or examples for creating self-signed certificates using OpenSSL, which is available on Linux and macOS.
  • Explicitly mention that certificate creation can be performed on any OS and provide links or steps for non-Windows environments.
  • Where PowerShell is referenced, clarify if PowerShell Core (cross-platform) is supported, or provide alternatives.
  • Ensure that any command-line tool recommendations are cross-platform or alternatives are listed.
GitHub Create Pull Request
Healthcare Apis Quickstart: Deploy Azure API for FHIR using an ARM template ...i-for-fhir/azure-api-fhir-resource-manager-template.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation gives equal coverage to Azure Portal, PowerShell, and CLI methods for deploying Azure API for FHIR. However, there is a subtle Windows bias: PowerShell is presented as a primary automation option, and the CLI prerequisites suggest Git Bash (a Windows-centric Bash shell) before mentioning native Bash environments. PowerShell examples are prominent, and the CLI instructions do not explicitly mention Linux/macOS shells or provide platform-specific notes. The documentation does not provide any Linux/macOS-specific troubleshooting or highlight differences in shell environments.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux/macOS terminals, not just Git Bash on Windows.
  • Provide notes or troubleshooting tips for Linux/macOS users, especially regarding shell differences and environment setup.
  • Add parity in example ordering: alternate between PowerShell and CLI as the first example, or clarify that both are cross-platform.
  • Consider including screenshots or references for Linux/macOS environments where appropriate.
  • Remove or supplement the Git Bash suggestion with references to native Bash/Zsh on Linux/macOS.
GitHub Create Pull Request
Healthcare Apis Authentication and authorization in Azure Health Data Services ...ticles/healthcare-apis/authentication-authorization.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Windows-specific tools (PowerShell) and patterns (Visual Studio Code REST Client extension) before cross-platform or Linux-native equivalents (curl, CLI). No explicit Linux/macOS examples are provided, and Windows tools are listed first when suggesting how to obtain access tokens. However, the page does mention CLI and curl, which are cross-platform, and does not provide step-by-step examples that are Windows-only.
Recommendations
  • Provide explicit Linux/macOS examples for obtaining access tokens, such as using curl or Azure CLI.
  • List cross-platform tools (curl, CLI) before Windows-specific tools (PowerShell, Visual Studio Code REST Client extension) when suggesting options.
  • Include sample commands for both Windows (PowerShell) and Linux/macOS (bash/curl) to ensure parity.
  • Clarify that all listed tools are available cross-platform where applicable.
GitHub Create Pull Request
Healthcare Apis Data conversion for Azure API for FHIR ...les/healthcare-apis/azure-api-for-fhir/convert-data.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by exclusively referencing the Azure portal (a web UI often associated with Windows workflows) for configuration steps and by not providing explicit Linux/macOS command-line examples or guidance. CLI instructions use the Azure CLI, which is cross-platform, but there is no mention of Linux-specific considerations, nor are there examples showing Linux shell usage or differences. Visual Studio Code is referenced for template editing, which is cross-platform, but no alternative editors or Linux-specific instructions are provided. No PowerShell-only commands or Windows-only tools are present, but the overall workflow assumes familiarity with Windows-centric Azure portal navigation.
Recommendations
  • Add explicit Linux/macOS shell examples for CLI steps, such as using bash/zsh.
  • Clarify that Azure CLI commands work on Linux/macOS and provide installation instructions for those platforms.
  • Mention alternative editors for template customization, such as Vim or VS Code on Linux.
  • Include screenshots or instructions for Azure portal navigation on non-Windows platforms (if any differences exist).
  • Note any OS-specific considerations for hosting templates or configuring firewalls.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for finding identity object IDs, but PowerShell (typically associated with Windows) is presented first in every section. There is a notable emphasis on Microsoft Graph PowerShell commands, which are more commonly used on Windows, and no explicit mention of Linux/macOS compatibility or usage patterns. However, Azure CLI examples are present, which are cross-platform.
Recommendations
  • Alternate the order of examples, sometimes showing Azure CLI first to avoid implicit prioritization of Windows tools.
  • Explicitly mention that Azure CLI works on Linux and macOS, and provide installation/use guidance for those platforms.
  • Add a brief note about PowerShell Core availability on Linux/macOS, or link to relevant documentation for cross-platform usage.
  • Consider including Bash or shell script examples where appropriate, especially for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 2 of 3 Next →