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 26-50 of 90 flagged pages
Connectors Access CICS Programs from Standard Workflows ...ticles/connectors/integrate-cics-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 page demonstrates a Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) and its Designer tool, which are Windows-only. All instructions for generating required metadata (HIDX files) depend on HIS Designer, which requires .NET Framework 4.8 (Windows-only). There are no mentions of Linux-compatible alternatives, nor are there examples or guidance for Linux users. The historical context and tool recommendations focus on Windows integration patterns first and exclusively.
Recommendations
  • Explicitly state platform requirements for HIS Designer and .NET Framework, clarifying Windows-only support.
  • Investigate and document any Linux-compatible methods for generating HIDX files, or provide guidance for Linux users (e.g., using containers, remote Windows VMs, or alternative tools if available).
  • If no Linux alternatives exist, suggest workarounds for Linux users, such as running HIS Designer in a Windows VM or via cloud-hosted Windows environments.
  • Add a section addressing Linux user scenarios, including any limitations and possible future roadmap for cross-platform support.
  • Ensure parity in examples and instructions by including Linux-specific notes or alternatives where possible.
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-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 exhibits Windows bias by exclusively referencing Windows-based tools (Host Integration Server Designer, .NET Framework 4.8) for generating required metadata (HIDX files) and by highlighting historical Windows integration patterns. There are no mentions of Linux equivalents, alternative cross-platform tooling, or instructions for Linux users. The prerequisites and setup steps assume a Windows environment, and no examples or guidance are provided for Linux users.
Recommendations
  • Provide information on whether the HIS Designer tool can be run on Linux (e.g., via Wine, Mono, or a container), or offer a cross-platform alternative for generating HIDX files.
  • Explicitly state OS requirements for all tooling and offer guidance for Linux users, such as remote access to a Windows VM or alternative approaches.
  • Include Linux-specific examples or instructions for uploading HIDX files and managing workflows in Azure Logic Apps from Linux environments.
  • Mention any available REST APIs, CLI tools (such as Azure CLI), or other cross-platform methods for performing required actions.
  • Clarify whether the integration steps (e.g., uploading files, configuring workflows) can be performed entirely via browser or CLI from any OS.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias primarily through exclusive reliance on Windows-only tooling (3270 Design Tool requiring .NET Framework 4.8), lack of Linux alternatives or examples, and repeated references to Windows environments (App Service Environment v3 with Windows plans only). No Linux-compatible design tool or workflow is mentioned, and all setup instructions assume access to Windows software and Azure portal UI, with no CLI or cross-platform alternatives.
Recommendations
  • Provide information about Linux-compatible alternatives for the 3270 Design Tool, or clarify if none exist and suggest possible workarounds.
  • Include examples or instructions for using the IBM 3270 connector with Linux-based environments, such as App Service Environment v3 with Linux plans, if supported.
  • Offer cross-platform setup instructions, such as using Azure CLI, PowerShell Core (cross-platform), or REST API, in addition to Azure portal UI.
  • Explicitly state platform limitations and recommend best practices for Linux users, including any third-party or open-source tools that could be used to generate HIDX files.
  • Add notes or sections comparing Windows and Linux support for the connector, and update prerequisites to reflect platform requirements.
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: 2026-01-09 00:34
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) for generating required metadata files, and by highlighting historical Windows integration patterns. There are no mentions of Linux equivalents, cross-platform alternatives, or instructions for Linux users. All setup and prerequisites assume a Windows environment.
Recommendations
  • Explicitly state platform requirements for Host Integration Server Designer and clarify if Linux or macOS alternatives exist.
  • If possible, provide instructions or tooling for generating HIDX files on Linux (e.g., via containerized tools, web-based designer, or CLI utilities).
  • Include a section addressing Linux users, with guidance on how to participate in the workflow or alternatives if Windows-only tooling is required.
  • Mention any cross-platform compatibility for the connector itself, and clarify which steps are platform-dependent.
  • If no Linux alternatives exist, acknowledge this limitation and suggest workarounds (such as using a Windows VM or cloud-hosted service for metadata generation).
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-ibmi-apps-distributed-program-calls.md ...ctors/integrate-ibmi-apps-distributed-program-calls.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows tools (Host Integration Server Designer, .NET Framework 4.8) as prerequisites for generating required metadata, without mentioning Linux alternatives or cross-platform options. All setup instructions and examples assume a Windows environment, and there are no examples or guidance for Linux users. The documentation introduces Windows tooling before any discussion of platform-neutral or Linux-compatible approaches.
Recommendations
  • Provide information about whether the HIS Designer tool or equivalent functionality is available for Linux or macOS, or suggest alternative methods for generating HIDX files on non-Windows platforms.
  • If the connector or workflow setup can be performed from Linux or macOS, include explicit instructions or examples for those platforms.
  • Mention any cross-platform requirements or limitations up front, so Linux users can assess compatibility before starting.
  • If .NET Framework is required, clarify whether .NET Core/.NET 6+ (cross-platform) is supported, or provide guidance for Linux users.
  • Consider adding a section or callout for Linux users, noting any differences, workarounds, or unsupported scenarios.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-cics-apps-ibm-mainframe.md ...ticles/connectors/integrate-cics-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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-based tools (Host Integration Server, HIS Designer, .NET Framework 4.8) for generating required metadata files (HIDX) and does not mention or provide Linux-compatible alternatives or examples. All setup instructions and prerequisites assume a Windows environment, and there is no guidance for Linux users or parity in tooling.
Recommendations
  • Identify and document any Linux-compatible tools or methods for generating HIDX files, or clarify if none exist.
  • If possible, provide instructions for running HIS Designer or equivalent tooling on Linux (e.g., via Wine, containers, or alternative open-source tools).
  • Explicitly state platform requirements and limitations, so Linux users are aware of the lack of support.
  • Add Linux-specific examples or troubleshooting guidance if/when Linux support becomes available.
  • Consider collaborating with product teams to develop cross-platform tooling or web-based solutions for metadata generation.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/enable-stateful-affinity-built-in-connectors.md ...ectors/enable-stateful-affinity-built-in-connectors.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed instructions for enabling stateful mode in Azure Logic Apps, including examples using the Azure portal, Azure Resource Management API, and Azure PowerShell. However, it exclusively features PowerShell for command-line automation, which is a Windows-centric tool, and does not mention or provide equivalent examples for Linux users (e.g., Azure CLI, Bash, or REST calls via curl). There is no guidance for Linux-native workflows or tools, and PowerShell is presented as the only scripting option for automation.
Recommendations
  • Add equivalent Azure CLI examples for updating website configuration and troubleshooting, as Azure CLI is cross-platform and widely used on Linux.
  • Include REST API examples using curl or similar Linux-native tools to demonstrate how Linux users can perform the same operations.
  • Explicitly mention that PowerShell is available cross-platform, but also provide Bash/CLI alternatives for parity.
  • Review troubleshooting steps to ensure they are not PowerShell-exclusive and offer solutions for Linux environments.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing only a PowerShell script for enabling CORS on Azure Blob Storage and referencing Windows-centric tools (Azure Portal, Azure Storage Explorer) without mentioning or providing Linux CLI equivalents. There are no examples or instructions for performing these tasks using Linux-native tools such as Azure CLI, Bash, or cross-platform scripting options.
Recommendations
  • Add Azure CLI and Bash examples for enabling CORS on Azure Blob Storage, alongside the PowerShell script.
  • Explicitly mention that Azure Storage Explorer is available on multiple platforms, and provide installation instructions for Linux.
  • Include instructions for uploading Swagger files and managing blob containers using Azure CLI or REST API, not just through the Azure Portal or Storage Explorer.
  • Ensure that all automation and scripting examples are provided for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-mq.md ...b/main/articles/connectors/connectors-create-api-mq.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 exclusively reference Windows tools (e.g., certmgr.exe, PowerShell, Windows certificate stores), and all step-by-step guides for viewing or adding certificates use PowerShell and Windows-centric UI. There are no equivalent instructions or examples for Linux environments, nor are Linux certificate stores or command-line tools (such as openssl or Linux file paths) mentioned. Windows terminology and tools are presented first and exclusively, with no parity for Linux users.
Recommendations
  • Add instructions for managing certificates on Linux hosts, including using openssl and Linux file system paths.
  • Provide examples for viewing and adding certificates using Linux shell commands (e.g., openssl, keytool) and describe where certificates should be placed on Linux-based App Service hosts.
  • Clarify whether the MQ connector and Logic Apps can run on Linux-based App Service plans, and if so, document the Linux-specific steps for certificate management and troubleshooting.
  • Where PowerShell scripts are referenced, provide equivalent bash or shell commands for Linux users.
  • Reference Linux certificate stores (such as /etc/ssl/certs) and explain how to validate and import certificates in those environments.
  • Ensure that troubleshooting and error messages include guidance for both Windows and Linux users.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/built-in.md ...s/azure-docs/blob/main/articles/connectors/built-in.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 mild Windows bias. It references Windows-centric technologies such as PowerShell and .NET Framework for code execution, and mentions 'File System' connectors that typically target Windows network shares, without clarifying Linux compatibility or providing Linux-specific examples. The inline code section lists PowerShell and C# (traditionally Windows-focused) before JavaScript, and does not mention Bash or other Linux-native scripting options. There are no explicit Linux or Unix examples, nor is there guidance for Linux users regarding file system connectors or script execution.
Recommendations
  • Add explicit examples and documentation for using built-in connectors with Linux file systems (e.g., NFS, SMB on Linux, or local Linux paths).
  • Clarify whether the 'File System' connector supports Linux hosts and provide setup instructions for Linux environments.
  • Include Bash or other Linux-native scripting options in the 'Run code from workflows' section, alongside PowerShell and C#.
  • Where PowerShell is mentioned, also provide equivalent Bash or shell script examples for Linux users.
  • Review connector documentation to ensure parity in describing both Windows and Linux scenarios, especially for file operations and code execution.
  • Explicitly state platform compatibility for connectors and actions that may be perceived as Windows-centric.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively referencing the on-premises data gateway, which is primarily a Windows-only tool, and by instructing users to install the Oracle client on the same computer as the gateway without mentioning Linux support or alternatives. There are no examples or instructions for Linux environments, and all troubleshooting steps assume a Windows setup (e.g., service names like PBIEgwService).
Recommendations
  • Explicitly state platform support for the on-premises data gateway and Oracle client, including whether Linux is supported.
  • If Linux is supported, provide installation and configuration instructions for Linux environments alongside Windows instructions.
  • Include troubleshooting steps relevant to Linux (e.g., service management commands, common Linux errors).
  • Mention cross-platform alternatives or clarify limitations for non-Windows users.
  • Add examples and screenshots from Linux environments where applicable.
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: 2026-01-09 00:34
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) for generating required metadata files, and does not mention or provide Linux alternatives or examples. All setup instructions and screenshots are based on Windows environments, with no guidance for Linux users. This may hinder Linux developers from following the workflow or using the IBM Host File connector effectively.
Recommendations
  • Provide instructions for generating HIDX files using cross-platform or Linux-compatible tools, if available.
  • List any Linux alternatives to HIS Designer and Visual Studio, or clarify if the process is Windows-only.
  • Explicitly state OS requirements and limitations for key steps (e.g., metadata generation) and suggest workarounds for Linux users (such as using a Windows VM or container).
  • Include example workflows and screenshots using Linux-based environments and tools where possible.
  • If no Linux-compatible options exist, acknowledge this limitation and provide guidance for Linux users to access required functionality.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/built-in.md ...s/azure-docs/blob/main/articles/connectors/built-in.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page for Azure Logic Apps built-in connectors demonstrates a moderate Windows bias. Windows-centric tools and technologies such as SQL Server, .NET Framework, and PowerShell are highlighted as built-in connectors or supported scripting languages. PowerShell is listed as a primary scripting option for inline code, alongside C# and JavaScript, but there is no mention of Bash, Python, or other Linux-native scripting languages. The File System connector refers to 'your network machine' without clarifying cross-platform support, which may imply a Windows environment. Windows technologies (SQL Server, .NET Framework, PowerShell) are mentioned before or instead of Linux equivalents, and there is no explicit mention of Linux file systems, Linux scripting, or open-source alternatives.
Recommendations
  • Add examples and explicit support for Linux-native scripting languages (e.g., Bash, Python) in the 'Run code from workflows' section.
  • Clarify whether the File System connector supports Linux file systems (e.g., ext4, NFS) and provide examples for both Windows and Linux environments.
  • Include references to open-source or cross-platform database connectors (e.g., PostgreSQL, MySQL) alongside SQL Server.
  • When listing scripting options, mention Linux-native tools and languages to ensure parity.
  • Review connector documentation to ensure that both Windows and Linux usage scenarios are described and illustrated equally.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-mq.md ...b/main/articles/connectors/connectors-create-api-mq.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: it references Windows-specific certificate stores and tools (such as certmgr.exe and PowerShell), provides instructions and examples only for Windows environments (e.g., using PowerShell and Windows Certificate Manager), and omits equivalent Linux instructions or tools for certificate management and validation. The documentation assumes the use of Windows-based App Service plans for certain features and does not mention Linux alternatives or provide parity in examples.
Recommendations
  • Add instructions and examples for managing certificates on Linux hosts, such as using openssl, update-ca-certificates, or keytool.
  • Include Linux-specific steps for viewing and adding certificates to trusted stores (e.g., /etc/ssl/certs, /usr/local/share/ca-certificates).
  • Provide shell (bash) script examples alongside PowerShell for certificate thumbprint verification.
  • Clarify which features and workflows are supported on Linux-based App Service plans and document any differences.
  • Reference cross-platform tools and approaches for certificate management, not just Windows-specific utilities.
  • Explicitly state platform limitations and provide guidance for Linux users where Windows-only features exist.
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: 2026-01-08 00:53
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, and does not mention or provide Linux alternatives or examples. All screenshots and step-by-step instructions assume a Windows environment, and there is no guidance for Linux users on how to perform equivalent tasks.
Recommendations
  • Provide instructions and tooling options for Linux users to generate HIDX files, such as cross-platform CLI tools or web-based alternatives.
  • Include Linux-based examples for uploading files and managing workflows, such as using Azure CLI or REST API from a Linux shell.
  • Mention and document any platform requirements or limitations explicitly, and suggest workarounds for non-Windows environments.
  • Offer guidance for Linux users on how to interact with Azure Logic Apps and IBM Host File connector without relying on Windows-only software.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows by providing only a PowerShell script for enabling CORS on Azure Storage, referencing Windows-centric tools (Azure Storage Explorer, Azure portal) without mentioning Linux equivalents or CLI alternatives, and omitting Linux-specific instructions or examples for hosting Swagger files or configuring CORS.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for enabling CORS on Azure Storage, suitable for Linux and macOS users.
  • Mention cross-platform tools such as azcopy or Azure CLI for blob management, alongside Azure Storage Explorer.
  • Clarify that Azure Storage Explorer is available on Linux and macOS, or suggest other cross-platform alternatives.
  • Include instructions for uploading Swagger files and configuring access using Linux-native tools and commands.
  • Ensure that all PowerShell examples are paired with CLI/Bash alternatives for parity.
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: 2026-01-08 00:53
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) Designer, which is a Windows-only tool, and requiring Microsoft .NET Framework 4.8 as a prerequisite. There are no mentions of Linux equivalents, alternatives, or cross-platform tooling for generating the required HIDX metadata file. All setup and usage instructions assume a Windows environment, with no guidance for Linux users.
Recommendations
  • Document whether the HIS Designer for Logic Apps can be run on Linux (e.g., via Wine or containers), or clarify its platform limitations.
  • Provide alternative methods or tools for generating HIDX files on Linux, if available, or suggest open-source or cross-platform approaches.
  • Explicitly state platform requirements early in the prerequisites section to inform non-Windows users.
  • If no Linux support exists, recommend requesting or developing cross-platform tooling for HIDX file generation.
  • Include a section addressing Linux/macOS users, outlining any possible workarounds or future roadmap for parity.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/enable-stateful-affinity-built-in-connectors.md ...ectors/enable-stateful-affinity-built-in-connectors.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by providing detailed instructions and examples for Azure PowerShell, a Windows-centric tool, without offering equivalent examples for Linux-native tools (such as Azure CLI or Bash scripting). The troubleshooting and configuration sections rely exclusively on PowerShell commands, and there is no mention of Linux shell alternatives or cross-platform approaches. The order of presentation also places PowerShell before any Linux-friendly options, and no Linux-specific guidance is provided.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Include Bash script snippets for configuration tasks, especially for updating website configuration.
  • Explicitly mention that Azure CLI and REST API can be used from Linux, and provide step-by-step instructions.
  • Reorder sections so that cross-platform or Linux-friendly tools (Azure CLI, REST API) are presented before or alongside PowerShell.
  • Add troubleshooting steps and error handling examples for Azure CLI and Bash users.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-ibmi-apps-distributed-program-calls.md ...ctors/integrate-ibmi-apps-distributed-program-calls.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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) for generating required metadata files (HIDX). There are no mentions of Linux equivalents or alternatives, nor are there instructions or examples for Linux users. The prerequisites and setup steps assume a Windows environment, and all tool downloads and requirements are Windows-centric.
Recommendations
  • Provide information on whether the HIS Designer or equivalent tools are available for Linux or via cross-platform methods (e.g., .NET Core, containerized solutions).
  • If Linux support is not available, explicitly state this limitation and suggest possible workarounds (such as using a Windows VM or container on Linux).
  • Include instructions or examples for Linux users, such as how to generate HIDX files from a Linux environment, or how to interact with the connector from Linux-based Azure Logic Apps workflows.
  • Mention any open-source or third-party alternatives that could be used on Linux, if available.
  • Ensure parity in documentation by listing Linux prerequisites and setup steps alongside Windows instructions.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-cics-apps-ibm-mainframe.md ...ticles/connectors/integrate-cics-apps-ibm-mainframe.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing Microsoft Host Integration Server (HIS) tools, specifically the HIS Designer and Transaction Integrator, which are Windows-only applications. All prerequisites and setup instructions assume the use of Windows and .NET Framework, with no mention of Linux-compatible alternatives or cross-platform tooling. There are no examples or guidance for Linux users, nor is there any discussion of how to perform equivalent tasks on non-Windows platforms.
Recommendations
  • Explicitly state platform requirements and limitations for HIS Designer and related tools.
  • Provide guidance or alternatives for Linux users, such as any available cross-platform tools or methods for generating HIDX files.
  • If no Linux alternatives exist, suggest possible workarounds (e.g., using a Windows VM or container) and document the process.
  • Add examples or instructions for Linux environments where feasible, such as uploading HIDX files via CLI tools available on Linux.
  • Consider collaborating with product teams to develop or highlight cross-platform solutions for mainframe integration in Azure Logic Apps.
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: 2026-01-08 00:53
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 and prerequisites. The required 3270 Design Tool is only available for Windows (.NET Framework 4.8 required), with no mention of Linux-compatible alternatives or instructions. All setup and workflow examples assume use of the Azure portal, which is cross-platform, but do not provide command-line or automation examples that would be relevant for Linux users. There is no guidance for users who may wish to generate HIDX files or interact with the connector from Linux environments.
Recommendations
  • Provide information about Linux-compatible alternatives for generating HIDX files, or clarify if the 3270 Design Tool can be run under Wine/Mono or in a container.
  • Include instructions or examples for interacting with Azure Logic Apps and the IBM 3270 connector via CLI (Azure CLI, PowerShell Core, REST API), which can be used on Linux.
  • Explicitly state platform requirements and limitations for the 3270 Design Tool, and suggest workarounds for Linux users.
  • If no Linux-native tooling exists, consider providing a roadmap or guidance for cross-platform support, or recommend open-source alternatives if available.
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: 2026-01-08 00:53
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 the on-premises data gateway, which is primarily a Windows-only tool, and by instructing users to install the Oracle client on the same computer as the gateway. There are no examples or guidance for Linux environments, nor is there mention of Linux-compatible alternatives or installation instructions. All troubleshooting and error mitigation steps assume a Windows context (e.g., service names, installation patterns).
Recommendations
  • Include explicit instructions for connecting to Oracle Database from Linux environments, such as using self-hosted integration runtimes or other Linux-compatible gateways.
  • Provide Linux-specific installation steps for the Oracle client and clarify whether the gateway can be run on Linux (or note its limitations).
  • Add troubleshooting guidance relevant to Linux systems, including service management and common errors.
  • Mention Linux alternatives or workarounds early in the prerequisites section, not only after Windows instructions.
  • Ensure parity in examples by showing both Windows and Linux command-line or configuration steps where applicable.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/enable-stateful-affinity-built-in-connectors.md ...ectors/enable-stateful-affinity-built-in-connectors.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed Azure PowerShell instructions and troubleshooting, while omitting equivalent examples for Linux-native tools (such as Azure CLI, Bash, or scripting with curl). The PowerShell method is given a dedicated section, and no Linux/Unix shell examples are provided for updating configuration or troubleshooting. The focus on PowerShell and lack of cross-platform command-line guidance may disadvantage Linux users.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell instructions, including configuration updates and troubleshooting steps.
  • Provide Bash/curl examples for interacting with the Azure Resource Management API, showing how to PATCH the resource using standard Linux tools.
  • Explicitly mention that all command-line steps can be performed on Linux/macOS, and provide platform-agnostic instructions where possible.
  • Ensure troubleshooting steps are not PowerShell-specific and include guidance for Linux users.
  • Consider reordering or presenting PowerShell and CLI/Bash examples side-by-side to avoid a 'Windows-first' impression.
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-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) Designer and requiring Microsoft .NET Framework 4.8 for metadata generation, both of which are Windows-only tools. There are no mentions of Linux-compatible alternatives or instructions for Linux users. All setup and prerequisite instructions assume a Windows environment, and the documentation does not acknowledge or provide parity for Linux-based development workflows.
Recommendations
  • Explicitly state platform requirements and limitations (e.g., HIS Designer is Windows-only) at the start of the prerequisites section.
  • Provide guidance or workarounds for Linux users, such as using a Windows VM, Docker container, or remote desktop to access HIS Designer.
  • Investigate and document any cross-platform or open-source alternatives for generating HIDX files, or clarify if none exist.
  • Include a section addressing Linux/macOS users, outlining the steps they need to take or the limitations they will encounter.
  • If possible, advocate for or develop a cross-platform version of the HIS Designer tool, or provide a REST API for HIDX generation.
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-07-13 21:37
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 its exclusive reliance on Windows-only tooling (the 3270 Design Tool requires Microsoft .NET Framework 4.8), lack of mention of Linux-compatible alternatives, and by referencing App Service Environment v3 'with Windows plans only' without clarifying Linux support or alternatives. There are no Linux-specific instructions, examples, or tool recommendations, and the prerequisites and setup steps assume a Windows environment.
Recommendations
  • Provide information on whether the 3270 Design Tool can run on Linux (e.g., via Mono or Wine), or recommend Linux-compatible alternatives if available.
  • Clarify whether the Logic Apps Standard environment supports Linux plans and, if so, provide equivalent instructions for Linux users.
  • Include explicit notes or examples for Linux users, such as how to upload HIDX files or interact with Azure Logic Apps from Linux-based environments.
  • If no Linux alternatives exist for required tools, state this clearly and suggest possible workarounds or roadmap intentions for Linux support.
GitHub Create Pull Request
← Previous Page 2 of 4 Next →