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 176-200 of 1000 flagged pages
Data Factory
Copy data from Oracle Responsys (Preview)
...in/articles/data-factory/connector-oracle-responsys.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a primary method for pipeline creation and referencing Azure Resource Manager templates and REST API, but does not mention or provide examples for Linux-native tools or CLI usage. There are no Linux-specific instructions, nor are there examples using Azure CLI, which is cross-platform. The order of methods puts PowerShell before REST API and ARM templates, reinforcing a Windows-first approach. No Linux shell or command-line examples are provided.
Recommendations
- Include Azure CLI examples for pipeline and linked service creation, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention Linux compatibility and provide instructions for Linux users where relevant (e.g., installing drivers, authentication).
- Reorder the list of supported creation methods to avoid putting PowerShell first; consider listing CLI and SDKs before platform-specific tools.
- Add a section or note on using the service from Linux environments, including any prerequisites or differences.
- Provide sample commands or scripts for Linux shell environments (bash) where applicable.
Create Pull Request
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the prerequisites and troubleshooting sections. It explicitly instructs users to place SAP NetWeaver RFC SDK libraries in the %windir%\system32 folder, which is a Windows-specific location, and does not mention Linux equivalents or provide guidance for Linux-based Integration Runtime hosts. There are no examples or instructions for Linux environments, and all tooling and troubleshooting steps assume a Windows setup.
Recommendations
- Add instructions for installing SAP NetWeaver RFC SDK libraries on Linux-based Integration Runtime hosts, including typical library locations (e.g., /usr/lib, /opt/sap, etc.).
- Include troubleshooting steps for Linux environments, such as verifying library placement and permissions.
- Mention Linux compatibility in the prerequisites, and clarify any limitations or additional steps required for Linux hosts.
- Provide examples or screenshots for both Windows and Linux environments when describing setup and configuration steps.
- Avoid using Windows-specific environment variables (e.g., %windir%) without also providing Linux equivalents.
Data Factory
Troubleshoot the Azure Blob Storage connector
...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 page exhibits Windows bias by referencing Windows-specific tools (diawp.exe.config) and configuration steps, particularly in the FIPS mode troubleshooting section. There are no Linux-specific troubleshooting instructions or examples, and the guidance assumes a Windows environment for the self-hosted integration runtime. No parity is provided for Linux or cross-platform scenarios.
Recommendations
- Include troubleshooting steps for Linux environments, such as how to disable FIPS mode or equivalent on Linux VMs hosting the self-hosted integration runtime.
- Reference Linux configuration files and commands where applicable, alongside Windows examples.
- Clarify whether the self-hosted integration runtime is supported on Linux, and if so, provide platform-specific guidance.
- Ensure examples and recommendations are presented for both Windows and Linux users, or explicitly state platform limitations.
Data Factory
Copy and transform data to and from SQL Server
...lob/main/articles/data-factory/connector-sql-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows authentication and Windows-specific tools (such as SQL Server Management Studio and SQL Server Configuration Manager) in connection setup and troubleshooting sections. Windows authentication is described in detail and given equal prominence to SQL authentication, despite being less relevant for Linux environments. Troubleshooting steps and tool references are exclusively Windows-centric, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for connecting to SQL Server from Linux, nor instructions for configuring SQL Server on Linux or using Linux-native tools.
Recommendations
- Add explicit instructions and examples for connecting to SQL Server from Linux environments, including authentication options and connection string formats.
- Include troubleshooting steps and tool references for SQL Server on Linux, such as using sqlcmd, systemctl, or configuration files instead of Windows-only tools.
- Mention Linux authentication patterns (e.g., Kerberos, integrated authentication via GSSAPI) where applicable, and clarify Windows authentication limitations on Linux.
- Provide parity in examples and screenshots, showing both Windows and Linux workflows for common tasks (e.g., enabling remote connections, configuring firewalls, checking TCP/IP settings).
- Clearly indicate which features and instructions are Windows-only, and offer Linux alternatives or note their absence.
Data Factory
Troubleshoot the FTP, SFTP, and HTTP connectors
...s/data-factory/connector-troubleshoot-ftp-sftp-http.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (WinSCP) are mentioned as verification options for SFTP credentials, and third-party base64 encoding tools are recommended before Linux-native command-line solutions. While some Linux commands (openssl, ssh-keygen) are included, they are not always presented as primary options, and there is a lack of explicit Linux/POSIX shell examples for common troubleshooting tasks (e.g., base64 encoding, file verification). The documentation does not provide parity in troubleshooting steps or tool recommendations for Linux users, and Windows-centric tools are referenced without Linux alternatives.
Recommendations
- Include Linux-native command-line examples for base64 encoding (e.g., 'base64 -w 0 < keyfile') alongside or before third-party web tools.
- Mention Linux/POSIX alternatives to WinSCP, such as FileZilla, lftp, or the native 'sftp' command for credential verification.
- Ensure that troubleshooting steps reference both Windows and Linux tools and patterns, and avoid recommending Windows tools exclusively or first.
- Add explicit Linux shell commands for common operations (e.g., checking file permissions, encoding keys, verifying connectivity) to achieve parity.
- Where possible, present cross-platform solutions (e.g., Python scripts, CLI commands) before platform-specific GUI tools.
Data Factory
Troubleshoot the SAP Table, SAP Business Warehouse Open Hub, and SAP ODP connectors
...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 troubleshooting steps that exclusively use PowerShell commands (Test-NetConnection), which are only available on Windows. There are no equivalent Linux or cross-platform examples (such as using telnet, nc, or curl), and Windows tools are mentioned without reference to Linux alternatives.
Recommendations
- Add equivalent Linux command examples, such as 'nc <sap server> 3300' or 'telnet <sap server> 3300', for testing connectivity.
- Explicitly mention that the PowerShell command is for Windows and provide guidance for users on Linux or macOS.
- Consider using cross-platform tools (e.g., curl, netcat) in examples to ensure parity.
- Review other troubleshooting steps to ensure both Windows and Linux environments are covered.
Data Factory
Troubleshoot the file system connector
...les/data-factory/connector-troubleshoot-file-system.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates Windows bias by exclusively recommending PowerShell for configuring the self-hosted integration runtime (SHIR) security settings. There is no mention of Linux command-line alternatives or guidance for non-Windows environments, and Windows tooling is referenced first and exclusively.
Recommendations
- Provide equivalent Linux shell (bash) commands or instructions for configuring SHIR settings.
- Mention cross-platform compatibility and clarify if the recommended steps are Windows-only or available on Linux/macOS.
- Include examples using Linux tools (e.g., shell scripts, CLI commands) alongside PowerShell.
- Add a note or section for Linux users, outlining any differences or additional steps required.
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the FIPS troubleshooting section, where instructions and file paths are exclusively for Windows (e.g., C:\Program Files\Microsoft Integration Runtime), and configuration changes are shown only for Windows environments. There are no Linux equivalents or examples provided for troubleshooting on Linux-based Self-hosted Integration Runtime machines. The documentation assumes Windows as the default platform for installation and troubleshooting, omitting guidance for Linux users.
Recommendations
- Add explicit troubleshooting instructions for Self-hosted Integration Runtime installed on Linux, including file paths, configuration file locations, and commands.
- Provide Linux-specific examples and screenshots alongside Windows ones, especially for tasks like disabling FIPS or editing configuration files.
- Clarify platform support in each troubleshooting step, indicating whether the guidance applies to Windows, Linux, or both.
- Where relevant, mention Linux tools or commands (e.g., using nano/vim for config editing, systemctl for service restarts) in addition to Windows tools.
- Include a section or note on platform differences and how to adapt troubleshooting steps for Linux environments.
Data Factory
Troubleshoot the REST connector
...n/articles/data-factory/connector-troubleshoot-rest.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates Windows bias by referencing 'Command Prompt' as the environment for running curl, omitting mention of Linux/macOS terminals. It recommends Fiddler, a Windows-centric tool, without suggesting Linux alternatives. No Linux-specific troubleshooting examples or tool recommendations are provided.
Recommendations
- Explicitly mention that curl can be run in Linux/macOS terminals as well as Windows Command Prompt.
- Provide example curl commands for both Windows (Command Prompt/PowerShell) and Linux/macOS (bash/zsh).
- Suggest cross-platform alternatives to Fiddler, such as mitmproxy or Wireshark, for SSL troubleshooting.
- Add notes or sections addressing troubleshooting steps and tool usage on Linux and macOS platforms.
Data Factory
Troubleshoot the SharePoint Online list connector
...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. Troubleshooting steps for enabling ACS in SharePoint Online exclusively reference the SharePoint Online Management Shell (a Windows-only tool) and provide only PowerShell command examples. There are no equivalent instructions or examples for Linux or cross-platform environments, nor is there mention of alternative methods for non-Windows users.
Recommendations
- Provide alternative instructions for Linux and macOS users, such as using Azure CLI, Microsoft Graph API, or REST API calls to perform the same tenant configuration tasks.
- Include cross-platform command examples (e.g., bash, curl, or Python scripts) where possible.
- Explicitly state platform requirements and offer guidance for users who do not have access to Windows environments.
- Reference any available web-based portals or interfaces that can accomplish the same configuration without requiring Windows-only tools.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides programmatic guidance exclusively using PowerShell scripts, which are native to Windows environments. There are no examples or references to Linux-compatible tools (such as Bash, Azure CLI, or Python scripts), nor is there mention of how Linux users can achieve the same tasks. This creates a Windows-centric bias and may hinder users working in Linux or cross-platform environments.
Recommendations
- Add equivalent examples using Azure CLI, Bash, or Python scripts for Linux and macOS users.
- Explicitly mention cross-platform alternatives and clarify which tools/scripts work on which operating systems.
- Provide guidance on how to run the provided PowerShell scripts on Linux (e.g., using PowerShell Core), or offer containerized/scripted solutions that work natively on Linux.
- Ensure future documentation includes both Windows and Linux approaches side-by-side, or links to platform-specific instructions.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in the section on installing the Vertica ODBC driver, where only Windows installation steps and screenshots are provided. There are no instructions or examples for installing the ODBC driver on Linux or macOS, despite the self-hosted integration runtime being supported on those platforms. Additionally, Windows-specific tools and UI patterns (such as Start -> ODBC Data Source Administrator) are referenced without Linux equivalents.
Recommendations
- Add parallel instructions and screenshots for installing the Vertica ODBC driver on Linux (and macOS if supported), including command-line examples (e.g., using .rpm/.deb packages or tarballs).
- Mention and provide examples for verifying ODBC driver installation on Linux (e.g., using odbcinst or editing odbc.ini/odbcinst.ini files).
- When referencing Windows-specific tools or UI paths, include equivalent Linux commands or configuration file locations.
- Explicitly state platform support for the self-hosted integration runtime and clarify any OS-specific requirements or limitations.
- Ensure that all code and configuration examples are platform-agnostic or provide both Windows and Linux variants where differences exist.
Data Factory
Continuous integration and delivery pre- and post-deployment scripts
...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 page exclusively uses Azure PowerShell and PowerShell scripts for all CI/CD pre- and post-deployment examples, with no mention of Bash, Azure CLI, or Linux-native scripting alternatives. All sample code, instructions, and YAML pipeline tasks are centered around PowerShell, and the page assumes the use of PowerShell Core without discussing Linux or cross-platform execution details. There are no Linux-specific examples, nor guidance for users who may prefer Bash or Azure CLI.
Recommendations
- Add equivalent examples using Azure CLI and Bash scripts for pre- and post-deployment tasks.
- Explicitly mention cross-platform compatibility and provide instructions for running scripts on Linux agents.
- Include YAML pipeline tasks that use Bash or AzureCLI@2 instead of only AzurePowerShell@5.
- Discuss any differences or considerations when running deployment scripts on Linux vs. Windows agents.
- Reference documentation for installing and configuring Azure CLI alongside Azure PowerShell.
Data Factory
Continuous integration and delivery
...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 demonstrates a significant Windows bias, particularly through its exclusive recommendation and examples of PowerShell scripts for pre- and post-deployment tasks. There is no mention of Bash, shell scripts, or cross-platform alternatives. The guidance assumes the use of PowerShell (including PowerShell Core), and does not provide Linux-native or cross-platform script examples. This may hinder users working in Linux-based CI/CD environments or those preferring non-Windows tooling.
Recommendations
- Provide equivalent Bash or shell script examples for pre- and post-deployment tasks, or clarify how to adapt the PowerShell scripts for Linux environments.
- Explicitly state that PowerShell Core is cross-platform, and provide instructions for installing and running it on Linux and macOS, if PowerShell must be used.
- Mention and, where possible, demonstrate how to use Azure CLI or other cross-platform tools for deployment steps, in addition to or instead of PowerShell.
- Ensure that all script references and downloadable samples include both .ps1 and .sh (or similar) versions, or at least guidance for Linux users.
- Review the documentation for other implicit assumptions of a Windows environment (e.g., file paths, tool availability) and address them for Linux parity.
Data Factory
Switch activity in Azure Data Factory
.../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 file paths are given in Windows format (e.g., C:\ADF). There are no equivalent instructions or examples for Linux or cross-platform environments (such as Bash or Azure CLI). The tutorial and walkthrough links also reference Azure PowerShell specifically, reinforcing the Windows-centric approach.
Recommendations
- Provide equivalent examples using Azure CLI and Bash, which are cross-platform and widely used on Linux and macOS.
- Include Linux-style file paths (e.g., /home/user/ADF) alongside Windows paths in examples.
- Add a section or note explicitly stating that Azure Data Factory can be managed from Linux/macOS and provide links to relevant documentation.
- Ensure that tutorials and walkthroughs reference both PowerShell and Azure CLI options, giving users a choice based on their platform.
- Review and update reusable content includes to avoid Windows-only references.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by providing only PowerShell examples and walkthroughs for pipeline execution, with no mention of Linux shell equivalents (e.g., Bash, CLI). The tutorial and sample commands are Windows-centric, and there is no guidance for users on Linux or macOS platforms.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for pipeline creation and execution, which are cross-platform.
- Include Bash shell script samples for running pipelines, especially for Linux and macOS users.
- Explicitly mention platform compatibility and provide links or sections for Linux/macOS instructions where relevant.
- Ensure that tutorials and walkthroughs are available for both PowerShell and CLI, and present them side-by-side or in parallel sections.
Data Factory
Automate continuous integration
...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. All automation and scripting examples use PowerShell, with no mention of Bash, CLI, or cross-platform alternatives. The guidance assumes the use of Windows tools and patterns (e.g., .ps1 scripts, Azure PowerShell modules), and troubleshooting steps reference PowerShell scripts and logs. There are no Linux-specific instructions or examples, and Windows-centric terminology and tools are presented first and exclusively.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for deployment, trigger management, and Key Vault integration.
- Explicitly state which steps are cross-platform and which require Windows, and offer alternatives for Linux/macOS users.
- Include guidance for running CI/CD pipelines on Linux agents, including installation and usage of necessary modules or tools.
- Reference PowerShell Core as a cross-platform option, but also show how to accomplish tasks using non-PowerShell tools.
- Add troubleshooting steps and log references for Linux environments, not just .ps1 files.
- Review all sample scripts and provide Bash or Azure CLI versions alongside PowerShell.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell command examples for pipeline creation and execution, referencing Windows file paths (e.g., C:\ADF), and omitting any equivalent instructions for Linux or cross-platform environments (such as Bash, Azure CLI, or platform-neutral tooling). The tutorial and walkthrough links also focus exclusively on Azure PowerShell, reinforcing the Windows-centric approach.
Recommendations
- Add equivalent Azure CLI examples for pipeline creation, management, and execution, using Bash syntax and Linux file paths.
- Include notes or sections on how to perform these tasks on Linux/macOS, highlighting any differences in environment setup or command usage.
- Reference cross-platform tools (such as Azure CLI, REST API, or SDKs) alongside PowerShell, ensuring parity in documentation and examples.
- Avoid using Windows-specific file paths (e.g., C:\ADF) in generic examples; use platform-neutral paths or provide both Windows and Linux/macOS variants.
- Update tutorial links and walkthroughs to include cross-platform options, not just PowerShell.
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 by providing only PowerShell command examples for pipeline deployment and monitoring, referencing Windows file paths (e.g., C:\ADF), and omitting equivalent instructions for Linux or cross-platform environments (such as Bash, Azure CLI, or generic REST API usage). The use of PowerShell and Windows-centric tooling is presented as the default and only option, with no mention of alternatives for Linux or macOS users.
Recommendations
- Add equivalent examples using Azure CLI and Bash scripts for pipeline creation, deployment, and monitoring.
- Use cross-platform file path conventions or clarify that the instructions apply to Windows, and provide Linux/macOS alternatives (e.g., ~/ADF or /home/user/ADF).
- Include REST API usage examples for users who prefer language-agnostic or platform-independent approaches.
- Explicitly mention that PowerShell is one option and link to documentation for other platforms/tools.
- Review and update references to Windows-specific tooling to ensure Linux and macOS users are equally supported.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias primarily in the authentication section, where only a PowerShell snippet is provided for base64-encoding a PFX certificate file. No equivalent Linux or cross-platform command (e.g., using OpenSSL or base64 utilities) is mentioned. The use of PowerShell and reference to PFX (a Windows-centric format) further reinforces the bias. There are no Linux shell examples or alternative tools provided for certificate handling or encoding.
Recommendations
- Add Linux and cross-platform examples for base64-encoding PFX files, such as using 'openssl' and 'base64' commands.
- Mention alternative certificate formats and conversion tools available on Linux (e.g., PEM to PFX using OpenSSL).
- Where PowerShell is referenced, provide equivalent bash/zsh commands and note platform compatibility.
- Clarify that the process can be performed on both Windows and Linux, and link to relevant cross-platform documentation.
Data Factory
Deploy SSIS packages
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages, with no mention of Linux-compatible alternatives or cross-platform command-line examples. The related content also highlights Windows authentication and PowerShell provisioning before other methods, and does not provide guidance for Linux users or non-Windows environments.
Recommendations
- Include information on whether SSIS deployment and management tools (SSDT, SSMS, dtutil, AzureDTExec) are available or supported on Linux or macOS, and provide alternatives if not.
- Add examples or instructions for deploying and running SSIS packages from Linux environments, such as using Azure CLI, REST API, or Data Factory UI.
- Clarify cross-platform support for provisioning Azure-SSIS IR, and provide parity in documentation for Linux (e.g., using Azure CLI or ARM templates before or alongside PowerShell).
- Mention authentication options that work on Linux, and provide guidance for connecting to Azure SQL from non-Windows platforms.
- Explicitly state any limitations or requirements for Windows-only tools, and direct Linux users to appropriate resources or workarounds.
Data Factory
Use an Azure Resource Manager template to create an integration runtime
...ure-ssis-integration-runtime-resource-manager-template.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 by exclusively providing PowerShell commands for deploying and managing Azure-SSIS integration runtimes. There are no examples or instructions for Linux users, such as using Azure CLI, Bash, or other cross-platform tools. Windows-specific tools and patterns (PowerShell cmdlets) are mentioned first and exclusively, with no mention of Linux equivalents or alternatives.
Recommendations
- Add equivalent Azure CLI examples for deploying and managing Azure-SSIS IR, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Include Bash script examples for template deployment to demonstrate Linux compatibility.
- Explicitly mention that PowerShell examples are for Windows and provide links or instructions for Linux/macOS users.
- Review related content links to ensure Linux-friendly documentation is referenced, such as Azure CLI guides.
- Consider adding a section discussing platform compatibility and tool choice for different operating systems.
Data Factory
Create a self-hosted integration runtime
...data-factory/create-self-hosted-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All installation instructions, prerequisites, and tooling references are specific to Windows environments. Only Windows operating systems are listed as supported, and all command-line and automation examples use PowerShell or Windows batch tools. There is no mention of Linux or macOS support, nor are there any examples or guidance for non-Windows platforms. Windows-specific tools (e.g., registry edits, Windows event logs, Notepad, File Explorer, Windows Firewall, NT SERVICE accounts) are referenced throughout, and the use of Windows DPAPI for credential encryption is assumed. The documentation does not provide parity for Linux users or acknowledge cross-platform scenarios.
Recommendations
- Clearly state in the prerequisites whether Linux or macOS are supported or not. If not, explain the roadmap or rationale.
- If Linux support exists or is planned, provide equivalent installation and configuration instructions for Linux (e.g., supported distributions, package managers, service management, file locations).
- Include Linux/macOS command-line examples (e.g., Bash, systemd, Linux firewall configuration) alongside PowerShell/Windows examples.
- Reference cross-platform tools where possible, or provide alternatives for non-Windows environments.
- If Windows-only features are required (e.g., DPAPI, registry edits), explicitly call out these dependencies and suggest workarounds or alternatives for other platforms.
- Review all screenshots and UI instructions to ensure they are not exclusively Windows-centric, or provide Linux/macOS equivalents where applicable.
- Mention any limitations or differences in feature support between Windows and other platforms.
Data Factory
Create Azure integration runtime
...icles/data-factory/create-azure-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates bias towards Windows by exclusively providing Azure PowerShell examples for creating Azure Integration Runtime, without mentioning or providing equivalent CLI commands (such as Azure CLI or Bash) that are commonly used on Linux and macOS. The use of PowerShell cmdlets and lack of cross-platform command-line instructions may hinder Linux users from easily following the steps.
Recommendations
- Add Azure CLI examples for creating and managing Azure Integration Runtime, alongside PowerShell examples.
- Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide sample Bash commands.
- Include a table or section comparing PowerShell and CLI approaches, highlighting cross-platform compatibility.
- Ensure that all command-line instructions are available for both Windows and Linux environments to improve parity.
Data Factory
Create an Azure-SSIS integration runtime via Azure portal
...actory/create-azure-ssis-integration-runtime-portal.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns, such as SSMS, UNC paths, and PowerShell, without offering equivalent Linux alternatives or examples. Windows authentication and file system conventions are mentioned exclusively, and the only command-line example referenced is PowerShell. There is no mention of Linux-compatible tools, authentication methods, or file system paths, and no Linux-specific guidance is provided.
Recommendations
- Include Linux-compatible command-line examples, such as using Azure CLI or Bash scripts, alongside or before PowerShell examples.
- Mention Linux-compatible tools for managing SSIS packages, such as Azure Data Studio or cross-platform alternatives to SSMS.
- Provide guidance on using Linux file system paths and authentication methods, and clarify how Azure-SSIS IR can be managed from Linux environments.
- Add explicit instructions or notes for users working from Linux or macOS, including any limitations or required workarounds.
- Ensure that references to file system access (e.g., UNC paths) are supplemented with SMB/CIFS mount instructions for Linux, or alternatives using Azure Files.
- Balance references to Windows authentication with information about supported authentication methods on non-Windows platforms.