Azure Docs

14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2185 issues found
Showing 626-650 of 2185 flagged pages
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/signalr-howto-troubleshoot-method.md ...les/azure-signalr/signalr-howto-troubleshoot-method.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation shows some Windows bias by listing Windows tools (Fiddler) before Linux alternatives (tcpdump), providing more detailed logging instructions for Windows-specific platforms (e.g., Windows Phone 8, .NET client for Windows desktop), and referencing Windows configuration files (web.config) without Linux equivalents. There are no explicit Linux command-line examples or parity in logging/tracing instructions for Linux environments.
Recommendations
  • Present cross-platform tools (e.g., tcpdump, Wireshark) before or alongside Windows tools like Fiddler, and clarify their OS compatibility.
  • Add explicit Linux/macOS examples for collecting network traces and enabling server/client logs, including relevant configuration file locations and commands.
  • Include instructions for enabling logging/tracing in Linux-hosted environments (e.g., systemd, Linux file paths, environment variables).
  • Avoid referencing Windows-specific platforms (e.g., Windows Phone 8) without mentioning Linux/mobile alternatives or clarifying their scope.
  • Where web.config is referenced for .NET/ASP.NET, provide guidance for equivalent settings in Linux deployments (e.g., appsettings.json, environment variables).
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/signalr-howto-troubleshoot-guide.md ...cles/azure-signalr/signalr-howto-troubleshoot-guide.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by referencing Windows-specific tools (such as Fiddler), using Windows-centric debugging instructions (like 'Just My Code' and CLR exceptions in Visual Studio), and omitting Linux equivalents or instructions. There are no examples or troubleshooting steps tailored for Linux environments, containers, or cross-platform .NET development, and all code/configuration samples assume Windows/ASP.NET hosting patterns.
Recommendations
  • Add Linux-specific troubleshooting steps, such as using tcpdump, Wireshark, or curl for network diagnostics.
  • Include instructions for viewing logs and debugging in Linux environments (e.g., using dotnet-trace, journalctl, or VS Code debugging).
  • Mention and provide examples for cross-platform tools (e.g., Wireshark instead of only Fiddler, or browser DevTools for all OSes).
  • Clarify that .NET Core and ASP.NET Core are cross-platform, and provide guidance for running and troubleshooting on Linux and in containers.
  • When referencing configuration files (like web.config), note differences for Linux deployments (e.g., appsettings.json, environment variables).
  • Balance the order of examples so that Linux or cross-platform approaches are presented alongside or before Windows-specific ones.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/signalr-howto-move-across-regions.md ...les/azure-signalr/signalr-howto-move-across-regions.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for moving an Azure SignalR resource using the Azure Portal and Azure PowerShell, with all CLI-based examples and scripts using PowerShell commands and referencing Windows tools (e.g., Notepad). There are no examples using Azure CLI, Bash, or Linux-native editors, and PowerShell is presented as the only scripting option, which may disadvantage Linux or cross-platform users.
Recommendations
  • Add equivalent Azure CLI (az) command examples for exporting, editing, and deploying ARM templates, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include instructions and examples for editing JSON files using cross-platform editors (e.g., nano, vim, code) instead of only referencing Notepad.
  • When referencing file operations or command-line steps, provide both Windows (PowerShell) and Linux (Bash) command examples.
  • Structure sections so that cross-platform or Linux-friendly options (Azure CLI, Bash) are presented alongside or before Windows-specific (PowerShell) instructions.
  • Explicitly state that the steps can be performed on any OS, and provide links to relevant Azure CLI documentation.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/signalr-quickstart-azure-signalr-service-arm-template.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/signalr-quickstart-azure-signalr-service-arm-template.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents deployment instructions in three tabs: Portal, PowerShell, and CLI. PowerShell (a Windows-centric tool) is given equal prominence to the cross-platform CLI, and is listed before CLI in all sections. In the CLI prerequisites, the only Bash shell example given is 'Git Bash' (a Windows-focused tool), and there is no mention of native Linux or macOS shells. There are no explicit Linux/macOS-specific examples or notes, and the documentation assumes familiarity with Windows tools and patterns.
Recommendations
  • In the CLI prerequisites, mention native Bash shells on Linux and macOS, not just Git Bash for Windows.
  • Add explicit notes or examples for Linux and macOS users, especially regarding shell environments and installation steps.
  • Consider listing CLI instructions before PowerShell, as CLI is cross-platform and more widely used outside Windows.
  • Where possible, include screenshots or terminal examples from Linux/macOS environments, not just Windows.
  • Clarify that PowerShell Core is available cross-platform, if relevant, and provide installation links for Linux/macOS.
  • Avoid language that assumes the user is on Windows (e.g., by referencing only Windows tools or patterns).
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/signalr-tutorial-build-blazor-server-chat-app.md ...gnalr/signalr-tutorial-build-blazor-server-chat-app.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing on Visual Studio (a Windows-centric IDE) for project creation, deployment, and debugging, with no mention of cross-platform alternatives or Linux workflows. All UI-based instructions and screenshots are from Visual Studio, and there are no explicit instructions or examples for Linux users (e.g., using VS Code, command-line publishing, or Linux-specific tools). The only cross-platform element is the use of the .NET CLI for project creation and package management, but the overall flow assumes a Windows/Visual Studio environment.
Recommendations
  • Add parallel instructions for Linux/macOS users, such as using VS Code or JetBrains Rider, and provide equivalent command-line steps for project creation, running, and publishing.
  • Include screenshots or terminal output from Linux environments to illustrate cross-platform compatibility.
  • Document how to deploy to Azure App Service using the dotnet CLI or GitHub Actions, not just Visual Studio's Publish feature.
  • Mention how to debug and run the app on Linux (e.g., using dotnet run and browser access), and clarify that <kbd>F5</kbd> is a Visual Studio shortcut, suggesting alternatives for other environments.
  • Reference Linux package managers and installation steps for .NET SDK where appropriate.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/signalr-quickstart-dotnet.md ...n//articles/azure-signalr/signalr-quickstart-dotnet.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented towards Windows development environments. It exclusively lists Windows tools (Visual Studio 2019), assumes use of the .NET Framework (not .NET Core/.NET 5+), and provides instructions only for Visual Studio and PowerShell. There are no examples or guidance for Linux or cross-platform development, such as using VS Code, JetBrains Rider, or command-line .NET CLI workflows. The instructions for package installation use PowerShell and Visual Studio UI, with no mention of Linux-compatible alternatives.
Recommendations
  • Add instructions for setting up and running the sample using .NET Core/.NET 5+ and the cross-platform dotnet CLI.
  • Include Linux/macOS prerequisites, such as installing .NET SDK and using editors like VS Code or JetBrains Rider.
  • Provide package installation instructions using the dotnet CLI (e.g., 'dotnet add package ...') alongside PowerShell/Visual Studio examples.
  • Clarify which steps are Windows-specific and offer equivalent steps for Linux/macOS environments.
  • Mention that the sample can be run on Linux/macOS using Mono or .NET Core if applicable, or clarify if it is Windows-only.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/configure-replication.md ...main//articles/azure-sql-edge/configure-replication.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows-first bias by referencing SQL Server Management Studio (SSMS) and the New Subscription Wizard (both Windows-only tools) as primary configuration methods, without providing equivalent Linux-native instructions or examples. There are no explicit Linux command-line or cross-platform examples, and the documentation assumes the use of Windows-based SQL Server tools for replication setup and management.
Recommendations
  • Include explicit instructions and examples for configuring replication using cross-platform tools such as Azure Data Studio (which is available on Linux) and direct Transact-SQL scripts that can be run from any OS.
  • Provide command-line examples using sqlcmd or Azure CLI, which are available on Linux, for all major steps (creating publications, subscriptions, initializing data).
  • Clearly mention and demonstrate how to perform all required actions from a Linux environment, including any prerequisites or differences in workflow.
  • Avoid referencing Windows-only tools (like SSMS or the New Subscription Wizard) as the primary or only method; instead, present cross-platform or Linux-native methods first or alongside Windows methods.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/backup-restore.md ...s/blob/main//articles/azure-sql-edge/backup-restore.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. While the initial backup and restore examples use bash and Docker commands (which are cross-platform and Linux-friendly), the section on backing up to Azure Blob Storage provides only a PowerShell script for generating SAS tokens and storage credentials, with no Linux/CLI or Azure CLI equivalent. Additionally, the documentation consistently refers to SQL Server Management Studio (SSMS) before Azure Data Studio when describing how to connect to the database, which may suggest a Windows-first approach. There is also an absence of Linux-native tooling or scripting examples for Azure operations.
Recommendations
  • Provide equivalent Azure CLI or Bash scripting examples for generating SAS tokens and storage credentials, not just PowerShell.
  • When mentioning connection tools, list Azure Data Studio before or alongside SSMS, as it is cross-platform.
  • Explicitly mention that all Docker and bash commands work on both Linux and Windows (with WSL or Docker Desktop), and provide any necessary platform-specific notes.
  • Include a note or section for Linux users on how to perform Azure Storage operations using native tools (e.g., az CLI, curl, or Python scripts).
  • Audit for any other Windows-specific terminology or assumptions, and ensure Linux parity throughout the documentation.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/tutorial-sync-data-sync.md ...in//articles/azure-sql-edge/tutorial-sync-data-sync.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows bias by requiring a Windows computer for the Data Sync Agent, mentioning only Windows-based tools (such as PowerShell) for management and automation, and omitting any Linux or cross-platform alternatives or instructions. There are no Linux-specific examples or guidance, and the documentation assumes the user is operating in a Windows environment.
Recommendations
  • Provide explicit guidance on whether the Data Sync Agent can be run on Linux (e.g., via Wine, containers, or native support), or clarify its platform limitations.
  • Include Linux-based examples for setup and management, such as using Azure CLI or bash scripts where possible.
  • If PowerShell is required, mention cross-platform PowerShell Core and provide installation instructions for Linux and macOS.
  • Clearly state platform requirements and, if Windows is mandatory, suggest possible workarounds for Linux users (such as using a Windows VM or container).
  • Add troubleshooting and best practices sections relevant to Linux environments, if supported.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/security-overview.md ...lob/main//articles/azure-sql-edge/security-overview.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing Windows-specific tools and concepts (such as 'Client Network Configuration' for Windows), linking to Windows-focused documentation before Linux equivalents, and omitting Linux-specific configuration or client examples. There is a lack of parity in practical guidance for Linux users, despite Azure SQL Edge being a cross-platform product typically deployed on Linux-based IoT devices.
Recommendations
  • Provide Linux-specific examples and references alongside or before Windows ones, especially for client configuration and networking.
  • Include practical Linux configuration steps or links (e.g., how to configure client connectivity on Linux, using sqlcmd or other Linux-native tools).
  • When referencing tools or configuration guides, ensure both Windows and Linux equivalents are mentioned and linked.
  • Review all external links to ensure Linux documentation is not omitted or relegated to footnotes.
  • Explicitly mention and provide examples for common Linux deployment scenarios, such as Docker on Linux hosts, and how to secure them.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/tutorial-deploy-azure-resources.md ...cles/azure-sql-edge/tutorial-deploy-azure-resources.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell-based deployment scripts, referencing Windows-centric tools (such as Visual Studio 2019), and omitting equivalent Linux shell or bash examples. The instructions assume the use of PowerShell and Windows tooling throughout, with no guidance for users on Linux or macOS platforms.
Recommendations
  • Provide equivalent Bash or shell script examples for all PowerShell scripts, ensuring Linux and macOS users can follow along without needing PowerShell.
  • List cross-platform tools (such as VS Code) before or alongside Windows-only tools like Visual Studio 2019, and clarify which steps are platform-specific.
  • Explicitly mention and link to Linux/macOS installation instructions for prerequisites (e.g., Azure CLI, Docker, Azure Data Studio).
  • Where PowerShell modules are used, offer Azure CLI or REST API alternatives that are platform-agnostic.
  • Add a section or callout for Linux/macOS users, summarizing any differences or additional steps required.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/configure-vsan-esa.md ...blob/main//articles/azure-vmware/configure-vsan-esa.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., Set-vSANDataInTransitEncryption), using 'Run command' patterns typical of Windows/Azure environments, and mentioning Windows Server Failover Clusters as a supported feature. There are no Linux/Unix command-line examples, nor are Linux tools or workflows referenced. The documentation assumes the use of Windows-centric tools and interfaces, with no parity for Linux users.
Recommendations
  • Provide equivalent Linux/Unix command-line examples (e.g., using VMware's govc CLI, REST API, or PowerCLI on Linux).
  • Mention and document how to perform the same operations from a Linux environment, including any required tools or prerequisites.
  • List Linux-based guest OS requirements and considerations alongside Windows-specific features like WSFC.
  • Avoid assuming the use of PowerShell or Windows-only tools; where possible, present cross-platform alternatives first or in parallel.
  • Clarify if any features or commands are only available via Windows tools, and suggest workarounds or alternatives for Linux users.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/deploy-onnx.md ...docs/blob/main//articles/azure-sql-edge/deploy-onnx.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation assumes a Windows environment throughout: it exclusively references Windows-specific tools (ODBC Driver 17 for SQL Server, Azure Data Studio), uses connection strings and drivers tailored for Windows, and does not mention or provide examples for Linux users. There are no instructions for installing required drivers or tools on Linux, nor any mention of Linux-specific considerations or alternatives.
Recommendations
  • Provide explicit instructions for installing ODBC drivers and Azure Data Studio on Linux, including supported distributions and package managers.
  • Include Linux-specific connection string examples (e.g., correct driver names/paths for unixODBC).
  • Mention any differences in behavior or troubleshooting steps for Linux environments.
  • Add a note or section clarifying cross-platform support and any prerequisites for Linux users.
  • Ensure that all tools referenced (such as Azure Data Studio) are available and supported on Linux, and provide download links or installation commands for Linux.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/concepts-apis-sdks.md ...lob/main//articles/digital-twins/concepts-apis-sdks.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. While it generally uses cross-platform Azure CLI commands, it consistently mentions the Azure portal (a web UI, but often associated with Windows-centric workflows) as a primary method. When discussing file uploads, it lists AzCopy (primarily a Windows tool) before the Azure CLI, and does not mention Linux-native tools or provide explicit Linux shell examples. All code and SDK examples are in .NET/C#, with no mention of Python, Java, or other cross-platform SDKs. There are no PowerShell-specific examples, but the overall pattern prioritizes Windows-friendly tools and .NET, with little attention to Linux or open-source developer workflows.
Recommendations
  • When listing upload methods, mention the Azure CLI first, and include Linux-native tools (e.g., curl, Python scripts, or Linux shell commands) as alternatives.
  • Provide explicit Linux shell (bash) command examples for common tasks, such as uploading files or generating tokens.
  • Include SDK usage examples in other supported languages (e.g., Python, Java, JavaScript) to demonstrate cross-platform parity.
  • Clarify that AzCopy and the Azure CLI are available on Linux, and provide installation links or notes for Linux users.
  • When referencing the Azure portal, clarify that it is web-based and platform-agnostic, to avoid the impression of Windows exclusivity.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/troubleshoot.md ...ocs/blob/main//articles/azure-sql-edge/troubleshoot.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally provides Linux-centric troubleshooting steps and examples, especially for Docker and container management. However, there are several instances where Windows and PowerShell are mentioned explicitly, sometimes before or in preference to Linux equivalents. For example, the section on running Docker commands as Administrator on Windows is presented alongside (and sometimes before) Linux sudo instructions. There are also specific notes about PowerShell quoting differences, and references to launching PowerShell as Administrator, which are not matched with equivalent Linux shell guidance. There is little mention of Linux-specific tools or patterns beyond basic Docker and bash usage, and no mention of macOS.
Recommendations
  • Ensure that for every Windows/PowerShell-specific instruction or troubleshooting step, there is a Linux (and optionally macOS) equivalent provided with equal prominence.
  • When discussing command-line examples, present Linux and Windows examples side by side, or clearly label them for each platform.
  • Avoid mentioning Windows tools or patterns (such as running as Administrator or PowerShell quoting) without also providing the analogous Linux shell context (e.g., sudo, bash quoting).
  • Include troubleshooting steps and examples for macOS where applicable, especially for Docker usage.
  • Consider reordering sections so that Linux and Windows instructions are presented in parallel, rather than Windows-first or Windows-only.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/tutorial-run-ml-model-on-sql-edge.md ...es/azure-sql-edge/tutorial-run-ml-model-on-sql-edge.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure Data Studio (a tool with a strong Windows association, though cross-platform), and by providing connection instructions that assume a Microsoft SQL Server workflow typical of Windows environments. There are no explicit Linux command-line examples, nor are Linux-native tools or workflows mentioned. The instructions do not address connecting from Linux environments or using Linux-native SQL clients.
Recommendations
  • Include instructions for connecting to Azure SQL Edge using common Linux tools such as sqlcmd or Azure CLI.
  • Provide examples for opening and running Jupyter notebooks from the Linux command line (e.g., using Jupyter Lab or VS Code on Linux).
  • Explicitly mention that Azure Data Studio is available on Linux and macOS, or suggest alternative Linux-native tools.
  • Add a section or note describing how to perform the same steps in a Linux environment, including any differences in file paths or prerequisites.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/architecture-api-management.md ...//articles/azure-vmware/architecture-api-management.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-centric automation tools (e.g., Azure portal, PowerShell, Azure DevOps) as primary management mechanisms for API Management on Azure VMware Solution. There are no examples or mentions of Linux-native tools (such as Azure CLI, Bash scripting, or cross-platform automation), nor are there instructions or diagrams that show Linux-based workflows.
Recommendations
  • Include examples and references to Azure CLI commands for managing API Management resources, alongside or instead of PowerShell.
  • Mention Bash scripting and Linux automation tools as alternatives to PowerShell for DevOps and administrative tasks.
  • Ensure diagrams and workflow descriptions are tool-agnostic or explicitly mention both Windows and Linux management options.
  • Provide links to cross-platform documentation and tutorials for managing Azure API Management from Linux environments.
  • Review all references to management tools to ensure Linux parity and avoid implying that PowerShell is the only or primary automation option.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/tutorial-set-up-iot-edge-modules.md ...les/azure-sql-edge/tutorial-set-up-iot-edge-modules.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (Visual Studio 2019, Azure Data Studio) and workflows (right-click build/push in Visual Studio), with no mention of Linux equivalents or cross-platform alternatives. There are no command-line or Linux-based instructions for building, pushing, or deploying modules, nor for interacting with Azure SQL Edge. The instructions assume a Windows GUI environment and do not provide parity for Linux users.
Recommendations
  • Provide command-line instructions for building and pushing IoT Edge modules using Docker CLI and Azure CLI, which work on both Windows and Linux.
  • Include examples using Visual Studio Code (which is cross-platform) and/or command-line editors, rather than only Visual Studio 2019.
  • Offer instructions for connecting to Azure SQL Edge using sqlcmd or Azure Data Studio on Linux, and clarify that Azure Data Studio is available cross-platform.
  • Explicitly mention and show how to perform all steps on Linux, including editing files, running builds, and deploying modules.
  • Avoid GUI-only workflows (such as right-clicking in Visual Studio) or provide equivalent CLI steps.
GitHub Create Pull Request
Azure Docs 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-12 23:44
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) as the only example for automating role assignments, without providing equivalent Azure CLI (cross-platform) or Bash examples. There is also a general lack of Linux-specific or cross-platform command-line instructions, and the only automation example is Windows-centric.
Recommendations
  • Provide Azure CLI examples (az role assignment create ...) alongside or before PowerShell cmdlets for role assignment automation.
  • When referencing automation, mention both PowerShell and Bash/CLI options to ensure parity for Linux and macOS users.
  • Include explicit notes or examples for Linux/macOS users where command-line tools or scripts are discussed.
  • Review other sections for implicit assumptions of Windows environments and add cross-platform guidance where appropriate.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/tutorial-sync-data-factory.md .../articles/azure-sql-edge/tutorial-sync-data-factory.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias primarily by referencing and providing examples for Windows-specific tools (such as SqlPackage.exe and .cmd command syntax), without mentioning or providing equivalent instructions for Linux environments. There are no examples or guidance for using Linux-native tools or running these commands in a Linux shell. The order of tool presentation also places Windows tools first, with no Linux parity.
Recommendations
  • Provide Linux equivalents for all command-line tools mentioned (e.g., show how to use sqlpackage on Linux, including installation and usage examples with bash syntax).
  • Explicitly mention cross-platform compatibility for tools like sqlcmd and Azure Data Studio, and provide Linux/macOS installation links and usage instructions.
  • Include bash/zsh shell command examples alongside .cmd examples, and clarify any differences in environment variables or file paths.
  • Avoid referring to tools as .exe unless specifically discussing Windows; use generic tool names where possible.
  • Add a section or callout for Linux users, highlighting any differences or prerequisites for running the tutorial on Linux.
GitHub Create Pull Request
Azure Docs 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-12 23:44
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 dedicated sections and examples, and PowerShell is mentioned early as a primary use case. There is an explicit mention of using Azure CLI with PowerShell as a requirement, and the Windows CMD section is present, but there is no equivalent section for native Linux shells beyond Bash (e.g., zsh, fish), nor is there parity in depth for Linux-specific environments. The order of presentation (Bash, then PowerShell, then Windows CMD) is reasonable, but the focus on PowerShell and Windows CMD, and the explicit mention of PowerShell in requirements, indicate a Windows-first and PowerShell-heavy bias.
Recommendations
  • Add examples and guidance for other common Linux shells (e.g., zsh, fish) if relevant.
  • Clarify that the Azure CLI and its extensions are fully supported on Linux and macOS, not just Windows.
  • In the CLI version requirements, avoid framing PowerShell as the default or primary shell; instead, mention Bash and other shells equally.
  • Ensure that Linux and macOS users are given equal prominence in installation and usage instructions.
  • Consider reordering sections or providing a table that summarizes shell-specific requirements for Bash, zsh, PowerShell, and CMD, to avoid implicit prioritization of Windows environments.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/includes/vcenter-access-identity-description.md ...vmware/includes/vcenter-access-identity-description.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page consistently refers to Windows Server Active Directory as the primary or sole example of identity management integration, with no mention of Linux-based identity sources (such as OpenLDAP) or examples for Linux environments. Windows terminology and tools are mentioned exclusively, and Linux alternatives are not discussed or demonstrated.
Recommendations
  • Include examples and references for integrating Linux-based identity sources, such as OpenLDAP, alongside Windows Server Active Directory.
  • Provide parity in documentation by mentioning both Windows and Linux identity management solutions when discussing user and group assignment.
  • Add explicit instructions or links for configuring vCenter Server with non-Windows LDAP/LDAPS sources.
  • Avoid presenting Windows tools and patterns as the default or only option; instead, present both Windows and Linux options equally.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/azure-vmware-solution-known-issues.md ...les/azure-vmware/azure-vmware-solution-known-issues.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While most of the content is platform-neutral and focused on Azure VMware Solution specifics, there are several instances where Windows tools or patterns are referenced without Linux equivalents. For example, remediation steps for VMware Tools vulnerabilities reference 'VMware Tools for Windows' and provide no mention of Linux or cross-platform guidance. The use of the 'Set-Tools-Repo' Run command is not clarified for Linux guests. There are no explicit Linux or PowerShell command examples, but the language and focus tend to assume a Windows-centric environment.
Recommendations
  • When referencing VMware Tools updates, specify whether the instructions apply to both Windows and Linux guests, or provide separate guidance for each.
  • If using Azure VMware Solution Run commands (e.g., 'Set-Tools-Repo'), clarify their applicability for both Windows and Linux VMs, or provide Linux-specific alternatives if needed.
  • Where issues or vulnerabilities are Windows-specific (e.g., 'VMware Tools for Windows'), explicitly state this and, if relevant, mention the status or steps for Linux guests.
  • Consider including examples or notes for Linux administrators where operational steps might differ.
  • Review documentation for any implicit assumptions of a Windows environment and add clarifications or parity for Linux users.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/configure-vsan.md ...ocs/blob/main//articles/azure-vmware/configure-vsan.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a bias towards Windows environments by exclusively using PowerShell cmdlets for all configuration tasks, referencing Azure portal workflows that are inherently Windows-centric, and mentioning Windows VM prerequisites before Linux. There are no Linux shell or cross-platform CLI examples, and the documentation assumes the use of Windows tools and patterns throughout.
Recommendations
  • Provide equivalent Linux shell (bash) or cross-platform CLI examples for all configuration tasks, not just PowerShell cmdlets.
  • Include instructions for performing these tasks using VMware's native tools (e.g., vSphere CLI, govc) that are available on Linux.
  • When listing prerequisites or requirements, alternate the order of Windows and Linux, or present them together to avoid 'windows_first' bias.
  • Explicitly mention that the Azure portal and Run Command features can be accessed from any OS, and clarify any OS-specific dependencies.
  • Add links or references to VMware documentation that covers Linux-based management and automation approaches.
GitHub Create Pull Request
Azure Docs https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/configure-external-identity-source-nsx-t.md ...ure-vmware/configure-external-identity-source-nsx-t.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing Windows Server Active Directory as the LDAP provider, requiring Windows-specific infrastructure (domain controllers, AD CA), and omitting any examples or guidance for Linux-based LDAP servers (such as OpenLDAP). All prerequisites, examples, and screenshots are centered on Windows environments, with no mention of Linux alternatives or parity.
Recommendations
  • Include examples and instructions for integrating with common Linux-based LDAP servers (e.g., OpenLDAP), including configuration steps and screenshots where possible.
  • Update prerequisites to mention that any standards-compliant LDAP server (not just Windows Server Active Directory) can be used, and provide guidance for both Windows and Linux environments.
  • Provide certificate guidance for Linux LDAP servers (e.g., using OpenSSL or Linux-based CA) in addition to Windows CA instructions.
  • Use neutral language throughout the documentation, such as 'LDAP server' instead of 'Windows Server Active Directory', unless specifically referring to a Windows-only scenario.
  • Add troubleshooting tips and best practices for both Windows and Linux LDAP deployments.
GitHub Create Pull Request
← Previous Page 26 of 88 Next →