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 226-250 of 319 flagged pages
Data Factory Troubleshoot the Azure Blob Storage connector ...a-factory/connector-troubleshoot-azure-blob-storage.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias primarily in the troubleshooting section for FIPS mode, where it references disabling FIPS via diawp.exe.config and notes that 'Windows doesn't recommend the FIPS mode.' No Linux or macOS equivalents or instructions are provided for self-hosted integration runtime scenarios, and the troubleshooting steps assume a Windows environment. There are no PowerShell-heavy examples, but Windows tools and patterns are mentioned exclusively, with no parity for Linux users.
Recommendations
  • Provide troubleshooting steps for disabling FIPS or handling MD5 requirements on Linux/macOS self-hosted integration runtime installations.
  • Clarify whether the self-hosted integration runtime is supported on Linux/macOS and, if so, include relevant configuration instructions.
  • Avoid language that assumes Windows as the default environment; mention Linux/macOS where applicable.
  • If certain features are Windows-only, explicitly state this and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Data Factory Troubleshoot the Dynamics 365, Dataverse (Common Data Service), and Dynamics CRM connectors ...a-factory/connector-troubleshoot-dynamics-dataverse.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references XrmToolBox, a Windows-only tool, as a troubleshooting method for Dynamics 365 connectors. No Linux/macOS alternatives or cross-platform instructions are provided. There are no command-line or script examples (PowerShell, Bash, etc.), but the only explicit tool mentioned is Windows-specific.
Recommendations
  • Provide alternative troubleshooting tools or methods that work on Linux/macOS, such as cross-platform CLI tools or REST API instructions.
  • If XrmToolBox functionality is essential, document how to achieve similar results using platform-independent approaches (e.g., using the Dynamics Web API, or open-source alternatives).
  • Explicitly mention platform compatibility for referenced tools and suggest workarounds for non-Windows users.
  • Include examples or instructions for Linux/macOS environments where applicable.
GitHub Create Pull Request
Data Factory Troubleshoot the REST connector ...n/articles/data-factory/connector-troubleshoot-rest.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias by instructing users to use 'curl' in a Command Prompt window, which is a Windows-specific context. It does not mention Linux/macOS terminals, nor does it provide Linux/macOS-specific troubleshooting steps or examples. Additionally, Fiddler is recommended as a troubleshooting tool, which is primarily a Windows application, with no mention of Linux/macOS alternatives.
Recommendations
  • Explicitly mention that 'curl' can be used in Linux/macOS terminals as well as Windows Command Prompt.
  • Provide example 'curl' commands for Linux/macOS (e.g., using Bash syntax).
  • List cross-platform alternatives to Fiddler, such as Wireshark or mitmproxy, for SSL troubleshooting.
  • Avoid assuming the user's environment is Windows; use neutral language like 'terminal' or 'command line'.
GitHub Create Pull Request
Data Factory Connector upgrade guidance ...in/articles/data-factory/connector-upgrade-guidance.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell scripts for programmatically identifying impacted objects, with no mention of Linux/macOS alternatives (such as Azure CLI, Bash, or REST API). This creates friction for users on non-Windows platforms, as PowerShell is not natively available and may require extra setup or adaptation.
Recommendations
  • Add equivalent examples using Azure CLI and/or REST API for programmatic queries.
  • Explicitly mention cross-platform options and provide guidance for running PowerShell Core on Linux/macOS if PowerShell is required.
  • List Linux/macOS-compatible tools and scripts alongside PowerShell examples.
  • Consider presenting cross-platform examples first or side-by-side with Windows-specific ones.
GitHub Create Pull Request
Data Factory Automate continuous integration ...ntinuous-integration-delivery-automate-azure-pipelines.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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, primarily through exclusive use of PowerShell for scripting and automation tasks, references to .ps1 files, and instructions that assume the use of Azure PowerShell modules. There are no examples or guidance for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform scripting alternatives. The documentation also references Windows-centric patterns (e.g., PowerShell scripts in repositories) and does not mention Linux agents or provide parity for non-Windows environments.
Recommendations
  • Include equivalent examples using Bash or Azure CLI for tasks such as stopping/starting triggers and managing deployments.
  • Explicitly mention support for Linux/macOS agents and provide instructions for running scripts on those platforms.
  • Clarify whether all tasks (e.g., ARM Template Deployment, Key Vault access) are supported on Linux agents and document any differences.
  • Provide sample scripts in both PowerShell (.ps1) and Bash (.sh) formats.
  • Reorder examples to present cross-platform or Linux options alongside or before Windows/PowerShell examples.
GitHub Create Pull Request
Data Factory If Condition activity ...les/data-factory/control-flow-if-condition-activity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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. All command-line examples use Azure PowerShell, referencing Windows file paths (e.g., C:\ADF), and there are no equivalent instructions or examples for Linux/macOS users (such as Bash/CLI commands or POSIX file paths). The tutorial and walkthrough links also focus on Azure PowerShell, further reinforcing the bias. Linux and macOS users are left to adapt Windows-centric instructions without guidance.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, using POSIX file paths (e.g., /home/user/ADF).
  • Include a section or note explaining how to run the pipeline and manage resources from Linux/macOS environments.
  • Provide sample Bash scripts or command snippets for common tasks (e.g., uploading JSON files, running pipelines).
  • Reference cross-platform tools and avoid assuming a Windows file system layout.
  • Update tutorial links to include Linux/macOS walkthroughs.
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-11 06:20
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 for deploying or running the pipeline, nor any mention of Linux/macOS alternatives. The tutorial and walkthrough links also focus on Azure PowerShell, reinforcing a Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, with sample Bash scripts.
  • Use platform-neutral file paths in examples (e.g., /home/user/ADF or ./ADF).
  • Include explicit instructions for Linux/macOS users, such as prerequisites and environment setup.
  • Reference cross-platform tools and workflows in the tutorial links.
  • Clarify that JSON definitions can be used with multiple tools, not just PowerShell.
GitHub Create Pull Request
Data Factory Web Activity ...ain/articles/data-factory/control-flow-web-activity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell-only example for base64-encoding a PFX certificate, referencing Windows tooling and patterns without mentioning Linux/macOS equivalents. No Linux or cross-platform alternatives (e.g., OpenSSL, base64 CLI) are provided for certificate conversion or encoding, which may hinder non-Windows users attempting to follow authentication steps.
Recommendations
  • Add Linux/macOS command-line examples for base64-encoding a PFX file (e.g., using 'base64' or 'openssl').
  • Explicitly mention that certificate conversion and encoding can be performed on any OS, and provide cross-platform instructions.
  • Where PowerShell is referenced, also provide Bash or other shell equivalents.
  • Consider linking to external resources for certificate handling on Linux/macOS.
GitHub Create Pull Request
Data Factory Continuous integration and delivery ...ticles/data-factory/continuous-integration-delivery.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 in its CI/CD best practices section, specifically recommending PowerShell scripts for pre- and post-deployment tasks and linking to a PowerShell (.ps1) script. There is no mention of Bash, shell, or cross-platform alternatives, nor are Linux/macOS-specific instructions or examples provided. The guidance assumes users are familiar with PowerShell and Windows tooling, and does not address how Linux/macOS users can perform equivalent tasks.
Recommendations
  • Provide equivalent Bash or shell script examples for pre- and post-deployment tasks.
  • Explicitly mention that PowerShell Core is cross-platform and provide installation instructions for Linux/macOS.
  • Include guidance or links for running deployment scripts on Linux/macOS agents in Azure Pipelines.
  • Add notes or examples for using Azure CLI as an alternative to PowerShell where possible.
  • Reorder examples or notes so that cross-platform solutions are presented before or alongside Windows-specific ones.
GitHub Create Pull Request
Data Factory Until activity ...n/articles/data-factory/control-flow-until-activity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides extensive PowerShell command examples and instructions, assuming use of Windows paths (e.g., C:\ADF) and Windows-native tooling. There are no equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI), nor any mention of how to adapt the workflow for non-Windows environments. The only command-line walkthrough is PowerShell-based, and Windows file path conventions are used throughout.
Recommendations
  • Add equivalent Azure CLI and Bash examples for pipeline deployment and monitoring.
  • Include instructions for saving and referencing JSON files using Linux/macOS file paths.
  • Explicitly mention cross-platform options and note any differences or limitations.
  • Reorder examples so that platform-neutral JSON definitions come before platform-specific command-line instructions.
  • Provide links to official Azure CLI documentation for Data Factory tasks.
GitHub Create Pull Request
Data Factory Copy activity ...b/main/articles/data-factory/copy-activity-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page does not provide explicit examples or instructions that are Windows-specific, such as PowerShell commands or references to Windows-only tools. However, in the 'Related content' section, the tutorials and quickstarts listed are either .NET-based or PowerShell-based, which are traditionally Windows-centric technologies. There are no Linux/macOS-specific examples, nor are there references to cross-platform command-line tools or scripting languages (e.g., Bash, Python). This creates a subtle bias by prioritizing Windows-friendly approaches and omitting Linux/macOS parity in getting started guides.
Recommendations
  • Add tutorials and quickstarts that use cross-platform tools and languages, such as Python, Bash, or Azure CLI, to demonstrate Copy activity usage on Linux/macOS.
  • Explicitly mention that self-hosted integration runtime can be installed and run on Linux, and provide setup instructions or links for Linux environments.
  • Include examples or references for Linux file systems and workflows in the main documentation and in the 'Related content' section.
  • Ensure that connector documentation covers both Windows and Linux scenarios, especially for on-premises data movement.
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-11 06:20
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 (Windows-centric), with no mention of equivalent Azure CLI or Bash commands for Linux/macOS users. The only automation example is via PowerShell, and the use of Set-AzDataFactoryV2IntegrationRuntime is a Windows/PowerShell-specific tool. There is no guidance for Linux or macOS users on how to perform the same task outside of the UI.
Recommendations
  • Add equivalent Azure CLI examples for creating and configuring Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that the PowerShell example is for Windows, and provide Bash/CLI alternatives.
  • Include a note or section on how Linux/macOS users can automate this process using Azure CLI or REST API.
  • Ensure command-line automation instructions are not Windows-exclusive and appear in parallel or before Windows-specific examples.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page references Windows-centric tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages, without mentioning Linux/macOS alternatives or parity. There are no examples or guidance for Linux users, and Windows tools are presented as the default or only option.
Recommendations
  • Explicitly state platform requirements for SSDT, SSMS, dtutil, and AzureDTExec, clarifying their Windows-only nature.
  • Provide guidance or alternatives for Linux/macOS users, such as using Azure portal, REST APIs, or cross-platform Data Factory pipeline activities.
  • Add examples or workflows for deploying and running SSIS packages from Linux/macOS environments, if supported.
  • Where possible, highlight platform-neutral methods (e.g., Data Factory pipeline activities) before Windows-specific tools.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides PowerShell-based deployment and management examples, which are native to Windows. There are no CLI, Bash, or cross-platform instructions for deploying or managing Azure-SSIS IR, creating friction for Linux and macOS users. Windows tools and patterns are mentioned first and exclusively.
Recommendations
  • Add equivalent Azure CLI examples for deploying and managing Azure-SSIS IR.
  • Include Bash script samples for template deployment.
  • Explicitly mention cross-platform options and clarify which commands work on Linux/macOS.
  • Provide links to Azure CLI documentation for relevant resource management tasks.
GitHub Create Pull Request
Data Factory Azure Private Link for Azure Data Factory ...ain/articles/data-factory/data-factory-private-link.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for creating a virtual machine to host the self-hosted integration runtime (IR), but only Windows Server images are mentioned and recommended. There are no examples or guidance for deploying the self-hosted IR on Linux or macOS, nor are alternative OS options acknowledged. This creates friction for users who prefer or require non-Windows environments.
Recommendations
  • Explicitly mention that self-hosted IR can be installed on Linux (if supported), and provide equivalent instructions for creating a Linux VM in Azure.
  • List supported operating systems for self-hosted IR, including Linux distributions and macOS if applicable.
  • Provide example commands and screenshots for Linux VM creation and IR installation.
  • If Linux/macOS are not supported, clearly state this limitation early in the documentation.
GitHub Create Pull Request
Data Factory General Troubleshooting ...ticles/data-factory/data-factory-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 provide only PowerShell-based unzip commands, and examples use 'powershell.exe', which is Windows-specific. Additionally, the explanation of unsupported compression algorithms references Windows behavior first and does not mention Linux alternatives or tools. Some troubleshooting steps for ODBC connections reference PowerShell tutorials before Linux/JDBC equivalents. There are no Linux shell or macOS command examples for tasks like unzipping or troubleshooting, and Windows tools (e.g., Fiddler) are mentioned without Linux alternatives.
Recommendations
  • Provide equivalent Linux/macOS shell commands (e.g., 'unzip', 'tar', or '7z') alongside PowerShell examples for file extraction and manipulation.
  • When referencing troubleshooting tools like Fiddler, mention Linux alternatives such as Wireshark, tcpdump, or mitmproxy.
  • In sections discussing compression, clarify how Linux zip tools behave and suggest cross-platform solutions.
  • Ensure that examples and troubleshooting steps are presented in a platform-neutral order, or provide both Windows and Linux/macOS options side-by-side.
  • Link to Linux/macOS-specific documentation or tutorials where relevant (e.g., JDBC setup, shell scripting for Azure Batch).
GitHub Create Pull Request
Data Factory Using credentials ...re-docs/blob/main/articles/data-factory/credentials.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by referencing Windows-centric tools (Azure portal, PowerShell) and providing examples and screenshots exclusively for these interfaces. There is no mention of Linux/macOS-specific tools or command-line examples (e.g., Azure CLI, Bash), nor are there instructions or screenshots for non-Windows platforms. PowerShell is listed as a scripting option, but Azure CLI or Bash scripts are not mentioned, and the Azure portal (a web interface) is shown as the primary method for configuration.
Recommendations
  • Add Azure CLI examples for creating and managing user-assigned managed identities and credentials, as CLI is cross-platform.
  • Include Bash script samples for resource management tasks.
  • Provide screenshots or step-by-step instructions for using Azure CLI on Linux/macOS.
  • Explicitly mention cross-platform SDKs and tools, and clarify which steps can be performed on any OS.
  • List Azure CLI before or alongside PowerShell when referencing scripting options.
GitHub Create Pull Request
Data Factory Mapping data flow script ...cs/blob/main/articles/data-factory/data-flow-script.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary method for programmatically generating and submitting Data Flow Script (DFS) outside the UI. There are no examples or mentions of Linux/macOS equivalents (such as Bash, curl, or Azure CLI), and PowerShell is mentioned before any generic API usage. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add explicit examples for Linux/macOS users, such as using Azure CLI or REST API with curl.
  • Mention API usage as a cross-platform method before or alongside PowerShell.
  • Clarify that PowerShell is one of several options, and provide parity in instructions for non-Windows environments.
  • Include sample scripts or commands for Bash or other common Linux/macOS shells.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Critical implementation steps, such as installing the Data Factory self-hosted integration runtime, are described as requiring a Windows machine or Windows VM, with no mention of Linux support or alternatives. Pricing estimates and architecture diagrams also assume Windows VMs. There are no examples or guidance for Linux-based integration runtime hosts, nor is there discussion of Linux-specific considerations, even though Hadoop clusters are typically Linux-based.
Recommendations
  • Explicitly state whether the Data Factory self-hosted integration runtime can be installed on Linux machines, and provide installation instructions/examples for Linux if supported.
  • Include Linux VM options in architecture diagrams and pricing estimates, or clarify Windows-only requirements.
  • Add guidance for Linux users, such as how to configure the integration runtime on Linux, and address any differences in authentication, performance, or monitoring.
  • If Windows is required, explain the rationale and provide workarounds or alternatives for Linux environments.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias in its guidance for deploying self-hosted Integration Runtime (IR) for Azure Data Factory. It exclusively recommends installing IR on Azure Windows VMs, with no mention of Linux support or examples. All VM sizing and scaling advice is Windows-specific, and there are no instructions or references for deploying IR on Linux or macOS environments. This creates friction for users who prefer or require Linux-based infrastructure.
Recommendations
  • Explicitly state whether self-hosted IR supports Linux VMs, and if so, provide equivalent instructions for Linux deployment.
  • Include Linux VM sizing recommendations alongside Windows examples.
  • Offer guidance on monitoring and scaling IR on Linux VMs.
  • If IR is Windows-only, clarify this limitation early in the documentation and suggest alternatives for Linux users where possible.
  • Add troubleshooting and best practices sections relevant to Linux environments.
GitHub Create Pull Request
Data Factory Security considerations .../data-factory/data-movement-security-considerations.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias in its coverage of hybrid scenarios and credential management for self-hosted integration runtime. It exclusively references Windows-specific technologies (such as DPAPI and Windows Firewall), PowerShell cmdlets (Set-AzDataFactoryV2LinkedService, New-AzDataFactoryV2LinkedServiceEncryptedCredential), and port requirements tied to Windows/PowerShell usage. There is no mention of Linux or macOS equivalents, nor are alternative credential encryption or firewall management approaches for non-Windows platforms provided. This may create friction or confusion for users deploying self-hosted integration runtime on Linux or macOS, or those who do not use PowerShell.
Recommendations
  • Add explicit guidance for deploying and securing self-hosted integration runtime on Linux and macOS, including credential encryption and storage options.
  • Provide examples using cross-platform tools (e.g., Azure CLI, REST API) for credential management, in addition to PowerShell.
  • Clarify whether DPAPI and Windows Firewall requirements apply only to Windows hosts, and describe alternatives for Linux/macOS (e.g., using Gnome Keyring, libsecret, or other OS-native encryption).
  • Include port and firewall configuration instructions for Linux (e.g., iptables, firewalld, ufw) and macOS (pf, application firewall).
  • Indicate if any features (such as encrypted credential storage) are unavailable or different on non-Windows platforms.
GitHub Create Pull Request
Data Factory Enable Microsoft Entra authentication for Azure SSIS integration runtime ...ata-factory/enable-aad-authentication-azure-ssis-ir.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a notable Windows bias. All command-line examples use PowerShell, with no Bash, CLI, or Linux/macOS alternatives. The instructions for database user creation and management rely exclusively on SQL Server Management Studio (SSMS), a Windows-only tool, without mentioning cross-platform SQL clients. The order of presentation and tool selection implicitly prioritizes Windows environments, creating friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI and/or Bash examples alongside PowerShell for all command-line steps, especially for group and managed identity management.
  • Include instructions for using cross-platform SQL clients (such as Azure Data Studio, sqlcmd, or other ODBC-compliant tools) for T-SQL operations instead of relying solely on SSMS.
  • Explicitly mention platform-agnostic alternatives where possible, and clarify which steps can be completed on Linux/macOS.
  • Reorder examples or add parallel sections so Linux/macOS users are not forced to adapt Windows-centric instructions.
GitHub Create Pull Request
Data Factory Encrypt Azure Data Factory with customer-managed key ...n/articles/data-factory/enable-customer-managed-key.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. In the 'Enable Soft Delete and Do Not Purge on Azure Key Vault' section, PowerShell is mentioned before Azure CLI, and no explicit Linux/macOS command examples are provided. The instructions and screenshots focus on the Azure portal UI, which is cross-platform, but command-line examples and tooling references (PowerShell, Azure CLI) are presented in a way that prioritizes Windows users. There are no bash or Linux-specific instructions, and PowerShell is referenced without noting its cross-platform availability.
Recommendations
  • Provide explicit bash/Azure CLI examples for Linux/macOS users alongside PowerShell commands.
  • When referencing command-line tools, clarify cross-platform availability (e.g., PowerShell Core runs on Linux/macOS).
  • Present Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
  • Add notes or links for Linux/macOS users on how to perform equivalent operations.
  • Ensure screenshots and instructions are not exclusively tailored to Windows environments.
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-11 06:20
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 Windows-centric tools such as SQL Server Management Studio (SSMS) and SQL Server Agent, and by providing step-by-step instructions and screenshots for these tools. There are no examples or guidance for Linux/macOS users, such as using Azure Data Studio, cross-platform SQL clients, or command-line alternatives. Windows tools are mentioned first and exclusively, and no Linux/macOS equivalents or workarounds are suggested.
Recommendations
  • Add instructions for connecting to SSISDB and configuring properties using Azure Data Studio or other cross-platform SQL clients.
  • Include examples for invoking SSISDB stored procedures using command-line tools like sqlcmd (available on Linux/macOS) or Azure CLI.
  • Provide guidance for managing jobs and scheduling tasks on non-Windows platforms, such as using cron jobs with sqlcmd or Azure CLI.
  • Mention that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
  • Ensure screenshots and UI walkthroughs are supplemented with command-line or cross-platform alternatives.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows Authentication Heavy Windows First
Summary
The documentation demonstrates a notable Windows bias. It heavily references Windows authentication, UNC paths, and Windows-centric tools (SSDT, SSMS, dtutil), with no mention of Linux/macOS alternatives or considerations. All file path examples use Windows UNC format, and authentication examples are Windows-centric. The documentation assumes the use of Windows-based tooling for package creation and management, and does not provide parity guidance for Linux/macOS users.
Recommendations
  • Add explicit notes clarifying platform requirements and limitations, especially regarding SSIS package creation and management tools (SSDT, SSMS, dtutil), which are Windows-only.
  • Provide guidance for Linux/macOS users, such as remote access to Windows VMs for package development, or alternatives for monitoring and management.
  • Clarify whether Azure Files UNC paths can be accessed from Linux/macOS, and if so, provide equivalent mount and access instructions for those platforms.
  • Where authentication is discussed, note that Windows authentication is not available on Linux/macOS, and suggest alternatives (e.g., SQL authentication, managed identities) where possible.
  • Consider reordering examples so that platform-neutral or cloud-native approaches (e.g., Azure Key Vault, SQL authentication) are presented before Windows-specific ones.
  • Explicitly state that the SSIS runtime and tooling are Windows-only, and provide links to official documentation on cross-platform limitations.
GitHub Create Pull Request
← Previous Page 10 of 13 Next →