Connectors

70
Total Pages
58
Linux-Friendly Pages
12
Pages with Bias
17.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

32 issues found
Showing 1-25 of 32 flagged pages
Connectors Process IBM Host Files in Standard Workflows ...icles/connectors/integrate-host-files-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 page demonstrates a notable Windows bias, primarily through exclusive reliance on Windows-only tools (HIS Designer, Visual Studio, .NET Framework 4.8) for critical metadata generation and workflow setup. There are no Linux/macOS alternatives or instructions, and all example screenshots and setup steps assume a Windows environment. This creates friction for Linux/macOS users, who cannot complete key tasks without access to Windows.
Recommendations
  • Provide alternative methods for generating HIDX files that work on Linux/macOS (e.g., a cross-platform CLI tool, web-based designer, or open-source solution).
  • Clarify system requirements and explicitly state the lack of Linux/macOS support, if applicable.
  • Offer guidance for Linux/macOS users, such as using remote Windows VMs or containers, or suggest partner/community tools if available.
  • Include example workflows and screenshots using Linux/macOS environments where possible (e.g., using Azure portal from Linux, FTP tools, etc.).
  • Consider prioritizing platform-neutral instructions and tools in future updates.
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-12 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 a Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) Designer and Transaction Integrator, which are Windows-only tools. The prerequisite for creating the required HIDX metadata file is Microsoft .NET Framework 4.8, also Windows-only. No Linux or macOS alternatives, installation instructions, or parity tools are mentioned. All setup and workflow examples assume use of Windows tools, and there is no guidance for non-Windows environments.
Recommendations
  • Explicitly state the platform requirements for HIS Designer and .NET Framework, clarifying that these are Windows-only.
  • Provide guidance or workarounds for Linux/macOS users, such as using a Windows VM or container, or remote desktop to a Windows machine.
  • Investigate and document any cross-platform alternatives for generating HIDX files, or provide a roadmap for Linux/macOS support.
  • Include a section in prerequisites and setup for non-Windows users, outlining steps to access required tools.
  • If possible, develop and document a web-based or cross-platform tool for HIDX file generation.
GitHub Create Pull Request
Connectors Connect to Oracle Database ...les/connectors/connectors-create-api-oracledatabase.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation assumes the use of the on-premises data gateway, which is primarily a Windows-only tool. There is no mention of Linux or macOS support for the gateway, nor are there any examples or instructions for installing or using the gateway or Oracle client on non-Windows platforms. All troubleshooting and installation steps implicitly target Windows environments.
Recommendations
  • Explicitly state platform support for the on-premises data gateway (e.g., clarify if Linux/macOS are supported or not).
  • If Linux/macOS support exists, provide installation and troubleshooting steps for those platforms.
  • If only Windows is supported, recommend alternatives for Linux users (e.g., using Azure VM with Oracle, or other integration methods).
  • Include examples or notes for connecting to Oracle Database from Logic Apps in Linux/macOS scenarios, if possible.
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 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. All setup and tool instructions assume a Windows environment, and the documentation does not address how non-Windows users can complete critical steps.
Recommendations
  • Explicitly state platform requirements for the 3270 Design Tool and .NET Framework.
  • Provide guidance or alternatives for Linux/macOS users, such as running the tool via Wine, using a VM, or offering a cross-platform version.
  • Mention any open-source or third-party tools that can generate HIDX files on non-Windows platforms, if available.
  • Add a section discussing Linux/macOS compatibility and workarounds for the HIDX file creation step.
  • Consider prioritizing platform-neutral instructions or clearly labeling Windows-specific steps.
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 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) Designer, which is a Windows-only tool, and requiring .NET Framework 4.8 for metadata generation. There are no mentions of Linux or macOS alternatives, nor any guidance for non-Windows users. All examples and setup instructions assume a Windows environment, creating friction for users on other platforms.
Recommendations
  • Explicitly state platform requirements for HIS Designer and .NET Framework, and clarify that these are Windows-only.
  • Provide guidance or workarounds for Linux/macOS users, such as using a Windows VM, Docker container, or remote desktop to access HIS Designer.
  • Investigate and document any cross-platform alternatives for generating HIDX files, or provide a REST API or CLI tool that can be run on Linux/macOS.
  • Add a section addressing Linux/macOS users, outlining steps they can take to complete the workflow.
  • If possible, advocate for development of cross-platform tooling for Host Integration Designer tasks.
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 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
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. There are no Linux or macOS alternatives or instructions for creating the required HIDX file, nor is there mention of cross-platform tooling. All setup and workflow examples assume use of the Azure portal, which is web-based and cross-platform, but the critical design step is gated by a Windows-only tool.
Recommendations
  • Provide information about Linux/macOS alternatives for creating HIDX files, such as open-source or cross-platform 3270 screen capture tools, if available.
  • Document whether the 3270 Design Tool can be run under Wine or in a VM on Linux/macOS, and provide guidance if so.
  • Consider developing or recommending a cross-platform version of the 3270 Design Tool, or at least a CLI-based tool that can run on Linux/macOS.
  • Explicitly state the platform limitations and suggest workarounds for non-Windows users.
  • Add a note clarifying that the rest of the workflow (Azure portal, Logic Apps) is cross-platform, but the design step is not.
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 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing Windows-only tooling (HIS Designer for Logic Apps, Visual Studio, .NET Framework 4.8) for generating required metadata (HIDX files). There are no Linux/macOS alternatives or instructions, and all example screenshots and setup steps assume a Windows environment. This creates friction for Linux/macOS users who cannot natively use these tools.
Recommendations
  • Provide guidance or tooling for generating HIDX files on Linux/macOS, such as a cross-platform CLI, web-based tool, or Docker image.
  • Clarify whether HIDX files can be manually authored or converted from COBOL copybooks using open-source or platform-agnostic tools.
  • Explicitly state platform requirements and offer workarounds for non-Windows users (e.g., using a Windows VM, Azure-hosted VM, or container).
  • Include example workflows and screenshots using Linux/macOS environments where possible.
  • List prerequisites for both Windows and non-Windows platforms, and provide parity in setup instructions.
GitHub Create Pull Request
Connectors Connect to Oracle Database ...les/connectors/connectors-create-api-oracledatabase.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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, and provides no guidance or examples for Linux or macOS environments. All installation and troubleshooting steps reference Windows patterns and services, such as PBIEgwService, with no mention of Linux equivalents or alternatives. This creates friction for non-Windows users attempting to connect Azure Logic Apps to Oracle Database.
Recommendations
  • Explicitly state OS requirements and limitations for the on-premises data gateway.
  • Provide guidance or alternatives for Linux/macOS users, such as using Azure VM with Oracle or other cross-platform connectors.
  • Include troubleshooting steps and service management instructions for Linux environments if supported.
  • Add examples or workflows that demonstrate Oracle connectivity from Linux-based systems, or clarify if such scenarios are unsupported.
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 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) Designer, which is a Windows-only tool, as the required method for generating the HIDX metadata file. The prerequisites and setup instructions mention only Windows tools and dependencies (such as .NET Framework 4.8), with no mention of Linux/macOS alternatives or compatibility. There are no examples or guidance for Linux or macOS users, and the workflow setup implicitly assumes a Windows environment.
Recommendations
  • Clarify whether HIS Designer is available or supported on Linux/macOS, and if not, explicitly state this limitation.
  • Provide alternative methods or third-party tools for generating HIDX files on Linux/macOS, if available.
  • If possible, develop and document a cross-platform version of the HIS Designer or a CLI tool for HIDX generation.
  • Add a section addressing Linux/macOS users, including any workarounds or limitations.
  • List Windows prerequisites after general requirements, not before, and avoid assuming Windows as the default platform.
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: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed instructions and code samples for Azure PowerShell, a Windows-centric tool, but does not offer equivalent examples for Linux-native tools (such as Azure CLI or REST via curl). The troubleshooting and configuration sections rely exclusively on PowerShell commands, and there are no Linux shell or cross-platform alternatives presented. This creates a bias toward Windows users and may hinder Linux users from following the guide easily.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, showing how to update resource properties and troubleshoot errors using az commands.
  • Include REST API usage examples with curl, demonstrating how to PATCH the resource configuration from a Linux shell.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, but provide native shell examples to improve accessibility.
  • Ensure troubleshooting steps are also covered for CLI and REST methods, not just PowerShell.
  • Review all screenshots and UI instructions to confirm they are not Windows-specific (e.g., avoid references to Windows-only browser features or tools).
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 (HIS Designer, Visual Studio, .NET Framework 4.8) for generating required metadata files, with no mention of Linux alternatives or cross-platform options. All setup and workflow examples assume the use of Windows environments and tools, and there are no instructions or guidance for Linux users. The documentation does not provide parity for Linux users who may wish to generate or manage HIDX files, nor does it mention any Linux-compatible approaches.
Recommendations
  • Provide instructions for generating HIDX files on Linux, or clarify if the process is Windows-only.
  • List any cross-platform or Linux-compatible alternatives to HIS Designer and Visual Studio, if available.
  • Explicitly state platform requirements and limitations for metadata generation and workflow design.
  • Offer guidance on using Azure Logic Apps and IBM Host File connector from Linux environments, including file upload and workflow management.
  • If no Linux alternatives exist, suggest workarounds (e.g., using a Windows VM or container) and document these steps.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-oracledatabase.md ...les/connectors/connectors-create-api-oracledatabase.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
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, and all installation and troubleshooting steps reference installing and running the gateway and Oracle client on 'the computer' without clarifying platform support. There are no Linux-specific instructions or examples, and no mention of Linux compatibility or alternatives. This creates a bias toward Windows environments.
Recommendations
  • Explicitly state platform support for the on-premises data gateway and Oracle client (e.g., whether Linux is supported or not).
  • If Linux is supported, provide Linux-specific installation steps and troubleshooting guidance for both the gateway and Oracle client.
  • If Linux is not supported, clearly call this out in the prerequisites or limitations section.
  • Include examples or notes for Linux users, such as using Oracle Instant Client on Linux, or alternatives for connecting from Linux hosts.
  • When referencing services or commands (e.g., restarting PBIEgwService), provide Linux equivalents if available, or note their absence.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-native-http-swagger.md .../articles/connectors/connectors-native-http-swagger.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates Windows bias by primarily referencing Windows-centric tools and patterns. The only automation example for enabling CORS uses a PowerShell script, and Azure Storage Explorer (a GUI tool popular on Windows) is mentioned before any CLI alternatives. There are no Linux shell (bash/az CLI) examples, and Windows tools are referenced first or exclusively for key steps.
Recommendations
  • Provide equivalent bash/az CLI commands for enabling CORS on Azure Storage, alongside the PowerShell example.
  • Mention cross-platform tools (such as az CLI and REST API) before or alongside Windows-specific tools like PowerShell and Azure Storage Explorer.
  • Clarify that Azure Storage Explorer is available on Linux and macOS, or suggest alternative CLI workflows for Linux users.
  • Add explicit Linux/macOS instructions or examples where automation or tooling is discussed, to ensure parity.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-3270-apps-ibm-mainframe.md ...ticles/connectors/integrate-3270-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias primarily through exclusive reliance on Windows-only tools (such as the 3270 Design Tool, which requires Microsoft .NET Framework 4.8), and by not mentioning or providing alternatives for Linux users. All setup and tool prerequisites are Windows-centric, and there are no examples or guidance for Linux environments. Additionally, the App Service Environment v3 support is explicitly limited to 'Windows plans only', and no mention is made of Linux-based App Service plans or cross-platform compatibility.
Recommendations
  • Provide information about Linux-compatible alternatives for the 3270 Design Tool, or clarify if none exist.
  • If possible, offer a cross-platform or web-based version of the 3270 Design Tool, or document how Linux/Mac users can generate HIDX files (e.g., via a containerized or remote Windows environment).
  • Explicitly state the platform limitations (e.g., '3270 Design Tool is only available for Windows') early in the prerequisites section.
  • If the connector or workflow is supported on Linux-based App Service plans, document the steps and any differences.
  • Include a section or FAQ addressing Linux and Mac users, outlining their options and any workarounds.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-host-files-ibm-mainframe.md ...icles/connectors/integrate-host-files-ibm-mainframe.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a bias toward Windows environments by exclusively referencing Windows-only tools such as Host Integration Server (HIS) Designer and Visual Studio, and by requiring the Microsoft .NET Framework 4.8 as a prerequisite. There are no examples or guidance for Linux or cross-platform users, and all setup and workflow steps assume a Windows-based development environment. Linux alternatives or instructions are not mentioned.
Recommendations
  • Provide guidance or alternatives for Linux users, such as cross-platform tools for generating HIDX files or accessing host file metadata.
  • If the HIS Designer is Windows-only, explicitly state this limitation and suggest possible workarounds (e.g., using a Windows VM, Docker container, or cloud-hosted environment).
  • Include examples or instructions for Linux-based workflows, such as using Azure CLI, cross-platform editors, or scripting environments.
  • Mention any open-source or third-party tools that can be used on Linux to create or manipulate HIDX files, if available.
  • Clarify whether the IBM Host File connector and related processes can be managed entirely through the Azure Portal or CLI, which are cross-platform, and provide examples accordingly.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-ims-apps-ibm-mainframe.md ...rticles/connectors/integrate-ims-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
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) Designer and Transaction Integrator, which are Windows-only tools. All setup instructions and prerequisites assume the use of Windows (e.g., requiring .NET Framework 4.8), and there is no mention of Linux-compatible alternatives or workflows. No examples or guidance are provided for Linux users, nor is there any discussion of cross-platform support or parity.
Recommendations
  • Explicitly state platform requirements and limitations (e.g., HIS Designer is Windows-only) early in the documentation.
  • Provide guidance or alternatives for Linux users, such as recommending open-source or cross-platform tools if available, or clarifying if none exist.
  • Include a section addressing Linux/macOS users, even if only to acknowledge the lack of support and suggest possible workarounds (e.g., using a Windows VM or container).
  • If possible, develop and document Linux-compatible tooling for HIDX file generation and integration.
  • Ensure future documentation includes parity in examples and instructions for both Windows and Linux environments.
GitHub Create Pull Request
Connectors Call REST API endpoints from workflows .../articles/connectors/connectors-native-http-swagger.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. When describing how to enable CORS for Azure Blob Storage, it highlights the Azure portal (a web interface, but often associated with Windows usage) and specifically recommends a PowerShell script for automation, without mentioning Linux/macOS alternatives like Azure CLI, Bash, or cross-platform scripting. Azure Storage Explorer is mentioned, which is cross-platform, but PowerShell is referenced first and exclusively for scripting. No Linux/macOS-specific instructions or examples are provided for these tasks.
Recommendations
  • Provide Azure CLI or Bash script examples for enabling CORS and uploading Swagger files, alongside PowerShell.
  • Explicitly state that Azure Storage Explorer is available for Windows, Linux, and macOS.
  • Add notes or links for Linux/macOS users on installing and using Azure CLI and Storage Explorer.
  • Avoid listing PowerShell scripts as the only automation method; offer parity with cross-platform tools.
  • When referencing scripting, present Azure CLI and PowerShell examples side-by-side or in parallel sections.
GitHub Create Pull Request
Connectors Connect to IBM MQ ...b/main/articles/connectors/connectors-create-api-mq.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias, especially in certificate management and troubleshooting sections. It references Windows-specific tools (certmgr.exe), Windows certificate stores, and provides only PowerShell/Kudu console examples for viewing certificates. There are no Linux/macOS equivalents or instructions for managing certificates or troubleshooting on non-Windows hosts, despite IBM MQ and Azure Logic Apps being cross-platform. Windows terminology and procedures are presented as the default or only option.
Recommendations
  • Provide Linux/macOS equivalents for certificate management, such as using openssl, keytool, or Linux certificate stores.
  • Add examples for viewing and adding certificates on Linux/macOS hosts (e.g., using bash, openssl, or platform-native tools).
  • Clarify platform requirements for App Service Environment and certificate handling, and explicitly state if Linux/macOS are supported or not.
  • Where PowerShell is used, offer alternative commands for bash/zsh or other common shells.
  • Reference cross-platform documentation for certificate stores and management, not just Windows-specific links.
GitHub Create Pull Request
Connectors Enable stateful mode for stateless built-in connectors ...ectors/enable-stateful-affinity-built-in-connectors.md
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias by exclusively providing Azure PowerShell examples and troubleshooting steps, with no mention of cross-platform CLI alternatives such as Azure CLI, Bash, or REST API usage from Linux/macOS. Windows-centric tools and patterns (PowerShell, Set-AzResource) are presented as the primary or only automation method, and troubleshooting guidance is only given for PowerShell. There are no Linux/macOS-specific instructions or parity in examples.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, including updating website configuration and troubleshooting.
  • Explicitly mention that Azure CLI and REST API can be used from Linux/macOS and provide sample commands.
  • Include Bash script examples for automation tasks.
  • Clarify platform compatibility for each method (e.g., PowerShell, CLI, REST API).
  • Provide troubleshooting steps for Azure CLI and REST API usage, not just PowerShell.
GitHub Create Pull Request
Connectors Access CICS Programs from Standard Workflows ...ticles/connectors/integrate-cics-apps-ibm-mainframe.md
Medium 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 page demonstrates a Windows bias by exclusively referencing Windows-only tooling (HIS Designer, which requires .NET Framework 4.8), and by mentioning Microsoft Host Integration Server (HIS) and its Transaction Integrator as the primary method for integration. There are no Linux or macOS alternatives or instructions, and no examples or guidance for non-Windows environments. The prerequisites and setup steps assume access to Windows tools, creating friction for Linux/macOS users.
Recommendations
  • Clearly state platform requirements and limitations for HIS Designer and Host Integration Server.
  • Provide guidance or alternatives for Linux/macOS users, such as web-based tools, containerized solutions, or cross-platform utilities if available.
  • If no Linux/macOS options exist, suggest workarounds (e.g., using a Windows VM, Azure-hosted Windows environment, or remote desktop).
  • Add a section addressing Linux/macOS users, clarifying what is and isn't possible, and linking to any relevant resources.
  • Consider developing or documenting cross-platform tooling for metadata generation if feasible.
GitHub Create Pull Request
Connectors Access IMS Programs from Standard Workflows ...rticles/connectors/integrate-ims-apps-ibm-mainframe.md
Medium 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-only tools (Host Integration Server Designer, which requires .NET Framework 4.8), omitting any mention of Linux/macOS-compatible alternatives or instructions. All setup and prerequisite steps assume a Windows environment, and no Linux or cross-platform guidance is provided for generating the required HIDX metadata files. This creates friction for Linux/macOS users who cannot natively run the required tooling.
Recommendations
  • Explicitly state platform requirements for HIS Designer and .NET Framework, and clarify that these are Windows-only.
  • Provide guidance for Linux/macOS users, such as using a Windows VM, Docker container, or remote desktop to access the HIS Designer.
  • Investigate and document any cross-platform alternatives for generating HIDX files, or provide a roadmap for such tooling.
  • Add a section addressing Linux/macOS users, outlining workarounds or future plans for parity.
  • Consider providing sample HIDX files for testing, so users on non-Windows platforms can follow along with later steps.
GitHub Create Pull Request
Connectors Connect to IBM MQ ...b/main/articles/connectors/connectors-create-api-mq.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation displays a notable Windows bias, especially in certificate management and troubleshooting sections. Windows tools (certmgr.exe, PowerShell) are referenced exclusively for certificate store manipulation, and instructions for viewing or adding certificates rely on Windows-centric approaches. The documentation also references Windows-only hosting scenarios (ASE v3 with Windows plans) and uses PowerShell for certificate inspection without mentioning Linux/macOS equivalents. Linux or macOS methods for certificate management are missing, and Windows terminology (Trusted Root Certification Authorities Store) is used throughout.
Recommendations
  • Provide equivalent Linux/macOS instructions for viewing and managing certificates (e.g., using openssl, keytool, or Linux certificate stores).
  • Mention Linux/macOS certificate store locations and management tools alongside Windows instructions.
  • Clarify which steps are Windows-only and offer alternatives for non-Windows environments.
  • Include examples or references for Linux/macOS users in troubleshooting and configuration sections.
  • Avoid presenting Windows tools and terminology first or exclusively; strive for platform-neutral language.
GitHub Create Pull Request
Connectors Access COBOL & RPG Programs from Standard Workflows ...ctors/integrate-ibmi-apps-distributed-program-calls.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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-only tools (Host Integration Server Designer, which requires .NET Framework 4.8), and does not mention or provide Linux/macOS alternatives or examples. All setup instructions and prerequisites assume a Windows environment, with no guidance for non-Windows users. This creates friction for Linux/macOS users who may wish to use the IBM i connector with Azure Logic Apps.
Recommendations
  • Clearly state platform requirements for HIS Designer and .NET Framework, and highlight that these are Windows-only.
  • Provide guidance or alternatives for Linux/macOS users, such as remote access to a Windows VM, containerized solutions, or any available cross-platform tools.
  • If possible, develop and document a cross-platform method for generating HIDX files, or provide a web-based tool.
  • Include explicit notes or sections for Linux/macOS users outlining any limitations and possible workarounds.
  • Consider listing platform requirements at the top of the prerequisites section.
GitHub Create Pull Request
Connectors Call REST API endpoints from workflows .../articles/connectors/connectors-native-http-swagger.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates moderate Windows bias, particularly in the section on hosting Swagger files in Azure Storage. It references the Azure portal (a web tool, but often associated with Windows workflows), Azure Storage Explorer (primarily a Windows application, though cross-platform), and provides a PowerShell script for automating CORS configuration, with no mention of Linux/macOS CLI alternatives (e.g., Bash, Azure CLI, or REST API). Windows-centric tools and patterns are mentioned first and exclusively for automation, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI and/or Bash script examples for enabling CORS and uploading Swagger files to Azure Storage, alongside PowerShell.
  • Explicitly mention cross-platform availability of Azure Storage Explorer and link to installation instructions for Linux/macOS.
  • Add notes or examples for using REST API calls to configure CORS and upload files, which work on any OS.
  • Ensure that automation steps are not PowerShell-exclusive and present Linux/macOS alternatives equally or first.
GitHub Create Pull Request
Connectors Enable stateful mode for stateless built-in connectors ...ectors/enable-stateful-affinity-built-in-connectors.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 providing Azure PowerShell examples exclusively, referencing Windows-centric tools (PowerShell, Azure portal), and omitting equivalent Linux/macOS CLI instructions (such as Azure CLI or bash). The troubleshooting and configuration sections rely on PowerShell commands, with no mention of cross-platform alternatives. Windows tools and patterns are presented first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all configuration and troubleshooting steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or provide installation guidance for non-Windows platforms.
  • Include bash or shell script equivalents where possible, especially for REST API calls.
  • Reorder examples to present cross-platform methods (Azure CLI, REST API) before or alongside Windows-specific tools.
  • Clarify which steps are platform-agnostic (e.g., REST API) and which require Windows tools.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →