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 1151-1175 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/sap-change-data-capture-shir-preparation.md
...ta-factory/sap-change-data-capture-shir-preparation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Windows tools and patterns. All examples, such as editing the hosts file and testing connectivity, use Windows-specific paths and PowerShell commands. There is no mention of Linux equivalents or support, and the installation instructions assume a Windows environment (e.g., use of the SAP .NET Connector and C:\Windows\System32\drivers\etc\hosts).
Recommendations
- Provide Linux-specific instructions for installing and configuring the self-hosted integration runtime, if supported.
- Include Linux equivalents for connectivity testing (e.g., using 'nc' or 'telnet' instead of PowerShell's Test-NetConnection).
- Show how to edit the hosts file on Linux (typically /etc/hosts) alongside the Windows example.
- Clarify whether the SAP .NET Connector and the integration runtime are supported on Linux, and if not, explicitly state the platform requirements at the top of the documentation.
- If only Windows is supported, add a clear note to avoid confusion for Linux users.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/ssis-azure-files-file-shares.md
.../articles/data-factory/ssis-azure-files-file-shares.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation consistently assumes a Windows environment: all file path examples use Windows syntax (e.g., C:\abc.txt, UNC paths), and authentication instructions reference Windows authentication exclusively. There are no examples or guidance for Linux-based file systems, authentication methods, or path formats, and no mention of Linux-compatible alternatives for file access or integration.
Recommendations
- Include examples of file paths and shares using Linux/Unix conventions (e.g., /mnt/share/abc.txt, SMB/CIFS mounts on Linux).
- Document how to connect Azure-SSIS IR to file shares using Linux authentication methods (such as SMB with username/password or Kerberos, if supported).
- Clarify whether Azure-SSIS IR supports Linux-based nodes or only Windows, and if Linux is supported, provide equivalent instructions.
- Add notes or sections for users running SSIS packages developed or executed in cross-platform environments, highlighting any differences or additional configuration steps.
- Provide links to documentation on mounting Azure Files or on-premises shares from Linux systems, if relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/quickstart-create-data-factory-rest-api.md
...ata-factory/quickstart-create-data-factory-rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All code examples use PowerShell cmdlets (e.g., Invoke-AzRestMethod, Connect-AzAccount), and the prerequisites explicitly require Azure PowerShell installation. There are no examples or guidance for using cross-platform tools such as Azure CLI, curl, or HTTP libraries in other languages. The only tool mentioned for interacting with Azure Storage is Azure Storage Explorer, which, while cross-platform, is presented in a way that assumes a GUI workflow. There is no mention of Linux or macOS command-line workflows, and no alternative shell or scripting examples are provided.
Recommendations
- Provide equivalent examples using Azure CLI (az rest, az login, etc.), which is cross-platform and widely used on Linux/macOS.
- Include REST API invocation examples using curl or HTTPie, which are available on all platforms.
- Add notes or sections for Linux/macOS users, clarifying that PowerShell Core is available cross-platform, but also offering native shell alternatives.
- Mention and demonstrate the use of platform-agnostic tools for authentication and resource management.
- Reorganize the documentation to present cross-platform or platform-neutral approaches first, or at least in parallel with PowerShell.
- Explicitly state that the steps can be performed from any OS, and provide guidance for users who may not have or want to use PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/scenario-ssis-migration-rules.md
...articles/data-factory/scenario-ssis-migration-rules.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-centric bias. It references Windows-specific tools (e.g., cmdkey), discusses Windows authentication and environment variables, and uses Windows terminology (UNC paths, registry, %TEMP%) without mentioning Linux equivalents or providing Linux/Unix examples. There are no examples or guidance for Linux-based SSIS deployments or cross-platform considerations.
Recommendations
- Include Linux/Unix equivalents for environment variables (e.g., $TMPDIR) and file paths.
- Provide examples or notes for handling authentication and environment variables in Linux-based SSIS IR scenarios.
- Mention whether features like registry access, UNC paths, or Windows authentication are relevant or supported in Linux environments, and suggest alternatives where appropriate.
- If cmdkey or other Windows tools are referenced, provide Linux alternatives (such as keyring or credential storage solutions).
- Clarify whether the Azure-SSIS IR supports Linux-based execution, and if so, provide parity in documentation examples and troubleshooting.
- Add explicit notes when a feature or workaround is Windows-only, and suggest Linux-compatible approaches if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/security-and-access-control-troubleshoot-guide.md
...tory/security-and-access-control-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: troubleshooting steps and examples (such as using PsPing, editing the Windows hosts file, and referencing Windows file paths) are exclusively Windows-centric. There are no equivalent Linux commands or instructions provided, and Windows tools (e.g., PsPing.exe, Notepad) are mentioned without Linux alternatives. This may hinder Linux users from effectively following the guidance.
Recommendations
- For every Windows-specific command (e.g., PsPing, editing C:\Windows\System32\drivers\etc\hosts), provide equivalent Linux commands (e.g., use 'ping', 'nc', or 'curl'; edit /etc/hosts with nano or vi).
- When referencing file paths or tools, include both Windows and Linux variants side by side.
- If using screenshots or examples, offer both Windows and Linux UI/CLI where applicable.
- Explicitly mention that the instructions apply to both Windows and Linux, or clarify any OS-specific limitations.
- Consider adding a section or callout for Linux troubleshooting steps, especially for common operations like network diagnostics and file editing.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/solution-template-delta-copy-with-control-table.md
...ory/solution-template-delta-copy-with-control-table.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing SQL Server and Azure SQL Database (both Microsoft/Windows-centric), using T-SQL syntax, and omitting any examples or guidance for Linux-based database systems (such as MySQL, PostgreSQL, or MariaDB). No mention is made of Linux command-line tools, shell scripts, or non-Windows database management patterns. The instructions and screenshots assume a Windows-oriented workflow and do not provide parity for Linux users.
Recommendations
- Include examples for popular Linux-based databases (e.g., MySQL, PostgreSQL) alongside SQL Server.
- Provide equivalent SQL and stored procedure code for MySQL and PostgreSQL.
- Mention and demonstrate how to create and manage control tables and stored procedures in Linux environments.
- Add notes or sections on connecting to Linux-hosted databases from Azure Data Factory.
- Balance the order of presentation so that Linux and open-source database options are mentioned alongside or before Windows-specific ones.
- Include screenshots or CLI examples that are relevant to Linux users (e.g., using Bash, psql, or mysql command-line tools).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/self-hosted-integration-runtime-auto-update.md
...factory/self-hosted-integration-runtime-auto-update.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples are provided in PowerShell, and the only automation scripts use Windows-centric tools (PowerShell, Azure CLI in PowerShell context). There are no Linux shell (bash) equivalents or references to Linux-specific usage patterns. The documentation assumes the use of the 'self-hosted integration runtime client', which is a Windows application, and does not mention Linux installation, management, or monitoring options. Windows tools and patterns are presented exclusively and before any mention (if any) of Linux alternatives.
Recommendations
- Provide equivalent bash (Linux shell) command examples for all PowerShell scripts, especially for Azure CLI usage.
- Explicitly mention whether the self-hosted integration runtime supports Linux, and if so, provide Linux installation and management instructions.
- If the integration runtime is Windows-only, clarify this early in the documentation to set user expectations.
- Include screenshots or instructions for Linux environments, if supported.
- Avoid assuming the use of Windows tools (e.g., PowerShell, Windows client UI) as the only management method; reference cross-platform tools where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/ssis-integration-runtime-ssis-activity-faq.md
...-factory/ssis-integration-runtime-ssis-activity-faq.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools, file paths, and troubleshooting steps (e.g., SSMS, C:\ProgramData, Visual C++ runtime, NT AUTHORITY accounts, and Windows authentication). There are no Linux-specific troubleshooting steps, examples, or mentions of Linux file paths or authentication patterns. All examples and instructions assume a Windows environment, with no parity for Linux users.
Recommendations
- Include troubleshooting steps and examples for Linux-based self-hosted integration runtime scenarios, if supported.
- Reference cross-platform tools or provide Linux equivalents for Windows-specific tools (e.g., alternatives to SSMS, Visual C++ runtime, or Windows authentication).
- Use neutral or dual file path examples (e.g., /var/log/ssis or C:\ProgramData\SSISTelemetry) where possible.
- Clarify in the introduction or prerequisites if only Windows environments are supported, or explicitly state the lack of Linux support.
- If Linux is not supported, add a clear note to inform users and avoid confusion.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/source-control.md
...ocs/blob/main//articles/data-factory/source-control.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a mild Windows bias. PowerShell and SDK are mentioned as primary programmatic interfaces for making changes to Data Factory, with no mention of Linux-native tools or CLI alternatives. Windows-specific tools and patterns (e.g., PowerShell, Azure Portal UI, Microsoft Edge browser) are referenced, and troubleshooting steps and notes often assume a Windows environment. There are no explicit Linux or cross-platform command-line examples, and the documentation does not highlight parity for Linux users.
Recommendations
- Include Azure CLI examples alongside or instead of PowerShell for programmatic interactions, as Azure CLI is cross-platform.
- Mention that both PowerShell and Azure CLI are available, and provide links to relevant documentation for both.
- When referencing browser compatibility issues (e.g., Microsoft Edge), clarify if there are any issues or recommendations for Linux browsers (e.g., Chrome, Firefox on Linux).
- Add notes or sections for Linux/macOS users, especially for tasks like authentication, repository connection, and troubleshooting.
- Avoid assuming the use of Windows tools or UI patterns; where possible, use neutral language or provide parity for Linux environments.
- Explicitly state that all features are available regardless of OS, or note any exceptions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/ssis-integration-runtime-management-troubleshoot.md
...ry/ssis-integration-runtime-management-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing PowerShell cmdlets as the primary method for error retrieval, recommending the use of SSMS (SQL Server Management Studio, a Windows-only tool) for troubleshooting, and mentioning .cmd scripts (a Windows batch file format) as the default for custom setup. There are no Linux or cross-platform command-line examples, nor are Linux-native tools or scripting formats (such as Bash or .sh scripts) mentioned. The documentation assumes a Windows environment for local testing and management tasks.
Recommendations
- Provide equivalent Azure CLI and/or Bash examples alongside PowerShell cmdlets for error retrieval and management.
- Mention and provide guidance for using cross-platform SQL tools (e.g., Azure Data Studio, sqlcmd) in addition to SSMS.
- Allow and document the use of .sh (Bash) scripts for custom setup, and clarify how to use them in SSIS IR environments.
- Explicitly state support for Linux/macOS environments where applicable, and include troubleshooting steps relevant to those platforms.
- Review all tool and script recommendations to ensure Linux users are not excluded from management or troubleshooting workflows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-enable-remote-access-intranet-tls-ssl-certificate.md
...rial-enable-remote-access-intranet-tls-ssl-certificate.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments. All command-line examples use PowerShell, and certificate management instructions rely on Windows-specific tools (MMC snap-in, Integration Runtime Configuration Manager). There are no Linux or cross-platform instructions or examples, and all terminology and screenshots are Windows-centric.
Recommendations
- Provide equivalent Linux instructions for all steps, including obtaining FQDNs (e.g., using `hostname -f`), generating certificates (e.g., using OpenSSL), and installing certificates (e.g., using `update-ca-certificates` or relevant Linux certificate stores).
- Include Linux command-line examples alongside PowerShell, clearly labeling each.
- Mention and demonstrate how to configure the integration runtime on Linux, if supported, or explicitly state Windows-only support.
- Reference cross-platform certificate formats and providers, not just those supported by Windows Server.
- Add troubleshooting steps for Linux environments, such as checking certificate installation and permissions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/transform-data.md
...ocs/blob/main//articles/data-factory/transform-data.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation references both Windows and Linux in the context of HDInsight clusters, but it often lists Windows before Linux (e.g., 'Windows/Linux-based HDInsight cluster'), which subtly prioritizes Windows. The only explicit tooling example in the 'Related content' section is a Spark tutorial using PowerShell, a Windows-centric tool, with no Linux/bash equivalent provided. There are no command-line examples or walkthroughs for Linux users, and .NET custom activities are highlighted without mention of cross-platform alternatives.
Recommendations
- When mentioning supported platforms, list Linux before or alongside Windows to avoid implicit prioritization (e.g., 'Linux/Windows-based HDInsight cluster').
- Provide equivalent tutorials and examples using bash or other Linux-native tools alongside PowerShell examples.
- Include references to cross-platform SDKs or scripting languages (such as Python) when discussing custom activities, not just .NET.
- In the 'Related content' section, add links to tutorials that use Linux command-line environments or tools.
- Explicitly state platform parity where it exists, and call out any platform-specific limitations or differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-hybrid-copy-powershell.md
...ticles/data-factory/tutorial-hybrid-copy-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell. All command-line examples use PowerShell, and the installation and configuration steps for the self-hosted integration runtime are exclusively for Windows. There are no instructions or examples for Linux or cross-platform alternatives. Windows tools (such as SQL Server Management Studio and Notepad) are referenced, and file paths use Windows conventions. Linux users are not provided with equivalent steps or guidance.
Recommendations
- Provide equivalent command-line examples using Azure CLI and/or Bash scripts for Linux and macOS users.
- Document the availability (or lack) of self-hosted integration runtime on Linux, and if not available, state this clearly and suggest alternatives (such as using Azure-hosted IR or Docker-based solutions if supported).
- Include instructions for creating and editing JSON files using cross-platform editors (e.g., nano, vim, VS Code) and use platform-agnostic file paths.
- Reference SQL Server tools available on Linux (e.g., Azure Data Studio, sqlcmd) for database setup and queries.
- Add a section or callout at the beginning clarifying platform support and linking to Linux/macOS-specific guidance if available.
- Where possible, use neutral language and ordering (e.g., 'On Windows, do X; on Linux, do Y') rather than assuming a Windows environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/transform-data-using-stored-procedure.md
.../data-factory/transform-data-using-stored-procedure.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page focuses exclusively on SQL Server, Azure SQL Database, and Synapse Analytics, which are typically associated with Windows environments. There are no examples or mentions of Linux-based SQL engines (such as SQL Server on Linux, PostgreSQL, or MySQL), nor are there any CLI or scripting examples for Linux (e.g., Bash). The only tutorial referenced is for PowerShell, a Windows-centric tool, and there is no mention of Linux equivalents or cross-platform command-line usage. The guidance for installing the Self-hosted integration runtime assumes a Windows environment, with no mention of Linux installation or support.
Recommendations
- Include examples or references for running SQL Server on Linux, or clarify cross-platform support for the Self-hosted integration runtime.
- Provide Linux/Bash-based examples for invoking stored procedures or managing pipelines, alongside PowerShell.
- Reference tutorials or documentation that use cross-platform tools (such as Azure CLI or REST API) rather than only PowerShell.
- Mention support for other SQL engines commonly used on Linux (if applicable), or clarify the Windows-centric scope if intentional.
- Explicitly state platform requirements and provide parity in instructions for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-control-flow.md
...b/main//articles/data-factory/tutorial-control-flow.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. All code examples and setup instructions are based on Visual Studio (Windows-only), the .NET SDK, and PowerShell/NuGet Package Manager Console. Prerequisites and tooling exclusively mention Windows tools such as Visual Studio and Azure Storage Explorer, with no mention of Linux or cross-platform alternatives. There are no instructions or code samples for Linux or macOS users, nor are any cross-platform development environments or SDKs (such as Python or Java) referenced.
Recommendations
- Add equivalent instructions and code samples for Linux and macOS users, such as using VS Code or JetBrains Rider as the IDE, and the .NET Core SDK (which is cross-platform) instead of Visual Studio 2019.
- Provide command-line instructions for installing the required NuGet packages using the dotnet CLI (e.g., 'dotnet add package ...'), which works on all platforms.
- Mention and provide examples for using cross-platform tools such as Azure CLI and azcopy for interacting with Azure Storage, in addition to or instead of Azure Storage Explorer.
- Include alternative code samples using other supported SDKs (such as Python or Java) that are popular and well-supported on Linux.
- Explicitly state which steps are Windows-specific and offer Linux/macOS alternatives where possible.
- Ensure that all screenshots and UI instructions are either cross-platform or have Linux/macOS equivalents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-transform-data-hive-virtual-network.md
...actory/tutorial-transform-data-hive-virtual-network.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line examples are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux-based workflows. Windows-specific tools and file paths (such as editing the hosts file at C:\Windows\System32\drivers\etc) are referenced without Linux equivalents. The instructions assume the user is operating from a Windows environment, and there is no guidance for users on Linux or macOS.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Include instructions for editing the hosts file on Linux (e.g., /etc/hosts) alongside the Windows path.
- Mention that the self-hosted integration runtime can be installed on Linux (if supported), or clarify OS requirements.
- Add notes or sections for users working from Linux or macOS, including any prerequisites or differences in workflow.
- Where screenshots or UI instructions are given, clarify if they are Windows-specific and provide alternatives for other platforms if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/transform-data-using-custom-activity.md
...s/data-factory/transform-data-using-custom-activity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a significant Windows bias. It provides only PowerShell commands for Azure Batch and Data Factory operations, uses Windows-specific command-line examples (e.g., 'cmd /c', '.exe' applications), and references Windows tools and patterns exclusively or before any Linux equivalents. There are no examples or guidance for Linux users, such as Bash commands, Linux shell syntax, or running Linux executables/scripts in custom activities.
Recommendations
- Include equivalent Bash/CLI examples alongside PowerShell commands for creating and managing Azure Batch accounts and pipelines.
- Provide Linux shell command examples (e.g., '/bin/bash -c', './helloworld.sh') in the 'command' property for custom activities, and clarify how to run Linux executables/scripts.
- Mention that Azure Batch pools can be provisioned with Linux nodes and provide guidance/examples for both Windows and Linux pool configurations.
- When referencing tools (like '.exe' files or 'cmd /c'), also show how to use Linux-native tools and patterns (e.g., shell scripts, ELF binaries).
- Add notes or sections explaining any differences in behavior or setup between Windows and Linux Batch pools, including file paths, permissions, and supported runtimes.
- Ensure that all code snippets and walkthroughs have Linux equivalents or clearly indicate OS-specific steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-hybrid-copy-portal.md
...//articles/data-factory/tutorial-hybrid-copy-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation assumes the user is on Windows, referencing SQL Server Management Studio (SSMS) for SQL Server setup and providing no Linux alternatives or command-line instructions. It does not mention or demonstrate how to perform equivalent steps on Linux (e.g., using Azure Data Studio, sqlcmd, or Linux-based SQL Server installations). The instructions for installing the self-hosted integration runtime also implicitly assume a Windows environment, with no mention of Linux support or setup steps.
Recommendations
- Include instructions for setting up SQL Server and creating tables using cross-platform tools such as Azure Data Studio or sqlcmd, which are available on Linux and macOS.
- Explicitly mention that the self-hosted integration runtime can be installed on Linux (if supported), and provide Linux installation steps or a link to relevant documentation.
- Provide command-line alternatives (e.g., Bash scripts, CLI commands) for steps currently described only via GUI tools that are Windows-centric.
- Add a note clarifying platform support and, where steps differ, provide parallel instructions for Linux users.
- Reference Linux-compatible editors (e.g., nano, vim) in addition to Notepad when instructing users to save keys or configuration values.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-deploy-ssis-packages-azure.md
...es/data-factory/tutorial-deploy-ssis-packages-azure.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages, with no mention of Linux or cross-platform alternatives. All command-line and GUI instructions assume a Windows environment, and there are no examples or guidance for Linux users. PowerShell is referenced for firewall configuration, and Windows authentication is mentioned in related links, further reinforcing the Windows-centric approach.
Recommendations
- Explicitly state the platform requirements for tools like SSDT, SSMS, dtutil, and AzureDTExec, and clarify if they are Windows-only.
- If Linux or cross-platform options exist (e.g., Azure Data Studio, Azure CLI, REST APIs), provide equivalent instructions or examples.
- For command-line utilities, mention any Docker images, Wine compatibility, or alternatives for non-Windows environments if available.
- When referencing PowerShell, also provide Azure CLI or Bash equivalents for firewall and resource management tasks.
- Add a section or note addressing Linux/macOS users, outlining any limitations or workarounds for provisioning and managing Azure-SSIS IR.
- Ensure that related links and further reading include any cross-platform guidance where available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-incremental-copy-change-data-capture-feature-portal.md
...al-incremental-copy-change-data-capture-feature-portal.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a bias toward Windows by exclusively referencing SQL Server Management Studio (SSMS) for database operations, without mentioning or providing alternatives for Linux users (such as Azure Data Studio or sqlcmd). There are no examples or instructions for performing equivalent steps on Linux or macOS platforms, and the only client tool mentioned is a Windows-only application. This may hinder accessibility and clarity for users on non-Windows systems.
Recommendations
- Include alternative instructions using cross-platform tools such as Azure Data Studio or sqlcmd for database operations, alongside or instead of SQL Server Management Studio.
- Explicitly mention that SSMS is Windows-only and provide links or guidance for Linux/macOS users.
- Wherever a tool or UI is referenced (e.g., 'right-click database'), provide equivalent command-line instructions that can be executed on any OS.
- Add a section or notes on how to perform all database-related steps (table creation, enabling CDC, data modification) using command-line tools available on Linux and macOS.
- Ensure screenshots and walkthroughs are not exclusively based on Windows UI; consider including examples from cross-platform tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/standard-premium/troubleshoot-compression.md
...frontdoor/standard-premium/troubleshoot-compression.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (Fiddler, IIS) and configuration steps for Microsoft IIS servers, without mentioning or providing equivalent Linux tools, web servers (e.g., Apache, Nginx), or command-line examples. Browser developer tools are mentioned, but the only server-side troubleshooting guidance is for IIS, and Fiddler is highlighted as a primary tool.
Recommendations
- Include Linux/Unix command-line examples for checking HTTP headers (e.g., using curl or wget).
- Mention and provide steps for common Linux web servers such as Apache (mod_deflate) and Nginx (gzip module) when discussing server-side compression settings.
- List cross-platform tools (e.g., curl, HTTPie, or browser developer tools) before or alongside Windows-specific tools like Fiddler.
- Add troubleshooting steps for Linux-based origins, including how to check and configure compression and handle proxy headers.
- Ensure parity in examples and guidance for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-hybrid-copy-data-tool.md
...rticles/data-factory/tutorial-hybrid-copy-data-tool.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (SQL Server Management Studio), omitting Linux alternatives for SQL Server management, and implicitly assuming a Windows environment for the installation of the self-hosted integration runtime. There are no instructions or examples for performing the same steps on Linux systems, nor are cross-platform tools or command-line alternatives mentioned.
Recommendations
- Include instructions for managing SQL Server from Linux, such as using Azure Data Studio or sqlcmd, and provide installation links for these tools.
- Clarify that the self-hosted integration runtime can be installed on Linux (if supported), or explicitly state platform limitations and provide workarounds.
- Add Linux-specific examples for connecting to SQL Server, creating databases/tables, and running queries (e.g., using sqlcmd or Azure Data Studio on Linux).
- When referencing tools like Notepad, suggest cross-platform alternatives (e.g., VS Code, nano, gedit).
- Explicitly mention platform support and provide parallel steps for both Windows and Linux users throughout the tutorial.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-certificate-requirements.md
...nline/azure-stack-edge-gpu-certificate-requirements.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific certificate providers (Microsoft RSA/Schannel Cryptographic Provider), defaulting to Windows export settings (3DES from Windows 10/Server 2016), and only providing next steps for certificate creation using Azure PowerShell cmdlets and the Azure Stack Hub Readiness Checker tool (both Windows-centric). There are no Linux or cross-platform examples or tools mentioned for certificate creation, export, or management.
Recommendations
- Include Linux-based examples for certificate creation and export, such as using OpenSSL commands.
- Mention cross-platform certificate providers or clarify if only Microsoft-specific providers are supported.
- Provide guidance for exporting PFX certificates with the required settings from Linux/macOS environments.
- Add alternative next steps for Linux/macOS users, such as using OpenSSL or Azure CLI.
- Clarify any platform-specific limitations or requirements explicitly, so non-Windows users are aware.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-certificates-overview.md
...x-online/azure-stack-edge-gpu-certificates-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by primarily referencing Azure PowerShell and Windows-centric tools for certificate creation and management. Instructions and links for certificate generation and management are focused on PowerShell, with no mention of Linux or cross-platform alternatives (such as OpenSSL). Additionally, verification steps and UI instructions assume a Windows environment (e.g., right-clicking certificates), and there are no Linux-specific examples or guidance.
Recommendations
- Provide equivalent Linux and cross-platform instructions for certificate creation and management, such as using OpenSSL commands.
- Include examples and links for generating and converting certificates on Linux/macOS, not just via PowerShell or Windows tools.
- When referencing certificate verification steps (e.g., checking Key Usage), include instructions for Linux (e.g., using openssl x509 -text).
- Avoid assuming a Windows UI (such as right-clicking certificates); offer CLI-based alternatives.
- Ensure all referenced tools (e.g., Readiness Checker) are available or have alternatives for Linux/macOS, or clearly state platform limitations.
- Where possible, present Windows and Linux instructions side-by-side or in parallel sections to ensure parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-incremental-copy-multiple-tables-portal.md
...ry/tutorial-incremental-copy-multiple-tables-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (SQL Server Management Studio), assuming SQL Server as the on-premises source, and omitting any Linux-based alternatives or instructions. There are no examples or guidance for users running SQL Server on Linux, nor for using cross-platform tools (such as Azure Data Studio or sqlcmd). All setup and verification steps are described using Windows-centric workflows and terminology.
Recommendations
- Include instructions and examples for users running SQL Server on Linux, such as connecting via Azure Data Studio or sqlcmd.
- Mention and provide steps for using cross-platform tools (Azure Data Studio, sqlcmd) alongside SQL Server Management Studio.
- Clarify that SQL Server can run on both Windows and Linux, and provide any necessary Linux-specific prerequisites or commands (e.g., installation, firewall, service management).
- When referencing file paths, authentication, or environment setup, include Linux equivalents or note any differences.
- Add a section or callout for Linux users, highlighting any platform-specific considerations for self-hosted integration runtime installation and connectivity.