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 251-275 of 302 flagged pages
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/configure-customer-managed-keys.md
...althcare-apis/dicom/configure-customer-managed-keys.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses Azure Portal (GUI) and ARM template examples for configuration, with no mention of command-line tools such as Azure CLI, PowerShell, or Bash. While this avoids explicit Windows-only tools, the heavy reliance on GUI workflows and the absence of cross-platform CLI instructions (especially Azure CLI/Bash, which are common on Linux and macOS) results in an implicit Windows bias. The documentation does not provide Linux-friendly automation or scripting options, nor does it acknowledge non-Windows environments.
Recommendations
- Add Azure CLI examples for all major steps (enabling managed identity, assigning roles, updating encryption keys, etc.), as Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are included, ensure equivalent Bash/Azure CLI examples are provided and presented first or side-by-side.
- Explicitly mention that all steps can be performed from any OS using Azure CLI or ARM templates, not just via the Azure Portal.
- Include sample scripts or command snippets for Linux/macOS users to automate the process.
- Review screenshots and instructions to ensure they do not assume a Windows environment (e.g., file paths, UI conventions).
Create Pull Request
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/de-identified-export.md
...thcare-apis/azure-api-for-fhir/de-identified-export.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation references Azure Storage Explorer (a GUI tool most commonly used on Windows) for obtaining the ETag, but does not provide alternative methods (such as CLI or cross-platform tools) for Linux users. No command-line examples (e.g., using Azure CLI, PowerShell, or Bash) are provided for either Windows or Linux, but the only tool mentioned is typically associated with Windows environments.
Recommendations
- Provide cross-platform command-line examples for obtaining the ETag, such as using Azure CLI (az storage blob show ...) or REST API calls, which work on both Windows and Linux.
- Explicitly mention and link to Azure Storage Explorer downloads for all supported platforms (Windows, macOS, Linux) to clarify its availability.
- Include examples of how to perform the export operation using both PowerShell and Bash/Azure CLI to ensure parity.
- Where GUI tools are referenced, always provide equivalent CLI instructions for automation and Linux compatibility.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/azure-active-directory-identity-configuration.md
...-fhir/azure-active-directory-identity-configuration.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation does not provide any OS-specific command-line examples, but it references the Azure CLI for obtaining tokens, which is cross-platform. However, there is a subtle bias in that no Linux- or Unix-specific tools or workflows are mentioned, and there are no explicit examples or guidance for Linux users. The only tool mentioned for token inspection is a Microsoft web tool (jwt.ms), with no mention of common Linux command-line utilities (e.g., jq, curl, openssl) that could be used for similar purposes.
Recommendations
- Provide explicit command-line examples for obtaining and inspecting tokens using cross-platform tools (e.g., Azure CLI, curl, jq) and clarify that Azure CLI works on Linux, macOS, and Windows.
- Include Linux/Unix command-line snippets for decoding JWTs (e.g., using base64, jq, or openssl) alongside the mention of jwt.ms.
- If referencing tools or shortcuts, ensure parity by mentioning both GUI/web and command-line options, and clarify platform compatibility.
- Explicitly state that the workflows and tools described are cross-platform where applicable, to reassure non-Windows users.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/register-service-azure-ad-client-app.md
...e-api-for-fhir/register-service-azure-ad-client-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes the registration process using the Azure portal GUI, which is platform-agnostic, but does not provide any command-line examples (such as Azure CLI or PowerShell). There is no mention of Linux-specific tools or workflows, nor are there any CLI examples that would support cross-platform automation. The absence of CLI instructions can be seen as a subtle Windows bias, as GUI workflows are more commonly associated with Windows environments, while Linux users often prefer or require CLI-based instructions.
Recommendations
- Add Azure CLI examples for registering a service client application, obtaining secrets, and configuring permissions. Ensure these examples are tested on both Windows and Linux.
- If PowerShell examples are added, provide equivalent Bash/Azure CLI commands for Linux/macOS users.
- Explicitly mention that the Azure portal is accessible from any OS, but provide links or sections for command-line alternatives.
- Include a note or section on automating these steps using scripts, with examples for both Windows (PowerShell) and Linux (Bash/Azure CLI).
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/register-public-azure-ad-client-app.md
...re-api-for-fhir/register-public-azure-ad-client-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal UI for application registration and does not provide any command-line examples. There is no mention of cross-platform CLI tools (such as Azure CLI), nor are there any Linux-specific instructions or screenshots. While the portal is technically cross-platform via browser, the lack of CLI or script-based examples (which are especially valued in Linux environments) and the absence of any mention of Linux or non-Windows workflows suggests a subtle Windows-first bias.
Recommendations
- Add Azure CLI examples for registering public client applications, as Azure CLI is cross-platform and widely used on Linux.
- Include PowerShell and Bash script examples side by side where scripting is relevant.
- Explicitly mention that the Azure portal can be accessed from any OS, and provide links or notes for users who prefer CLI or automation.
- Add a section or callout for Linux/macOS users, highlighting any differences or tips for those environments.
- Where screenshots are used, consider including examples from non-Windows browsers or generic browser windows to avoid implicit Windows bias.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently presents Microsoft Graph PowerShell examples before Azure CLI examples in each section, which may suggest a preference for Windows-centric tools. While Azure CLI is cross-platform and included, the PowerShell-first ordering and explicit mention of PowerShell may make Linux/macOS users feel secondary. No Linux-specific shell examples or guidance are provided.
Recommendations
- Alternate the order of examples so that Azure CLI (which is cross-platform) appears before PowerShell in some sections, or present both simultaneously without implied priority.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and consider adding bash/zsh shell context where appropriate.
- Add a brief note at the start clarifying that both PowerShell and Azure CLI are supported on all major platforms, and users can choose whichever is most convenient.
- Where possible, provide examples in native Linux shell syntax (e.g., bash) for common tasks, especially if there are differences in output handling or environment setup.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicomweb-standard-apis-curl.md
...s/healthcare-apis/dicom/dicomweb-standard-apis-curl.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform, using cURL for all API examples, which is available on both Windows and Linux. However, there is a subtle Windows bias in the way file paths are described: the only explicit example for {path-to-dicoms} uses a Windows-style path (C:/dicom-server/docs/dcms), and there is no Linux/Unix-style path example provided. No PowerShell or Windows-specific tools are used, but the absence of Linux path examples may cause confusion for Linux users.
Recommendations
- Provide both Windows and Linux/Unix-style path examples for {path-to-dicoms}, e.g., 'C:/dicom-server/docs/dcms' and '/home/user/dicoms'.
- Explicitly state that cURL commands work on both Windows and Linux, and mention any OS-specific considerations (such as path separators or quoting).
- If referencing file paths or environment variables, show both Windows and Linux/Unix conventions side by side.
- Consider adding a short section or note for Linux/macOS users, clarifying any differences in usage or syntax.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicomweb-standard-apis-python.md
...healthcare-apis/dicom/dicomweb-standard-apis-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes the use of the Azure CLI for authentication and instructs users to 'sign in to Azure from the CLI' without specifying the platform. However, the Azure CLI is cross-platform, but there is no mention of Linux or macOS environments, nor are there any examples or troubleshooting steps specific to those platforms. There are no explicit Windows-only commands or PowerShell scripts, but the lack of Linux/macOS context or examples may cause confusion for non-Windows users.
Recommendations
- Explicitly state that the Azure CLI is cross-platform and provide installation links for Windows, Linux, and macOS.
- Add a note or section describing how to authenticate using the Azure CLI on Linux and macOS, including any differences in environment variables or shell usage.
- Provide troubleshooting tips for common authentication issues on Linux/macOS (e.g., PATH issues, login persistence).
- Where file paths are referenced (e.g., {path to the folder that includes green-square.dcm}), clarify path conventions for both Windows (C:\path\to\folder) and Linux/macOS (/home/user/path/to/folder).
- If referencing the Azure CLI, clarify that commands are to be run in a terminal or shell, and that both Windows Command Prompt, PowerShell, and Unix shells (bash, zsh) are supported.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/register-application-cli-rest.md
...icles/healthcare-apis/register-application-cli-rest.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally cross-platform, using Azure CLI and bash-style variable syntax, which is compatible with Linux and macOS. However, there is a subtle Windows bias: the only editor mentioned is Visual Studio Code, and there is a note about running scripts in PowerShell and needing to adjust variable syntax, which is presented as an afterthought. There are no explicit Linux or macOS instructions, nor are common Linux editors or shells mentioned. The documentation assumes familiarity with bash but does not clarify cross-platform compatibility or provide Linux/macOS-specific guidance.
Recommendations
- Explicitly mention that the CLI and scripts work on Linux, macOS, and Windows, and clarify which shell is assumed (e.g., bash, zsh, PowerShell).
- Provide examples or notes for running the scripts in Linux/macOS shells, including any differences in variable syntax or command usage.
- Mention common Linux/macOS editors (e.g., nano, vim) alongside Visual Studio Code, or refer to 'your preferred editor'.
- If referencing PowerShell, provide equivalent bash/zsh syntax or note any differences.
- Add a section or note confirming that all commands are cross-platform unless otherwise specified.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/azure-active-directory-identity-configuration.md
...-fhir/azure-active-directory-identity-configuration.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation does not provide any OS-specific command-line examples, but it does reference the Azure CLI for obtaining tokens without clarifying cross-platform compatibility or providing Linux-specific context. The only tool mentioned for token inspection is a web-based Microsoft tool (jwt.ms), with no mention of common Linux command-line alternatives. There are no explicit PowerShell or Windows-only commands, but the lack of Linux-specific examples or tool recommendations may disadvantage Linux users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and provide installation/use instructions for Linux users.
- Include Linux-native command-line examples for obtaining and decoding JWT tokens (e.g., using curl and jq).
- Mention open-source, cross-platform tools for JWT inspection (such as jwt-cli or command-line decoding with base64 and jq) alongside web-based tools.
- Ensure that any future command-line examples are provided for both Windows (PowerShell/CMD) and Linux (bash) environments.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicomweb-standard-apis-curl.md
...s/healthcare-apis/dicom/dicomweb-standard-apis-curl.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform by using cURL for all command-line examples, which is available on both Windows and Linux. However, there is a subtle Windows bias in the way file paths are presented: the only example given for {path-to-dicoms} uses a Windows-style path (C:/dicom-server/docs/dcms), and there is no mention or example of a Linux/Unix-style path. No PowerShell or Windows-only tools are used, but the pathing convention may confuse Linux users.
Recommendations
- Provide both Windows and Linux/Unix path examples for {path-to-dicoms}, e.g., 'C:/dicom-server/docs/dcms' and '/home/user/dicoms'.
- Explicitly state that cURL commands work on both Windows and Linux, and mention any OS-specific considerations (such as path separators or quoting).
- Add a note or a table showing the difference in file path syntax between Windows and Linux.
- If referencing file paths or environment variables, show both Windows and Linux conventions side by side.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/de-identified-export.md
...thcare-apis/azure-api-for-fhir/de-identified-export.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references 'Azure storage explorer' as the tool to obtain the Etag, which is a GUI tool primarily available for Windows (though cross-platform, it is most commonly associated with Windows environments). There are no examples or instructions for obtaining the Etag using command-line tools or methods common on Linux, such as Azure CLI or REST API calls. No Linux-specific or cross-platform command-line examples are provided.
Recommendations
- Include instructions and examples for obtaining the Etag using Azure CLI (az storage blob show) and/or REST API, which are cross-platform and commonly used on Linux.
- Explicitly mention that Azure Storage Explorer is available for Windows, macOS, and Linux, if referenced, to avoid the perception of Windows-only tooling.
- Provide both GUI (Storage Explorer) and CLI (Azure CLI/REST API) methods side-by-side for all steps involving Azure Storage operations.
- Ensure that any tool or workflow mentioned is either cross-platform or that alternatives are provided for Linux users.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently presents Microsoft Graph PowerShell examples before Azure CLI examples in each section, which may suggest a preference for Windows/PowerShell workflows. While Azure CLI examples are provided (which are cross-platform), the ordering and emphasis on PowerShell may make Linux/macOS users feel secondary.
Recommendations
- Alternate the order of examples, sometimes presenting Azure CLI first to avoid implicit prioritization of PowerShell.
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS to reassure non-Windows users.
- Consider providing Bash shell examples where relevant, especially for scripting scenarios.
- Add a brief section or note highlighting cross-platform support and recommending tools for each OS.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/register-public-azure-ad-client-app.md
...re-api-for-fhir/register-public-azure-ad-client-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on using the Azure portal (web UI) for app registration and does not provide any command-line examples. There is no mention of cross-platform CLI tools (such as Azure CLI or Microsoft Graph CLI), nor are there any Linux-specific instructions or examples. This can be considered a subtle 'Windows-first' or 'portal-first' bias, as many Windows users are accustomed to using GUIs, while Linux users often prefer or require CLI-based workflows. The lack of CLI examples or references to cross-platform tools may hinder Linux users or those automating deployments.
Recommendations
- Add examples using Azure CLI (az ad app create, az ad app update, etc.) for registering public client applications, which work on both Windows and Linux.
- Include references or links to Microsoft Graph API documentation for programmatic registration, which is platform-agnostic.
- Explicitly mention that the Azure portal is accessible from any OS, but provide parity by showing how to accomplish the same tasks via CLI or scripts.
- If Powershell examples are ever added, ensure equivalent Bash/Azure CLI examples are also included.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/register-service-azure-ad-client-app.md
...e-api-for-fhir/register-service-azure-ad-client-app.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation focuses exclusively on using the Azure portal (a web interface) for registering a service app in Microsoft Entra ID, without providing any command-line examples. There are no references to platform-specific tools, but the absence of CLI or scripting examples (such as Azure CLI, Bash, or PowerShell) means Linux users lack parity, especially since Azure CLI is cross-platform. The 'REST Client' mentioned in 'Next steps' is ambiguous, but if it refers to a Visual Studio Code extension, it is available cross-platform. However, the lack of explicit Linux-friendly instructions or examples is a subtle bias.
Recommendations
- Add Azure CLI examples for registering a service client application, including commands for app registration, secret creation, and permission assignment.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, but provide alternative instructions for users who prefer command-line or automated workflows.
- If referencing REST Client, clarify its cross-platform availability and provide curl or httpie examples for Linux users.
- Ensure that any screenshots or instructions do not assume a particular OS, or supplement them with CLI/script equivalents.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/quickstart-bicep.md
...s/healthcare-apis/deidentification/quickstart-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, Azure PowerShell is featured equally alongside Azure CLI, and PowerShell is a Windows-centric tool. There is no mention of Bash or Linux-specific shell environments, and the prerequisites include both Azure CLI and Azure PowerShell setup instructions, potentially giving the impression that PowerShell is required or preferred. No explicit Linux tools or patterns are referenced.
Recommendations
- Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and can be run in Bash or other shells.
- Add explicit Bash shell examples or notes for Linux/macOS users, especially for common tasks like file saving or environment setup.
- Rephrase prerequisites to indicate that Azure CLI is sufficient for all steps and that Azure PowerShell is optional, primarily for users who prefer it.
- Consider adding a section or callout for Linux/macOS users, highlighting any differences or confirming parity.
- Avoid implying that PowerShell is required by listing Azure CLI (cross-platform) first and PowerShell as an alternative.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/configure-customer-managed-keys.md
...althcare-apis/dicom/configure-customer-managed-keys.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively provides instructions using the Azure Portal GUI and ARM templates, with no command-line examples (such as Azure CLI, PowerShell, or Bash). While this avoids explicit Windows-only tools, the absence of any Linux-oriented or cross-platform command-line instructions (e.g., Azure CLI commands) means users on Linux or macOS lack parity. The GUI focus implicitly favors Windows users, as the Azure Portal experience is often associated with Windows environments, and no mention is made of Linux shell or automation options.
Recommendations
- Add Azure CLI examples for all major steps (enabling managed identity, assigning roles, updating encryption keys), as Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are added, ensure Azure CLI or Bash equivalents are also present and shown first or side-by-side.
- Explicitly mention that all steps can be performed from any OS using the Azure CLI or REST API, and provide links or code snippets.
- Include a section or callout for automation and scripting, highlighting cross-platform tools and patterns.
- Review screenshots and instructions to ensure they do not assume a Windows-centric workflow or terminology.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicomweb-standard-apis-c-sharp.md
...ealthcare-apis/dicom/dicomweb-standard-apis-c-sharp.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides C# code samples that use Windows-style file paths (e.g., backslashes in file paths and @"{Path To file}" syntax), and does not mention or provide any Linux/Unix-specific guidance or examples. There are no references to Linux tools, file path conventions, or cross-platform considerations, which may cause confusion or extra effort for Linux users.
Recommendations
- Provide examples of file paths using both Windows (e.g., C:\path\to\file.dcm) and Linux (e.g., /home/user/file.dcm) conventions.
- Explicitly mention that the code samples are cross-platform if applicable, and note any platform-specific considerations.
- Include a note or section on running the C# code on Linux (e.g., using .NET Core/5+/6+ on Linux) and any dependencies or setup steps required.
- Avoid using only Windows-style path separators (\\) in file save/load examples; show both or use Path.Combine or similar cross-platform APIs.
- If any tools or commands are referenced (such as Azure CLI), ensure that Linux usage is also described or linked.
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 →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides a C# example using the Firefly client API, which is most commonly used on Windows platforms. There are no examples for Linux-friendly tools or languages (such as curl, Python, or bash scripting), nor is there mention of Linux command-line usage or cross-platform approaches. The documentation implicitly assumes a Windows/.NET development environment.
Recommendations
- Add equivalent examples using curl to demonstrate how to set custom HTTP headers from the Linux command line.
- Provide a Python requests example to show how to add custom headers in a cross-platform language.
- Explicitly mention that custom headers can be set from any HTTP client, not just C#/.NET.
- Consider including a table or section listing common ways to set HTTP headers in different environments (Windows, Linux, macOS).
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by mentioning PowerShell explicitly and presenting it before Bash when discussing the integrated terminal in Visual Studio Code. The section 'Run PowerShell or CLI' lists PowerShell first, includes a screenshot of PowerShell, and only generically refers to 'CLI' (with a screenshot) rather than explicitly mentioning Bash, Zsh, or other common Linux shells. No Linux-specific tools or examples are provided, but the main workflow is cross-platform as it relies on VS Code and its REST Client extension.
Recommendations
- Explicitly mention Bash, Zsh, or other Linux shells alongside PowerShell in the 'Run PowerShell or CLI' section.
- Provide a screenshot or example of running the workflow in a Linux terminal (e.g., Bash in VS Code).
- Ensure that references to terminal usage are balanced and not Windows-first; consider listing Bash before or alongside PowerShell.
- If any troubleshooting or command-line steps are included in the future, provide both Windows (PowerShell) and Linux (Bash) command examples.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/deploy-choose-method.md
...n/articles/healthcare-apis/iot/deploy-choose-method.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently lists Azure PowerShell before Azure CLI when describing deployment methods, which subtly prioritizes Windows-centric tooling. There is also a repeated emphasis on Azure PowerShell as a primary automation method, which is more familiar to Windows users, even though Azure CLI is cross-platform and often preferred on Linux. No explicit Linux-only examples or tools are mentioned, and no Linux shell (e.g., Bash) scripting examples are provided.
Recommendations
- List Azure CLI before Azure PowerShell when describing deployment methods, or alternate their order to avoid implicit prioritization.
- Explicitly mention that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Provide example commands for both Azure CLI and Azure PowerShell, or at least clarify that both are equally supported.
- Consider including Bash scripting examples or references for Linux users.
- Add a note or section highlighting Linux compatibility and any Linux-specific considerations for deploying the MedTech service.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/register-application-cli-rest.md
...icles/healthcare-apis/register-application-cli-rest.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally cross-platform, using Azure CLI and bash-style syntax, which is compatible with both Linux and Windows. However, there is a subtle Windows bias: the note about running scripts in Visual Studio Code and PowerShell appears early, and PowerShell-specific advice (adding the $ symbol for variables) is given without any equivalent Linux shell notes. No Linux-specific tools or environments are mentioned, and the only environment-specific advice is for Windows/PowerShell users.
Recommendations
- Include explicit notes or examples for running the scripts in Linux/macOS shells (e.g., bash, zsh), such as variable syntax differences or environment setup.
- Mention that the CLI commands work natively in Linux/macOS terminals, not just in PowerShell or Visual Studio Code.
- Provide a brief section or note on how to adapt the scripts for PowerShell (e.g., variable assignment differences), rather than implying PowerShell is the default.
- Balance environment references by mentioning both Windows and Linux/macOS editors (e.g., Visual Studio Code, GNOME Terminal, Terminal.app) where scripts can be run.
- If referencing Visual Studio Code, clarify that it is cross-platform and not exclusive to Windows.
Healthcare Apis
Quickstart: Deploy Azure API for FHIR using an ARM template
...i-for-fhir/azure-api-fhir-resource-manager-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing PowerShell instructions before CLI, referencing Git Bash (a Windows-centric Bash shell) for CLI prerequisites, and using PowerShell as the primary scripting example. While Linux/macOS users can follow the CLI instructions, the documentation assumes Windows environments in some places and does not mention native Bash shells for Linux/macOS.
Recommendations
- Explicitly mention native Bash shells for Linux/macOS in CLI prerequisites, not just Git Bash for Windows.
- Provide parity in example ordering: alternate or randomize PowerShell and CLI sections, or clarify that both are equally supported.
- Add notes or links for installing Azure CLI and running Bash commands on Linux/macOS.
- Where PowerShell is referenced, clarify that it is available cross-platform, or provide alternative shell instructions if needed.
- Ensure screenshots and instructions do not assume Windows-only environments.
Healthcare Apis
Data conversion for Azure API for FHIR
...les/healthcare-apis/azure-api-for-fhir/convert-data.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by exclusively referencing the Azure portal (a web interface often associated with Windows environments) for configuration steps and showing screenshots from the portal. While CLI examples are provided, there is no mention of Linux/macOS-specific shell commands, nor is there any guidance for Linux users (e.g., using bash, zsh, or alternative tools). The Visual Studio Code extension is cross-platform, but the documentation does not clarify this or provide parity examples for Linux/macOS users. No PowerShell-specific commands are shown, but the overall workflow assumes familiarity with Windows-centric Azure tooling.
Recommendations
- Explicitly mention that the Azure portal and CLI tools are cross-platform and can be used from Linux/macOS as well as Windows.
- Provide Linux/macOS-specific CLI examples, such as bash/zsh commands for installing the Azure CLI and managing ACR.
- Include screenshots or instructions for Linux/macOS environments where appropriate.
- Clarify that the Visual Studio Code extension is available on all major platforms.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, networking).
Healthcare Apis
Find identity object IDs for authentication in Azure API for FHIR
...re-apis/azure-api-for-fhir/find-identity-object-ids.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently presents Microsoft Graph PowerShell examples before Azure CLI examples in each section, which may suggest a preference for Windows/PowerShell environments. However, Azure CLI commands are provided for all tasks, ensuring Linux/macOS users can complete the same actions. No Windows-only tools are required, but the ordering and emphasis may create a perception of Windows bias.
Recommendations
- Alternate the order of examples so that Azure CLI is shown first in some sections, or present both examples side-by-side.
- Explicitly state that both PowerShell and Azure CLI are fully supported on Windows, Linux, and macOS.
- Consider adding a short note at the top clarifying that all commands are cross-platform and that users can choose their preferred tool.
- If possible, include Bash shell examples or clarify that Azure CLI commands work in Bash and other Unix shells.