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 51-75 of 90 flagged pages
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-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation assumes the on-premises data gateway and Oracle client are installed on a generic 'computer', but all troubleshooting, installation, and service references (e.g., PBIEgwService) are specific to Windows environments. There are no Linux-specific instructions, examples, or troubleshooting steps, and the gateway is implicitly treated as a Windows-only tool.
Recommendations
  • Explicitly state whether the on-premises data gateway is supported on Linux, and if so, provide installation and troubleshooting steps for Linux environments.
  • Include Linux-specific examples for installing the Oracle client and managing the gateway service (e.g., systemd commands).
  • When referencing services (like PBIEgwService), clarify that this is the Windows service name and provide the equivalent for Linux if available.
  • Add troubleshooting steps and common error resolutions for Linux users.
  • Avoid using generic terms like 'computer' when the instructions are Windows-specific; specify the OS or provide parallel instructions for both Windows and Linux.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-azureblobstorage.md ...s/connectors/connectors-create-api-azureblobstorage.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure portal (a web UI, but often associated with Windows-centric workflows), and by providing instructions and screenshots that assume use of the Azure portal UI. There is no mention of Linux command-line tools (such as Azure CLI or azcopy), nor are there any PowerShell or CLI examples, but the only non-portal tool mentioned is Visual Studio Code, which is cross-platform. However, all step-by-step instructions for finding connection strings, access keys, and configuring storage accounts are written in terms of navigating the Azure portal UI, which is more familiar to Windows users. There are no examples or instructions for performing equivalent tasks using the Azure CLI, Bash, or other Linux-native tools. Additionally, the documentation refers to App Service Environment v3 as 'Windows plans only' without clarifying Linux support or alternatives.
Recommendations
  • Add parallel instructions and examples for performing all key tasks (such as retrieving storage account keys, connection strings, and configuring networking/firewall rules) using the Azure CLI, which is available on Linux, macOS, and Windows.
  • Where screenshots are provided for the Azure portal, also provide equivalent CLI commands (e.g., az storage account show-connection-string, az storage account keys list, az storage container create, etc.).
  • Explicitly mention that Visual Studio Code is cross-platform and provide any Linux/macOS-specific setup notes if relevant.
  • Clarify whether App Service Environment v3 or other features are available or supported on Linux plans, and provide guidance for Linux users if there are differences.
  • Include a section or callout for Linux/macOS users, summarizing the parity of features and tools, and linking to relevant documentation for non-Windows environments.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-informix.md .../articles/connectors/connectors-create-api-informix.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a subtle Windows bias: it mentions 'IBM Informix for Windows running in Azure virtualization' as a cloud-based example before any mention of Linux, and references 'Windows (kerberos)' as an authentication type without clarifying Linux support. There are no explicit Linux examples or references to Linux-specific tools or authentication patterns, and the documentation does not clarify whether the on-premises data gateway or Informix connector works equally well on Linux systems.
Recommendations
  • Explicitly mention support for Linux-based Informix servers, both on-premises and in the cloud, alongside or before Windows examples.
  • Provide example connection strings and authentication patterns for Linux Informix deployments.
  • Clarify whether the on-premises data gateway can be installed and used on Linux hosts, and provide installation instructions if supported.
  • If authentication methods differ on Linux (e.g., Kerberos on Linux), document these options and provide guidance.
  • Include screenshots or walkthroughs that reference Linux environments, not just Windows.
  • Avoid listing Windows as the only or first example when describing supported platforms.
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-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation assumes the on-premises data gateway and Oracle client are installed on a generic 'computer', but all troubleshooting and operational guidance implicitly targets Windows environments. There are no Linux-specific instructions, examples, or troubleshooting steps. The only service mentioned by name is PBIEgwService, which is a Windows service. There is no mention of Linux installation, service management, or compatibility, and all links and references are Windows-centric.
Recommendations
  • Explicitly state whether the on-premises data gateway and Oracle client are supported on Linux, and if so, provide installation and configuration steps for Linux environments.
  • Include Linux-specific troubleshooting steps, such as how to check if the gateway service is running (e.g., using systemd or service commands), and how to install the Oracle client on Linux.
  • Mention Linux equivalents for service management (e.g., 'sudo systemctl restart gateway-service') alongside Windows instructions.
  • Clarify any platform limitations or differences in supported features between Windows and Linux.
  • Add screenshots or command-line examples from Linux environments where relevant.
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: 2025-07-08 04:23
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 referencing Windows-specific tools (such as certmgr.exe and PowerShell), focusing on Windows certificate stores, and omitting equivalent Linux instructions or examples. Certificate management and validation steps are described only for Windows environments, with no mention of Linux-based approaches or commands. The documentation also refers to App Service Environment v3 'with Windows-only' plans as a requirement for certain features, without discussing Linux alternatives or parity.
Recommendations
  • Provide equivalent Linux instructions for certificate management, such as using openssl or Linux certificate stores (e.g., /etc/ssl/certs).
  • Include Linux command-line examples (e.g., bash, openssl, keytool) alongside PowerShell and Windows tool references.
  • Clarify whether Linux-based App Service Environments or hosts are supported, and if not, explicitly state the limitation.
  • If features are Windows-only, explain why and offer guidance or workarounds for Linux users.
  • Reference cross-platform tools or approaches where possible, and avoid assuming the use of Windows by default.
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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed instructions and code examples for Azure PowerShell, a Windows-centric tool, without offering equivalent examples for Linux-native tools (such as Azure CLI, Bash, or REST via curl). The PowerShell method is given a dedicated section, and troubleshooting steps are also PowerShell-based. No Linux shell or cross-platform command-line examples are provided, and there is no mention of Linux-specific considerations or parity.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell instructions, including configuration updates and troubleshooting.
  • Provide REST API examples using curl or HTTPie, which are cross-platform and commonly used on Linux.
  • Explicitly mention that all management operations can be performed from Linux/macOS using Azure CLI or REST, and provide links or examples.
  • Include troubleshooting steps using Azure CLI or REST, not just PowerShell.
  • Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., avoid referencing Windows-only tools or paths).
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/file-system.md ...zure-docs/blob/main/articles/connectors/file-system.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. It explicitly states that the File System connector only supports Windows file systems and Windows operating systems, and all examples, prerequisites, and authentication methods are Windows-centric (e.g., Windows authentication, domain\username format, references to Windows domains, and App Service Environment v3 with Windows plans only). There are no examples, instructions, or even mentions of Linux file systems or how to connect to non-Windows file shares. Linux users are not addressed, and no alternatives or workarounds are suggested.
Recommendations
  • Clearly state early in the documentation that Linux file systems are not supported, and provide a roadmap or link to feature requests if Linux support is planned.
  • If partial Linux support exists (e.g., via SMB/CIFS shares from Linux servers), document the requirements and limitations, and provide Linux-specific examples.
  • Offer alternative approaches for Linux environments, such as using SFTP, NFS, or other connectors that support Linux file systems, and link to relevant documentation.
  • Include a section comparing Windows and Linux support, so users can quickly determine applicability.
  • If Linux support is not planned, suggest community or third-party solutions for Linux file system integration.
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-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by providing a PowerShell script as the only automation example for enabling CORS on Azure Blob Storage, and by referencing Windows-centric tools (Azure Portal, Azure Storage Explorer) without mentioning Linux CLI alternatives. There are no explicit Linux or cross-platform command-line examples (such as Azure CLI or Bash scripts) for key tasks, and the PowerShell script is not accompanied by a Linux equivalent.
Recommendations
  • Provide Azure CLI (az storage cors add ...) and Bash script examples alongside the PowerShell script for enabling CORS, ensuring parity for Linux and macOS users.
  • Explicitly mention that Azure Storage Explorer is cross-platform, and provide download links for Linux and macOS versions.
  • Include instructions for performing all tasks (such as uploading Swagger files, setting CORS, retrieving blob URLs) using the Azure CLI and/or REST API, not just the Azure Portal or PowerShell.
  • Add a note clarifying that all steps can be performed on Windows, Linux, or macOS, and link to relevant cross-platform documentation where appropriate.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-sqlazure.md .../articles/connectors/connectors-create-api-sqlazure.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific environments (e.g., App Service Environment v3 (Windows plans only)), authentication methods (Windows Authentication), and tools (on-premises data gateway, which is primarily a Windows service). There are no examples or explicit instructions for Linux-based environments, nor are Linux authentication or deployment scenarios discussed. The documentation assumes the use of the Azure portal and Visual Studio Code, but does not mention Linux-specific considerations or alternatives. Windows authentication is described in detail, but there is no mention of Kerberos or other Linux-compatible authentication methods. The 'on-premises data gateway' requirement for on-prem SQL is a Windows-only solution, with no Linux alternative or workaround provided.
Recommendations
  • Add explicit notes and examples for connecting from Linux-based environments, including any differences in connector support or authentication flows.
  • Document alternatives to the on-premises data gateway for Linux (such as self-hosted integration runtimes or other cross-platform options, if available).
  • If Windows Authentication is only supported via the data gateway (which is Windows-only), clarify this limitation and suggest Linux-compatible authentication methods (e.g., SQL Server Authentication, Azure AD authentication).
  • Include sample connection strings and walkthroughs for Linux-based deployments (e.g., running Logic Apps Standard on Linux App Service plans, if supported).
  • Review all tool and environment references to ensure Linux parity is addressed, or clearly state when features are Windows-only.
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-07-08 04:23
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 by exclusively referencing Windows-based tools (such as Microsoft Host Integration Server and HIS Designer, which require .NET Framework 4.8 and Visual Studio), and does not mention or provide any Linux-compatible alternatives or examples. The setup and screenshots are all based on Windows environments, and there is no guidance for users on Linux or macOS platforms.
Recommendations
  • Provide information on whether the HIS Designer and related tooling are available or supported on Linux or macOS, or explicitly state if they are Windows-only.
  • If possible, suggest or develop cross-platform alternatives for generating HIDX files or parsing host files, or provide guidance for using the connector from non-Windows environments.
  • Include example workflows or instructions that can be followed from Linux or macOS, such as using Azure CLI, VS Code (cross-platform), or other non-Windows tools.
  • Clarify any prerequisites that are Windows-specific, and offer workarounds or alternatives for Linux users where feasible.
  • Add screenshots or walkthroughs using cross-platform tools or interfaces, not just Visual Studio or Windows-only applications.
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-08 04:23
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 Windows-based tools (Host Integration Server Designer, which requires .NET Framework 4.8) for generating required metadata files. There are no Linux or cross-platform alternatives mentioned for these critical steps, and the prerequisites and setup instructions assume a Windows environment. No Linux-specific guidance or parity is provided.
Recommendations
  • Provide information about whether the Host Integration Server Designer or equivalent tooling is available for Linux or via cross-platform means (e.g., .NET Core, containerized solutions).
  • If no Linux-native tooling exists, explicitly state this limitation and suggest possible workarounds (such as using a Windows VM or container).
  • Include Linux-specific instructions or examples where possible, especially for steps like file management, installation, and workflow integration.
  • Consider developing or recommending cross-platform tools for generating HIDX files to improve accessibility for non-Windows users.
  • Clarify in the prerequisites section that the current tooling is Windows-only, and provide links or guidance for Linux users to set up the necessary environment.
GitHub Create Pull Request
Connectors https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-db2.md .../main/articles/connectors/connectors-create-api-db2.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias. It references 'IBM DB2 for Windows running in Azure virtualization' as the primary example of a cloud DB2 database, and in several places, Windows-specific terminology or authentication (e.g., 'Windows (Kerberos)') is mentioned. Username length for DB2 for Windows is highlighted (30 bytes), while Linux/UNIX is only briefly mentioned (8 bytes) and never prioritized. There are no Linux-specific examples, screenshots, or instructions, and the documentation does not mention Linux tools or patterns for connecting to DB2, nor does it provide parity in examples or troubleshooting for Linux environments.
Recommendations
  • Provide explicit examples and screenshots for connecting to DB2 on Linux (and UNIX) servers, not just Windows.
  • When listing supported platforms or username formats, avoid listing Windows first or giving it more detail than Linux/UNIX.
  • Include Linux authentication options and clarify any differences or requirements for Linux-based DB2 servers.
  • Mention Linux/UNIX as equally valid cloud or on-premises DB2 deployment targets, not just Windows.
  • If there are Linux-specific considerations (such as case sensitivity, authentication, or firewall rules), document them.
  • Ensure parity in troubleshooting steps and connection string examples for both Windows and Linux environments.
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: 2025-07-08 04:23
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) and the HIS Designer for Logic Apps, which are Windows-only tools. All setup and prerequisite instructions assume the use of these Windows-based tools, with no mention of Linux-compatible alternatives or workflows. There are no examples or guidance for Linux users, and the documentation does not clarify whether the required tools or processes are available or supported on non-Windows platforms.
Recommendations
  • Explicitly state platform requirements and limitations, including whether HIS Designer and related tools are Windows-only.
  • If Linux-compatible tools or workflows exist (e.g., command-line utilities, cross-platform designer tools, or REST APIs), provide equivalent instructions and examples for Linux users.
  • If no Linux alternatives exist, acknowledge this limitation and suggest possible workarounds (such as using a Windows VM or container).
  • Consider collaborating with product teams to develop or document Linux-compatible tooling or processes for cross-platform parity.
  • Add a section addressing common questions for non-Windows users, including guidance on how to proceed if they are developing from Linux or macOS environments.
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-14 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 by exclusively referencing Windows-only tools (Host Integration Server Designer, which requires .NET Framework 4.8), and by describing integration patterns historically focused on Windows environments. There are no Linux/macOS alternatives or instructions, and the prerequisites and setup steps assume access to Windows software. This creates friction for Linux/macOS users who cannot natively run the required HIS Designer tool or .NET Framework.
Recommendations
  • Provide information about running HIS Designer on Linux/macOS, such as via Wine or virtual machines, or clarify if this is unsupported.
  • Offer alternative metadata generation methods that work on Linux/macOS, if available.
  • Explicitly state platform requirements and limitations for HIS Designer and .NET Framework.
  • If possible, develop and document a cross-platform tool for generating HIDX files.
  • Include notes or examples for Linux/macOS users regarding workflow setup and file upload.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing Azure PowerShell examples and troubleshooting steps, referencing Windows-centric tools and patterns, and omitting equivalent Linux/macOS CLI (e.g., Azure CLI, Bash) instructions. The ordering and emphasis on PowerShell further reinforce the Windows-first approach, leaving Linux/macOS users without direct guidance for completing key configuration tasks.
Recommendations
  • Add Azure CLI (az) examples for updating website configuration and troubleshooting, with explicit Bash syntax.
  • Include notes or sections for Linux/macOS users, clarifying cross-platform alternatives to PowerShell commands.
  • Reorder examples to present cross-platform methods (Azure portal, REST API, Azure CLI) before Windows-specific tools.
  • Reference platform-agnostic tools and avoid assuming PowerShell as the default automation environment.
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-14 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-based tools (Host Integration Server Designer, .NET Framework 4.8) for generating required metadata files, 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. This creates friction for non-Windows users attempting to integrate CICS programs with Azure Logic Apps.
Recommendations
  • Clarify whether HIS Designer and related tools are available or supported on Linux/macOS, or provide alternatives if possible.
  • If the tools are Windows-only, explicitly state this limitation and suggest workarounds (such as using a Windows VM or container).
  • Add notes or examples for Linux/macOS users, including any relevant steps for uploading files or interacting with Azure Logic Apps from those platforms.
  • Consider developing or referencing cross-platform tools for generating HIDX files, or provide a REST API for metadata generation.
  • Reorder documentation to present platform-neutral steps first, and clearly indicate where platform-specific requirements exist.
GitHub Create Pull Request
Connectors Built-in connector overview ...s/azure-docs/blob/main/articles/connectors/built-in.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation mentions the ability to execute PowerShell scripts as a built-in action for Standard workflows, but does not mention or provide parity for Linux/macOS shell scripting (e.g., Bash). This suggests a bias toward Windows scripting environments in the 'Run code from workflows' section.
Recommendations
  • Add support and documentation for running Bash scripts or other Linux/macOS shell scripts as built-in actions, if supported.
  • If Bash or other shells are not supported, clarify this limitation explicitly for non-Windows users.
  • Provide examples or links for cross-platform scripting alternatives where possible.
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-14 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 page demonstrates a notable Windows bias. Certificate management instructions and examples are almost exclusively Windows-centric, referencing Windows Certificate Manager (certmgr.exe), Windows certificate stores, and PowerShell scripts for certificate inspection. The prerequisite steps for on-premises gateway installation require .NET Framework, a Windows-only technology. No Linux or macOS equivalents or instructions are provided for certificate management, gateway installation, or troubleshooting, and all examples use Windows tools first or exclusively.
Recommendations
  • Provide Linux/macOS equivalents for certificate management, such as using openssl, keytool, or Linux certificate stores.
  • Include instructions for installing and configuring the on-premises data gateway on Linux (if supported), or clarify Windows-only requirements.
  • Add troubleshooting steps and examples for Linux environments, including how to inspect certificate stores and manage certificates.
  • Where PowerShell is referenced, offer alternative bash or shell commands for Linux/macOS users.
  • Clearly indicate platform limitations and offer guidance for cross-platform scenarios.
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-14 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. In the section on hosting Swagger files in Azure Storage, the only automation script provided is a PowerShell script, which is native to Windows. The Azure portal is referenced as the primary UI for configuration, and Azure Storage Explorer (a cross-platform tool) is mentioned, but only after the portal and PowerShell. No Linux/macOS CLI or shell script examples are given for enabling CORS or uploading files, and no mention is made of using Azure CLI or REST API for these tasks.
Recommendations
  • Provide equivalent Azure CLI or Bash shell examples for enabling CORS and uploading Swagger files to Azure Storage.
  • Mention Azure CLI and REST API as alternatives to PowerShell and the Azure portal for configuration tasks.
  • Ensure that cross-platform tools (e.g., Azure Storage Explorer, Azure CLI) are presented before or alongside Windows-specific tools.
  • Add explicit Linux/macOS instructions or notes where tasks can be completed using non-Windows environments.
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-14 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, which is a Windows-only tool requiring .NET Framework 4.8. There are no mentions of Linux or macOS alternatives for generating the required HIDX metadata file, nor are there instructions or examples for non-Windows environments. The prerequisites and setup steps assume access to Windows tooling, creating friction for Linux/macOS users.
Recommendations
  • Explicitly state the platform requirements for HIS Designer and HIDX file generation.
  • 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 roadmap for future support.
  • Add a section clarifying that the rest of the workflow (Azure Logic Apps, connector usage) is platform-agnostic after the HIDX file is created.
  • Consider providing sample HIDX files for testing so non-Windows users can follow the workflow steps without needing to generate their own.
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-13 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. In the section on hosting Swagger files in Azure Storage, the only script-based automation example provided is a PowerShell script, which is Windows-centric. The Azure portal is referenced as the primary UI for configuration steps, and Azure Storage Explorer is mentioned as an alternative, but no Linux/macOS CLI or Bash examples are given. The PowerShell script is linked before any mention of cross-platform automation, and there are no instructions for using Azure CLI or Bash to enable CORS or upload files, which would benefit Linux/macOS users.
Recommendations
  • Add Azure CLI and Bash examples for enabling CORS and uploading Swagger files to blob storage.
  • Explicitly mention that Azure Storage Explorer is cross-platform and provide download links for Linux/macOS.
  • Include instructions for performing all steps via CLI (Azure CLI, Bash) for users who do not use Windows or PowerShell.
  • Add notes or links to documentation for Linux/macOS users on how to perform equivalent tasks.
GitHub Create Pull Request
Connectors Built-in connector overview ...s/azure-docs/blob/main/articles/connectors/built-in.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation page for Azure Logic Apps built-in connectors is generally cross-platform and does not show overt Windows bias in its connector descriptions or workflow guidance. However, in the 'Run code from workflows' section, PowerShell is listed as a supported script language for inline code execution, but there is no mention of Bash or other Linux-native scripting languages. This could create friction for Linux/macOS users who may prefer Bash or similar shells over PowerShell.
Recommendations
  • Add support for Bash or other Linux-native scripting languages in inline code actions, or clarify if only PowerShell is supported and why.
  • Provide examples or documentation links for running Linux shell scripts from Logic Apps workflows, if possible.
  • Explicitly state platform compatibility for script actions, so users know which operating systems and runtimes are supported.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates a notable Windows bias, especially in certificate management and troubleshooting sections. Windows tools (e.g., certmgr.exe, PowerShell scripts) are referenced exclusively for certificate operations, and instructions for adding certificates to the Trusted Root CA Store are Windows-centric. There is no mention of Linux or macOS equivalents for certificate management, nor are cross-platform alternatives provided. The use of PowerShell and references to Windows-specific environments (App Service Environment v3 with Windows-only plans) further reinforce the bias.
Recommendations
  • Provide equivalent instructions for Linux and macOS users, such as using openssl, update-ca-certificates, or keytool for certificate management.
  • Include examples of how to view and add certificates on Linux/macOS hosts, e.g., referencing /etc/ssl/certs or using platform-native tools.
  • Clarify whether Azure-hosted logic apps can run on Linux and, if so, how certificate management differs.
  • Where PowerShell is used, offer bash or shell script alternatives for Linux/macOS environments.
  • Explicitly state platform limitations and provide guidance for non-Windows users.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples use Azure PowerShell, with no mention of Azure CLI or bash alternatives that would be more familiar to Linux/macOS users. Troubleshooting and configuration steps reference PowerShell exclusively. The order of presentation places Windows-centric tools (Azure portal, PowerShell) before any cross-platform or Linux-friendly options. There are no Linux-specific instructions or examples, and no mention of how to perform equivalent tasks using Linux-native tools.
Recommendations
  • Add Azure CLI examples for all configuration steps, including updating website configuration and troubleshooting.
  • Explicitly mention that Azure CLI and REST API methods are cross-platform and provide sample bash commands.
  • Reorder sections so that cross-platform methods (REST API, Azure CLI) are presented before Windows-specific tools like PowerShell.
  • Include troubleshooting steps using Azure CLI or REST API, not just PowerShell.
  • Add notes clarifying which tools are available on Linux/macOS and how to install them if needed.
GitHub Create Pull Request
Connectors Connect to Oracle Database ...les/connectors/connectors-create-api-oracledatabase.md
Medium 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 assumes installation of the on-premises data gateway and Oracle client on a 'computer' without specifying platform, but all references and troubleshooting steps (e.g., PBIEgwService) are specific to the Windows version of the gateway. There are no instructions or examples for installing or running the gateway or Oracle client on Linux or macOS, nor is there mention of platform-specific differences.
Recommendations
  • Explicitly state supported operating systems for the on-premises data gateway and Oracle client.
  • If Linux/macOS are supported, provide installation instructions and troubleshooting steps for those platforms.
  • If only Windows is supported, clarify this early in the prerequisites section.
  • Include examples or notes for Linux/macOS users regarding alternative approaches or limitations.
GitHub Create Pull Request
← Previous Page 3 of 4 Next →