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 26-50 of 58 flagged pages
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/tutorial-command-line-cli.md ...in/articles/digital-twins/tutorial-command-line-cli.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/concepts-security.md .../blob/main/articles/digital-twins/concepts-security.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/concepts-apis-sdks.md ...blob/main/articles/digital-twins/concepts-apis-sdks.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/concepts-cli.md ...-docs/blob/main/articles/digital-twins/concepts-cli.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/concepts-ontologies-convert.md .../articles/digital-twins/concepts-ontologies-convert.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/tutorial-end-to-end.md ...lob/main/articles/digital-twins/tutorial-end-to-end.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins Azure Digital Twins CLI command set ...-docs/blob/main/articles/digital-twins/concepts-cli.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides examples and guidance for Bash, PowerShell, and Windows CMD environments. However, Windows-specific shells (PowerShell and CMD) receive more detailed coverage, with PowerShell mentioned before Bash in several places and Windows CMD included as a separate section. There is also a reference to using Azure CLI with PowerShell as a requirement, which may be confusing for Linux/macOS users. Linux/macOS shells (Bash/zsh) are covered but not as thoroughly, and examples for Bash are less prominent than those for PowerShell.
Recommendations
  • Ensure Bash examples are presented first or equally with PowerShell, as Bash is the default shell on Linux/macOS.
  • Clarify that Azure CLI works natively on Linux/macOS and that PowerShell is not required for those platforms.
  • Add explicit examples for zsh (common on macOS) and clarify any differences from Bash.
  • Avoid implying that PowerShell is the default or required shell for Azure CLI usage.
  • Include troubleshooting tips for Linux/macOS users where shell-specific issues may arise.
GitHub Create Pull Request
Digital Twins Troubleshoot CLI parsing failures ...articles/digital-twins/troubleshoot-error-cli-parse.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation lists Windows shells (CMD, PowerShell) and Windows-specific escape characters (backtick) alongside Bash, but Windows environments and tools are mentioned first and more prominently. There are no Linux/macOS-specific examples or detailed guidance for those platforms, and PowerShell is referenced multiple times, suggesting a Windows-centric approach.
Recommendations
  • Provide explicit Linux/macOS examples, including common shells like Bash and Zsh.
  • List Linux/macOS environments before or alongside Windows environments to avoid Windows-first ordering.
  • Clarify escape character requirements for Bash/Zsh (e.g., single quotes, double quotes, backslash), not just backtick/backslash.
  • Include troubleshooting steps and examples for Linux/macOS users.
  • Mention platform-specific nuances (e.g., file path formats, shell quoting) for parity.
GitHub Create Pull Request
Digital Twins Tutorial: Create a graph in Azure Digital Twins (CLI) ...in/articles/digital-twins/tutorial-command-line-cli.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Cloud Shell Heavy Missing Linux Example
Summary
The tutorial is written for the Azure CLI, which is cross-platform, but the documentation repeatedly references Azure Cloud Shell (browser-based, often Windows-centric) and gives instructions and screenshots for Cloud Shell file uploads. There is minimal guidance for Linux/macOS users regarding file paths, shell differences, or alternative workflows. Windows/Cloud Shell instructions and screenshots are presented first and exclusively, while Linux-specific considerations (like escaping characters in Bash) are mentioned only in notes and not illustrated with examples.
Recommendations
  • Add explicit instructions and screenshots for Linux/macOS terminal usage, including file path conventions and file upload/download methods.
  • Provide examples of CLI commands run in native Bash/zsh shells, not just Cloud Shell.
  • Clarify differences in escaping JSON and special characters between Bash, PowerShell, and Cloud Shell, with concrete examples for each.
  • Mention and illustrate how to use the Azure CLI on Linux/macOS, including installation, authentication, and file management.
  • Balance screenshots and step-by-step instructions between Cloud Shell (browser) and native terminals on different OSes.
GitHub Create Pull Request
Digital Twins Azure Digital Twins CLI command set ...-docs/blob/main/articles/digital-twins/concepts-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides examples and tips for Bash, PowerShell, and Windows CMD environments. However, Windows-specific environments (PowerShell and CMD) receive more detailed attention, with PowerShell mentioned in CLI requirements and given its own section before Windows CMD. The CLI version requirements specifically call out PowerShell, and Windows CMD is treated as a distinct shell, while Linux/macOS shells are only represented by Bash. There are no explicit Linux/macOS examples beyond Bash, and Windows environments are mentioned first or in more detail in several places.
Recommendations
  • Add explicit examples for macOS Terminal and common Linux shells (e.g., zsh, fish) if shell behavior differs.
  • Clarify that Bash examples apply to both Linux and macOS, and mention these platforms explicitly.
  • Reorder sections so that Bash/Linux/macOS examples are presented before Windows-specific ones to avoid 'windows_first' bias.
  • In CLI requirements, mention compatibility with Linux/macOS shells and not just PowerShell.
  • Provide a summary table comparing shell-specific escaping for Bash (Linux/macOS), PowerShell, CMD, and other common shells.
GitHub Create Pull Request
Digital Twins Customer personal data requests in Azure Digital Twins ...cles/digital-twins/resources-customer-data-requests.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently references the Azure portal (a web-based tool) and REST APIs for data management, but does not provide any command-line examples or tooling guidance for Linux/macOS users. The absence of CLI, shell, or cross-platform automation examples means Linux users may lack clear instructions for exporting or deleting data outside the portal or REST API documentation.
Recommendations
  • Add Azure CLI examples for identifying, exporting, and deleting personal data, as Azure CLI is cross-platform.
  • Include sample curl commands for REST API operations, demonstrating how Linux/macOS users can interact with the APIs.
  • Explicitly mention that the Azure portal is web-based and accessible from any OS/browser, to clarify parity.
  • Provide links or references to automation scripts or SDKs that work on Linux/macOS.
GitHub Create Pull Request
Digital Twins Troubleshoot CLI parsing failures ...articles/digital-twins/troubleshoot-error-cli-parse.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation lists Windows shells (CMD, PowerShell) before Linux equivalents and refers to Windows-specific escaping (backtick). PowerShell is mentioned multiple times, and no Linux/macOS-specific examples or shell behaviors are provided. There is no explicit Linux example or discussion of Linux-specific issues, and Windows tools are referenced alongside generic options.
Recommendations
  • Provide explicit Linux/macOS shell examples, such as Bash and zsh, including how to escape special characters in those environments.
  • List Linux/macOS shells before or alongside Windows shells to avoid ordering bias.
  • Discuss shell-specific quirks for Linux/macOS (e.g., single vs. double quotes, backslash escaping) with concrete examples.
  • Include troubleshooting steps or examples for common Linux/macOS parsing failures.
GitHub Create Pull Request
Digital Twins Tutorial: Create a graph in Azure Digital Twins (CLI) ...in/articles/digital-twins/tutorial-command-line-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Cloud Shell Heavy Missing Linux Example
Summary
The documentation is generally cross-platform, focusing on the Azure CLI (which is available on Windows, Linux, and macOS). However, there is a notable bias toward Windows and Cloud Shell usage: file upload instructions and screenshots are Cloud Shell-centric (which is more familiar to Windows users), and Linux/macOS-specific instructions (such as file upload or shell escaping) are either missing or only briefly mentioned. Windows/Cloud Shell workflows are described in detail, while Linux/macOS alternatives are not equally covered.
Recommendations
  • Add explicit instructions and screenshots for uploading files to Azure CLI on Linux/macOS (e.g., using SCP, curl, or local file paths).
  • Provide examples of running Azure CLI commands in native Linux/macOS terminals, including common shell escaping issues and solutions.
  • Balance Cloud Shell instructions with guidance for users running Azure CLI locally on Linux/macOS.
  • Include troubleshooting tips for Linux/macOS users, such as permissions, path formats, and environment setup.
  • Where screenshots are used, alternate between Windows/Cloud Shell and Linux/macOS terminal views.
GitHub Create Pull Request
Digital Twins Customer personal data requests in Azure Digital Twins ...cles/digital-twins/resources-customer-data-requests.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a web interface typically accessed via browsers on Windows) and REST APIs, without mentioning or providing examples for Linux-specific tools, command-line interfaces, or patterns. There are no examples using Linux shell commands, CLI tools, or cross-platform automation methods. The workflow descriptions implicitly assume users are familiar with Windows-centric interfaces and do not address Linux users' needs.
Recommendations
  • Include examples using Azure CLI commands for identifying, exporting, and deleting personal data, as Azure CLI is cross-platform and commonly used on Linux.
  • Provide sample REST API calls using curl or wget from a Linux shell, demonstrating how to interact with Azure Digital Twins programmatically.
  • Mention and link to documentation for cross-platform tools (e.g., Azure CLI, PowerShell Core) and clarify their availability on Linux.
  • Add guidance for automating data export and deletion using shell scripts or other Linux-native tools.
  • Ensure that instructions do not assume use of the Azure portal as the primary or only method, and present CLI/API options alongside GUI instructions.
GitHub Create Pull Request
Digital Twins Customer personal data requests in Azure Digital Twins ...cles/digital-twins/resources-customer-data-requests.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently references the Azure portal and REST APIs for data management tasks, but does not provide any platform-specific examples. However, the Azure portal is a web-based tool often associated with Windows environments, and there is no mention of Linux-native tools, command-line interfaces, or examples using Bash, curl, or other Linux utilities. The lack of Linux-specific guidance or parity in examples may make the documentation less accessible to Linux users.
Recommendations
  • Add examples of using REST APIs with Linux tools such as curl or httpie.
  • Include instructions for performing data export and deletion using Bash scripts or Linux command-line utilities.
  • Clarify that the Azure portal is accessible from any OS via a web browser, and provide parity in examples for both Windows and Linux environments.
  • Reference Azure CLI usage for managing Azure Digital Twins, with example commands for Linux users.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/resources-customer-data-requests.md ...cles/digital-twins/resources-customer-data-requests.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing the Azure portal (a web interface most commonly accessed from Windows environments) as the primary tool for managing personal data, with no mention of Linux-specific tools, CLI, or cross-platform command-line examples. There are no examples using Azure CLI, Bash, or Linux-native workflows, and the REST API references lack platform-agnostic usage samples.
Recommendations
  • Include examples using Azure CLI commands for identifying, exporting, and deleting personal data, which are cross-platform and commonly used on Linux.
  • Provide sample REST API calls using curl or other Linux-native tools, demonstrating how to perform operations from a Linux environment.
  • Explicitly mention that the Azure portal and REST APIs are accessible from any operating system, and clarify that no Windows-only tools are required.
  • Add a section or callout for Linux users, highlighting parity and best practices for managing Azure Digital Twins data from Linux systems.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/resources-customer-data-requests.md ...cles/digital-twins/resources-customer-data-requests.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references the Azure portal and REST APIs for managing personal data in Azure Digital Twins, but does not provide platform-specific examples. However, the Azure portal is a web-based tool that is often associated with Windows environments, and there is no mention of Linux-native tools, CLI commands, or shell scripting alternatives. The lack of Linux-specific guidance or parity in examples may make the documentation less accessible to Linux users.
Recommendations
  • Include examples using Azure CLI commands for identifying, exporting, and deleting personal data, which are platform-agnostic and commonly used on Linux.
  • Mention that the Azure portal is accessible from any modern web browser, regardless of OS, to clarify cross-platform compatibility.
  • Provide sample scripts for using REST APIs with curl or other Linux-native tools.
  • Explicitly state that all described operations can be performed from Linux, macOS, or Windows environments.
  • Add links or references to Linux-specific documentation or tutorials where relevant.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/includes/digital-twins-tutorial-sample-configure.md ...ns/includes/digital-twins-tutorial-sample-configure.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-manage-model.md ...lob/main/articles/digital-twins/how-to-manage-model.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-send-twin-to-twin-events.md ...icles/digital-twins/how-to-send-twin-to-twin-events.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-manage-model.md ...lob/main/articles/digital-twins/how-to-manage-model.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-manage-twin.md ...blob/main/articles/digital-twins/how-to-manage-twin.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-parse-models.md ...lob/main/articles/digital-twins/how-to-parse-models.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-query-graph.md ...blob/main/articles/digital-twins/how-to-query-graph.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/resources-customer-data-requests.md ...cles/digital-twins/resources-customer-data-requests.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
← Previous Page 2 of 3 Next →