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 51-75 of 302 flagged pages
Healthcare Apis Choose a deployment method for the MedTech service - Azure Health Data Services ...n/articles/healthcare-apis/iot/deploy-choose-method.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by consistently mentioning Azure PowerShell before Azure CLI, which is more cross-platform and Linux-friendly. There are no explicit Linux shell (bash) examples, and PowerShellβ€”a Windows-centric toolβ€”is presented as a primary automation method. The page does not reference Linux-specific deployment tools or patterns, nor does it provide parity for Linux users in terms of example commands or workflows.
Recommendations
  • Present Azure CLI before Azure PowerShell in lists and examples, as CLI is cross-platform and widely used on Linux.
  • Include explicit bash shell examples for ARM template and Bicep deployments, demonstrating Linux command-line usage.
  • Add notes or sections highlighting Linux compatibility and best practices for deployment.
  • Reference Linux-native tools (e.g., curl, wget, jq) where appropriate for automation.
  • Ensure that all example links and walkthroughs provide both PowerShell and bash/CLI instructions.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively mentioning PowerShell and the 'New-SelfSignedCertificate' command for creating self-signed certificates, without referencing Linux or cross-platform alternatives. No Linux command-line examples (e.g., OpenSSL) are provided for certificate creation, and the only tool mentioned for this task is Windows-specific. Other steps are platform-neutral, but the certificate section is notably Windows-centric.
Recommendations
  • Include Linux and cross-platform instructions for creating self-signed certificates, such as using OpenSSL.
  • Provide example commands for both Windows (PowerShell) and Linux/macOS (bash/OpenSSL) when discussing certificate creation.
  • Explicitly mention that certificate creation can be performed on any OS and link to relevant documentation for Linux/macOS users.
  • Review other sections for subtle platform assumptions and ensure parity in tool recommendations.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page shows evidence of Windows bias in the section 'Deploy and configure Azure Health Data Services using scripts', where PowerShell is mentioned first and exclusively, with no explicit mention of Bash or Linux shell equivalents. While Azure CLI and ARM templates are referenced, the scripting focus is on PowerShell, which is traditionally a Windows tool. There are no Linux-specific examples or instructions, and no mention of Linux tools or shell scripts for deployment and configuration.
Recommendations
  • Provide Bash or Linux shell script examples alongside PowerShell scripts for deployment and configuration tasks.
  • Explicitly mention Linux compatibility for CLI and ARM template instructions.
  • Ensure that all scripting and automation instructions are cross-platform, and clarify any platform-specific requirements or limitations.
  • Include links to Linux-specific documentation or guides where relevant.
  • List CLI and Bash examples before or alongside PowerShell to avoid 'windows_first' ordering.
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-09 00:34
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 presenting PowerShell instructions and examples before Azure CLI, which is more commonly used on Linux and macOS. The PowerShell example is more detailed, including output formatting, while the CLI example is less emphasized. References to 'Azure PowerShell' and the use of Windows-centric tools and patterns are more prominent than Linux equivalents.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux users.
  • Ensure CLI and PowerShell examples are equally detailed, including sample outputs for both.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide installation links for those platforms.
  • Add notes or tabs for Bash scripting or automation on Linux, where relevant.
  • Avoid language that implies PowerShell is the default or preferred method.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/get-started-with-fhir.md ...articles/healthcare-apis/fhir/get-started-with-fhir.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 πŸ”§ Windows Tools
Summary
The documentation frequently lists PowerShell as a primary method for performing tasks, often mentioning it before Azure CLI or REST API. There is a consistent pattern of referencing PowerShell and Windows-centric tools (e.g., Power BI) without providing explicit Linux-specific examples or alternatives. While cURL and REST Client are mentioned, the overall flow and examples favor Windows environments and tooling.
Recommendations
  • Ensure that Azure CLI examples are provided and prioritized equally or before PowerShell, as Azure CLI is cross-platform.
  • Include explicit Linux shell (bash) examples for common tasks, such as obtaining access tokens and performing CRUD operations.
  • Mention and provide examples for Linux-friendly tools (e.g., jq, wget) where applicable.
  • Add guidance for using FHIR data with open-source analytics tools (e.g., Jupyter, Apache Superset) alongside Power BI.
  • Clarify that all steps can be performed on Linux and macOS, not just Windows, and link to platform-specific instructions where needed.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/known-issues.md ...ocs/blob/main/articles/healthcare-apis/known-issues.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 Missing Linux Example Windows First
Summary
The documentation page provides a workaround for configuring the storage account for FHIR export using only PowerShell commands and Az PowerShell module, which are primarily Windows-centric tools. There are no equivalent examples or instructions for Linux users (e.g., using Azure CLI or Bash), and Windows/PowerShell tooling is presented as the default or only option.
Recommendations
  • Add equivalent Azure CLI (az) commands for configuring the storage account for export, which work natively on Linux and macOS.
  • Include Bash script examples alongside PowerShell to ensure parity for Linux users.
  • Explicitly mention cross-platform options and clarify which tools are available on Windows, Linux, and macOS.
  • Consider listing Azure CLI instructions before or alongside PowerShell to avoid Windows-first bias.
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-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 providing PowerShell examples first, referencing Visual Studio Code (commonly used on Windows), and omitting explicit Linux shell examples. The Azure CLI example uses Bash syntax but does not clarify Linux compatibility or provide Linux-specific guidance. There is no mention of Linux tools, shell environments, or alternative editors.
Recommendations
  • Provide explicit Linux shell (bash) examples and clarify their compatibility.
  • Include instructions for running Azure CLI commands on Linux and macOS, including prerequisites.
  • Mention alternative editors (e.g., VS Code on Linux, nano, vim) when referencing script validation.
  • Ensure parity by listing both PowerShell and bash examples side-by-side, and avoid presenting Windows tools first.
  • Add notes about differences in environment setup or command usage between Windows and Linux.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning Windows-specific tools (PowerShell, Visual Studio Code REST Client) before cross-platform or Linux-native equivalents, and does not provide explicit Linux or bash examples for obtaining access tokens. The reference to 'sts.windows.net' in token claims further reinforces a Windows-centric perspective. There is no mention of Linux command-line patterns (e.g., bash scripts, curl usage) in example flows, nor are Linux-specific tools or instructions provided.
Recommendations
  • Provide explicit Linux/bash examples for obtaining access tokens, such as using curl or wget.
  • List cross-platform tools (e.g., curl, Azure CLI) before or alongside Windows tools like PowerShell.
  • Include sample commands for both PowerShell and bash to demonstrate parity.
  • Clarify that Visual Studio Code and its REST Client extension are available on Linux and macOS, or suggest alternative Linux-native tools.
  • Add a section or callout for Linux users, highlighting any platform-specific considerations or best practices.
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-09 00:34
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 providing command-line examples and instructions that are specific to Windows environments (e.g., nslookup output from a Windows shell, RDP instructions), mentioning PowerShell before Azure CLI, and omitting explicit Linux or cross-platform command examples. The use of Windows-centric terminology and screenshots further reinforces this bias, while Linux or macOS users are not directly addressed or provided with equivalent guidance.
Recommendations
  • Include Linux/macOS command-line examples alongside Windows examples, especially for tools like nslookup.
  • When referencing command-line tools, present Azure CLI and PowerShell options together, or lead with the more cross-platform Azure CLI.
  • Replace or supplement RDP instructions with SSH-based access instructions for Linux VMs.
  • Add screenshots or terminal output from Linux/macOS environments where relevant.
  • Explicitly mention that the steps apply to both Windows and Linux unless there are platform-specific differences, and call out such differences where they exist.
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-09 00:34
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 app, mentioning it before the Azure CLI alternative. The use of PowerShell and the 'azurepowershell-interactive' code block suggests a preference for Windows tooling. There are no explicit Linux shell or cross-platform examples, and the documentation does not clarify platform compatibility for the steps provided.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and works natively on Linux and macOS.
  • Explicitly state platform compatibility for each method (e.g., 'PowerShell: Windows only', 'Azure CLI: Windows, Linux, macOS').
  • Include bash or shell script examples where relevant, especially for Linux users.
  • Add a note or section for Linux/macOS users, outlining any prerequisites or differences in the registration process.
  • Review and update documentation to ensure equal visibility and support for Linux and cross-platform tools.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation demonstrates a Windows bias by primarily referencing Windows-centric tools and workflows, such as the Azure portal (GUI), Visual Studio Code extension, and Azure PowerShell/CLI commands without explicit Linux shell examples. Instructions for enabling managed identity, assigning roles, and registering ACR servers are shown using the Azure portal and PowerShell/CLI, which are most commonly used on Windows. There are no Linux-specific command-line examples (e.g., bash, curl, jq), nor are there references to Linux-native tools or workflows. The Visual Studio Code extension is highlighted, which is more popular on Windows, and there is no mention of alternative editors or command-line approaches favored by Linux users.
Recommendations
  • Provide equivalent Linux shell (bash) examples for API calls, such as using curl or wget to interact with the $convert-data endpoint.
  • Include instructions for using Azure CLI from a Linux terminal, clarifying cross-platform compatibility and any OS-specific prerequisites.
  • Mention alternative editors (e.g., Vim, Emacs) or command-line tools for template customization, in addition to Visual Studio Code.
  • Explicitly state that all CLI commands work on Linux, macOS, and Windows, and note any differences in installation or usage.
  • Add screenshots or walkthroughs for Linux environments (e.g., Ubuntu) when demonstrating portal or CLI steps.
  • Reference Linux-native authentication and identity management patterns where relevant (e.g., using managed identities from Linux VMs).
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-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 providing PowerShell examples for key operations (including ARM template deployment), listing PowerShell before Azure CLI, and omitting Linux-specific shell examples (e.g., Bash). There are no references to Linux tools or shell scripting, and the deployment instructions assume a Windows/PowerShell environment.
Recommendations
  • Add Bash or shell script examples for ARM template deployment, using Azure CLI on Linux/macOS.
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
  • Include links or references to Linux-specific documentation or troubleshooting guides.
  • Where PowerShell is used, offer equivalent Bash/CLI commands for Linux users.
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-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 providing only PowerShell commands and examples for scripting and application setup, with no equivalent Linux shell (e.g., Bash) examples. The use of PowerShell is assumed for tasks such as reply URL encoding and running .NET applications, and there is no mention of Linux tools or cross-platform alternatives. All command-line instructions are presented in a Windows-centric manner, and there is no guidance for Linux or macOS users.
Recommendations
  • Provide equivalent Bash shell scripts for reply URL encoding and other scripting tasks.
  • Explicitly mention that .NET and git commands are cross-platform, and provide any necessary Linux/macOS installation or usage notes.
  • Add instructions or screenshots for Linux/macOS environments where relevant (e.g., file paths, running the app).
  • Clarify that PowerShell commands can be run on Linux/macOS (if true), or provide alternatives.
  • Include troubleshooting tips for non-Windows environments, such as common permission or environment variable issues.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the exclusive method for creating custom roles, without mentioning cross-platform alternatives such as Azure CLI or REST API. There are no Linux-specific examples or instructions, and the only tool mentioned for advanced role management is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Add instructions and examples for creating custom roles using Azure CLI, which is cross-platform and widely used on Linux.
  • Reference REST API methods for role assignment and management, providing sample requests and responses.
  • Explicitly mention that PowerShell is available on Linux and macOS, or clarify platform requirements for each tool.
  • Ensure that any screenshots or step-by-step guides do not assume a Windows-only environment.
  • Provide parity in tooling recommendations, listing both Windows and Linux-friendly options for all advanced tasks.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using PowerShell syntax for all Azure CLI commands, explicitly stating PowerShell as the terminal of choice, and using PowerShell variable assignment and command substitution patterns. There are no examples or guidance for Linux/macOS users, who would use Bash or other shells.
Recommendations
  • Provide parallel Bash examples for all Azure CLI commands, using Bash variable assignment and command substitution syntax.
  • Avoid stating PowerShell as the default or only terminal; instead, mention that the tutorial works on any platform and show both PowerShell and Bash usage.
  • Add a note clarifying that Azure CLI commands are cross-platform, and provide guidance for users on Linux/macOS.
  • Where possible, use syntax that is compatible across shells, or clearly separate Windows/PowerShell and Linux/Bash sections.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and its prerequisites are included alongside CLI setup. There are no Linux-specific instructions, nor is there mention of Bash scripting, shell environments, or cross-platform nuances. The 'Next steps' section points to a .NET client library, which is most commonly used on Windows. Overall, the page assumes parity between CLI and PowerShell, but PowerShell's inclusion and prominence may signal a Windows bias.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and highlight its use for Linux/macOS users.
  • Add explicit instructions or notes for Linux/macOS environments, such as saving files and running commands in Bash.
  • Consider including Bash script examples or references for automating deployments on Linux.
  • If PowerShell is mentioned, note that PowerShell Core is available cross-platform, or provide links to installation guides for Linux/macOS.
  • Balance 'Next steps' by referencing SDKs/libraries for other languages/platforms (e.g., Python, Java) that are popular on Linux.
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-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 Windows bias by exclusively mentioning PowerShell and its New-SelfSignedCertificate command for creating self-signed certificates, without providing equivalent Linux or cross-platform alternatives. No Linux command-line tools or methods (such as OpenSSL) are referenced, and no examples for Linux environments are given.
Recommendations
  • Include Linux and cross-platform instructions for creating self-signed certificates, such as using OpenSSL.
  • Provide example commands for both Windows (PowerShell) and Linux/macOS (bash/OpenSSL) when discussing certificate creation.
  • Explicitly mention that certificate creation can be performed on any platform and link to relevant documentation for Linux/macOS users.
  • Review other steps for platform-specific assumptions and ensure parity in tool recommendations and examples.
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-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 exclusively using PowerShell for all Azure CLI and resource management commands, and explicitly stating 'we're using PowerShell' in the tutorial. There are no Bash or Linux shell examples for these steps, and the instructions assume a Windows/PowerShell environment throughout. Only the Python SDK usage and a single curl command are presented in a cross-platform way, but all Azure CLI setup, resource creation, and cleanup are PowerShell-centric.
Recommendations
  • Provide equivalent Bash/Linux shell examples alongside PowerShell for all Azure CLI commands.
  • Remove or rephrase statements that imply PowerShell is the default or preferred shell (e.g., 'we're using PowerShell').
  • Add guidance for users on Linux/macOS, including how to set variables and run Azure CLI commands in Bash.
  • Ensure cleanup and resource management steps include both PowerShell and Bash syntax.
  • Consider a table or toggle for users to select their preferred shell environment (PowerShell vs Bash).
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-09 00:34
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 cross-platform alternatives (such as Azure CLI or REST API). No Linux-specific instructions or examples are provided, and the only tool mentioned for advanced configuration is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Include Azure CLI examples for creating custom roles, as CLI is cross-platform and widely used on Linux.
  • Mention REST API methods for role management to provide platform-agnostic options.
  • Clarify that PowerShell is available on Linux and macOS, or provide installation instructions for non-Windows users.
  • Add explicit Linux/macOS command-line examples alongside PowerShell instructions to ensure parity.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell instructions and referencing running scripts in Visual Studio Code locally, which is most commonly used on Windows. While Azure CLI examples are provided (which are cross-platform), the instructions and context often mention PowerShell first and suggest running commands in environments typically associated with Windows. There are no explicit Linux shell examples (e.g., bash scripts), nor is there mention of Linux-specific tooling or workflows. The use of 'Azure Cloud Shell' mitigates some bias, but local execution is described primarily in Windows-centric terms.
Recommendations
  • Provide explicit bash shell examples for Linux users, including variable assignment and script execution.
  • Mention Linux and macOS environments as valid options for running Azure CLI commands, not just Visual Studio Code or PowerShell.
  • Clarify that Azure CLI commands can be run natively on Linux/macOS terminals, and provide any necessary notes about differences (e.g., environment variable syntax).
  • Include screenshots or references to Linux desktop environments where appropriate.
  • Avoid suggesting PowerShell as the default local scripting environment; present both PowerShell and bash options equally.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/azure-entra-external-id-setup.md .../healthcare-apis/fhir/azure-entra-external-id-setup.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 consistently presenting PowerShell examples and instructions for deploying resources, with explicit references to running scripts in PowerShell locally using Visual Studio Code. While Azure CLI examples are provided (which are cross-platform), PowerShell is listed first in every code tab, and there are no explicit Linux-specific instructions, troubleshooting, or environment setup notes. There is no mention of Linux shell environments (e.g., bash, zsh), nor any guidance for Linux users regarding prerequisites or alternative tooling. The documentation also references running code in Visual Studio Code locally, which is more common in Windows-centric workflows.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit prioritization of Windows tools.
  • Add explicit instructions and troubleshooting notes for Linux environments, including common shell prerequisites and package installation steps.
  • Mention that Azure CLI is fully supported on Linux and macOS, and provide links to installation guides for those platforms.
  • Include examples of running scripts in bash or zsh, and clarify that Visual Studio Code is available cross-platform.
  • Add a note that all ARM template deployments can be performed from Linux, macOS, or Windows, and highlight any platform-specific considerations.
  • Where screenshots or UI instructions are given, clarify that the Microsoft Entra admin center and Graph Explorer are web-based and OS-agnostic.
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-09 00:34
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 providing PowerShell-based instructions and commands for configuring Azure Storage networking and permissions, without offering equivalent examples for Linux users (e.g., Bash, Azure CLI). The only command-line tooling referenced is PowerShell, which is traditionally associated with Windows environments. There are no Linux or cross-platform alternatives mentioned, and the PowerShell steps are presented as the default approach.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for all PowerShell commands, especially for configuring storage account networking and permissions.
  • Explicitly mention that PowerShell is available cross-platform, but also offer guidance for users who prefer Bash or Azure CLI.
  • Add a section or callout for Linux/macOS users, detailing how to perform the same steps using their preferred tools.
  • Ensure that command-line examples are presented in a platform-neutral way, or offer both Windows and Linux alternatives side-by-side.
  • Reference documentation or quickstarts for Azure CLI and REST API usage, not just PowerShell.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/fhir-service-bicep.md ...in/articles/healthcare-apis/fhir/fhir-service-bicep.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 examples and terminology are presented alongside Azure CLI, but Windows-centric tools (such as Git Bash for Windows) are mentioned first or exclusively. The prerequisites and example sections often reference Windows tools before Linux equivalents, and the CLI tab suggests Git Bash (a Windows solution) for Bash shells, rather than mentioning native Linux/macOS terminals. There is no explicit mention of Linux or macOS environments, nor guidance for those platforms.
Recommendations
  • Explicitly mention native Bash shells on Linux and macOS in the prerequisites, not just Git Bash for Windows.
  • Provide guidance for installing Azure CLI and running commands on Linux/macOS, including links to official installation docs for those platforms.
  • Ensure that examples and instructions are platform-neutral, or provide separate instructions for Linux/macOS where differences exist.
  • Avoid listing Windows tools or patterns first unless there is a clear reason; alternate the order or clarify parity.
  • Add notes or sections addressing common Linux/macOS scenarios, such as using the terminal, file paths, and shell environments.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/configure-export-data.md ...articles/healthcare-apis/fhir/configure-export-data.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively providing PowerShell commands for configuring Azure Storage networking and trusted services. There are no equivalent examples or instructions for Linux users (e.g., Bash, Azure CLI, or REST API). The use of PowerShell and references to installing PowerShell modules further reinforce a Windows-centric approach, with no mention of cross-platform alternatives.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples for all PowerShell commands, especially for configuring storage account network rules.
  • Mention and link to REST API documentation for users who prefer scripting outside of PowerShell.
  • Clarify that PowerShell is available cross-platform, but also highlight and demonstrate Linux-native workflows.
  • Ensure screenshots and UI instructions are not specific to Windows environments, and note any platform differences if relevant.
  • Add a section or callout for Linux/macOS users, outlining steps and tools available on those platforms.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/fhir-service-resource-manager-template.md ...re-apis/fhir/fhir-service-resource-manager-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently presenting PowerShell (a Windows-centric tool) before CLI examples, referencing Windows tools such as Visual Studio Code and Git Bash for Bash shells, and omitting native Linux shell examples. The instructions and tooling recommendations are oriented toward Windows users, with Linux alternatives mentioned only as secondary options or not at all.
Recommendations
  • Present CLI (az) examples before or alongside PowerShell examples to avoid implying Windows is the primary platform.
  • Explicitly mention native Linux shells (e.g., Ubuntu Bash, macOS Terminal) in the prerequisites and instructions, not just Git Bash (which is a Windows workaround).
  • Add guidance for running commands in Linux/macOS environments, including installation steps for Azure CLI on those platforms.
  • Avoid language that assumes Visual Studio Code or PowerShell as the default environment; suggest cross-platform editors and shells.
  • Ensure all code samples use platform-agnostic paths and syntax (e.g., forward slashes for file paths, environment variable usage) or provide platform-specific notes where necessary.
GitHub Create Pull Request
← Previous Page 3 of 13 Next →