Data Factory
564
Total Pages
364
Linux-Friendly Pages
200
Pages with Bias
35.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
1000 issues found
Showing 551-575 of 1000 flagged pages
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-incremental-copy-change-tracking-feature-portal.md
...torial-incremental-copy-change-tracking-feature-portal.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exhibits a Windows bias by exclusively referencing Windows-specific tools (SQL Server Management Studio) for database access and omitting any mention of Linux-compatible alternatives. There are no examples or instructions for Linux users to connect to Azure SQL Database (e.g., via Azure Data Studio, sqlcmd, or other cross-platform tools). The only client tool mentioned is SQL Server Management Studio, which is Windows-only, and it is introduced without alternatives or parity for Linux/macOS users.
Recommendations
- Add instructions and examples for connecting to Azure SQL Database using cross-platform tools such as Azure Data Studio or the sqlcmd command-line utility.
- Explicitly mention that SQL Server Management Studio is a Windows-only tool and provide Linux/macOS alternatives in the same section.
- Wherever database queries are to be run, provide command-line examples (e.g., using sqlcmd) in addition to GUI-based instructions.
- Review screenshots and UI steps to ensure they are not exclusively based on Windows-only tools, or supplement them with cross-platform tool screenshots where possible.
- Consider a 'Platform note' at the start of the tutorial to guide Linux/macOS users to appropriate tools and steps.
Create Pull Request
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-web-table.md
...blob/main/articles/data-factory/connector-web-table.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a bias towards Windows by exclusively recommending Microsoft Excel (2016/2013) and Power BIβboth Windows-centric toolsβfor extracting the table index from an HTML page. There are no Linux or cross-platform alternatives mentioned, nor are command-line or open-source tools suggested. The only workflow for a key step (getting the table index) is described using Windows GUI applications, leaving Linux users without guidance.
Recommendations
- Provide alternative instructions for extracting the table index using cross-platform or Linux tools, such as Python scripts (e.g., using BeautifulSoup or pandas), curl, or command-line utilities.
- Include example commands or scripts that work on Linux/macOS as well as Windows.
- Mention open-source tools (e.g., LibreOffice Calc, web scraping libraries) that can perform similar tasks to Excel/Power Query.
- Reorder or parallelize the instructions so that Windows and Linux/macOS approaches are presented with equal prominence.
- Explicitly state that the process can be completed on non-Windows platforms, and provide links or references to relevant resources.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-xero.md
...docs/blob/main/articles/data-factory/connector-xero.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows versions as prerequisites for the self-hosted integration runtime, without mentioning Linux support or providing Linux-specific guidance. There are no Linux or cross-platform examples for key steps such as generating private keys, and the documentation does not clarify whether the integration runtime or connector can be run on Linux. All example commands and operational notes are either Windows-centric or omit Linux entirely.
Recommendations
- Explicitly state whether the self-hosted integration runtime and Xero connector are supported on Linux, and if so, provide Linux prerequisites alongside Windows.
- For steps involving key generation (e.g., generating privatekey.pem with openssl), provide example commands for both Windows (using Git Bash or WSL) and Linux environments.
- If certain features are Windows-only, clearly label them as such and, where possible, provide Linux alternatives or workarounds.
- Include screenshots or instructions for Linux-based Azure Data Factory/Synapse deployments if supported.
- Review all operational notes and ensure parity by adding Linux-specific instructions or clarifications where relevant.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-hybrid-copy-powershell.md
...ticles/data-factory/tutorial-hybrid-copy-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All command-line examples use PowerShell, and the installation and configuration steps for the self-hosted integration runtime explicitly require a Windows machine. There are no instructions or examples for Linux or macOS users, and Windows-specific tools (such as SQL Server Management Studio and Notepad) are referenced without alternatives. The documentation assumes the user is operating on Windows from start to finish.
Recommendations
- Provide equivalent instructions and examples for Linux and macOS users, including using Azure CLI or Bash scripts instead of only PowerShell.
- Mention and demonstrate cross-platform tools (e.g., Azure Data Studio for SQL Server management, VS Code, or nano/vim for editing JSON files) alongside Windows-only tools.
- Clarify platform requirements early in the prerequisites, and if the self-hosted integration runtime is Windows-only, explicitly state this and suggest alternatives (such as using Azure-hosted integration runtime or Docker-based solutions) for Linux users.
- Where possible, include links or references to Linux/macOS installation guides for required tools (e.g., Azure CLI, Data Factory integration runtime if available, SQL Server clients).
- Structure the documentation so that platform-agnostic steps come first, and platform-specific instructions are clearly separated, with Linux/macOS sections given equal prominence.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-diagnostic-tool.md
...ory/self-hosted-integration-runtime-diagnostic-tool.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references Windows tools and workflows, such as the use of 'dmgcmd.exe' and the Configuration Manager UI, with no mention of Linux equivalents or support. There are no Linux command-line examples or references to Linux-based installation or troubleshooting, implying the tool is Windows-only or that Linux users are not considered.
Recommendations
- Explicitly state whether the diagnostic tool is Windows-only or if Linux is supported.
- If Linux is supported, provide equivalent Linux command-line instructions and examples (e.g., using a .sh script or Linux binary).
- Mention Linux-specific troubleshooting steps or UI, if available.
- If Linux is not supported, clarify this early in the documentation to set user expectations.
- Consider adding a section on cross-platform support and any differences in usage or output between Windows and Linux.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-automate-azure-pipelines.md
...ntinuous-integration-delivery-automate-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong bias towards Windows environments by exclusively providing PowerShell-based automation examples and instructions. It references Azure PowerShell modules and scripts, assumes the use of .ps1 files, and does not mention or provide equivalent Bash, CLI, or cross-platform scripting alternatives. There is no guidance for Linux or macOS users, nor are there examples using the Azure CLI or other non-Windows-native tools. The documentation also refers to downloading and running PowerShell scripts, further reinforcing a Windows-centric approach.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands and Bash scripts for all PowerShell-based instructions, especially for stopping and starting triggers.
- Explicitly mention that Azure Pipelines agents can run on Linux and macOS, and provide guidance for those environments.
- Include notes or sections for cross-platform compatibility, highlighting any differences or requirements for Linux/macOS users.
- Where PowerShell scripts are referenced, offer Bash or shell script alternatives, or at least link to resources for non-Windows users.
- Avoid assuming the use of .ps1 files and PowerShell modules as the only automation method; present Azure CLI as a first-class option.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-incremental-copy-multiple-tables-portal.md
...ry/tutorial-incremental-copy-multiple-tables-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (SQL Server Management Studio), using Windows-specific terminology (e.g., 'Server Explorer', 'New Query'), and omitting any mention of Linux-compatible alternatives or command-line approaches. There are no examples or instructions for performing the same tasks on Linux systems, such as using Azure Data Studio, sqlcmd, or other cross-platform tools. The instructions for installing the self-hosted integration runtime also assume a Windows environment, with no mention of Linux installation steps.
Recommendations
- Include instructions and examples for Linux users, such as using Azure Data Studio or sqlcmd for database operations.
- Mention and provide steps for installing the self-hosted integration runtime on Linux, referencing the official cross-platform installation documentation.
- Replace or supplement references to 'SQL Server Management Studio' and 'Server Explorer' with cross-platform alternatives.
- Add notes or sections highlighting differences or additional steps required for Linux environments.
- Ensure screenshots and UI instructions are not exclusively tailored to Windows-only tools.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-incremental-copy-overview.md
...les/data-factory/tutorial-incremental-copy-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell-based tutorials (as indicated by the '-powershell.md' suffix in linked tutorials), and does not provide equivalent Linux/bash/CLI examples. The terminology and workflow examples focus on Windows-centric tools and patterns, with no mention of Linux shell, bash, or cross-platform command-line alternatives. This may limit accessibility for users on Linux or macOS platforms.
Recommendations
- Provide parallel step-by-step tutorials using Azure CLI, Bash, or cross-platform scripting tools alongside PowerShell examples.
- Explicitly mention and link to Linux-compatible tools and workflows where possible.
- Ensure that all code samples and automation scripts are available in both PowerShell and Bash/CLI formats.
- Add a section or callout for Linux/macOS users, highlighting any platform-specific considerations or differences.
- Review and update tutorial file names and links to reflect cross-platform parity (e.g., '-powershell.md' and '-bash.md' versions).
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-sample-script.md
...ctory/continuous-integration-delivery-sample-script.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell scripts and Azure PowerShell tasks for all examples, with no mention of Bash, Azure CLI, or Linux-native scripting alternatives. All instructions, sample scripts, and YAML pipeline tasks are PowerShell-centric, assuming the user will use PowerShell Core even in cross-platform scenarios. There are no Linux/Unix shell or Azure CLI equivalents provided, and the documentation does not address how to achieve the same tasks outside of the PowerShell ecosystem.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for Linux users.
- Explicitly mention that PowerShell Core is cross-platform, but also offer native Bash/CLI alternatives for users who prefer not to use PowerShell.
- Include YAML pipeline tasks that demonstrate running Bash scripts or AzureCLI@2 tasks to achieve the same pre- and post-deployment automation.
- Add a section discussing cross-platform considerations and how to adapt the workflow for Linux-based build agents.
- Reference official Azure CLI documentation and provide links to relevant CLI commands for managing Data Factory triggers and deployments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery.md
...ticles/data-factory/continuous-integration-delivery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a strong bias towards Windows environments, particularly through its exclusive recommendation and usage of PowerShell scripts for pre- and post-deployment tasks. There are no examples or guidance for performing these tasks using Linux-native tools (such as Bash or shell scripts), nor is there mention of cross-platform alternatives. The documentation also assumes the use of PowerShell Core but does not clarify how to adapt the process for Linux users, and Windows-centric tools and patterns are referenced without Linux parity.
Recommendations
- Provide equivalent Bash or shell script examples for pre- and post-deployment tasks, alongside the PowerShell scripts.
- Explicitly state that PowerShell Core is cross-platform and provide instructions for installing and running it on Linux/macOS.
- Mention and, where possible, provide examples using Azure CLI (az) commands for deployment steps, as these are cross-platform.
- Reorder or supplement recommendations so that Linux and cross-platform options are presented alongside or before Windows-specific tools.
- Clarify any platform-specific limitations or considerations for Linux/macOS users in the relevant sections.
- Link to documentation or guides for running Azure DevOps pipelines and scripts in Linux-based agents.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-if-condition-activity.md
...les/data-factory/control-flow-if-condition-activity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell command examples for pipeline deployment and execution, referencing Windows file paths (e.g., C:\ADF), and omitting any equivalent instructions for Linux or cross-platform environments (such as Azure CLI or Bash). There is no mention of Linux tools or shell scripting, and the workflow assumes a Windows/PowerShell context throughout.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, using Bash syntax and Linux file paths (e.g., /home/user/ADF).
- Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
- Where file paths are referenced, show both Windows and Linux path formats.
- Consider providing a table or section comparing PowerShell and CLI/Bash approaches for common tasks.
- Update the note and tutorial references to include Linux/macOS walkthroughs, not just PowerShell.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-switch-activity.md
.../articles/data-factory/control-flow-switch-activity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All command-line examples are provided exclusively in PowerShell, with explicit references to Windows file paths (e.g., C:\ADF). There is no mention of Linux, Bash, or cross-platform alternatives for running the pipeline or managing files. The tutorial and walkthrough links also focus on Azure PowerShell, reinforcing the Windows-centric approach.
Recommendations
- Provide equivalent Bash/CLI examples for Linux and macOS users, using Azure CLI commands (az datafactory ...).
- Use cross-platform file path examples (e.g., /home/user/ADF or <path-to-adf-folder>) or clarify that file paths should be adapted to the user's OS.
- Include a note or section on how to perform the same steps on Linux/macOS, including installation and authentication steps for Azure CLI.
- Reference tutorials or quickstarts that use Azure CLI or REST API, not just Azure PowerShell.
- Avoid assuming the user is on Windows by default in instructions and examples.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/author-global-parameters.md
...main/articles/data-factory/author-global-parameters.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references deploying global parameters via a PowerShell script as the only example of scripting automation for CI/CD, without mentioning Linux-compatible alternatives (such as Azure CLI, Bash, or cross-platform scripting). This suggests a bias toward Windows tooling and omits guidance for users on Linux or macOS platforms.
Recommendations
- Provide equivalent examples using Azure CLI or Bash scripts for deploying global parameters, ensuring Linux and macOS users have clear guidance.
- Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, or clarify if only Windows PowerShell is supported.
- Add a note or section describing how to perform CI/CD tasks related to global parameters on Linux environments.
- Where possible, present cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools like PowerShell.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/apply-dataops.md
...-docs/blob/main/articles/data-factory/apply-dataops.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the automated testing section, where .NET/NUnit with Visual Studio and PowerShell are highlighted as primary tools for automated testing and CI/CD scripting. There are no examples or explicit mentions of Linux-based tools, shell scripting, or cross-platform alternatives for these tasks. The documentation assumes familiarity with Windows-centric tooling and omits Linux/Unix equivalents or guidance.
Recommendations
- Include examples and references for Linux-based CI/CD and testing workflows, such as using bash scripts, Python, or cross-platform test runners.
- Mention and provide examples for running Azure CLI commands in both Windows (PowerShell) and Linux (bash) environments.
- Highlight cross-platform editors and tools (e.g., VS Code, Git CLI, GitHub Actions) alongside Visual Studio and PowerShell.
- Add explicit notes or sections on how to perform key tasks (e.g., automated testing, deployment scripting) on Linux/macOS systems.
- Where PowerShell is mentioned, provide equivalent bash or shell script snippets.
- Reference cross-platform CI/CD pipelines (e.g., GitHub Actions, Azure Pipelines with Linux agents) and show parity in instructions.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-package-store.md
...actory/azure-ssis-integration-runtime-package-store.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, with all examples and instructions assuming the use of Windows tools such as SSMS, dtutil, cmdkey, net use, and DOS batch scripting. There is no mention of Linux or cross-platform alternatives, and no guidance is provided for users operating from Linux or macOS systems.
Recommendations
- Provide equivalent instructions and examples for Linux environments, including how to connect to Azure Files (e.g., using SMB mounting on Linux) and how to run dtutil if available or alternatives for package deployment.
- Mention whether SSMS and dtutil are available or supported on non-Windows platforms, and if not, suggest workarounds or alternative tools (such as Azure Data Studio or REST APIs).
- Include PowerShell Core (cross-platform) or Bash script examples where possible, especially for batch operations.
- Clarify any platform limitations explicitly at the start of the documentation, so Linux/macOS users know what is and isn't supported.
- If certain features are Windows-only, provide links or references to cross-platform approaches for managing SSIS packages in Azure.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/ci-cd-github-troubleshoot-guide.md
...ticles/data-factory/ci-cd-github-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it does not explicitly present Windows or PowerShell commands as primary examples, it references PowerShell APIs and Windows-centric tools (such as PowerShell and Nunit) without providing equivalent Linux or cross-platform alternatives. There are no explicit Linux shell, Bash, or CLI examples, and the documentation assumes familiarity with Windows-based DevOps tooling. The mention of PowerShell APIs and Nunit for testing, without mentioning Linux-friendly alternatives (e.g., Bash, pytest, xUnit), further reinforces this bias. Additionally, there are no explicit instructions or examples for Linux users, and no mention of cross-platform command-line tools.
Recommendations
- Provide equivalent Linux/Bash/CLI examples alongside any PowerShell or Windows-specific instructions.
- Mention and provide examples for cross-platform testing frameworks (e.g., pytest for Python, xUnit for .NET) in addition to Nunit.
- When referencing PowerShell APIs, also mention Azure CLI or REST API alternatives that are platform-agnostic.
- Explicitly state when a tool or method is cross-platform, and clarify any platform-specific limitations.
- Include troubleshooting steps or automation examples that work on Linux agents (e.g., using Bash scripts in Azure Pipelines).
- Review all references to Windows tools and ensure Linux equivalents are documented and easy to find.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-express-virtual-network-injection.md
...-integration-runtime-express-virtual-network-injection.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias primarily through its reliance on PowerShell scripts for configuration (notably in the custom DNS setup), the absence of any Linux/bash/CLI examples for scripting or automation, and the exclusive mention of Windows-centric tools and file formats (e.g., .ps1 scripts). There are no references to Linux shell scripts or cross-platform alternatives, and the related content section only highlights a PowerShell-based approach for joining the virtual network, omitting Azure CLI or other Linux-friendly methods.
Recommendations
- Provide equivalent examples using Azure CLI and bash scripts for all configuration steps, especially for custom setup scripts and automation.
- Include references and links to Linux-based or cross-platform tooling in the related content section (e.g., 'Join Azure-SSIS IR to a virtual network via Azure CLI').
- Offer sample scripts in both PowerShell (.ps1) and bash (.sh) formats, or use platform-agnostic scripting where possible.
- Explicitly state platform compatibility for provided scripts and instructions, and guide users on adapting steps for Linux environments.
- Ensure that any downloadable resources (like setup scripts) have Linux-compatible versions or clear instructions for Linux users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/built-in-preinstalled-components-ssis-integration-runtime.md
...lt-in-preinstalled-components-ssis-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. It explicitly states that Azure-SSIS IR runs on Windows Server 2019 and lists only Windows-based components, drivers, and tools (e.g., OLEDB, ODBC, WMI, MSMQ, SQL Server Native Client, Excel, Access Database Engine). There is no mention of Linux support, Linux-based tools, or cross-platform alternatives. All examples and terminology are Windows-centric, and there are no Linux equivalents or instructions provided.
Recommendations
- Clearly state in the introduction that Azure-SSIS IR is Windows-only, if that is the case, or clarify any Linux support or roadmap.
- If Linux support is planned or available, provide a parallel table or section listing Linux-compatible components, drivers, and tasks.
- Where possible, mention cross-platform alternatives to Windows-specific technologies (e.g., alternatives to WMI, MSMQ, or Excel/Access drivers).
- Add a note or FAQ addressing the lack of Linux support and suggest workarounds or alternatives for Linux users.
- Ensure that future documentation for similar services includes both Windows and Linux perspectives, or explicitly states platform limitations.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/choose-the-right-integration-runtime-configuration.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/choose-the-right-integration-runtime-configuration.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments in its discussion of self-hosted integration runtimes. It references Windows-specific tools (such as the diagnostic tool and PowerShell-based setup), omits explicit Linux installation or management examples, and links to articles that imply or directly use Windows-centric approaches. There is no mention of Linux as a supported platform for self-hosted integration runtime, nor are there examples or guidance for Linux users, which may lead readers to assume Windows is the only or primary supported environment.
Recommendations
- Explicitly state platform support for self-hosted integration runtime, including whether Linux is supported.
- Provide parallel Linux-based setup, configuration, and management instructions alongside any Windows/PowerShell examples.
- Reference or link to Linux-specific diagnostic and monitoring tools if available, or clarify any limitations.
- Ensure that examples and linked articles (such as those for shared integration runtime setup) include both Windows and Linux instructions, or clarify platform applicability.
- Use neutral language (e.g., 'machine' instead of 'Windows machine') unless a feature is truly platform-specific, and always mention alternatives for Linux where possible.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-until-activity.md
...n/articles/data-factory/control-flow-until-activity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples are provided exclusively in PowerShell, with explicit references to Windows file paths (e.g., C:\ADF). There are no examples or guidance for running the same tasks on Linux or macOS, nor are cross-platform tools (such as Azure CLI) mentioned. The instructions and walkthroughs assume a Windows environment, potentially excluding users on other platforms.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works on Windows, Linux, and macOS.
- Use platform-agnostic file paths in examples, or provide both Windows and Linux/macOS path examples (e.g., C:\ADF and ~/ADF).
- Explicitly mention that the JSON definitions and pipeline concepts are platform-independent, and show how to deploy/run them from Linux/macOS.
- Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.
- Where possible, use screenshots or instructions that are not specific to Windows UI conventions.
- Review related tutorials and quickstarts to ensure they also offer Linux/macOS parity.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-standard-virtual-network-injection.md
...integration-runtime-standard-virtual-network-injection.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments, primarily through the exclusive use of PowerShell for scripting examples and references to Windows-specific tools and concepts (e.g., Windows firewall rules, RDP/port 3389, and Secure Access Workstation). There are no Linux CLI (Azure CLI, Bash) equivalents or examples provided, and no mention of Linux-based tooling or workflows. This may hinder users who manage Azure resources from Linux or cross-platform environments.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell scripts for all automation and configuration tasks.
- Include notes or sections on how to perform relevant firewall and NSG configurations from Linux environments, referencing tools like iptables, ufw, or Azure CLI.
- Clarify that RDP/port 3389 and Windows firewall rules are only relevant for Windows-based nodes, and provide guidance for Linux-based scenarios if supported.
- Ensure that all scripting and automation guidance is cross-platform, or clearly indicate when a step is Windows-specific.
- Add a section or callout for Linux administrators, summarizing any differences or additional steps required when managing Azure-SSIS IR from Linux.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-integration-runtime.md
.../articles/data-factory/concepts-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias, particularly in the Self-hosted Integration Runtime (IR) section, where it explicitly states that the self-hosted IR is only supported on Windows operating systems. There is no mention of Linux support, installation steps, or parity. Additionally, tools and examples referenced for SSIS workloads (such as SQL Server Data Tools and SQL Server Management Studio) are Windows-centric, with no alternatives or guidance for Linux users. No PowerShell-specific examples are present, but the overall pattern is Windows-first and Windows-only for critical features.
Recommendations
- Add explicit information about Linux support status for Self-hosted IR. If not supported, clarify roadmap or alternatives.
- If Linux support is available or planned, provide installation and configuration instructions for Linux environments.
- Include references to cross-platform tools or alternatives for managing SSIS packages, or clarify if only Windows tools are supported.
- Wherever possible, provide parity in examples and instructions for both Windows and Linux environments.
- If certain features are Windows-only, clearly state this early in the documentation and suggest workarounds or alternatives for Linux users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/compute-linked-services.md
.../main/articles/data-factory/compute-linked-services.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation demonstrates a moderate Windows bias. While many examples and configurations are cross-platform (e.g., JSON for Linux-based clusters), there is a notable preference for Windows tools and patterns, such as referencing PowerShell cmdlets (New-AzBatchAccount, New-AzBatchPool) and Microsoft Azure Storage Explorer for storage management. PowerShell is mentioned before portal or CLI alternatives, and there is no mention of Linux-native tools or shell commands for equivalent operations. The documentation does specify Linux as the default for HDInsight clusters, but operational guidance and tooling references are Windows-centric.
Recommendations
- Provide equivalent Azure CLI and/or Bash shell commands alongside PowerShell cmdlets for resource creation and management (e.g., for Azure Batch accounts and pools).
- Mention cross-platform or Linux-native tools for storage management (e.g., az storage blob delete, rclone, or s3cmd) in addition to Microsoft Azure Storage Explorer.
- When referencing tools or patterns, avoid listing Windows/PowerShell options first; instead, present cross-platform solutions or alternate between Windows and Linux approaches.
- Explicitly state when features or examples are cross-platform, and provide guidance for both Windows and Linux users where applicable.
- Include troubleshooting and operational instructions (such as SSH access, file deletion, or script actions) with both Windows and Linux command-line examples.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-datasets-linked-services.md
...cles/data-factory/concepts-datasets-linked-services.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by prominently featuring PowerShell as a primary automation tool, listing it before REST API and omitting Linux-native alternatives (such as Azure CLI or Bash scripting). There are no Linux-specific examples or references to cross-platform tooling, and the quickstart and creation sections prioritize Windows-centric tools and workflows.
Recommendations
- Add Azure CLI examples and quickstarts alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash scripting or shell-based automation examples for dataset creation and management.
- When listing tools or SDKs, present cross-platform options (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
- Explicitly mention that all features are available on Linux and macOS, and provide links to relevant Linux documentation.
- Ensure screenshots and UI walkthroughs do not assume a Windows environment (e.g., avoid Windows-only UI elements or terminology).
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-linked-services.md
...main/articles/data-factory/concepts-linked-services.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prominently featuring PowerShell as a primary automation/example tool, listing it before cross-platform alternatives, and omitting explicit Linux/CLI examples. The tooling and quickstart sections prioritize Windows-centric tools (PowerShell, .NET) and do not mention or provide parity for Linux-native approaches (such as Azure CLI or Bash scripting).
Recommendations
- Add explicit examples and quickstarts using Azure CLI and Bash scripts, which are cross-platform and commonly used on Linux.
- List cross-platform tools (such as REST API, Azure CLI) before or alongside Windows-specific tools like PowerShell and .NET.
- Include a section or callout for Linux/macOS users, highlighting supported tools and any differences in workflow.
- Ensure that all automation and scripting guidance includes both PowerShell and Bash/Azure CLI equivalents.
- Review and update related tutorials to provide Linux-friendly instructions and screenshots where appropriate.