Data Factory

1123
Total Pages
968
Linux-Friendly Pages
155
Pages with Bias
13.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

319 issues found
Showing 151-175 of 319 flagged pages
Data Factory Continuous integration and delivery pre- and post-deployment scripts ...ctory/continuous-integration-delivery-sample-script.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
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 CI/CD pre- and post-deployment scripting in Azure Data Factory. All examples, instructions, and YAML pipeline snippets are centered around PowerShell (.ps1 files), with no mention of Bash, shell scripts, or cross-platform alternatives. The installation section references Azure PowerShell, and the only tooling discussed is Windows-centric. There are no Linux/macOS-specific instructions or examples, and the documentation implicitly assumes users are on Windows or using PowerShell Core.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users.
  • Include instructions for running scripts using Azure CLI or Bash tasks in Azure Pipelines.
  • Clarify cross-platform compatibility of PowerShell Core and .ps1 scripts, including any limitations on Linux/macOS.
  • Add notes or sections specifically addressing Linux/macOS environments and how to adapt the workflow.
  • Consider listing Linux/macOS approaches before or alongside Windows/PowerShell methods to reduce perceived bias.
GitHub Create Pull Request
Data Factory Switch activity in Azure Data Factory .../articles/data-factory/control-flow-switch-activity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page provides only PowerShell command examples and assumes the use of Windows file paths (e.g., C:\ADF). There are no CLI, Bash, or cross-platform instructions, nor are Linux/macOS equivalents mentioned. The tutorial links and workflow are centered around Azure PowerShell, which is most commonly used on Windows.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works natively on Linux/macOS.
  • Use generic or platform-agnostic file paths in examples (e.g., /home/user/ADF or ./ADF) alongside Windows paths.
  • Explicitly mention that the workflow can be completed on Linux/macOS and provide step-by-step instructions for those platforms.
  • Include notes or links to installing and using Azure PowerShell on Linux/macOS, or recommend Azure CLI for those users.
  • Reorder examples or provide parallel sections so that Linux/macOS users do not have to adapt Windows-centric instructions.
GitHub Create Pull Request
Data Factory Wait activity ...in/articles/data-factory/control-flow-wait-activity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides sample PowerShell commands and links to a PowerShell-based tutorial, with no equivalent examples or walkthroughs for Linux/macOS users (e.g., Azure CLI, Bash). Windows tools and patterns are mentioned exclusively and before any cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI and Bash examples for pipeline creation and execution.
  • Include links to tutorials or walkthroughs for Linux/macOS users using Azure CLI.
  • Present cross-platform examples (Azure CLI, REST API) alongside PowerShell, or list them first to avoid Windows-first bias.
  • Explicitly state that the Wait activity itself is platform-agnostic, but provide parity in tooling instructions.
GitHub Create Pull Request
Data Factory Web Activity ...ain/articles/data-factory/control-flow-web-activity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias towards Windows by providing a PowerShell-only example for base64-encoding a PFX certificate, with no equivalent Linux/macOS command (such as OpenSSL or base64). The mention of 'your favorite utility' is vague and does not guide non-Windows users. No Linux/macOS-specific tools or examples are provided for certificate handling, which may create friction for those users.
Recommendations
  • Add Linux/macOS command-line examples for base64-encoding PFX files, e.g., using OpenSSL and base64.
  • Explicitly mention cross-platform tools for certificate conversion and encoding, such as OpenSSL.
  • Where PowerShell is referenced, provide equivalent bash/zsh commands.
  • Clarify that the process is not Windows-specific and provide guidance for users on all platforms.
GitHub Create Pull Request
Data Factory Deploy SSIS packages ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page primarily references Windows-centric tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages, without mentioning Linux/macOS alternatives or clarifying cross-platform support. Examples and tool references are Windows-first, and there are no instructions or notes for Linux users.
Recommendations
  • Explicitly state platform support for each tool (e.g., whether SSDT, SSMS, dtutil, AzureDTExec are available on Linux/macOS).
  • Provide Linux/macOS equivalents or alternatives for package deployment and execution, if available.
  • Include example commands or workflows for Linux/macOS users, or link to relevant cross-platform documentation.
  • If Windows-only tools are required, clearly note this and suggest workarounds or alternatives for non-Windows users.
GitHub Create Pull Request
Data Factory Continuous integration and delivery ...ticles/data-factory/continuous-integration-delivery.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, particularly in the CI/CD best practices section. PowerShell is recommended exclusively for pre- and post-deployment scripting, with no mention of Bash, shell scripts, or cross-platform alternatives. The provided script is a PowerShell (.ps1) file, and warnings focus on PowerShell Core usage, which, while cross-platform, is still less common on Linux/macOS. There are no Linux/macOS-specific examples or guidance, and Windows-centric tools and patterns are referenced before any alternatives.
Recommendations
  • Provide equivalent Bash or shell script examples for pre- and post-deployment tasks.
  • Explicitly mention that PowerShell Core is available on Linux/macOS and provide installation instructions or links.
  • Include notes or examples for running CI/CD scripts in Linux/macOS environments, such as using Bash in Azure Pipelines.
  • Clarify that users can choose between PowerShell and Bash depending on their platform and provide parity in documentation.
  • List cross-platform prerequisites and troubleshooting steps for both Windows and Linux/macOS users.
GitHub Create Pull Request
Data Factory Copy activity ...b/main/articles/data-factory/copy-activity-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for Azure Data Factory & Synapse Copy activity does not provide explicit Windows or PowerShell-heavy examples, nor does it mention Windows-specific tools or patterns. However, there is a subtle Windows bias in the 'Related content' section, where the only hybrid/on-premises example is 'Copy data from a SQL Server database to Azure' and is labeled as a PowerShell tutorial. There are no equivalent Linux or bash-based hybrid copy tutorials, nor are Linux-specific scenarios (e.g., copying from a Linux file system using bash/Shell) highlighted. The page also lists 'File System' as a supported connector, but does not clarify cross-platform usage or provide parity in example walkthroughs for Linux/macOS users.
Recommendations
  • Add Linux/macOS-specific examples in the 'Related content' section, such as copying data from a Linux file system to Azure using bash or shell scripts.
  • Provide explicit parity in hybrid/on-premises scenarios, including tutorials for Linux environments (e.g., using bash, Python, or other cross-platform tools).
  • Clarify in the documentation that the 'File System' connector supports both Windows and Linux file systems, and provide configuration examples for each.
  • If PowerShell is mentioned, also mention bash or other Linux-native scripting options where applicable.
GitHub Create Pull Request
Data Factory Create Azure integration runtime ...icles/data-factory/create-azure-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a command-line example only for Azure PowerShell (Set-AzDataFactoryV2IntegrationRuntime), which is primarily a Windows tool. There are no equivalent examples for Linux/macOS users, such as Azure CLI or REST API. The documentation implicitly assumes the user is on Windows or has access to PowerShell, creating friction for Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
  • Add Azure CLI example for creating Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API example for advanced users who may wish to automate or script the process independently of OS.
  • Clearly state that PowerShell is available on Linux/macOS, but also provide alternatives for users who do not wish to install PowerShell.
  • Ensure that command-line examples are presented for both Windows and Linux/macOS environments, or indicate parity.
GitHub Create Pull Request
Data Factory Create an Azure-SSIS integration runtime via Azure portal ...actory/create-azure-ssis-integration-runtime-portal.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page is largely platform-neutral in its main instructions, focusing on the Azure portal UI. However, there is evidence of Windows bias: the only command-line automation method referenced is Azure PowerShell (with no mention of Bash, Azure CLI, or Linux-native scripting), and Windows-centric tools and patterns (e.g., UNC paths, SSMS, references to Windows authentication) are mentioned without Linux/macOS equivalents. Additionally, the related content section lists PowerShell before other automation options, reinforcing a Windows-first approach.
Recommendations
  • Add equivalent examples and references for Azure CLI and Bash scripting for provisioning and managing Azure-SSIS IR, alongside PowerShell.
  • Clarify cross-platform support for SSIS package management tools (e.g., mention Azure Data Studio or other non-Windows alternatives to SSMS).
  • When referencing file paths, include Linux/macOS syntax or note platform differences (e.g., UNC paths vs. NFS paths).
  • Explicitly state platform requirements or limitations for features that are Windows-only (e.g., Windows authentication, SSMS usage).
  • Order automation options (PowerShell, CLI, ARM templates) in a platform-neutral way, or group them together.
GitHub Create Pull Request
Data Factory Use an Azure Resource Manager template to create an integration runtime ...ure-ssis-integration-runtime-resource-manager-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell-based deployment and management examples for Azure Resource Manager templates and Azure-SSIS IR, with no mention of Linux/macOS-compatible alternatives such as Azure CLI, Bash, or REST API. Windows tools and patterns are referenced exclusively, creating friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI commands for template deployment and IR management, with full examples.
  • Include Bash or shell script examples for Linux/macOS users.
  • Reference REST API methods for users who prefer platform-agnostic automation.
  • Explicitly state cross-platform options and link to relevant documentation.
  • Reorder examples so that cross-platform methods (CLI, REST) are shown before or alongside PowerShell.
GitHub Create Pull Request
Data Factory General Troubleshooting ...ticles/data-factory/data-factory-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is generally cross-platform, but there are several instances of Windows bias. Notably, troubleshooting steps for Azure Batch custom activities and file extraction use PowerShell commands exclusively, with no Linux or macOS shell alternatives. Windows tools (e.g., Fiddler) are recommended for network troubleshooting, and references to Windows-specific compression behavior are made before mentioning third-party or cross-platform alternatives. These examples and recommendations are presented without Linux/macOS equivalents or ordering parity.
Recommendations
  • Provide equivalent Linux/macOS shell commands (e.g., unzip, tar) alongside PowerShell examples for file extraction and manipulation.
  • Mention cross-platform tools (e.g., Wireshark, tcpdump, curl) for network troubleshooting in addition to or before Windows-only tools like Fiddler.
  • Clarify compression algorithm support and recommend cross-platform zip utilities (e.g., 7zip, unzip) for creating compatible archives.
  • Where Windows-specific behaviors are described, add notes for Linux/macOS users about differences or alternative approaches.
  • Ensure that examples and troubleshooting steps are presented in a platform-neutral order or grouped by OS.
GitHub Create Pull Request
Data Factory Migrate data from Amazon S3 to Azure Storage ...ta-factory/data-migration-guidance-s3-azure-storage.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in its guidance for deploying self-hosted Integration Runtime (IR) for private network migrations. It exclusively recommends installing the IR on Azure Windows VMs, with no mention of Linux VM support or examples. All configuration and scaling guidance is tailored to Windows environments, potentially excluding Linux users or creating friction for those preferring Linux-based infrastructure.
Recommendations
  • Explicitly state whether self-hosted Integration Runtime supports Linux VMs. If supported, provide equivalent instructions and best practices for deploying IR on Linux VMs.
  • Include Linux-based example configurations and scaling guidance alongside Windows instructions.
  • Clarify any platform limitations for IR, and if Windows is required, explain why and suggest alternatives for Linux users where possible.
  • Add notes or links to documentation about cross-platform support for IR, including any differences in setup, monitoring, or performance.
GitHub Create Pull Request
Data Factory Create an Azure-SSIS integration runtime in Azure Data Factory .../data-factory/create-azure-ssis-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-centric tools (SSDT, SSMS, dtutil), highlights Azure PowerShell for provisioning, and mentions enabling settings via PowerShell before any Linux alternatives. There are no explicit Linux/macOS command-line examples or mentions of cross-platform tools for provisioning or managing Azure-SSIS IR. The order of presentation also tends to list Windows/PowerShell options before others.
Recommendations
  • Include CLI examples using Azure CLI (az), which is cross-platform, for provisioning Azure-SSIS IR and configuring firewall rules.
  • Mention and provide guidance for using cross-platform database tools (e.g., Azure Data Studio) for deploying and managing SSIS packages.
  • Explicitly state which steps and tools are available on Linux/macOS and provide links or instructions for those environments.
  • Balance the order of tool presentation so that Windows and cross-platform options are equally visible.
  • Add notes or sections for Linux/macOS users, clarifying any limitations or alternative approaches.
GitHub Create Pull Request
Data Factory Using credentials ...re-docs/blob/main/articles/data-factory/credentials.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references Windows-centric tools (Azure portal, PowerShell) and lists them before alternatives (SDK, REST API). There are no explicit Linux/macOS command-line examples (e.g., Azure CLI), and screenshots exclusively show the Azure portal, which is platform-neutral but often associated with Windows workflows. PowerShell is mentioned as a primary scripting tool, with no parity for Bash or Azure CLI. This may create friction for Linux/macOS users who prefer CLI or non-Windows automation.
Recommendations
  • Add Azure CLI examples for creating and managing user-assigned managed identities and credentials.
  • Explicitly mention that the Azure portal is web-based and accessible from any OS.
  • Provide Bash script samples or references for Linux/macOS users.
  • List SDK, REST API, and CLI options together, not prioritizing PowerShell or Windows tools.
  • Include screenshots or instructions for cross-platform tools where relevant.
GitHub Create Pull Request
Data Factory Create a shared self-hosted integration runtime with PowerShell ...eate-shared-self-hosted-integration-runtime-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell-based instructions for command-line operations, referencing Windows PowerShell ISE, and linking to Windows-specific installation guides. There are no equivalent examples or instructions for Linux/macOS users (e.g., Bash, Azure CLI), nor is there mention of cross-platform alternatives for scripting or installation. This creates friction for non-Windows users attempting to follow the guide.
Recommendations
  • Provide Azure CLI examples alongside PowerShell for all command-line steps.
  • Clarify that Azure PowerShell can be installed and used on Linux/macOS, and provide installation instructions for those platforms.
  • Avoid referencing Windows PowerShell ISE; suggest cross-platform editors (e.g., VS Code) instead.
  • Explicitly mention and demonstrate how to download and install the self-hosted integration runtime on Linux/macOS, if supported, or clarify platform limitations.
  • Order examples so that cross-platform solutions (Azure CLI, REST API) are presented before or alongside Windows-specific ones.
GitHub Create Pull Request
Data Factory Managed identity ...articles/data-factory/data-factory-service-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing PowerShell-based examples for key operations (such as generating and retrieving managed identities) and referencing PowerShell commands for tasks like obtaining the application ID. No equivalent CLI or Bash examples are given, and PowerShell is mentioned before REST/SDK alternatives. This creates friction for Linux/macOS users who are more likely to use Azure CLI or Bash scripts.
Recommendations
  • Add Azure CLI examples for all operations currently demonstrated with PowerShell, such as creating, updating, and retrieving managed identities.
  • Include Bash script snippets where appropriate, especially for REST API calls.
  • Present cross-platform tools (Azure CLI, REST API) before or alongside PowerShell in example sections.
  • Explicitly note which commands are platform-specific and provide alternatives for non-Windows environments.
GitHub Create Pull Request
Data Factory Migrate data from an on-premises Hadoop cluster to Azure Storage ...-factory/data-migration-guidance-hdfs-azure-storage.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, particularly in its instructions for installing the Data Factory self-hosted integration runtime. It repeatedly specifies installation on Windows machines or Windows VMs, with no mention of Linux or macOS support or examples. The pricing section also references Azure Windows VMs exclusively. There are no Linux installation instructions, nor is there any discussion of Linux compatibility or parity for the self-hosted integration runtime. This creates friction for users operating in Linux environments, which are common for Hadoop clusters.
Recommendations
  • Explicitly state whether the Data Factory self-hosted integration runtime supports Linux and macOS, and provide installation instructions/examples for those platforms if supported.
  • If Linux is supported, include architecture diagrams and best practices for deploying the integration runtime on Linux VMs, alongside Windows examples.
  • Update pricing examples to include Linux VM options and cost comparisons.
  • Clarify any platform-specific limitations or differences in performance, scalability, or security.
  • If Linux/macOS are not supported, clearly state this limitation early in the documentation.
GitHub Create Pull Request
Data Factory Security considerations .../data-factory/data-movement-security-considerations.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias in its coverage of hybrid/on-premises scenarios. It references Windows-specific technologies such as DPAPI for credential encryption, PowerShell cmdlets (Set-AzDataFactoryV2LinkedService, New-AzDataFactoryV2LinkedServiceEncryptedCredential), and Windows Firewall. There are no equivalent examples or instructions for Linux/macOS environments, nor are alternative encryption/storage mechanisms discussed for non-Windows platforms. The port requirements and credential management instructions are described exclusively in terms of Windows tools and patterns, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS equivalents for credential encryption and storage, such as using OpenSSL, GnuPG, or platform-native keyrings.
  • Include examples using cross-platform tools (e.g., Azure CLI, REST API) for managing linked services and credentials, not just PowerShell.
  • Clarify whether the self-hosted integration runtime can be installed and operated on Linux/macOS, and if so, document the differences in credential management and firewall configuration.
  • Describe firewall configuration steps for Linux (e.g., using iptables, firewalld, ufw) alongside Windows Firewall.
  • Explicitly state any platform limitations or requirements for hybrid scenarios, so non-Windows users can plan accordingly.
GitHub Create Pull Request
Data Factory Assess your Azure Data Factory pipelines for migration to Fabric ...ur-azure-data-factory-to-fabric-data-factory-migration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation repeatedly references the PowerShell upgrade tool as the primary method for migration, without mentioning Linux/macOS alternatives or cross-platform tools. No Bash, CLI, or platform-neutral instructions are provided, and PowerShell is presented as the default solution for migration tasks.
Recommendations
  • Include Azure CLI or REST API migration instructions alongside PowerShell examples.
  • Explicitly state whether the PowerShell upgrade tool works on Linux/macOS (via PowerShell Core), and provide installation guidance for those platforms.
  • Add Bash or shell script examples for exporting assessment results and performing migrations.
  • Clarify cross-platform compatibility in the 'Next steps' and FAQ sections.
  • List Linux/macOS tools or workflows before or alongside Windows/PowerShell options.
GitHub Create Pull Request
Data Factory How to clean up SSISDB logs automatically ...ctory/how-to-clean-up-ssisdb-logs-with-elastic-jobs.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing SQL Server Management Studio (SSMS) for configuration steps, using Windows-centric terminology (Object Explorer, right-click, dialog boxes), and omitting any mention of Linux/macOS alternatives for connecting to and managing SSISDB. All screenshots and walkthroughs assume SSMS, which is only available on Windows. There are no examples using cross-platform tools (Azure Data Studio, sqlcmd, etc.), nor any guidance for Linux/macOS users.
Recommendations
  • Add instructions for configuring SSISDB log clean-up properties using T-SQL scripts that can be run from any platform (e.g., via Azure Data Studio, sqlcmd, or other cross-platform tools).
  • Include screenshots or walkthroughs using Azure Data Studio, which runs on Windows, Linux, and macOS.
  • Explicitly mention that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
  • Provide PowerShell and T-SQL examples for all steps, not just Elastic Database Jobs, to ensure parity.
  • Add a section or note for Linux/macOS users outlining how to perform all tasks without SSMS.
GitHub Create Pull Request
Data Factory Create tumbling window triggers .../data-factory/how-to-create-tumbling-window-trigger.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page displays a moderate Windows bias in its code samples and tooling recommendations. The PowerShell example is presented first and references Windows-specific installation instructions and file paths (e.g., C:\ADFv2QuickStartPSH\MyTrigger.json). The Azure CLI example is provided, which is cross-platform, but the PowerShell section is more detailed and assumes a Windows environment. There are no explicit Linux/macOS examples or notes about using PowerShell on non-Windows platforms.
Recommendations
  • Add explicit instructions for running Azure PowerShell on Linux/macOS, including installation steps and any platform-specific caveats.
  • Use platform-neutral file paths in examples (e.g., ./MyTrigger.json instead of C:\...).
  • Provide Bash or shell script equivalents for common tasks, especially for file creation and command execution.
  • Clarify that Azure CLI is cross-platform and recommend it as the default for Linux/macOS users.
  • Consider presenting Azure CLI examples before PowerShell, or side-by-side, to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
Data Factory How to ingest data into Fabric using the Azure Data Factory Copy activity ...how-to-ingest-data-into-fabric-from-azure-data-factory.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a notable Windows bias, especially in the authentication section. PowerShell is the only method provided for forcing a permissions refresh, with no mention of Linux/macOS alternatives (such as Bash, curl, or cross-platform CLI tools). Windows/PowerShell tools are referenced exclusively and shown before any cross-platform options, and there are no Linux/macOS-specific instructions or examples throughout the page.
Recommendations
  • Provide equivalent Linux/macOS instructions for tasks currently shown only with PowerShell, such as using Azure CLI, REST API via curl, or Python scripts to refresh permissions.
  • Explicitly mention cross-platform alternatives where possible, and clarify which steps are OS-agnostic.
  • Include examples or notes for Linux/macOS users in sections that currently assume Windows/PowerShell usage.
  • Reorder examples or add parallel instructions so that Windows and Linux/macOS users are equally supported.
GitHub Create Pull Request
Data Factory Provision Enterprise Edition for the Azure-SSIS Integration Runtime ...y/how-to-configure-azure-ssis-ir-enterprise-edition.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides instructions using Azure PowerShell, a tool most commonly used on Windows, and does not mention or provide examples for Linux/macOS users (e.g., Azure CLI or REST API). Windows authentication is referenced without alternatives for non-Windows environments. This creates friction for users on Linux or macOS who may not use PowerShell or require platform-agnostic instructions.
Recommendations
  • Add equivalent instructions using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for provisioning and configuring Azure-SSIS IR.
  • Clarify authentication alternatives for non-Windows environments, especially where Windows Authentication is referenced.
  • Present examples for both Windows and Linux/macOS platforms, or note platform requirements explicitly.
GitHub Create Pull Request
Data Factory Schedule an Azure-SSIS integration runtime ...tory/how-to-schedule-azure-ssis-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a notable Windows bias, primarily through the exclusive use of PowerShell for automation and monitoring examples, and references to Windows-centric tools such as SQL Server Management Studio. There are no equivalent examples or guidance for Linux/macOS users (e.g., using Bash, Azure CLI, or cross-platform alternatives), and Windows tools are mentioned first and exclusively in relevant sections.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for automation and monitoring tasks, ensuring Linux/macOS users can follow along without PowerShell.
  • Mention and demonstrate cross-platform tools (such as Azure Data Studio) alongside or before Windows-only tools like SQL Server Management Studio.
  • Clearly state platform requirements and offer alternative instructions for non-Windows environments wherever possible.
  • Add notes or sections highlighting how Linux/macOS users can accomplish the same tasks using supported tools.
GitHub Create Pull Request
Data Factory Use the Execute SSIS Package activity from the portal ...ta-factory/how-to-invoke-ssis-package-ssis-activity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows Authentication Emphasis Windows First
Summary
The documentation exhibits a notable Windows bias. It repeatedly references Windows authentication, UNC paths, and Windows-centric tooling (SQL Server Data Tools, SQL Server Management Studio, dtutil). The use of Azure Files is described exclusively with UNC paths, which are a Windows convention. There are no Linux/macOS-specific instructions, examples, or clarifications about cross-platform compatibility for authentication, file paths, or tooling. The related content also highlights PowerShell, a Windows-first automation tool.
Recommendations
  • Add explicit guidance for Linux/macOS users regarding file path conventions (e.g., SMB mount paths, alternatives to UNC).
  • Clarify whether Azure-SSIS IR and Execute SSIS Package activity support Linux/macOS clients for package upload, configuration, and monitoring.
  • Provide examples for authentication and credential management that do not rely solely on Windows authentication (e.g., Azure AD, service principals).
  • Mention cross-platform alternatives to SSDT and SSMS, or clarify if these steps must be performed on Windows.
  • Include notes or sections on how Linux/macOS users can interact with Azure Files, e.g., using SMB mounts or REST APIs.
  • If PowerShell is required, suggest cross-platform PowerShell Core or alternative CLI tools where possible.
GitHub Create Pull Request
← Previous Page 7 of 13 Next →