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 1901-1925 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/change-data-capture-troubleshoot.md
...icles/data-factory/change-data-capture-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively provides SQL Server (a Microsoft/Windows-centric database) examples and troubleshooting steps, with all code snippets and instructions tailored to SQL Server's T-SQL and system stored procedures. There are no examples, troubleshooting steps, or tool mentions for Linux-based databases or environments (such as PostgreSQL, MySQL, or command-line tools commonly used on Linux). No PowerShell is present, but the overall focus is on Windows-native tooling and patterns.
Recommendations
- Include equivalent examples for popular Linux-based databases that support change data capture, such as PostgreSQL (using logical replication or wal2json) or MySQL (using binlog).
- Provide troubleshooting steps and queries for Linux environments, including relevant command-line tools (e.g., psql, mysql CLI).
- Mention cross-platform considerations, such as how to enable CDC on non-SQL Server sources and any differences in resource configuration.
- If the CDC resource is only compatible with SQL Server, explicitly state this limitation and provide guidance or links for users of other platforms.
- Add notes or examples for configuring and troubleshooting CDC in environments where SQL Server is running on Linux, if supported.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/concepts-roles-permissions.md
...n//articles/data-factory/concepts-roles-permissions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation references PowerShell as the only command-line interface for managing Azure Data Factory permissions, with no mention of cross-platform alternatives such as Azure CLI, Bash, or Linux-specific workflows. This suggests a bias toward Windows environments and tools, and may leave Linux or macOS users without clear guidance.
Recommendations
- Include Azure CLI examples alongside or instead of PowerShell for all command-line instructions, as Azure CLI is cross-platform and works on Windows, Linux, and macOS.
- Explicitly mention that PowerShell Core is available cross-platform, or clarify when examples are Windows-specific.
- Provide Bash or shell script examples where appropriate, especially for common tasks like role assignment.
- Reference both Windows and Linux environments when discussing SDK usage or automation, ensuring parity in instructions and tool recommendations.
- Add a section or note about managing Azure Data Factory permissions from Linux/macOS, including any relevant tools or differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-azure-sql-database.md
.../articles/data-factory/connector-azure-sql-database.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing SQL Server Management Studio (SSMS) as the tool for connecting to Azure SQL Database for administrative tasks, without mentioning cross-platform or Linux-native alternatives. There are no explicit PowerShell or Windows command-line examples, but the exclusive mention of SSMS and lack of Linux/macOS tooling or CLI examples may disadvantage Linux users.
Recommendations
- When instructing users to connect to Azure SQL Database for administrative tasks (e.g., creating users, running T-SQL), mention cross-platform tools such as Azure Data Studio, sqlcmd, or Azure CLI, alongside or instead of SQL Server Management Studio.
- Provide example commands using sqlcmd or Azure CLI for tasks like connecting to the database and running T-SQL, especially in sections where SSMS is referenced.
- Explicitly state that administrative steps can be performed from Linux, macOS, or Windows, and link to documentation for cross-platform tools.
- Where screenshots or UI walkthroughs are provided, consider including or referencing equivalent experiences on non-Windows platforms, if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/about-upgrade-circuit-bandwidth.md
...ticles/expressroute/about-upgrade-circuit-bandwidth.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation lists PowerShell as a primary method for upgrading circuit bandwidth, and it appears before Azure CLI, which is more commonly used on Linux. There are no explicit Linux-specific examples or references, and the ordering of methods (portal, PowerShell, then CLI) subtly prioritizes Windows-centric tools.
Recommendations
- Provide explicit Linux command-line examples using Azure CLI, and clarify that Azure CLI is cross-platform.
- Reorder the list of upgrade methods to list Azure CLI before PowerShell, or present them in parallel to avoid implying priority.
- Add a note that all management operations can be performed from Linux, macOS, or Windows using Azure CLI.
- Where possible, include bash shell snippets or references to Linux environments to reinforce cross-platform support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-hubspot.md
.../blob/main//articles/data-factory/connector-hubspot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references Windows support explicitly when discussing the self-hosted integration runtime, without mentioning Linux support or providing Linux-specific instructions. There are no examples or guidance for Linux users, and the prerequisites link only discusses Windows versions.
Recommendations
- Explicitly state whether Linux is supported for the self-hosted integration runtime, and provide a link to Linux prerequisites if available.
- Add Linux-specific setup instructions or clarify if the connector is Windows-only.
- Include examples or notes for Linux users where relevant, especially in sections discussing prerequisites and runtime environments.
- If Linux is not supported, clearly state this limitation early in the documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-odbc.md
...ocs/blob/main//articles/data-factory/connector-odbc.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation assumes the use of Windows environments for ODBC integration, particularly in references to installing 64-bit ODBC drivers and using the Integration Runtime Configuration Manager for diagnostics, which is a Windows-only tool. There are no examples or guidance for Linux-based Integration Runtime hosts, nor any mention of Linux-specific ODBC driver installation or troubleshooting steps.
Recommendations
- Add explicit instructions and examples for installing and configuring 64-bit ODBC drivers on Linux-based Integration Runtime hosts.
- Document how to troubleshoot ODBC connectivity issues on Linux, including command-line tools (e.g., isql, unixODBC) and relevant log file locations.
- Clarify whether the Integration Runtime Configuration Manager is available on Linux, and if not, provide alternative diagnostic steps for Linux environments.
- Ensure that all example connection strings and DSN setup instructions include Linux-compatible patterns and references to unixODBC.
- Add a section or note highlighting cross-platform considerations, especially for organizations running Self-hosted Integration Runtime on Linux servers.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-rest.md
...ocs/blob/main//articles/data-factory/connector-rest.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation exhibits mild Windows bias, primarily through the explicit mention of Windows-centric tools (Visual Studio, PowerShell's Invoke-RestMethod) as recommended options for testing REST API requests. These tools are listed before or instead of cross-platform or Linux-native alternatives. No Linux or cross-platform command-line tools (such as curl or httpie) are suggested, and no Linux-specific examples are provided. However, the majority of the documentation is platform-neutral, focusing on Azure Data Factory UI and JSON configuration.
Recommendations
- When suggesting tools for testing REST APIs, include cross-platform and Linux-native options such as 'curl' and 'httpie' alongside Visual Studio and PowerShell.
- Rephrase the tip to present tool options in a platform-neutral order, e.g., 'You can use tools like curl, httpie, PowerShell's Invoke-RestMethod, Visual Studio, or a web browser to validate.'
- Wherever possible, provide example commands for both Windows (PowerShell) and Linux/macOS (bash/curl) environments.
- Review other documentation pages for similar tips or examples and ensure Linux parity in tool recommendations and sample commands.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-odata.md
...cs/blob/main//articles/data-factory/connector-odata.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Windows authentication is listed as a primary authentication method alongside Basic and Anonymous, and the Windows authentication example is provided before service principal or API key examples. The documentation also references Windows-specific patterns (e.g., domain\user format for usernames). However, there are no explicit PowerShell examples or exclusive reliance on Windows-only tools, and the overall content is mostly platform-neutral JSON configuration. Linux authentication methods and patterns are not mentioned, and there is no discussion of Linux-specific considerations or parity.
Recommendations
- Explicitly mention Linux compatibility for all authentication types, especially for Basic and Anonymous authentication.
- Clarify whether Windows authentication is supported from non-Windows (Linux) self-hosted integration runtimes, and provide guidance or alternatives if not.
- Add examples or notes for configuring OData linked services from Linux-based integration runtimes, including any differences in username formats or authentication support.
- Balance the order of authentication examples so that Windows authentication is not always listed before Linux-compatible options.
- If certain authentication types (e.g., Windows authentication) are only supported on Windows, clearly state this and suggest alternatives for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-shopify.md
.../blob/main//articles/data-factory/connector-shopify.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references support for Windows versions in the context of the self-hosted integration runtime, but does not mention Linux support or provide Linux-specific instructions or examples. There are no Linux or cross-platform command-line examples, and the only platform-specific mention is for Windows.
Recommendations
- Explicitly state whether Linux is supported for the self-hosted integration runtime and provide a link to Linux prerequisites if available.
- Add Linux-specific instructions or notes where platform requirements are discussed.
- Include examples or references for Linux users, such as how to set up the integration runtime on Linux if supported.
- Ensure parity in documentation by mentioning both Windows and Linux where platform support is relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-postgresql.md
...ob/main//articles/data-factory/connector-postgresql.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments, particularly in the section describing ODBC SSL verification with the Self Hosted Integration Runtime (SHIR). It exclusively references Windows file paths (e.g., C:\Windows\ServiceProfiles\DIAHostService\AppData\Roaming\postgresql\root.crt) and only provides instructions for setting up DSN and certificates on Windows servers. There are no equivalent instructions or examples for Linux-based SHIR hosts, nor is there mention of Linux file paths or configuration patterns.
Recommendations
- Add parallel instructions for configuring ODBC SSL verification on Linux-based SHIR hosts, including the typical file paths for root.crt (e.g., /home/<user>/.postgresql/root.crt or /etc/ssl/certs).
- Clarify whether the SHIR is supported on Linux and, if so, provide explicit steps for DSN and certificate setup on Linux.
- Wherever file paths or system-specific instructions are given, provide both Windows and Linux variants, or clearly state platform limitations.
- Include examples or notes for Linux administrators to ensure parity and inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-sap-business-warehouse-open-hub.md
...a-factory/connector-sap-business-warehouse-open-hub.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by requiring the installation of the SAP .NET Connector (a Windows-only component) on the Self-hosted Integration Runtime machine, with no mention of Linux alternatives or support. There are no Linux-specific instructions, tools, or examples provided, and the prerequisites implicitly assume a Windows environment.
Recommendations
- Explicitly state OS requirements and limitations for the Self-hosted Integration Runtime and SAP .NET Connector, clarifying that only Windows is supported if that is the case.
- If possible, provide or reference Linux-compatible alternatives for SAP connectivity, such as the SAP Java Connector (JCo) or other cross-platform connectors.
- Include a section or note addressing Linux users, outlining any workarounds, limitations, or roadmap for Linux support.
- Ensure that future documentation includes parity in examples and instructions for both Windows and Linux environments, or clearly state when this is not feasible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-sap-business-warehouse.md
...icles/data-factory/connector-sap-business-warehouse.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific system paths (e.g., %windir%\system32) for SAP NetWeaver RFC SDK library placement and does not provide equivalent instructions or troubleshooting steps for Linux environments. There are no Linux-specific examples or guidance for installing dependencies or configuring the integration runtime on Linux hosts.
Recommendations
- Add explicit instructions for installing and configuring the SAP NetWeaver RFC SDK on Linux, including typical library paths (e.g., /usr/lib, /opt/sap, etc.).
- Include troubleshooting tips for Linux environments, such as verifying shared library placement and permissions.
- Mention any differences in required dependencies or environment variables between Windows and Linux for the Self-hosted Integration Runtime.
- Provide example commands or scripts for Linux (e.g., shell commands for copying libraries or setting environment variables).
- Ensure that all references to system paths or tools are accompanied by Linux equivalents where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-troubleshoot-dynamics-dataverse.md
...a-factory/connector-troubleshoot-dynamics-dataverse.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references XrmToolBox, a Windows-only tool, as a recommended troubleshooting utility for Dynamics 365 connectors. There are no equivalent Linux or cross-platform tools mentioned, nor are there any command-line or scripting examples (e.g., PowerShell, Bash) for either platform. This creates a bias toward Windows environments and leaves Linux users without clear guidance or alternatives.
Recommendations
- Identify and recommend cross-platform or Linux-compatible tools for troubleshooting Dynamics 365 connectors, such as using REST APIs, Postman, or open-source alternatives.
- If XrmToolBox is essential, clarify its Windows-only nature and suggest how Linux/Mac users might access similar functionality (e.g., via Wine, virtual machines, or alternative tools).
- Provide troubleshooting examples or scripts using cross-platform tools (e.g., curl, Python, or .NET Core CLI) where possible.
- Explicitly state platform requirements for any recommended tools and offer parity in guidance for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/continuous-integration-delivery-improvements.md
...actory/continuous-integration-delivery-improvements.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides only Windows-style (C:\...) path examples for npm commands and does not show equivalent Linux/macOS examples (e.g., /home/user/...). While the YAML pipeline uses 'ubuntu-latest' as the build agent, all explicit command-line examples use Windows paths, which may confuse or exclude Linux/macOS users.
Recommendations
- For every command-line example using a Windows path (e.g., C:\DataFactories\DevDataFactory), provide an equivalent Linux/macOS example (e.g., /home/user/DataFactories/DevDataFactory) alongside.
- Add a note clarifying that the npm commands work on all platforms and that users should use the appropriate path format for their OS.
- Wherever possible, use environment variables or relative paths in examples to improve cross-platform clarity.
- Explicitly mention that the tools and scripts are cross-platform and tested on both Windows and Linux build agents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-xero.md
...ocs/blob/main//articles/data-factory/connector-xero.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Windows versions as prerequisites for the self-hosted integration runtime, but does not mention Linux support or provide Linux-specific instructions. There are no Linux or cross-platform examples for generating private keys or running the integration runtime, and the only command-line example (openssl) is generic and not contextualized for Linux users.
Recommendations
- Explicitly state whether the self-hosted integration runtime supports Linux, and if so, provide installation and configuration instructions for Linux environments.
- If only Windows is supported, clarify this limitation early in the documentation.
- Provide Linux-specific examples for generating private keys (e.g., using openssl on Linux), including command-line usage and file handling.
- Wherever prerequisites or environment requirements are listed, include both Windows and Linux (if supported), or explain the platform limitations.
- Ensure parity in troubleshooting and operational guidance for both Windows and Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/control-flow-expression-language-functions.md
...-factory/control-flow-expression-language-functions.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is largely platform-neutral in its examples and explanations, focusing on Azure Data Factory/Synapse expression syntax and JSON. However, there is a recurring Windows bias in the references to time zone names and formatting: the documentation repeatedly refers users to 'Microsoft Time Zone Values' and links to Windows-specific time zone documentation. The time zone names used in examples (e.g., 'Pacific Standard Time') are Windows-style, and there is no mention of IANA/Olson time zone identifiers, which are standard on Linux and other non-Windows systems. This may cause confusion or extra work for Linux users. There are no PowerShell or Windows command-line examples, but the time zone handling is Windows-centric.
Recommendations
- Document whether only Windows time zone names are supported, or if IANA/Olson time zone identifiers can be used. If so, provide Linux-friendly examples.
- If only Windows time zones are supported, explicitly state this limitation and provide guidance for Linux users on how to map IANA time zones to Windows time zones (e.g., via a mapping table or link to a converter).
- Where time zone names are referenced, mention both Windows and IANA/Olson equivalents, or provide a cross-reference.
- Review all links and references to ensure they are not exclusively Windows-focused when cross-platform alternatives exist.
- Consider adding a note or section clarifying time zone handling for users on Linux or macOS environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/copy-clone-data-factory.md
...main//articles/data-factory/copy-clone-data-factory.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references a pattern for sharing SelfHosted Integration Runtime that is published specifically for PowerShell, which is a Windows-centric tool. There are no examples or references to Linux or cross-platform command-line tools (such as Azure CLI or Bash scripts) for cloning or managing Data Factory resources. This may hinder Linux users or those preferring cross-platform tooling.
Recommendations
- Provide equivalent guidance and examples using Azure CLI and/or Bash scripts for all operations currently described with PowerShell.
- When linking to patterns or external guides (such as for sharing SelfHosted Integration Runtime), ensure that Linux-compatible instructions are included or referenced alongside PowerShell.
- Explicitly mention cross-platform alternatives (e.g., Azure CLI, REST API) wherever PowerShell is referenced.
- Add a section or callout clarifying that all steps can be performed from Linux/macOS environments using supported tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/copy-activity-performance-features.md
...les/data-factory/copy-activity-performance-features.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias, particularly in the 'Staged copy' section, where firewall configuration examples and port references are given specifically for Windows (e.g., 'Windows firewall') before mentioning general or cross-platform scenarios. There are no explicit Linux or cross-platform command-line examples, and the only firewall example is Windows-centric. However, the overall content is largely platform-agnostic and does not rely heavily on Windows-specific tools or PowerShell.
Recommendations
- When discussing firewall configuration, provide Linux/Unix equivalents (e.g., iptables, ufw) alongside Windows Firewall instructions.
- Use cross-platform language when referring to operating system features (e.g., 'operating system firewall' instead of 'Windows firewall').
- If providing examples or instructions that involve system configuration, include both Windows and Linux variants.
- Consider adding a note or section on deploying and optimizing Self-hosted Integration Runtime on Linux, as it is supported.
- Ensure that any references to tools or system settings are not Windows-specific unless necessary, or provide parity for other platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/ensure-tags-exists-on-new-virtual-machines.md
...ent-grid/ensure-tags-exists-on-new-virtual-machines.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation exclusively uses PowerShell scripts and AzureRM modules for automation, with no mention of Bash, CLI, or Linux-based approaches. All code samples and instructions assume a Windows-centric workflow, omitting Linux-native tools or guidance.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands and Bash scripts for Linux users.
- Include notes or sections on how to import and use automation modules in Linux environments.
- Clarify that Azure Automation runbooks can be authored in Python or PowerShell, and provide a Python example.
- Mention cross-platform compatibility and highlight any differences in steps for Linux/macOS users.
- Link to documentation on using Azure Automation and Event Grid from non-Windows platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/data-migration-guidance-overview.md
...icles/data-factory/data-migration-guidance-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias by mentioning Windows Installer (MSI) as an authentication method for enterprise-grade security, without referencing equivalent Linux-native authentication or installation methods. There are no code examples, but the only tool-specific reference is Windows-centric. No Linux-specific tools or patterns are mentioned, and there is no guidance for Linux users regarding authentication or installation.
Recommendations
- Mention Linux-native authentication and installation options alongside Windows Installer (MSI), such as using service principals, managed identities, or package managers (e.g., apt, yum) for self-hosted integration runtime setup.
- If referencing MSI, clarify that it is a Windows-specific installer and provide equivalent instructions or links for Linux environments.
- Include examples or documentation links for setting up self-hosted integration runtime on Linux, if supported.
- Review security and credential management sections to ensure Linux and cross-platform parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/enable-customer-managed-key.md
...//articles/data-factory/enable-customer-managed-key.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows environments by referencing PowerShell and Azure CLI together, but does not provide explicit command-line examples for either, nor does it mention or provide Linux-specific guidance or screenshots. All UI instructions and screenshots are based on the Azure Portal, which is platform-agnostic, but there is a lack of parity in addressing Linux command-line workflows or tools. The documentation does not mention Linux shell commands, nor does it clarify cross-platform compatibility for CLI instructions.
Recommendations
- Explicitly provide both Windows PowerShell and Linux/Bash Azure CLI command examples for key operations such as enabling Soft Delete and Do Not Purge on Key Vault.
- Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample commands in Bash syntax.
- Include at least one example using a Linux shell (e.g., Bash) for generating or uploading keys to Azure Key Vault.
- If screenshots are shown for the Azure Portal, clarify that the portal is accessible from any OS.
- Add a section or note on how to perform all steps using only command-line tools on Linux, for users who prefer or require non-GUI workflows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/guidance-for-byod-approach.md
...n//articles/data-factory/guidance-for-byod-approach.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation assumes the use of Self-Hosted Integration Runtime (SHIR), which is a Windows-only tool, and provides no guidance or examples for Linux environments. There are no references to Linux equivalents, installation steps, or troubleshooting, and all instructions implicitly target Windows users.
Recommendations
- Explicitly state that SHIR is only supported on Windows, and provide alternatives or workarounds for Linux users if available.
- If Linux support is planned or possible (e.g., via Docker or Azure IR), include detailed instructions for Linux environments.
- Add examples and troubleshooting steps for both Windows and Linux platforms, or clarify platform limitations early in the documentation.
- Mention any cross-platform options (such as Azure Integration Runtime) and compare them to SHIR, so Linux users can make informed decisions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/includes/sql-connector-addtional-connection-properties.md
...ludes/sql-connector-addtional-connection-properties.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references 'integratedSecurity' as using 'the current Windows account credentials' for authentication, without mentioning Linux or cross-platform authentication mechanisms. There are no Linux or cross-platform equivalents or examples provided, and the language assumes a Windows-centric environment.
Recommendations
- Clarify whether 'integratedSecurity' is supported on Linux or non-Windows platforms, and if so, describe the mechanism (e.g., Kerberos, GSSAPI).
- Provide examples or notes for Linux/macOS users regarding authentication options and any differences in behavior.
- Avoid language that assumes Windows as the default environment; instead, specify platform-specific behaviors where relevant.
- If certain features are Windows-only, explicitly state this and suggest alternatives for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/how-to-use-sql-managed-instance-with-ir.md
...ata-factory/how-to-use-sql-managed-instance-with-ir.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively referencing Windows-centric tools and patterns such as SQL Server Management Studio (SSMS) and SQL Agent jobs, without mentioning or providing examples for Linux-based management tools or command-line alternatives. There are no examples or guidance for users working from Linux environments, and some features (like port 3389 and Windows Firewall) are described in a Windows-specific context.
Recommendations
- Include examples and instructions for managing Azure SQL Managed Instance and SSIS from Linux environments, such as using Azure CLI, Azure Data Studio, or cross-platform tools.
- Mention and provide examples for Linux-compatible tools (e.g., Azure Data Studio, sqlcmd) alongside SSMS.
- Clarify when features or instructions are Windows-specific, and offer Linux alternatives where possible.
- For agent jobs and automation, provide examples using Azure Automation, Logic Apps, or cross-platform scripting (e.g., Bash, PowerShell Core) instead of only referencing SQL Agent jobs.
- Review references to Windows Firewall and port 3389 (RDP) to clarify their relevance in cross-platform or cloud-native scenarios, and provide guidance for Linux-based troubleshooting if applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/includes/data-factory-v2-connector-get-started.md
...tory/includes/data-factory-v2-connector-get-started.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation lists Azure PowerShell as a primary tool for performing the Copy activity, which is traditionally associated with Windows environments. Additionally, there is no explicit mention of Linux-specific tools or command-line examples (such as Azure CLI), and the ordering of tools places PowerShell before more cross-platform options.
Recommendations
- Include Azure CLI as a recommended tool, as it is widely used on Linux and macOS.
- Provide explicit Linux command-line examples or references alongside PowerShell.
- Reorder the list to avoid suggesting Windows-centric tools (like PowerShell) before cross-platform or Linux-friendly options.
- Ensure parity in documentation by mentioning both Windows and Linux workflows where applicable.