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 76-100 of 302 flagged pages
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/smart-on-fhir.md ...ob/main/articles/healthcare-apis/fhir/smart-on-fhir.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell scripts for key steps (such as generating reply URLs and running .NET applications), referencing Windows-specific tools and patterns (PowerShell, dotnet user-secrets), and omitting equivalent Linux/macOS shell commands or guidance. All command-line examples use PowerShell syntax, and there is no mention of Bash, Linux, or cross-platform alternatives. This may hinder Linux or macOS users attempting to follow the tutorial.
Recommendations
  • Provide Bash/zsh equivalents for all PowerShell scripts, especially for base64 encoding and string manipulation tasks.
  • Clearly indicate that .NET and git commands are cross-platform, and provide any necessary Linux/macOS installation instructions.
  • Include explicit notes or sections for Linux/macOS users, highlighting any differences in environment setup or command usage.
  • Where PowerShell is used, offer alternative commands using Bash or other common shells.
  • Avoid assuming localhost:5001 is always available; mention how to run the app on Linux/macOS and troubleshoot port issues.
  • Add screenshots or instructions showing the process on non-Windows platforms if applicable.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/using-curl.md .../blob/main/articles/healthcare-apis/fhir/using-curl.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell in prerequisites and examples, referencing Windows-specific tools (PowerShell, Git Bash), and lacking explicit Linux/macOS shell examples. The CLI section mentions Bash only in the context of 'Git Bash for Windows', and does not provide native Linux/macOS instructions or examples. All shell scripting examples use PowerShell or Azure CLI, with no direct Bash or Linux/macOS terminal equivalents.
Recommendations
  • Add explicit Bash examples for Linux/macOS users, including native shell commands for obtaining access tokens and using cURL.
  • Update prerequisites to mention Bash shells available by default on Linux/macOS, not just 'Git Bash for Windows'.
  • Provide installation instructions for cURL and Azure CLI for Linux/macOS, not just generic download links.
  • Ensure that examples using environment variables and command syntax are compatible with Bash/zsh (e.g., $fhirservice vs $fhirservice in PowerShell).
  • Reorder sections so that Windows and Linux/macOS instructions are presented with equal prominence, or provide tabs for each platform.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/health-data-services-get-started.md ...es/healthcare-apis/health-data-services-get-started.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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, and mentions them before or alongside Azure CLI. There is a tendency to list Windows-centric tools (PowerShell, .NET C#) before cross-platform or Linux-native tools (cURL, Python), and no explicit Linux-specific examples or guidance are provided. This may make Linux users feel secondary or unsupported.
Recommendations
  • Provide explicit Linux/bash examples for common tasks, such as authentication and resource management, using Azure CLI and cURL.
  • When listing tools or scripting options, alternate the order or group by platform (e.g., 'PowerShell (Windows), Bash (Linux), Azure CLI (cross-platform)').
  • Add sample commands and scripts for Linux environments, including bash scripts and Python usage for API access.
  • Clarify that Azure CLI, cURL, and REST client are fully supported on Linux and macOS, and provide links to installation guides for these platforms.
  • Avoid listing Windows-centric tools first unless there is a technical reason; strive for parity in documentation structure and examples.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/register-application.md .../main/articles/healthcare-apis/register-application.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively mentioning PowerShell and the Windows-specific 'New-SelfSignedCertificate' command for generating self-signed certificates, without providing equivalent Linux/macOS instructions (e.g., using OpenSSL). No Linux or cross-platform examples are given for certificate creation, and Windows tools are referenced without alternatives.
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 and Bash/OpenSSL).
  • Reference platform-agnostic tools or clarify which steps are OS-specific.
  • Add notes or links to external resources for Linux/macOS users where Windows tools are mentioned.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/deploy-choose-method.md ...n/articles/healthcare-apis/iot/deploy-choose-method.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by repeatedly referencing Azure PowerShell as a primary deployment method alongside Azure CLI, without clarifying cross-platform compatibility or providing explicit Linux/macOS shell examples. PowerShell is traditionally associated with Windows, and its mention before or alongside CLI can imply a Windows-first approach. There are no bash, shell, or Linux-specific deployment instructions or examples, and no mention of platform differences or requirements.
Recommendations
  • Explicitly state that Azure CLI and Bicep are cross-platform and provide examples using bash or other Linux/macOS shells.
  • Clarify that Azure PowerShell is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
  • Add Linux/macOS-specific deployment instructions or examples, such as using bash scripts or terminal commands.
  • Ensure that references to PowerShell do not implicitly suggest Windows-only usage; consider listing CLI examples first or in parallel.
  • Include a note on platform compatibility for each deployment method.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/release-notes-2021.md ...ob/main/articles/healthcare-apis/release-notes-2021.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Deploy and configure Azure Health Data Services using scripts' section, where PowerShell is mentioned first and most prominently, with no explicit mention of Bash or Linux shell scripts. There is a lack of Linux-specific examples or references, and Windows-centric tools (PowerShell, ARM templates) are referenced without clear Linux equivalents or parity.
Recommendations
  • Provide Bash or Linux shell script examples alongside PowerShell scripts for deployment and configuration tasks.
  • Explicitly mention cross-platform compatibility for CLI and ARM templates, and clarify any platform-specific requirements.
  • Ensure that Linux tools and patterns (e.g., Azure CLI usage in Bash, deployment from Linux environments) are documented and given equal prominence.
  • Add notes or sections for Linux users, including troubleshooting tips and environment setup instructions.
  • Review and update documentation to avoid listing Windows tools first unless there is a technical reason.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/workspace-overview.md ...ob/main/articles/healthcare-apis/workspace-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as the first deployment option and mentioning it explicitly, while not providing any Linux-specific examples or guidance. Although Azure CLI and Terraform are mentioned, there are no concrete examples or instructions for Linux users, and the overall deployment guidance leans toward Windows-centric tools and patterns.
Recommendations
  • Provide explicit Linux shell (bash) examples for workspace and service deployment using Azure CLI.
  • Include step-by-step instructions or links for deploying via Azure CLI on Linux and macOS.
  • Ensure parity in example scripts, showing both PowerShell and bash equivalents side-by-side.
  • Mention cross-platform compatibility for all tools (Azure CLI, Terraform) and clarify usage on Linux.
  • Avoid listing PowerShell first; alternate or group deployment options to avoid perceived prioritization.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/customer-managed-key.md ...thcare-apis/azure-api-for-fhir/customer-managed-key.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples for both direct configuration and ARM template deployment, and mentioning PowerShell before CLI. There are no explicit Linux shell (bash) or cross-platform scripting examples, and the CLI example is presented after PowerShell. No Linux-specific tools or patterns are referenced, and the deployment script for ARM templates is only shown in PowerShell, with no equivalent bash or Linux shell example.
Recommendations
  • Add bash (Linux shell) examples for ARM template deployment using Azure CLI (e.g., az deployment group create).
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Explicitly mention that all CLI commands work on Linux, macOS, and Windows, and provide platform-agnostic instructions.
  • Include guidance for Linux users on prerequisites and environment setup (e.g., installing Azure CLI on Linux).
  • Where PowerShell is used, provide equivalent bash or shell script alternatives for key operations.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/configure-azure-rbac.md .../main/articles/healthcare-apis/configure-azure-rbac.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by referencing PowerShell as the method for creating custom roles, without mentioning cross-platform or Linux alternatives. There are no CLI or Bash examples, and the only tool mentioned for advanced role management is Azure PowerShell, which is traditionally associated with Windows environments. No Linux-specific instructions or parity examples are provided.
Recommendations
  • Include Azure CLI examples for creating custom roles, as Azure CLI is cross-platform and widely used on Linux.
  • Mention Bash or shell scripting alternatives where PowerShell is referenced.
  • Add explicit instructions or links for performing RBAC tasks on Linux/macOS, ensuring parity with Windows guidance.
  • Clarify that Azure PowerShell is available cross-platform, if it is intended to be used on Linux/macOS, and provide installation instructions for those platforms.
  • Where screenshots or UI steps are shown, note any differences for Linux/macOS users, if applicable.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/deploy-choose-method.md ...n/articles/healthcare-apis/iot/deploy-choose-method.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently mentioning Azure PowerShell before Azure CLI, which is more cross-platform and commonly used on Linux. There are no explicit Linux-specific examples, nor are Linux-native tools or shell patterns (e.g., Bash) referenced. The deployment methods and examples focus on Azure PowerShell and the Azure portal, both of which are traditionally Windows-centric, with no mention of Linux command-line usage or considerations.
Recommendations
  • Provide Linux-specific examples, such as using Bash scripts or native Linux shell commands for deployment.
  • List Azure CLI before Azure PowerShell when describing cross-platform deployment options, or present them in parallel to avoid implicit prioritization.
  • Explicitly state that Azure CLI is fully supported on Linux and macOS, and provide links or guidance for installing and using CLI on those platforms.
  • Include troubleshooting or configuration notes relevant to Linux environments, such as file permissions or environment variables.
  • Add a section or callout highlighting cross-platform support and parity, reassuring users that all deployment methods work on Linux, macOS, and Windows.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/deploy-manual-portal.md ...n/articles/healthcare-apis/iot/deploy-manual-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by mentioning Azure PowerShell before Azure CLI and REST API as deployment options, without providing explicit Linux or cross-platform examples. There are no command-line examples shown, but the language and ordering suggest a preference for Windows-centric tools and workflows. No Linux-specific guidance or parity is provided, and screenshots are all from the Azure portal, which is platform-agnostic but does not address CLI or automation scenarios common in Linux environments.
Recommendations
  • Explicitly provide Azure CLI examples alongside or before PowerShell examples, as CLI is cross-platform and widely used on Linux.
  • Include references to Bash scripting and Linux shell environments when discussing automation or scripting options.
  • Add a section or callout for Linux users, highlighting any platform-specific considerations or best practices.
  • Ensure ordering of tool mentions (CLI, PowerShell, REST API) does not implicitly prioritize Windows tools.
  • Provide sample deployment scripts for both PowerShell and Bash/CLI to demonstrate parity.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/authentication-authorization.md ...ticles/healthcare-apis/authentication-authorization.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning Windows-centric tools (PowerShell, Visual Studio Code REST Client) before cross-platform or Linux-native alternatives. There are no explicit Linux or bash examples, and Windows tools are listed first when suggesting ways to obtain access tokens. The documentation does not provide parity in example commands or tool recommendations for Linux users.
Recommendations
  • Include explicit Linux/bash examples for obtaining access tokens, such as using curl or wget with sample commands.
  • List cross-platform tools (curl, CLI) before Windows-specific tools (PowerShell, Visual Studio Code REST Client) when suggesting options.
  • Provide step-by-step instructions for both Windows (PowerShell) and Linux (bash) environments where relevant.
  • Mention Linux-native editors (e.g., Vim, nano) or IDEs alongside Visual Studio Code.
  • Ensure that all tool recommendations are cross-platform or provide alternatives for both Windows and Linux users.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/convert-data.md ...les/healthcare-apis/azure-api-for-fhir/convert-data.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Azure Portal (GUI) instructions and referencing Azure PowerShell/CLI tools without clarifying Linux compatibility or providing explicit Linux shell examples. The use of Visual Studio Code extensions is also presented without mention of cross-platform alternatives or installation instructions for Linux. There are no Linux-specific command-line examples, nor is there guidance for Linux users on installing required tools or performing equivalent tasks.
Recommendations
  • Add explicit Linux shell (bash) examples for CLI commands, including installation steps for Azure CLI and extension on Linux.
  • Clarify that Azure CLI commands work cross-platform and provide sample commands for both Windows (PowerShell) and Linux (bash).
  • Include instructions for installing and using the FHIR Converter Visual Studio Code extension on Linux and macOS, or mention alternative editors if applicable.
  • Where GUI steps are described (Azure Portal), provide equivalent CLI or scriptable alternatives for users on Linux.
  • Review all tool references (e.g., Template Management CLI, Azure CLI) to ensure Linux compatibility is stated and any platform-specific caveats are documented.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/configure-private-link.md ...care-apis/azure-api-for-fhir/configure-private-link.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing command-line examples and usage patterns that are specific to Windows environments (e.g., nslookup output from a Windows command prompt, RDP instructions), mentioning PowerShell and Azure CLI but not Bash or Linux shell alternatives, and omitting explicit Linux/Unix examples or guidance. The documentation also references RDP for VM access, which is a Windows-centric remote access method, and does not mention SSH or Linux VMs.
Recommendations
  • Include Linux/Unix-specific examples for command-line operations, such as showing nslookup or dig output from a Linux shell.
  • When referencing VM access, mention both RDP (for Windows) and SSH (for Linux) as options.
  • Provide Azure CLI examples using Bash syntax and clarify that CLI commands can be run from any OS.
  • Balance references to PowerShell with equivalent Bash or shell script examples.
  • Explicitly state that the instructions apply to both Windows and Linux environments, and highlight any OS-specific considerations.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/configure-local-rbac.md ...thcare-apis/azure-api-for-fhir/configure-local-rbac.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both PowerShell and Azure CLI examples for creating service principals, but PowerShell is presented first and in more detail. The PowerShell example assumes use of the Az module, which is most commonly used on Windows, and references Visual Studio Code, a tool often associated with Windows workflows. There is no explicit mention of Linux or bash environments, nor are there instructions for running these commands on Linux or macOS. The CLI example uses bash syntax but does not clarify cross-platform compatibility or provide Linux-specific guidance.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit Windows prioritization.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example environments.
  • Add notes or sections for Linux/macOS users, including any prerequisites or differences in command usage.
  • Reference common Linux tools (e.g., terminal, bash) and provide guidance for running scripts in those environments.
  • Avoid assuming Visual Studio Code as the default environment, or clarify its cross-platform availability.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/smart-on-fhir.md ...es/healthcare-apis/azure-api-for-fhir/smart-on-fhir.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell scripts for key steps (e.g., reply URL encoding, dotnet user-secrets), using Windows-centric tooling and patterns, and omitting equivalent Linux/macOS shell commands. All command-line examples use PowerShell syntax, and there are no bash or cross-platform alternatives. The instructions assume familiarity with Windows tools and the Azure Portal, with no mention of CLI or automation options that are more common on Linux.
Recommendations
  • Provide bash/zsh shell script equivalents for all PowerShell examples, especially for reply URL encoding and dotnet user-secrets usage.
  • Explicitly state cross-platform compatibility for .NET SDK and app launcher steps, and provide Linux/macOS installation instructions if needed.
  • Include screenshots or instructions for using Azure CLI for app registration and configuration, not just Azure Portal.
  • Add a section or notes clarifying how users on Linux/macOS can follow each step, including any required package installations or environment setup.
  • Where possible, use generic commands or highlight differences between Windows and Linux/macOS environments.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/quickstart-asynchronous-python.md ...pis/deidentification/quickstart-asynchronous-python.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for Azure CLI commands, explicitly stating PowerShell is used as the terminal of choice, and omitting equivalent Linux/macOS shell (bash) examples for resource setup and management. This may disadvantage users on Linux or macOS platforms, who typically use bash or other POSIX-compliant shells.
Recommendations
  • Provide all Azure CLI command examples in both PowerShell and bash syntax, or use bash as the default for cross-platform parity.
  • Avoid stating a Windows-specific shell as the default; instead, mention that users can use their preferred terminal (PowerShell, bash, etc.).
  • Add explicit instructions for Linux/macOS users, including any differences in environment setup, variable assignment, and command usage.
  • Where possible, use shell-agnostic Azure CLI commands and avoid PowerShell-specific variable assignment and command substitution patterns.
  • Include a note or section on platform compatibility, clarifying that the service and SDK are usable from Windows, Linux, and macOS.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/register-resource-azure-ad-client-app.md ...-api-for-fhir/register-resource-azure-ad-client-app.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation page demonstrates Windows bias by presenting PowerShell as the primary method for registering a resource application in Microsoft Entra ID, with the PowerShell example shown before the Azure CLI example. The use of PowerShell and references to Azure PowerShell tools suggest a preference for Windows environments. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or considerations.
Recommendations
  • Provide bash shell examples for Linux users alongside PowerShell and Azure CLI examples.
  • Explicitly mention that Azure CLI works cross-platform and can be used on Linux, macOS, and Windows.
  • Reorder examples so that cross-platform tools (like Azure CLI) are presented before Windows-specific tools (like PowerShell).
  • Add a note or section highlighting Linux compatibility and any platform-specific considerations.
  • Avoid implying PowerShell is the default or preferred method unless there is a technical reason.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/quickstart-bicep.md ...s/healthcare-apis/deidentification/quickstart-bicep.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting Azure PowerShell examples alongside Azure CLI, referencing PowerShell requirements in prerequisites, and listing PowerShell as a primary deployment method. There is an implicit prioritization of Windows tooling (PowerShell) and no mention of Linux-specific considerations or alternative shells. The examples and instructions assume familiarity with PowerShell, which is native to Windows, and do not address Linux users' needs or provide parity for Linux environments.
Recommendations
  • Explicitly mention Linux compatibility and provide instructions for Linux environments, such as shell differences and installation steps.
  • Include Bash-specific examples or notes for Linux/macOS users, especially where file paths or command syntax may differ.
  • Clarify that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
  • Avoid listing PowerShell requirements before CLI requirements, or group them together neutrally.
  • Add troubleshooting or environment preparation notes for Linux users (e.g., installing Azure CLI on Ubuntu, handling file permissions).
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicom-register-application.md ...es/healthcare-apis/dicom/dicom-register-application.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation shows Windows bias by exclusively mentioning PowerShell and the 'New-SelfSignedCertificate' command for creating self-signed certificates, with no reference to Linux or cross-platform alternatives (such as OpenSSL). There are no Linux-specific instructions or examples, and Windows tooling is presented as the default approach.
Recommendations
  • Include Linux and cross-platform instructions for creating self-signed certificates, such as using OpenSSL.
  • Provide examples for both Windows (PowerShell) and Linux/macOS (bash/terminal) where command-line steps are required.
  • Explicitly mention that certificate creation can be performed on non-Windows platforms and link to relevant guides.
  • Avoid presenting Windows tools as the sole or default option; offer parity in tooling and examples.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/configure-storage.md .../healthcare-apis/deidentification/configure-storage.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 for all Azure CLI commands and variables, and explicitly states that PowerShell is being used as the terminal of choice. There are no Bash or Linux shell examples, and variable assignment and command usage are tailored to Windows/PowerShell users. This creates a bias toward Windows environments and may hinder Linux or macOS users.
Recommendations
  • Provide parallel Bash/Linux shell examples for all Azure CLI commands, including variable assignment and command execution.
  • Avoid stating a preference for PowerShell; instead, mention that the tutorial works in any terminal and provide both PowerShell and Bash syntax where they differ.
  • Explicitly note any differences in command usage or variable handling between PowerShell and Bash.
  • Include a section or callout for macOS/Linux users to ensure inclusivity and parity.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/manage-access-rbac.md ...healthcare-apis/deidentification/manage-access-rbac.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell (a Windows-centric tool) before Azure CLI, providing detailed PowerShell examples and output, and referencing PowerShell-specific commands and patterns. The CLI example is present, but PowerShell is given prominence and more explanation. There is no mention of Linux-specific shell usage, and the CLI tab does not clarify cross-platform compatibility or provide Linux-oriented context.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more widely used on Linux.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell syntax for Bash (e.g., export variables, use single quotes for parameters).
  • Balance the level of detail between PowerShell and CLI examples, including sample output for CLI.
  • Explicitly mention that PowerShell is primarily used on Windows, while CLI is recommended for Linux/macOS users.
  • Add a note or tab for Linux-specific considerations, such as authentication methods or environment setup.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicom-configure-azure-rbac.md ...es/healthcare-apis/dicom/dicom-configure-azure-rbac.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell for creating custom roles, without mentioning cross-platform alternatives such as Azure CLI or REST API. No Linux-specific or platform-neutral examples are provided, and the only automation tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Include equivalent instructions and examples for Azure CLI, which is cross-platform and widely used on Linux.
  • Mention REST API options for role assignment and custom role creation, providing links or examples.
  • Add a note clarifying that PowerShell is available on Linux and macOS, but also provide CLI commands for parity.
  • Ensure screenshots and UI instructions are platform-neutral or clarify any platform-specific differences.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/configure-import-data.md ...articles/healthcare-apis/fhir/configure-import-data.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by exclusively providing PowerShell commands for configuring Azure Storage networking and installing modules, without offering equivalent examples for Linux environments (e.g., Bash/CLI). Windows tools and patterns (PowerShell, PsGallery) are mentioned without reference to cross-platform alternatives, and the command-line instructions are presented as the primary method, implicitly prioritizing Windows users. No Linux shell or Azure CLI examples are provided, and there is no guidance for users on non-Windows platforms.
Recommendations
  • Provide Azure CLI (az) command examples alongside PowerShell for all configuration steps, especially for storage account networking and role assignments.
  • Include Bash shell instructions for installing Azure CLI and running relevant commands on Linux/macOS.
  • Explicitly state that all operations can be performed from Linux/macOS as well as Windows, and link to cross-platform tool documentation.
  • Add a note or section for Linux/macOS users, highlighting any differences or considerations.
  • Avoid presenting PowerShell as the only or default method; offer parity in example ordering and detail for both Windows and Linux environments.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/azure-ad-b2c-setup.md ...in/articles/healthcare-apis/fhir/azure-ad-b2c-setup.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides deployment instructions using PowerShell and Azure CLI, with explicit mention of running PowerShell locally in Visual Studio Codeβ€”a pattern most common on Windows. PowerShell examples are presented first in each code tab, and there is no mention of Linux-specific shell environments or considerations. While Azure CLI is cross-platform, the lack of explicit Linux/macOS guidance or examples (e.g., bash scripts, Linux-specific troubleshooting, or environment setup) suggests a Windows-centric bias. Additionally, screenshots and UI instructions are based on the Azure Portal, which is platform-agnostic, but the scripting and automation focus leans toward Windows.
Recommendations
  • Add explicit instructions for running Azure CLI and scripts on Linux/macOS, including any required environment setup (e.g., bash, zsh).
  • Provide bash script examples where appropriate, and clarify that Azure CLI commands work natively on Linux/macOS.
  • Mention alternative editors (such as VS Code on Linux/macOS, or other terminal environments) when suggesting where to run scripts.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., authentication, file permissions, environment variables).
  • When presenting code tabs, alternate the order or clarify parity between PowerShell and CLI, and avoid suggesting PowerShell as the default unless necessary.
GitHub Create Pull Request
← Previous Page 4 of 13 Next →