Connectors

38
Total Pages
21
Linux-Friendly Pages
17
Pages with Bias
44.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

90 issues found
Showing 1-25 of 90 flagged pages
Connectors Connect to Oracle Database ...les/connectors/connectors-create-api-oracledatabase.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation assumes the use of the on-premises data gateway, which is primarily a Windows-only tool. There are no instructions or examples for Linux or macOS environments, nor any mention of alternatives or workarounds for non-Windows platforms. All troubleshooting and installation steps refer to Windows-centric patterns and services, such as PBIEgwService, with no Linux equivalents or parity.
Recommendations
  • Explicitly state platform requirements for the on-premises data gateway and Oracle client, including Windows-only limitations.
  • Provide guidance or alternatives for Linux/macOS users, such as using Azure VM with Oracle Database or other cross-platform connectors.
  • Include Linux/macOS-specific troubleshooting steps and installation instructions if possible.
  • Mention any future plans or workarounds for non-Windows environments, or link to relevant resources.
GitHub Create Pull Request
Connectors Process IBM Host Files in Standard Workflows ...icles/connectors/integrate-host-files-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a notable Windows bias by exclusively referencing Windows-only tools (HIS Designer, Visual Studio, .NET Framework 4.8) for critical steps such as generating the required HIDX metadata file. There are no instructions or alternatives for Linux or macOS users to perform these tasks, nor are cross-platform tools mentioned. Screenshots and examples consistently use Windows environments and applications, and prerequisites assume access to Windows software.
Recommendations
  • Provide explicit instructions or alternatives for Linux/macOS users to generate HIDX files, such as a cross-platform CLI tool, web-based designer, or containerized solution.
  • Clarify whether the HIS Designer or HIDX generation can be performed on non-Windows platforms, and if not, offer a workaround or note the limitation.
  • Include examples and screenshots using Linux/macOS environments where possible, or at least acknowledge the steps for those platforms.
  • List prerequisites and installation steps for Linux/macOS if supported, or clearly state the platform requirements up front.
GitHub Create Pull Request
Connectors Connect to 3270 apps on IBM mainframes ...ticles/connectors/integrate-3270-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias primarily through its reliance on the 3270 Design Tool, which requires Microsoft .NET Framework 4.8—a Windows-only prerequisite. No Linux or macOS alternatives or workarounds are mentioned for generating the required HIDX file, nor is there discussion of cross-platform tooling for this critical step. All examples and screenshots are based on the Azure Portal web interface, which is cross-platform, but the tooling dependency for metadata generation is Windows-exclusive.
Recommendations
  • Provide information about generating HIDX files on Linux/macOS, such as alternative tools, command-line utilities, or containerized solutions.
  • Explicitly state platform limitations and suggest workarounds (e.g., using a Windows VM, Docker container, or remote desktop for Linux/macOS users).
  • If no cross-platform solution exists, consider prioritizing development or documentation of such a tool.
  • Add a note in the prerequisites section clarifying that the 3270 Design Tool is Windows-only and suggest steps for non-Windows users.
GitHub Create Pull Request
Connectors Access CICS Programs from Standard Workflows ...ticles/connectors/integrate-cics-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-only tools (HIS Designer, .NET Framework 4.8) for generating required metadata files, without mentioning Linux/macOS alternatives or compatibility. All setup instructions and prerequisites assume a Windows environment, and there are no examples or guidance for Linux or macOS users.
Recommendations
  • Clarify whether HIS Designer is available for Linux/macOS, and if not, provide alternative methods or tools for generating HIDX files on those platforms.
  • If possible, offer a cross-platform version of HIS Designer or document a workflow using open-source or platform-agnostic tools.
  • Explicitly state OS requirements and limitations for critical tooling, and suggest workarounds (e.g., using a Windows VM or container) for non-Windows users.
  • Include examples or notes for Linux/macOS users regarding installation, file upload, and workflow creation steps.
GitHub Create Pull Request
Connectors Connect to 3270 apps on IBM mainframes ...ticles/connectors/integrate-3270-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation requires the use of the '3270 Design Tool' for generating HIDX files, which is only available for Windows (.NET Framework 4.8 required). No Linux/macOS alternatives or workarounds are mentioned, and all setup instructions assume access to this Windows-only tool. There are no examples or guidance for Linux/macOS users on how to generate the required artifacts, creating a significant barrier for non-Windows users.
Recommendations
  • Provide information about Linux/macOS-compatible tools or methods for generating HIDX files, if available.
  • Offer a web-based or cross-platform version of the 3270 Design Tool.
  • Document any possible workarounds, such as running the Windows tool in a VM or via Wine, and note limitations.
  • Explicitly state the Windows-only requirement early in the prerequisites section.
  • Consider providing sample HIDX files for testing, so Linux/macOS users can follow the rest of the workflow.
GitHub Create Pull Request
Connectors Process IBM Host Files in Standard Workflows ...icles/connectors/integrate-host-files-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a notable Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) and HIS Designer for Logic Apps, both of which are Windows-only tools. All instructions for generating the required HIDX metadata file depend on downloading and installing HIS Designer, which requires .NET Framework 4.8 (Windows-only). There are no examples or guidance for Linux or macOS users, nor are alternative cross-platform tools mentioned. Screenshots and workflow steps reference Visual Studio, further reinforcing the Windows-centric approach.
Recommendations
  • Explicitly state HIS Designer is Windows-only and clarify platform requirements early in the prerequisites.
  • Provide or reference alternative methods for generating HIDX metadata files on Linux/macOS, if available (e.g., CLI tools, open-source alternatives, or web-based solutions).
  • If no alternatives exist, offer guidance for Linux/macOS users, such as using a Windows VM, Azure Virtual Desktop, or Docker container to run HIS Designer.
  • Include a note or section on cross-platform considerations and limitations.
  • Add Linux/macOS-specific examples or workflows where possible, especially for file handling and workflow triggers.
GitHub Create Pull Request
Connectors Connect to 3270 apps on IBM mainframes ...ticles/connectors/integrate-3270-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias primarily through its reliance on the 3270 Design Tool, which requires Microsoft .NET Framework 4.8—a Windows-only prerequisite. There are no alternative instructions or tools for Linux or macOS users to generate the required HIDX file, nor is there mention of cross-platform compatibility for the design tool. All setup and workflow examples assume use of the Azure Portal (web-based), but the critical metadata generation step is Windows-dependent. Linux/macOS users are left without a clear path to complete the task.
Recommendations
  • Provide information on whether the 3270 Design Tool can run under Wine or Mono on Linux/macOS, or offer a supported cross-platform version.
  • List alternative methods or open-source tools for generating HIDX files on non-Windows platforms, if available.
  • Explicitly state the platform limitations of the 3270 Design Tool and suggest workarounds for Linux/macOS users.
  • Consider adding a note or section for Linux/macOS users outlining the steps required to obtain or generate HIDX files if they do not have access to Windows.
  • If possible, develop and document a web-based or cross-platform tool for HIDX file creation.
GitHub Create Pull Request
Connectors Access CICS Programs from Standard Workflows ...ticles/connectors/integrate-cics-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-based tools (HIS Designer, .NET Framework 4.8) for generating required metadata, with no mention of Linux/macOS alternatives or compatibility. All setup instructions and prerequisites assume a Windows environment, and there are no examples or guidance for Linux or macOS users.
Recommendations
  • Clarify whether HIS Designer and required components (e.g., .NET Framework) are available or supported on Linux/macOS, or provide alternatives if available.
  • If the tools are Windows-only, explicitly state this limitation and suggest possible workarounds (e.g., using a Windows VM, Docker container, or remote desktop).
  • Add examples or notes for Linux/macOS users regarding how to obtain or generate the HIDX file, or how to interact with the Azure portal from non-Windows systems.
  • Consider developing or linking to cross-platform tooling for metadata generation if feasible.
GitHub Create Pull Request
Connectors Connect to IBM MQ ...b/main/articles/connectors/connectors-create-api-mq.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: it references Windows-specific certificate stores and tools (such as certmgr.exe and PowerShell), provides certificate management instructions only for Windows environments, and omits equivalent Linux procedures or examples. The use of PowerShell and Windows Certificate Manager is described in detail, while no mention is made of Linux commands (e.g., openssl, keytool) or Linux certificate store locations. Additionally, App Service Environment instructions are repeatedly described as 'Windows-only' without Linux alternatives or parity guidance.
Recommendations
  • Add instructions for managing certificates on Linux hosts, including how to add certificates to the appropriate Linux certificate stores (e.g., /etc/ssl/certs, update-ca-certificates).
  • Provide Linux command-line examples for viewing and adding certificates, such as using openssl, keytool, or update-ca-certificates.
  • Clarify whether the MQ connector and Logic Apps workflows can run on Linux-based App Service plans, and if so, provide equivalent steps for those environments.
  • Include troubleshooting guidance for Linux environments, such as how to check cipher suites and certificate validation using Linux tools.
  • When referencing certificate management, mention both Windows and Linux approaches, or explicitly state platform limitations.
  • Avoid presenting Windows tools and procedures as the default or only option; structure instructions to address both platforms equally or in parallel.
GitHub Create Pull Request
Connectors Enable stateful mode for stateless built-in connectors ...ectors/enable-stateful-affinity-built-in-connectors.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell examples and referencing Windows-centric tools (Azure portal, PowerShell) for configuration tasks. There are no examples or guidance for equivalent Linux-native tools (such as Azure CLI or bash scripting), nor are Linux workflows or cross-platform alternatives mentioned. The order of presentation also places PowerShell before any Linux-friendly options, and troubleshooting steps are only given for PowerShell.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, including updating website configuration and troubleshooting.
  • Explicitly mention that Azure CLI and REST API methods work on Linux, macOS, and Windows, and provide sample commands.
  • Include bash or shell script snippets for Linux users where appropriate.
  • Ensure troubleshooting guidance covers CLI-based workflows, not just PowerShell.
  • Review screenshots and UI instructions to clarify cross-platform access (e.g., Azure portal is web-based and OS-agnostic).
GitHub Create Pull Request
Connectors Connect to Oracle Database ...les/connectors/connectors-create-api-oracledatabase.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page assumes the use of the on-premises data gateway, which is primarily a Windows-based tool, and provides instructions and troubleshooting steps that implicitly target Windows environments (e.g., service names like PBIEgwService, installation steps for the Oracle client on the gateway computer). There are no examples or guidance for Linux environments, nor is there mention of Linux-compatible alternatives for the gateway or Oracle client installation.
Recommendations
  • Explicitly state platform requirements for the on-premises data gateway and Oracle client, including Windows and Linux support status.
  • If Linux is supported, provide installation steps and troubleshooting guidance for Linux environments (e.g., systemd service management, package installation commands).
  • If the gateway is Windows-only, mention this limitation clearly and suggest alternatives for Linux users, such as using Azure VM with Oracle Database or other integration methods.
  • Include Linux-specific examples and screenshots where applicable.
  • List both Windows and Linux prerequisites and commands side-by-side to ensure parity.
GitHub Create Pull Request
Connectors Call REST API endpoints from workflows .../articles/connectors/connectors-native-http-swagger.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric tools and workflows, such as the Azure portal (web UI, often used on Windows), Azure Storage Explorer (primarily distributed for Windows), and providing a PowerShell script for CORS configuration without mentioning Linux alternatives (e.g., Bash, Azure CLI). There are no Linux-specific examples or parity for command-line operations, and Windows tools/scripts are mentioned first or exclusively.
Recommendations
  • Provide equivalent Linux/Bash/Azure CLI examples for configuring CORS and uploading Swagger files to Azure Storage.
  • Mention cross-platform availability of Azure Storage Explorer and clarify usage on Linux/macOS.
  • Include sample commands using Azure CLI for all operations currently demonstrated with PowerShell.
  • Add notes or sections for Linux users, including how to perform tasks via terminal or non-Windows environments.
  • Ensure that examples and tooling references are balanced between Windows and Linux, or presented in a platform-neutral order.
GitHub Create Pull Request
Connectors Connect to 3270 apps on IBM mainframes ...ticles/connectors/integrate-3270-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias primarily through exclusive reliance on Windows-only tooling (the 3270 Design Tool requires .NET Framework 4.8, which is Windows-only), and by not mentioning or providing Linux alternatives or examples for key steps such as metadata generation. There are no Linux-specific instructions, nor is there guidance for users on non-Windows platforms. The documentation also references App Service Environment v3 'with Windows plans only' before clarifying connector availability, further reinforcing Windows-first positioning.
Recommendations
  • Provide information about Linux-compatible alternatives for generating HIDX files, or clarify if the 3270 Design Tool can be run under Wine/Mono on Linux.
  • Explicitly state platform requirements and limitations for the 3270 Design Tool, and suggest workarounds or alternatives for Linux/Mac users.
  • If possible, develop and document a cross-platform or web-based tool for HIDX file creation.
  • Add a section addressing Linux users, including any steps they can take to use the connector (e.g., remote desktop to Windows, containerized tool usage, etc.).
  • Ensure future documentation includes parity in examples and instructions for both Windows and Linux environments.
GitHub Create Pull Request
Connectors Process IBM Host Files in Standard Workflows ...icles/connectors/integrate-host-files-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-only tools (HIS Designer, Visual Studio, .NET Framework 4.8) for metadata generation and workflow setup. There are no mentions of Linux-compatible alternatives, nor are there instructions or examples for Linux users. The documentation assumes the use of Windows environments and tooling, which may exclude or complicate usage for Linux-based developers.
Recommendations
  • Provide Linux-compatible alternatives for generating HIDX files, such as a cross-platform CLI tool or web-based designer.
  • Include instructions for installing and running necessary tools on Linux (e.g., via Mono, Wine, or native ports).
  • Offer workflow examples that use Linux-native tools and environments (e.g., VS Code on Linux, Azure CLI, or other editors).
  • Explicitly state platform requirements and limitations, and suggest workarounds for Linux users.
  • Add parity in screenshots and step-by-step guides for Linux environments where possible.
GitHub Create Pull Request
Connectors Access COBOL & RPG Programs from Standard Workflows ...ctors/integrate-ibmi-apps-distributed-program-calls.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively referencing Microsoft Windows tools (Host Integration Server Designer, .NET Framework 4.8) for required metadata generation, without mentioning Linux alternatives or cross-platform options. All setup instructions and prerequisites assume a Windows environment, and no Linux-compatible workflows, tools, or examples are provided.
Recommendations
  • Document whether the HIS Designer for Logic Apps is available for Linux or provide alternative Linux-compatible tools for generating HIDX files.
  • If possible, provide instructions for generating HIDX files on Linux (e.g., via Wine, containers, or open-source equivalents).
  • Explicitly state platform requirements and limitations, and recommend cross-platform approaches if available.
  • Include Linux-specific examples or workflows for users who do not have access to Windows environments.
  • Mention any plans for Linux support or provide links to community-supported solutions for Linux users.
GitHub Create Pull Request
Connectors Access CICS Programs from Standard Workflows ...ticles/connectors/integrate-cics-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) and its Designer tool, which are Windows-only. All setup and prerequisite instructions assume the use of Windows tools (HIS Designer, .NET Framework 4.8), with no mention of Linux alternatives or cross-platform options. There are no examples or instructions for Linux users, nor is there guidance on how to perform equivalent tasks outside the Windows ecosystem.
Recommendations
  • Provide information on whether the HIS Designer or equivalent tooling is available for Linux or via web-based/cloud interfaces.
  • If Linux support is not available, explicitly state this limitation and suggest any possible workarounds (e.g., using a Windows VM, Docker container, or remote desktop).
  • Include instructions or examples for Linux users where possible, such as uploading HIDX files via CLI tools (Azure CLI, PowerShell Core on Linux), or using cross-platform methods.
  • Mention any open-source or third-party alternatives for generating HIDX files that may be usable on Linux.
  • Ensure that documentation does not assume Windows as the default environment; clarify OS requirements and provide parity in guidance for Linux users.
GitHub Create Pull Request
Connectors Access IMS Programs from Standard Workflows ...rticles/connectors/integrate-ims-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools (Host Integration Server Designer, .NET Framework 4.8), and by describing integration patterns and prerequisites that are only available on Windows. There are no examples, instructions, or tool recommendations for Linux users, nor is there mention of Linux-compatible alternatives for generating the required HIDX metadata files. The documentation assumes a Windows environment for all setup and integration steps.
Recommendations
  • Provide explicit instructions or alternatives for Linux users, such as recommending or developing a cross-platform tool for generating HIDX files.
  • Clarify whether the Host Integration Designer or equivalent functionality is available on Linux, or provide a roadmap for Linux support.
  • If possible, offer containerized or web-based versions of the HIS Designer to enable Linux and macOS users to participate in the workflow.
  • Include Linux-specific examples for file upload, workflow creation, and connector configuration, using CLI tools or Azure Portal accessible from Linux.
  • Add a section addressing platform requirements and limitations, making clear the Windows dependency and suggesting workarounds for non-Windows environments.
GitHub Create Pull Request
Connectors Process IBM Host Files in Standard Workflows ...icles/connectors/integrate-host-files-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools (Host Integration Server, HIS Designer, Visual Studio, .NET Framework 4.8) for generating and managing IBM Host File metadata. All setup and workflow examples assume the use of these Windows tools, with no mention of Linux alternatives or cross-platform options. There are no instructions or examples for performing equivalent tasks on Linux, and Windows tooling is presented as the default and only path.
Recommendations
  • Provide instructions or tooling for generating HIDX files on Linux, such as CLI tools, open-source alternatives, or containerized solutions.
  • Mention whether HIS Designer and related tools can be run on Linux (e.g., via Mono, Wine, or in a container), or clarify their platform limitations.
  • Offer examples of workflows using Linux-based environments, such as using Linux-compatible editors or automation tools.
  • Explicitly state platform requirements and suggest workarounds or alternatives for non-Windows users.
  • Include parity in screenshots and step-by-step guides for Linux users, where possible.
GitHub Create Pull Request
Connectors Built-in connector overview ...s/azure-docs/blob/main/articles/connectors/built-in.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several areas. It references Windows-centric technologies and tools such as SQL Server, .NET Framework, and PowerShell script execution, without mentioning Linux equivalents or alternatives. Inline code examples explicitly list PowerShell and C# (commonly associated with Windows), but do not mention Bash, Python, or other Linux-friendly scripting options. The 'File System' connector refers to connecting to a 'network machine' without clarifying Linux support or providing parity examples. Overall, examples and tool references prioritize Windows technologies and omit Linux-specific guidance.
Recommendations
  • Add explicit examples and documentation for Linux-based scripting (e.g., Bash, Python) in the 'Run code from workflows' section alongside PowerShell and C#.
  • Clarify whether the 'File System' connector supports Linux file systems, and provide usage examples for Linux environments.
  • Include references to Linux database systems (e.g., PostgreSQL, MySQL) in addition to SQL Server, or clarify cross-platform support.
  • When listing connectors or supported technologies, avoid Windows-first ordering; instead, present options in alphabetical order or group by platform-neutral categories.
  • Where authentication or integration patterns differ between Windows and Linux (e.g., file paths, permissions), provide guidance for both platforms.
  • Explicitly state platform compatibility for connectors and actions, especially for those commonly associated with Windows.
GitHub Create Pull Request
Connectors Connect to Oracle Database ...les/connectors/connectors-create-api-oracledatabase.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page assumes the use of the on-premises data gateway, which is primarily a Windows-only tool, and all installation and troubleshooting steps reference installing software on 'the computer' without specifying Linux support or alternatives. There are no examples or instructions for Linux environments, nor is there mention of Linux-compatible gateway installation or Oracle client setup. This creates a bias toward Windows users and may exclude or confuse those using Linux servers for Oracle Database access.
Recommendations
  • Explicitly state platform requirements for the on-premises data gateway and Oracle client, including whether Linux is supported.
  • If Linux is supported, provide step-by-step instructions for installing the gateway and Oracle client on Linux, including common distributions.
  • Add troubleshooting steps and error resolutions specific to Linux environments (e.g., service management, file paths, permissions).
  • Where possible, mention cross-platform alternatives or clarify any limitations for non-Windows users.
  • Include Linux-specific screenshots or command-line examples alongside Windows ones.
GitHub Create Pull Request
Connectors Call REST API endpoints from workflows .../articles/connectors/connectors-native-http-swagger.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell scripts as the primary method for automating CORS configuration and mentioning Azure Storage Explorer (a Windows-centric tool) before any Linux alternatives. There are no examples or instructions for Linux shell commands (e.g., Bash, Azure CLI), nor are cross-platform alternatives presented alongside Windows tools. The documentation does not provide parity for Linux users in automation or tooling guidance.
Recommendations
  • Add equivalent Azure CLI or Bash script examples for configuring CORS on Azure Storage, alongside or before the PowerShell script.
  • Explicitly mention cross-platform tools (such as azcopy, Azure CLI, or web-based portal) for blob management and CORS configuration.
  • Clarify that Azure Storage Explorer is available on Linux and macOS, or suggest alternatives if needed.
  • Ensure that automation examples (scripts) are provided for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) users.
  • Review all instructions and screenshots to ensure they are not exclusively Windows-centric and provide parity for Linux environments.
GitHub Create Pull Request
Connectors Connect to 3270 apps on IBM mainframes ...ticles/connectors/integrate-3270-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates Windows bias primarily through exclusive reliance on Windows-only tooling (the 3270 Design Tool requires .NET Framework 4.8, which is Windows-only), and by omitting any mention of Linux-compatible alternatives or instructions. All setup and prerequisites assume a Windows environment, and there are no examples or guidance for Linux users. The documentation also refers to App Service Environment v3 'with Windows plans only', further reinforcing Windows-centric patterns.
Recommendations
  • Provide information on whether the 3270 Design Tool can be run on Linux (e.g., via Mono or Wine), or suggest Linux-compatible alternatives if available.
  • Explicitly state OS requirements and offer guidance for Linux users, such as using Azure CLI, cross-platform .NET, or containerized solutions.
  • Include Linux-specific setup instructions or examples, especially for uploading files and managing Logic Apps resources.
  • If no Linux alternatives exist, acknowledge this limitation and suggest workarounds or future roadmap for Linux support.
GitHub Create Pull Request
Connectors Connect to IBM MQ ...b/main/articles/connectors/connectors-create-api-mq.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: certificate management instructions and examples are exclusively Windows-centric, referencing Windows Certificate Manager (certmgr.exe), Windows certificate stores, and PowerShell scripts for certificate inspection. No Linux equivalents or cross-platform alternatives are provided for certificate management or validation, nor are Linux tools (such as OpenSSL or Linux certificate stores) mentioned. The troubleshooting and configuration sections also refer to Windows operating system behaviors and do not address Linux scenarios. This may hinder Linux users from following the documentation effectively.
Recommendations
  • Add Linux-specific instructions for certificate management, such as using OpenSSL and updating Linux certificate stores (e.g., /etc/ssl/certs).
  • Provide cross-platform examples for viewing and adding certificates, including Linux shell commands (e.g., openssl, update-ca-certificates) alongside PowerShell.
  • Reference Linux tools and procedures (such as keytool, OpenSSL, or system certificate stores) in addition to Windows tools like certmgr.exe.
  • Clarify which steps are platform-specific and offer alternatives for Linux and macOS users.
  • Include troubleshooting guidance for Linux environments, especially regarding cipher suites and certificate validation.
  • Ensure parity in screenshots and step-by-step instructions for both Windows and Linux users.
GitHub Create Pull Request
Connectors Enable stateful mode for stateless built-in connectors ...ectors/enable-stateful-affinity-built-in-connectors.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias towards Windows environments by providing detailed Azure PowerShell examples and troubleshooting steps, referencing Windows-centric tools (PowerShell), and omitting equivalent Linux/CLI/bash instructions. The order of presentation also places PowerShell as a primary method, with no mention of cross-platform alternatives like Azure CLI or REST API usage via curl. This may disadvantage users working on Linux or macOS systems.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell instructions, showing how to perform the same configuration tasks on Linux/macOS.
  • Include REST API usage examples using curl or similar cross-platform tools, especially for the 'Update By Id' operation.
  • Explicitly mention that PowerShell is available on Linux/macOS, or clarify platform requirements for each method.
  • Reorder sections so that platform-neutral methods (Azure portal, REST API, Azure CLI) are presented before Windows-specific tools like PowerShell.
  • Add troubleshooting steps and error handling for Azure CLI and REST API methods, not just PowerShell.
GitHub Create Pull Request
Connectors Access COBOL & RPG Programs from Standard Workflows ...ctors/integrate-ibmi-apps-distributed-program-calls.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) and HIS Designer, which are Windows-only tools, for generating required metadata (HIDX files). All setup instructions assume the use of Windows and .NET Framework, with no mention of Linux-compatible alternatives or cross-platform tooling. There are no Linux or PowerShell/Bash examples, nor any guidance for users on non-Windows platforms.
Recommendations
  • Document whether the HIS Designer or equivalent tooling is available for Linux or macOS, or provide alternative methods for generating HIDX files on those platforms.
  • If possible, offer a cross-platform or web-based tool for HIDX file creation and management.
  • Include explicit instructions or examples for Linux users, such as using Wine, containers, or remote Windows VMs for running HIS Designer.
  • Clarify any platform limitations in the prerequisites section, so non-Windows users are aware of requirements and workarounds.
  • Consider providing sample HIDX files or metadata for testing, so Linux users can follow the workflow steps without needing Windows-only tools.
GitHub Create Pull Request
← Previous Page 1 of 4 Next →