Healthcare Apis

237
Total Pages
185
Linux-Friendly Pages
52
Pages with Bias
21.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (86)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicom-configure-azure-rbac.md [View Details]
Scanned: 2025-07-17 00:00 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicom-register-application.md [View Details]
Scanned: 2025-07-17 00:00 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/get-healthcare-apis-access-token-cli.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/get-started-with-azure-api-fhir.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicom-configure-azure-rbac.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/davinci-pdex-tutorial.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any OS-specific instructions or examples, but it also does not include any Windows- or PowerShell-specific commands, tools, or patterns. However, there is a lack of explicit Linux (or cross-platform) command-line examples or instructions, which could leave Linux users unsure about how to perform certain actions, such as loading sample data or interacting with the API.
Recommendations:
  • Add explicit instructions or examples for loading sample data using cross-platform tools such as curl or HTTPie, with command-line snippets that work on both Windows and Linux.
  • If any sample .http files are intended for use with a specific tool (e.g., VS Code REST Client, Postman), clarify this and provide cross-platform usage notes.
  • Include a section or callout noting that all examples are platform-agnostic and can be run from any OS with appropriate tools.
  • If there are any scripts or automation steps, provide both PowerShell and Bash (or generic shell) equivalents.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicom-register-application.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/de-identified-export.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/azure-active-directory-identity-configuration.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/configure-local-rbac.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/register-service-azure-ad-client-app.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/customer-managed-key.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/azure-api-fhir-resource-manager-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/register-public-azure-ad-client-app.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/register-resource-azure-ad-client-app.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/smart-on-fhir.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/find-identity-object-ids.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/pull-dicom-changes-from-change-feed.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation provides only a C# example for accessing DICOM Change Feed logs, with no mention of Linux-specific tools, patterns, or alternative languages/platforms (such as Python or Bash) that are commonly used on Linux. There is no explicit Windows bias in terms of tools or PowerShell, but the lack of Linux-oriented examples or cross-platform guidance may disadvantage Linux users.
Recommendations:
  • Add code examples in additional languages popular on Linux, such as Python (using requests or pydicom) or Bash (using curl).
  • Explicitly mention that the REST API can be accessed from any platform, and provide generic HTTP request examples.
  • Include instructions or notes on how to run the C# example on Linux (e.g., using .NET Core/SDK on Linux).
  • Where possible, provide parity in tooling and setup instructions for both Windows and Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/quickstart-asynchronous-python.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by exclusively using PowerShell syntax for all Azure CLI and scripting examples, stating 'we're using PowerShell' without providing Bash or Linux shell equivalents. There are no Linux/macOS-specific instructions or examples, and variable assignment and command usage are tailored to PowerShell users. This may hinder accessibility for users on Linux or macOS platforms who use Bash or other shells.
Recommendations:
  • Provide parallel Bash/Linux shell examples for all Azure CLI commands and scripting steps, especially for variable assignment and command chaining.
  • Explicitly mention that Azure CLI works cross-platform and that users can use Bash, zsh, or other shells on Linux/macOS.
  • Where PowerShell-specific syntax is used (e.g., variable assignment with $Var = ...), show the Bash equivalent (e.g., VAR=...) side-by-side.
  • In the prerequisites or opening sections, clarify that the tutorial is cross-platform and provide guidance for both Windows (PowerShell) and Linux/macOS (Bash) users.
  • For clean-up and other scripting sections, ensure Bash alternatives are present and tested.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/configure-import-data.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a Windows bias by providing only PowerShell commands and instructions for configuring Azure Storage networking and permissions. There are no equivalent examples or guidance for Linux or cross-platform tools (such as Azure CLI, Bash, or REST API via curl). The use of PowerShell is presented as the default and only scripting method, and Windows-centric tools are referenced without mention of alternatives.
Recommendations:
  • Provide equivalent Azure CLI commands for all PowerShell examples, especially for installing modules and configuring storage account network rules.
  • Include Bash/curl examples for REST API interactions where applicable.
  • Explicitly mention that PowerShell commands can be run cross-platform (if true), or clarify platform requirements.
  • Present cross-platform or Linux-native instructions alongside or before Windows/PowerShell examples.
  • Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/get-started-with-fhir.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation consistently lists PowerShell as a primary scripting option and often mentions it before Azure CLI or REST API, which can be used cross-platform. There are no explicit Linux/bash examples or references to Linux-specific tools or workflows. The document also highlights Power BI (a Windows-centric tool) for analytics, with no mention of Linux-friendly alternatives. While cURL and REST Client are mentioned, there is a general lack of parity in example scripts or guidance for Linux users.
Recommendations:
  • Ensure that all scripting examples are provided in both PowerShell and bash/Azure CLI formats, with equal prominence.
  • When listing scripting options, alternate the order or explicitly state that Azure CLI and REST API are cross-platform.
  • Include Linux-specific guidance or examples, such as using bash scripts, and clarify that cURL and REST Client are available on Linux.
  • For analytics, mention cross-platform tools (such as Jupyter Notebooks, Python/pandas, or open-source BI tools) alongside Power BI.
  • Review linked sample scripts to ensure they include bash/Linux equivalents and are not PowerShell-exclusive.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/github-projects.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example Windows First
Summary:
The documentation page references tools and workflows that are primarily associated with Windows environments, such as PowerShell scripts (.ps1), Visual Studio Code extensions, and Azure Data Factory pipelines, without mentioning or providing equivalent Linux or cross-platform alternatives. There are no explicit Linux or bash examples, and the only script linked is a PowerShell script, suggesting a Windows-first approach.
Recommendations:
  • Provide Linux/bash shell script examples or equivalents alongside PowerShell scripts, especially for automation tasks (e.g., creating Synapse external tables).
  • Mention and link to cross-platform tools or clarify when tools (such as VS Code extensions) are available on Linux/macOS as well as Windows.
  • Include references to Linux-native workflows (e.g., using Azure CLI in bash, or running tools in Docker containers) where appropriate.
  • Explicitly state platform compatibility for each tool or script, and provide installation or usage instructions for Linux users.
  • Where Azure Data Factory or other Windows-centric tools are mentioned, suggest or document alternative approaches that are commonly used in Linux environments (e.g., Apache NiFi, custom Python scripts, etc.).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/concepts-machine-learning.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns (such as Azure SQL Server, Power BI, and Microsoft Teams) without mentioning Linux-compatible alternatives or cross-platform options. There are no command-line or code examples, but the exclusive mention of these Microsoft ecosystem tools and the absence of Linux or open-source equivalents suggest an implicit prioritization of Windows environments.
Recommendations:
  • Include references to cross-platform or Linux-friendly alternatives for data repositories (e.g., PostgreSQL, MySQL) and BI tools (e.g., Grafana, Kibana) alongside Azure SQL Server and Power BI.
  • Mention that Azure services (such as Azure Databricks, Azure Functions, and Azure Data Lake) are accessible from both Windows and Linux environments.
  • Provide examples or guidance for integrating with open-source or Linux-based care coordination tools in addition to Microsoft Teams.
  • Explicitly state the cross-platform compatibility of the solution components where applicable.
  • Where possible, add sample workflows or architectural notes for Linux-based deployments or hybrid environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/health-data-services-get-started.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation frequently mentions PowerShell and Azure CLI scripts for client application registration and access token retrieval, often listing PowerShell before Azure CLI. It references .NET SDK and C# as access tools, which are more commonly associated with Windows environments. There are no explicit Linux or cross-platform shell (e.g., Bash) examples, nor are Linux-specific tools or workflows highlighted. The documentation lacks parity in presenting Linux-native approaches or examples, and Windows-centric tools are mentioned first or exclusively.
Recommendations:
  • Provide explicit Bash or Linux shell examples alongside or before PowerShell examples.
  • Mention Azure CLI as the primary cross-platform tool, and clarify that it works on Linux, macOS, and Windows.
  • Include examples using Linux-native tools (e.g., Bash scripts, curl) for authentication and API access.
  • Balance references to .NET/C# with Python or JavaScript examples, which are more cross-platform.
  • Clearly state that all features and workflows are supported on Linux and macOS, not just Windows.
  • Where screenshots are used, include examples from non-Windows environments when possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/smart-on-fhir.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing all command-line examples in PowerShell, referencing .NET SDK and dotnet user-secrets (which are more familiar to Windows users), and omitting equivalent Linux/bash commands or guidance. There are no explicit Linux or cross-platform instructions for cloning repositories, running scripts, or setting environment variables, which may hinder Linux users.
Recommendations:
  • Provide all command-line examples in both PowerShell and bash (or at least indicate bash equivalents).
  • Explicitly mention that .NET SDK and dotnet user-secrets are cross-platform, and provide Linux/macOS installation and usage notes.
  • When referencing file paths, use platform-neutral or dual examples (e.g., forward and backslashes).
  • Add a section or callout for Linux/macOS users, highlighting any differences in setup or command usage.
  • Where scripts are shown (e.g., for base64 encoding), provide both PowerShell and bash (or Python) versions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/device-messages-through-iot-hub.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by exclusively recommending Visual Studio Code with the Azure IoT Tools extension for device creation and message sending, without mentioning or providing alternatives for Linux users. There are no command-line or cross-platform instructions (such as using Azure CLI, IoT CLI, or Python scripts), and all tooling is presented in a way that assumes a Windows/GUI workflow. No Linux-specific or cross-platform examples or tools are referenced.
Recommendations:
  • Include instructions for using Azure CLI or Azure IoT CLI to create devices and send test messages, which work on both Windows and Linux.
  • Provide examples using cross-platform tools such as Python scripts (using the Azure IoT SDK) for device simulation.
  • Explicitly mention that Visual Studio Code and the Azure IoT Tools extension are available on Linux and macOS, or provide alternative workflows for users who prefer not to use a GUI.
  • Add a section or callout for Linux users, outlining the equivalent steps using terminal commands.
  • Ensure screenshots and step-by-step instructions are not solely focused on Windows environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicomweb-standard-apis-curl.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicomweb-standard-apis-python.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/register-application-cli-rest.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/azure-active-directory-identity-configuration.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/github-projects.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example Windows First
Summary:
The documentation page exhibits subtle Windows bias by referencing Windows-centric tools (e.g., PowerShell scripts, SSMS, Power BI) and providing links to PowerShell scripts without mentioning or providing equivalent Linux/bash alternatives. There are no explicit Linux or cross-platform command-line examples, and the analytics tooling and workflow descriptions prioritize or exclusively mention Windows ecosystem tools.
Recommendations:
  • Where PowerShell scripts are referenced (e.g., Set-SynapseEnvironment.ps1), provide or link to bash/shell script equivalents or note cross-platform compatibility.
  • When listing analytics tools (e.g., SSMS, Power BI), also mention cross-platform or open-source alternatives (e.g., Azure Data Studio, Jupyter Notebooks, Apache Spark).
  • Explicitly state when tools or scripts are cross-platform, or provide guidance for Linux/macOS users.
  • Include Linux/macOS setup and usage examples alongside Windows ones, especially for CLI tools.
  • Review all tool references to ensure Linux users are not excluded or left without clear guidance.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicomweb-standard-apis-curl.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/azure-api-fhir-resource-manager-template.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a mild Windows bias by listing PowerShell instructions before CLI/Bash, emphasizing Azure PowerShell (a Windows-centric tool), and suggesting Git Bash (from Git for Windows) as the Bash shell example for CLI users. While Linux/Bash usage is supported via the Azure CLI, the documentation's ordering and tool recommendations subtly prioritize Windows environments.
Recommendations:
  • Alternate the order of PowerShell and CLI/Bash instructions or present CLI/Bash first to balance platform emphasis.
  • In the prerequisites for CLI, mention native Bash shells on Linux/macOS before or alongside Git Bash for Windows.
  • Explicitly state that all CLI examples work natively on Linux/macOS terminals, not just in Git Bash or Windows environments.
  • Where possible, provide cross-platform notes or highlight any differences in command usage between Windows and Linux/macOS.
  • Consider adding a short section or callout confirming full support for Linux/macOS environments to reassure non-Windows users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/configure-private-link.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by providing command-line examples and instructions that are Windows-centric, such as showing nslookup output from a Windows command prompt (C:\Users\testuser>), referencing RDP (Remote Desktop Protocol) to access VMs, and mentioning Azure PowerShell before Azure CLI. There are no explicit Linux or cross-platform command-line examples, and Linux-native access methods (like SSH) are not mentioned. The documentation assumes familiarity with Windows tools and workflows, potentially making it less accessible to Linux users.
Recommendations:
  • Provide equivalent Linux command-line examples alongside Windows ones, such as showing nslookup output from a Linux shell (e.g., $ nslookup ...).
  • Mention SSH as an alternative to RDP for accessing VMs, and provide instructions for both.
  • When listing automation options (PowerShell, CLI, ARM templates), avoid listing PowerShell first or highlight CLI as cross-platform.
  • Explicitly state that all steps can be performed from Linux, macOS, or Windows, and link to relevant cross-platform documentation.
  • Include screenshots or terminal outputs from Linux environments where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/de-identified-export.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/configure-local-rbac.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation provides both PowerShell and Azure CLI examples for creating service principals, but PowerShell is presented first and is described as being tested in Visual Studio Code, which is more common on Windows. There is no explicit mention or example of running these commands on Linux or macOS, nor are there any notes about differences or prerequisites for non-Windows environments. The documentation implicitly assumes a Windows-centric workflow.
Recommendations:
  • Provide explicit examples or notes for running Azure CLI commands on Linux/macOS, including any differences in environment variables or shell syntax.
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first, as Azure CLI is cross-platform.
  • Mention that Visual Studio Code and Azure CLI are available on all major platforms, and clarify that the CLI commands work on Linux and macOS.
  • Add a brief section or note about prerequisites or setup for Linux/macOS users, such as installing Azure CLI and using bash/zsh.
  • Where possible, avoid assuming the use of PowerShell or Windows-specific tools unless necessary, and provide parity in instructions for all platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/customer-managed-key.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by providing PowerShell-based deployment examples and scripts, mentioning PowerShell before or in addition to Azure CLI, and omitting explicit Linux/bash shell examples for ARM template deployment. The CLI example is present, but the only script-based ARM deployment example is in PowerShell, which is Windows-centric. There are no bash or cross-platform shell script examples for Linux/macOS users.
Recommendations:
  • Add bash (Linux/macOS) examples for deploying ARM templates using Azure CLI (e.g., az deployment group create) alongside the PowerShell example.
  • When presenting script-based workflows, provide both PowerShell and bash/CLI equivalents, and avoid presenting PowerShell exclusively or first.
  • Explicitly mention that Azure CLI commands are cross-platform and runnable on Windows, Linux, and macOS.
  • Where possible, use neutral language and ordering (e.g., 'Using Azure CLI and PowerShell') or group examples by platform.
  • Consider including a table or section summarizing all supported methods (Portal, PowerShell, CLI, ARM Template via CLI/PowerShell) with links to platform-specific instructions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/davinci-pdex-tutorial.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any OS-specific command-line examples, but it references sample HTTP files and REST requests without specifying how to execute them. There are no explicit instructions or examples for either Windows (e.g., PowerShell, Windows tools) or Linux (e.g., curl, bash). However, the lack of any mention of Linux tools or command-line usage may disadvantage Linux users who are looking for parity or clear instructions.
Recommendations:
  • Add explicit examples for loading sample HTTP files using cross-platform tools such as curl or HTTPie, with command-line snippets for both Windows (PowerShell/cmd) and Linux/macOS (bash).
  • If any sample files are intended to be used with specific tools (e.g., REST clients, Postman, curl), clarify this and provide instructions for both Windows and Linux users.
  • Include a section or note on how to execute the provided .http files on different platforms, mentioning any platform-agnostic tools (e.g., VS Code REST Client extension, Postman) and how to use them.
  • Ensure that any future additions of command-line or scripting examples are provided for both Windows and Linux environments, or use platform-neutral syntax where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/find-identity-object-ids.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/get-started-with-azure-api-fhir.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by specifically mentioning PowerShell as a deployment option before the Azure CLI and ARM templates. There are no explicit Linux or cross-platform command-line examples, and the only script-based deployment method called out by name is PowerShell, which is primarily associated with Windows environments. The lack of Linux-specific instructions or examples may make it less approachable for Linux users.
Recommendations:
  • Ensure that Azure CLI examples are given equal prominence to PowerShell, as the CLI is cross-platform and widely used on Linux.
  • Where PowerShell is mentioned, also provide Bash or shell script equivalents for Linux users.
  • Explicitly state that the Azure CLI and ARM templates can be used from any platform, including Linux and macOS.
  • If possible, include screenshots or walkthroughs from both Windows and Linux environments.
  • Avoid listing Windows-specific tools (like PowerShell) before cross-platform alternatives unless there is a technical reason.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/register-resource-azure-ad-client-app.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation demonstrates a Windows bias by presenting PowerShell as the primary method for registering the resource application, mentioning it before the Azure CLI alternative. The PowerShell example is highlighted first, and the language and structure suggest a preference for Windows-native tools and workflows, with no explicit mention of Linux or cross-platform considerations.
Recommendations:
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and works natively on Linux and macOS.
  • Explicitly state that both PowerShell and Azure CLI commands can be run on Windows, Linux, and macOS, and provide guidance for users on non-Windows systems.
  • Include a note or section addressing Linux/macOS users, confirming that the Azure CLI example is fully supported and providing any necessary setup instructions.
  • Avoid language that implies PowerShell is the default or preferred approach unless there is a technical reason.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/register-public-azure-ad-client-app.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/register-service-azure-ad-client-app.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/smart-on-fhir.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by providing only PowerShell scripts and commands for key setup steps (e.g., generating reply URLs, cloning and running the app, setting secrets), with no equivalent Bash or Linux shell examples. The use of PowerShell and .NET tooling is assumed throughout, and there is no mention of Linux-specific instructions or cross-platform alternatives. This may hinder Linux users or those working in non-Windows environments.
Recommendations:
  • Provide equivalent Bash/Linux shell commands for all PowerShell examples, especially for generating base64-encoded URLs and running .NET applications.
  • Explicitly mention that the .NET SDK and dotnet CLI are cross-platform, and provide any Linux/macOS-specific installation or usage notes.
  • Include instructions for configuring and running the sample app on Linux/macOS, including file path and environment variable differences.
  • Where screenshots or UI steps are shown, clarify if there are any platform-specific differences or confirm cross-platform parity.
  • Consider adding a section or callout for Linux/macOS users to ensure inclusivity and parity in setup and troubleshooting.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-test-postman.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any platform-specific examples or instructions, but it also fails to mention or demonstrate any tools or commands for either Windows or Linux. This omission can be considered a bias of omission, as Linux users are not given guidance or parity in testing the FHIR API connection.
Recommendations:
  • Add explicit examples for both Windows (e.g., using PowerShell or curl in Command Prompt) and Linux (e.g., using curl or httpie in a terminal) to demonstrate how to test the FHIR API connection.
  • Mention cross-platform tools and provide sample commands for each platform.
  • Clarify that the instructions are platform-agnostic if no platform-specific steps are needed, or explicitly state which tools are recommended for each OS.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/configure-azure-rbac.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a bias towards Windows by referencing Azure PowerShell as the only scripting/automation method for creating custom roles, without mentioning Azure CLI or Bash alternatives. There are no Linux-specific or cross-platform command-line examples, and the only automation guidance links to a PowerShell-based tutorial. The rest of the instructions are GUI-based, which are platform-neutral but do not provide parity for Linux users who may prefer CLI tools.
Recommendations:
  • Add equivalent Azure CLI (az) commands for creating and managing custom roles, alongside the PowerShell example.
  • Reference both Azure PowerShell and Azure CLI documentation when discussing automation or scripting.
  • Include explicit Linux/macOS command-line examples where relevant, especially for automation tasks.
  • Clarify that both PowerShell and Azure CLI are cross-platform, but provide usage examples for each.
  • Consider adding a section or note on how to perform these tasks using Bash or in a Linux environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/manage-access-rbac.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation demonstrates a Windows bias by presenting Azure PowerShell (a Windows-centric tool) before Azure CLI, and by providing a detailed PowerShell example and output before the CLI example. The PowerShell section is more verbose and includes a sample response, while the CLI section is more concise and lacks output details. There is no mention of Linux-specific considerations or examples, and the PowerShell tool is highlighted first, which may suggest a preference for Windows environments.
Recommendations:
  • Alternate the order of PowerShell and CLI examples, or present CLI first to avoid implicit prioritization of Windows tools.
  • Provide equally detailed examples and output for both Azure CLI and PowerShell, including sample responses for CLI commands.
  • Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Add a note or section for Linux/macOS users, clarifying that Azure CLI is the recommended tool for non-Windows environments.
  • Ensure that all instructions and examples are platform-neutral where possible, and avoid assuming the use of Windows-specific tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/configure-private-endpoints.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively describes how to configure private endpoint network access using the Azure portal, with no command-line examples or automation guidance. There are no references to Windows-specific tools or PowerShell, but there is also a lack of parity for Linux users: no CLI (Azure CLI), Bash, or cross-platform automation examples are provided. This omission can disadvantage users who prefer or require non-GUI, scriptable, or Linux-based workflows.
Recommendations:
  • Add Azure CLI examples for all major steps (creating private endpoints, configuring network access, approving/rejecting/removing connections), as the CLI is cross-platform and widely used on Linux.
  • Include Bash script snippets where appropriate to demonstrate automation.
  • Reference both portal and CLI documentation links where available.
  • Explicitly mention that all operations can be performed via the Azure CLI or PowerShell, and provide links or examples for both.
  • Ensure that any future updates include parity between portal, PowerShell, and CLI/Bash instructions to support both Windows and Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/configure-private-link.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by exclusively referencing Remote Desktop Protocol (RDP) for VM access, which is a Windows-centric tool. There are no examples or instructions for accessing the VM from Linux (e.g., via SSH), nor are there any Linux command-line examples or references to Linux tools. The documentation assumes the use of the Azure Portal UI and Windows-based access patterns, omitting parity for Linux users.
Recommendations:
  • Include instructions for accessing the VM using SSH, which is standard for Linux-based VMs.
  • Provide command-line examples for both Windows (PowerShell/CMD) and Linux (Bash) environments when testing endpoints or configuring network settings.
  • Mention both RDP (for Windows VMs) and SSH (for Linux VMs) as options for connecting to the VM.
  • Add notes or sections that clarify how Linux users can perform equivalent actions, ensuring cross-platform parity.
  • Where screenshots or portal steps are shown, consider including CLI or script-based alternatives that work on both Windows and Linux.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/configure-storage.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation is heavily biased towards Windows and PowerShell users. All command-line examples use PowerShell syntax (e.g., variable assignment with $ and $(...)), and the text explicitly states 'we're using PowerShell' without providing equivalent Bash/Linux shell examples. There is no mention of Linux, macOS, or cross-platform shell usage, which may hinder accessibility for non-Windows users.
Recommendations:
  • Provide parallel Bash/Linux shell examples for all command-line steps, using standard Bash variable syntax and command substitution.
  • Clarify that Azure CLI is cross-platform and can be used in any shell, not just PowerShell.
  • Avoid language like 'we're using PowerShell' unless alternatives are also presented; instead, state that examples are provided for both PowerShell and Bash.
  • Add a section or callout for macOS/Linux users, ensuring parity in instructions and troubleshooting.
  • Where possible, use shell-agnostic Azure CLI commands without shell-specific variable assignment, or show both approaches.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicom-register-application.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation demonstrates Windows bias by referencing the PowerShell-specific 'New-SelfSignedCertificate' command for creating self-signed certificates, without mentioning Linux or cross-platform alternatives. No Linux or macOS command-line examples or tools are provided for certificate creation, and the only tool mentioned for this task is Windows PowerShell.
Recommendations:
  • Include Linux/macOS equivalents for certificate creation, such as using 'openssl' to generate self-signed certificates.
  • Provide cross-platform command-line examples or reference platform-agnostic tools where possible.
  • Explicitly mention that 'New-SelfSignedCertificate' is a Windows/PowerShell command and offer alternatives for non-Windows users.
  • Consider adding a table or section summarizing certificate creation options for Windows, Linux, and macOS.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicom-configure-azure-rbac.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation demonstrates Windows bias by exclusively referencing Azure PowerShell for creating custom roles, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI, REST API, or ARM templates. No Linux or cross-platform command-line examples are provided, and the only automation tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations:
  • Provide equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux.
  • Mention REST API or ARM template options for creating custom roles, with links to relevant documentation.
  • Explicitly state that PowerShell is available on Linux and macOS, or clarify if the instructions are Windows-specific.
  • Add Linux/macOS screenshots or terminal examples where applicable.
  • Ensure that all automation and scripting guidance is presented in a platform-agnostic way, or in parallel for both PowerShell and CLI.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/quickstart-bicep.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/fhir-service-bicep.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a mild Windows bias by listing PowerShell (a Windows-centric tool) before CLI in several sections, referencing Git Bash (a workaround for Bash on Windows) as the example Bash shell, and generally presenting PowerShell examples alongside CLI, rather than giving equal focus to native Linux shells or tools. There is no explicit omission of Linux support, but the ordering and tool references subtly prioritize Windows users.
Recommendations:
  • Alternate the order of PowerShell and CLI tabs so that CLI (which is cross-platform and native to Linux/macOS) appears first in some sections.
  • When referencing Bash shells, mention native Linux/macOS terminals before or alongside Git Bash for Windows.
  • Clarify that Azure CLI commands can be run natively on Linux/macOS terminals, not just in Git Bash on Windows.
  • Consider providing a short note about running PowerShell Core on Linux/macOS if PowerShell examples are included.
  • Ensure that all prerequisites and instructions are equally clear for both Windows and Linux/macOS users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/quickstart-asynchronous-python.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by exclusively using PowerShell syntax for all Azure CLI and scripting examples, and explicitly stating that PowerShell is the terminal of choice. There are no equivalent Bash or Linux shell examples, and variable assignment patterns are Windows/PowerShell-specific. This may hinder Linux/macOS users, who typically use Bash or other Unix shells.
Recommendations:
  • Provide all Azure CLI examples in both PowerShell and Bash syntax, or use Bash as the default since Azure CLI is cross-platform.
  • Avoid PowerShell-specific variable assignment (e.g., $Variable = ...) in favor of Bash-compatible syntax (e.g., VARIABLE=...).
  • Clarify that the tutorial works on any OS with Azure CLI, and offer guidance for both Windows (PowerShell) and Linux/macOS (Bash) users.
  • Include a note or tabbed code blocks to switch between PowerShell and Bash examples.
  • Ensure clean-up and resource management commands are also shown in Bash.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/configure-customer-managed-keys.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicomweb-standard-apis-python.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation page is largely cross-platform, as it uses Python and avoids OS-specific commands or tools. However, there is a subtle 'windows_first' bias in the authentication section, where the instructions for obtaining an Azure access token reference the Azure CLI without clarifying its cross-platform availability or mentioning alternatives (such as Azure Cloud Shell, Bash, or PowerShell). The documentation assumes familiarity with the Azure CLI and does not explicitly reassure Linux/macOS users that all steps and tools are supported on their platforms.
Recommendations:
  • Explicitly state that the Azure CLI is cross-platform and works on Windows, Linux, and macOS.
  • Mention that authentication can be performed using Azure Cloud Shell (browser-based, OS-agnostic) or Bash, not just the Azure CLI.
  • If referencing the Azure CLI, provide a link to installation instructions for all platforms.
  • Add a note confirming that all code examples are OS-independent and tested on both Windows and Linux.
  • If any file path examples are shown, use POSIX-style paths or clarify path conventions for both Windows and Linux.
  • If any troubleshooting steps are needed for authentication, mention platform-specific nuances if they exist.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/pull-dicom-changes-from-change-feed.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation provides only a C# example for accessing DICOM Change Feed logs, with no mention of Linux-specific tools, environments, or alternative languages commonly used on Linux (such as Python or Bash). There are no references to Windows-specific tools, but the lack of Linux-oriented examples or cross-platform guidance may disadvantage Linux users.
Recommendations:
  • Add code examples in additional languages popular on Linux, such as Python (using requests or pydicom) or Bash (using curl).
  • Explicitly mention that the C# example can be run cross-platform using .NET Core/.NET 6+, and provide instructions for doing so on Linux.
  • Include sample REST API calls using curl or httpie to demonstrate platform-agnostic access.
  • Clarify any platform dependencies or prerequisites for the DICOM client package, and provide installation instructions for both Windows and Linux.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/events/events-enable-diagnostic-settings.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any command-line examples or tooling instructions, but it also does not mention or show any platform-specific tools (such as PowerShell, Windows CLI, or Linux shell). However, the absence of any CLI examples means there is a missed opportunity to demonstrate parity between Windows (PowerShell) and Linux (Bash/Azure CLI) environments.
Recommendations:
  • Add step-by-step instructions for enabling diagnostic settings using both Azure CLI (cross-platform) and PowerShell, ensuring both Windows and Linux users are supported.
  • Explicitly mention that the Azure Portal instructions are platform-agnostic, but provide links or references to command-line alternatives for automation.
  • Wherever possible, include code blocks for both PowerShell and Bash/Azure CLI to illustrate cross-platform usage.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicomweb-standard-apis-c-sharp.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/events/events-consume-logic-apps.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by referencing 'Windows Plan' specifically when choosing a plan type, without mentioning Linux or cross-platform options. There are no command-line examples, but the only plan type explicitly named is Windows. No Linux-specific instructions, screenshots, or parity notes are provided, and there is no mention of Linux hosting or deployment scenarios. The documentation assumes a GUI (Azure Portal) workflow, which is platform-agnostic, but the explicit mention of 'Windows Plan' and absence of Linux alternatives or clarifications creates a subtle bias.
Recommendations:
  • When specifying plan types, mention both Windows and Linux hosting options if available, or clarify if only Windows is supported.
  • If Logic Apps can be hosted on Linux (e.g., via Docker containers or App Service Linux plans), provide equivalent instructions or notes.
  • Avoid using 'Windows Plan' as a default term; use 'App Service Plan' or specify both Windows and Linux variants.
  • Add a note or section clarifying platform compatibility for Logic Apps, especially for users deploying from non-Windows environments.
  • If command-line or scripting options are relevant (e.g., Azure CLI, Bicep, ARM templates), provide examples that work cross-platform.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/azure-ad-b2c-setup.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/configure-import-data.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/configure-export-data.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/get-started-with-fhir.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/fhir-service-resource-manager-template.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/smart-on-fhir.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/includes/custom-header-auditlog.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/using-rest-client.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/health-data-services-get-started.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/using-curl.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/concepts-machine-learning.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/deploy-arm-template.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively describes deployment using the Azure Portal and the 'Deploy to Azure' button, without providing any command-line examples or alternative instructions for Linux users (e.g., Azure CLI, Bash). There are no references to Windows-specific tools, but the lack of Linux/CLI parity may disadvantage users who prefer or require non-GUI or cross-platform approaches.
Recommendations:
  • Add a section demonstrating how to deploy the ARM template using the Azure CLI (az deployment group create ...) with Bash examples.
  • Include PowerShell examples if desired, but ensure Linux/Bash/CLI examples are presented with equal prominence.
  • Mention that the deployment can be performed from any OS using the Azure CLI, not just via the Azure Portal.
  • Provide links to official Azure CLI installation and usage guides for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/get-started.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/deploy-choose-method.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/iot/device-messages-through-iot-hub.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/release-notes-2021.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/known-issues.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/register-application.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/configure-azure-rbac.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/configure-private-link.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/github-projects.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/health-data-services-get-started.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/known-issues.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/register-application.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/register-application-cli-rest.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.