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 51-75 of 319 flagged pages
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-microsoft-access.md
...in/articles/data-factory/connector-microsoft-access.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 by exclusively referencing the Microsoft Access ODBC driver (which is only available on Windows), providing example connection strings with Windows file paths (e.g., C:\mydatabase.accdb), and omitting any mention of Linux or cross-platform alternatives. There are no instructions or examples for Linux users, nor is there guidance on running the Integration Runtime or accessing Access databases from non-Windows platforms.
Recommendations
- Explicitly state that the Microsoft Access ODBC driver is only available on Windows and clarify platform limitations.
- Provide guidance or alternatives for Linux users, such as using third-party ODBC drivers (if any exist) or containerized Windows environments.
- Include example connection strings and file paths for both Windows and Linux (if supported), or clearly indicate if Linux is not supported.
- Add a section discussing cross-platform considerations and any workarounds for non-Windows environments.
- If Linux is not supported, suggest alternative approaches for Linux users, such as converting Access databases to supported formats.
Create Pull Request
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-hive.md
...docs/blob/main/articles/data-factory/connector-hive.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows support and tools first and exclusively, such as only mentioning Windows versions for the self-hosted integration runtime and not providing Linux equivalents or examples. There are no Linux-specific instructions, examples, or troubleshooting steps, and the documentation does not clarify Linux compatibility for the self-hosted integration runtime or connector usage.
Recommendations
- Explicitly state Linux support and provide a list of supported Linux distributions for the self-hosted integration runtime, if applicable.
- Add Linux-specific installation and configuration instructions for the self-hosted integration runtime, including any prerequisites or differences from Windows.
- Include Linux-based examples or screenshots where relevant, or clarify if the UI/process is identical.
- Mention any limitations or known issues when using Linux as the host OS for integration runtime.
- Ensure that references to Windows tools or patterns are balanced with Linux equivalents, or clarify if features are Windows-only.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-http.md
...docs/blob/main/articles/data-factory/connector-http.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page exhibits Windows bias in several ways. Windows authentication is listed as a built-in option alongside Basic, Digest, and ClientCertificate, with no mention of Linux equivalents (such as Kerberos or NTLM via Linux tools). The only tool explicitly recommended for testing HTTP requests is PowerShell's Invoke-RestMethod, with no mention of Linux-native tools like curl or wget. Instructions for certificate management and permissions are entirely based on Windows tools (MMC, cert store, DIAHostService), with no guidance for Linux certificate stores or service accounts. These patterns prioritize Windows tooling and workflows, and omit Linux alternatives.
Recommendations
- Include Linux-native tools (e.g., curl, wget) alongside PowerShell for HTTP request testing.
- Add guidance for managing certificates and permissions on Linux self-hosted integration runtime hosts, such as using OpenSSL and Linux certificate stores.
- Clarify authentication options for Linux hosts, including how to use Basic, Digest, or client certificates in a Linux environment.
- Where Windows-specific instructions are given (e.g., MMC, DIAHostService), provide Linux equivalents or note platform differences.
- Explicitly state platform support and limitations for authentication types (e.g., Windows authentication only available on Windows hosts).
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-postgresql.md
...lob/main/articles/data-factory/connector-postgresql.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias in several areas. The only explicit instructions for configuring SSL certificates for ODBC connections reference Windows-specific paths (e.g., C:\Windows\ServiceProfiles\DIAHostService\AppData\Roaming\postgresql\root.crt) and tools, with no mention of Linux equivalents. There are no examples or guidance for Linux-based Self-hosted Integration Runtime (SHIR) deployments, and the documentation implicitly assumes a Windows environment for advanced configuration steps. Additionally, Windows is mentioned first and exclusively in relevant sections.
Recommendations
- Provide equivalent instructions and file paths for configuring SSL certificates on Linux-based SHIR hosts (e.g., /var/opt/ or /home/ directories).
- Explicitly state support for Linux-based SHIR and include examples or notes for Linux users wherever Windows-specific instructions are given.
- Avoid referencing only Windows tools or paths; when necessary, present Linux and Windows instructions side by side.
- Audit the documentation for other implicit Windows assumptions and ensure Linux parity in all advanced configuration and troubleshooting sections.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-netezza.md
...s/blob/main/articles/data-factory/connector-netezza.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows versions as supported platforms for the self-hosted integration runtime, omitting explicit mention of Linux support or instructions. There are no Linux-specific examples or guidance for installing the Netezza ODBC driver or running the integration runtime on Linux, and all platform-specific references are to Windows. Additionally, the only linked reference for prerequisites points to a page about Windows requirements, and there are no Linux or cross-platform command-line examples (e.g., Bash, shell scripts) or troubleshooting notes.
Recommendations
- Explicitly state whether the self-hosted integration runtime and Netezza ODBC driver are supported on Linux, and if so, provide installation instructions for Linux (e.g., Ubuntu, CentOS).
- Add Linux-specific examples for installing the IBM Netezza ODBC driver, including package dependencies and environment variable configuration.
- If the integration runtime is Windows-only, clarify this early in the prerequisites section to set expectations for Linux users.
- Wherever platform-specific instructions are given (such as for driver installation), provide both Windows and Linux variants, or link to official cross-platform guides.
- Include troubleshooting tips or common issues for Linux environments if supported.
- Review referenced prerequisite articles to ensure Linux parity or add Linux sections where missing.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-odata.md
...ocs/blob/main/articles/data-factory/connector-odata.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation displays a Windows bias primarily through the exclusive mention and example of Windows authentication (including domain\user syntax) and the lack of Linux-specific authentication examples or discussion. Windows authentication is listed as a main supported authentication type, and an example is provided, but there is no mention of Linux-integrated authentication methods (such as Kerberos on Linux) or how to configure equivalent authentication from non-Windows environments. Additionally, the use of Windows-centric tools and patterns (e.g., domain\user) is present, and Linux alternatives are not discussed.
Recommendations
- Add examples and guidance for configuring OData authentication from Linux environments, including how to use Kerberos or other common Linux authentication mechanisms if supported.
- Clarify whether Windows authentication is supported only from Windows-based integration runtimes, and if so, explicitly state this limitation.
- Provide parity by including Linux/Unix authentication scenarios or explicitly stating their (un)support.
- If only Windows authentication is supported, suggest alternative authentication methods (e.g., Basic, OAuth, API Key) for Linux users, and provide examples.
- Review and update the documentation to avoid Windows-centric language and patterns where possible, or provide equivalent Linux instructions.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sap-hana.md
.../blob/main/articles/data-factory/connector-sap-hana.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias in several ways: it only references the SAP HANA ODBC driver for Windows in the prerequisites, does not mention or provide instructions for Linux-based Integration Runtime hosts, and all authentication and setup examples are Windows-centric (e.g., Windows authentication, user@domain.com). There are no Linux-specific examples or guidance, and Windows tools and terminology are presented exclusively and/or first.
Recommendations
- Add instructions and download links for SAP HANA ODBC drivers for Linux, and clarify that Self-hosted Integration Runtime can be installed on Linux (if supported).
- Provide Linux-specific examples for setting up the ODBC driver, including environment variables, installation commands, and configuration file locations.
- Include authentication examples relevant to Linux environments (e.g., basic authentication, Kerberos if supported), and clarify any differences.
- Avoid using 'Windows authentication' as the only advanced authentication example; mention alternatives or note platform limitations.
- When referencing the SAP HANA client, specify both Windows and Linux options, and provide parity in setup steps.
- Explicitly state platform support and any limitations for both Windows and Linux in the prerequisites section.
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 Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell and reference Windows file paths (e.g., C:\ADF). There are no equivalent instructions or examples for Linux or cross-platform CLI tools (such as Azure CLI or Bash). The tutorial and walkthrough links also focus on Azure PowerShell, reinforcing the Windows-centric approach.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, including pipeline creation, linked service setup, dataset creation, and pipeline execution.
- Include Linux/macOS file path examples (e.g., /home/user/ADF) alongside Windows paths.
- Explicitly mention cross-platform compatibility and provide instructions for running the workflow on Linux/macOS.
- Link to tutorials or quickstarts that use Azure CLI or REST API, not just PowerShell.
- Add a note clarifying that the steps can be performed on non-Windows platforms, and highlight any platform-specific considerations.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-square.md
...cs/blob/main/articles/data-factory/connector-square.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by referencing Windows support and prerequisites for the Square connector, specifically in the context of the self-hosted integration runtime. There is no mention of Linux support, Linux prerequisites, or examples for Linux-based self-hosted integration runtime deployments. All instructions and compatibility statements focus on Windows, and there are no Linux-specific tools, commands, or screenshots provided.
Recommendations
- Explicitly state whether Linux-based self-hosted integration runtime is supported for the Square connector. If supported, provide Linux-specific prerequisites and instructions.
- Include examples or references for deploying and configuring the self-hosted integration runtime on Linux, alongside the existing Windows information.
- If Linux is not supported, clearly mention this limitation to avoid confusion.
- Ensure that any references to operating system requirements are presented in a cross-platform manner, or provide parallel guidance for both Windows and Linux environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sybase.md
...cs/blob/main/articles/data-factory/connector-sybase.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias by mentioning Windows authentication as a primary supported method, referencing Windows-specific data providers, and omitting any discussion of Linux equivalents or examples. There are no instructions or examples for installing the Sybase provider on Linux, nor any mention of Linux authentication or integration runtime setup. The documentation implicitly assumes a Windows environment for self-hosted integration runtime and Sybase connectivity.
Recommendations
- Add explicit instructions and examples for installing the Sybase data provider on Linux-based integration runtime hosts.
- Discuss Linux authentication options, such as Kerberos or other supported mechanisms, if available.
- Provide parity in examples by including Linux command-line or configuration steps alongside Windows-focused instructions.
- Clarify whether the self-hosted integration runtime and Sybase connector are supported on Linux, and if so, document any platform-specific requirements or limitations.
- Mention any differences in setup or troubleshooting for Linux environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-teradata.md
.../blob/main/articles/data-factory/connector-teradata.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: it references Windows-specific dependencies (such as .NET Data Provider and Visual C++ Redistributable), authentication types prioritize 'Windows' alongside 'Basic' and 'LDAP', and examples for authentication and driver installation are Windows-centric. There are no explicit Linux equivalents, instructions, or examples for installing dependencies or configuring the integration runtime on Linux systems. The documentation does not mention Linux support or provide parity for Linux-based self-hosted integration runtime scenarios.
Recommendations
- Add explicit instructions and examples for installing required Teradata drivers and dependencies on Linux systems, including supported distributions.
- Clarify whether the self-hosted integration runtime and Teradata connector are supported on Linux, and provide guidance if so.
- Include Linux authentication scenarios (e.g., Kerberos, LDAP on Linux) and configuration examples.
- Avoid using 'Windows authentication' as a default or primary example; instead, present 'Basic' or 'LDAP' first, and clearly indicate platform-specific options.
- Mention Linux equivalents for required system libraries (e.g., .NET Core/Mono, relevant C++ libraries) and provide installation commands.
- Add troubleshooting tips for Linux environments, if supported.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-azure-blob-storage.md
...a-factory/connector-troubleshoot-azure-blob-storage.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation shows Windows bias by referencing Windows-specific tools (e.g., diawp.exe.config) and policies (FIPS mode on Windows VMs) without mentioning Linux equivalents or providing guidance for Linux users. There are no Linux-specific troubleshooting steps or examples, and the only OS-specific advice is for Windows, which is presented first and exclusively.
Recommendations
- Add troubleshooting steps for Linux environments, such as how to handle FIPS-related issues on Linux-based self-hosted integration runtimes.
- Include Linux-specific file paths and configuration examples alongside Windows ones (e.g., where to find and edit configuration files on Linux).
- Explicitly state whether certain errors or solutions are Windows-only, and provide Linux alternatives if available.
- Ensure parity in examples and recommendations by including both Windows and Linux scenarios where applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-sap.md
...in/articles/data-factory/connector-troubleshoot-sap.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell (Windows-specific) example for network troubleshooting (Test-NetConnection), with no equivalent Linux or cross-platform commands. This suggests a bias toward Windows environments and tools, potentially excluding Linux users.
Recommendations
- Add equivalent Linux troubleshooting commands, such as using 'nc', 'telnet', or 'curl' to test connectivity to the SAP server.
- Present both Windows and Linux examples side by side to ensure parity.
- Explicitly mention that the troubleshooting steps apply to both Windows and Linux integration runtime hosts, if applicable.
- Consider referencing cross-platform tools or commands where possible.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-hive.md
...n/articles/data-factory/connector-troubleshoot-hive.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides troubleshooting steps that reference Windows-specific paths (e.g., C:\Program Files\MIT\Kerberos\bin) and environment variable configuration, without mentioning Linux equivalents. There are no Linux-specific instructions or examples, and the guidance implicitly assumes a Windows environment.
Recommendations
- Include Linux-specific paths for the krb5.conf file (e.g., /etc/krb5.conf) and describe where to find or place Kerberos configuration files on Linux systems.
- Provide instructions for setting environment variables (KRB5_CONFIG, KRB5CCNAME) on Linux (e.g., using export in bash) alongside the Windows system variable method.
- Mention how to restart relevant services or processes on Linux, not just 'restart the VM and SHIR from the machine'.
- Wherever file paths or commands are given, present both Windows and Linux versions in parallel for parity.
- Explicitly state that the instructions apply to both Windows and Linux, and clarify any platform-specific differences.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-rest.md
...n/articles/data-factory/connector-troubleshoot-rest.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing 'Command Prompt' as the default terminal for running curl, and by recommending Fiddler (a Windows-centric tool) for SSL troubleshooting. There are no explicit Linux or macOS examples, nor are alternative Linux tools mentioned. The guidance assumes a Windows environment and omits parity for Linux users.
Recommendations
- Provide explicit Linux (and optionally macOS) examples for running curl, e.g., 'open a terminal on Linux/macOS'.
- Mention cross-platform alternatives to Fiddler, such as mitmproxy or Wireshark, for SSL troubleshooting.
- Avoid assuming the use of 'Command Prompt'; instead, use neutral language like 'open a terminal window'.
- Where possible, add notes about any platform-specific differences in curl usage or troubleshooting steps.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-sharepoint-online-list.md
...ctory/connector-troubleshoot-sharepoint-online-list.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 exclusively recommending the SharePoint Online Management Shell (a Windows-only tool) and providing only PowerShell command examples for troubleshooting. There are no equivalent instructions or examples for Linux or macOS users, nor any mention of cross-platform alternatives. The troubleshooting steps assume the reader is using Windows, omitting guidance for non-Windows environments.
Recommendations
- Provide equivalent troubleshooting steps using cross-platform tools, such as Azure CLI or PowerShell Core, which are available on Linux and macOS.
- Include examples for Linux and macOS users, specifying any prerequisites or differences in authentication and command syntax.
- Mention and link to cross-platform alternatives where Windows-only tools are referenced.
- Clearly state platform requirements and offer guidance for users who do not have access to Windows environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-upgrade-guidance.md
...in/articles/data-factory/connector-upgrade-guidance.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only PowerShell script examples for programmatically finding impacted objects, with no mention of Linux-compatible alternatives such as Azure CLI, Bash, or Python scripts. This creates a bias toward Windows users and tools, potentially excluding Linux or cross-platform users from easily following the guidance.
Recommendations
- Add equivalent examples using Azure CLI and/or Bash scripts for Linux and cross-platform users.
- Mention that PowerShell Core is available on Linux, if the provided scripts are compatible, and provide instructions for installing and running PowerShell on Linux.
- Provide Python script examples, as Python is widely used and cross-platform.
- Explicitly state that the guidance applies to all platforms, and ensure that tool recommendations are inclusive of both Windows and Linux environments.
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 demonstrates a Windows bias by referencing 'Windows versions' as a prerequisite for the self-hosted integration runtime, without mentioning Linux support or alternatives. There are no Linux-specific instructions, examples, or clarifications about cross-platform compatibility for the integration runtime. The only command-line example given (for generating a private key) uses 'openssl', which is cross-platform, but the context does not clarify Linux support. The documentation does not provide parity for Linux users in terms of setup, troubleshooting, or platform-specific considerations.
Recommendations
- Explicitly state whether the self-hosted integration runtime is supported on Linux, and if so, provide installation and configuration instructions for Linux alongside Windows.
- If only Windows is supported, clearly mention this limitation early in the documentation.
- Provide Linux-specific examples or notes where relevant (e.g., for openssl commands, file paths, environment variables).
- Include troubleshooting tips or known issues for Linux environments if supported.
- Ensure that references to 'Windows versions' are balanced with equivalent Linux information or a clear statement of platform support.
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 (and Power Query/Power BI) for extracting the index of a table from an HTML page. No Linux or cross-platform alternatives are mentioned, and all step-by-step instructions and screenshots are for Windows tools. There are no examples or guidance for users on Linux or macOS platforms.
Recommendations
- Add instructions for extracting table indexes using cross-platform or Linux tools, such as Python scripts (e.g., using BeautifulSoup or pandas), command-line utilities (e.g., curl + pup/xq), or browser developer tools.
- Include at least one example using a Linux or macOS environment to demonstrate parity.
- Mention open-source, platform-independent alternatives before or alongside Windows-specific tools.
- Clarify that the current method using Excel is only one option and not a requirement, and encourage community contributions for other platforms.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-vertica.md
...s/blob/main/articles/data-factory/connector-vertica.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias, particularly in the 'Install Vertica ODBC driver' section, where only Windows installation steps and screenshots are provided. There are no instructions or examples for installing the ODBC driver on Linux or macOS, nor are cross-platform considerations mentioned. The use of Windows-specific tools (e.g., ODBC Data Source Administrator) is referenced without Linux equivalents.
Recommendations
- Add installation instructions and screenshots for the Vertica ODBC driver on Linux (and macOS, if supported), including common distributions (e.g., Ubuntu, RHEL).
- Mention and provide examples for Linux tools and commands (e.g., using 'odbcinst' or editing odbc.ini/odbcinst.ini files) alongside Windows tools.
- Clearly indicate platform-specific steps and provide parity in documentation structure and detail.
- Where screenshots are used, provide alternatives or notes for Linux users.
- Explicitly state supported platforms for the self-hosted integration runtime and Vertica ODBC driver, and link to relevant platform-specific resources.
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 Tools
Missing Linux Example
Windows First
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 instructions for Linux or cross-platform CLI tools such as Azure CLI, Bash, or Python SDK. The only automation walkthrough is for Azure PowerShell, and the page does not mention or link to Linux/macOS alternatives. The 'devx-track-azurepowershell' custom tag further reinforces the Windows/PowerShell focus.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, including pipeline deployment and monitoring.
- Provide Bash shell script examples for Linux/macOS users, using platform-agnostic file paths and commands.
- Mention and link to cross-platform tools (e.g., Azure CLI, REST API, Python SDK) in the introductory and example sections.
- Use neutral file paths (e.g., ./ADF/) or show both Windows and Linux path formats in examples.
- Include a note clarifying that all features are available on Linux/macOS and how to use them outside of PowerShell.
- Balance PowerShell and CLI examples, or provide tabs/switchers for users to select their preferred platform.
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 Windows bias by exclusively providing PowerShell examples and instructions, referencing Windows-centric tools and workflows (such as .ps1 scripts and Azure PowerShell modules), and omitting equivalent Linux/bash examples. There is no mention of cross-platform alternatives or guidance for users operating in Linux environments, and Windows/PowerShell approaches are presented as the default or only option.
Recommendations
- Provide equivalent bash or Azure CLI examples for all PowerShell scripts and tasks, especially for stopping and starting triggers.
- Explicitly mention that Azure Pipelines agents can run on Linux and MacOS, and provide instructions for those platforms.
- Reference cross-platform tools (e.g., Azure CLI) alongside PowerShell, and clarify when a task or script is Windows-specific.
- Add notes or sections for Linux users, including how to install necessary modules and run deployment scripts.
- Ensure that all code samples and automation steps have Linux-compatible alternatives, and test them for parity.
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 Azure PowerShell for all examples and instructions, with no mention of Bash, Azure CLI, or Linux shell scripting alternatives. All code samples, parameters, and YAML pipeline tasks are PowerShell-centric, and there is no guidance for users on Linux or macOS environments. The documentation assumes familiarity with Windows/PowerShell tools and patterns, which may hinder Linux users.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for pre- and post-deployment tasks.
- Include instructions for installing and configuring Azure CLI on Linux/macOS.
- Show YAML pipeline tasks using the AzureCLI@2 task and Bash scripts, in addition to AzurePowerShell.
- Explicitly mention cross-platform compatibility and note any differences or limitations.
- Add a section or notes for users running pipelines on Linux agents, including script compatibility considerations.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-linked-templates.md
...ry/continuous-integration-delivery-linked-templates.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric tools (such as VSTS, now Azure DevOps, which is historically Windows-focused), and omitting explicit Linux or cross-platform alternatives. There are no examples or instructions for Linux users, such as using Azure CLI, Bash, or cross-platform deployment scripts. The guidance assumes familiarity with Windows workflows and does not mention Linux-specific considerations or tooling.
Recommendations
- Add explicit examples for Linux environments, such as using Azure CLI or Bash scripts for uploading templates and managing SAS tokens.
- Mention cross-platform tools (e.g., Azure DevOps Pipelines, GitHub Actions) and provide parity in instructions for both Windows and Linux users.
- Include references to Linux-compatible storage upload methods (e.g., az storage blob upload) and how to generate SAS tokens using CLI.
- Clarify that the process is platform-agnostic where possible, and highlight any platform-specific steps or caveats.
- Provide sample scripts for both PowerShell and Bash to cover pre- and post-deployment tasks.
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 demonstrates a Windows bias by exclusively recommending PowerShell scripts for pre- and post-deployment tasks, referencing only PowerShell Core and not mentioning Bash or other Linux-compatible scripting alternatives. There are no Linux shell or cross-platform script examples, and the guidance assumes the use of Windows-centric tools and patterns, such as PowerShell modules, without providing Linux equivalents or parity.
Recommendations
- Provide equivalent Bash or shell script examples for pre- and post-deployment tasks, or explicitly mention how to adapt the PowerShell scripts for Linux environments.
- Clarify that PowerShell Core is cross-platform, but also offer native Linux shell alternatives for users who prefer Bash or other scripting languages.
- Mention and document how to run deployment automation from Linux-based agents in Azure Pipelines, including any prerequisites or differences.
- List both Windows and Linux approaches side-by-side where scripts or automation are required, ensuring Linux users are not left out.
- Review all referenced scripts and tools for Windows-specific dependencies and provide guidance or alternatives for Linux users.