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 101-125 of 302 flagged pages
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/configure-export-data.md
...articles/healthcare-apis/fhir/configure-export-data.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands for configuring Azure Storage networking and trusted services. There are no equivalent examples or instructions for Linux users (e.g., Bash/CLI), and the use of PowerShell is presented as the default method for command-line configuration. The documentation also references Windows-centric tools and patterns without mentioning cross-platform alternatives.
Recommendations
- Provide Azure CLI (az) command equivalents for all PowerShell examples, ensuring Linux and macOS users can follow along without needing PowerShell.
- Explicitly mention that PowerShell commands can be run on Linux and macOS, or provide links to instructions for installing PowerShell cross-platform.
- Where UI steps are described, clarify that the Azure Portal is web-based and platform-agnostic.
- Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
- Review all command-line instructions to ensure parity between Windows and Linux environments, and avoid implying that Windows tools are the only or preferred option.
Create Pull Request
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/azure-entra-external-id-setup.md
.../healthcare-apis/fhir/azure-entra-external-id-setup.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently referencing PowerShell and Visual Studio Code as the primary local scripting environment, with instructions to run scripts in PowerShell locally. Although Azure CLI examples are provided (which are cross-platform), explicit instructions for running scripts locally mention PowerShell and Visual Studio Code, both of which are Windows-centric. There is no mention of Linux or macOS environments, nor are there examples or instructions tailored to those platforms. The documentation also omits guidance for Linux-specific shell environments (e.g., bash, zsh) and does not address potential differences in script execution or prerequisites for non-Windows users.
Recommendations
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide instructions for running scripts in native Linux/macOS terminals (e.g., bash, zsh).
- Replace or supplement references to 'PowerShell locally in Visual Studio Code' with 'your preferred terminal or shell environment' and clarify cross-platform compatibility.
- Add notes or sections on prerequisites and setup for Linux/macOS users, such as installing Azure CLI, using bash scripts, and handling authentication.
- Include screenshots or examples from Linux/macOS environments where relevant, to ensure parity and inclusivity.
- Avoid implying that PowerShell is the default or only local scripting environment; present it as one option among several.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/fhir-service-resource-manager-template.md
...re-apis/fhir/fhir-service-resource-manager-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently presenting PowerShell instructions and references before CLI/Bash equivalents, recommending Windows-centric tools (e.g., Git Bash for Windows), and omitting native Linux shell examples. The PowerShell workflow is described in greater detail, and Windows tools are mentioned explicitly, while Linux-native environments and shell usage are not discussed.
Recommendations
- Present CLI/Bash instructions before or alongside PowerShell, not after.
- Include examples for native Linux environments (e.g., Ubuntu, macOS Terminal) rather than referencing Git Bash for Windows.
- Clarify that Azure CLI commands work natively in Linux/macOS terminals, not just in Git Bash.
- Balance the detail level between PowerShell and CLI sections, ensuring both workflows are equally explained.
- Add troubleshooting notes or tips relevant to Linux users (e.g., file path formats, shell differences).
- Avoid language that assumes Windows as the default platform (e.g., 'run the code in PowerShell locally' could be 'run the code in your preferred shell').
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/using-curl.md
.../blob/main/articles/healthcare-apis/fhir/using-curl.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell in prerequisites and examples, referencing Windows-specific tools (PowerShell, Visual Studio Code, Git Bash), and lacking explicit Linux shell examples. The CLI section mentions Bash only as an optional install for Windows, and does not provide native Linux instructions or context. There are no explicit Linux or macOS shell commands or environment setup steps, and PowerShell is presented first throughout.
Recommendations
- Add explicit Linux/macOS prerequisites, such as instructions for using native Bash/Zsh shells.
- Provide example commands for Linux/macOS environments, including shell commands for authentication and token retrieval.
- Present CLI/Bash examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Reference Linux-native tools and patterns (e.g., using native terminal, package managers for cURL installation) in the prerequisites.
- Clarify that cURL and Azure CLI are cross-platform and provide guidance for their use on Linux/macOS.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by providing only PowerShell scripts for key steps (e.g., reply URL encoding), using Windows-centric tools and patterns (dotnet user-secrets, PowerShell), and omitting equivalent Linux/bash examples. All command-line instructions and code snippets assume a Windows environment, with no mention of Linux alternatives or cross-platform considerations. The use of localhost:5001 and dotnet commands is not inherently Windows-only, but the exclusive use of PowerShell and lack of bash or shell script examples reinforces the bias.
Recommendations
- Provide equivalent bash/shell script examples for reply URL encoding and other scripting steps.
- Explicitly mention cross-platform compatibility for .NET and git commands, and clarify any OS-specific instructions.
- Add Linux/macOS setup instructions where environment setup or tooling may differ (e.g., dotnet user-secrets usage, running the app).
- Where PowerShell is used, offer bash alternatives side-by-side, or note that the script can be adapted for Linux/macOS.
- Include screenshots or notes for Linux/macOS users, especially for steps involving local development and file paths.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by repeatedly mentioning PowerShell and Azure CLI as scripting options for client application registration and access token retrieval, without explicitly referencing Bash or Linux shell equivalents. PowerShell is listed before Azure CLI, and there are no Linux-specific examples or guidance. The documentation also references .NET C# as a tool for accessing services, which is more common on Windows. There are no examples or instructions tailored for Linux users, such as Bash scripts or Linux authentication patterns.
Recommendations
- Include explicit Bash/Linux shell examples alongside PowerShell and Azure CLI commands.
- Reference Linux tools and workflows (e.g., curl, jq, Bash scripts) when describing API access and automation.
- List Azure CLI and Bash examples before or alongside PowerShell to avoid Windows-first ordering.
- Provide guidance for Linux authentication and token retrieval, such as using Azure CLI in Bash.
- Mention cross-platform SDKs (e.g., Python, Java) and provide sample code for both Windows and Linux environments.
- Clarify that all steps and tools are cross-platform where applicable, and note any platform-specific limitations.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by consistently presenting PowerShell instructions and references to Windows tools (such as Git Bash for Windows) before or alongside Bash/Azure CLI examples. The prerequisites and deployment steps mention Azure PowerShell and Git Bash (Windows) before general Bash shells, and PowerShell examples are given equal prominence to CLI, which may suggest a Windows-centric approach. There are no explicit Linux-specific instructions or examples, and the CLI instructions do not mention native Linux environments.
Recommendations
- Explicitly mention native Bash shells on Linux/macOS in the prerequisites, not just Git Bash for Windows.
- Provide examples or notes for running Azure CLI commands on Linux/macOS, including installation links for those platforms.
- Consider listing CLI (Bash) instructions before PowerShell to avoid implicit prioritization of Windows tools.
- Add troubleshooting or environment notes for Linux/macOS users where relevant.
- Ensure parity in tool recommendations, e.g., mention that Azure CLI works cross-platform and provide links for all OSes.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation consistently lists PowerShell as a primary method for performing tasks, often before Azure CLI or REST API. Windows-centric tools and patterns (PowerShell, .NET SDK, Power BI) are mentioned throughout, with no explicit Linux-specific examples or guidance. While cURL and REST Client are referenced, there is no parity in showing Linux shell commands or addressing Linux-specific considerations. The documentation implicitly assumes familiarity with Windows tooling and does not provide equal visibility to Linux workflows.
Recommendations
- Provide explicit Linux shell (bash) examples alongside PowerShell, especially for common tasks like authentication and CRUD operations.
- List Azure CLI and REST API methods before or alongside PowerShell to avoid Windows-first ordering.
- Include Linux-specific notes or troubleshooting tips where relevant (e.g., token acquisition, file paths, environment variables).
- Reference cross-platform tools (e.g., Postman, cURL) with example commands for both Windows and Linux.
- Add guidance for using FHIR data with open-source analytics tools (e.g., Jupyter, pandas) in addition to Power BI.
- Ensure that sample scripts and links in the documentation are tested and usable on Linux systems.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/release-notes-2021.md
...ob/main/articles/healthcare-apis/release-notes-2021.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Deploy and configure Azure Health Data Services using scripts' section, where PowerShell is mentioned first and most prominently. While Azure CLI and ARM templates are also referenced, there are no explicit Bash or Linux shell script examples, nor is there mention of Linux-specific deployment patterns or tools. The overall documentation does not provide parity for Linux users in terms of scripting or operational guidance.
Recommendations
- Include explicit Bash and Linux shell script examples alongside PowerShell scripts for deployment and configuration tasks.
- Mention Linux tools (such as bash, curl, jq) and provide equivalent instructions for common operations.
- Present Azure CLI examples before or alongside PowerShell to avoid Windows-first ordering.
- Add notes or sections clarifying cross-platform compatibility and any OS-specific considerations.
- Ensure that all referenced scripts and templates are tested and documented for both Windows and Linux environments.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/known-issues.md
...ocs/blob/main/articles/healthcare-apis/known-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page provides a workaround for configuring the storage account for FHIR export using only PowerShell commands and the Az PowerShell module, which are Windows-centric tools. There are no equivalent examples or instructions for Linux users (e.g., using Azure CLI or Bash), and Windows tooling is mentioned exclusively and first. This creates a bias towards Windows users and may hinder Linux users from easily following the workaround.
Recommendations
- Provide equivalent Azure CLI (az) commands for configuring the storage account, which work natively on Linux, macOS, and Windows.
- Include Bash script examples alongside PowerShell, or offer cross-platform instructions.
- Explicitly state that the workaround can be performed on Linux and macOS, and link to relevant cross-platform Azure documentation.
- Review other workarounds and examples to ensure Linux parity and avoid Windows-first presentation.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/register-application.md
.../main/articles/healthcare-apis/register-application.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Certificates & secrets' section, where it recommends using PowerShell and the New-SelfSignedCertificate command to create self-signed certificates, without mentioning Linux or cross-platform alternatives. No Linux-specific tools or commands are provided, and no parity is offered for certificate creation on non-Windows systems.
Recommendations
- Include Linux and cross-platform alternatives for certificate creation, such as using OpenSSL (e.g., 'openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365') alongside the PowerShell example.
- Explicitly state that certificate creation can be performed on any OS and provide guidance for macOS and Linux users.
- Where Windows-specific tools are mentioned, add equivalent instructions or references for Linux/macOS users.
- Review other sections for implicit Windows-first assumptions and ensure parity in tool recommendations and examples.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/workspace-overview.md
...ob/main/articles/healthcare-apis/workspace-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning PowerShell as a deployment option before CLI, Terraform, and .NET SDK, and by not providing any Linux-specific examples or guidance. The use of 'PowerShell' as the first listed tool and the absence of explicit Linux shell or bash examples suggest a preference for Windows tooling and patterns. There are no examples or instructions tailored for Linux users, nor is there mention of Linux-specific considerations.
Recommendations
- Provide explicit bash or Azure CLI examples for Linux users alongside PowerShell examples.
- List deployment tools in a neutral or alphabetical order (e.g., CLI, PowerShell, Terraform, .NET SDK) to avoid implicit prioritization.
- Include notes or sections addressing Linux-specific setup or usage patterns, such as using Azure CLI on Linux.
- Ensure screenshots and walkthroughs are platform-agnostic or include both Windows and Linux variants.
- Mention cross-platform compatibility for all tools and scripts, clarifying usage on Linux, macOS, and Windows.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows and Microsoft-centric tools and workflows. It exclusively references Microsoft Azure services, Power BI, Azure SQL Server, and Microsoft Teams, all of which are more commonly associated with Windows environments. There are no examples, mentions, or guidance for Linux-based tools, open-source alternatives, or cross-platform workflows. The data repository and visualization tools are described in terms of their native integration with Microsoft products, with no mention of Linux-compatible or open-source equivalents.
Recommendations
- Include examples or references to Linux-compatible tools for data storage (e.g., PostgreSQL, MySQL) and visualization (e.g., Grafana, Kibana) alongside Azure SQL Server and Power BI.
- Mention cross-platform alternatives for care coordination and dashboards, such as open-source messaging or dashboarding tools.
- Clarify that Azure services can be accessed and managed from Linux environments, and provide CLI or REST API examples that are platform-agnostic.
- Add notes or links to documentation for deploying and managing these services from Linux or macOS, not just Windows.
- Balance the order of tool mentions, e.g., list open-source or cross-platform options before or alongside Microsoft-specific ones.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/quickstart-bicep.md
...s/healthcare-apis/deidentification/quickstart-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, it consistently presents Azure PowerShell (a Windows-centric tool) as an equal alternative to Azure CLI, and includes PowerShell prerequisites and instructions. There is no mention of Linux-specific considerations, nor are there examples for Bash scripting or other Linux-native tools. The structure and language assume parity between CLI and PowerShell, which may unintentionally prioritize Windows users or workflows.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows (unless using PowerShell Core).
- Add explicit Bash shell examples or notes for Linux/macOS users, especially for file operations (e.g., saving the Bicep file).
- Reorder sections to present Azure CLI examples before PowerShell, or clarify that CLI is the default for non-Windows environments.
- Include a note or section on running these commands on Linux/macOS, including any differences in prerequisites or environment setup.
- Remove or de-emphasize PowerShell prerequisites for users not on Windows, or provide equivalent Linux/macOS setup instructions.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell for creating custom roles, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI or ARM templates. There are no Linux or cross-platform command-line examples, and the only automation tool mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Include Azure CLI examples for creating custom roles, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Mention and link to documentation for creating custom roles using ARM templates or the Azure Portal, which are platform-agnostic.
- When referencing PowerShell, clarify that it is available cross-platform, but also provide equivalent instructions for non-Windows users.
- Add a section or note highlighting cross-platform tools and approaches for managing Azure RBAC, ensuring Linux users are equally supported.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing the PowerShell command 'New-SelfSignedCertificate' 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 explicit command-line tool mentioned is Windows-specific.
Recommendations
- Provide equivalent Linux/macOS instructions for creating self-signed certificates, such as using 'openssl' (e.g., 'openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes').
- Mention cross-platform tools or approaches (e.g., Azure CLI, OpenSSL) alongside Windows tools.
- Where PowerShell is referenced, clarify if it is available cross-platform, or provide alternative shell commands.
- Add explicit Linux/macOS screenshots or terminal examples where relevant, or at least mention that the steps are applicable across platforms.
- Review for other Windows-centric terminology and ensure parity in tool and workflow recommendations.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/get-healthcare-apis-access-token-cli.md
...e-api-for-fhir/get-healthcare-apis-access-token-cli.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation uses variable assignment syntax ($token=...) that is specific to PowerShell or Windows Command Prompt, without providing equivalent examples for Bash or Linux shells. This may confuse Linux/macOS users, as the syntax is not portable. The documentation implicitly assumes a Windows environment, omitting Linux-specific guidance or examples.
Recommendations
- Provide both PowerShell/Windows and Bash/Linux command examples for variable assignment and usage.
- Explicitly mention which shell the example is intended for, and offer alternatives for other platforms.
- Add a note clarifying that the Azure CLI works cross-platform, and show how to adapt the commands for different environments.
- Consider using syntax highlighting or code block labels (e.g., 'bash', 'powershell') to distinguish between examples.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation references PowerShell as a deployment method before mentioning the Azure CLI, and links to a PowerShell-specific quickstart. There are no explicit Linux or Bash examples, and the ordering of deployment options places Windows-centric tools first. No Linux-specific tools or patterns are mentioned, and there is no guidance for Linux users.
Recommendations
- Provide Linux/Bash examples alongside or before PowerShell examples when describing deployment options.
- Explicitly mention that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash).
- Reorder deployment options to avoid Windows-first bias, e.g., list Azure CLI before PowerShell or present them in parallel.
- Include screenshots or instructions relevant to Linux environments where applicable.
- Add a note clarifying that all deployment methods are available on both Windows and Linux, and link to platform-specific guidance if available.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates bias towards Windows by exclusively referencing Azure PowerShell for creating custom roles, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI or REST API. There are no Linux or cross-platform command-line examples, and the only automation tool mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Include Azure CLI examples for creating custom roles, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Mention REST API options for custom role creation to provide a platform-agnostic approach.
- If PowerShell is referenced, clarify that it is available cross-platform, or provide equivalent Bash or CLI commands.
- Add explicit Linux/macOS instructions or notes to ensure parity and inclusivity for non-Windows users.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a mild Windows bias by referencing the PowerShell command 'New-SelfSignedCertificate' as the tool 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-specific guidance is Windows-centric.
Recommendations
- Include equivalent Linux/macOS commands for generating self-signed certificates, such as using 'openssl'.
- Explicitly mention that 'New-SelfSignedCertificate' is a Windows PowerShell command and provide cross-platform alternatives.
- Add a note or section for non-Windows users, outlining steps to create and export certificates using common Linux/macOS tools.
- Wherever possible, use platform-agnostic language and tools, or provide parallel instructions for each major OS.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both PowerShell and Azure CLI examples for creating a service principal, but the PowerShell example is presented first and is described as being tested in Visual Studio Code, which is more commonly associated with Windows environments. There is no explicit mention of Linux or macOS compatibility, nor are there any bash-specific or Linux shell examples, which may leave Linux users uncertain about cross-platform support.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide bash/zsh shell context for CLI examples.
- Add a note or section confirming that all steps are cross-platform and highlight any differences (if any) for Linux/macOS users.
- Consider presenting Azure CLI (which is cross-platform) examples before PowerShell, or at least in parallel, to avoid a Windows-first impression.
- If Visual Studio Code is mentioned, clarify that it is available on all major platforms, or suggest alternatives for Linux users.
- Include troubleshooting tips or links for Linux users who may encounter environment-specific issues.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell scripts as the primary or only scripting example for deploying ARM templates, and by referencing PowerShell before or in more detail than cross-platform alternatives. There are no explicit Linux shell (bash) or scripting examples for ARM template deployment, and the PowerShell deployment script is presented without a CLI or bash equivalent. While Azure CLI is included for service creation, the overall pattern prioritizes Windows-native tooling and omits Linux-native command-line workflows.
Recommendations
- Add bash or shell script examples for ARM template deployment using Azure CLI (e.g., az deployment group create) to ensure Linux users have parity.
- When presenting scripting examples, provide both PowerShell and bash/CLI alternatives side by side.
- Avoid presenting PowerShell as the only automation option for deployment; always include cross-platform CLI commands.
- Explicitly mention that Azure CLI commands work on both Windows and Linux, and provide any OS-specific notes if needed.
- Review the order of examples to avoid always listing Windows/PowerShell first; consider alternating or grouping by platform.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing PowerShell instructions and prerequisites before CLI/Bash equivalents, and by recommending Git Bash (from Git for Windows) as the Bash shell for CLI users. PowerShell is presented as a primary automation method, and the CLI section assumes a Bash shell but specifically references a Windows-centric tool (Git Bash) rather than native Linux/macOS terminals. However, Linux CLI parity is generally maintained in the examples.
Recommendations
- In the CLI prerequisites, mention native Bash shells on Linux and macOS first, then mention Git Bash for Windows users as an alternative.
- Reorder the sections so that CLI (cross-platform) instructions appear before PowerShell (Windows-centric) instructions, or clarify that both are equally supported.
- In the prerequisites and instructions, avoid phrasing that implies PowerShell is the default or preferred automation tool.
- Explicitly state that all CLI examples work natively on Linux and macOS terminals, and provide any necessary notes for Windows users.
- Where possible, provide links or notes for installing Bash on all platforms, not just Git Bash for Windows.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell as the primary method for registering the resource application, mentioning it before the Azure CLI alternative. The use of PowerShell and the 'azurepowershell-interactive' code block further reinforces a preference for Windows tooling and workflows. While Azure CLI is mentioned, there is no explicit mention of Linux or cross-platform environments, and no Linux-specific guidance or examples are provided.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more inclusive of Linux/macOS users.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for running them in different environments.
- If PowerShell is mentioned, clarify that PowerShell Core is available cross-platform, or provide Bash shell equivalents where appropriate.
- Add a section or note highlighting Linux/macOS compatibility and any prerequisites for running the commands on those platforms.
- Review and update custom metadata (e.g., 'devx-tr2ck-azurepowershell') to ensure it does not reinforce a Windows-centric approach.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing all command-line and scripting examples in PowerShell, referencing .NET tooling (dotnet user-secrets, dotnet run) without mentioning cross-platform compatibility, and omitting equivalent Linux/bash examples. There is no mention of Linux-specific tools or alternative shell commands, and the workflow assumes familiarity with Windows-centric patterns.
Recommendations
- Provide equivalent bash/Linux shell script examples for all PowerShell commands, such as base64 encoding and string manipulation.
- Clarify that .NET Core and related tools (dotnet CLI) are cross-platform, and provide explicit instructions for Linux/macOS users where paths or commands may differ.
- Include notes or sections for Linux/macOS users, especially for steps involving local development, environment variable management, and running the sample app.
- When referencing file paths or localhost URLs, mention any differences in how these are handled on non-Windows systems.
- Where screenshots or UI instructions are given, clarify if there are any differences for users on other operating systems.