Digital Twins
108
Total Pages
87
Linux-Friendly Pages
21
Pages with Bias
19.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
58 issues found
Showing 51-58 of 58 flagged pages
Digital Twins
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/tutorial-code.md
...docs/blob/main/articles/digital-twins/tutorial-code.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The tutorial uses generic 'command window' language and presents all command-line examples in a way that works on both Windows and Linux (e.g., 'dotnet' commands). However, it implicitly assumes a Windows-first perspective by referencing Visual Studio-specific tips and not mentioning Linux-specific editors or shell environments. There are no explicit Linux or macOS examples, nor are there any references to common Linux tools or editors. The only editor called out by name is Visual Studio, and the only tip for file management is specific to Visual Studio, which is primarily a Windows tool. There are no explicit PowerShell or Windows command prompt commands, but the lack of Linux-specific guidance or parity tips is a subtle bias.
Recommendations
- Include explicit references to Linux and macOS environments, such as mentioning common editors (e.g., VS Code, Vim, nano) and shell environments (e.g., Bash, Zsh).
- Provide Linux/macOS-specific tips where appropriate, such as how to copy files or set file properties using common Linux tools.
- When giving Visual Studio-specific tips, also provide equivalent instructions for cross-platform editors like VS Code or JetBrains Rider.
- Clarify that all 'dotnet' CLI commands work on Linux, macOS, and Windows, and show example terminal prompts for each platform where relevant.
- Add a section or callout confirming that the tutorial has been tested on Linux and macOS, and note any platform-specific caveats.
Create Pull Request
Digital Twins
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-authenticate-client.md
...n/articles/digital-twins/how-to-authenticate-client.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides only .NET (C#) code samples and instructions, which are most commonly associated with Windows development environments. There are no examples or setup instructions for Linux or cross-platform development environments, and all package management and project setup guidance is tailored to Visual Studio or the dotnet CLI, both of which are Windows-centric or at least Windows-first in their documentation and usage patterns. No Linux-specific tools, shell commands, or environment setup instructions are provided.
Recommendations
- Add equivalent code samples for other supported languages (e.g., Python, Java, JavaScript) and show how to authenticate using Azure.Identity in those languages.
- Include instructions for setting up projects and installing dependencies using cross-platform tools (e.g., pip for Python, npm for JavaScript, Maven/Gradle for Java).
- Provide examples of environment variable configuration and credential management for Linux/macOS shells (e.g., bash, zsh), not just Windows/Visual Studio.
- Explicitly mention that the authentication approaches work on Linux and macOS, and provide any necessary platform-specific notes.
- Where referencing command-line tools, include both Windows (dotnet CLI, PowerShell) and Linux/macOS (bash, sh) equivalents.
Digital Twins
Create a data history connection
...digital-twins/how-to-create-data-history-connection.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates minor Windows bias by mentioning PowerShell and Windows environments before Linux/Bash in several places. However, all CLI examples are written for Bash, and Linux users are explicitly supported. There are no Windows-only tools or commands, and Linux parity is generally maintained.
Recommendations
- When referencing CLI environments, mention Bash/Linux first, or equally alongside PowerShell/Windows.
- Provide explicit PowerShell command examples in addition to Bash, or link to conversion guidance for users who prefer PowerShell.
- Clarify that all CLI commands work on Linux/macOS, and highlight any OS-specific caveats if they exist.
- Consider adding a short section or note for macOS users if there are any unique considerations.
Digital Twins
Customer personal data requests in Azure Digital Twins
...cles/digital-twins/resources-customer-data-requests.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page consistently references the Azure portal (a web interface) and REST APIs for managing personal data in Azure Digital Twins, but does not provide any platform-specific examples. However, there is a subtle Windows bias: the Azure portal is mentioned as the primary method for data operations, and there are no examples or guidance for Linux/macOS users (e.g., using CLI tools, curl, or scripting for REST API calls). No Windows-only tools are referenced, but the lack of Linux/macOS parity in examples or alternative workflows creates a mild bias.
Recommendations
- Add examples using cross-platform tools (e.g., Azure CLI, curl, PowerShell Core) for REST API operations.
- Explicitly mention that the Azure portal is web-based and accessible from any OS/browser.
- Provide sample REST API calls using curl or Azure CLI, which are available on Linux/macOS.
- Clarify that all described operations can be performed from any operating system.
Digital Twins
Security for Azure Digital Twins solutions
.../blob/main/articles/digital-twins/concepts-security.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias, primarily in the 'Automating roles' section, where PowerShell cmdlets (specifically New-AzRoleAssignment) are referenced as the example for automating role assignments. No Linux or cross-platform CLI examples (such as Azure CLI) are provided in this context. Additionally, the first and only automation example is Windows-centric, and there is no mention of Linux/macOS equivalents or guidance for users on those platforms. The rest of the documentation is generally platform-neutral, focusing on Azure concepts and services.
Recommendations
- Include Azure CLI examples alongside PowerShell cmdlets for role assignment automation, e.g., show az role assignment create usage.
- Explicitly mention that both PowerShell and Azure CLI are supported and provide links to both sets of documentation.
- Where automation is discussed, offer code snippets for both Windows (PowerShell) and Linux/macOS (Azure CLI/bash).
- Add a note clarifying that all operations can be performed from any OS using Azure CLI, not just from Windows/PowerShell.
Digital Twins
Create a data history connection
...digital-twins/how-to-create-data-history-connection.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates minor Windows bias by mentioning PowerShell and Windows environments first in notes and tips, and by referencing Azure Cloud Shell in PowerShell mode before Bash. However, all CLI examples are written for Bash, and the documentation explicitly states that commands can be adjusted for PowerShell. There are no exclusive Windows-only tools or examples, and Linux/macOS users are not blocked from completing any tasks.
Recommendations
- Provide explicit PowerShell command examples alongside Bash examples, or link to a conversion guide.
- Clarify that Azure CLI works equally well on Linux/macOS and Windows, and provide parity in example ordering.
- Avoid mentioning PowerShell or Windows environments first in notes; instead, present Bash and PowerShell options side-by-side.
- Add a brief section or table showing the equivalence of Bash and PowerShell variable syntax for CLI commands.
Digital Twins
Security for Azure Digital Twins solutions
.../blob/main/articles/digital-twins/concepts-security.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the 'Automating roles' section, where PowerShell cmdlets (specifically New-AzRoleAssignment) are referenced as the example for role assignment automation. No Linux CLI (az CLI) or cross-platform scripting examples are provided, and PowerShell is mentioned first and exclusively. The rest of the documentation is generally platform-neutral, focusing on Azure concepts and portal usage, but the automation example may create friction for Linux/macOS users.
Recommendations
- Add equivalent az CLI examples for role assignment automation (e.g., az role assignment create) alongside PowerShell cmdlets.
- Explicitly mention that automation can be performed using cross-platform tools such as Azure CLI, not just PowerShell.
- Where scripting examples are given, provide both PowerShell and az CLI syntax, or default to az CLI for broader platform compatibility.
- Review other sections for subtle Windows-first language or tool references and ensure parity for Linux/macOS users.
Digital Twins
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/concepts-query-units.md
...ob/main/articles/digital-twins/concepts-query-units.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides only a C# code example and does not include any platform-specific command-line instructions or tooling references. However, it lacks parity in code examples for other platforms or languages (such as Python, JavaScript, or shell scripting), and does not mention or demonstrate how to extract the query-charge header using tools or methods common on Linux (e.g., curl, jq, bash). There is no explicit Windows bias in terms of mentioning Windows tools or PowerShell, but the absence of Linux-oriented examples or guidance constitutes a subtle bias.
Recommendations
- Add examples using cross-platform command-line tools such as curl or HTTPie to demonstrate how to extract the query-charge header from the API response.
- Include code snippets in other popular languages (e.g., Python, JavaScript) that are commonly used on Linux and macOS, not just C#.
- Explicitly mention that the API can be accessed from any platform and provide guidance for both Windows and Linux users.
- If referencing SDKs, provide links and examples for SDKs in multiple languages, not just .NET/C#.