Azure SQL Edge

41
Total Pages
25
Linux-Friendly Pages
16
Pages with Bias
39.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

25 issues found
Showing 1-25 of 25 flagged pages
Azure SQL Edge 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-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page demonstrates a Windows-first bias. It references SQL Server Management Studio (SSMS) and the New Subscription Wizardβ€”both Windows-only toolsβ€”before mentioning cross-platform alternatives like Azure Data Studio. There are no explicit Linux command-line examples or guidance for Linux-based environments, and the documentation assumes the use of Windows-centric workflows and tools throughout.
Recommendations
  • Provide explicit examples for configuring replication using command-line tools available on Linux, such as sqlcmd or Azure Data Studio's cross-platform features.
  • Mention Azure Data Studio as an equal alternative to SSMS, and provide step-by-step instructions for both tools where possible.
  • Clarify that the described procedures can be performed from Linux environments, and include any necessary prerequisites or differences.
  • If any PowerShell scripts or Windows-specific steps are referenced, add equivalent Bash or shell script examples for Linux users.
  • Add a section or note highlighting support for cross-platform management and any limitations or differences when using Linux.
GitHub Create Pull Request
Azure SQL Edge 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-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates bias towards Windows by exclusively referencing and providing examples for Windows-specific tools such as SQL Server Management Studio (SSMS), SqlPackage.exe, and cmd.exe commands. There are no equivalent instructions or examples for Linux users, such as using Azure Data Studio on Linux, sqlcmd in a bash shell, or Linux-compatible versions of SqlPackage. The ordering of tool recommendations also places Windows tools first, with no mention of Linux alternatives.
Recommendations
  • Include explicit instructions and examples for Linux users, such as using Azure Data Studio or sqlcmd from a bash shell.
  • Provide Linux-compatible SqlPackage usage examples, including installation and command-line usage on Linux/macOS.
  • Mention cross-platform tools (like Azure Data Studio and sqlcmd) before Windows-only tools (like SSMS), or at least present them in parallel.
  • Clarify which tools are cross-platform and which are Windows-only, and provide download links or installation instructions for Linux/macOS where applicable.
  • Where command-line examples are given, provide both Windows (cmd.exe/PowerShell) and Linux (bash) syntax.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/security-overview.md ...blob/main/articles/azure-sql-edge/security-overview.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page shows subtle Windows bias by referencing Windows-specific tools and configuration paths before or instead of Linux equivalents. For example, the 'Client Network Configuration' link points to a Windows-only page, and there are no explicit Linux command examples or Docker-based configuration walkthroughs, despite Azure SQL Edge being primarily deployed on Linux containers. The mention of the absence of 'mssql-conf' utility is present, but there is no compensating Linux-centric guidance or examples.
Recommendations
  • Provide Linux-specific examples for client configuration, such as using sqlcmd or ODBC on Linux, and link to relevant Linux documentation.
  • Include Docker-based configuration and security best practices, as Azure SQL Edge is typically deployed in containers on Linux.
  • Balance references to Windows and Linux tools, ensuring that Linux-first or cross-platform instructions are given equal prominence.
  • When referencing configuration files or utilities, provide explicit Linux paths and examples (e.g., editing mssql.conf on Linux, using environment variables in Docker Compose).
  • Replace or supplement Windows-only links (such as 'Client Network Configuration') with Linux or cross-platform alternatives.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/deploy-kubernetes.md ...blob/main/articles/azure-sql-edge/deploy-kubernetes.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing SQL Server Management Studio (SSMS) as the client tool for connecting to Azure SQL Edge, which is a Windows-only application. There are no examples or mentions of Linux-native or cross-platform tools (such as Azure Data Studio or sqlcmd) for connecting to the SQL Edge instance. The checklist and connection instructions both prioritize SSMS, and there is no guidance for Linux users on how to connect or manage the deployment from non-Windows environments.
Recommendations
  • Include examples and explicit instructions for connecting to Azure SQL Edge using cross-platform tools such as Azure Data Studio and sqlcmd.
  • Update checklists and connection sections to mention both SSMS (Windows) and alternative tools (Linux/macOS/cross-platform) equally.
  • Provide sample connection commands for Linux/macOS terminals using sqlcmd or Azure Data Studio.
  • Where possible, use neutral terminology (e.g., 'Connect with a SQL client') and list both Windows and Linux options.
  • Add a note or section for Linux users, clarifying supported tools and providing installation links.
GitHub Create Pull Request
Azure SQL Edge 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-13 21:37
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 exclusively providing PowerShell scripts for resource deployment, referencing Windows-centric tools (Visual Studio 2019, Azure IoT Edge tools), and omitting equivalent Linux/bash instructions. While some commands use Azure CLI, they are embedded within PowerShell scripts, and there are no standalone bash or Linux shell examples. The prerequisites and workflow assume a Windows environment, making it less accessible for Linux or cross-platform users.
Recommendations
  • Provide equivalent bash/Linux shell scripts for all PowerShell examples, especially for resource deployment steps.
  • List cross-platform tools (such as VS Code with Azure extensions) alongside or before Windows-only tools like Visual Studio 2019.
  • Clearly indicate which steps are platform-specific and offer alternatives for Linux/macOS users.
  • Separate Azure CLI commands from PowerShell scripts and provide standalone CLI/bash instructions.
  • Review and update prerequisites to include Linux-compatible development environments and tools.
GitHub Create Pull Request
Azure SQL Edge 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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing SQL Server Management Studio (SSMS) and the New Subscription Wizardβ€”both Windows-only toolsβ€”when describing how to configure replication. There are no explicit examples or instructions for performing these tasks on Linux, nor is there mention of Linux-specific tools or command-line workflows. The documentation assumes the use of Windows-based SQL Server instances and management tools, with no parity for Linux environments.
Recommendations
  • Include explicit instructions and examples for configuring replication using command-line tools (e.g., sqlcmd) or scripts that work cross-platform, especially on Linux.
  • Mention and provide examples using Azure Data Studio, which is cross-platform, for relevant tasks.
  • Clarify which steps or tools are Windows-only and suggest Linux alternatives where possible.
  • Add a section or callout for Linux users, outlining any differences or additional steps required.
  • Ensure that all example commands and workflows are either cross-platform or have Linux equivalents provided.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/backup-restore.md ...cs/blob/main/articles/azure-sql-edge/backup-restore.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First
Summary
The documentation provides a generally cross-platform approach for Azure SQL Edge, with most local operations using Bash and Docker commands suitable for Linux environments. However, when demonstrating how to generate a SAS token for Azure Blob Storage, the only example provided is a PowerShell script using Azure PowerShell modules, which are primarily Windows-centric. There are no equivalent Bash/Azure CLI examples for Linux or macOS users. Additionally, the documentation consistently refers to connecting via SQL Server Management Studio (SSMS) before mentioning Azure Data Studio, which is more cross-platform, indicating a subtle 'windows_first' bias.
Recommendations
  • Provide equivalent Bash/Azure CLI scripts for generating SAS tokens and managing Azure Storage, ensuring Linux and macOS users can follow along without needing PowerShell.
  • When listing tools for connecting to Azure SQL Edge, mention Azure Data Studio before SSMS or highlight its cross-platform nature.
  • Where possible, ensure that all code examples and instructions are available in both Windows (PowerShell/SSMS) and Linux/macOS (Bash/Azure CLI/Azure Data Studio) formats.
  • Add explicit notes or sections for Linux/macOS users, especially in areas where the workflow differs from Windows.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/deploy-kubernetes.md ...blob/main/articles/azure-sql-edge/deploy-kubernetes.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively referencing SQL Server Management Studio (SSMS) as the client tool for connecting to Azure SQL Edge, which is a Windows-only application. No Linux or cross-platform alternatives (such as Azure Data Studio or sqlcmd) are mentioned. Additionally, the checklist and summary sections both highlight SSMS as the connection tool, reinforcing the Windows-first perspective. There are no examples or instructions for connecting from Linux or macOS environments.
Recommendations
  • Mention and provide examples for cross-platform tools such as Azure Data Studio and sqlcmd for connecting to Azure SQL Edge.
  • Update the checklist and summary sections to reference both SSMS and cross-platform alternatives, e.g., 'Connect with SSMS or Azure Data Studio'.
  • Include connection instructions and screenshots for Linux/macOS users, demonstrating parity with the Windows experience.
  • If possible, provide a table or section listing available client tools for different operating systems.
GitHub Create Pull Request
Azure SQL Edge 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-08 04:23
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 exclusively referencing Azure Data Studio (a GUI tool most commonly used on Windows), using Microsoft SQL Server connection terminology, and omitting any Linux-specific instructions or command-line alternatives. There are no examples or guidance for connecting from Linux environments, nor are cross-platform tools or CLI methods mentioned.
Recommendations
  • Include instructions for connecting to Azure SQL Edge using cross-platform command-line tools such as sqlcmd or Azure CLI.
  • Explicitly mention that Azure Data Studio is available on Linux and macOS, or provide alternative Linux-native tools.
  • Provide example commands for connecting from Linux terminals, including authentication and file path conventions.
  • Balance the documentation by listing Linux-compatible steps alongside Windows GUI steps, ensuring parity for users on all platforms.
GitHub Create Pull Request
Azure SQL Edge 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-08 04:23
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), omitting Linux equivalents or alternatives. There are no command-line or cross-platform instructions for building, pushing, or deploying modules, nor are there examples using Linux-native editors or tools. The workflow assumes a Windows development environment and does not address Linux users' needs.
Recommendations
  • Include instructions for building and pushing IoT Edge modules using cross-platform command-line tools such as Docker CLI and Azure CLI, with example commands for Linux.
  • Mention and provide examples for using VS Code (which is cross-platform) instead of or in addition to Visual Studio 2019.
  • Provide guidance for connecting to Azure SQL Edge using sqlcmd or Azure Data Studio on Linux, including installation and usage notes.
  • Ensure all UI navigation steps in the Azure Portal are clearly marked as browser-based and not OS-specific.
  • Add explicit notes or sections for Linux/macOS users, highlighting any differences or additional requirements.
GitHub Create Pull Request
Azure SQL Edge 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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing Windows tools (ODBC Driver 17 for SQL Server, Azure Data Studio), using Windows-style connection strings, and omitting any Linux-specific instructions or troubleshooting. There are no examples or notes for Linux users regarding driver installation, connection string differences, or alternative tools. The documentation assumes the reader is using Windows, which may hinder Linux users attempting the same workflow.
Recommendations
  • Add explicit instructions for installing ODBC Driver 17 for SQL Server on Linux (e.g., Ubuntu, CentOS), including relevant package manager commands.
  • Mention that Azure Data Studio is cross-platform and provide download/installation links for Linux and macOS.
  • Provide Linux-specific connection string examples, noting any differences in driver naming or path syntax.
  • Include troubleshooting tips for common Linux issues (e.g., driver not found, permissions).
  • Clarify that the workflow is supported on both Windows and Linux, and ensure parity in setup and execution steps.
  • If any steps are Windows-only, clearly label them and offer Linux alternatives where possible.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/security-overview.md ...blob/main/articles/azure-sql-edge/security-overview.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias by referencing Windows-specific tools and patterns before or instead of Linux equivalents. For example, the 'Client Network Configuration' link points to a Windows-specific page, and there are no Linux-specific client configuration instructions. Additionally, while there are some Linux references (e.g., encrypted connections), there are no explicit Linux command-line or configuration examples, and Windows terminology is used by default.
Recommendations
  • Provide Linux-specific client configuration guidance and examples, such as how to configure client network settings on Linux.
  • Include Linux command-line examples (e.g., using sqlcmd or mssql-tools on Linux) alongside or before Windows examples.
  • When referencing configuration utilities or files, clarify the Linux equivalents and provide sample commands or file snippets.
  • Ensure that links and references are balanced between Windows and Linux, or provide parallel links for both platforms.
  • Review terminology to avoid defaulting to Windows-centric language (e.g., 'host computer' instead of 'host system').
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/tutorial-sync-data-sync.md ...ain/articles/azure-sql-edge/tutorial-sync-data-sync.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by requiring a Windows computer for the Data Sync Agent, referencing only Windows-based tools (such as the Data Sync Agent and PowerShell), and omitting any mention of Linux or cross-platform alternatives. There are no instructions or examples for Linux users, nor is there guidance for running the Data Sync Agent or related tooling on Linux systems.
Recommendations
  • Provide explicit guidance on whether the Data Sync Agent can be run on Linux (natively or via compatibility layers such as Wine or containers), or clarify its platform limitations.
  • Include Linux-based examples or alternatives for all steps, such as using Azure CLI or REST APIs where possible, instead of only PowerShell.
  • Mention any cross-platform data sync tools or approaches if available, or suggest workarounds for Linux users.
  • Clearly state platform requirements and, if Windows is mandatory, explain why and provide links to feature requests or roadmap items for Linux support.
GitHub Create Pull Request
Azure SQL Edge 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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing and providing examples for Windows-specific tools (such as SqlPackage.exe and SQL Server Management Studio), omitting Linux equivalents or cross-platform alternatives. There are no examples or instructions for performing the same tasks on Linux, and Windows tools are mentioned first and exclusively.
Recommendations
  • Include instructions and examples for using cross-platform or Linux-native tools (e.g., sqlcmd on Linux, Azure Data Studio on Linux, or Docker CLI commands for interacting with SQL Edge containers).
  • Mention and provide download links for Linux-compatible versions of tools like SqlPackage (which is available for Linux) and show example commands for Linux shells (bash) alongside Windows (cmd).
  • Avoid referencing only Windows-specific tools (like SQL Server Management Studio) or, if referenced, clearly indicate their cross-platform alternatives and usage.
  • When providing command-line examples, offer both Windows (cmd/PowerShell) and Linux (bash) syntax.
  • Explicitly state that Azure Data Studio and sqlcmd are available on Linux and macOS, and provide relevant installation and usage instructions.
GitHub Create Pull Request
Azure SQL Edge 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-08 04:23
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. It exclusively provides PowerShell-based automation scripts for deploying Azure resources, with no equivalent Bash or Linux shell examples. The prerequisites recommend Visual Studio 2019 (a Windows-centric IDE) and Azure PowerShell, and the deployment workflow is described only in terms of PowerShell scripts. While some steps use Azure CLI (which is cross-platform), these are embedded within PowerShell scripts, and there are no standalone Linux/Bash instructions. Linux users are left to adapt the instructions themselves.
Recommendations
  • Provide equivalent Bash/Linux shell scripts for all deployment steps, especially for resource provisioning and automation.
  • List cross-platform tools (e.g., VS Code, Azure CLI) before or alongside Windows-specific tools like Visual Studio.
  • Clearly indicate which steps are cross-platform and which are Windows-only, and offer alternatives where possible.
  • Include a dedicated section or callouts for Linux/macOS users, ensuring parity in setup and deployment instructions.
  • Where PowerShell is used for automation, provide Bash alternatives or reference Azure CLI commands that can be run directly in a Linux shell.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/deploy-dacpac.md ...ocs/blob/main/articles/azure-sql-edge/deploy-dacpac.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation references SQLPackage.exe and SQL Client Tools, which are traditionally Windows-based tools, without mentioning cross-platform or Linux-native alternatives. There are no explicit Linux or cross-platform command-line examples, and the documentation does not clarify how to perform equivalent actions on Linux systems.
Recommendations
  • Explicitly mention that sqlpackage is available as a cross-platform tool and provide installation instructions for Linux and macOS.
  • Include command-line examples for deploying DACPAC/BACPAC using sqlpackage on Linux (e.g., bash commands).
  • Avoid referencing only Windows-specific tools like SQLPackage.exe; instead, use 'sqlpackage' and clarify platform support.
  • If GUI tools are referenced (like Azure Data Studio), clarify their cross-platform availability.
  • Add troubleshooting steps and manual deployment instructions for Linux environments.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/performance-best-practices.md .../articles/azure-sql-edge/performance-best-practices.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily presents platform-agnostic guidance but exhibits subtle Windows bias by referencing SQL Server documentation and best practices that are historically Windows-centric, and by not providing explicit Linux or cross-platform examples for configuration steps. Only at the end is Linux mentioned, and even then, only as a link out rather than as integrated guidance. There are no Linux-specific command-line examples or configuration snippets, and no mention of Linux tools or patterns for managing SQL Edge.
Recommendations
  • Integrate Linux-specific configuration examples (e.g., editing mssql.conf using nano/vi, using systemd for service management).
  • Provide both Windows and Linux command-line examples for common tasks (such as setting memory limits, managing tempdb files, or configuring recovery models).
  • Reference Linux tools and patterns (such as using bash scripts, system resource monitoring with top/vmstat, or Docker commands on Linux).
  • Ensure that links to further reading include both Windows and Linux-focused documentation, or provide parity in the depth of guidance for both platforms.
  • Consider reordering sections so that Linux guidance is not relegated to the end, but is presented alongside or before Windows-centric information, reflecting the cross-platform nature of Azure SQL Edge.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/tutorial-renewable-energy-demo.md ...icles/azure-sql-edge/tutorial-renewable-energy-demo.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation uses generic terms like 'command prompt' and provides no explicit examples or instructions for Linux users. The navigation path uses backslashes (\), which is a Windows convention, and there are no mentions of Linux shells, terminals, or file path formats. There is also no mention of Linux-specific setup steps or troubleshooting, despite Azure SQL Edge being a cross-platform product.
Recommendations
  • Explicitly mention both Windows and Linux environments in setup instructions.
  • Provide parallel examples for opening a terminal/command prompt on both Windows (Command Prompt/PowerShell) and Linux (Terminal/Bash).
  • Use platform-agnostic path separators (or show both Windows and Linux path formats).
  • Include Linux-specific notes for installing Git and navigating directories.
  • Add troubleshooting tips or environment notes for common Linux distributions.
GitHub Create Pull Request
Azure SQL Edge 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
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation assumes the use of Windows-based tools and drivers (such as ODBC Driver 17 for SQL Server and Azure Data Studio) and does not provide any Linux-specific instructions or alternatives. There is no mention of Linux-compatible drivers, nor are there installation or troubleshooting notes for Linux users. All connection strings and tool recommendations are Windows-centric, and there are no examples or guidance for Linux environments.
Recommendations
  • Add explicit instructions for installing and configuring ODBC Driver 17 for SQL Server on Linux, including package manager commands for popular distributions (e.g., apt, yum).
  • Mention and provide links to Linux-compatible versions of Azure Data Studio, and clarify any differences in installation or usage.
  • Include troubleshooting notes for common Linux issues (e.g., driver library paths, permissions).
  • Provide example connection strings and code snippets that work on Linux, including any required environment variables or driver names.
  • Clearly state cross-platform compatibility and highlight any steps that differ between Windows and Linux.
  • If any steps are Windows-only, provide equivalent Linux alternatives or explicitly note the limitation.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/deploy-dacpac.md ...ocs/blob/main/articles/azure-sql-edge/deploy-dacpac.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation references SQLPackage.exe and SQL Client Tools, which are traditionally Windows-based tools, without mentioning their cross-platform availability or Linux alternatives. There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-specific workflows or tools.
Recommendations
  • Clarify that sqlpackage is available cross-platform (Windows, Linux, macOS), and provide instructions or examples for Linux users (e.g., how to install and run sqlpackage on Linux).
  • Avoid referencing only Windows-specific tools like SQLPackage.exe; instead, use 'sqlpackage' and link to cross-platform installation guides.
  • Include Linux command-line examples (e.g., using bash, curl, or az CLI) for uploading files to Azure Blob storage and running sqlpackage.
  • Mention any differences or considerations for Linux users, such as file paths, permissions, or container volume mounts.
  • Ensure parity in instructions and terminology for both Windows and Linux environments throughout the documentation.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/configure.md ...re-docs/blob/main/articles/azure-sql-edge/configure.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for Docker commands, but consistently lists the PowerShell (Windows) example after the Bash (Linux) example. However, the PowerShell examples are present throughout, which may suggest a slight Windows bias. There is also a notable focus on Docker volume mapping caveats for Windows and macOS, but Linux-specific issues are not discussed. No Linux-specific tools or patterns are omitted, and the documentation generally assumes a Linux-style file system layout. There are no missing Linux examples, but the presence of PowerShell examples in every code block may suggest a 'parity' bias toward Windows users.
Recommendations
  • Continue to provide both Bash and PowerShell examples, but clarify when each should be used (e.g., 'For Linux/macOS, use Bash; for Windows, use PowerShell').
  • Consider listing Bash (Linux) examples first, as Azure SQL Edge is primarily Linux-based.
  • Add a brief section or note about common Linux-specific issues or troubleshooting tips, to balance the Windows/macOS caveats.
  • If possible, provide a table or tabbed interface for code examples, allowing users to select their OS/shell, rather than listing both inline.
  • Ensure that any references to file paths or permissions include both Linux and Windows equivalents where relevant.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/tutorial-renewable-energy-demo.md ...icles/azure-sql-edge/tutorial-renewable-energy-demo.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation instructs users to 'open a command prompt' and uses backslashes in file paths, both of which are Windows-centric. There are no explicit Linux or cross-platform instructions or examples, and no mention of Linux-specific tools or terminal usage.
Recommendations
  • Replace 'open a command prompt' with 'open a terminal or command prompt', or specify both Windows and Linux/Mac instructions.
  • Provide both Windows (backslash) and Linux/Mac (forward slash) path examples.
  • Include a note or section for Linux/Mac users, such as using Terminal and navigating with appropriate commands.
  • Verify that all steps and referenced scripts are cross-platform, or provide platform-specific guidance where necessary.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/overview.md ...ure-docs/blob/main/articles/azure-sql-edge/overview.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First
Summary
The documentation page lists several tools for working with Azure SQL Edge, with a notable emphasis on Windows-centric tools such as SQL Server Management Studio (SSMS) and SQL Server Data Tools in Visual Studio, both of which are primarily Windows applications. While cross-platform tools like Azure Data Studio and Visual Studio Code are mentioned, the order of presentation places Windows-only tools before cross-platform alternatives, and there are no Linux-specific examples or guidance. This subtly prioritizes Windows environments and may give the impression that Linux is less supported or an afterthought.
Recommendations
  • Reorder the list of tools to mention cross-platform and Linux-compatible tools (Azure Data Studio, Visual Studio Code) before Windows-only tools (SSMS, SQL Server Data Tools).
  • Explicitly state which tools are available on Linux and provide links or instructions for installing them on Linux.
  • Include Linux-specific usage examples or references, such as command-line tools (sqlcmd, Azure CLI) and Docker/Kubernetes deployment instructions tailored for Linux environments.
  • Add a section or callout highlighting best practices for Linux users, including troubleshooting tips or common issues encountered on Linux platforms.
  • Ensure parity in documentation by providing equal detail and prominence to Linux-compatible workflows and tools.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/performance-best-practices.md .../articles/azure-sql-edge/performance-best-practices.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page predominantly provides platform-agnostic guidance but demonstrates subtle Windows bias by referencing SQL Server documentation and best practices that are historically Windows-centric, without providing explicit Linux or cross-platform examples. Only at the end is Linux mentioned, and even then, only as a link to another page, with no in-place Linux-specific configuration examples or commands.
Recommendations
  • Provide explicit Linux-based examples for configuration steps, such as editing mssql.conf or setting Docker memory limits using Linux command-line tools.
  • Balance references to SQL Server documentation with links to Linux-specific or cross-platform resources.
  • Include Linux shell command examples alongside any configuration recommendations, not just links.
  • Move the 'Linux OS configurations' section higher in the document or integrate Linux-specific notes throughout, rather than as an afterthought.
  • Where Windows-centric concepts or defaults are mentioned (e.g., tempdb practices), clarify any differences or additional steps needed for Linux deployments.
GitHub Create Pull Request
Azure SQL Edge https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-sql-edge/troubleshoot.md ...docs/blob/main/articles/azure-sql-edge/troubleshoot.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally provides Linux-oriented troubleshooting steps and command examples (e.g., use of sudo, systemctl, bash shells). However, there is a subtle Windows bias in the ordering and phrasing: Windows-specific advice (such as running PowerShell as Administrator and quoting differences in PowerShell) is often mentioned before or more prominently than Linux equivalents. Additionally, PowerShell is referenced explicitly, and quoting issues in PowerShell are called out, but no equivalent shell-specific advice is given for Linux shells.
Recommendations
  • Ensure that Linux and Windows troubleshooting steps are presented with equal prominence and in parallel structure, rather than mentioning Windows-specific advice first or more prominently.
  • When referencing shell-specific behaviors (such as quoting), provide equivalent advice for both Windows (PowerShell, CMD) and Linux (bash, sh, etc.), or clarify when an issue is platform-specific.
  • If mentioning PowerShell or Windows command prompts, also mention common Linux shells and their behaviors, especially for users who may be less familiar with Linux.
  • Consider providing side-by-side command examples for both Windows and Linux where applicable, especially for common tasks like checking Docker status, running containers, or accessing logs.
  • Review the documentation for any implicit assumptions about the user's platform, and strive for parity in the depth and clarity of instructions for both Windows and Linux users.
GitHub Create Pull Request