Data Factory

564
Total Pages
364
Linux-Friendly Pages
200
Pages with Bias
35.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1000 issues found
Showing 526-550 of 1000 flagged pages
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-web-table.md ...blob/main/articles/data-factory/connector-web-table.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 toward Windows by exclusively recommending Microsoft Excel (2016/2013) and Power BIβ€”both Windows-centric toolsβ€”for extracting the index of a table in an HTML page. There are no Linux or cross-platform alternatives mentioned, nor are command-line or open-source approaches provided. The documentation assumes access to Windows environments and Microsoft Office products, which may not be available to Linux users.
Recommendations
  • Provide alternative instructions using cross-platform or Linux-native tools, such as Python scripts (with pandas and BeautifulSoup), curl, or command-line HTML parsers to extract table indices.
  • Include examples or step-by-step guides for Linux users, ensuring parity with the Windows/Excel workflow.
  • Mention open-source tools (e.g., LibreOffice Calc, csvkit, or web scraping utilities) that can accomplish the same task on non-Windows platforms.
  • Reorder or supplement the documentation so that Windows-specific tools are not the only or primary method described for key tasks.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-programmatically.md ...main/articles/data-factory/monitor-programmatically.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing REST API examples exclusively in PowerShell, referencing PowerShell and Windows-specific tools throughout, and omitting equivalent Linux/bash/cURL examples. PowerShell is used as the default scripting language for REST API and dedicated PowerShell sections, with no mention of cross-platform alternatives. This may hinder Linux users or those working in non-Windows environments.
Recommendations
  • Add REST API examples using bash and cURL to complement the existing PowerShell scripts, ensuring Linux and macOS users have clear guidance.
  • Explicitly mention that PowerShell examples are Windows-centric and provide equivalent bash/cURL commands where possible.
  • Reorganize sections so that cross-platform or OS-neutral examples (e.g., Python, REST API with cURL) are presented before or alongside Windows-specific tools.
  • Where PowerShell is used, note if it can be run cross-platform (e.g., PowerShell Core), or clarify any Windows-only dependencies.
  • Include a table or note summarizing which tools and SDKs are available and supported on different operating systems.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-portal.md ...actory/create-azure-ssis-integration-runtime-portal.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by referencing PowerShell for backup configuration, mentioning Windows authentication for on-premises data stores, and using Windows-centric patterns (UNC paths, SSMS, and File System linked services). There are no Linux-specific instructions or examples, and alternative Linux tools or workflows are not discussed.
Recommendations
  • Provide equivalent Linux CLI examples (e.g., using Azure CLI, Bash scripts) alongside or instead of PowerShell instructions, especially for tasks like configuring backup storage redundancy.
  • Clarify whether features such as file system access, SSMS management, and UNC paths are supported or have alternatives on Linux-based environments.
  • Include guidance for connecting to on-premises data stores from non-Windows environments, such as using Kerberos or other authentication methods available on Linux.
  • Mention and link to cross-platform tools (e.g., Azure Data Studio) where SSMS is referenced.
  • Explicitly state platform requirements or limitations where Windows-specific tools or patterns are necessary, and suggest Linux-compatible alternatives where possible.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/manage-azure-ssis-integration-runtime.md .../data-factory/manage-azure-ssis-integration-runtime.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page provides detailed instructions and code samples exclusively using Azure PowerShell cmdlets, which are most commonly used and natively supported on Windows. There are no equivalent examples or guidance for Linux users (e.g., using Azure CLI, Bash, or cross-platform scripting). The focus on PowerShell and absence of Linux-oriented tools or examples indicates a Windows-centric bias.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, and provide installation or usage notes if PowerShell is required.
  • Where possible, provide Bash script examples or REST API calls to demonstrate reconfiguration and deletion tasks in a platform-agnostic way.
  • Ensure that any references to tools or scripting environments include both Windows and Linux options, or clarify cross-platform compatibility.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-sample-script.md ...ctory/continuous-integration-delivery-sample-script.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell scripts and Azure PowerShell tasks for all CI/CD automation examples, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. All sample code, instructions, and YAML pipeline tasks are PowerShell-centric, and there are no Linux-native or cross-platform examples provided. The documentation assumes the use of PowerShell Core but does not address Linux environments or provide parity for non-Windows users.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for pre- and post-deployment automation, ensuring Linux users have clear guidance.
  • Explicitly mention that PowerShell Core is cross-platform and provide instructions for running scripts on Linux agents.
  • Include YAML pipeline examples that use AzureCLI@2 or Bash tasks alongside AzurePowerShell tasks.
  • Reference or link to documentation on setting up Linux build agents and running deployment scripts in non-Windows environments.
  • Clarify any limitations or differences when running the scripts on Linux versus Windows, and offer troubleshooting tips for Linux users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-hdfs-azure-storage.md ...-factory/data-migration-guidance-hdfs-azure-storage.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 demonstrates a Windows bias by exclusively referencing Windows machines and VMs for installing the Data Factory self-hosted integration runtime, both on-premises and in Azure. There are no examples or guidance for Linux-based installations, nor is there mention of Linux as a supported platform for the integration runtime. This may lead users to believe that only Windows environments are supported or recommended, despite the prevalence of Linux in Hadoop ecosystems.
Recommendations
  • Explicitly mention that the Data Factory self-hosted integration runtime can be installed on Linux (if supported), and provide equivalent instructions and recommendations for Linux environments.
  • Include architecture diagrams and configuration examples that use Linux VMs or machines, especially given the commonality of Linux in Hadoop clusters.
  • When discussing VM sizing and scaling, provide example configurations for both Windows and Linux VMs.
  • Clarify authentication and credential management steps for Linux-based deployments, including any differences in setup or best practices.
  • If Linux is not supported for the integration runtime, clearly state this limitation early in the documentation to set expectations for users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-configure-azure-ssis-ir-enterprise-edition.md ...y/how-to-configure-azure-ssis-ir-enterprise-edition.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 exclusively provides instructions and examples using Azure PowerShell, a Windows-centric tool, with no mention of Linux alternatives or cross-platform CLI options. All provisioning steps and code samples assume a Windows environment, and there is no guidance for users on Linux or macOS platforms.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Clearly indicate whether the Azure-SSIS IR can be provisioned and managed from non-Windows environments, and provide guidance if there are limitations.
  • Include bash or shell script examples alongside PowerShell, or at least reference the Azure CLI documentation for Linux/macOS users.
  • Review references to Windows-specific authentication or configuration steps and provide Linux/macOS alternatives where possible.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-resource-manager-template.md ...ickstart-create-data-factory-resource-manager-template.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows bias by referencing Notepad and Windows file paths (e.g., C:\ADFv2QuickStartPSH), omitting Linux/macOS equivalents for file creation and editing. All command-line cleanup instructions use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. There are no Linux/macOS-specific instructions or screenshots, and Windows-centric patterns are presented as the default.
Recommendations
  • Provide parallel instructions for Linux/macOS users, such as using nano, vim, or other common editors, and using POSIX file paths (e.g., /home/user/ADFv2QuickStart).
  • Include Azure CLI commands (az group delete, az datafactory delete) alongside PowerShell for resource cleanup, and clarify which shell each command is for.
  • Avoid referencing Windows-specific tools (like Notepad) exclusively; suggest cross-platform editors or provide alternatives.
  • Add notes or callouts for platform-specific differences, and ensure screenshots or instructions are not Windows-only.
  • Consider a section or tabbed examples for Windows, Linux, and macOS users to improve accessibility and parity.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-integration-runtime.md ...n/articles/data-factory/monitor-integration-runtime.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a strong Windows bias by exclusively providing PowerShell commands for monitoring integration runtimes, referencing Windows-specific tools and patterns (such as the self-hosted IR being described as running on 'on-premises Windows machine'), and omitting any Linux or cross-platform CLI examples. There is no mention of Bash, Azure CLI, or REST API alternatives, and all code snippets and operational guidance assume a Windows/PowerShell environment.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets, especially for monitoring integration runtimes.
  • Include REST API sample requests and responses for monitoring tasks, to support automation and cross-platform use.
  • Clarify whether self-hosted integration runtime can be installed and monitored on Linux, and if so, provide relevant instructions and examples.
  • When referencing tools or commands, present cross-platform options (e.g., Azure CLI, REST API) before or alongside PowerShell.
  • Avoid language that assumes the self-hosted IR is always on Windows unless this is a technical limitation; if so, state it explicitly.
  • Add Bash shell examples where appropriate, especially for scripting and automation scenarios.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-configure-azure-ssis-ir-custom-setup.md ...factory/how-to-configure-azure-ssis-ir-custom-setup.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All examples, tools, and scripts assume a Windows OS (e.g., .cmd, .bat, .ps1 files, use of msiexec.exe, cmdkey, odbcconf.exe, and PowerShell). There are no Linux or cross-platform examples, and all instructions and sample scripts are Windows-specific. The documentation does not mention or provide alternatives for Linux-based environments, nor does it clarify that Azure-SSIS IR is Windows-only, which may confuse users seeking Linux support.
Recommendations
  • Explicitly state early in the documentation that Azure-SSIS IR is a Windows-based service, and Linux customizations are not supported. This will set clear expectations for cross-platform users.
  • If any Linux or cross-platform support is planned or available (e.g., for other Azure Data Factory runtimes), provide links or references to those options.
  • Where possible, clarify that all script and tool references (e.g., .cmd, .ps1, msiexec.exe) are Windows-specific, and suggest alternatives or workarounds for users on non-Windows platforms (such as preparing scripts on Linux and uploading via cross-platform tools).
  • Add a section or FAQ addressing the lack of Linux support, and direct users to appropriate Azure documentation for Linux-based data integration scenarios.
  • If any steps (such as uploading files to Azure Storage) can be performed with cross-platform tools (e.g., Azure CLI, azcopy), provide those examples alongside Windows-specific ones.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-configure-shir-for-log-analytics-collection.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-configure-shir-for-log-analytics-collection.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 demonstrates a Windows bias by exclusively referencing Windows tools and workflows (e.g., Event Viewer, Windows Performance Counters, Log Analytics agent for Windows), and by omitting any mention of Linux equivalents or instructions for configuring log analytics collection on Linux-based SHIR hosts. All examples and screenshots are Windows-specific, and there is no guidance for Linux users.
Recommendations
  • Add a dedicated section for configuring log analytics collection on Linux-based SHIR hosts, including references to the Log Analytics agent for Linux and relevant documentation.
  • Provide Linux-specific examples for selecting and forwarding logs (e.g., syslog, journald) and performance counters (e.g., using collectd or telegraf).
  • Include screenshots or command-line instructions relevant to Linux environments.
  • Mention both Windows and Linux options in all relevant sections, or clarify if SHIR is only supported on Windows (if that is the case).
  • Ensure parity in troubleshooting and verification steps for both operating systems.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-ssis.md ...e-docs/blob/main/articles/data-factory/monitor-ssis.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Azure PowerShell and Windows-specific tools (SSMS, SSDT, SQL Server Agent) for monitoring and querying SSIS operations, without providing equivalent Linux or cross-platform alternatives. There are no examples or instructions for Linux users, and the only command-line example mentioned is Azure PowerShell, which is primarily associated with Windows environments.
Recommendations
  • Include Azure CLI examples alongside or instead of Azure PowerShell for checking SSIS IR operational status, as Azure CLI is cross-platform.
  • Mention and provide examples for querying logs using cross-platform tools such as Azure Data Studio, which runs on Linux, macOS, and Windows.
  • Clarify whether SSIS monitoring and management tasks can be performed from Linux environments, and if so, provide relevant instructions.
  • When referencing tools like SSMS or SSDT, note their platform limitations and suggest alternatives or workarounds for non-Windows users.
  • Ensure that all monitoring and alerting workflows described can be executed from Linux or cross-platform environments, or clearly state any limitations.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/join-azure-ssis-integration-runtime-virtual-network.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/join-azure-ssis-integration-runtime-virtual-network.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by referencing Azure PowerShell as the primary or only CLI-based method for provisioning and managing Azure-SSIS IR. There are no examples or mentions of equivalent Linux-friendly tools such as Azure CLI or Bash scripting. The related content and step-by-step instructions focus on Azure PowerShell and ADF UI, both of which are more familiar to Windows users, with no parity for Linux command-line environments.
Recommendations
  • Include equivalent Azure CLI (az) commands alongside or in place of Azure PowerShell examples for all provisioning and management tasks.
  • Add explicit instructions or links for performing tasks using Bash or cross-platform scripting environments.
  • Ensure that all references to command-line tooling mention both Azure PowerShell and Azure CLI, with examples for each.
  • Review related content and tutorials to provide Linux-friendly workflows, not just Windows-centric ones.
  • Clarify in the documentation that both Windows and Linux users are supported, and provide troubleshooting tips relevant to both environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/scenario-ssis-migration-overview.md ...icles/data-factory/scenario-ssis-migration-overview.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 demonstrates a Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, dtexec, DMA) and workflows, without mentioning Linux-compatible alternatives or providing Linux-specific guidance. All examples and tool references assume a Windows environment, and there is no discussion of how to perform these tasks on Linux or cross-platform environments.
Recommendations
  • Include information about running SSIS-related command-line utilities (such as dtexec, dtutil) on Linux, if supported, or clarify their platform limitations.
  • Mention and provide guidance for any cross-platform or Linux-compatible tools for SSIS package management and migration, or explicitly state if such tools are not available.
  • If SSMS/SSDT are required and only available on Windows, suggest alternatives for Linux users (such as Azure Data Studio, if applicable) or provide remote access strategies.
  • Add a section or notes addressing Linux users, outlining what is and isn't possible from non-Windows environments and any workarounds.
  • Ensure that any scripts or automation examples are provided in a cross-platform manner (e.g., PowerShell and Bash, where possible).
GitHub Create Pull Request
Data Factory 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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows-centric bias by referencing Windows authentication, Windows environment variables, registry entries, UNC paths, and Windows-specific tools (e.g., cmdkey) without providing equivalent Linux/Unix guidance or examples. There is a lack of parity in addressing Linux scenarios, and the documentation assumes a Windows environment for SSIS workloads and migration steps.
Recommendations
  • Provide equivalent Linux/Unix examples or guidance where Windows-specific features (e.g., environment variables, authentication, registry, UNC paths) are discussed.
  • Clarify whether SSIS Integration Runtime supports Linux-based execution, and if not, state this explicitly.
  • If Linux is not supported, briefly explain why and provide alternative approaches for cross-platform compatibility.
  • For sections referencing Windows tools (e.g., cmdkey), mention if there are Linux equivalents or note their absence.
  • When discussing file paths, include examples using both Windows (UNC/absolute) and Linux (POSIX) path formats.
  • For environment variables, explain how to set and use them in both Windows and Linux contexts, if applicable.
  • Where registry usage is mentioned, suggest Linux alternatives (such as config files) or clarify limitations.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data.md ...docs/blob/main/articles/data-factory/transform-data.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 shows mild Windows bias. In the descriptions of HDInsight activities (Hive, Pig, MapReduce, Streaming), clusters are described as 'Windows/Linux-based', with Windows mentioned first. The Stored Procedure activity only references SQL Server and Azure SQL, which are traditionally Windows-centric, with no mention of Linux-based alternatives. The custom activity section focuses on .NET, a technology historically associated with Windows, and does not provide examples for Linux-native scripting or environments. There are no explicit Linux shell or bash examples, and the only tutorial linked is for Spark with PowerShell, a Windows-first tool.
Recommendations
  • When listing supported platforms (e.g., 'Windows/Linux-based HDInsight cluster'), alternate the order or use 'Linux/Windows-based' to avoid implicit prioritization.
  • Include explicit examples or references for Linux-native tools and scripting (e.g., bash, Python scripts) alongside .NET and PowerShell.
  • For the Stored Procedure activity, mention support for open-source or Linux-based databases if applicable, or clarify platform support.
  • Provide at least one tutorial or example using Linux-native tools (e.g., bash, Python CLI) instead of only PowerShell.
  • In the custom activity section, highlight support for running custom scripts in Linux environments and provide sample code for both Windows and Linux scenarios.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-proxy-ssis.md ...-factory/self-hosted-integration-runtime-proxy-ssis.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All command-line examples are provided exclusively in PowerShell, with no mention of Linux or cross-platform alternatives. The installation and configuration steps assume a Windows environment (e.g., references to Local Security Policy, NT SERVICE accounts, and C:\ProgramData paths). Windows authentication and tools like Visual Studio/SSDT are discussed without Linux equivalents or alternatives. There is no guidance for Linux users, and no mention of whether the self-hosted IR or SSIS proxy features are supported or unsupported on Linux.
Recommendations
  • Clearly state platform support at the beginning of the documentation (e.g., if only Windows is supported, make this explicit).
  • If Linux is supported, provide equivalent Linux/Bash command-line instructions alongside PowerShell examples.
  • Mention Linux-specific considerations for installing drivers, setting up service accounts, and configuring authentication.
  • Provide file path examples and log locations for both Windows and Linux, if applicable.
  • If features are Windows-only, suggest alternatives or workarounds for Linux users, or link to relevant documentation.
  • Consider including a table or section comparing Windows and Linux setup steps, highlighting any differences.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-create-schedule-trigger.md ...rticles/data-factory/how-to-create-schedule-trigger.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the Azure PowerShell section. The PowerShell instructions explicitly reference installing Azure PowerShell on Windows and use Windows-style file paths (e.g., C:\ADFv2QuickStartPSH\MyTrigger.json). The prerequisites for PowerShell only mention Windows installation, omitting cross-platform guidance. While the Azure CLI and SDK sections are platform-neutral, the PowerShell section is both Windows-centric and appears before the CLI section, which is more cross-platform friendly. There are no explicit Linux or macOS examples or notes for PowerShell usage.
Recommendations
  • In the Azure PowerShell section, clarify that Azure PowerShell is cross-platform and provide installation instructions for Linux and macOS, not just Windows.
  • Use platform-neutral file paths in examples (e.g., ./MyTrigger.json or mention both Windows and Linux/macOS path formats).
  • Add a note that PowerShell Core is available on Linux and macOS, and provide links to installation guides for those platforms.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is more commonly used on Linux/macOS.
  • Wherever file paths or shell commands are shown, provide both Windows and Linux/macOS variants, or use variables/placeholders.
  • Explicitly state that all SDKs and CLI tools are cross-platform, and provide any platform-specific caveats if needed.
GitHub Create Pull Request
Data Factory 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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation displays a Windows bias by referencing PowerShell cmdlets as the primary method for troubleshooting, mentioning Windows-specific tools (like SSMS), and omitting Linux equivalents or examples. There are no instructions or troubleshooting steps tailored for Linux users, nor are cross-platform command-line tools or patterns (such as Azure CLI or SQLCMD) presented. The guidance assumes a Windows environment for local testing and management.
Recommendations
  • Include Azure CLI examples alongside or instead of PowerShell cmdlets for cross-platform compatibility.
  • Mention and provide examples for using SQLCMD or Azure Data Studio, which are available on Linux, instead of only referencing SSMS.
  • Explicitly state whether the troubleshooting steps are applicable to both Windows and Linux environments, and provide Linux-specific guidance where necessary.
  • When recommending local testing of scripts, clarify how to do so on Linux (e.g., using bash scripts or compatible shells) and note any differences.
  • Ensure that all references to tools or commands are accompanied by their cross-platform alternatives, and avoid assuming the user is on Windows.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-copy-data-portal.md ...ain/articles/data-factory/tutorial-copy-data-portal.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 demonstrates a subtle Windows bias by referencing Notepad for file creation, omitting Linux/macOS equivalents, and not providing cross-platform command-line instructions for file or data manipulation. The only desktop tool mentioned for interacting with Azure Blob Storage is Azure Storage Explorer, which is cross-platform, but the initial file creation and manipulation steps assume a Windows environment. No Linux shell or macOS Terminal examples are provided, and there is no mention of Linux-native editors or commands.
Recommendations
  • When instructing users to create a text file, provide alternative commands for Linux/macOS (e.g., using echo/cat or nano/vi).
  • Explicitly mention that Azure Storage Explorer is available on Windows, macOS, and Linux.
  • Where file movement or manipulation is required, offer cross-platform command-line examples (e.g., cp/mv for Linux/macOS, copy/move for Windows).
  • Avoid referencing Windows-specific tools (like Notepad) without also listing Linux/macOS equivalents.
  • Consider adding a table or callout box with equivalent steps for Windows, Linux, and macOS users.
GitHub Create Pull Request
Data Factory 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 →
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 a Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and managing SSIS packages, with no mention of Linux-compatible alternatives or cross-platform workflows. There are no examples or guidance for Linux users, and the documentation assumes the use of Windows authentication and file system conventions. Windows tools are mentioned first and exclusively throughout.
Recommendations
  • Explicitly state the platform requirements for tools like SSDT, SSMS, dtutil, and AzureDTExec, clarifying that they are Windows-only and suggesting workarounds for Linux users (e.g., using Windows containers, remote desktop, or Azure-hosted VMs).
  • Provide guidance or links for Linux users on how to interact with Azure Data Factory and Azure-SSIS IR, such as using the Azure Portal, REST APIs, or Azure CLI (where applicable).
  • If possible, mention any cross-platform or web-based alternatives for package deployment and management, or clarify the lack thereof.
  • Add a section or notes highlighting the absence of native Linux support for SSIS tooling, and suggest best practices for Linux-based development environments (e.g., using cloud-hosted Windows environments for SSIS tasks).
  • Ensure that any command-line examples or references are clearly marked as Windows-specific, and consider providing equivalent steps (if available) for Linux or macOS users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network-portal.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network-portal.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by requiring Azure PowerShell, referencing Windows file paths (e.g., C:\Windows\System32\drivers\etc), and providing instructions only for Windows environments (such as editing the Windows hosts file). There are no examples or guidance for performing equivalent steps on Linux-based VMs, nor are cross-platform tools or commands (like Azure CLI or Linux file paths) mentioned. This could hinder users working in Linux environments or those preferring non-Windows tooling.
Recommendations
  • Provide equivalent instructions for Linux-based VMs, such as how to edit /etc/hosts for DNS resolution.
  • Include Azure CLI commands as alternatives to Azure PowerShell for all steps, or clarify which steps are cross-platform.
  • Explicitly mention that the self-hosted integration runtime can be installed on both Windows and Linux VMs, and provide installation steps for both.
  • When referencing file paths or system modifications (like editing hosts files), show both Windows and Linux syntax.
  • Review all screenshots and UI references to ensure they are not exclusively Windows-centric, or add Linux equivalents where possible.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-hybrid-copy-portal.md ...n/articles/data-factory/tutorial-hybrid-copy-portal.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 demonstrates a Windows bias by exclusively referencing Windows tools (SQL Server Management Studio), providing setup instructions that assume a Windows environment, and omitting any Linux-specific guidance or alternatives. There are no examples or instructions for Linux users, such as using sqlcmd or Azure Storage CLI tools on Linux, nor is there mention of Linux-compatible SQL Server management or integration runtime installation steps.
Recommendations
  • Add parallel instructions for Linux users, such as using sqlcmd or Azure Data Studio to create databases and tables.
  • Include guidance for installing and configuring the self-hosted integration runtime on Linux (if supported), or clearly state platform limitations.
  • Provide examples of how to interact with Azure Blob Storage using cross-platform tools like Azure CLI or AzCopy, not just via the Azure Portal.
  • Explicitly mention any platform-specific requirements or limitations early in the prerequisites section.
  • Ensure screenshots and step-by-step instructions are inclusive of both Windows and Linux environments where possible.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-spark-portal.md ...s/data-factory/tutorial-transform-data-spark-portal.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by requiring Azure PowerShell for setup, referencing only PowerShell installation instructions, and omitting any Linux or cross-platform CLI alternatives for uploading files or managing resources. No Linux shell or Azure CLI examples are provided, and the prerequisite section assumes a Windows environment by default.
Recommendations
  • Provide equivalent instructions for Linux and macOS users, such as using the Azure CLI (az) for resource management and file uploads.
  • Include examples for uploading files to Azure Blob Storage using cross-platform tools like Azure CLI or AzCopy, not just PowerShell.
  • In the prerequisites, mention both Azure PowerShell and Azure CLI as supported options, and link to installation guides for both.
  • Where scripting or command-line actions are required, present both Windows (PowerShell) and Linux/macOS (bash) command examples side by side.
  • Explicitly state that the tutorial is cross-platform and highlight any steps that are platform-specific.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-vertica.md ...s/blob/main/articles/data-factory/connector-vertica.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, particularly in the 'Install Vertica ODBC driver for the version 2.0' section, where only Windows installation steps and screenshots are provided. There are no instructions or examples for installing the ODBC driver on Linux or macOS, despite Vertica and self-hosted integration runtimes being commonly deployed on Linux servers. The documentation also references Windows-specific tools (e.g., ODBC Data Source Administrator, Start menu) without mentioning Linux equivalents.
Recommendations
  • Add parallel instructions and screenshots for installing the Vertica ODBC driver on Linux (and optionally macOS), including command-line steps (e.g., using rpm, deb, or tar.gz packages).
  • Mention and provide examples for configuring ODBC on Linux, such as editing odbc.ini and odbcinst.ini files.
  • Reference Linux tools and locations (e.g., using isql for testing, typical driver install paths) alongside Windows tools.
  • Clearly indicate in each section whether the instructions apply to Windows, Linux, or both, and provide tabs or callouts for OS-specific steps.
  • Ensure all critical setup and troubleshooting steps are covered for both Windows and Linux environments to support cross-platform parity.
GitHub Create Pull Request
← Previous Page 22 of 40 Next →