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 1126-1150 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/format-parquet.md
...ocs/blob/main//articles/data-factory/format-parquet.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias in its instructions for configuring Java runtimes for Self-hosted Integration Runtime. It references Windows-specific tools and paths (e.g., Windows registry, C:\Program Files), and provides no explicit Linux or cross-platform guidance or examples for setting up Java or environment variables. This may hinder Linux users attempting similar configurations.
Recommendations
- Provide explicit Linux instructions for installing and configuring JRE/JDK/OpenJDK, including typical installation paths and environment variable setup (e.g., JAVA_HOME, PATH).
- Mention Linux equivalents for Windows registry checks, such as checking JAVA_HOME or common installation directories.
- Include Linux shell command examples for setting environment variables (e.g., export JAVA_HOME=/usr/lib/jvm/java-23-openjdk-amd64).
- Clarify that the instructions apply to both Windows and Linux, or specify any platform-specific differences.
- Add screenshots or terminal snippets for Linux where Windows screenshots are provided.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/how-to-invoke-ssis-package-ssdt.md
...ticles/data-factory/how-to-invoke-ssis-package-ssdt.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Windows-only tools (SSDT, Visual Studio, Solution Explorer), Windows authentication, and Windows file system conventions (UNC paths). There are no Linux or cross-platform alternatives or examples provided, and all instructions assume a Windows environment. No mention is made of running or developing SSIS packages from non-Windows platforms, nor are any Linux tools, shells, or workflows referenced.
Recommendations
- Explicitly state the platform requirements and limitations at the beginning of the documentation, clarifying that SSDT and Visual Studio are Windows-only tools.
- If possible, provide information or links about cross-platform alternatives for SSIS development and execution (such as Azure Data Factory UI, Azure CLI, or REST APIs) that can be used from Linux or macOS.
- Include a section addressing Linux/macOS users, outlining what is and is not possible from those platforms, and suggest workarounds (such as using remote Windows VMs or containers).
- Avoid assuming the user is on Windows in all examples and instructions; where appropriate, note that certain steps are Windows-specific.
- If any command-line or automation is discussed, provide PowerShell and Bash (or cross-platform CLI) equivalents where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/how-to-migrate-ssis-job-ssms.md
.../articles/data-factory/how-to-migrate-ssis-job-ssms.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically requiring SQL Server Management Studio (SSMS), a Windows-only tool, for migration steps. All instructions, screenshots, and workflows assume the use of SSMS and SQL Server Agent, with no mention of Linux-compatible tools, cross-platform alternatives, or command-line options. There are no examples or guidance for users on Linux or macOS platforms.
Recommendations
- Provide alternative migration instructions using cross-platform tools, such as Azure Data Studio (which is available on Windows, Linux, and macOS), if possible.
- Include command-line or PowerShell Core (pwsh) scripts that can be run on Linux/macOS, or reference Azure CLI/REST API approaches for migration.
- Explicitly state the Windows-only requirement for SSMS and suggest workarounds or remote access options for Linux users.
- Add a section or note addressing Linux/macOS users, outlining any limitations and possible migration paths that do not require SSMS.
- If no Linux-native options exist, request or advocate for development of such features in future tooling.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/how-to-invoke-ssis-package-ssis-activity.md
...ta-factory/how-to-invoke-ssis-package-ssis-activity.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. It exclusively references Windows concepts such as UNC paths, Windows authentication, and Windows-centric tools like SQL Server Data Tools (SSDT) and SQL Server Management Studio (SSMS). All file path examples use Windows UNC notation, and there is no mention of Linux file systems, authentication mechanisms, or cross-platform alternatives. The documentation assumes the use of Windows-based Azure-SSIS IR and does not address Linux-based scenarios or provide parity for users on non-Windows platforms.
Recommendations
- Provide equivalent examples and instructions for Linux environments, such as using SMB/CIFS mounts on Linux for Azure Files, and clarify any platform limitations.
- Mention and, where possible, provide alternatives to Windows authentication (e.g., Azure Active Directory, SQL authentication) that work across platforms.
- Include file path examples using Linux conventions (e.g., /mnt/azurefiles/...) alongside UNC paths, and explain how Linux users can access Azure Files.
- Reference cross-platform tools (such as Azure Data Studio) in addition to or instead of Windows-only tools like SSMS and SSDT.
- Explicitly state any platform limitations (e.g., if only Windows-based Azure-SSIS IR is supported) at the beginning of the documentation.
- If PowerShell is referenced, provide equivalent CLI or Bash examples for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/how-to-invoke-ssis-package-azure-enabled-dtexec.md
...ory/how-to-invoke-ssis-package-azure-enabled-dtexec.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows environments. It assumes the use of SQL Server Management Studio (SSMS), a Windows-only tool, for both installation and configuration of AzureDTExec. All command-line examples use Windows paths and DOS-style commands, with no mention of Linux or cross-platform alternatives. There is no discussion of running AzureDTExec on Linux or macOS, nor are there instructions or examples for non-Windows environments.
Recommendations
- Clarify whether AzureDTExec is supported on Linux or macOS. If not, explicitly state this limitation.
- If cross-platform support exists or is planned, provide installation and configuration instructions for Linux and macOS, including any prerequisites and differences.
- Include command-line examples using Linux/macOS shell syntax (e.g., bash), and reference file paths and environment variables as they would appear on those systems.
- Mention any alternative tools or workflows available for non-Windows users, such as using Azure Data Factory UI, REST APIs, or Azure CLI.
- If SSMS is required and only available on Windows, suggest remote or containerized approaches for Linux/macOS users, or recommend equivalent Azure-native management tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/how-to-create-tumbling-window-trigger.md
.../data-factory/how-to-create-tumbling-window-trigger.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias in its code samples and tooling recommendations. The PowerShell section is presented first and references Windows-specific paths (e.g., C:\ADFv2QuickStartPSH\), and the installation instructions for Azure PowerShell explicitly reference 'Install Azure PowerShell on Windows with PowerShellGet'. There is no mention of Linux or macOS compatibility for PowerShell, nor are there any Bash or shell script examples. The CLI section is more cross-platform, but the overall emphasis and ordering favor Windows environments.
Recommendations
- Explicitly state that Azure PowerShell is available on Linux and macOS, and provide installation instructions for those platforms.
- Use cross-platform file paths in examples (e.g., use relative paths or note both Windows and Linux/macOS path formats).
- Add Bash or shell script equivalents for the PowerShell examples, especially for common tasks like creating and managing JSON files.
- Consider presenting Azure CLI examples before PowerShell, as CLI is natively cross-platform.
- Wherever possible, clarify that both PowerShell and CLI commands can be run on any OS, and provide links to relevant cross-platform documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/how-to-schedule-azure-ssis-integration-runtime.md
...tory/how-to-schedule-azure-ssis-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows and PowerShell bias. All scripting and automation examples are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or cross-platform alternatives. The use of Windows-centric tools such as SQL Server Management Studio (SSMS) is assumed for verification steps. There is no guidance for users on Linux or macOS, and no examples using platform-agnostic tools or commands. The documentation also references PowerShell modules and Azure Automation runbooks in PowerShell without offering equivalent instructions for other environments.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands for starting, stopping, and monitoring Azure-SSIS IR, as Azure CLI is cross-platform.
- Include Bash script examples for automation tasks, especially for scheduling via cron or using Azure CLI in Linux/macOS environments.
- Mention and provide steps for using Data Factory REST APIs directly with curl or other HTTP clients, which are platform-neutral.
- For verification steps, suggest alternatives to SQL Server Management Studio, such as Azure Data Studio (cross-platform) or querying via sqlcmd.
- Clarify in prerequisites and throughout the guide that all steps can be performed from Linux/macOS using Azure CLI and REST APIs, not just from Windows/PowerShell.
- Where PowerShell is referenced, explicitly note that it is available cross-platform, but also provide syntax for native shells (Bash, zsh, etc.) where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/includes/data-factory-quickstart-verify-output-cleanup.md
...ludes/data-factory-quickstart-verify-output-cleanup.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only PowerShell commands for resource cleanup, which are specific to Windows environments. There are no equivalent examples for Linux users (e.g., using Azure CLI or Bash), and the exclusive use of PowerShell commands suggests a Windows-centric approach.
Recommendations
- Include Azure CLI (az) command examples for both deleting a resource group and deleting a data factory, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Explicitly mention that PowerShell commands are for Windows users, and provide parallel instructions for Linux/macOS users.
- Consider adding Bash script snippets or terminal commands where appropriate to ensure Linux parity.
- Review screenshots and UI instructions to ensure they are not Windows-specific, or provide notes for cross-platform differences if any.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/introduction.md
...-docs/blob/main//articles/data-factory/introduction.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page for Azure Data Factory shows mild Windows bias. While the core content is platform-neutral, the 'Monitor' section highlights PowerShell as a primary automation/monitoring tool, and the 'Related content' section lists PowerShell before other SDKs (such as .NET, Python, REST). There is no mention of Linux-specific tools or CLI examples (e.g., Bash, Azure CLI), and PowerShell is referenced without noting its cross-platform availability or alternatives. The documentation does not provide Linux command-line examples or reference Linux-native tooling, which may leave Linux users feeling secondary.
Recommendations
- Add Azure CLI examples and references alongside or before PowerShell, especially in sections discussing automation, monitoring, and deployment.
- Explicitly mention that PowerShell is cross-platform, or provide Bash/Linux shell equivalents where relevant.
- In the 'Related content' section, list Azure CLI and Python examples before or alongside PowerShell to avoid the impression of Windows-first tooling.
- Where monitoring or scripting is discussed, include references to Linux-native tools (e.g., Bash scripts, cron jobs, or integration with Linux monitoring solutions) as alternatives.
- Ensure that all code samples and quickstart links are available for both Windows and Linux environments, and make this parity clear in the documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/event-grid-dotnet-get-started-pull-delivery.md
...nt-grid/event-grid-dotnet-get-started-pull-delivery.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), using Windows UI navigation (menus, dialogs, screenshots), and providing only PowerShell-based NuGet installation commands. There are no instructions or examples for Linux or cross-platform development environments (such as VS Code, JetBrains Rider, or command-line .NET tooling on Linux/macOS). All setup and workflow steps assume a Windows/Visual Studio context, with no mention of Linux equivalents or alternatives.
Recommendations
- Add instructions for creating and managing .NET projects using the dotnet CLI, which is cross-platform and works on Linux/macOS as well as Windows.
- Provide alternative steps for installing NuGet packages using the dotnet CLI (e.g., 'dotnet add package Azure.Messaging.EventGrid.Namespaces') instead of only PowerShell/Visual Studio UI.
- Include screenshots or descriptions for cross-platform editors such as VS Code, or mention that the steps can be performed in any editor.
- Explicitly state that the sample code and instructions are cross-platform, and provide any Linux/macOS-specific prerequisites or notes.
- Where UI navigation is described, offer equivalent command-line alternatives for users not on Windows.
- Mention that Visual Studio is available for Mac, or suggest other IDEs/editors for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/join-azure-ssis-integration-runtime-virtual-network.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/join-azure-ssis-integration-runtime-virtual-network.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by referencing Azure PowerShell as the primary or sole CLI-based method for provisioning and managing Azure-SSIS IR. There are no examples or mentions of using cross-platform tools such as Azure CLI or Bash scripts, and no Linux-specific instructions or parity. The related content and step-by-step guides focus on Azure PowerShell and ADF UI, both of which are more familiar to Windows users, with no equivalent Linux or platform-neutral alternatives provided.
Recommendations
- Add examples and instructions using Azure CLI (az), which is cross-platform and works natively on Linux, macOS, and Windows.
- Wherever Azure PowerShell is referenced, provide a parallel Azure CLI command or script.
- Explicitly mention that all steps can be performed from Linux/macOS environments using Azure CLI or REST APIs.
- Include a section or callout for Linux/macOS users, highlighting any differences or additional requirements.
- Ensure that all referenced tutorials and related articles also contain Linux-friendly instructions and not just PowerShell or Windows-centric tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/event-hubs-integration.md
...ob/main//articles/event-grid/event-hubs-integration.md
High Priority
View Details →
Detected Bias Types
Windows First
Visual Studio Only
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by requiring Visual Studio for publishing the Azure Functions app and running the sample project, without mentioning or providing alternatives for Linux users (such as VS Code or Azure Functions Core Tools). The instructions for running the sample data generator and publishing the function are tightly coupled to Windows/Visual Studio workflows. While the Azure CLI is used for infrastructure deployment (which is cross-platform), the development and deployment steps for the function app and data generator are Windows-centric, with no Linux or cross-platform guidance.
Recommendations
- Provide instructions for publishing the Azure Functions app using cross-platform tools such as Azure Functions Core Tools and VS Code, including command-line examples.
- Offer guidance for running the WindTurbineDataGenerator sample on Linux, including .NET CLI commands (e.g., 'dotnet run') and any prerequisites for Linux environments.
- Explicitly mention that Visual Studio is not required and that Linux/macOS users can use alternative editors and tools.
- Include screenshots or terminal output examples from Linux environments where applicable.
- Ensure that all steps (especially code publishing and sample execution) have Linux/macOS equivalents or alternatives documented alongside Windows instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/manage-azure-ssis-integration-runtime.md
.../data-factory/manage-azure-ssis-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based command-line examples for managing Azure-SSIS integration runtimes. There are no equivalent examples or instructions for Linux users (e.g., using Azure CLI, Bash, or cross-platform tools). The reliance on PowerShell and references to PowerShell cmdlets implicitly assume a Windows environment or require users to install PowerShell Core on non-Windows systems, which is not acknowledged or addressed.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available cross-platform, and provide installation instructions or links for Linux/macOS users if PowerShell is required.
- Add Bash script examples where appropriate, especially for common automation scenarios.
- Ensure that references to tools and commands are not Windows-specific unless absolutely necessary, and always offer Linux/macOS alternatives when possible.
- Review related content and tutorials to ensure Linux parity throughout the documentation set.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/monitor-programmatically.md
...ain//articles/data-factory/monitor-programmatically.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing REST API examples exclusively in PowerShell, referencing PowerShell cmdlets and tools throughout, and omitting equivalent Linux/bash/cURL examples. Windows/PowerShell approaches are presented first or exclusively in several sections, making it less accessible for Linux or cross-platform users.
Recommendations
- Provide REST API examples using cross-platform tools such as curl or HTTPie, alongside or instead of PowerShell scripts.
- Include bash or shell script examples for monitoring pipelines, especially in the REST API and general scripting sections.
- Clearly indicate when examples are Windows-specific and offer equivalent Linux/macOS instructions where possible.
- Balance the order of presentation so that Windows and Linux approaches are given equal prominence.
- Reference cross-platform tools (e.g., Azure CLI) in addition to or instead of Windows-only tools (e.g., PowerShell cmdlets).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/quickstart-create-data-factory-resource-manager-template.md
...ickstart-create-data-factory-resource-manager-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns (e.g., Notepad, C:\ paths), providing only Azure PowerShell commands for resource cleanup, and omitting Linux/macOS equivalents for file creation and command-line operations. No cross-platform or Linux-specific instructions are given, and all examples assume a Windows environment.
Recommendations
- Provide Linux/macOS equivalents for file creation (e.g., using nano, vim, or echo in the terminal) and use of home directory paths (e.g., ~/ADFv2QuickStart).
- Include Azure CLI commands for resource cleanup and management, as Azure CLI is cross-platform and commonly used on Linux/macOS.
- Avoid referencing Windows-only tools like Notepad; instead, suggest 'a text editor of your choice' and give examples for both Windows and Linux/macOS.
- Show both Windows and Linux/macOS file path conventions in examples.
- Clearly indicate when instructions are platform-specific, and provide parallel steps for other operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/monitor-ssis.md
...-docs/blob/main//articles/data-factory/monitor-ssis.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 Azure PowerShell and Windows-centric tools (SSMS, SSDT, SQL Server Agent) for monitoring and managing SSIS operations. There are no examples or mentions of Linux-based tools, command-line interfaces, or cross-platform alternatives for monitoring or querying SSIS logs and metrics.
Recommendations
- Include examples using Azure CLI (which is cross-platform) for checking SSIS IR operational status, alongside or instead of Azure PowerShell.
- Mention and provide examples for querying logs and metrics using tools available on Linux, such as Azure Data Studio (which is cross-platform) instead of only SSMS and SSDT.
- Clarify whether all monitoring and querying features are available from non-Windows environments, and provide guidance for Linux/macOS users.
- If certain features are Windows-only, explicitly state this and suggest alternative approaches for Linux users where possible.
- Add sample Kusto Query Language (KQL) queries that can be run from the Azure Portal or Azure Data Studio, emphasizing their cross-platform nature.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/monitor-integration-runtime.md
...//articles/data-factory/monitor-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples and monitoring instructions use PowerShell cmdlets, with no mention of equivalent CLI, REST API, or SDK approaches that would be more cross-platform. The self-hosted integration runtime is described as being installed on 'on-premises Windows machine', with no discussion of Linux support or alternatives. Windows tools and patterns (PowerShell, SSMS, SSDT) are referenced exclusively or before any cross-platform options. There are no Linux-specific instructions, examples, or clarifications regarding support.
Recommendations
- Provide equivalent Azure CLI and/or REST API examples for all PowerShell cmdlets, especially for monitoring integration runtimes.
- Clarify whether self-hosted integration runtime can be installed on Linux, and if so, provide Linux installation and monitoring instructions.
- Mention and demonstrate cross-platform tools (e.g., Azure CLI, Data Factory REST API, SDKs in Python/Java) alongside or before Windows-specific tools.
- When referencing tools like SSMS or SSDT, note any cross-platform alternatives or limitations.
- Explicitly state OS requirements or support for each integration runtime type, and offer guidance for Linux users where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/sap-change-data-capture-debug-shir-logs.md
...ata-factory/sap-change-data-capture-debug-shir-logs.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references the Microsoft Integration Runtime Configuration Manager, a Windows-only tool, for sending logs. There are no instructions or examples for performing the same task on Linux or non-Windows platforms. The workflow, screenshots, and terminology are all Windows-centric, with no mention of Linux equivalents or command-line alternatives.
Recommendations
- Provide equivalent instructions for Linux environments, such as using command-line tools or configuration files to collect and send logs.
- Clarify whether the self-hosted integration runtime and its diagnostic tools are available on Linux, and if not, state this explicitly.
- If Linux is supported, include screenshots or terminal examples for Linux users.
- Mention any cross-platform or web-based alternatives to the Configuration Manager, if available.
- Ensure that future documentation addresses both Windows and Linux users equally, or clearly states platform limitations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/self-hosted-integration-runtime-diagnostic-tool.md
...ory/self-hosted-integration-runtime-diagnostic-tool.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows tools (such as dmgcmd.exe), showing only Windows UI screenshots, and omitting any mention of Linux support or equivalent commands. There are no Linux-specific instructions or examples, nor is there clarification on whether the tool is available for Linux environments.
Recommendations
- Explicitly state whether the diagnostic tool is available for Linux or only for Windows.
- If Linux is supported, provide equivalent Linux command-line examples and screenshots.
- Mention any Linux-specific installation or troubleshooting steps, or clarify if the tool is not available for Linux.
- If the tool is Windows-only, recommend alternative diagnostic approaches for Linux users or provide a roadmap for Linux support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/quickstart-create-data-factory-bicep.md
...s/data-factory/quickstart-create-data-factory-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and resource management, but consistently lists PowerShell after CLI. However, it references Notepad as the example text editor, which is Windows-specific, and does not mention Linux or cross-platform alternatives. There are no Linux shell-specific instructions or examples for file creation or manipulation, nor is there mention of Linux-native tools for any step. The documentation assumes use of the Azure portal or Windows tools for all non-CLI/PowerShell tasks.
Recommendations
- When suggesting a text editor, mention cross-platform options such as VS Code, nano, or vim alongside Notepad.
- Include Linux shell commands (e.g., 'echo' or 'cat') for creating the emp.txt file, in addition to the Notepad instruction.
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide any necessary notes for Linux users (such as file path differences).
- Where PowerShell is referenced, clarify that Azure PowerShell is available cross-platform, or provide Bash alternatives where appropriate.
- Consider including a section or callout for Linux/macOS users to ensure parity and inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/self-hosted-integration-runtime-proxy-ssis.md
...-factory/self-hosted-integration-runtime-proxy-ssis.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias throughout. All setup and configuration instructions assume a Windows environment, referencing Windows-specific tools (PowerShell, Local Security Policy, service accounts like NT SERVICE\DIAHostService), file paths (C:\ProgramData\SSISTelemetry), and drivers/installers that are only available for Windows. There are no examples or guidance for Linux environments, nor any mention of cross-platform alternatives or limitations. PowerShell is the only scripting example provided, and all troubleshooting/logging instructions use Windows paths and tools.
Recommendations
- Explicitly state if the self-hosted IR and SSIS proxy feature is only supported on Windows, or clarify any Linux support.
- If Linux is supported, provide equivalent setup, configuration, and troubleshooting instructions for Linux environments, including command-line examples (e.g., Bash scripts), file paths, and service management.
- If only Windows is supported, add a clear note at the top of the documentation to prevent confusion for Linux users.
- Where possible, mention cross-platform alternatives or limitations (e.g., 'This feature is not available on Linux').
- Include references to Linux-compatible tools or drivers if available, or provide guidance on running in a Linux environment (such as via containers or compatibility layers).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/quickstart-create-data-factory-dot-net.md
...data-factory/quickstart-create-data-factory-dot-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) for project creation, using PowerShell commands for NuGet package installation, and omitting any Linux or cross-platform development instructions. There are no examples or guidance for Linux users, such as using VS Code, the .NET CLI, or Bash for package management and project setup.
Recommendations
- Add instructions for creating the .NET project using the .NET CLI (dotnet new console) for cross-platform compatibility.
- Provide NuGet package installation commands using the .NET CLI (dotnet add package ...) alongside the PowerShell/Visual Studio instructions.
- Mention and provide guidance for using cross-platform editors like Visual Studio Code.
- Clarify that the .NET SDK and Azure SDK libraries are cross-platform, and explicitly state that the steps can be performed on Linux, macOS, and Windows.
- Include screenshots or terminal examples from Linux/macOS environments where appropriate.
- Avoid assuming the use of Visual Studio or PowerShell as the default environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/quickstart-create-data-factory-python.md
.../data-factory/quickstart-create-data-factory-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits mild Windows bias by referencing Notepad as the default text editor for creating files and by suggesting 'command prompt with administrator privileges' as the terminal to use. Azure Storage Explorer, a GUI tool, is recommended for file uploads, which is more common in Windows workflows. There are no explicit Linux or macOS instructions or examples for equivalent tasks (such as using nano/vim, or Linux CLI tools for file creation and upload). No PowerShell-specific commands are present, but the overall tone and tool selection assume a Windows environment.
Recommendations
- When instructing users to create a text file, mention cross-platform editors (e.g., 'Use Notepad (Windows), nano/vim (Linux/macOS), or any text editor of your choice').
- For uploading files to Azure Blob Storage, provide CLI alternatives such as 'az storage blob upload' or 'Azure CLI' commands, and mention that Azure Storage Explorer is optional and cross-platform.
- Replace 'Open a terminal or command prompt with administrator privileges' with 'Open a terminal or command prompt with appropriate permissions', and clarify that the instructions apply to Windows, Linux, and macOS.
- Wherever tools or workflows are mentioned, ensure parity by listing Linux/macOS equivalents alongside Windows tools, or by using neutral, cross-platform language.
- Explicitly state that all Python code and Azure SDK commands are cross-platform, and provide any OS-specific caveats if necessary.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/scenario-ssis-migration-overview.md
...icles/data-factory/scenario-ssis-migration-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation heavily references Windows-centric tools (SSDT, SSMS, dtutil, dtexec, DMA) and workflows, with no mention of Linux equivalents or cross-platform alternatives. All command-line utilities and management tools cited are Windows-only, and there are no examples or guidance for users operating from Linux environments. The documentation assumes the user is on Windows, both in tool recommendations and migration steps.
Recommendations
- Explicitly state the platform requirements for tools like SSMS, SSDT, dtutil, dtexec, and DMA, and clarify their Windows-only nature.
- If possible, provide or reference any available cross-platform or Linux-compatible alternatives for package management and migration (e.g., Azure CLI, REST APIs, or third-party tools).
- Include examples or guidance for users working from Linux environments, such as how to interact with Azure Data Factory or SSIS from Linux (if supported).
- Reorder explanations or tables to avoid always listing Windows tools and patterns first; consider a neutral or cross-platform-first approach.
- Add a section addressing limitations and workarounds for Linux users, or explicitly state if Linux is not supported for these migration tasks.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/self-hosted-integration-runtime-troubleshoot-guide.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/self-hosted-integration-runtime-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exhibits a strong Windows bias throughout. All troubleshooting steps, log collection, and configuration instructions assume a Windows environment, referencing Windows-specific tools (Event Viewer, MMC, certutil, regedit, Process Monitor, Control Panel, Windows Services, etc.), Windows file paths, and PowerShell commands. There are no Linux equivalents or instructions, nor any mention of how to perform these tasks on Linux-based self-hosted IR nodes. Even when cross-platform tools (like openssl) are mentioned, their context is still within a Windows workflow.
Recommendations
- Add explicit sections or callouts for Linux-based self-hosted IR nodes, where supported, covering log collection, service management, and troubleshooting.
- Provide Linux equivalents for all Windows-only instructions (e.g., using journalctl/syslog for logs, openssl for certificates, systemctl for service management, Linux file paths, etc.).
- Include bash or shell script examples alongside PowerShell commands.
- Reference cross-platform tools (such as Wireshark, openssl, curl) in a platform-agnostic way, and clarify any platform-specific limitations.
- Where features are Windows-only, clearly state this and provide guidance or alternatives for Linux users.
- Review all screenshots and UI references to ensure they are not exclusively Windows-focused, or supplement with Linux examples where possible.