Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1051-1075 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/jetpack.md
...s/azure-docs/blob/main//articles/cyclecloud/jetpack.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias: Windows paths and behaviors are often mentioned before Linux equivalents, and some features are described as Windows-specific or unsupported on Windows, but there is a lack of explicit Linux-specific examples or details. While Linux is mentioned, the documentation does not provide parity in examples or highlight Linux-specific usage patterns, especially for commands or features that differ between platforms.
Recommendations
- Provide Linux-specific examples and command outputs where behaviors differ, especially for features not supported on Windows (e.g., 'jetpack run_on_shutdown').
- When listing file paths or installation directories, alternate the order or present Linux first to balance perception.
- Include explicit notes or examples for Linux system integration (e.g., systemd service management, udev rules usage).
- Clarify any differences in command behavior or output between Windows and Linux, and provide guidance for both platforms.
- Where possible, provide shell command examples for Linux (e.g., using bash or systemctl), not just generic console blocks.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/overview-ccws.md
...e-docs/blob/main//articles/cyclecloud/overview-ccws.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a subtle Windows bias by referencing Visual Studio Code as a primary access tool alongside SSH, without mentioning Linux-native alternatives or workflows. There are no explicit Linux command-line examples, and the documentation does not provide parity in tooling or instructions for Linux users. The Azure CLI is mentioned, but no OS-specific guidance or examples are given, and Windows-centric tools (e.g., Visual Studio Code) are mentioned before or instead of Linux equivalents.
Recommendations
- Provide explicit Linux command-line examples for accessing and managing the Slurm cluster, such as using native SSH clients and Linux text editors (e.g., Vim, Nano) for job submission.
- Mention Linux-native tools and workflows alongside or before Windows tools like Visual Studio Code, or clarify that VS Code is cross-platform.
- Include instructions or references for both Windows and Linux users when describing how to connect to the cluster, submit jobs, or manage resources.
- Add a section or note highlighting that all features and access methods are available on Linux, and provide links to Linux-specific documentation where appropriate.
- Ensure that any screenshots or walkthroughs show both Windows and Linux environments, or use neutral, cross-platform examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/release-notes/8-5-0.md
.../blob/main//articles/cyclecloud/release-notes/8-5-0.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The release notes highlight Windows support (Windows Server 2019/2022, HPC Pack 2019) as a new feature, explicitly naming Windows versions and tools before mentioning Linux equivalents. There is no mention of Linux distributions in the same section, and no Linux-specific tools are called out, despite later mentioning Ubuntu 22 support for Slurm. No Linux command-line or usage examples are provided.
Recommendations
- When listing supported operating systems, mention Linux distributions (e.g., Ubuntu, CentOS, RHEL) alongside Windows versions, and do so in parallel structure.
- Highlight Linux-specific features or improvements (such as new supported distributions or tools) in the same section as Windows features.
- Provide parity in examples and tool mentions, e.g., if HPC Pack is mentioned for Windows, mention OpenHPC or other Linux HPC solutions if supported.
- Include Linux command-line examples or references where relevant, especially for new features or installation instructions.
- Ensure that Linux and Windows features are presented with equal prominence and detail.
Azure Docs
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 only .NET/NUnit with Visual Studio and PowerShell are mentioned as tools for automated testing and CI/CD scripting. There are no examples or explicit mentions of Linux-native tools, shell scripting, or cross-platform alternatives for these tasks. The documentation assumes familiarity with Windows-centric development environments and does not provide parity for Linux users.
Recommendations
- Include examples of using Linux-native tools for automated testing, such as running tests with Python (pytest, unittest), Bash scripts, or cross-platform test runners.
- Mention and provide examples of using Azure CLI (az) in Bash or other shells, not just PowerShell, for CI/CD and deployment automation.
- Reference cross-platform editors and IDEs (e.g., VS Code) in addition to Visual Studio, and clarify that NUnit and other .NET tools can be run on Linux via .NET Core.
- Add explicit Linux/macOS command-line examples for common tasks (e.g., using Bash scripts for deployment, running az CLI commands in Linux shells).
- Ensure that any references to scripting or automation (such as 'run TEST pipelines with PowerShell or AZ CLI') include both Windows and Linux shell syntax where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/author-global-parameters.md
...ain//articles/data-factory/author-global-parameters.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page references deploying global parameters via a PowerShell script as the only example of scripting automation for CI/CD. No equivalent Bash, Azure CLI, or cross-platform scripting examples are provided. The documentation implicitly assumes the use of Windows tooling for automation, omitting Linux-native or cross-platform alternatives.
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 PowerShell scripting is retained, and provide instructions for both Windows PowerShell and PowerShell Core.
- Wherever PowerShell is referenced, add a parallel example using Azure CLI, which is natively cross-platform.
- Audit for any UI screenshots or instructions that are Windows-specific and clarify if the experience is identical on other operating systems.
Azure Docs
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 demonstrates a Windows bias by referencing only PowerShell scripts (e.g., setupdnsserver.ps1) and not providing equivalent Linux/bash examples or mentioning cross-platform alternatives. The custom setup instructions and downloadable scripts are Windows-specific, and there is no guidance for users on Linux or macOS platforms. Additionally, the related content highlights Azure PowerShell usage without mentioning Azure CLI or other non-Windows tooling.
Recommendations
- Provide equivalent bash or shell script examples alongside PowerShell scripts for custom setup tasks.
- Offer downloadable setup scripts in both .ps1 (PowerShell) and .sh (bash) formats.
- Include instructions for configuring custom DNS and other features using Azure CLI, not just PowerShell.
- In related content, add links to documentation for performing tasks via Azure CLI or ARM templates, not just Azure PowerShell.
- Explicitly mention cross-platform compatibility and note any steps that are Windows-only, offering alternatives where possible.
Azure Docs
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 First
Missing Linux Example
Windows Tools
Summary
The documentation page describes integration runtime options in Azure Data Factory but implicitly assumes a Windows-centric environment for self-hosted integration runtimes. There are references to on-premises machines, SQL Server, and certificates, but no mention of Linux support, Linux installation, or examples for Linux-based deployments. Linked articles and tooling (such as the diagnostic tool and PowerShell-based instructions) further reinforce a Windows-first perspective. There are no explicit Linux instructions, examples, or parity in tooling references.
Recommendations
- Explicitly mention that self-hosted integration runtime can be installed on both Windows and Linux (if supported), and provide guidance for both platforms.
- Include Linux-specific installation and configuration examples alongside or before Windows/PowerShell examples.
- Reference Linux-compatible tools and commands (e.g., Bash scripts, systemd services) where appropriate.
- Ensure that linked articles (such as those for creating shared runtimes or using diagnostic tools) include Linux instructions or alternatives.
- Clarify any platform-specific limitations or differences in features, maintenance, or monitoring.
- Add examples of using Linux-based on-premises data sources and integration runtime nodes.
Azure Docs
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 exclusively describes components and features available on Azure-SSIS Integration Runtime, which is explicitly stated to run on Windows Server 2019 and .NET Framework 4.7.2. All listed drivers, providers, and tasks are Windows-centric, with no mention of Linux support, equivalents, or examples. There is no guidance for Linux users or references to cross-platform alternatives.
Recommendations
- Clearly state in the introduction that Azure-SSIS IR is currently only available on Windows, and that Linux is not supported, to set expectations for cross-platform users.
- If any Linux or cross-platform options exist (e.g., Data Flow in Azure Data Factory, Azure Data Factory Mapping Data Flows, or third-party SSIS alternatives for Linux), provide links or references to those.
- Where possible, mention if/when Linux support is planned, or provide a roadmap or workaround for Linux users.
- For each component or feature, note if there are equivalent tools or approaches available on Linux, even if outside of SSIS IR.
- Add a comparison table or FAQ section addressing platform support and alternatives for Linux users.
Azure Docs
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 demonstrates a bias towards Windows environments by referencing PowerShell and Windows-centric tools (such as Azure 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 the use of Windows-based patterns and tools for automation and scripting. This may hinder Linux users or those working in cross-platform CI/CD environments.
Recommendations
- Provide equivalent bash or Azure CLI examples alongside PowerShell commands, especially for tasks like changing integration runtime or managing ARM templates.
- Mention cross-platform test frameworks (e.g., pytest for Python, xUnit for .NET Core, or other language-agnostic tools) in addition to Nunit.
- Explicitly state when a method or tool is cross-platform, and provide guidance for both Windows and Linux users where relevant.
- Include examples or references for running CI/CD pipelines and automation scripts on Linux agents, not just Windows agents.
- Ensure that all automation and scripting recommendations are accessible and documented for both Windows and Linux environments.
Azure Docs
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 provides only PowerShell script examples for configuring UDRs and references Windows-specific tools and firewall rules (e.g., Windows firewall). There are no CLI, Bash, or Linux-native examples or instructions, and the only automation example is in PowerShell. The documentation assumes the use of Windows-based management tools, which may disadvantage users on Linux or macOS platforms.
Recommendations
- Provide equivalent Azure CLI (az) and Bash script examples alongside PowerShell scripts for all automation and configuration tasks.
- Mention cross-platform tools (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
- Clarify that all configuration steps can be performed from Linux/macOS as well as Windows, and provide links or references to relevant cross-platform documentation.
- When discussing firewall rules, avoid referencing only Windows firewall; mention that similar rules may need to be set on Linux firewalls (e.g., iptables, firewalld) if applicable.
- Add a section or note explicitly addressing Linux/macOS users, summarizing which steps are platform-agnostic and which require adaptation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/concepts-pipelines-activities.md
...articles/data-factory/concepts-pipelines-activities.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a Windows/Powershell bias primarily through its references and walkthroughs. The 'Related content' and sample pipeline walkthroughs consistently point to guides that use Powershell, which is most commonly associated with Windows environments. There are no explicit Linux, Bash, or cross-platform CLI examples or walkthroughs provided. This can make it less approachable for Linux users or those preferring cross-platform tooling.
Recommendations
- Provide equivalent walkthroughs and quickstarts using Azure CLI and/or Bash scripts alongside Powershell examples.
- Ensure that links in 'Related content' include Linux/Bash/CLI-based tutorials, not just Powershell.
- Explicitly mention that pipelines and activities can be managed from Linux/macOS environments, and provide examples.
- Where sample JSON or code is shown, include notes or links on how to deploy/run these from both Windows (Powershell) and Linux (Bash/CLI).
- Audit all referenced tutorials and ensure Linux parity in step-by-step guides.
Azure Docs
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 Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments. All examples and instructions assume the use of Windows-only tools such as SQL Server Management Studio (SSMS), dtutil, cmdkey, and net use. Command-line examples are given in Windows batch syntax, and there is no mention of Linux or cross-platform alternatives. The documentation does not address how to perform these tasks from Linux or macOS, nor does it mention whether the tools are available or supported on those platforms.
Recommendations
- Provide equivalent instructions and examples for Linux environments, including how to connect to Azure Files (e.g., using smbclient or mount.cifs) and how to use dtutil if available, or alternatives if not.
- Clarify whether SSMS and dtutil are available or supported on Linux (e.g., via Azure Data Studio, Docker, or Wine), and provide guidance for non-Windows users.
- Include PowerShell Core (cross-platform) or Azure CLI examples where possible, instead of only Windows batch commands.
- Explicitly state any platform limitations and suggest workarounds or alternatives for Linux/macOS users.
- Consider referencing Azure Data Studio or other cross-platform tools for package management, if supported.
Azure Docs
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 bias toward Windows environments by prominently featuring PowerShell as a primary automation tool, listing it before cross-platform or Linux-native alternatives, and omitting explicit Linux/Unix shell or CLI examples. The quickstart and tooling sections prioritize Windows-centric tools (PowerShell, .NET), with no mention of Bash, Azure CLI, or Linux-specific workflows, which may hinder discoverability and usability for Linux users.
Recommendations
- Add equivalent Linux/Bash shell examples alongside PowerShell in quickstart and tooling sections.
- Mention and provide examples using Azure CLI (az), which is cross-platform, for dataset creation and management.
- Ensure that REST API examples include curl or httpie commands, not just .NET or PowerShell.
- Reorder tool listings to avoid always putting Windows tools first; consider grouping by platform or listing cross-platform tools first.
- Explicitly state that all features are available on both Windows and Linux, and provide links to Linux-specific guidance where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/concepts-linked-services.md
...ain//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 listing PowerShell as a primary tool for creating linked services, referencing PowerShell-based quickstarts before mentioning alternatives, and omitting explicit Linux/CLI examples. There is no mention of Bash, Azure CLI, or Linux-specific workflows, and the tooling focus is on Windows-centric technologies.
Recommendations
- Add explicit examples and quickstarts for Azure CLI and Bash to provide Linux parity.
- List cross-platform tools (such as Azure CLI and REST API) before or alongside PowerShell in tool/SDK lists.
- Include sample commands for creating linked services using Azure CLI and Bash scripts.
- Clarify that all major operations can be performed from Linux environments, not just Windows/PowerShell.
- Ensure that references to PowerShell are balanced with equivalent Linux-friendly alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/concepts-parameters-variables.md
...articles/data-factory/concepts-parameters-variables.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing only PowerShell-based tutorials in the 'Related content' section, with no mention of Linux shell, Bash, or cross-platform CLI examples. All step-by-step guides for building pipelines reference PowerShell, which is traditionally associated with Windows environments, and there are no Linux or platform-neutral alternatives provided.
Recommendations
- Include equivalent Bash or Azure CLI examples and tutorials alongside PowerShell-based instructions.
- Explicitly mention cross-platform options (such as Azure CLI or REST API) for users on Linux or macOS.
- Update 'Related content' links to include at least one Linux/Bash-focused tutorial for each PowerShell-based tutorial.
- Clarify in the documentation introduction that the examples are platform-specific, or provide a table of contents with links to both Windows and Linux instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/configure-azure-ssis-integration-runtime-performance.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/configure-azure-ssis-integration-runtime-performance.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell scripts for configuration, referencing only Windows-centric tools and patterns, and omitting any Linux or cross-platform CLI examples. There is no mention of how to perform equivalent tasks using Azure CLI, Bash, or other cross-platform tools, which may hinder Linux users or those working in non-Windows environments.
Recommendations
- Provide equivalent configuration examples using Azure CLI and/or Bash scripts alongside PowerShell examples.
- Explicitly mention cross-platform tooling options (e.g., Azure CLI) and link to relevant documentation.
- Clarify which steps are platform-agnostic and which are specific to Windows, and provide guidance for Linux/macOS users where applicable.
- Ensure that references to scripts or automation do not assume a Windows environment by default.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-amazon-redshift.md
...in//articles/data-factory/connector-amazon-redshift.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing only Windows versions for supported environments, linking exclusively to Windows installation instructions for the Amazon Redshift ODBC driver, and omitting any mention or examples for Linux-based setups. There are no PowerShell-specific examples, but the lack of Linux parity in prerequisites and installation guidance is notable.
Recommendations
- Include explicit support statements and instructions for Linux environments where applicable, especially for the self-hosted integration runtime.
- Provide links to both Windows and Linux installation guides for the Amazon Redshift ODBC driver.
- Add Linux-based examples or notes in the prerequisites and installation sections to ensure users on non-Windows platforms are not excluded.
- Clarify whether the self-hosted integration runtime and Amazon Redshift connector are supported on Linux, and if so, provide relevant setup steps.
- Review all referenced documentation (such as prerequisites and driver installation) to ensure Linux users are equally guided.
Azure Docs
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. It references Windows-specific tools (such as Microsoft Azure Storage Explorer), provides PowerShell cmdlets (New-AzBatchAccount, New-AzBatchPool) as primary automation examples for Azure Batch, and links to a blog post about using PowerShell to manage Azure Batch accounts. There is no mention of Linux/Unix command-line alternatives (such as Azure CLI or Bash scripting) for these operations. Additionally, Windows tools and patterns are mentioned before or instead of cross-platform or Linux-native equivalents.
Recommendations
- For every PowerShell example or cmdlet, provide an equivalent Azure CLI (az) command example, which is cross-platform and widely used on Linux.
- When referencing tools like Microsoft Azure Storage Explorer, mention alternative methods for managing storage (e.g., using az storage CLI commands, or third-party Linux-compatible tools).
- Avoid linking only to Windows/PowerShell-centric blog posts; include documentation or tutorials for Linux/macOS users.
- Explicitly state OS support and parity in relevant sections, and ensure that Linux/Unix workflows are equally represented in examples and tool recommendations.
- Where possible, provide Bash script snippets or references for common automation tasks alongside PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-amazon-rds-for-oracle.md
...ticles/data-factory/connector-amazon-rds-for-oracle.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: file path examples (e.g., C:\MyTrustStoreFile) and instructions for placing files are Windows-centric; there are no equivalent Linux file path or command examples. The only explicit file system example is for Windows, and there is no mention of Linux or cross-platform considerations when configuring truststores or working with self-hosted integration runtime. All command-line examples use generic openssl commands, but the context and file paths are Windows-focused. There are no PowerShell-specific commands, but the documentation assumes a Windows environment for critical steps.
Recommendations
- Provide Linux/Unix file path examples (e.g., /home/user/MyTrustStoreFile) alongside Windows paths when instructing users where to place files.
- Explicitly mention that the self-hosted integration runtime can run on both Windows and Linux, and provide any OS-specific considerations.
- Add Linux-specific instructions or notes for steps involving file placement, permissions, or environment variables (e.g., setting TNS_ADMIN).
- Ensure screenshots and UI references are OS-neutral or clarify if there are differences for Linux users.
- Where relevant, include bash shell equivalents for any command-line steps or scripts.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-azure-table-storage.md
...articles/data-factory/connector-azure-table-storage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing PowerShell commands exclusively for generating a Shared Access Signature (SAS) token, without offering equivalent CLI or scripting examples for Linux/macOS users. No mention is made of cross-platform tools (such as Azure CLI or REST API), and the only command-line guidance is Windows-centric. This may hinder Linux users or those in non-Windows environments from following the instructions seamlessly.
Recommendations
- Provide Azure CLI examples for generating SAS tokens, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include REST API examples for SAS token generation for advanced or automation scenarios.
- When referencing command-line tools, mention both PowerShell and Azure CLI, and present them in parallel or in a 'choose your platform' format.
- Explicitly state that the PowerShell example is for Windows and provide equivalent steps for Linux/macOS.
- Review other sections for similar tool or command references and ensure Linux parity throughout.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/concepts-pipeline-execution-triggers.md
...s/data-factory/concepts-pipeline-execution-triggers.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 in its examples and tooling references. The only command-line example for running a pipeline is given in Azure PowerShell, with no equivalent Bash, Azure CLI, or Linux-native example. The PowerShell example is presented before the Python SDK and REST API, and there is no mention of cross-platform tools such as Azure CLI. The documentation assumes familiarity with PowerShell and Windows tooling, omitting Linux or macOS command-line workflows.
Recommendations
- Add Azure CLI examples for running pipelines, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Provide Bash shell examples for REST API calls (e.g., using curl) to demonstrate manual pipeline execution on Linux.
- Ensure that references to tooling (such as PowerShell) are accompanied by equivalent Linux/macOS instructions or alternatives.
- Reorder examples so that cross-platform tools (Azure CLI, REST API, Python SDK) are presented before or alongside Windows-specific tools like PowerShell.
- Explicitly state that all SDKs and APIs are available on Linux, and provide links or notes for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-amazon-rds-for-sql-server.md
...es/data-factory/connector-amazon-rds-for-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 referencing Windows authentication as a primary authentication method, providing examples and instructions that assume a Windows environment (such as domain\username format), and exclusively mentioning Windows-specific tools and configuration steps (e.g., SQL Server Management Studio, SQL Server Configuration Manager, Windows Firewall) in troubleshooting. There are no Linux equivalents or cross-platform instructions provided, and Linux authentication scenarios are not discussed.
Recommendations
- Add explicit mention and examples for Linux-based authentication scenarios (e.g., using SQL authentication from Linux hosts, Kerberos/Active Directory integration on Linux).
- Include troubleshooting steps and tools relevant to Linux environments, such as how to configure network access, firewalls (iptables, firewalld, ufw), and connectivity testing from Linux machines.
- When referencing tools like SQL Server Management Studio or Configuration Manager, also mention cross-platform alternatives (e.g., Azure Data Studio, sqlcmd) and provide equivalent instructions.
- Avoid assuming the use of Windows domain accounts in examples; provide generic or Linux-compatible examples where possible.
- Clarify any platform-specific limitations or requirements, and provide guidance for both Windows and Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-concur.md
...s/blob/main//articles/data-factory/connector-concur.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by only referencing Windows support for the self-hosted integration runtime, with no mention of Linux support or instructions. There are no Linux-specific examples, tools, or troubleshooting steps, and the prerequisites link explicitly states Windows versions. No PowerShell-specific commands are shown, but the overall guidance assumes a Windows environment.
Recommendations
- Explicitly state whether Linux is supported for the self-hosted integration runtime for this connector. If not, clarify this limitation up front.
- If Linux is supported, add Linux installation and configuration instructions, including any required dependencies or troubleshooting tips.
- Provide parity in examples and screenshots for both Windows and Linux environments, or at least acknowledge the experience on Linux.
- Reference Linux tools and patterns where appropriate, such as using shell commands or systemd for service management.
- If only Windows is supported, consider adding a note explaining the lack of Linux support and, if possible, provide a roadmap or alternatives for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-file-system.md
...b/main//articles/data-factory/connector-file-system.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by prioritizing Windows authentication, using Windows-style paths and escape sequences, referencing Windows tools (such as PowerShell) for integration runtime setup, and providing detailed guidance for Windows environments. Linux support is mentioned only briefly (via Samba), with no Linux-specific configuration examples, authentication guidance, or command-line instructions. All code and path examples use Windows conventions, and references to Linux are minimal and secondary.
Recommendations
- Provide Linux-specific examples for configuring file shares, including NFS and Samba, with corresponding path formats and authentication methods.
- Include Linux command-line instructions (e.g., using bash or shell scripts) for setting up self-hosted integration runtimes, in addition to PowerShell.
- Document Linux authentication options (such as username/password, Kerberos, or SSH keys) and clarify any differences or limitations compared to Windows authentication.
- Show both Windows and Linux path formats in all relevant examples and tables, making it clear how to configure for each OS.
- Expand the prerequisites and setup sections to explicitly cover Linux server requirements, permissions, and troubleshooting.
- Ensure that references to Windows tools (like PowerShell) are paired with Linux equivalents or alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/custom-event-to-hybrid-connection.md
...ticles/event-grid/custom-event-to-hybrid-connection.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias primarily in the 'Create application to process events' section, where only a C#/.NET sample and Visual Studio (a Windows-centric IDE) are referenced for building the consumer application. There are no Linux or cross-platform development instructions, nor are alternative languages or tools highlighted. The prerequisite steps and CLI usage are otherwise cross-platform, but the application development steps assume a Windows environment.
Recommendations
- Include instructions and/or sample applications for Linux and macOS users, such as using VS Code, JetBrains Rider, or command-line .NET tools (dotnet CLI) to build and run the sample.
- Provide equivalent consumer samples in other languages (e.g., Python, Node.js) that are easily runnable on Linux.
- Explicitly mention that the Azure CLI and cURL commands work on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
- Add links to cross-platform development guides or samples for Azure Relay Hybrid Connections.
- Rephrase the application development steps to be IDE-agnostic or provide alternatives to Visual Studio, such as using 'dotnet build' and 'dotnet run' from the command line.