Digital Twins

108
Total Pages
88
Linux-Friendly Pages
20
Pages with Bias
18.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (24)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-ingest-iot-hub-data.md [View Details]
Scanned: 2025-07-15 00:00 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by prioritizing Windows-centric development tools (Visual Studio, Visual Studio Code) and workflows, referencing Windows-specific patterns (such as NuGet package manager), and omitting explicit Linux or cross-platform alternatives for key steps. While Azure CLI is used (which is cross-platform), the instructions and examples for creating and publishing Azure Functions are heavily oriented toward Windows development environments, and there is a lack of Linux-specific guidance or troubleshooting. There are also references to shell escaping issues, but these are only briefly mentioned without concrete Linux/Bash examples.
Recommendations:
  • Add explicit instructions and examples for Linux users, such as using the Azure CLI and dotnet CLI in Bash or other Linux shells for all steps (creating, building, and publishing Azure Functions).
  • Include Linux-specific troubleshooting tips, especially for shell escaping and environment differences.
  • Provide parity in tool recommendations, such as mentioning JetBrains Rider or other cross-platform IDEs alongside Visual Studio.
  • Clarify that the Azure CLI commands work cross-platform, and provide example terminal commands for both Windows (CMD/PowerShell) and Linux (Bash/Zsh).
  • Where Visual Studio or NuGet Package Manager is mentioned, also describe how to perform the same actions using the dotnet CLI on Linux.
  • Add screenshots or terminal output examples from Linux environments where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/includes/digital-twins-tutorial-sample-configure.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation uses Windows-style backslashes in folder paths (e.g., 'digital-twins-samples-main\AdtSampleApp\SampleClientApp') and does not provide equivalent Linux/macOS path examples. There are no Linux-specific instructions or examples, which may confuse or exclude users on non-Windows platforms.
Recommendations:
  • Provide folder navigation examples using both Windows (backslash) and Linux/macOS (forward slash) path separators.
  • Explicitly mention that the instructions apply to all platforms, or provide platform-specific notes where differences exist.
  • Include a note or section for Linux/macOS users to clarify any differences in file paths or commands.
  • Review referenced includes (e.g., 'digital-twins-local-credentials-outer.md') to ensure they also offer cross-platform guidance.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-manage-model.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation page provides code examples and instructions primarily using the .NET SDK (C#) and references Visual Studio Code for model authoring, but does not offer any Linux- or cross-platform-specific command-line examples (e.g., Bash, curl, or Python). There is no mention of Linux-specific tools or shell environments, and no explicit parity for Linux users in the examples or tooling guidance. REST API and Azure CLI are mentioned but not exemplified. The documentation implicitly assumes a Windows/.NET development environment.
Recommendations:
  • Add explicit Linux-friendly examples, such as using curl or HTTPie for REST API calls, and Bash scripts for model management.
  • Provide Azure CLI command examples for all major operations (upload, retrieve, update, delete models), and ensure these are shown alongside or before SDK-specific examples.
  • Include Python SDK examples, which are cross-platform and popular in Linux environments.
  • Clarify that Visual Studio Code is cross-platform, and suggest alternative editors or tools commonly used on Linux if relevant.
  • Where possible, avoid assuming a .NET/C# development environment as the default; present REST API and CLI as primary options for cross-platform parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-manage-graph.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a bias toward Windows environments and tools. All code samples are in C# and reference .NET SDKs, with setup instructions and project creation steps tailored to Visual Studio and Windows-centric workflows. There are no Linux-specific instructions, shell examples, or alternative tooling guidance. The documentation assumes use of Windows tools (e.g., Visual Studio, right-click 'Save as', dotnet CLI) and omits parity for Linux users.
Recommendations:
  • Provide explicit instructions for Linux users, such as using VS Code or JetBrains Rider, and include terminal commands for common Linux distributions.
  • Include bash/zsh shell command examples alongside Windows/PowerShell commands where relevant (e.g., for dotnet CLI, file downloads, and authentication setup).
  • Mention cross-platform editors and tools (e.g., VS Code, nano, vim) in addition to Visual Studio.
  • Clarify that the .NET SDK and Azure Digital Twins SDK are cross-platform, and provide any Linux-specific installation or troubleshooting notes.
  • Show how to download files using wget/curl as alternatives to browser right-click instructions.
  • Add a note or section on running the sample code on Linux/macOS, including any environment variable setup or authentication differences.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-send-twin-to-twin-events.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Visual Studio Heavy
Summary:
The documentation consistently lists Visual Studio (a Windows-centric IDE) before Visual Studio Code and Azure CLI in instructions for creating and publishing Azure Functions. While cross-platform tools like Azure CLI and VS Code are mentioned, the ordering and emphasis on Visual Studio may suggest a Windows-first approach. There are no explicit PowerShell-only commands or Windows-only tools, but the documentation could better highlight Linux parity.
Recommendations:
  • When listing development environments, alternate the order or explicitly state that all methods are cross-platform, with VS Code and Azure CLI being fully supported on Linux.
  • Add explicit notes or sections for Linux/macOS users, especially for common development and deployment workflows.
  • Provide example commands and screenshots from Linux terminals (e.g., bash) in addition to or instead of Windows-centric tools.
  • Clarify that Visual Studio Code and Azure CLI are recommended for Linux users, and link to Linux-specific setup guides where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-ingest-iot-hub-data.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by prioritizing Windows-centric development tools (Visual Studio, Visual Studio Code) and workflows, referencing Windows-specific patterns (such as NuGet package manager in Visual Studio), and omitting explicit Linux or cross-platform alternatives for key steps. While the Azure CLI is cross-platform, the instructions and examples assume familiarity with Windows tooling and do not provide parity for Linux users in terms of editor, package management, or shell-specific guidance.
Recommendations:
  • Explicitly mention and provide examples for Linux development environments, such as using VS Code on Linux, JetBrains Rider, or command-line editors (vim, nano).
  • Include instructions for installing .NET SDK and required packages using Linux package managers (apt, yum, etc.) and dotnet CLI.
  • When referencing Visual Studio or Visual Studio Code, clarify that both are available cross-platform and provide links to Linux installation guides.
  • For shell commands, provide notes or examples for escaping special characters in both Bash and PowerShell, and clarify any differences.
  • Highlight any platform-specific prerequisites or troubleshooting steps for Linux (e.g., permissions, environment variables).
  • Ensure that all steps (such as running the device simulator or publishing the function) are validated and documented for Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-manage-graph.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a bias towards Windows by providing only .NET/C# SDK code samples, referencing Visual Studio as the default editor, and using Windows-centric instructions for downloading files. There are no Linux-specific examples, alternative SDKs (such as Python, Java, or JavaScript), or CLI-based workflows. The instructions for setting up and running code assume a Windows development environment, and there is no mention of Linux-compatible editors, shells, or package managers.
Recommendations:
  • Provide code samples in additional languages supported by the Azure Digital Twins SDK, such as Python, Java, or JavaScript, to ensure cross-platform accessibility.
  • Include instructions for setting up and running the sample project on Linux and macOS, including references to cross-platform editors like VS Code and command-line tools.
  • Offer alternative commands for package installation using Linux/macOS shells (e.g., bash) and package managers.
  • When describing file downloads, mention Linux/macOS methods (such as wget or curl) alongside browser-based instructions.
  • Explicitly state that the SDK and tools are cross-platform, and provide any necessary steps for Linux users (such as setting environment variables or handling authentication).
  • Add a section or callouts for Linux users, highlighting any differences or considerations in the development workflow.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-manage-model.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation page provides code examples and workflows primarily using the .NET SDK (C#) and references Visual Studio Code for authoring, but does not include any Linux- or cross-platform-specific command-line examples (such as Bash, curl, or jq), nor does it mention Linux tools or workflows. REST API and Azure CLI are mentioned, but no concrete Linux shell examples are provided. There is an implicit Windows-first bias due to the focus on .NET/C# and lack of parity for Linux users.
Recommendations:
  • Add explicit Linux shell (Bash) examples for REST API usage, such as using curl to upload, retrieve, and delete models.
  • Include Azure CLI command examples for all major operations (upload, retrieve, delete models), and clarify that Azure CLI is cross-platform.
  • Where SDK examples are given in C#, provide equivalent examples in Python (which is widely used on Linux) or JavaScript.
  • Mention and demonstrate how to use common Linux tools (e.g., jq for JSON manipulation) in relevant workflows.
  • Ensure that any references to Visual Studio Code highlight its cross-platform nature and suggest alternative editors for Linux where appropriate.
  • If PowerShell or Windows-specific tools are referenced elsewhere, provide Linux alternatives or note their equivalents.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-manage-twin.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation page provides only .NET/C# code examples and project setup instructions that are tailored to Windows-centric workflows (e.g., Visual Studio, right-click 'Save as', and 'console app project'). There are no Linux-specific instructions, CLI, or cross-platform code samples. The guidance for downloading files and setting up projects assumes a Windows environment and omits Linux or macOS equivalents.
Recommendations:
  • Include equivalent instructions for Linux and macOS users, such as using 'curl' or 'wget' to download files instead of browser-based 'right-click Save as'.
  • Provide setup and run instructions for common Linux editors (e.g., VS Code, JetBrains Rider) and command-line workflows (e.g., 'dotnet new console' from the terminal).
  • Add CLI-based examples (e.g., using Azure CLI or REST API with curl) for managing digital twins, alongside the .NET SDK examples.
  • Clarify that the .NET SDK and code samples are cross-platform, and explicitly mention how to run them on Linux and macOS.
  • Where possible, provide code snippets in additional languages (such as Python or JavaScript) that are popular in Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-parse-models.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation focuses exclusively on the .NET parser library and provides only C# code examples, which are most commonly associated with Windows development environments. There are no examples or guidance for using the parser library on Linux or with non-Windows tools, nor is there mention of cross-platform usage or alternative languages/environments.
Recommendations:
  • Include explicit instructions or notes on using the .NET parser library on Linux (e.g., with .NET Core/.NET 6+), including any prerequisites or differences.
  • Provide code examples or command-line snippets for running the parser on Linux (e.g., using dotnet CLI on Ubuntu).
  • Mention that the .NET parser library is cross-platform and can be used on Linux and macOS as well as Windows.
  • If possible, add examples in other languages supported by Azure Digital Twins (such as Python or JavaScript) to broaden platform inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-query-graph.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation page primarily provides query language examples and C#/.NET SDK usage, with no explicit examples or instructions for Linux users or non-Windows environments. The only shell-related tip references 'Cloud Shell' without clarifying platform, and the SDK example is exclusively in C#. There are no Linux/Unix shell, Python, or cross-platform SDK examples, nor is there mention of Linux-specific tools or workflows.
Recommendations:
  • Add examples using cross-platform SDKs, such as Python or JavaScript, to demonstrate query execution from non-Windows environments.
  • Clarify whether 'Cloud Shell' refers to Azure Cloud Shell (which is cross-platform) and provide equivalent command-line examples for both Windows (PowerShell) and Linux (Bash).
  • Include REST API call examples using curl or HTTPie, which are common on Linux and macOS.
  • Explicitly mention that the SDKs and APIs can be used from Linux, and provide at least one end-to-end example from a Linux environment.
  • Balance the order of examples so that Windows-specific tools or languages are not always presented first.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-send-twin-to-twin-events.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Visual Studio Heavy Missing Linux Example
Summary:
The documentation consistently presents Visual Studio (a Windows-centric tool) before Visual Studio Code and the Azure CLI, both in project creation and publishing steps. There are no explicit Linux-specific instructions or examples, and the use of Visual Studio is emphasized, which may not be available or preferred on Linux systems. While Azure CLI is mentioned, there is no guidance for Linux-specific environments or workflows, and no mention of common Linux editors or shell environments.
Recommendations:
  • Present Visual Studio Code and Azure CLI instructions before Visual Studio, or at least in parallel, to avoid implying a Windows-first workflow.
  • Explicitly mention that all Azure CLI and .NET Core commands work on Linux, and provide example commands run in a Linux shell (e.g., bash).
  • Include instructions or links for setting up and using Azure Functions with Linux-native tools and editors (e.g., JetBrains Rider, Vim, or Emacs).
  • Add a note clarifying that Visual Studio is optional and not required for Linux users.
  • Provide sample commands and screenshots from a Linux terminal to demonstrate parity.
  • Ensure that any referenced sample code repositories include Linux setup instructions (e.g., requirements for dotnet SDK on Linux, troubleshooting tips).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-use-apis.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 is heavily oriented toward Windows users by exclusively referencing Visual Studio (a Windows-centric IDE) and its .http file support for making API calls. There are no examples or guidance for Linux users or for cross-platform tools/editors. The workflow assumes the use of Visual Studio and does not mention alternatives like VS Code, curl, Postman, or HTTPie, which are commonly used on Linux and macOS. While Azure CLI is cross-platform, the entire process is framed within the context of Visual Studio on Windows.
Recommendations:
  • Add equivalent instructions for using cross-platform tools such as Visual Studio Code with the REST Client extension, curl, HTTPie, or Postman to make API requests.
  • Provide explicit examples for Linux and macOS users, including how to structure and send HTTP requests outside of Visual Studio.
  • Clarify that Visual Studio is primarily a Windows tool and suggest alternatives for non-Windows environments.
  • Include screenshots or terminal examples from Linux environments where appropriate.
  • Consider restructuring the article to present cross-platform methods first or in parallel with Visual Studio instructions, rather than focusing solely on Windows tooling.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/resources-customer-data-requests.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page consistently references the Azure portal and REST APIs for managing personal data in Azure Digital Twins, but does not provide any platform-specific command-line examples. However, the Azure portal is a web-based tool often associated with Windows-centric workflows, and there are no examples or mentions of Linux-native tools, CLI commands, or cross-platform automation (e.g., Azure CLI, Bash scripts). This may implicitly favor Windows users or those familiar with the Azure portal, while omitting guidance for Linux users or those preferring command-line interfaces.
Recommendations:
  • Include examples using Azure CLI commands for identifying, exporting, and deleting personal data, as Azure CLI is cross-platform and widely used on Linux.
  • Provide Bash script snippets for common tasks, or reference automation via shell scripting.
  • Explicitly mention that the REST APIs can be accessed using tools like curl or httpie, and provide example commands.
  • Clarify that the Azure portal is web-based and accessible from any OS, but supplement with CLI and scripting alternatives for Linux users.
  • Add a section or callout highlighting cross-platform tooling and automation options.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/troubleshoot-error-cli-parse.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation lists Windows and PowerShell shells alongside Linux/Bash, but Windows environments (CMD, PowerShell) are mentioned as primary local shell options. PowerShell and CMD are referenced before or equally with Bash, and escaping guidance refers to backtick (PowerShell/Windows) before backslash (Bash/Linux). There are no explicit Linux-specific examples or troubleshooting steps, and Linux/Bash is not prioritized.
Recommendations:
  • Provide explicit Linux/Bash examples for escaping special characters, including common pitfalls with Bash.
  • List Linux/Bash environments before or alongside Windows/PowerShell when suggesting alternative shells.
  • Include sample error messages or command lines as they would appear in both Bash (Linux/macOS) and PowerShell/CMD (Windows).
  • Clarify which escape characters are used in which shells, with clear tables or examples for both Linux and Windows.
  • Reference Linux-native tools and environments (e.g., Ubuntu Terminal, macOS Terminal) in addition to Windows tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/tutorial-code.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation primarily uses Azure CLI commands, which are cross-platform, but there are subtle Windows biases. Cloud Shell (browser-based, but often associated with Windows users) is referenced heavily, and file upload instructions are written in a GUI-centric way. There are explicit notes about escaping characters in Bash and PowerShell, but the main recommendation is to use Bash, with PowerShell only mentioned as a caveat. There are no explicit Linux-specific instructions or examples (e.g., using Linux-native tools or file paths), and the workflow assumes a Windows-style user experience (e.g., manual file downloads and uploads via browser).
Recommendations:
  • Provide explicit Linux shell (bash) examples for file operations, such as using wget or curl to download model files directly from GitHub, instead of instructing users to manually copy and paste file contents.
  • Include Linux-native file path examples (e.g., /home/user/Room.json) alongside or instead of generic file names.
  • Offer instructions for uploading files to Cloud Shell using CLI tools (e.g., az storage file upload, scp) in addition to GUI-based upload steps.
  • When discussing escaping characters, provide both Bash and PowerShell examples side by side, and clarify which applies to which environment.
  • Add a section or callout for Linux/macOS users, highlighting any differences in workflow or commands, to ensure parity and inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/concepts-security.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a mild Windows bias by referencing PowerShell cmdlets (e.g., New-AzRoleAssignment) and their parameters as the primary or only automation example for role assignments. There are no CLI (e.g., Azure CLI) or Linux shell examples provided for equivalent tasks, and no mention of cross-platform tooling for automation. This may hinder Linux or cross-platform users from easily following automation guidance.
Recommendations:
  • Provide equivalent Azure CLI examples (e.g., using 'az role assignment create') alongside PowerShell cmdlets for role assignment automation.
  • Explicitly mention that both PowerShell and Azure CLI are supported, and clarify which tools are cross-platform.
  • Where automation is discussed, offer both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) command examples.
  • Link to documentation for both PowerShell and Azure CLI modules relevant to Azure Digital Twins and RBAC.
  • Review other sections for implicit Windows-first assumptions and ensure parity in tool and example coverage.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/concepts-apis-sdks.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Powershell Heavy Missing Linux Example
Summary:
The documentation page exhibits a mild Windows bias. While it generally references cross-platform tools like the Azure CLI and AzCopy, it tends to mention Windows-centric tools (such as the Azure portal and .NET SDK) first or exclusively. There are no explicit Linux or macOS-specific instructions, examples, or mentions of alternative tools (e.g., Bash, curl, or Python SDKs). The only sample project referenced is written in .NET (C#), and there are no code snippets or walkthroughs for Linux command-line environments. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users.
Recommendations:
  • Include explicit Linux/macOS instructions and examples alongside Windows/portal instructions, such as using Bash, curl, or wget for API calls and blob uploads.
  • Provide sample projects or code snippets in additional languages (e.g., Python, Java, JavaScript) that are popular in Linux environments, not just .NET (C#).
  • When listing tools or methods (e.g., for uploading blobs), mention cross-platform CLI tools (like Azure CLI and AzCopy) before or alongside the Azure portal.
  • Add example commands for both Windows (PowerShell/CMD) and Linux (Bash) where relevant, especially for authentication and file operations.
  • Reference SDKs for multiple languages and platforms, not just .NET, and provide links or examples for each.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/concepts-cli.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation provides examples and guidance for Bash, PowerShell, and Windows CMD environments. However, PowerShell and Windows CMD receive more detailed attention, with specific sections and examples for each, and PowerShell is mentioned in CLI version requirements. Bash is covered, but Linux-specific shells beyond Bash (e.g., zsh, fish) are not mentioned. The order of presentation places Bash first, but PowerShell is referenced in requirements and receives more nuanced discussion. There is a subtle Windows bias in the prominence and detail given to Windows-native shells and tools.
Recommendations:
  • Expand Linux parity by including examples for additional common Linux shells (e.g., zsh, fish) or explicitly stating that Bash examples apply to most POSIX shells.
  • Clarify that the Azure CLI and its extensions are fully cross-platform, and highlight any Linux/macOS-specific considerations if they exist.
  • Balance the depth of examples and troubleshooting tips between Bash and PowerShell/Windows CMD sections.
  • In CLI version requirements, avoid referencing PowerShell specifically unless there is a unique requirement for it; otherwise, generalize to all supported shells.
  • Consider adding a table summarizing shell-specific syntax differences for quick reference, ensuring equal visibility for Linux and Windows environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/concepts-ontologies-convert.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a bias towards Windows environments by only providing C#/.NET Core sample code and referencing Windows-centric workflows (such as downloading ZIP files and using .NET tools) without mentioning or providing equivalent Linux or cross-platform alternatives. There are no Linux-specific instructions, shell commands, or examples, and the tools highlighted (dotNetRDF, .NET Core CLI) are more familiar to Windows users. The documentation assumes a Windows workflow (e.g., ZIP extraction, .NET usage) and does not address Linux users' needs or provide parity in examples.
Recommendations:
  • Include Linux-specific instructions for running the sample applications, such as using the .NET CLI on Linux and alternative ways to extract ZIP files (e.g., using unzip command).
  • Provide equivalent shell (bash) command examples for downloading and running the converter tools on Linux/macOS.
  • Mention and, if possible, provide sample code in other cross-platform languages commonly used on Linux (such as Python with RDFLib).
  • Explicitly state that the .NET Core tools and libraries are cross-platform, and provide installation instructions for Linux and macOS.
  • Add troubleshooting tips or notes for common Linux issues (e.g., file permissions, dependency installation).
  • Consider including Docker-based instructions or containers to ensure parity across operating systems.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/tutorial-end-to-end.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by using Windows-style paths (backslashes), referencing Windows tools (File Explorer), and providing screenshots from Windows environments. There are no explicit Linux or macOS instructions, examples, or screenshots, and some steps (such as zipping files) assume familiarity with Windows tooling. The language and examples do not address cross-platform differences or provide parity for Linux users.
Recommendations:
  • Provide parallel instructions and screenshots for Linux/macOS environments, including terminal commands for file navigation and zipping files (e.g., using 'zip' command).
  • Use platform-agnostic path notation or clarify both Windows (\) and Linux/macOS (/) path formats in file navigation steps.
  • Include notes or sections that address common differences in running .NET projects and Azure CLI commands on Linux/macOS, such as prerequisites or shell differences.
  • Replace or supplement Windows-specific tool references (like File Explorer) with cross-platform alternatives (e.g., using the terminal or Finder on macOS).
  • Add explicit statements confirming that all steps are supported on Linux/macOS, and provide troubleshooting tips for non-Windows users where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/concepts-query-units.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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#.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-authenticate-client.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.