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 76-90 of 90 flagged pages
Connectors
Access IMS Programs from Standard Workflows
...rticles/connectors/integrate-ims-apps-ibm-mainframe.md
Medium Priority
View Details →
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, .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 could create friction for non-Windows users attempting to integrate IMS programs with Azure Logic Apps.
Recommendations
- Clarify whether the Host Integration Server Designer is available or supported on Linux/macOS, or provide alternative tooling for these platforms.
- If only Windows is supported, explicitly state this limitation and suggest possible workarounds (e.g., using a Windows VM or container).
- Provide examples or guidance for Linux/macOS users on how to generate and upload HIDX files, if possible.
- Consider developing or recommending cross-platform tools for metadata generation in future releases.
Create Pull Request
Connectors
Access COBOL & RPG Programs from Standard Workflows
...ctors/integrate-ibmi-apps-distributed-program-calls.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft tools (Host Integration Server Designer, .NET Framework 4.8) required for metadata generation, with no mention of Linux or macOS alternatives. All setup instructions and prerequisites assume a Windows environment, and there are no examples or guidance for non-Windows users. This creates friction for Linux/macOS users attempting to integrate COBOL/RPG programs with Azure Logic Apps.
Recommendations
- Provide information on whether HIS Designer can be run on Linux/macOS (e.g., via Wine, Mono, or containerization), or clarify its platform limitations.
- Offer alternative methods or tools for generating HIDX files on Linux/macOS, if available.
- Explicitly state platform requirements and limitations for key tooling in the prerequisites section.
- If possible, develop and document a cross-platform metadata generation tool or workflow.
- Include troubleshooting or workaround guidance for non-Windows users.
Connectors
Integrate and manage security operations & Microsoft Graph Security
...ecurity-operations-create-api-microsoft-graph-security.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references the Azure portal and Logic App Designer, which are primarily accessed via web browsers and are platform-agnostic. However, all step-by-step instructions and examples assume use of the Azure portal, with no mention of Linux/macOS-specific tooling, CLI, or automation options. There are no examples using Azure CLI, Bash, or other Linux-native tools, nor are alternatives to the portal (such as az logicapp commands) discussed. Windows-centric terms (e.g., Outlook connector, Power Automate, Power Apps) are mentioned before any Linux alternatives, and no Linux/macOS-specific guidance is provided.
Recommendations
- Add examples using Azure CLI (az logicapp ...) for creating and managing Logic Apps and Microsoft Graph Security connections.
- Include instructions for performing key tasks (e.g., authentication, connector setup) via command line or automation scripts suitable for Linux/macOS users.
- Mention cross-platform alternatives to Outlook connector (e.g., SMTP, SendGrid) for sending alerts.
- Explicitly state that all steps can be performed from any OS via browser, and clarify any OS-specific requirements if present.
- Provide parity in examples, showing both portal and CLI/script approaches side by side.
Connectors
Enable stateful mode for stateless built-in connectors
...ectors/enable-stateful-affinity-built-in-connectors.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing Azure PowerShell examples for command-line configuration, referencing Windows-centric tools, and omitting equivalent instructions for Linux/macOS users (such as Azure CLI or REST API via curl). The troubleshooting section also relies solely on PowerShell. While the Azure portal and REST API are cross-platform, command-line automation is presented only for Windows environments.
Recommendations
- Add Azure CLI examples for all PowerShell commands, ensuring Linux/macOS users have parity.
- Include REST API usage examples with curl or similar cross-platform tools.
- Present command-line examples in parallel (PowerShell and CLI), or show CLI first to avoid Windows-first ordering.
- Clarify that Azure CLI and REST API methods work on all platforms, and link to relevant documentation.
- Provide troubleshooting steps using CLI or REST API, not just PowerShell.
Connectors
Integrate and manage security operations & Microsoft Graph Security
...ecurity-operations-create-api-microsoft-graph-security.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on Azure Logic Apps and Microsoft Graph Security integration, referencing Microsoft-specific tools and workflows (Azure portal, Outlook connector, Microsoft Entra, etc.) without mentioning or providing examples for Linux-based workflows, CLI tools, or cross-platform alternatives. All examples and instructions assume use of the Azure portal and Microsoft ecosystem, with no parity for Linux users or non-Windows environments.
Recommendations
- Include examples for using Azure Logic Apps and Microsoft Graph Security from Linux environments, such as via Azure CLI, REST API, or cross-platform SDKs.
- Mention and provide instructions for accessing and managing Logic Apps and Graph Security using non-GUI tools (e.g., Azure CLI, PowerShell Core on Linux, Bash scripts).
- Add references or links to documentation for Linux users, such as how to authenticate with Microsoft Entra from Linux, or how to send notifications using non-Outlook email clients.
- Ensure that examples and screenshots are not exclusively from the Azure portal, and provide parity for command-line or API-based workflows.
- Explicitly state platform requirements and alternatives for users who do not use Windows or the Azure portal.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-integrate-security-operations-create-api-microsoft-graph-security.md
...ecurity-operations-create-api-microsoft-graph-security.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal and Microsoft-centric tools (Logic Apps, Entra, Outlook, Power Automate, Power Apps) without mentioning Linux-compatible alternatives or CLI-based workflows. All examples and instructions assume use of the Azure portal (typically accessed via a browser on Windows), and there are no references to Linux tools, shell commands, or cross-platform automation approaches. No PowerShell-specific examples are present, but the absence of Linux or CLI examples creates an implicit bias.
Recommendations
- Add equivalent instructions for using Azure Logic Apps and Microsoft Graph Security connector via Azure CLI, which is cross-platform and works on Linux.
- Include examples or references for managing security operations using REST API calls or automation scripts (e.g., Bash, curl) that can be run on Linux systems.
- Mention that the Azure portal and Logic Apps Designer are accessible from any OS with a supported browser, and clarify platform independence.
- Provide links or guidance for Linux users on installing and using Azure CLI or other cross-platform tools to achieve the same workflows.
- Where possible, include sample workflows or automation scripts for Linux environments alongside portal-based instructions.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-integrate-security-operations-create-api-microsoft-graph-security.md
...ecurity-operations-create-api-microsoft-graph-security.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal and Microsoft-centric tools and workflows, with no mention of Linux alternatives or cross-platform CLI options. All examples and instructions assume usage of the Azure portal (typically accessed via a web browser on Windows) and do not provide guidance for Linux users, such as using Azure CLI, REST API, or other platform-agnostic tools. There are no PowerShell-specific examples, but the overall workflow is tightly coupled to Microsoft cloud services and their default interfaces, which are most commonly used on Windows.
Recommendations
- Add instructions and examples for using Azure CLI and REST API to create and manage Logic Apps and Microsoft Graph Security connectors, which are platform-agnostic and work on Linux, macOS, and Windows.
- Include explicit notes or sections for Linux users, such as how to authenticate and manage resources from Linux environments.
- Provide sample workflows or scripts that can be executed from Linux shells (e.g., Bash) for common tasks described in the documentation.
- Reference cross-platform tools and interfaces (such as VS Code, Azure CLI, or direct API calls) alongside or before Windows-centric tools like the Azure portal.
- Clarify that the Azure portal is accessible from any OS via a web browser, but also highlight alternative methods for users who prefer command-line or automated approaches.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-azureblobstorage.md
...s/connectors/connectors-create-api-azureblobstorage.md
Medium Priority
View Details →
Detected Bias Types
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.
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
Medium Priority
View Details →
Detected Bias Types
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.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-create-api-informix.md
.../articles/connectors/connectors-create-api-informix.md
Medium Priority
View Details →
Detected Bias Types
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.
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
Medium Priority
View Details →
Detected Bias Types
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.
Connectors
Integrate and manage security operations & Microsoft Graph Security
...ecurity-operations-create-api-microsoft-graph-security.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references the Azure portal and Logic App Designer, which are primarily accessed via a web browser and are platform-agnostic. However, there is a subtle Windows bias: all step-by-step instructions and examples assume use of the Azure portal (often associated with Windows environments), and there are no references to Linux/macOS-specific tools, CLI workflows, or alternative approaches. No PowerShell or Windows-only tools are mentioned, but the lack of CLI or cross-platform examples may create friction for Linux/macOS users who prefer or require non-GUI workflows.
Recommendations
- Add equivalent instructions for using Azure CLI or Azure PowerShell (which is cross-platform) to create and manage Logic Apps and Microsoft Graph Security connections.
- Include examples for managing Logic Apps and connectors via REST API or automation scripts, which are platform-neutral.
- Explicitly state that all portal-based steps can be performed from any OS with a supported browser.
- Provide links or references to Linux/macOS setup guides for Azure development.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation page for Azure Logic Apps built-in connectors is generally cross-platform and avoids explicit Windows bias in its connector descriptions and workflow examples. However, in the 'Run code from workflows' section, PowerShell is listed as a supported scripting language for inline code execution, but there is no mention of Bash or other Linux-native scripting languages. This may suggest a slight bias towards Windows/PowerShell environments for custom code execution within workflows.
Recommendations
- Add examples or documentation for running Bash scripts or other Linux-native scripting languages in workflows, if supported.
- Clarify whether inline code actions support Linux shell scripts, and provide guidance for Linux users.
- Ensure parity in scripting language support and documentation between Windows (PowerShell) and Linux (Bash, sh, etc.) environments.
- If PowerShell is the only supported shell, explicitly state this and provide rationale, or roadmap for Linux shell support.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/connectors-native-recurrence.md
...in/articles/connectors/connectors-native-recurrence.md
Low Priority
View Details →
Detected Bias Types
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.
Connectors
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/connectors/built-in.md
...s/azure-docs/blob/main/articles/connectors/built-in.md
Low Priority
View Details →
Detected Bias Types
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.