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 1-25 of 58 flagged pages
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias. While the Azure CLI is cross-platform, the tutorial repeatedly references Azure Cloud Shell (which defaults to Bash but is often used in Windows environments) and provides instructions for uploading files using the Cloud Shell GUI, a pattern more familiar to Windows users. There is a specific note about escaping characters in PowerShell, but Linux/Bash-specific issues are only briefly mentioned. The tutorial does not provide explicit Linux command-line examples for file upload or manipulation, nor does it discuss Linux-specific CLI setup or troubleshooting. The examples and screenshots are primarily from Cloud Shell, which can be used on any platform but is often associated with Windows users. There is no mention of Linux-native tools (e.g., wget, curl, cp) for downloading or managing files, and the documentation does not offer parity in guidance for Linux users.
Recommendations
  • Add explicit Linux/Bash command-line examples for downloading sample files (e.g., using wget or curl) and managing files locally.
  • Include a section or notes on Linux-specific CLI setup, troubleshooting, and environment preparation.
  • Provide parity in error handling and escaping instructions for both Bash and PowerShell, with concrete examples for each.
  • Offer screenshots and instructions for both Windows (Cloud Shell, PowerShell) and Linux (local terminal, Bash) environments.
  • Mention Linux-native tools and patterns alongside Windows/Cloud Shell equivalents, ensuring equal visibility and guidance.
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-11 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, there is a noticeable Windows bias: PowerShell and Windows CMD are given dedicated sections and examples, and PowerShell is mentioned before Bash in some contexts (e.g., CLI version requirements). The CLI version requirement is specifically called out for PowerShell users, and Windows-specific shell behaviors are explained in detail. There are no examples for Linux-specific shells beyond Bash (e.g., zsh, fish), and the documentation assumes familiarity with Windows tools and patterns.
Recommendations
  • Add explicit examples and guidance for popular Linux shells beyond Bash, such as zsh and fish.
  • Reorder sections so that Bash/Linux examples and requirements are presented before Windows/PowerShell ones, or present all shell types in parallel.
  • Clarify that CLI version requirements apply to all platforms, not just PowerShell users.
  • Include troubleshooting tips for Linux users (e.g., file permissions, path differences) where relevant.
  • Avoid assuming Windows as the default environment; use neutral language and structure.
  • Mention and link to Linux-specific installation instructions and shell configuration tips.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias. The only explicit command-line example references a PowerShell cmdlet (`New-AzRoleAssignment`), and the guidance for automation is centered on PowerShell usage. There are no CLI (az), Bash, or Linux-native examples provided. Additionally, references to tools and patterns (such as Azure portal and PowerShell) are presented without Linux equivalents or parity, and Windows-centric tools are mentioned before any cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI (az) command examples for role assignment and other automation tasks, alongside or before PowerShell examples.
  • Include Bash scripting examples where automation is discussed, especially for Linux users.
  • Explicitly mention cross-platform compatibility for tools and commands, and provide links to Linux-specific documentation where relevant.
  • Where the Azure portal is referenced, clarify that it is accessible from any OS and provide parity for command-line instructions.
  • Review all sections for implicit assumptions of Windows environments and add Linux/macOS notes or alternatives where appropriate.
GitHub Create Pull Request
Digital Twins Troubleshoot CLI parsing failures ...articles/digital-twins/troubleshoot-error-cli-parse.md
High Priority View Details →
Scanned: 2026-01-11 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) when suggesting alternative environments, and refers to escaping with backtick (PowerShell-specific) before mentioning Bash. There is a notable emphasis on Windows tools and patterns, with no Linux-specific examples or detailed guidance for Linux users.
Recommendations
  • Present shell options in a neutral or Linux-first order (e.g., Bash, then PowerShell/CMD).
  • Include explicit Linux/Bash examples for escaping special characters, alongside PowerShell examples.
  • Mention Linux-specific tools or patterns where relevant (e.g., quoting/escaping in Bash).
  • Clarify differences in escaping requirements between Bash and PowerShell, with examples for each.
  • Ensure parity by providing troubleshooting steps tailored for both Linux and Windows environments.
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, it gives explicit version requirements for Azure CLI 'with PowerShell' first, and PowerShell and Windows CMD receive dedicated sections and examples, while Bash is covered but not as extensively. There is a slight prioritization of Windows-centric shells (PowerShell, CMD) and tools, with more detailed examples and tips for those environments, which may suggest a Windows bias.
Recommendations
  • Provide equally detailed examples and tips for Linux shells beyond Bash, such as Zsh or Fish, if relevant.
  • Clarify that Azure CLI is cross-platform and highlight installation and usage on Linux and macOS explicitly.
  • Ensure that Linux/Bash examples are as comprehensive as PowerShell and Windows CMD examples, including edge cases and troubleshooting tips.
  • Add a section on using the CLI in WSL (Windows Subsystem for Linux) and native Linux environments.
  • Avoid mentioning Windows/PowerShell requirements before Linux equivalents unless there is a technical reason.
GitHub Create Pull Request
Digital Twins Create a data history connection ...digital-twins/how-to-create-data-history-connection.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 Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While the majority of CLI examples are written for Bash (Linux/macOS), there are repeated notes and recommendations for using PowerShell and Azure Cloud Shell in PowerShell mode. The documentation explicitly mentions PowerShell as an alternative, but does not provide PowerShell-specific commands or Linux-specific troubleshooting steps. There is no mention of Linux tools or patterns, and troubleshooting advice is sometimes Windows/PowerShell-centric (e.g., MSI errors in Cloud Shell). The documentation does not provide parity for Linux users in terms of examples or troubleshooting.
Recommendations
  • Provide explicit PowerShell command examples alongside Bash commands, or link to a conversion guide.
  • Include troubleshooting steps relevant to Linux environments (e.g., common issues with Bash, Linux authentication, file permissions).
  • Mention Linux-specific tools or patterns where appropriate (e.g., using native Linux shells, environment variable conventions).
  • Balance notes about PowerShell with equivalent notes for Bash/Linux users, ensuring both platforms are equally represented.
  • Clarify that the Azure CLI is cross-platform and provide guidance for both Windows and Linux users in setup and troubleshooting sections.
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 exhibits a mild Windows bias, primarily through the use of PowerShell cmdlet examples (e.g., New-AzRoleAssignment) and references to Windows-centric tools and patterns. The only explicit automation example uses a PowerShell cmdlet, and there is no mention of equivalent Linux/Unix CLI commands (such as Azure CLI or Bash scripts) for role assignment or other administrative tasks. Additionally, Windows tooling is referenced before any cross-platform alternatives, which may lead Linux users to feel unsupported or require additional research.
Recommendations
  • Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for all automation and role assignment tasks.
  • Explicitly mention cross-platform support and tools, such as Bash scripting and Azure CLI, in relevant sections.
  • Ensure that instructions and examples are not Windows-first; present Linux and cross-platform options either first or in parallel.
  • Add troubleshooting and setup guidance for Linux environments where relevant.
  • Include references to documentation or guides for Linux users, such as installing and using Azure CLI on Linux.
GitHub Create Pull Request
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 lists Windows environments (CMD, PowerShell) alongside Linux equivalents (Bash), but Windows shells and PowerShell are mentioned first and more frequently. There is a lack of Linux-specific troubleshooting examples, and the guidance for escaping characters references backslash and backtick (Windows/PowerShell conventions) without explicit mention of Linux/Bash escaping patterns (such as single/double quotes). No Linux-specific tools or patterns are discussed.
Recommendations
  • Provide Linux/Bash-specific examples for escaping characters, including use of single and double quotes.
  • Mention Linux shells (e.g., Bash, Zsh) before or alongside Windows shells to avoid Windows-first ordering.
  • Include troubleshooting steps or examples for common Linux shell parsing issues.
  • Reference Linux tools or conventions (e.g., use of cat for file input, quoting strategies) where relevant.
  • Ensure parity in examples and guidance for both Windows and Linux environments.
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: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it is focused on the Azure CLI (which is cross-platform), several patterns indicate a preference for Windows environments: Cloud Shell (which is Linux-based) is mentioned, but file upload instructions and screenshots are tailored to Cloud Shell's browser interface, which is most familiar to Windows users. There are explicit notes about escaping characters in Bash and PowerShell, but PowerShell-specific issues are mentioned after Bash, and no Linux-specific shell examples (e.g., zsh, fish) are provided. The sample models are from a C# project, which is more common in Windows development. There are no explicit Linux tool references or examples, and the documentation does not provide parity for Linux desktop workflows (e.g., using native Linux file managers, editors, or command-line utilities).
Recommendations
  • Add explicit Linux shell examples (e.g., zsh, fish) and clarify escaping requirements for those environments.
  • Provide instructions and screenshots for uploading files using Linux desktop tools (e.g., Nautilus, Dolphin) and command-line utilities (e.g., scp, wget, curl).
  • Include references to Linux-native editors (e.g., nano, vim, gedit) when instructing users to edit JSON files.
  • Balance PowerShell-specific notes with Bash and other Linux shell notes, and ensure Linux instructions are presented before or alongside Windows instructions.
  • Offer parity for Linux desktop workflows, such as using the Azure CLI directly in a Linux terminal, and clarify any differences in file paths or environment setup.
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: 2026-01-09 00:34
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 explicit examples and escape character guidance. PowerShell is mentioned early in the CLI requirements section, and Windows CMD is given its own section, while Linux-specific shells (e.g., Bash, Zsh) are only briefly covered. There is no mention of Linux distributions, nor examples for other popular shells used on Linux/macOS (e.g., Zsh, Fish). The documentation assumes familiarity with Windows tools and patterns, and PowerShell is referenced before Bash in some places.
Recommendations
  • Add explicit examples for Linux/macOS shells beyond Bash, such as Zsh and Fish, to improve parity.
  • Reorder shell-specific sections so that Bash (Linux/macOS) examples appear before PowerShell and Windows CMD, or group them together without Windows-first ordering.
  • Include notes on Linux-specific considerations, such as file permissions, environment variables, and common shell patterns.
  • Mention that the Azure CLI and its extensions are cross-platform and provide installation instructions for Linux/macOS alongside Windows.
  • Avoid assuming PowerShell usage as the default; clarify that Bash is the default shell on most Linux/macOS systems.
  • Add troubleshooting tips for common issues encountered on Linux/macOS platforms.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias, particularly in the 'Automating roles' section, where PowerShell cmdlets (e.g., New-AzRoleAssignment) are referenced as the primary automation method for role assignment. No equivalent Azure CLI or Linux shell examples are provided, and PowerShell is mentioned before any cross-platform alternatives. The documentation also references Azure portal and Windows-centric tooling, but does not offer parity for Linux or cross-platform command-line usage.
Recommendations
  • Include Azure CLI examples alongside PowerShell cmdlets for role assignment and automation, e.g., az role assignment create.
  • Explicitly mention that Azure CLI is cross-platform and provide sample commands for Linux/macOS users.
  • Where possible, provide Bash or shell script examples for common tasks, not just PowerShell.
  • Add notes clarifying that all features are available on Linux and macOS, and link to relevant cross-platform documentation.
  • Ensure that references to automation tools do not prioritize Windows/PowerShell over Azure CLI or other cross-platform solutions.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-create-data-history-connection.md ...digital-twins/how-to-create-data-history-connection.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While the Azure CLI commands are written for Bash (Linux/macOS), there are multiple notes and tips referencing PowerShell and Windows environments, often mentioning PowerShell before Bash or suggesting adjustments for PowerShell users. There are no explicit Linux-specific examples, troubleshooting steps, or tool recommendations, and the documentation does not acknowledge or provide parity for Linux-specific workflows beyond Bash. The Data Simulator tool is browser-based and platform-neutral, but overall, the documentation assumes a Windows-centric user base and does not provide Linux-first or Linux-only instructions.
Recommendations
  • Add explicit Linux troubleshooting steps and examples, especially for common issues encountered in Linux environments.
  • Provide PowerShell and Bash command variants side-by-side, or link to a conversion guide for CLI commands between Bash and PowerShell.
  • Include notes or sections that address Linux/macOS users directly, such as environment setup, file system differences, or shell-specific nuances.
  • Avoid language that implies PowerShell/Windows is the default or preferred environment; mention Bash and Linux equally or first where appropriate.
  • Reference Linux-native tools or workflows where relevant, such as using native package managers or shell features.
  • Ensure screenshots and portal instructions do not assume Windows-only conventions (e.g., file paths, browser recommendations).
GitHub Create Pull Request
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. While the tutorial is based on the Azure CLI (which is cross-platform), several sections and screenshots reference Cloud Shell, which is browser-based but often associated with Windows users. There is a notable emphasis on handling JSON escaping for PowerShell, with recommendations for using Bash but only minimal guidance for Linux users. Examples and troubleshooting tips are given for PowerShell and Cloud Shell, but there are no explicit Linux-specific examples, screenshots, or troubleshooting steps. The documentation does not mention Linux tools or workflows, and the guidance for file upload and management is tailored to Cloud Shell (often used by Windows users) rather than Linux terminal workflows.
Recommendations
  • Add explicit Linux/Bash terminal examples and troubleshooting steps, especially for JSON escaping and file paths.
  • Include screenshots or instructions for uploading files using Linux CLI tools (e.g., curl, wget, cp) in addition to Cloud Shell.
  • Provide guidance for Linux users on setting up the Azure CLI, including installation steps and environment preparation.
  • Balance PowerShell-specific notes with equivalent Bash/Linux notes, ensuring parity in troubleshooting and usage tips.
  • Mention common Linux tools and workflows where relevant, such as using nano/vim for editing files, or using scp/rsync for file transfer.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/troubleshoot-error-cli-parse.md ...articles/digital-twins/troubleshoot-error-cli-parse.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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) before or alongside Linux equivalents, but does not provide explicit Linux/Bash examples or highlight Linux-specific patterns. The mention of escaping with a backtick is primarily relevant to PowerShell, and Windows environments are given equal or greater prominence than Linux/Bash environments throughout.
Recommendations
  • Add explicit Linux/Bash examples for escaping special characters, such as using backslash for Bash.
  • List Linux/Bash environments first when suggesting alternative shells, or alternate the order to avoid perceived priority.
  • Clarify which escape characters are required for which shell (e.g., backslash for Bash, backtick for PowerShell), and provide examples for both.
  • Include troubleshooting steps or examples specific to common Linux distributions and shells (e.g., Ubuntu Bash, zsh).
  • Ensure parity in tool recommendations, mentioning Linux-native tools (e.g., cat, nano) for file input alongside Windows equivalents.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. The only explicit code example for automating role assignments uses a PowerShell cmdlet (`New-AzRoleAssignment`), which is a Windows-centric tool. There are no CLI (az CLI), Bash, or Linux-native examples provided for role assignment or automation. The mention of PowerShell appears before any alternative tooling, and no Linux equivalents or cross-platform options are discussed. The documentation also references Azure portal and Microsoft tools without mentioning cross-platform or Linux-friendly alternatives.
Recommendations
  • Add equivalent examples using Azure CLI (az) for role assignment and automation, which are cross-platform and widely used on Linux and macOS.
  • When mentioning PowerShell cmdlets, also provide Bash/CLI syntax side-by-side to ensure parity for Linux users.
  • Explicitly state that Azure CLI and REST API options are available and supported on Linux, macOS, and Windows.
  • Review other sections for implicit assumptions of Windows environments and clarify where cross-platform tools can be used.
  • Consider including links to documentation for Azure CLI and REST API usage for relevant tasks.
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: 2026-01-08 00:53
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 tips for Bash, PowerShell, and Windows CMD environments. However, Windows environments (PowerShell and CMD) receive more detailed attention, with PowerShell mentioned before Bash in some sections, and explicit references to Windows CMD. There is a specific CLI version requirement note for PowerShell users, but no equivalent for Bash or other Linux shells. The documentation does not mention Linux-specific shells beyond Bash, nor does it discuss macOS environments.
Recommendations
  • Add explicit notes and examples for Linux and macOS environments, including common shells such as zsh and fish.
  • Ensure that Bash examples are given equal prominence and detail as PowerShell examples.
  • Include any platform-specific installation or troubleshooting notes for Linux/macOS users.
  • Avoid mentioning Windows tools or shells first; alternate the order or group shell-specific guidance by platform.
  • Clarify that the Azure CLI and its extensions are cross-platform and provide links to platform-specific installation guides.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/troubleshoot-error-cli-parse.md ...articles/digital-twins/troubleshoot-error-cli-parse.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation lists Windows-specific shells (CMD, PowerShell) alongside Bash, but Windows environments and PowerShell are mentioned multiple times and sometimes before Linux equivalents. There are no explicit Linux-only examples, and the guidance does not provide parity in shell-specific troubleshooting steps for Linux users. The mention of escaping with a backtick is PowerShell-specific, and the shell options are listed in a way that may prioritize Windows tools.
Recommendations
  • Provide explicit Linux shell (e.g., Bash, Zsh) examples for escaping special characters, including sample commands.
  • List shell options in a neutral order or alternate which platform is mentioned first.
  • Include troubleshooting steps and examples for common Linux shells, not just Windows CMD/PowerShell.
  • Clarify which escaping methods apply to which shells (e.g., backslash for Bash, backtick for PowerShell), and provide links to relevant Linux shell documentation.
  • Add notes or examples for macOS users where applicable.
GitHub Create Pull Request
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: 2026-01-08 00:53
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 a subtle Windows bias. It references Cloud Shell (which is cross-platform but often associated with Azure's web interface), and provides instructions for uploading files using Cloud Shell's GUI, which is more familiar to Windows users. There are several notes about escaping characters in Bash vs. PowerShell, but PowerShell is mentioned specifically and first, with Linux/Bash guidance appearing as an aside. There are no explicit Linux command-line examples for file upload (e.g., using scp, curl, or wget), nor is there guidance for Linux users on handling file paths or permissions. The sample models are from a C# project, which is more common on Windows. Overall, the documentation assumes a Windows-centric workflow and does not provide Linux-specific alternatives or parity in examples.
Recommendations
  • Provide explicit Linux command-line examples for uploading files to Cloud Shell (e.g., using scp, curl, or wget).
  • Include instructions for handling file paths and permissions on Linux systems.
  • Mention Bash/Linux environments first or equally when discussing shell-specific issues (e.g., escaping characters).
  • Add notes or examples for common Linux tools and workflows, such as using the terminal to copy files, rather than relying on GUI upload instructions.
  • Reference sample projects in languages common to Linux environments (e.g., Python) alongside C#.
  • Ensure that all CLI commands and troubleshooting tips are validated for both Windows and Linux shells, and call out any differences clearly.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-ingest-iot-hub-data.md ...n/articles/digital-twins/how-to-ingest-iot-hub-data.md
High Priority View Details →
Scanned: 2025-07-15 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-manage-graph.md ...lob/main/articles/digital-twins/how-to-manage-graph.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-ingest-iot-hub-data.md ...n/articles/digital-twins/how-to-ingest-iot-hub-data.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-manage-graph.md ...lob/main/articles/digital-twins/how-to-manage-graph.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 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.
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
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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).
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/how-to-use-apis.md ...cs/blob/main/articles/digital-twins/how-to-use-apis.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Digital Twins https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/digital-twins/troubleshoot-error-cli-parse.md ...articles/digital-twins/troubleshoot-error-cli-parse.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 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.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →