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 226-250 of 302 flagged pages
Healthcare Apis Get started with the MedTech service - Azure Health Data Services .../blob/main/articles/healthcare-apis/iot/get-started.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions Azure PowerShell, Azure CLI, and REST API as deployment options, but lists PowerShell first and does not provide any explicit Linux-specific examples or guidance. There is no mention of Linux shell commands, nor are there examples for Bash or other Linux-native tooling. The deployment instructions reference the Azure portal and PowerShell, which are more commonly used on Windows, without balancing with Linux equivalents.
Recommendations
  • Provide explicit examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) side-by-side.
  • Mention Azure CLI and REST API before or alongside PowerShell to avoid Windows-first ordering.
  • Include sample commands for resource deployment using Bash/Azure CLI.
  • Clarify that all steps can be performed on Linux, macOS, and Windows, and link to platform-specific guides where available.
  • Add notes about cross-platform compatibility for Azure CLI and REST API usage.
GitHub Create Pull Request
Healthcare Apis Register a resource app in Microsoft Entra ID - Azure API for FHIR ...-api-for-fhir/register-resource-azure-ad-client-app.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example first for registering the resource application, followed by an Azure CLI example. PowerShell is a Windows-centric tool, and its precedence suggests a Windows-first bias. There are no explicit Linux shell or cross-platform examples beyond Azure CLI, and no mention of Linux-specific tools or considerations.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more accessible to Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Include Bash or shell script examples where relevant, especially for steps that might be performed outside Azure CLI.
  • Add a note clarifying platform compatibility for each tool, helping users choose the best option for their environment.
  • Consider referencing Linux-specific authentication or scripting patterns if applicable.
GitHub Create Pull Request
Healthcare Apis Find identity object IDs for authentication in Azure API for FHIR ...re-apis/azure-api-for-fhir/find-identity-object-ids.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation consistently presents Microsoft Graph PowerShell commands as the first example in each section, followed by Azure CLI commands. PowerShell is primarily a Windows-centric tool, and its prominence may disadvantage Linux users. While Azure CLI is cross-platform and included, the ordering and emphasis on PowerShell suggest a Windows-first bias.
Recommendations
  • Alternate the order of examples, sometimes presenting Azure CLI first to avoid implicit prioritization of Windows tools.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and encourage its use for cross-platform scenarios.
  • Consider adding Bash script examples or instructions for Linux environments where appropriate.
  • Clarify that PowerShell Core is available on Linux, if PowerShell examples are retained, and provide installation guidance.
GitHub Create Pull Request
Healthcare Apis Get started with Azure API for FHIR .../azure-api-for-fhir/get-started-with-azure-api-fhir.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by mentioning PowerShell as a deployment option before Azure CLI, and by referencing Windows-centric tools (PowerShell) alongside cross-platform options. There are no explicit Linux examples, nor is there mention of Linux-specific tools or workflows. The ordering and emphasis may lead Linux users to perceive the documentation as Windows-oriented.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform.
  • Explicitly mention that Azure CLI and ARM templates work on Linux, macOS, and Windows.
  • Provide Linux-specific instructions or screenshots where relevant, such as using Bash or terminal commands.
  • Add a note clarifying platform compatibility for all deployment methods.
  • Consider including a section or quickstart for Linux users to reinforce parity.
GitHub Create Pull Request
Healthcare Apis Private link for Azure API for FHIR ...care-apis/azure-api-for-fhir/configure-private-link.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Windows-centric examples and instructions, such as using RDP to access a VM and showing nslookup output from a Windows command prompt. There are no Linux-specific instructions, examples, or screenshots, and Windows tools/patterns (like RDP and C:\Users\ paths) are used exclusively or first. This may make it less accessible for users working primarily in Linux environments.
Recommendations
  • Add Linux-specific instructions and examples, such as how to SSH into a VM and run equivalent tests.
  • Include nslookup output from a Linux shell (e.g., bash) alongside the Windows example.
  • Mention Linux tools and commands (e.g., curl, dig) for testing connectivity to the FHIR server.
  • Clarify that both Windows and Linux VMs are supported and provide parity in troubleshooting steps.
  • When referencing remote access, mention both RDP (Windows) and SSH (Linux) as options.
GitHub Create Pull Request
Healthcare Apis Manage access to the de-identification service with Azure role-based access control (RBAC) in Azure Health Data Services ...healthcare-apis/deidentification/manage-access-rbac.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure PowerShell (a Windows-centric tool) before Azure CLI in the role assignment section, and provides a detailed PowerShell example with output, while the Azure CLI example is less detailed and lacks output. This ordering and depth can signal a bias toward Windows users and PowerShell workflows, even though Azure CLI is cross-platform and preferred by many Linux users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, or give them equal prominence.
  • Provide equally detailed examples and output for Azure CLI, including sample responses.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add guidance or links for using Azure CLI in Bash or other Linux shells.
  • Avoid language that implies PowerShell is the default or preferred method.
GitHub Create Pull Request
Healthcare Apis Access Azure Health Data Services using REST Client ...ain/articles/healthcare-apis/fhir/using-rest-client.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by mentioning PowerShell before Bash when discussing terminal usage in Visual Studio Code. The 'Run PowerShell or CLI' section lists PowerShell first, includes a screenshot of PowerShell, and refers to 'PowerShell or CLI', which may imply PowerShell as the default or preferred option. There are no explicit Linux-specific examples, nor is Bash usage illustrated with screenshots or detailed steps.
Recommendations
  • Present Bash and PowerShell equally, e.g., 'PowerShell or Bash' or 'Bash or PowerShell', and alternate their order in text and screenshots.
  • Include a screenshot of running Bash in Visual Studio Code alongside PowerShell.
  • Provide explicit instructions or examples for Bash usage, especially for Linux/macOS users.
  • Clarify that the REST Client extension and all steps are cross-platform, and highlight any platform-specific considerations if relevant.
  • Avoid implying PowerShell as the default by using neutral language such as 'Open the integrated terminal and select your preferred shell (PowerShell, Bash, etc.)'.
GitHub Create Pull Request
Healthcare Apis Get started with the MedTech service - Azure Health Data Services .../blob/main/articles/healthcare-apis/iot/get-started.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation refers to Azure PowerShell, Azure CLI, and REST API as options for deployment, but lists Azure PowerShell first, which is traditionally associated with Windows environments. There are no explicit examples or instructions for Linux users, and no mention of Linux-specific tools or patterns. The guidance and linked resources focus on Azure portal and PowerShell, which may implicitly favor Windows users.
Recommendations
  • Explicitly provide command-line examples for both Azure CLI and PowerShell, and clarify that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Include Linux-specific instructions or notes where relevant, such as installation steps for Azure CLI on Linux.
  • When listing deployment options, alternate or randomize the order, or mention Azure CLI before PowerShell to avoid implicit Windows-first bias.
  • Add a section or tip for Linux users, highlighting cross-platform compatibility and linking to Linux documentation for Azure tools.
GitHub Create Pull Request
Healthcare Apis Receive device messages through Azure IoT Hub - Azure Health Data Services ...healthcare-apis/iot/device-messages-through-iot-hub.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio Code and the Azure IoT Hub extension for device creation and message sending, without mentioning or providing alternatives for Linux users. There are no command-line examples (e.g., Azure CLI, Bash, or PowerShell) or instructions for Linux-native tools. The workflow assumes use of the Azure Portal and Visual Studio Code, which are most commonly used on Windows, and does not address Linux environments or provide parity in tooling or instructions.
Recommendations
  • Add instructions for using Azure CLI to create devices and send test messages to IoT Hub, which work cross-platform (Windows, Linux, macOS).
  • Provide examples using Bash scripts for device creation and message sending.
  • Mention and link to Linux-compatible tools (e.g., iothub-explorer, Azure CLI, REST API) for interacting with IoT Hub.
  • Clarify that Visual Studio Code and the Azure IoT Hub extension are available on Linux and macOS, and provide installation instructions for those platforms.
  • Include screenshots or terminal output examples from Linux environments.
  • Explicitly state platform compatibility for each tool and step, ensuring Linux users are not excluded.
GitHub Create Pull Request
Healthcare Apis Register a client application in Microsoft Entra ID using CLI and REST API - Azure Health Data Services ...icles/healthcare-apis/register-application-cli-rest.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation shows mild Windows bias by referencing PowerShell and Windows-specific scripting patterns (e.g., variable syntax with $), and by mentioning PowerShell as an environment for running scripts. The note about needing to add $ for variables in PowerShell is Windows-centric. There are no explicit Linux shell examples (e.g., bash, sh), nor are Linux-specific considerations mentioned. All CLI examples use syntax compatible with bash, but the guidance and environment references prioritize Windows/PowerShell.
Recommendations
  • Add explicit examples or notes for running the CLI commands in Linux/macOS environments, including variable syntax differences (e.g., export VAR=val, $VAR usage).
  • Mention bash/zsh as supported environments alongside PowerShell and Visual Studio Code.
  • Clarify that the CLI commands are cross-platform and provide any necessary adjustments for Linux shells (e.g., quoting, environment variables).
  • Include troubleshooting tips or environment setup instructions for Linux users.
  • Avoid referencing Windows/PowerShell-specific patterns before cross-platform alternatives.
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation displays mild Windows bias by recommending Git Bash (from Git for Windows) as the example Bash shell for CLI usage, rather than mentioning native Bash environments on Linux or macOS. This places a Windows-centric tool first and may imply a Windows-first audience. However, the CLI examples themselves are cross-platform and do not use Windows-specific commands. PowerShell is presented as a separate tab, which is appropriate, but the CLI prerequisites and examples could better acknowledge Linux/macOS environments.
Recommendations
  • In the CLI prerequisites, mention native Bash shells available on Linux and macOS before or alongside Git Bash for Windows.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide links or instructions for installing Bash on those platforms.
  • Avoid implying that Bash is primarily a Windows tool by referencing Git Bash first.
  • Consider adding a note that PowerShell is available cross-platform, but that Bash/CLI examples are generally preferred for Linux/macOS users.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/find-identity-object-ids.md ...re-apis/azure-api-for-fhir/find-identity-object-ids.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation consistently presents Microsoft Graph PowerShell examples before Azure CLI examples for all tasks, indicating a Windows-first approach. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux users. However, Azure CLI examples are provided in each case, which helps mitigate but does not eliminate the bias.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more accessible to Linux users.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily Windows-focused (though PowerShell Core is cross-platform, many users associate it with Windows).
  • Add Bash script examples where appropriate, especially for automation scenarios.
  • Include notes or links for installing Azure CLI on Linux systems.
  • Consider removing or de-emphasizing PowerShell examples unless there is a Windows-specific scenario.
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell as a deployment option before CLI and ARM template, and by referencing PowerShell-specific quickstart guides. There are no explicit Linux examples or mentions of Linux-specific tools or patterns, and the documentation does not clarify cross-platform compatibility for command-line instructions.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
  • Provide Linux/macOS-specific examples or screenshots where relevant, especially for command-line operations.
  • Ensure CLI examples are given equal or higher prominence than PowerShell, or present them together.
  • Clarify that ARM templates and Azure portal are platform-agnostic.
  • Add a section or note on how to perform common tasks from Linux/macOS environments, including authentication and deployment.
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio Code and the Azure IoT Hub extension for device creation and message sending, without mentioning or providing examples for equivalent Linux workflows or CLI tools. The tutorial assumes the use of a graphical interface common on Windows, and does not offer parity for Linux users who may prefer command-line tools or alternative editors.
Recommendations
  • Include instructions and examples for using Azure CLI and/or Azure IoT CLI tools (such as az iot hub device-identity and az iot hub device-message) for device creation and message sending, which work cross-platform.
  • Mention and provide examples for using Linux-native editors (such as Vim, Nano, or VS Code on Linux) and clarify that the Azure IoT Hub extension is available on Linux as well.
  • Explicitly state that all steps can be performed on Linux and macOS, and provide screenshots or terminal outputs from those platforms.
  • Add troubleshooting notes or prerequisites for Linux users, such as installation of required dependencies for VS Code extensions or CLI tools.
  • Consider reordering instructions to present cross-platform, command-line methods before or alongside Windows-centric GUI methods.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/using-rest-client.md ...ain/articles/healthcare-apis/fhir/using-rest-client.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by mentioning PowerShell before Bash when discussing terminal usage in Visual Studio Code. The section 'Run PowerShell or CLI' lists PowerShell first, includes a screenshot for PowerShell, and refers to 'PowerShell or CLI' rather than 'Bash or CLI'. There are no explicit Linux-specific examples, and no Linux tools are highlighted. However, the main workflow (using the REST Client extension in VS Code) is cross-platform, and the instructions do not rely on Windows-only tools outside the terminal section.
Recommendations
  • Present Bash and PowerShell examples equally, or mention Bash first to balance representation.
  • Include screenshots for both Bash and PowerShell terminals.
  • Explicitly state that all instructions apply equally to Linux, macOS, and Windows.
  • Where terminal usage is discussed, clarify that Bash is the default on Linux/macOS and PowerShell on Windows.
  • Consider adding a note or section for Linux/macOS users, highlighting any platform-specific considerations.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/get-started.md .../blob/main/articles/healthcare-apis/iot/get-started.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions Azure PowerShell, Azure CLI, and REST API as options for deployment, but lists PowerShell first, which may suggest a Windows-first bias. There are no explicit examples or instructions for Linux users, nor are Linux-specific tools or shell commands referenced. The only deployment example linked is via the Azure portal, which is platform-agnostic, but no command-line examples (for either Windows or Linux) are provided.
Recommendations
  • Provide explicit deployment examples using both Azure CLI (cross-platform) and Azure PowerShell, with clear indications of which commands work on Linux, macOS, and Windows.
  • Ensure that CLI examples are presented before or alongside PowerShell examples to avoid Windows-first ordering.
  • Include notes or sections for Linux users, such as prerequisites for Azure CLI installation on Linux, and troubleshooting tips specific to Linux environments.
  • Reference Linux-compatible tools and workflows where appropriate, and avoid assuming users are on Windows.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/get-started.md .../blob/main/articles/healthcare-apis/iot/get-started.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions Azure PowerShell as a deployment option before Azure CLI and REST API, which are more cross-platform. There are no explicit examples or instructions for Linux users, and no mention of Linux-specific tools or considerations. The guidance is generic but implicitly prioritizes Windows-centric tools and workflows.
Recommendations
  • Provide explicit examples for both Azure CLI and PowerShell, and clarify which commands work on Linux, macOS, and Windows.
  • List Azure CLI before PowerShell when presenting cross-platform options, or present them together with equal prominence.
  • Include notes or links for Linux users regarding installation and usage of Azure CLI and other relevant tools.
  • Add sample deployment scripts for Linux environments, or reference documentation that covers Linux-specific deployment steps.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/find-identity-object-ids.md ...re-apis/azure-api-for-fhir/find-identity-object-ids.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation consistently provides both Microsoft Graph PowerShell and Azure CLI examples for finding identity object IDs. However, PowerShell examples are always listed first, and PowerShell is a Windows-centric tool, which may signal a subtle preference for Windows environments. There is no explicit mention of Linux-specific tools or shell environments, nor guidance for Linux users beyond the Azure CLI, which is cross-platform.
Recommendations
  • Alternate the order of examples so that Azure CLI (cross-platform) is sometimes presented first.
  • Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell usage (e.g., bash).
  • Add a brief section clarifying platform compatibility for each tool, and recommend Azure CLI for Linux users.
  • Consider including examples using bash scripting or other Linux-native tools where relevant.
  • Avoid language or structure that implies PowerShell is the primary or preferred method.
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias by mentioning Windows-specific tools (such as Git Bash included in Git for Windows) as the primary Bash shell example for Azure CLI usage, and by listing PowerShell before CLI in both prerequisites and deployment instructions. There are no explicit Linux examples or references to native Linux environments or shells (e.g., Ubuntu, macOS Terminal, WSL), and the CLI instructions assume Bash but do not clarify cross-platform compatibility or provide Linux-specific guidance.
Recommendations
  • In the CLI prerequisites, mention native Bash shells on Linux and macOS (e.g., 'A Bash shell (such as Ubuntu Terminal, macOS Terminal, or Git Bash for Windows)').
  • Provide explicit instructions or notes for running Azure CLI commands on Linux/macOS, including installation links for those platforms.
  • When listing deployment options (Portal, PowerShell, CLI), alternate the order or clarify that CLI is cross-platform and not Windows-specific.
  • Avoid referencing Windows-specific tools (e.g., Git Bash) as the sole example; include alternatives for Linux and macOS users.
  • Add a note confirming that all CLI commands work natively on Linux and macOS, and provide troubleshooting tips for those environments if needed.
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell as a deployment option before Azure CLI and ARM templates, and by referencing PowerShell-specific quickstart guides. There are no explicit Linux examples, nor is there mention of Linux-specific tools or patterns. The Azure portal (web-based) is platform-neutral, but the ordering and emphasis on PowerShell may suggest a preference for Windows environments.
Recommendations
  • List Azure CLI deployment options before PowerShell, as CLI is cross-platform and widely used on Linux.
  • Explicitly mention that Azure CLI and ARM templates work on Linux, macOS, and Windows.
  • Provide example commands for both PowerShell and Azure CLI side-by-side, or clarify platform compatibility.
  • Include a note or section for Linux users, highlighting any relevant considerations or best practices.
  • Avoid implying PowerShell is the default or preferred method unless justified by technical reasons.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicom-services-conformance-statement.md ...are-apis/dicom/dicom-services-conformance-statement.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy
Summary
The documentation page contains references to 'DICOM PowerShell 3.4 Table CC.2.5-3' in the Worklist Service section, which suggests a Windows-centric tool or documentation source. There are no explicit Linux or cross-platform command-line examples, nor are Linux tools or workflows mentioned. The only example tooling referenced is Postman, which is cross-platform, but the PowerShell reference introduces a Windows bias.
Recommendations
  • Replace references to 'DICOM PowerShell 3.4 Table CC.2.5-3' with the official DICOM standard table, or clarify that the table is not Windows-specific.
  • Provide example requests using curl or other cross-platform command-line tools alongside Postman.
  • Avoid naming tables or resources after Windows-specific tools unless absolutely necessary; use neutral terminology.
  • If scripting examples are added, ensure both PowerShell (Windows) and bash/curl (Linux/macOS) variants are included.
  • Explicitly mention that the API and tooling are platform-agnostic where applicable.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/using-rest-client.md ...ain/articles/healthcare-apis/fhir/using-rest-client.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by mentioning PowerShell before Bash when discussing integrated terminal usage in Visual Studio Code. The section 'Run PowerShell or CLI' lists PowerShell first, includes a PowerShell screenshot, and refers to 'PowerShell or CLI scripts', which may imply PowerShell as the default or preferred option. However, Bash is mentioned and the instructions are generally cross-platform, focusing on VS Code and REST Client, which are available on both Windows and Linux. No explicit Windows-only tools or missing Linux examples are present.
Recommendations
  • Present Bash and PowerShell examples equally, or alternate their order to avoid implying preference.
  • Include explicit mention that all steps work on Linux, macOS, and Windows, and clarify that Bash is available by default on Linux/macOS.
  • Add screenshots showing Bash usage alongside PowerShell to visually reinforce parity.
  • Where 'PowerShell or CLI' is mentioned, clarify that 'CLI' includes Bash, zsh, and other Linux/macOS shells.
  • Consider adding troubleshooting notes relevant to Linux/macOS environments if any platform-specific issues may arise.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/deploy-arm-template.md ...in/articles/healthcare-apis/iot/deploy-arm-template.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes deployment using the Azure portal and the 'Deploy to Azure' button, which is a graphical method most commonly associated with Windows environments. There are no examples or instructions for deploying the ARM template using command-line tools such as Azure CLI, PowerShell, or Bash, nor are there any references to Linux or cross-platform deployment methods. This omission may disadvantage users on Linux or those preferring automation or scripting.
Recommendations
  • Add step-by-step instructions for deploying the ARM template using Azure CLI, which is cross-platform and widely used on Linux.
  • Include examples for PowerShell and Bash, showing how to deploy the template from the command line.
  • Explicitly mention that the Azure portal and ARM templates are accessible from any OS, and clarify cross-platform compatibility.
  • Provide links to documentation for deploying ARM templates using different tools (Azure CLI, PowerShell, REST API) and note their OS support.
  • Consider adding a section comparing deployment methods, highlighting pros and cons for Windows and Linux users.
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio Code and the Azure IoT Hub extension for device creation and message sending, without mentioning or providing alternatives for Linux users. There are no examples or instructions for using Linux-native tools or command-line interfaces (such as Azure CLI, IoT CLI, or direct REST API calls) to perform the same tasks. The workflow assumes the use of a graphical environment typical of Windows, and does not address Linux or cross-platform scenarios.
Recommendations
  • Add instructions and examples for using Azure CLI and/or Azure IoT CLI to create devices and send test messages, which work on both Windows and Linux.
  • Mention and provide examples for using REST API calls to interact with IoT Hub, suitable for any platform.
  • Explicitly state that Visual Studio Code and the Azure IoT Hub extension are available on Linux and macOS, or suggest equivalent Linux-friendly tools.
  • Include screenshots or terminal commands for Linux environments to demonstrate parity.
  • Add a section or callout for Linux users, outlining any platform-specific steps or considerations.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/includes/custom-header-auditlog.md ...les/healthcare-apis/includes/custom-header-auditlog.md
Medium Priority View Details →
Scanned: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation provides a C# client example (commonly associated with Windows environments) and does not include equivalent examples for Linux-prevalent languages or tools (such as curl, Python, or bash). There are no references to Linux command-line tools or cross-platform approaches, and the only code sample is Windows-centric.
Recommendations
  • Add equivalent examples using curl or HTTPie to demonstrate how to set custom headers from a Linux or cross-platform command line.
  • Include sample code in other popular, cross-platform languages such as Python (requests), JavaScript (fetch or axios), or Java.
  • Explicitly mention that the feature is accessible from any platform that can set HTTP headers, not just via the C# client.
  • Ensure that future documentation provides parity between Windows-centric and Linux-centric tools and languages.
GitHub Create Pull Request
← Previous Page 10 of 13 Next →