Azure Health Insights
67
Total Pages
65
Linux-Friendly Pages
2
Pages with Bias
3.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
7 issues found
Showing 1-7 of 7 flagged pages
Azure Health Insights
How to use Azure AI Health Insights containers
.../main/articles/azure-health-insights/use-containers.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific requirements (such as Docker needing to support Linux containers on Windows) are mentioned before Linux equivalents. There is a reference to using PowerShell and Azure CLI scripts for automation, but no Linux shell script examples are provided. The use of backslash as a line continuation character is noted, but no explicit Linux (bash) alternatives are shown. No Linux-specific troubleshooting or command-line examples are given, and the documentation does not provide parity for Linux automation or scripting.
Recommendations
- Add explicit Linux shell script examples for automating resource deployment and container configuration, alongside PowerShell and Azure CLI.
- When discussing line continuation characters, provide both Windows (backslash) and Linux (backslash or backtick) examples, or clarify with explicit examples for each OS.
- Mention Linux prerequisites and installation steps with equal prominence to Windows, including troubleshooting steps specific to Linux environments.
- Provide parity in automation examples: if PowerShell is mentioned, also include bash or shell script equivalents.
- Ensure that references to host operating systems (Windows, Linux, macOS) are balanced and that examples are provided for all major platforms.
Create Pull Request
Azure Health Insights
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-health-insights/includes/example-inference-follow-up-communication-json-request.md
...example-inference-follow-up-communication-json-request.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page references 'Powerscribe', a tool that is primarily Windows-based, and includes a sample document with Windows-style line endings (\r\n). There are no Linux or cross-platform equivalents mentioned, nor are there examples or references to Linux tools or patterns. The documentation does not provide parity for Linux users.
Recommendations
- Include examples or references to Linux-compatible tools for radiology report distribution or dictation (e.g., open-source alternatives or cross-platform solutions).
- Ensure sample data uses platform-neutral line endings (\n) or clarify that the API is agnostic to line ending style.
- Add a note or section describing how Linux users can interact with or process the data, including any relevant command-line tools or scripts.
- If Powerscribe is required, clarify its platform limitations and suggest alternatives for non-Windows environments.
Azure Health Insights
How to use Azure AI Health Insights containers
.../main/articles/azure-health-insights/use-containers.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. Windows-specific requirements (such as Docker needing to be configured for Linux containers on Windows) are mentioned before Linux equivalents. The page references using PowerShell and Azure CLI scripts for automation, but does not provide equivalent Bash or Linux shell script examples. There is no explicit Linux example for automation or scripting, and Windows-specific line continuation (`\`) is referenced with only a brief note to adapt for other OSes.
Recommendations
- Provide explicit Linux and macOS shell script examples for automation, alongside PowerShell.
- When mentioning OS-specific Docker configuration, list Linux and macOS requirements equally and not only as a note for Windows.
- Include Bash examples for resource deployment and container configuration, not just PowerShell.
- Clarify line continuation differences with concrete examples for both Windows (PowerShell) and Linux/macOS (Bash).
- Ensure troubleshooting and stopping instructions include Linux/macOS terminal conventions (e.g., using `kill` or `docker stop` in addition to Ctrl+C).
Azure Health Insights
How to use Azure AI Health Insights containers
.../main/articles/azure-health-insights/use-containers.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. Windows-specific requirements (such as Docker needing to be configured for Linux containers on Windows) are mentioned before Linux equivalents, and automation options reference PowerShell and Azure CLI scripts without mentioning Bash or Linux shell scripts. No explicit Linux examples are missing, but Windows tools and patterns are referenced first or exclusively in some sections.
Recommendations
- Add explicit Linux shell script examples for automation alongside PowerShell and Azure CLI.
- Mention Linux prerequisites and patterns before or alongside Windows-specific notes (e.g., clarify that Docker defaults to Linux containers on Linux).
- Provide troubleshooting and stopping instructions for both Windows (PowerShell/CMD) and Linux (Bash/terminal) environments.
- Ensure parity in references to command-line environments, not assuming Windows as the default.
- Clarify that all Docker commands are cross-platform and provide OS-specific notes where necessary (e.g., line continuation characters).
Azure Health Insights
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-health-insights/use-containers.md
.../main/articles/azure-health-insights/use-containers.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. Windows-specific instructions (such as Docker configuration for Linux containers on Windows) are mentioned before Linux equivalents. The use of backslash '\' as a line continuation character is noted, which is a Windows/PowerShell convention, and users are told to adapt it for their OS. Additionally, PowerShell and Azure CLI scripts are referenced as automation options, but no Linux shell script examples are provided. However, most command-line examples use Bash syntax and generic Docker commands, which are cross-platform.
Recommendations
- Add explicit Linux/macOS instructions for Docker installation and configuration, including references to package managers (apt, yum, brew).
- Provide Linux shell script examples for automating resource deployment and container configuration, alongside PowerShell and Azure CLI.
- Use POSIX-compliant line continuation (backslash at end of line) in examples, or show both Windows (backtick) and Linux (backslash) conventions.
- When mentioning OS-specific requirements, list Linux/macOS before or alongside Windows, not after.
- Clarify that all Docker commands are cross-platform and, where differences exist, provide side-by-side examples for Windows, Linux, and macOS.
Azure Health Insights
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-health-insights/use-containers.md
.../main/articles/azure-health-insights/use-containers.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. Windows-specific instructions (e.g., Docker configuration for Linux containers on Windows) are mentioned before Linux equivalents, and automation references (PowerShell and Azure CLI scripts) prioritize Windows tooling. There are no explicit Linux shell script examples, and the line continuation note is Windows-centric. However, most command examples use cross-platform Docker and cURL commands.
Recommendations
- Add explicit Linux and macOS instructions for Docker installation and configuration, including common troubleshooting steps for those platforms.
- Provide Linux shell script examples for automating resource deployment and container configuration, alongside PowerShell and Azure CLI.
- Clarify line continuation differences by showing both Windows (backslash) and Linux/macOS (backslash or no continuation) examples.
- Mention Linux and macOS terminal shortcuts (e.g., stopping containers) alongside Windows equivalents.
- Ensure all platform-specific notes are presented in parallel, not Windows-first.
Azure Health Insights
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-health-insights/use-containers.md
.../main/articles/azure-health-insights/use-containers.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation exhibits mild Windows bias by mentioning Windows-specific Docker configuration before Linux, specifically noting that 'On Windows, Docker must also be configured to support Linux containers.' Additionally, PowerShell and Windows tools are referenced as automation options before Azure CLI, and there is an implicit assumption of familiarity with Windows conventions (e.g., line continuation character guidance). However, the majority of examples and commands are cross-platform (bash/curl/Docker), and Linux is not excluded from any instructions.
Recommendations
- Explicitly provide Linux-specific guidance alongside Windows notes, such as clarifying Docker installation and configuration steps for both platforms.
- When mentioning automation options, list cross-platform tools (e.g., Azure CLI, bash scripts) before or alongside Windows-specific tools like PowerShell.
- Where line continuation characters are discussed, provide both Windows (^) and Linux (\) examples, or link to platform-specific documentation.
- Consider adding a short section or callout confirming that all commands are intended to work on both Linux and Windows (with Docker configured for Linux containers), and provide troubleshooting tips for both environments.