Connectors

38
Total Pages
22
Linux-Friendly Pages
16
Pages with Bias
42.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (22)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-informix.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-azureblobstorage.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-oracledatabase.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-3270-apps-ibm-mainframe.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-ims-apps-ibm-mainframe.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/enable-stateful-affinity-built-in-connectors.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-ims-apps-ibm-mainframe.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-ibmi-apps-distributed-program-calls.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) and the HIS Designer for Logic Apps, which are Windows-only tools. The only prerequisite for the HIS Designer is Microsoft .NET Framework 4.8, which is not natively available on Linux. There are no examples or instructions for Linux or cross-platform environments, nor are alternative tools or methods mentioned for non-Windows users.
Recommendations:
  • Provide information on whether the HIS Designer for Logic Apps can be used on Linux (e.g., via Mono, .NET Core, or Wine), or explicitly state if it is Windows-only.
  • If possible, offer alternative methods or tools for generating the required HIDX metadata file on Linux or macOS.
  • Include examples or workflow steps that can be performed from Linux environments, or clarify any platform limitations.
  • Mention any future plans or workarounds for non-Windows users, such as containerized versions of the HIS Designer or REST APIs for metadata generation.
  • Clearly indicate in the prerequisites section that the current tooling is Windows-specific, and provide guidance for users on other platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-cics-apps-ibm-mainframe.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/built-in.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy
Summary:
The documentation page is generally neutral and cross-platform, focusing on Azure Logic Apps built-in connectors without favoring Windows or Linux. However, in the 'Run code from workflows' section, PowerShell script execution is specifically called out as a supported option (alongside JavaScript and C#), which may indicate a slight Windows bias, as PowerShell is more commonly associated with Windows environments. There are no explicit Windows-only tools, examples, or patterns, and Linux equivalents are not omitted, but the mention of PowerShell without a corresponding Bash or Linux shell scripting example could be seen as a minor bias.
Recommendations:
  • Add examples or documentation for running Bash or other Linux shell scripts as inline code or via connectors, if supported.
  • Clarify whether PowerShell script execution is cross-platform (i.e., works with PowerShell Core on Linux) or Windows-only.
  • If only PowerShell is supported for scripting, consider explaining the rationale and providing guidance for Linux users.
  • Ensure that any scripting or code execution features highlight both Windows and Linux options where possible, or explicitly state platform limitations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-azureblobstorage.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation demonstrates a Windows bias primarily through exclusive references to the Azure portal (a web UI, but often associated with Windows-centric workflows) and the absence of Linux-specific instructions or command-line examples. The only development tool mentioned for local workflow creation is Visual Studio Code, which is cross-platform, but there are no references to Linux-native tools, shell commands, or CLI-based approaches. Additionally, in the connector technical reference, App Service Environment v3 is specified as 'Windows plans only' without mention of Linux plans or parity.
Recommendations:
  • Include explicit instructions and examples for using the Azure CLI and/or Azure PowerShell on Linux and macOS, especially for common tasks like retrieving storage account keys, connection strings, and managing resources.
  • Clarify whether all features and connectors are available on Linux-based App Service plans, and provide guidance for Linux users if there are differences.
  • Add references to Linux-native tools (e.g., az CLI, bash scripts) for managing Azure resources, alongside or instead of Azure portal steps.
  • Where screenshots are used, consider including examples from Linux environments or terminal-based workflows.
  • Explicitly state OS requirements or limitations for features that are Windows-only, and provide alternatives or workarounds for Linux users where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-oracledatabase.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-mq.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-db2.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-informix.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation demonstrates a mild Windows bias by referencing 'IBM Informix for Windows running in Azure virtualization' as the primary cloud-based example and by listing 'Windows (kerberos)' as an authentication type without mentioning Linux equivalents. There is no explicit Linux example or mention of Linux authentication mechanisms, and the documentation does not clarify cross-platform compatibility or provide parity in examples for Linux-based Informix deployments.
Recommendations:
  • Explicitly mention support for Linux-based Informix servers, both on-premises and in the cloud.
  • Provide example connection strings and scenarios for Informix running on Linux, not just Windows.
  • Clarify authentication options for Linux deployments (e.g., PAM, LDAP, or other mechanisms) alongside Windows (kerberos).
  • Ensure that screenshots and example values do not imply Windows-only environments (e.g., use generic hostnames or include Linux hostnames).
  • Add a note or section about cross-platform compatibility, including any differences or considerations for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-sqlazure.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-native-http-swagger.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-native-recurrence.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools
Summary:
The documentation is generally neutral and cross-platform, as it focuses on Azure Logic Apps' web-based designer and JSON definitions. However, there is a subtle Windows bias in the reference to time zones: the documentation links to a Microsoft Docs page listing Windows time zone identifiers and refers to 'Pacific Standard Time' as an example, which is a Windows-specific time zone ID. No Linux or IANA time zone equivalents are mentioned, and the only time zone reference is to a Windows-centric resource.
Recommendations:
  • When referencing time zones, mention both Windows time zone IDs and IANA/Olson time zone names, or clarify which are supported by Azure Logic Apps.
  • Provide a link or reference to IANA time zone documentation (e.g., https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) and clarify if only Windows time zones are accepted.
  • In examples, consider using UTC or ISO 8601 time zone formats, or explicitly note the mapping between Windows and IANA time zones for cross-platform clarity.
  • Add a note for Linux/macOS users that Windows time zone IDs may differ from those on their systems, and provide guidance or a mapping table if appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/file-system.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-3270-apps-ibm-mainframe.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by requiring the use of the 3270 Design Tool, which is dependent on Microsoft .NET Framework 4.8 (Windows-only), and by not mentioning or providing alternatives for Linux users. There are no Linux-compatible tools or instructions, nor are there any examples or guidance for Linux environments.
Recommendations:
  • Provide information about the platform compatibility of the 3270 Design Tool. If it is Windows-only, state this explicitly and suggest workarounds for Linux users (e.g., using Wine, or running in a Windows VM).
  • If possible, offer or reference a cross-platform or Linux-native tool for generating HIDX files.
  • Include explicit instructions or examples for Linux users, such as how to upload files to Azure from Linux (e.g., using Azure CLI or azcopy), and clarify that the Azure portal is web-based and accessible from any OS.
  • Mention any limitations or requirements for Linux users upfront in the prerequisites section.
  • If the connector or related tools are only supported on Windows-based App Service plans, clarify this and provide guidance for Linux-based plans or environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/enable-stateful-affinity-built-in-connectors.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/integrate-host-files-ibm-mainframe.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.