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 851-875 of 1000 flagged pages
Data Factory BCDR for Azure Data Factory and Azure Synapse Analytics Pipelines ...n/articles/data-factory/pipelines-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Azure PowerShell for automation tasks (such as disabling triggers and approving private endpoints) and links to PowerShell-based sample scripts, but does not provide equivalent CLI, Bash, or Linux/macOS instructions. There is no mention of cross-platform tools or examples, and automation guidance is centered on Windows tooling.
Recommendations
  • Provide equivalent examples using Azure CLI (az), which is cross-platform, alongside PowerShell instructions.
  • Include Bash script samples for disabling triggers and automating endpoint approvals.
  • Explicitly mention that all automation steps can be performed on Linux/macOS and provide links or code samples.
  • Reference platform-agnostic APIs (e.g., REST API) for tasks currently described with PowerShell.
  • Add a note clarifying that PowerShell is available on Linux/macOS, but also offer CLI/Bash alternatives for users who prefer native tools.
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references Azure PowerShell as a primary method for provisioning and managing Azure-SSIS IR, and links to a PowerShell-specific guide. There are no examples or mentions of Linux/macOS CLI tools (such as Azure CLI or Bash scripts), nor are cross-platform alternatives presented. This creates friction for users on Linux or macOS who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, if relevant, and provide installation guidance.
  • Ensure that all referenced guides (e.g., joining via PowerShell) have parallel guides for Azure CLI or REST API.
  • Present cross-platform methods (ADF UI, Azure CLI) before or alongside PowerShell examples to avoid Windows-first impression.
Data Factory Managed virtual network and managed private endpoints ...ta-factory/managed-virtual-network-private-endpoint.md
Medium Priority View Details →
Scanned: 2026-01-13 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 provides only Azure PowerShell examples for creating managed virtual networks and private endpoints, with no equivalent Azure CLI, REST API, or ARM template instructions. The PowerShell-centric approach assumes Windows usage and may exclude Linux/macOS users who typically use Azure CLI or REST. Additionally, the presence of 'devx-track-azurepowershell' in metadata and the absence of Linux/macOS-specific guidance or parity in example ordering further reinforce a Windows-first bias.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands.
  • Include REST API and ARM template instructions for resource creation.
  • Explicitly mention cross-platform tools and provide guidance for Linux/macOS users.
  • Order examples so that CLI and REST options appear before or alongside PowerShell.
  • Review screenshots and UI instructions to ensure they are not Windows-specific.
Data Factory Programmatically monitor an Azure Data Factory ...main/articles/data-factory/monitor-programmatically.md
Medium Priority View Details →
Scanned: 2026-01-13 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 provides REST API examples exclusively using PowerShell scripts, which are native to Windows and not available by default on Linux/macOS. There are no equivalent Linux/macOS shell (e.g., Bash, curl) examples for REST API usage. Additionally, PowerShell is given its own dedicated section, and Windows-centric tools (PowerShell cmdlets) are referenced throughout. This creates friction for Linux/macOS users who cannot easily follow the REST API or PowerShell instructions.
Recommendations
  • Add REST API examples using Bash and curl, demonstrating how to authenticate and query pipeline runs from Linux/macOS.
  • Include notes or links for cross-platform alternatives to PowerShell scripts, such as Azure CLI or Python scripts.
  • Ensure that REST API sections provide both PowerShell and Bash/curl examples, or at least mention how Linux/macOS users can perform equivalent operations.
  • Consider reordering or grouping examples so that Windows and Linux/macOS approaches are presented with equal prominence.
Data Factory Join Azure-SSIS integration runtime to a virtual network via Azure portal ...join-azure-ssis-integration-runtime-virtual-network-ui.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes joining Azure-SSIS IR to a virtual network via the Azure portal, which is a web-based GUI accessible from any OS. However, it repeatedly references starting Microsoft Edge or Google Chrome, with no mention of Linux-specific browsers (e.g., Firefox) or confirmation that the portal works on Linux/macOS. The only alternative method referenced is a link to a PowerShell-based guide, which is Windows-centric; there is no mention of Bash/CLI or Linux-native automation. No Linux/macOS-specific tools, patterns, or troubleshooting are discussed.
Recommendations
  • Explicitly confirm Azure portal compatibility with Linux/macOS browsers (e.g., Firefox, Chromium, Safari) and update browser recommendations accordingly.
  • Add guidance or links for performing these steps using Azure CLI or REST API, which are cross-platform and Linux-friendly.
  • Include troubleshooting notes or tips for Linux/macOS users, such as handling clipboard operations, file saving, or browser-specific behaviors.
  • Reference Linux-native automation options (e.g., Bash scripts using Azure CLI) alongside PowerShell alternatives.
Data Factory Reconfigure the Azure-SSIS integration runtime .../data-factory/manage-azure-ssis-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-13 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 provides detailed instructions and examples exclusively using Azure PowerShell cmdlets, which are most commonly used and best supported on Windows. There are no equivalent examples for Linux/macOS users (e.g., using Azure CLI, REST API, or cross-platform scripting). The PowerShell section is prominent and detailed, while no alternative tooling or parity guidance is offered for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API instructions or sample payloads for reconfiguring and deleting Azure-SSIS IRs, which can be used from any OS.
  • Explicitly state OS compatibility for PowerShell scripts and provide guidance for installing and using PowerShell Core on Linux/macOS if PowerShell must be used.
  • Reorder or parallelize examples so that cross-platform options (Azure CLI, REST API) are presented alongside or before Windows-specific tools.
  • Add a note clarifying which tools are supported on which platforms, and link to installation guides for Linux/macOS users.
Data Factory Monitor integration runtime in Azure Data Factory ...n/articles/data-factory/monitor-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell-based examples and cmdlets for monitoring integration runtimes in Azure Data Factory. There are no CLI, Bash, or cross-platform code samples, and the self-hosted integration runtime is described as being installed on 'on-premises Windows machine' with no mention of Linux support or alternatives. Windows tools and patterns (PowerShell, SSMS, SSDT) are referenced throughout, while Linux/macOS users are left without guidance or parity.
Recommendations
  • Add equivalent Azure CLI examples for all monitoring tasks, especially for getting integration runtime status and metrics.
  • Clarify whether self-hosted integration runtime can be installed on Linux/macOS, and provide instructions or links if supported.
  • Include Bash or shell script examples for JSON output parsing and monitoring.
  • Mention and document cross-platform tools (e.g., Azure portal, REST API) for monitoring, with examples.
  • Rephrase references to 'Windows machine' to 'supported operating systems' and specify OS requirements.
  • Ensure that all code samples and instructions are presented for both Windows and Linux/macOS users, or clearly state platform limitations.
Data Factory Monitor SSIS operations with Azure Monitor ...e-docs/blob/main/articles/data-factory/monitor-ssis.md
Medium Priority View Details →
Scanned: 2026-01-13 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 moderate Windows bias. It references Windows-centric tools such as SSMS (SQL Server Management Studio), SSDT (SQL Server Data Tools), and T-SQL, which are primarily used on Windows. The invocation methods and examples focus on these tools, with no mention of Linux/macOS alternatives or cross-platform command-line approaches. There are no examples or guidance for Linux users, and Windows tools are mentioned first and exclusively.
Recommendations
  • Include examples using cross-platform tools such as Azure CLI and REST API for monitoring and querying SSIS operations.
  • Mention and provide guidance for using Azure Data Studio, which is available on Linux/macOS, as an alternative to SSMS.
  • Clarify which steps and tools are Windows-only and provide Linux/macOS equivalents or workarounds where possible.
  • Add explicit examples or instructions for Linux/macOS users to ensure parity in monitoring and querying SSIS operations.
Data Factory Transform data by using Spark in Azure Data Factory ...s/data-factory/tutorial-transform-data-spark-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by listing Azure PowerShell as a prerequisite and linking only to Windows-centric installation instructions. There are no examples or guidance for using Azure CLI, Bash, or Linux/macOS tools to upload files to Azure Blob Storage, nor is there mention of cross-platform alternatives. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add instructions for uploading files to Azure Blob Storage using Azure CLI, which is cross-platform.
  • Include Bash or shell script examples for Linux/macOS users.
  • Link to Azure CLI installation and usage guides alongside PowerShell.
  • Clarify that Azure PowerShell is optional and that Azure CLI or Storage Explorer can be used on any OS.
Data Factory Create an Azure Data Factory using Bicep ...s/data-factory/quickstart-create-data-factory-bicep.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows a moderate Windows bias: it references Notepad as the example text editor, presents PowerShell examples alongside CLI but always includes them, and refers to Windows tools and patterns (e.g., Notepad, PowerShell) without mentioning Linux/macOS equivalents. Linux users are not blocked, but the guidance is less tailored to their experience.
Recommendations
  • When suggesting a text editor, mention cross-platform or Linux/macOS editors (e.g., 'a text editor such as Notepad (Windows), nano (Linux), or TextEdit (macOS)').
  • Clarify that Azure CLI commands work on all platforms and consider making CLI the default or first example, with PowerShell as an alternative.
  • Where PowerShell is shown, note that it is available cross-platform, or provide Bash equivalents if relevant.
  • Avoid referencing Windows-specific tools or patterns unless also mentioning Linux/macOS alternatives.
  • Explicitly state that all steps can be performed on Linux/macOS and provide links to relevant installation/setup guides if needed.
Data Factory Self-hosted integration runtime autoupdate and expire notification ...factory/self-hosted-integration-runtime-auto-update.md
Medium Priority View Details →
Scanned: 2026-01-13 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 by providing only PowerShell-based examples and commands for managing self-hosted integration runtime updates and expiration. There are no Linux/macOS-specific instructions, nor are cross-platform alternatives (such as Bash or CLI-only workflows) presented. The use of 'self-hosted integration runtime client' and screenshots further suggest a Windows-centric approach, with no mention of Linux installation or management patterns.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users using Azure CLI.
  • Clarify whether the 'self-hosted integration runtime client' is available and supported on Linux/macOS, and if so, include relevant screenshots and instructions.
  • Explicitly mention platform support and differences in update/notification workflows between Windows and Linux/macOS.
  • Add a section or callout for Linux/macOS users, outlining any required steps or limitations.
  • Ensure that CLI commands are presented in a platform-neutral way, or offer both PowerShell and Bash syntax side-by-side.
Data Factory Create Azure Data Factory using .NET SDK ...data-factory/quickstart-create-data-factory-dot-net.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows users, with all examples and instructions assuming Visual Studio on Windows, use of PowerShell/NuGet Package Manager Console, and Windows-specific tooling. There are no instructions or examples for Linux/macOS users, such as using .NET CLI, VS Code, or alternative package managers. This creates friction for non-Windows users attempting to follow the quickstart.
Recommendations
  • Add instructions for creating and running the .NET project using .NET CLI (dotnet new, dotnet add package, dotnet run) suitable for Linux/macOS.
  • Include examples for installing NuGet packages via dotnet CLI, not just PowerShell/Package Manager Console.
  • Mention and provide guidance for using VS Code or other cross-platform editors as alternatives to Visual Studio.
  • Clarify that the .NET SDK and Azure Data Factory APIs are cross-platform and can be used on Linux/macOS.
  • Add troubleshooting notes or links for Linux/macOS users regarding authentication and environment setup.
  • Avoid assuming Windows-only tools (e.g., Azure Storage Explorer) and suggest cross-platform alternatives.
Data Factory Troubleshoot security and access control issues ...tory/security-and-access-control-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation demonstrates a notable Windows bias, especially in troubleshooting steps involving network connectivity and DNS resolution. Windows-specific tools (PsPing, Notepad, editing C:\Windows\System32\drivers\etc\hosts) are referenced exclusively, with no mention of Linux/macOS equivalents. Example commands and file paths are Windows-only, and instructions for editing the hosts file are tailored to Windows users. No Linux or macOS alternatives are provided for key troubleshooting steps.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting steps, such as using 'ping', 'nc', or 'curl' for connectivity checks, and editing '/etc/hosts' for host file changes.
  • Include example commands for Linux/macOS alongside Windows commands, and clarify cross-platform applicability.
  • Mention cross-platform tools (e.g., 'ping', 'traceroute', 'nslookup') and avoid referencing Windows-only utilities unless alternatives are given.
  • Add screenshots or instructions for Linux/macOS environments where relevant.
  • Explicitly state when steps are OS-specific and provide parity for all supported platforms.
Data Factory Troubleshoot SSIS Integration Runtime management ...ry/ssis-integration-runtime-management-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing PowerShell cmdlets as a primary troubleshooting interface and suggesting the use of SQL Server Management Studio (SSMS), which is a Windows-only tool, for connectivity checks. There are no Linux/macOS equivalents or examples provided, and troubleshooting steps are described in a way that assumes Windows environments (e.g., 'create a new VM', 'install SSMS'). This may create friction for users on Linux or macOS platforms.
Recommendations
  • Provide troubleshooting examples using Azure CLI and REST API, which are cross-platform.
  • Mention and demonstrate the use of Azure Data Studio as an alternative to SSMS for Linux/macOS users.
  • Include explicit instructions for performing connectivity checks and script testing on Linux/macOS VMs.
  • Clarify that PowerShell is available cross-platform, but provide equivalent Bash/CLI commands where possible.
  • Add notes or sections highlighting platform-agnostic approaches to common troubleshooting tasks.
Data Factory Use custom activities in a pipeline ...s/data-factory/transform-data-using-custom-activity.md
Medium Priority View Details →
Scanned: 2026-01-13 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 exhibits a notable Windows bias. PowerShell commands are the only CLI examples given for managing pipelines and retrieving outputs, with no equivalent Bash, Azure CLI, or cross-platform alternatives. The use of .exe files (e.g., helloworld.exe, SampleApp.exe) as default examples further centers Windows environments. Windows-native commands (e.g., 'cmd /c dir', 'cmd /c echo hello world') are used in examples, and there is no mention of Linux shell equivalents or guidance for Linux/macOS users. The documentation assumes familiarity with Windows tools and patterns, making it less accessible for Linux/macOS users.
Recommendations
  • Provide Azure CLI and/or Bash examples alongside PowerShell for all command-line operations (e.g., starting pipelines, retrieving outputs).
  • Include Linux/macOS-compatible examples for custom activity commands (e.g., use 'ls' or 'echo' in Bash, and reference .sh scripts or ELF binaries instead of only .exe files).
  • Clarify that Azure Batch pools can be provisioned with Linux nodes and provide guidance/examples for both Windows and Linux pool configurations.
  • Explicitly state OS compatibility and how to adapt commands/applications for non-Windows environments.
  • Reorder examples or provide parallel examples so that Linux/macOS users are not always secondary.
Data Factory Transform data using Hadoop Pig activity ...ticles/data-factory/transform-data-using-hadoop-pig.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references a tutorial that is specifically for Spark transformation using PowerShell, which is a Windows-centric tool. No Linux or cross-platform CLI examples are provided for running or managing Pig activities. The documentation does not mention Linux tools or provide parity for Linux/macOS users in terms of workflow or example commands.
Recommendations
  • Add equivalent Linux/macOS CLI examples (e.g., using Azure CLI, Bash, or Python SDK) for managing Pig activities.
  • Reference tutorials or guides that use cross-platform tools, not just PowerShell.
  • Explicitly state that all steps can be performed on Linux/macOS and provide links to relevant documentation.
  • Ensure that any referenced scripts or commands are shown in both Windows and Linux formats (e.g., file paths, command syntax).
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for Azure Data Factory source control demonstrates a moderate Windows bias. PowerShell is referenced as a method for publishing changes and updating configuration, but there are no equivalent Linux/macOS CLI examples (e.g., Bash, Azure CLI). Troubleshooting and workflow sections mention PowerShell and SDK usage without cross-platform alternatives. Additionally, some browser-specific notes reference Microsoft Edge, a Windows-centric browser, and Visual Studio URLs are used for Azure DevOps, which is more common on Windows. There are no explicit Linux/macOS instructions or examples, and Windows tools/patterns are mentioned before any cross-platform alternatives.
Recommendations
  • Add equivalent examples for Linux/macOS users, such as Bash scripts or Azure CLI commands, wherever PowerShell is referenced.
  • Explicitly mention cross-platform compatibility for SDKs and CLI tools, and provide links to Linux/macOS installation guides.
  • Include troubleshooting steps and configuration instructions using Azure CLI or REST API, not just PowerShell.
  • Reference browser compatibility for Chrome, Firefox, and Safari, not just Microsoft Edge.
  • Where Visual Studio or Windows-specific URLs are used, clarify that these can be accessed from any OS and provide alternative instructions if needed.
Data Factory Transform data using Hadoop Streaming activity .../data-factory/transform-data-using-hadoop-streaming.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias towards Windows by using '.exe' files for mapper, reducer, and combiner programs in the JSON sample, which are Windows executables. There are no examples or mentions of Linux-compatible scripts (such as Python, Bash, or shell scripts), which are more common in Hadoop Streaming on Linux-based HDInsight clusters. The Windows-style executable is shown first and exclusively, with no Linux alternatives provided.
Recommendations
  • Provide examples using Linux-compatible scripts (e.g., Python, Bash, or shell scripts) for mapper and reducer, such as 'mapper.py' and 'reducer.sh'.
  • Clarify that both Windows and Linux executables/scripts are supported, and specify any platform limitations.
  • Add a section or note explaining how to prepare and upload Linux-based scripts to Azure Storage for use in HDInsight Streaming.
  • Show Linux examples before or alongside Windows examples to ensure parity.
Data Factory Copy data from SQL Server to Blob storage using Azure portal ...n/articles/data-factory/tutorial-hybrid-copy-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias. It exclusively references SQL Server Management Studio (SSMS), a Windows-only tool, for database setup and management, without mentioning Linux-compatible alternatives. There are no instructions or examples for performing equivalent steps on Linux or macOS, such as using Azure Data Studio or command-line tools. The integration runtime setup instructions do not clarify Linux support or provide Linux-specific guidance, and all screenshots and UI references assume a Windows environment.
Recommendations
  • Add instructions for setting up the SQL Server database using cross-platform tools like Azure Data Studio or sqlcmd, including installation and usage on Linux/macOS.
  • Clarify whether the self-hosted integration runtime can be installed on Linux/macOS, and provide platform-specific setup instructions if supported.
  • Include notes or sections for Linux/macOS users, highlighting any differences in process or prerequisites.
  • Present examples and tool recommendations for both Windows and Linux/macOS environments, or at least mention alternatives.
  • Ensure screenshots and UI references do not assume a Windows-only environment.
Medium Priority View Details →
Scanned: 2026-01-13 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 exhibits a Windows bias by requiring Azure PowerShell, referencing Windows file paths (e.g., hosts file location), and omitting Linux/macOS equivalents for key steps such as editing the hosts file or installing the self-hosted integration runtime. All examples and instructions assume a Windows environment, with no mention of Linux or macOS alternatives for VM setup, command-line tools, or file system locations.
Recommendations
  • Provide equivalent instructions for Linux/macOS environments, including how to install Azure CLI and self-hosted integration runtime on those platforms.
  • Include Linux/macOS file paths for editing the hosts file (e.g., /etc/hosts) and clarify any differences in syntax or permissions.
  • Offer examples using Azure CLI in addition to Azure PowerShell, and clarify which steps are cross-platform.
  • Explicitly state platform requirements or limitations for the self-hosted integration runtime and VM setup.
  • Add notes or sections highlighting any differences or additional steps required for Linux/macOS users.
Data Factory Provision the Azure-SSIS integration runtime ...es/data-factory/tutorial-deploy-ssis-packages-azure.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
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 Windows bias by exclusively referencing Windows-centric tools (SSDT, SSMS, dtutil, AzureDTExec), mentioning PowerShell for firewall configuration, and omitting Linux/macOS alternatives or examples. There are no instructions or examples for deploying or managing SSIS packages from Linux/macOS environments, nor are cross-platform command-line utilities or Azure CLI alternatives discussed. Windows tools and patterns are presented as the default or only option, creating friction for non-Windows users.
Recommendations
  • Include instructions and examples for using Azure CLI to configure firewall rules and other Azure resources, as an alternative to PowerShell.
  • Mention and provide guidance for cross-platform tools (e.g., Azure Data Studio, Azure CLI, REST API) for deploying and managing SSIS packages.
  • Clarify which steps can be performed from Linux/macOS and provide explicit examples or links to relevant documentation.
  • List Linux/macOS-compatible command-line utilities for SSIS package deployment and execution, if available, or note limitations.
  • Present cross-platform options before or alongside Windows-specific tools, rather than exclusively or first.
Data Factory Copy on-premises data using the Azure Copy Data tool ...rticles/data-factory/tutorial-hybrid-copy-data-tool.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. It exclusively references Windows-specific tools such as SQL Server Management Studio (SSMS) for database setup, and the express setup for the self-hosted integration runtime, which is primarily a Windows installer. There are no instructions or examples for Linux or macOS users, nor are alternative tools or setup patterns mentioned. The documentation assumes the user is on Windows throughout, creating friction for Linux/macOS users attempting to follow the tutorial.
Recommendations
  • Include instructions for setting up the SQL Server database using cross-platform tools (e.g., Azure Data Studio, sqlcmd, or Docker-based SQL Server).
  • Provide guidance for installing and registering the self-hosted integration runtime on Linux and macOS, including manual setup steps and supported platforms.
  • Mention and link to alternative database management tools available on Linux/macOS.
  • Add notes or sections clarifying platform support and any limitations for non-Windows users.
  • Ensure screenshots and step-by-step instructions are not exclusively Windows-centric.
Data Factory Transform data using Spark in Azure Data Factory ...ta-factory/tutorial-transform-data-spark-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The tutorial exclusively uses Azure PowerShell for all deployment, management, and monitoring steps, with no mention of Azure CLI, Bash, or cross-platform alternatives. All code and workflow examples are PowerShell-centric, and instructions assume the user is familiar with PowerShell and its environment. There are no Linux/macOS-specific instructions or examples, and the only prerequisite for command-line work is Azure PowerShell, which is primarily associated with Windows.
Recommendations
  • Provide equivalent Azure CLI commands and workflows alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux/macOS, and provide installation instructions for those platforms.
  • Add Bash script examples for file manipulation and deployment steps where appropriate.
  • Reorder examples or provide parallel sections so that Linux/macOS users do not feel secondary to Windows users.
  • Include troubleshooting notes for common issues encountered on Linux/macOS (e.g., authentication, file paths, environment setup).
Data Factory Configure a virtual network for injection of Azure-SSIS integration runtime ...ssis-integration-runtime-virtual-network-configuration.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal UI for configuration steps and only mentioning Azure PowerShell as an alternative in the related content. There are no examples or instructions for Linux users, such as using Azure CLI or Bash scripts, nor is there mention of Linux-specific tools or workflows. The documentation assumes a graphical interface and Windows-centric patterns, omitting parity for Linux command-line users.
Recommendations
  • Add step-by-step instructions using Azure CLI for all configuration tasks, including registering resource providers, delegating subnets, and granting permissions.
  • Include Bash script examples for automating network configuration tasks.
  • Reference Linux-compatible tools and workflows alongside Azure portal and PowerShell options.
  • Ensure that all examples and screenshots are supplemented with equivalent command-line instructions for cross-platform accessibility.
  • Explicitly mention that all tasks can be performed on Linux, macOS, and Windows, and provide links to relevant cross-platform documentation.
Data Factory Copy data from Oracle Responsys (Preview) ...in/articles/data-factory/connector-oracle-responsys.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions Azure PowerShell as a supported SDK for pipeline creation and references Azure Resource Manager templates, which are commonly used in Windows environments. There are no explicit Linux or cross-platform CLI examples (such as Azure CLI or bash scripts), nor are Linux-specific tools or workflows mentioned. The order of SDKs listed puts PowerShell before REST API and ARM templates, suggesting a Windows-first approach. No Linux-specific instructions, screenshots, or troubleshooting are provided.
Recommendations
  • Add Azure CLI examples alongside PowerShell for pipeline creation and management.
  • Include references to cross-platform tools and workflows, such as bash scripting or Linux-based automation.
  • Ensure that SDK and tool lists do not prioritize Windows-specific options; present them in a neutral or alphabetical order.
  • Provide troubleshooting steps or notes relevant to Linux environments, especially for self-hosted integration runtime scenarios.
  • Add screenshots or instructions that reflect Linux usage where applicable, such as using the Azure portal from Linux browsers or configuring self-hosted IR on Linux.