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 151-175 of 302 flagged pages
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/azure-ad-b2c-setup.md
...in/articles/healthcare-apis/fhir/azure-ad-b2c-setup.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented as the first option for deployment steps, and instructions reference running code in PowerShell locally in Visual Studio Code. While Azure CLI examples are provided (which are cross-platform), the repeated mention of PowerShell and the suggestion to use Visual Studio Code (a Microsoft product) for local execution reinforce a Windows-centric workflow. There are no explicit Linux-specific instructions or examples, and the documentation does not mention running commands in a native Linux shell or provide Linux troubleshooting tips.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands can be run in Bash or other Linux shells, not just in Azure Cloud Shell.
- Include notes or examples for running deployment steps in a native Linux environment (e.g., Ubuntu terminal), including any prerequisites or differences.
- Avoid references to Visual Studio Code as the default local environment; instead, mention generic terminals or popular Linux editors where appropriate.
- Add troubleshooting tips or common issues for Linux users, especially around authentication or environment setup.
- Where screenshots or UI references are made, clarify that the steps are platform-agnostic unless there are known differences.
Create Pull Request
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/configure-import-data.md
...articles/healthcare-apis/fhir/configure-import-data.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell commands for configuring Azure Storage networking, referencing the Az.Storage PowerShell module, and omitting equivalent Linux/bash/CLI examples. The use of PowerShell is presented as the default and only scripting method, with no mention of cross-platform alternatives such as Azure CLI or REST API calls. This may disadvantage users working on Linux or macOS systems.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for storage account configuration and network rule management.
- Explicitly mention that PowerShell is available cross-platform, but also offer bash or shell script examples where appropriate.
- Include REST API examples for advanced users or automation scenarios, making the documentation platform-agnostic.
- Reorder sections or add notes to clarify that all steps can be performed on any OS, not just Windows.
- Add a table or section comparing PowerShell, Azure CLI, and REST API approaches for key tasks.
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 demonstrates a bias towards Windows environments by providing only PowerShell commands for configuring Azure storage account network rules, with no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). The use of PowerShell and references to installing PowerShell modules assume a Windows-centric workflow. There are no instructions or code samples for users on Linux or macOS platforms.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all PowerShell commands, especially for configuring storage account network rules.
- Include notes or sections explicitly addressing Linux/macOS users, with Bash or shell command alternatives.
- Mention cross-platform tools (e.g., Azure CLI) before or alongside PowerShell to ensure parity.
- Clarify that PowerShell Core is available cross-platform, but also offer native Bash/CLI examples for users who prefer not to use PowerShell.
- Where screenshots or UI steps are shown, note any differences for users on non-Windows platforms if applicable.
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
Missing Linux Example
Summary
The documentation consistently lists PowerShell as a primary scripting option, often before Azure CLI, and refers to Windows-centric tools and workflows (e.g., Power BI, PowerShell). There are no explicit Linux-specific examples or mentions of Linux-native tools, and the documentation does not provide parity in demonstrating Linux command-line usage. The focus on PowerShell and Windows tools may make it less approachable for Linux users.
Recommendations
- Ensure that Azure CLI examples are provided and, where possible, listed before or alongside PowerShell to avoid Windows-first ordering.
- Include explicit Linux command-line examples, such as bash scripts, and clarify compatibility with Linux environments.
- Mention Linux-native tools (e.g., jq, wget, curl) and provide sample commands for common Linux shells.
- When referencing Power BI or other Windows-centric tools, suggest cross-platform or open-source alternatives where appropriate.
- Add a section or callout for Linux/macOS users, highlighting any differences or special considerations.
- Review linked sample scripts to ensure they include Linux-compatible versions and not just PowerShell.
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
Summary
The documentation exhibits a Windows bias by presenting PowerShell (a Windows-centric tool) instructions and prerequisites before CLI/Bash alternatives, and by referencing Windows tools (such as Git Bash for Windows) as the default Bash shell example. The CLI section also includes Windows-style path separators (\) in the template file path, which may confuse Linux users. There is little explicit mention or guidance for native Linux/macOS environments, and the overall structure prioritizes Windows/PowerShell workflows.
Recommendations
- Alternate the order of PowerShell and CLI sections, or present CLI (Bash) examples first to balance platform emphasis.
- In the prerequisites, mention native Bash shells on Linux/macOS before or alongside Git Bash for Windows.
- Use POSIX-style (/) path separators in CLI examples, or provide both Windows and Linux/macOS variants.
- Explicitly state that the Azure CLI commands work natively on Linux/macOS terminals, not just in Windows environments.
- Where possible, provide additional notes or troubleshooting tips for Linux/macOS users, such as file path conventions or shell differences.
- Avoid language that implies PowerShell is the primary or default method, and ensure parity in detail and troubleshooting between PowerShell and CLI sections.
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
Summary
The documentation page exhibits a Windows bias by providing all command-line examples in PowerShell, referencing .NET SDK usage without cross-platform clarification, and omitting equivalent Linux/bash commands. The instructions and tooling assume a Windows environment, with no mention of Linux or macOS alternatives for scripting, running, or configuring the sample applications.
Recommendations
- Provide bash/zsh shell script equivalents for all PowerShell command examples, especially for generating reply URLs and running dotnet commands.
- Explicitly state that the .NET SDK and sample applications are cross-platform, and provide any Linux/macOS-specific setup steps if needed.
- Include git clone and directory navigation commands in bash syntax alongside PowerShell.
- Mention any OS-specific prerequisites or troubleshooting tips for Linux/macOS users.
- Ensure screenshots and instructions do not assume Windows-only environments (e.g., file paths, UI differences).
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
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation repeatedly references PowerShell and Azure CLI scripts for automation and management tasks, often listing PowerShell before Azure CLI. There are no explicit Linux or cross-platform command-line examples, and no mention of Bash or Linux-specific tools. The focus on PowerShell and .NET C# as example tools, with no equivalent Linux or open-source alternatives highlighted, suggests a Windows-centric bias. Screenshots and instructions are portal-based, which are platform-agnostic, but all scripting and automation references lean toward Windows-native tools.
Recommendations
- Provide explicit Bash and Linux shell examples alongside PowerShell for all command-line tasks.
- When listing automation options, mention Azure CLI and Bash before or alongside PowerShell to avoid Windows-first ordering.
- Include examples using open-source and cross-platform tools (e.g., Python scripts, REST API calls via curl) with clear instructions for Linux users.
- Add notes or sections clarifying that all Azure CLI commands work on Linux, macOS, and Windows, and provide sample commands in a Linux terminal context.
- Where .NET C# is mentioned, also reference Python or Java SDKs to ensure language parity for non-Windows developers.
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 demonstrates a Windows bias by prioritizing PowerShell in prerequisites and examples, referencing Windows-specific tools (such as PowerShell and Git Bash), and omitting explicit Linux/macOS shell examples. While a CLI tab is present, it still uses some Windows-centric conventions and does not provide native Linux/macOS terminal instructions or context.
Recommendations
- Add explicit Linux/macOS sections in prerequisites, including instructions for installing cURL and Azure CLI on those platforms.
- Provide Bash/zsh shell examples for obtaining tokens and accessing services, using native Linux/macOS syntax and environment variables.
- Avoid referencing Windows-specific tools (e.g., PowerShell, Git Bash) as defaults; instead, present cross-platform alternatives or mention all major platforms equally.
- List CLI/Bash examples before or alongside PowerShell to avoid the impression of Windows-first ordering.
- Clarify that the instructions work on all major platforms, and provide troubleshooting tips for Linux/macOS users where appropriate.
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-centric tools and workflows. It mentions Azure SQL Server and Power BI (both traditionally Windows-focused), and Microsoft Teams, without referencing cross-platform or Linux-native alternatives. There are no examples or mentions of Linux-based tools or command-line workflows, and the documentation assumes familiarity with the Microsoft ecosystem.
Recommendations
- Include examples or references to cross-platform or Linux-native tools for data storage and visualization, such as PostgreSQL, Grafana, or open-source alternatives.
- Clarify whether the architecture and services (e.g., Azure Databricks, Azure Functions) can be deployed and managed from Linux environments, and provide relevant command-line or scripting examples (e.g., Bash, CLI).
- Mention and link to documentation for using Azure services from Linux or non-Windows environments, including deployment and monitoring.
- Balance references to Microsoft tools (Power BI, Teams) with open standards or third-party integrations where possible.
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing Azure PowerShell before Azure CLI and REST API, and by not providing any explicit Linux or cross-platform command-line examples. The mention of Azure PowerShell as a primary automation tool, without equal emphasis or examples for Azure CLI (which is more cross-platform), may lead Linux users to feel secondary. No Linux-specific instructions or examples are provided.
Recommendations
- Ensure that Azure CLI is mentioned before or alongside Azure PowerShell, as it is cross-platform and widely used on Linux.
- Provide explicit command-line examples for both Azure CLI and Azure PowerShell for each deployment step.
- Include notes or sections specifically addressing Linux/macOS users, clarifying that all steps can be performed on non-Windows platforms.
- Avoid implying that PowerShell is the default or preferred automation tool; instead, present CLI and REST API as equally valid options.
- Add links to Azure CLI installation and usage guides, especially for Linux users.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/device-messages-through-iot-hub.md
...healthcare-apis/iot/device-messages-through-iot-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively recommending Visual Studio Code with the Azure IoT Tools extension for device creation and message sending, without mentioning or providing alternatives for Linux users. All step-by-step instructions and screenshots are based on Visual Studio Code, a tool more commonly associated with Windows environments, and there is no mention of command-line alternatives (such as Azure CLI, az iot, or cross-platform scripts) that would be more familiar or accessible to Linux users. No Linux-specific instructions, tools, or troubleshooting tips are provided.
Recommendations
- Provide alternative instructions using Azure CLI (e.g., az iot hub device-identity create, az iot hub device-identity show, az iot hub device send-d2c-message) for device creation and message sending, which are cross-platform and work natively on Linux.
- Explicitly mention that Visual Studio Code and the Azure IoT Tools extension are available on Linux and macOS, and provide installation links or instructions for those platforms.
- Include screenshots or terminal output examples from Linux environments to demonstrate parity.
- Offer a table or section comparing different methods (GUI vs CLI) for device management and message sending, indicating which are cross-platform.
- Add troubleshooting tips or notes for common Linux-specific issues (such as permissions, dependency installation, or environment variables).
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 references PowerShell and CLI scripts for deployment and configuration, but only explicitly mentions PowerShell first, with no mention of Bash or Linux-specific examples. There is a general lack of Linux or cross-platform command-line tooling references, and no Linux-specific deployment or configuration guidance is provided.
Recommendations
- When mentioning deployment scripts, explicitly state support for both PowerShell (Windows) and Bash (Linux/macOS), and provide examples for each.
- If CLI scripts are cross-platform, clarify this and provide sample commands for both Windows and Linux environments.
- Include references to Linux-native tools and patterns (e.g., Bash scripts, shell commands) alongside or before Windows/PowerShell equivalents.
- Ensure that any automation or scripting guidance is tested and documented for both Windows and Linux platforms.
- Add a section or note clarifying cross-platform compatibility and any platform-specific considerations.
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 provides a detailed workaround for a known issue using only PowerShell (Az Module) commands, which are native to Windows environments. There are no equivalent instructions or examples for Linux or cross-platform CLI tools (such as Azure CLI), nor is there mention of how to perform the workaround on non-Windows systems. This creates a Windows-first and PowerShell-heavy bias, and omits guidance for Linux or macOS users.
Recommendations
- Provide equivalent Azure CLI (az) command examples for the workaround, as Azure CLI is cross-platform and works on Windows, Linux, and macOS.
- Explicitly mention that the PowerShell Az Module commands are Windows-centric, and offer alternative instructions for Linux/macOS users.
- Include a note or section on how to install and use Azure CLI for the same task, ensuring parity for non-Windows users.
- Review future documentation to ensure that both Windows (PowerShell) and cross-platform (Azure CLI, REST API) methods are presented side-by-side, or that cross-platform methods are prioritized.
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 demonstrates a Windows bias by exclusively referencing the PowerShell tool and its New-SelfSignedCertificate command for generating self-signed certificates, with no mention of Linux or cross-platform alternatives. There are no Linux shell or OpenSSL examples provided, nor is there guidance for non-Windows users on certificate creation.
Recommendations
- Include Linux and cross-platform instructions for creating self-signed certificates, such as using OpenSSL.
- Provide command-line examples for both Windows (PowerShell) and Linux/macOS (bash/OpenSSL) when referencing certificate generation.
- Explicitly mention that certificate creation can be performed on any OS and link to relevant platform-specific documentation.
- Review other sections for similar tool references and ensure parity in examples and tool recommendations.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/configure-azure-rbac.md
.../main/articles/healthcare-apis/configure-azure-rbac.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell for custom role creation, without mentioning cross-platform or Linux-native alternatives such as Azure CLI. There are no command-line examples for Linux users, and the only automation tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Provide Azure CLI examples alongside or instead of PowerShell for custom role creation, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell must be referenced.
- Add Linux/macOS-specific instructions or notes where relevant, especially for command-line operations.
- Ensure that any references to tools or scripts are balanced between Windows and Linux environments, or use platform-agnostic tools where possible.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/configure-private-link.md
...ain/articles/healthcare-apis/configure-private-link.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-centric tools and workflows. For example, it instructs users to use Remote Desktop Protocol (RDP) to access a VM, which is primarily a Windows method. There are no examples or instructions for Linux users (e.g., using SSH to access a Linux VM), nor are there any command-line examples that would apply to Linux environments. The documentation assumes the use of the Azure Portal GUI, which is cross-platform, but when it comes to VM access and verification, only Windows methods are mentioned.
Recommendations
- Include parallel instructions for Linux users, such as using SSH to access a Linux VM.
- Provide command-line examples (e.g., using curl or wget) to test endpoints from both Windows and Linux environments.
- Mention both RDP (for Windows) and SSH (for Linux) as options for accessing VMs.
- Clarify that the steps apply to both Windows and Linux VMs, and provide any OS-specific considerations.
- Where screenshots or UI steps are shown, note any differences for Linux users if applicable.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/github-projects.md
.../blob/main/articles/healthcare-apis/github-projects.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a subtle Windows bias, primarily through the exclusive mention and linking of a PowerShell script (Set-SynapseEnvironment.ps1) for setting up Synapse environments, with no equivalent Bash or Linux instructions provided. Additionally, tools and workflows such as SSMS (SQL Server Management Studio) and Power BI are referenced, which are traditionally Windows-centric. There are no explicit Linux or cross-platform command-line examples, and the documentation does not mention or prioritize Linux-compatible alternatives or instructions.
Recommendations
- Provide Linux/bash equivalents for all scripts and setup instructions, especially for critical steps like Synapse environment setup.
- Explicitly mention and link to cross-platform tools or alternatives where Windows-specific tools (e.g., SSMS, Power BI) are referenced.
- Add examples or documentation sections that demonstrate workflows on Linux and macOS, ensuring parity with Windows instructions.
- When referencing scripts or tools, indicate their platform compatibility and provide guidance for users on non-Windows systems.
- Consider listing cross-platform or Linux-first tools before or alongside Windows tools to avoid implicit prioritization.
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
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation repeatedly references PowerShell and Azure CLI scripts as primary automation methods, often listing PowerShell before Azure CLI. There is no mention of Linux-specific tools or workflows, and PowerShell (a traditionally Windows-centric tool) is emphasized for tasks such as registering applications, granting permissions, and obtaining tokens. While cURL and Python are mentioned for API access, the overall pattern prioritizes Windows-native tools and patterns, with no explicit Linux parity.
Recommendations
- Provide explicit Linux and macOS instructions and examples alongside or before PowerShell, especially for automation tasks.
- Highlight Azure CLI as a cross-platform tool and give it equal or greater prominence than PowerShell.
- Include bash shell script examples and references to native Linux tools where appropriate.
- Clarify that PowerShell Core is cross-platform if recommending it, or otherwise avoid implying PowerShell is the default.
- Add screenshots and walkthroughs using Linux environments (e.g., Azure Cloud Shell, Ubuntu terminal) where possible.
- Ensure that all code snippets and instructions are validated on both Windows and Linux platforms.
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 provides a workaround for a known issue using only PowerShell commands and the Az PowerShell module, which are Windows-centric tools. There are no equivalent instructions or examples for Linux or cross-platform environments (such as Azure CLI or Bash scripts). This creates a bias toward Windows users and may hinder Linux or macOS users from resolving the issue efficiently.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell commands for all workarounds.
- Explicitly mention cross-platform options and note which tools are available on Windows, Linux, and macOS.
- Where possible, use Bash or shell-agnostic scripting examples in addition to PowerShell.
- Add a note clarifying that the Az PowerShell module can be installed on Linux/macOS, but also recommend Azure CLI as a first-class alternative.
- Review all troubleshooting and workaround sections to ensure Linux and macOS users are not excluded.
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias primarily in the 'Certificates & secrets' section, where only the PowerShell command 'New-SelfSignedCertificate' is mentioned for creating a self-signed certificate. No equivalent Linux or cross-platform methods (such as using OpenSSL) are provided. The rest of the documentation is largely portal-based and platform-neutral, but the only command-line tool referenced is Windows-specific.
Recommendations
- Provide equivalent Linux/macOS instructions for creating self-signed certificates, such as using OpenSSL (e.g., 'openssl req -x509 ...').
- Mention cross-platform tools or methods alongside Windows-specific tools, ensuring parity in all procedural steps.
- Where PowerShell or Windows tools are referenced, add a note or section for Linux/macOS users with appropriate commands.
- Review other sections for subtle platform assumptions and ensure all examples and tool references are inclusive of major operating systems.
Healthcare Apis
Configure local role-based access control (local RBAC) for Azure API for FHIR
...thcare-apis/azure-api-for-fhir/configure-local-rbac.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides PowerShell and Azure CLI examples for creating service principals, but the PowerShell example is presented first and assumes familiarity with Windows-centric tooling. The CLI example uses Bash syntax but does not clarify Linux/macOS compatibility or provide explicit Linux/macOS instructions. There are no references to Linux-specific tools or shell environments, and the documentation does not address potential differences in running CLI commands on Linux/macOS versus Windows.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and provide example commands in a Linux shell context (e.g., bash, zsh).
- Add notes or sections clarifying any differences in command usage or prerequisites for Linux/macOS users.
- Provide Linux/macOS-specific instructions for installing and using the Azure CLI, including authentication steps if they differ.
- Consider presenting CLI examples before PowerShell examples, or side-by-side, to avoid Windows-first bias.
- Avoid language that assumes Visual Studio Code or PowerShell as the default environment; mention alternatives for Linux/macOS users.
Healthcare Apis
Private link for Azure API for FHIR
...care-apis/azure-api-for-fhir/configure-private-link.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Examples and tool references (such as RDP, PowerShell, and nslookup with Windows prompt) are Windows-centric, and Windows terminology (e.g., RDP, C:\Users\) is used exclusively in walkthroughs. Linux/macOS equivalents (e.g., SSH, Bash, Linux CLI, dig) are not mentioned or shown. This may create friction for non-Windows users, though most tasks can be completed with alternative tools.
Recommendations
- Provide Linux/macOS equivalents for all command-line examples (e.g., show 'dig' and 'nslookup' in Bash, use $HOME instead of C:\Users).
- Mention SSH as an alternative to RDP for VM access.
- Clarify that Azure CLI and PowerShell are cross-platform, and provide example commands for both environments.
- Add screenshots or instructions for Linux/macOS where appropriate.
- Avoid using Windows paths and prompts exclusively in code blocks.
Healthcare Apis
Configure customer-managed keys for Azure API for FHIR
...thcare-apis/azure-api-for-fhir/customer-managed-key.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides configuration instructions for customer-managed keys in Azure API for FHIR, with a notable emphasis on Windows-centric tools and workflows. PowerShell is featured prominently, both as a primary automation method and for ARM template deployment, with no mention of Linux/macOS alternatives (e.g., Bash scripts). Examples and deployment instructions are given for PowerShell before Azure CLI, and there is no explicit guidance for Linux/macOS users regarding environment setup or command differences. This creates friction for non-Windows users, though CLI and ARM templates are cross-platform.
Recommendations
- Add Bash shell script examples for ARM template deployment, demonstrating cross-platform usage.
- Explicitly state that Azure CLI commands work on Linux/macOS and provide any necessary environment setup instructions.
- If PowerShell is used, mention that PowerShell Core is available on Linux/macOS and provide installation links.
- Present CLI and ARM template examples before PowerShell, or group them together to avoid Windows-first bias.
- Include notes or tips for Linux/macOS users where workflows or tooling may differ.
Healthcare Apis
SMART on FHIR - Azure API for FHIR
...es/healthcare-apis/azure-api-for-fhir/smart-on-fhir.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples use PowerShell syntax, and there are no equivalent Linux/macOS shell (bash) examples. The instructions for cloning and running the sample app use PowerShell commands and .NET tooling, assuming a Windows environment. No mention is made of Linux-specific setup or alternative shell commands, and Windows-centric patterns (e.g., PowerShell scripting, dotnet user-secrets) are presented first and exclusively.
Recommendations
- Provide bash/zsh equivalents for all PowerShell command examples, especially for reply URL encoding and dotnet commands.
- Explicitly mention Linux/macOS compatibility for the sample app and .NET SDK usage.
- Add instructions for installing prerequisites (e.g., .NET SDK) on Linux/macOS.
- Include screenshots or notes for Linux/macOS environments where relevant.
- Clarify that the SMART on FHIR app launcher can be run cross-platform and provide troubleshooting tips for non-Windows users.
Healthcare Apis
Configure Azure RBAC role for the FHIR service in Azure Health Data Services
.../main/articles/healthcare-apis/configure-azure-rbac.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While most instructions are platform-agnostic (focused on Azure Portal UI), the only command-line tool mentioned for creating custom roles is Azure PowerShell, with no reference to Azure CLI or other cross-platform alternatives. The link to custom role creation specifically points to a PowerShell guide, and PowerShell is highlighted as the method for advanced tasks. No Linux/macOS-specific instructions or parity examples are provided.
Recommendations
- Add instructions and links for creating custom roles using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Explicitly mention that Azure Portal and Azure CLI are available on all major operating systems.
- Where PowerShell is referenced, provide equivalent Azure CLI commands or documentation links.
- Consider listing Azure CLI before or alongside PowerShell to avoid Windows-first impression.