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 126-150 of 302 flagged pages
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: 2025-07-13 21:37
Reviewed by: Unknown
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 syntax for all Azure CLI and scripting examples, stating 'we're using PowerShell' without providing Bash or Linux shell equivalents. There are no Linux/macOS-specific instructions or examples, and variable assignment and command usage are tailored to PowerShell users. This may hinder accessibility for users on Linux or macOS platforms who use Bash or other shells.
Recommendations
  • Provide parallel Bash/Linux shell examples for all Azure CLI commands and scripting steps, especially for variable assignment and command chaining.
  • Explicitly mention that Azure CLI works cross-platform and that users can use Bash, zsh, or other shells on Linux/macOS.
  • Where PowerShell-specific syntax is used (e.g., variable assignment with $Var = ...), show the Bash equivalent (e.g., VAR=...) side-by-side.
  • In the prerequisites or opening sections, clarify that the tutorial is cross-platform and provide guidance for both Windows (PowerShell) and Linux/macOS (Bash) users.
  • For clean-up and other scripting sections, ensure Bash alternatives are present and tested.
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: 2025-07-13 21:37
Reviewed by: Unknown
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 only PowerShell commands and instructions for configuring Azure Storage networking and permissions. There are no equivalent examples or guidance for Linux or cross-platform tools (such as Azure CLI, Bash, or REST API via curl). The use of PowerShell is presented as the default and only scripting method, and Windows-centric tools are referenced without mention of alternatives.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell examples, especially for installing modules and configuring storage account network rules.
  • Include Bash/curl examples for REST API interactions where applicable.
  • Explicitly mention that PowerShell commands can be run cross-platform (if true), or clarify platform requirements.
  • Present cross-platform or Linux-native instructions alongside or before Windows/PowerShell examples.
  • Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently lists PowerShell as a primary scripting option and often mentions it before Azure CLI or REST API, which can be used cross-platform. There are no explicit Linux/bash examples or references to Linux-specific tools or workflows. The document also highlights Power BI (a Windows-centric tool) for analytics, with no mention of Linux-friendly alternatives. While cURL and REST Client are mentioned, there is a general lack of parity in example scripts or guidance for Linux users.
Recommendations
  • Ensure that all scripting examples are provided in both PowerShell and bash/Azure CLI formats, with equal prominence.
  • When listing scripting options, alternate the order or explicitly state that Azure CLI and REST API are cross-platform.
  • Include Linux-specific guidance or examples, such as using bash scripts, and clarify that cURL and REST Client are available on Linux.
  • For analytics, mention cross-platform tools (such as Jupyter Notebooks, Python/pandas, or open-source BI tools) alongside Power BI.
  • Review linked sample scripts to ensure they include bash/Linux equivalents and are not PowerShell-exclusive.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/github-projects.md .../blob/main/articles/healthcare-apis/github-projects.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page references tools and workflows that are primarily associated with Windows environments, such as PowerShell scripts (.ps1), Visual Studio Code extensions, and Azure Data Factory pipelines, without mentioning or providing equivalent Linux or cross-platform alternatives. There are no explicit Linux or bash examples, and the only script linked is a PowerShell script, suggesting a Windows-first approach.
Recommendations
  • Provide Linux/bash shell script examples or equivalents alongside PowerShell scripts, especially for automation tasks (e.g., creating Synapse external tables).
  • Mention and link to cross-platform tools or clarify when tools (such as VS Code extensions) are available on Linux/macOS as well as Windows.
  • Include references to Linux-native workflows (e.g., using Azure CLI in bash, or running tools in Docker containers) where appropriate.
  • Explicitly state platform compatibility for each tool or script, and provide installation or usage instructions for Linux users.
  • Where Azure Data Factory or other Windows-centric tools are mentioned, suggest or document alternative approaches that are commonly used in Linux environments (e.g., Apache NiFi, custom Python scripts, etc.).
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/concepts-machine-learning.md ...icles/healthcare-apis/iot/concepts-machine-learning.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns (such as Azure SQL Server, Power BI, and Microsoft Teams) without mentioning Linux-compatible alternatives or cross-platform options. There are no command-line or code examples, but the exclusive mention of these Microsoft ecosystem tools and the absence of Linux or open-source equivalents suggest an implicit prioritization of Windows environments.
Recommendations
  • Include references to cross-platform or Linux-friendly alternatives for data repositories (e.g., PostgreSQL, MySQL) and BI tools (e.g., Grafana, Kibana) alongside Azure SQL Server and Power BI.
  • Mention that Azure services (such as Azure Databricks, Azure Functions, and Azure Data Lake) are accessible from both Windows and Linux environments.
  • Provide examples or guidance for integrating with open-source or Linux-based care coordination tools in addition to Microsoft Teams.
  • Explicitly state the cross-platform compatibility of the solution components where applicable.
  • Where possible, add sample workflows or architectural notes for Linux-based deployments or hybrid environments.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation frequently mentions PowerShell and Azure CLI scripts for client application registration and access token retrieval, often listing PowerShell before Azure CLI. It references .NET SDK and C# as access tools, which are more commonly associated with Windows environments. There are no explicit Linux or cross-platform shell (e.g., Bash) examples, nor are Linux-specific tools or workflows highlighted. The documentation lacks parity in presenting Linux-native approaches or examples, and Windows-centric tools are mentioned first or exclusively.
Recommendations
  • Provide explicit Bash or Linux shell examples alongside or before PowerShell examples.
  • Mention Azure CLI as the primary cross-platform tool, and clarify that it works on Linux, macOS, and Windows.
  • Include examples using Linux-native tools (e.g., Bash scripts, curl) for authentication and API access.
  • Balance references to .NET/C# with Python or JavaScript examples, which are more cross-platform.
  • Clearly state that all features and workflows are supported on Linux and macOS, not just Windows.
  • Where screenshots are used, include examples from non-Windows environments when possible.
GitHub Create Pull Request
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing all command-line examples in PowerShell, referencing .NET SDK and dotnet user-secrets (which are more familiar to Windows users), and omitting equivalent Linux/bash commands or guidance. There are no explicit Linux or cross-platform instructions for cloning repositories, running scripts, or setting environment variables, which may hinder Linux users.
Recommendations
  • Provide all command-line examples in both PowerShell and bash (or at least indicate bash equivalents).
  • Explicitly mention that .NET SDK and dotnet user-secrets are cross-platform, and provide Linux/macOS installation and usage notes.
  • When referencing file paths, use platform-neutral or dual examples (e.g., forward and backslashes).
  • Add a section or callout for Linux/macOS users, highlighting any differences in setup or command usage.
  • Where scripts are shown (e.g., for base64 encoding), provide both PowerShell and bash (or Python) versions.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/device-messages-through-iot-hub.md ...healthcare-apis/iot/device-messages-through-iot-hub.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively recommending Visual Studio Code with the Azure IoT Tools extension for device creation and message sending, without mentioning or providing alternatives for Linux users. There are no command-line or cross-platform instructions (such as using Azure CLI, IoT CLI, or Python scripts), and all tooling is presented in a way that assumes a Windows/GUI workflow. No Linux-specific or cross-platform examples or tools are referenced.
Recommendations
  • Include instructions for using Azure CLI or Azure IoT CLI to create devices and send test messages, which work on both Windows and Linux.
  • Provide examples using cross-platform tools such as Python scripts (using the Azure IoT SDK) for device simulation.
  • Explicitly mention that Visual Studio Code and the Azure IoT Tools extension are available on Linux and macOS, or provide alternative workflows for users who prefer not to use a GUI.
  • Add a section or callout for Linux users, outlining the equivalent steps using terminal commands.
  • Ensure screenshots and step-by-step instructions are not solely focused on Windows environments.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/github-projects.md .../blob/main/articles/healthcare-apis/github-projects.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits subtle Windows bias by referencing Windows-centric tools (e.g., PowerShell scripts, SSMS, Power BI) and providing links to PowerShell scripts without mentioning or providing equivalent Linux/bash alternatives. There are no explicit Linux or cross-platform command-line examples, and the analytics tooling and workflow descriptions prioritize or exclusively mention Windows ecosystem tools.
Recommendations
  • Where PowerShell scripts are referenced (e.g., Set-SynapseEnvironment.ps1), provide or link to bash/shell script equivalents or note cross-platform compatibility.
  • When listing analytics tools (e.g., SSMS, Power BI), also mention cross-platform or open-source alternatives (e.g., Azure Data Studio, Jupyter Notebooks, Apache Spark).
  • Explicitly state when tools or scripts are cross-platform, or provide guidance for Linux/macOS users.
  • Include Linux/macOS setup and usage examples alongside Windows ones, especially for CLI tools.
  • Review all tool references to ensure Linux users are not excluded or left without clear guidance.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/azure-api-fhir-resource-manager-template.md ...i-for-fhir/azure-api-fhir-resource-manager-template.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing PowerShell instructions before CLI/Bash, emphasizing Azure PowerShell (a Windows-centric tool), and suggesting Git Bash (from Git for Windows) as the Bash shell example for CLI users. While Linux/Bash usage is supported via the Azure CLI, the documentation's ordering and tool recommendations subtly prioritize Windows environments.
Recommendations
  • Alternate the order of PowerShell and CLI/Bash instructions or present CLI/Bash first to balance platform emphasis.
  • In the prerequisites for CLI, mention native Bash shells on Linux/macOS before or alongside Git Bash for Windows.
  • Explicitly state that all CLI examples work natively on Linux/macOS terminals, not just in Git Bash or Windows environments.
  • Where possible, provide cross-platform notes or highlight any differences in command usage between Windows and Linux/macOS.
  • Consider adding a short section or callout confirming full support for Linux/macOS environments to reassure non-Windows users.
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: 2025-07-12 23:44
Reviewed by: Unknown
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 instructions that are Windows-centric, such as showing nslookup output from a Windows command prompt (C:\Users\testuser>), referencing RDP (Remote Desktop Protocol) to access VMs, and mentioning Azure PowerShell before Azure CLI. There are no explicit Linux or cross-platform command-line examples, and Linux-native access methods (like SSH) are not mentioned. The documentation assumes familiarity with Windows tools and workflows, potentially making it less accessible to Linux users.
Recommendations
  • Provide equivalent Linux command-line examples alongside Windows ones, such as showing nslookup output from a Linux shell (e.g., $ nslookup ...).
  • Mention SSH as an alternative to RDP for accessing VMs, and provide instructions for both.
  • When listing automation options (PowerShell, CLI, ARM templates), avoid listing PowerShell first or highlight CLI as cross-platform.
  • Explicitly state that all steps can be performed from Linux, macOS, or Windows, and link to relevant cross-platform documentation.
  • Include screenshots or terminal outputs from Linux environments where appropriate.
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: 2025-07-12 23:44
Reviewed by: Unknown
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 is described as being tested in Visual Studio Code, which is more common on Windows. There is no explicit mention or example of running these commands on Linux or macOS, nor are there any notes about differences or prerequisites for non-Windows environments. The documentation implicitly assumes a Windows-centric workflow.
Recommendations
  • Provide explicit examples or notes for running Azure CLI commands on Linux/macOS, including any differences in environment variables or shell syntax.
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first, as Azure CLI is cross-platform.
  • Mention that Visual Studio Code and Azure CLI are available on all major platforms, and clarify that the CLI commands work on Linux and macOS.
  • Add a brief section or note about prerequisites or setup for Linux/macOS users, such as installing Azure CLI and using bash/zsh.
  • Where possible, avoid assuming the use of PowerShell or Windows-specific tools unless necessary, and provide parity in instructions for all platforms.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell-based deployment examples and scripts, mentioning PowerShell before or in addition to Azure CLI, and omitting explicit Linux/bash shell examples for ARM template deployment. The CLI example is present, but the only script-based ARM deployment example is in PowerShell, which is Windows-centric. There are no bash or cross-platform shell script examples for Linux/macOS users.
Recommendations
  • Add bash (Linux/macOS) examples for deploying ARM templates using Azure CLI (e.g., az deployment group create) alongside the PowerShell example.
  • When presenting script-based workflows, provide both PowerShell and bash/CLI equivalents, and avoid presenting PowerShell exclusively or first.
  • Explicitly mention that Azure CLI commands are cross-platform and runnable on Windows, Linux, and macOS.
  • Where possible, use neutral language and ordering (e.g., 'Using Azure CLI and PowerShell') or group examples by platform.
  • Consider including a table or section summarizing all supported methods (Portal, PowerShell, CLI, ARM Template via CLI/PowerShell) with links to platform-specific instructions.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/get-started-with-azure-api-fhir.md .../azure-api-for-fhir/get-started-with-azure-api-fhir.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by specifically mentioning PowerShell as a deployment option before the Azure CLI and ARM templates. There are no explicit Linux or cross-platform command-line examples, and the only script-based deployment method called out by name is PowerShell, which is primarily associated with Windows environments. The lack of Linux-specific instructions or examples may make it less approachable for Linux users.
Recommendations
  • Ensure that Azure CLI examples are given equal prominence to PowerShell, as the CLI is cross-platform and widely used on Linux.
  • Where PowerShell is mentioned, also provide Bash or shell script equivalents for Linux users.
  • Explicitly state that the Azure CLI and ARM templates can be used from any platform, including Linux and macOS.
  • If possible, include screenshots or walkthroughs from both Windows and Linux environments.
  • Avoid listing Windows-specific tools (like PowerShell) before cross-platform alternatives unless there is a technical reason.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell as the primary method for registering the resource application, mentioning it before the Azure CLI alternative. The PowerShell example is highlighted first, and the language and structure suggest a preference for Windows-native tools and workflows, with no explicit mention of Linux or cross-platform considerations.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and works natively on Linux and macOS.
  • Explicitly state that both PowerShell and Azure CLI commands can be run on Windows, Linux, and macOS, and provide guidance for users on non-Windows systems.
  • Include a note or section addressing Linux/macOS users, confirming that the Azure CLI example is fully supported and providing any necessary setup instructions.
  • Avoid language that implies PowerShell is the default or preferred approach unless there is a technical reason.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell scripts and commands for key setup steps (e.g., generating reply URLs, cloning and running the app, setting secrets), with no equivalent Bash or Linux shell examples. The use of PowerShell and .NET tooling is assumed throughout, and there is no mention of Linux-specific instructions or cross-platform alternatives. This may hinder Linux users or those working in non-Windows environments.
Recommendations
  • Provide equivalent Bash/Linux shell commands for all PowerShell examples, especially for generating base64-encoded URLs and running .NET applications.
  • Explicitly mention that the .NET SDK and dotnet CLI are cross-platform, and provide any Linux/macOS-specific installation or usage notes.
  • Include instructions for configuring and running the sample app on Linux/macOS, including file path and environment variable differences.
  • Where screenshots or UI steps are shown, clarify if there are any platform-specific differences or confirm cross-platform parity.
  • Consider adding a section or callout for Linux/macOS users to ensure inclusivity and parity in setup and troubleshooting.
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: 2025-07-12 23:44
Reviewed by: Unknown
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 Azure PowerShell as the only scripting/automation method for creating custom roles, without mentioning Azure CLI or Bash alternatives. There are no Linux-specific or cross-platform command-line examples, and the only automation guidance links to a PowerShell-based tutorial. The rest of the instructions are GUI-based, which are platform-neutral but do not provide parity for Linux users who may prefer CLI tools.
Recommendations
  • Add equivalent Azure CLI (az) commands for creating and managing custom roles, alongside the PowerShell example.
  • Reference both Azure PowerShell and Azure CLI documentation when discussing automation or scripting.
  • Include explicit Linux/macOS command-line examples where relevant, especially for automation tasks.
  • Clarify that both PowerShell and Azure CLI are cross-platform, but provide usage examples for each.
  • Consider adding a section or note on how to perform these tasks using Bash or in a Linux environment.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell (a Windows-centric tool) before Azure CLI, and by providing a detailed PowerShell example and output before the CLI example. The PowerShell section is more verbose and includes a sample response, while the CLI section is more concise and lacks output details. There is no mention of Linux-specific considerations or examples, and the PowerShell tool is highlighted first, which may suggest a preference for Windows environments.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to avoid implicit prioritization of Windows tools.
  • Provide equally detailed examples and output for both Azure CLI and PowerShell, including sample responses for CLI commands.
  • Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Add a note or section for Linux/macOS users, clarifying that Azure CLI is the recommended tool for non-Windows environments.
  • Ensure that all instructions and examples are platform-neutral where possible, and avoid assuming the use of Windows-specific tools.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/configure-private-link.md ...ain/articles/healthcare-apis/configure-private-link.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Remote Desktop Protocol (RDP) for VM access, which is a Windows-centric tool. There are no examples or instructions for accessing the VM from Linux (e.g., via SSH), nor are there any Linux command-line examples or references to Linux tools. The documentation assumes the use of the Azure Portal UI and Windows-based access patterns, omitting parity for Linux users.
Recommendations
  • Include instructions for accessing the VM using SSH, which is standard for Linux-based VMs.
  • Provide command-line examples for both Windows (PowerShell/CMD) and Linux (Bash) environments when testing endpoints or configuring network settings.
  • Mention both RDP (for Windows VMs) and SSH (for Linux VMs) as options for connecting to the VM.
  • Add notes or sections that clarify how Linux users can perform equivalent actions, ensuring cross-platform parity.
  • Where screenshots or portal steps are shown, consider including CLI or script-based alternatives that work on both Windows and Linux.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell users. All command-line examples use PowerShell syntax (e.g., variable assignment with $ and $(...)), and the text explicitly states 'we're using PowerShell' without providing equivalent Bash/Linux shell examples. There is no mention of Linux, macOS, or cross-platform shell usage, which may hinder accessibility for non-Windows users.
Recommendations
  • Provide parallel Bash/Linux shell examples for all command-line steps, using standard Bash variable syntax and command substitution.
  • Clarify that Azure CLI is cross-platform and can be used in any shell, not just PowerShell.
  • Avoid language like 'we're using PowerShell' unless alternatives are also presented; instead, state that examples are provided for both PowerShell and Bash.
  • Add a section or callout for macOS/Linux users, ensuring parity in instructions and troubleshooting.
  • Where possible, use shell-agnostic Azure CLI commands without shell-specific variable assignment, or show both approaches.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by referencing the PowerShell-specific 'New-SelfSignedCertificate' command for creating self-signed certificates, without mentioning Linux or cross-platform alternatives. No Linux or macOS command-line examples or tools are provided for certificate creation, and the only tool mentioned for this task is Windows PowerShell.
Recommendations
  • Include Linux/macOS equivalents for certificate creation, such as using 'openssl' to generate self-signed certificates.
  • Provide cross-platform command-line examples or reference platform-agnostic tools where possible.
  • Explicitly mention that 'New-SelfSignedCertificate' is a Windows/PowerShell command and offer alternatives for non-Windows users.
  • Consider adding a table or section summarizing certificate creation options for Windows, Linux, and macOS.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by exclusively referencing Azure PowerShell for creating custom roles, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI, REST API, or ARM templates. No Linux or cross-platform command-line examples are provided, and the only automation tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux.
  • Mention REST API or ARM template options for creating custom roles, with links to relevant documentation.
  • Explicitly state that PowerShell is available on Linux and macOS, or clarify if the instructions are Windows-specific.
  • Add Linux/macOS screenshots or terminal examples where applicable.
  • Ensure that all automation and scripting guidance is presented in a platform-agnostic way, or in parallel for both PowerShell and CLI.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing PowerShell (a Windows-centric tool) before CLI in several sections, referencing Git Bash (a workaround for Bash on Windows) as the example Bash shell, and generally presenting PowerShell examples alongside CLI, rather than giving equal focus to native Linux shells or tools. There is no explicit omission of Linux support, but the ordering and tool references subtly prioritize Windows users.
Recommendations
  • Alternate the order of PowerShell and CLI tabs so that CLI (which is cross-platform and native to Linux/macOS) appears first in some sections.
  • When referencing Bash shells, mention native Linux/macOS terminals before or alongside Git Bash for Windows.
  • Clarify that Azure CLI commands can be run natively on Linux/macOS terminals, not just in Git Bash on Windows.
  • Consider providing a short note about running PowerShell Core on Linux/macOS if PowerShell examples are included.
  • Ensure that all prerequisites and instructions are equally clear for both Windows and Linux/macOS users.
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: 2025-07-12 23:44
Reviewed by: Unknown
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 syntax for all Azure CLI and scripting examples, and explicitly stating that PowerShell is the terminal of choice. There are no equivalent Bash or Linux shell examples, and variable assignment patterns are Windows/PowerShell-specific. This may hinder Linux/macOS users, who typically use Bash or other Unix shells.
Recommendations
  • Provide all Azure CLI examples in both PowerShell and Bash syntax, or use Bash as the default since Azure CLI is cross-platform.
  • Avoid PowerShell-specific variable assignment (e.g., $Variable = ...) in favor of Bash-compatible syntax (e.g., VARIABLE=...).
  • Clarify that the tutorial works on any OS with Azure CLI, and offer guidance for both Windows (PowerShell) and Linux/macOS (Bash) users.
  • Include a note or tabbed code blocks to switch between PowerShell and Bash examples.
  • Ensure clean-up and resource management commands are also shown in Bash.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/events/events-consume-logic-apps.md ...es/healthcare-apis/events/events-consume-logic-apps.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing 'Windows Plan' specifically when choosing a plan type, without mentioning Linux or cross-platform options. There are no command-line examples, but the only plan type explicitly named is Windows. No Linux-specific instructions, screenshots, or parity notes are provided, and there is no mention of Linux hosting or deployment scenarios. The documentation assumes a GUI (Azure Portal) workflow, which is platform-agnostic, but the explicit mention of 'Windows Plan' and absence of Linux alternatives or clarifications creates a subtle bias.
Recommendations
  • When specifying plan types, mention both Windows and Linux hosting options if available, or clarify if only Windows is supported.
  • If Logic Apps can be hosted on Linux (e.g., via Docker containers or App Service Linux plans), provide equivalent instructions or notes.
  • Avoid using 'Windows Plan' as a default term; use 'App Service Plan' or specify both Windows and Linux variants.
  • Add a note or section clarifying platform compatibility for Logic Apps, especially for users deploying from non-Windows environments.
  • If command-line or scripting options are relevant (e.g., Azure CLI, Bicep, ARM templates), provide examples that work cross-platform.
GitHub Create Pull Request
← Previous Page 6 of 13 Next →