Digital Twins

216
Total Pages
210
Linux-Friendly Pages
6
Pages with Bias
2.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

17 issues found
Showing 1-17 of 17 flagged pages
Digital Twins Troubleshoot CLI parsing failures ...articles/digital-twins/troubleshoot-error-cli-parse.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists Windows shells (CMD, PowerShell) and Windows-specific escaping patterns (backtick) before or alongside Linux equivalents. Examples and troubleshooting steps do not provide Linux-specific details or examples, and Windows tools/shells are mentioned at least as prominently as Linux ones. There is no explicit Linux example or prioritization, and the mention of escaping with a backtick is a Windows/PowerShell-specific pattern.
Recommendations
  • Provide explicit Linux shell (Bash, Zsh) examples for escaping special characters, including common Linux-specific patterns (e.g., use of single/double quotes, backslash).
  • List Linux shells and solutions before or alongside Windows shells to avoid Windows-first ordering.
  • Clarify which escaping patterns apply to which shells (e.g., backtick for PowerShell, backslash for Bash) and provide examples for each.
  • Include troubleshooting steps or examples specifically for Linux environments, such as handling inline JSON in Bash.
  • Mention Linux tools (e.g., cat, nano, vi) for file creation and editing when suggesting passing JSON via file path.
GitHub Create Pull Request
Digital Twins Azure Digital Twins CLI command set ...-docs/blob/main/articles/digital-twins/concepts-cli.md
High Priority View Details →
Scanned: 2026-01-10 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 equal or greater attention than Bash, with PowerShell mentioned before Bash in some sections and detailed escaping instructions for Windows shells. There is a notable emphasis on Windows tools and patterns, such as PowerShell and CMD, and the CLI version requirements are specifically called out for PowerShell users. Linux-specific shells beyond Bash (e.g., zsh, fish) are not mentioned, and Bash guidance is limited compared to the detailed PowerShell/CMD sections.
Recommendations
  • Add examples and guidance for additional Linux shells (e.g., zsh, fish) to improve parity.
  • Ensure Bash/Linux instructions are presented before or alongside Windows/PowerShell instructions to avoid implicit Windows-first bias.
  • Expand Bash section to include more detailed examples and common pitfalls, matching the depth of PowerShell/CMD guidance.
  • Clarify that CLI version requirements apply to all platforms, not just PowerShell users.
  • Consider adding a summary table comparing shell-specific escaping requirements for quick reference.
GitHub Create Pull Request
Digital Twins Security for Azure Digital Twins solutions .../blob/main/articles/digital-twins/concepts-security.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias primarily by referencing PowerShell cmdlets (e.g., New-AzRoleAssignment) as the main example for role assignment automation, without providing equivalent Azure CLI or Bash examples. Windows-centric tools and patterns (PowerShell, cmdlet terminology) are mentioned exclusively or before any cross-platform alternatives. There are no explicit Linux or cross-platform command examples for key operations such as role assignment, which may hinder parity for Linux users.
Recommendations
  • Provide Azure CLI (az) examples alongside PowerShell cmdlets for all automation scenarios, especially for role assignment and resource management.
  • Include Bash shell command examples where relevant, to demonstrate cross-platform usage.
  • Explicitly mention that all operations can be performed from Linux/macOS environments using Azure CLI, and link to relevant documentation.
  • Avoid using Windows-specific terminology (e.g., 'cmdlet') as the primary example; instead, use neutral or cross-platform language.
  • Add a section or callout highlighting Linux/macOS compatibility and best practices for those platforms.
GitHub Create Pull Request
Digital Twins Customer personal data requests in Azure Digital Twins ...cles/digital-twins/resources-customer-data-requests.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (a web-based tool often associated with Windows workflows) and omitting command-line examples for Linux users. There are no examples using cross-platform tools such as Azure CLI, nor are there references to Linux shell commands or scripting patterns. The REST API is mentioned, but no practical example is given for Linux environments.
Recommendations
  • Add 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 to demonstrate how Linux users can interact with Azure Digital Twins.
  • Explicitly mention that the Azure portal is accessible from any OS/browser, but offer parity by including command-line alternatives.
  • Include links to documentation or tutorials for Linux users on managing Azure Digital Twins resources.
GitHub Create Pull Request
Digital Twins Tutorial: Create a graph in Azure Digital Twins (CLI) ...in/articles/digital-twins/tutorial-command-line-cli.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates several forms of Windows bias. Windows tools and patterns (such as Cloud Shell and file upload via GUI) are mentioned first or exclusively, with limited or no Linux-specific guidance. PowerShell is referenced as an alternative shell, but the main instructions and troubleshooting tips focus on Windows environments. There are missing Linux-specific examples for file upload and shell escaping, and the documentation does not provide parity for Linux command-line workflows or tools.
Recommendations
  • Add explicit instructions and screenshots for uploading files to Cloud Shell from Linux environments, including command-line methods (e.g., using SCP, wget, or Azure CLI storage commands).
  • Provide Linux-specific examples for shell escaping, especially for inline JSON and special characters, with clear Bash and Zsh syntax.
  • Mention and demonstrate Linux-native editors (e.g., nano, vim) for editing model files, not just generic 'code editor'.
  • Clarify that Azure CLI is cross-platform and provide troubleshooting tips for common Linux issues (e.g., file permissions, path formats).
  • Balance references to PowerShell and Bash, and ensure that Bash/Linux instructions are given equal prominence and detail.
  • Include a section or callout for Linux users, summarizing any differences or additional steps they may encounter.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation repeatedly references the Azure portal (a web interface) and REST APIs for managing personal data in Azure Digital Twins, but does not provide any command-line examples or tooling guidance. While the Azure portal is cross-platform via browser, the lack of CLI or scripting examples (such as Azure CLI, Bash, or PowerShell) means Linux/macOS users are not shown platform-native ways to automate or script these tasks. The documentation does not mention or prioritize Windows-specific tools, but it does omit Linux/macOS-centric patterns and examples.
Recommendations
  • Add Azure CLI examples for exporting and deleting personal data, showing commands that work natively on Linux/macOS.
  • Include sample Bash scripts for interacting with the Azure Digital Twins REST APIs.
  • Clarify that the Azure portal is accessible from any modern browser and is not Windows-specific.
  • If PowerShell is mentioned in other related docs, ensure parity with Bash/Azure CLI examples.
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-12 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 (Bash), and refers to escaping with backtick (PowerShell/Windows) before mentioning Bash/Linux conventions. There is no Linux/macOS-specific example or guidance, and the shell options are presented in a way that prioritizes Windows environments.
Recommendations
  • Provide explicit Linux/macOS examples for escaping special characters, such as using single/double quotes and backslash in Bash/zsh.
  • List shell options in a neutral or rotating order, or group them by OS (Windows, Linux/macOS, Cloud Shell).
  • Include a table or section comparing escaping requirements for common shells (Bash, zsh, CMD, PowerShell) with examples for each.
  • Clarify that file input is especially helpful on Linux/macOS due to quoting/escaping differences.
  • Add links to Linux/macOS shell documentation for further reading.
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-12 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 Azure CLI (which is available on Windows, Linux, and macOS). However, there is a notable bias toward Windows and Azure Cloud Shell workflows. File upload instructions and screenshots are Cloud Shell-centric, which is more familiar to Windows users. There is limited guidance for Linux/macOS users regarding file paths, shell differences, and escaping characters, and examples often assume Cloud Shell or Windows-style workflows. Linux-specific instructions and troubleshooting are minimal or absent.
Recommendations
  • Add explicit Linux/macOS examples for file upload and path usage, including screenshots or terminal commands for copying files locally.
  • Provide more detailed guidance on escaping special characters in Bash/zsh, with concrete examples for Linux/macOS shells.
  • Include troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path separators).
  • Balance screenshots and instructions between Cloud Shell and local CLI usage on Linux/macOS.
  • Where Cloud Shell is referenced, clarify its availability and usage on Linux/macOS, and offer alternatives for users who prefer local CLI.
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 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page primarily references the Azure portal (a web-based tool) and REST APIs for managing personal data in Azure Digital Twins. While the Azure portal is cross-platform via browser, there is a notable absence of examples or guidance for Linux/macOS users, such as using Azure CLI, curl, or other command-line tools to interact with the REST APIs. No PowerShell-specific bias is present, but the lack of Linux/macOS-centric instructions or examples creates friction for non-Windows users.
Recommendations
  • Add examples using Azure CLI for common tasks (identifying, exporting, deleting data) alongside portal instructions.
  • Provide sample curl commands for interacting with the REST APIs.
  • Explicitly mention that the Azure portal is accessible from any modern browser on any OS.
  • Include links to cross-platform tools and documentation (e.g., Azure CLI, REST API usage with curl or Postman).
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-11 06:20
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 (Bash), and mentions PowerShell multiple times. There are no explicit Linux/macOS-specific examples, and the guidance does not provide parity for Linux users beyond mentioning Bash as an option.
Recommendations
  • Provide explicit Linux/macOS shell examples (e.g., Bash, Zsh) for escaping characters.
  • List shell options in a neutral or rotating order, or group by OS.
  • Include troubleshooting steps and examples for common Linux/macOS parsing issues.
  • Reference Linux/macOS-specific documentation or external resources for shell differences.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Cloud Shell Heavy Missing Linux Example
Summary
The documentation is largely cross-platform, focusing on the Azure CLI (which is available on Windows, Linux, and macOS). However, there is a notable bias toward Azure Cloud Shell and Windows-centric workflows. File upload instructions and screenshots are Cloud Shell–specific, which is most commonly used from a browser on Windows. There are limited instructions for Linux/macOS users regarding file paths, shell differences, and escaping characters. PowerShell is mentioned only in a note, and Bash is recommended, but Linux-specific examples or troubleshooting are minimal. The tutorial does not provide explicit Linux/macOS file management guidance, and most screenshots are from Cloud Shell (which may feel Windows-centric).
Recommendations
  • Add explicit instructions and screenshots for Linux/macOS users, such as uploading files via SCP/SFTP or using local file paths.
  • Provide examples of CLI commands run from native Linux/macOS terminals, including handling of file paths and escaping characters.
  • Balance screenshots between Cloud Shell and native terminal environments (e.g., Ubuntu Terminal, macOS Terminal).
  • Include troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path separators).
  • Clarify that Azure CLI works equally well on Linux/macOS and provide links to installation guides for those platforms.
GitHub Create Pull Request
Digital Twins Azure Digital Twins CLI command set ...-docs/blob/main/articles/digital-twins/concepts-cli.md
Low Priority View Details →
Scanned: 2026-01-12 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) are given dedicated sections and examples, and PowerShell is mentioned in CLI requirements before Bash. There is a slight tendency to mention Windows environments and tools first, and PowerShell-specific guidance is detailed. Linux/macOS users are supported via Bash examples, but the overall structure and emphasis lean toward Windows environments.
Recommendations
  • Add explicit examples for Linux/macOS terminal environments (e.g., zsh, fish) if shell-specific differences exist.
  • Ensure Bash examples are shown first or equally with PowerShell/CMD, especially in introductory sections.
  • Clarify that the Azure CLI and its extensions are fully supported on Linux/macOS, and link to OS-specific installation guides.
  • Add a table summarizing shell-specific escaping for all major platforms, including Linux/macOS.
  • Avoid mentioning PowerShell in CLI requirements before Bash unless there is a specific reason.
GitHub Create Pull Request
Digital Twins Create a data history connection ...digital-twins/how-to-create-data-history-connection.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias, primarily in its references to PowerShell and the Azure Cloud Shell PowerShell environment. However, all CLI examples are written for Bash, and the documentation explicitly notes that commands are Bash-based and may need adjustment for PowerShell. The page does not provide PowerShell-specific command examples, nor does it reference Windows-only tools or workflows. The bias is limited to mentioning PowerShell as an alternative and referencing the Azure Cloud Shell PowerShell environment before Bash in some notes.
Recommendations
  • Provide explicit PowerShell command examples alongside Bash, or clarify how to translate Bash commands to PowerShell.
  • Ensure that references to PowerShell and Bash environments are presented with equal prominence (e.g., 'You can use Azure Cloud Shell in Bash or PowerShell environments').
  • Add a short section or link describing how Linux/macOS users can install and use Azure CLI, if not already present.
  • Avoid implying PowerShell is the default or preferred environment for CLI usage.
GitHub Create Pull Request
Digital Twins Security for Azure Digital Twins solutions .../blob/main/articles/digital-twins/concepts-security.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias, primarily in its use of PowerShell cmdlets (e.g., New-AzRoleAssignment) as the sole example for automating role assignments. Windows/PowerShell tooling is referenced before any mention of cross-platform alternatives, and there are no explicit CLI (az) or Bash examples for Linux/macOS users. However, most of the guidance is conceptual and not platform-specific, so Linux/macOS users can follow the instructions with some adaptation.
Recommendations
  • Provide equivalent examples using Azure CLI (az) for role assignments and automation tasks, alongside PowerShell.
  • Explicitly mention that both PowerShell and Azure CLI are supported and provide links to relevant cross-platform documentation.
  • Where cmdlets are referenced, add a note or example for Bash/Linux/macOS users showing the equivalent command.
  • Review other sections for subtle Windows-first language or tool references and ensure parity in examples and instructions.
GitHub Create Pull Request
Digital Twins Azure Digital Twins CLI command set ...-docs/blob/main/articles/digital-twins/concepts-cli.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides examples and shell-specific guidance for Bash, PowerShell, and Windows CMD. PowerShell and Windows CMD receive dedicated sections and examples, and Windows tooling (PowerShell, CMD) is mentioned before Linux/macOS alternatives in some places. The CLI version requirement is specifically called out for PowerShell users, but not for Bash or other shells. Bash is covered, but the overall structure and example order favor Windows environments.
Recommendations
  • Add explicit guidance and examples for Linux/macOS users, such as Zsh and other common shells.
  • Ensure CLI version requirements are stated for all platforms, not just PowerShell.
  • Alternate the order of shell examples so Linux/macOS shells are not always listed after Windows shells.
  • Provide a summary table comparing shell-specific escaping for Bash, Zsh, PowerShell, and CMD.
  • Clarify that the Azure CLI is cross-platform and works equally well on Linux/macOS.
GitHub Create Pull Request
Digital Twins Security for Azure Digital Twins solutions .../blob/main/articles/digital-twins/concepts-security.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing PowerShell cmdlets (e.g., New-AzRoleAssignment) as the primary automation example for role assignment, and linking to PowerShell module documentation. There are no explicit CLI (az CLI) or Linux/macOS shell examples for role assignment, nor are cross-platform tools or commands mentioned alongside PowerShell. The order of presentation and examples subtly prioritize Windows tooling and patterns.
Recommendations
  • Add equivalent Azure CLI (az CLI) examples for role assignment and automation, showing both Windows and Linux/macOS usage.
  • Reference both PowerShell and CLI documentation when discussing automation, and clarify that both are supported.
  • Where possible, provide code snippets for common tasks in both PowerShell and CLI/bash.
  • Explicitly mention cross-platform compatibility for all automation scenarios.
GitHub Create Pull Request
Digital Twins Create a data history connection ...digital-twins/how-to-create-data-history-connection.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page shows minor Windows bias. While the main CLI examples are written for Bash (Linux/macOS), there are repeated notes about using PowerShell and Azure Cloud Shell in PowerShell mode, and the possibility of adjusting commands for PowerShell. Windows/PowerShell environments are mentioned before Linux equivalents, and troubleshooting tips reference PowerShell and MSI (Managed Service Identity) issues more commonly encountered on Windows. However, all core instructions and examples are provided for Bash, and Linux/macOS users can follow the guide without significant friction.
Recommendations
  • Add explicit PowerShell command examples or a tabbed interface for Bash and PowerShell to ensure parity.
  • Clarify that Bash commands work on Linux/macOS and Windows (with WSL or Git Bash), and provide troubleshooting tips for Linux/macOS environments as well.
  • Where PowerShell is mentioned, provide equivalent Bash instructions or links to Bash-specific troubleshooting.
  • Avoid implying PowerShell is the default or preferred environment; mention Bash and PowerShell equally.
  • Add a short section or note confirming full support for Linux/macOS users and listing any OS-specific caveats.
GitHub Create Pull Request