Logic Apps

226
Total Pages
153
Linux-Friendly Pages
73
Pages with Bias
32.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

339 issues found
Showing 1-25 of 339 flagged pages
Logic Apps Connect to on-premises data sources ...rticles/logic-apps/connect-on-premises-data-sources.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation demonstrates a Windows bias by referencing the on-premises data gateway installation on a 'local computer' (which, in Microsoft context, is almost always Windows), mentioning Windows service account management, and providing PowerShell-based automation links for gateway administration. There are no explicit Linux/macOS installation instructions, examples, or tooling references, and the only automation examples are PowerShell-based, which is Windows-centric.
Recommendations
  • Explicitly state platform requirements for the on-premises data gateway, including whether Linux/macOS are supported for installation.
  • If Linux/macOS are supported, provide installation instructions and troubleshooting steps for those platforms.
  • Offer automation examples using cross-platform tools (e.g., Azure CLI, REST API) in addition to PowerShell.
  • Clarify service management instructions for non-Windows platforms (e.g., systemd for Linux).
  • Ensure screenshots and examples do not implicitly assume Windows-only environments.
GitHub Create Pull Request
Logic Apps Create and run .NET code from Standard workflows ...rticles/logic-apps/create-run-custom-code-functions.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by explicitly stating that the custom functions capability is only available in Visual Studio Code running on Windows. There are no instructions, examples, or troubleshooting steps for Linux or macOS users. All workflow creation, debugging, and deployment steps assume a Windows environment, leaving non-Windows users unable to complete the described tasks.
Recommendations
  • Clearly state Windows-only limitations at the top of the page and in prerequisites.
  • Provide a roadmap or timeline for Linux/macOS support, if possible.
  • Offer alternative approaches or workarounds for Linux/macOS users, such as using remote Windows environments or containers.
  • Add explicit troubleshooting and environment setup notes for non-Windows platforms, or link to relevant resources.
  • When Linux/macOS support becomes available, update all examples and instructions to include those platforms.
GitHub Create Pull Request
Logic Apps Install on-premises data gateway for logic app workflows ...gic-apps/install-on-premises-data-gateway-workflows.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for installing the on-premises data gateway for Azure Logic Apps demonstrates a notable Windows bias. The installation process is described exclusively in terms of running a Windows installer, with screenshots and instructions referencing Windows UI elements. Gateway management is linked to PowerShell cmdlets, a Windows-centric automation tool, and the gateway is described as running as a Windows service. There are no examples, instructions, or references for installing or operating the gateway on Linux or macOS systems, nor are alternative tools or patterns mentioned for non-Windows platforms.
Recommendations
  • Explicitly state platform support: Clarify whether the on-premises data gateway is Windows-only, or provide instructions for Linux/macOS if supported.
  • If Linux/macOS support exists, add installation steps, screenshots, and troubleshooting for those platforms.
  • If only Windows is supported, add a prominent note at the top of the page to inform non-Windows users.
  • Provide cross-platform automation options (e.g., REST API, CLI) in addition to PowerShell, or mention alternatives for Linux/macOS users.
  • Reference or link to any available Linux/macOS gateway alternatives or workarounds, if applicable.
GitHub Create Pull Request
Logic Apps B2B enterprise integration workflows ...gic-apps/logic-apps-enterprise-integration-overview.md
High 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 recommending Visual Studio 2019 (a Windows-only tool) and the Microsoft Azure Logic Apps Enterprise Integration Tools Extension for creating maps and schemas. There is no mention of Linux/macOS alternatives or cross-platform tooling for these critical tasks. Additionally, troubleshooting steps reference Windows-specific registry edits and DPI settings. While Visual Studio Code is mentioned for managing and deploying logic apps, the creation of essential B2B artifacts (maps and schemas) is tied to Windows-only software.
Recommendations
  • Provide guidance or tooling for creating maps and schemas on Linux/macOS, such as web-based designers or cross-platform CLI tools.
  • Explicitly mention Visual Studio Code as a possible alternative for artifact creation, if supported, or clarify its limitations.
  • Include Linux/macOS-specific instructions or note any platform restrictions for artifact creation.
  • List cross-platform options before or alongside Windows tools to avoid Windows-first bias.
GitHub Create Pull Request
Logic Apps (Deprecated) Edit and manage logic apps with Visual Studio ...les/logic-apps/manage-logic-apps-with-visual-studio.md
High 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 is heavily focused on Visual Studio and related Windows-only tools (Cloud Explorer, Visual Studio extension, Solution Explorer), with no mention of Linux/macOS alternatives or parity. Prerequisites and all workflow steps assume use of Visual Studio on Windows, and Azure PowerShell is listed but not cross-platform CLI tools. There are no examples or guidance for Linux/macOS users, nor any mention of VS Code or platform-neutral approaches.
Recommendations
  • Add guidance for managing logic apps using cross-platform tools such as Visual Studio Code, Azure CLI, or Azure portal.
  • Include Linux/macOS-specific instructions or note platform limitations explicitly.
  • Mention and provide examples for Azure CLI and VS Code extensions where applicable.
  • Clarify that Visual Studio and Cloud Explorer are Windows-only, and suggest alternatives for non-Windows users.
  • Reorder prerequisites and examples to present platform-neutral or cross-platform options first.
GitHub Create Pull Request
Logic Apps (Deprecated) Create automated workflows in multitenant Azure Logic Apps with Visual Studio ...pps/quickstart-create-logic-apps-with-visual-studio.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows users, specifically those using Visual Studio on Windows. All instructions, screenshots, and tool references (e.g., Visual Studio, PowerShell) are Windows-specific. There are no examples or guidance for Linux or macOS users, nor are cross-platform alternatives mentioned for key steps such as project creation, deployment, or workflow management.
Recommendations
  • Explicitly state that the Visual Studio extension and workflow are Windows-only, if that is the case, and direct Linux/macOS users to equivalent cross-platform tools (e.g., Visual Studio Code, Azure CLI).
  • Add a prominent note at the top clarifying platform support and linking to Linux/macOS-compatible quickstarts.
  • Where PowerShell is referenced, provide Azure CLI equivalents, which are cross-platform.
  • Include a table or section comparing Windows and non-Windows development options for Logic Apps.
  • Ensure all critical workflows have documented alternatives for Linux/macOS users, or clearly state if not possible.
GitHub Create Pull Request
Logic Apps Set Up SQL Database Storage for Standard Workflows ...les/logic-apps/set-up-sql-database-storage-standard.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively supporting and referencing Windows-based App Service plans, mentioning Windows authentication for local development, and omitting Linux-based hosting options. Visual Studio Code is presented as the only local development tool, with no mention of Linux-specific workflows, SQL server editions, or authentication patterns. Linux-based App Service plans are explicitly unsupported, and there are no examples or guidance for Linux users wishing to self-host or develop locally.
Recommendations
  • Add explicit instructions and examples for Linux-based local development, including supported SQL server editions and connection patterns.
  • Clarify whether SQL authentication and storage provider setup can be performed on Linux hosts, and provide steps if possible.
  • If Linux-based App Service plans are unsupported, explain the technical reasons and suggest alternatives for Linux users (e.g., container-based deployment, Azure Arc, or VM hosting).
  • Include Linux command-line tools and workflows (e.g., Azure CLI, bash scripts) alongside Visual Studio Code for cross-platform parity.
  • Provide troubleshooting guidance for Linux/macOS users, especially around SQL connectivity and authentication.
GitHub Create Pull Request
Logic Apps Create and run .NET code from Standard workflows ...rticles/logic-apps/create-run-custom-code-functions.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly stating that the custom functions capability is currently available only in Visual Studio Code running on Windows. No instructions, examples, or troubleshooting steps are provided for Linux or macOS users. All workflow creation, debugging, and deployment steps assume a Windows environment, leaving non-Windows users unable to complete the described tasks.
Recommendations
  • Clearly indicate Windows-only limitations at the top of the page and in prerequisites.
  • Provide a roadmap or timeline for Linux/macOS support, if available.
  • Add alternative instructions or workarounds for Linux/macOS users, or link to related documentation for cross-platform scenarios.
  • Include explicit troubleshooting notes for Linux/macOS users attempting to use the extension.
  • Regularly update documentation as platform parity improves.
GitHub Create Pull Request
Logic Apps Install on-premises data gateway for logic app workflows ...gic-apps/install-on-premises-data-gateway-workflows.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. The installation and management of the on-premises data gateway are described exclusively in terms of Windows tools and patterns. The installer, screenshots, and service management instructions all assume a Windows environment. PowerShell is referenced as the automation method, with no mention of Linux/macOS equivalents. There are no instructions or examples for installing or running the gateway on Linux or macOS, nor any discussion of cross-platform support or alternatives.
Recommendations
  • Explicitly state platform requirements and limitations at the top of the document.
  • If the gateway is Windows-only, clarify this early and provide rationale or alternatives for Linux/macOS users.
  • If cross-platform support exists, add installation instructions, screenshots, and troubleshooting steps for Linux and macOS.
  • Include automation and management examples using Bash, shell scripts, or other Linux-native tools if supported.
  • Reference Linux/macOS service management patterns (e.g., systemd) if the gateway can run on those platforms.
  • If PowerShell is the only automation option, mention PowerShell Core and its cross-platform capabilities.
GitHub Create Pull Request
Logic Apps B2B enterprise integration workflows ...gic-apps/logic-apps-enterprise-integration-overview.md
High Priority View Details →
Scanned: 2026-01-13 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 recommending Visual Studio 2019 and the Microsoft Azure Logic Apps Enterprise Integration Tools Extension for creating maps and schemas, both of which are Windows-only tools. There is no mention of Linux or macOS alternatives for these critical tasks. Additionally, troubleshooting steps reference Windows-specific registry edits and DPI settings. While Visual Studio Code is mentioned as an option for managing and deploying logic apps, it is not clarified whether it can be used for artifact creation, and Windows tools are listed first and in more detail.
Recommendations
  • Explicitly document cross-platform alternatives for creating maps and schemas, such as any available CLI tools, web-based editors, or Visual Studio Code extensions that work on Linux/macOS.
  • Clarify which tasks can be performed using Visual Studio Code or the Azure portal, and provide step-by-step instructions for those platforms.
  • If no Linux/macOS alternatives exist, acknowledge this limitation and suggest possible workarounds or roadmap plans.
  • Avoid Windows-specific troubleshooting steps (e.g., registry edits) without offering platform-agnostic guidance or noting their applicability.
GitHub Create Pull Request
Logic Apps (Deprecated) Edit and manage logic apps with Visual Studio ...les/logic-apps/manage-logic-apps-with-visual-studio.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily focused on Windows and Visual Studio, with all instructions, screenshots, and tool references centered around the Windows ecosystem. There are no examples or guidance for Linux or macOS users, and required tools (Visual Studio, Cloud Explorer, Azure PowerShell) are either Windows-only or primarily used on Windows. No alternatives or parity for Linux/macOS development environments are mentioned.
Recommendations
  • Add equivalent instructions for managing logic apps using cross-platform tools such as Visual Studio Code, Azure CLI, or ARM templates.
  • Provide examples and workflows for Linux/macOS users, including how to edit, deploy, and manage logic apps without Visual Studio.
  • Mention and link to cross-platform alternatives (e.g., VS Code extensions, Azure CLI, REST API) in the prerequisites and throughout the guide.
  • Clarify which steps are Windows-specific and offer Linux/macOS-compatible alternatives where possible.
  • Include screenshots and step-by-step guides for non-Windows environments.
GitHub Create Pull Request
Logic Apps Create rules engine project with Visual Studio Code ...logic-apps/rules-engine/create-rules-engine-project.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits bias toward Windows environments by exclusively referencing Microsoft Rules Composer and BizTalk Server, both of which are Windows-only tools. There are no Linux/macOS alternatives or instructions for creating or exporting rulesets. The examples and screenshots are all based on Visual Studio Code, which is cross-platform, but the critical prerequisite tooling and workflows (Rules Composer, BizTalk) are Windows-specific. Additionally, the .NET Framework references (net472) suggest a Windows-centric build process, with no mention of .NET Core/6+ or cross-platform compatibility.
Recommendations
  • Explicitly state platform requirements for Microsoft Rules Composer and BizTalk Server, and clarify that these steps require Windows.
  • Provide guidance or alternatives for Linux/macOS users, such as using .NET Core/6+ for custom code, or clarify if the Rules Engine supports .NET Standard or .NET 6+ assemblies.
  • If possible, offer a cross-platform way to author rulesets (e.g., via JSON/XML editing or open-source alternatives) and document how Linux/macOS users can participate in the workflow.
  • Add Linux/macOS-specific instructions for compiling and running the project, including terminal commands and environment setup.
  • Reorder or supplement examples so that cross-platform steps are presented first, and Windows-only steps are clearly marked as such.
GitHub Create Pull Request
Logic Apps (Deprecated) Create automated workflows in multitenant Azure Logic Apps with Visual Studio ...pps/quickstart-create-logic-apps-with-visual-studio.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows users, specifically those using Visual Studio on Windows. All instructions, screenshots, and tool requirements assume a Windows environment. Only Windows tools (Visual Studio, PowerShell) are mentioned, with no Linux/macOS equivalents or alternatives provided. There are no examples or guidance for Linux or macOS users, and the use of PowerShell for deployment prompts further cements the Windows-only approach.
Recommendations
  • Add explicit notes about platform support, clarifying that Visual Studio-based Logic Apps development is only available on Windows, and suggest alternatives for Linux/macOS users.
  • Provide links and brief instructions for using Visual Studio Code and Azure CLI, which are cross-platform, for Logic Apps development and deployment.
  • Where PowerShell is referenced, mention Azure CLI as an alternative and provide equivalent CLI commands/examples.
  • Reorder or supplement the prerequisites and workflow sections to highlight cross-platform options (e.g., Visual Studio Code, Azure CLI) before or alongside Windows-specific instructions.
  • Include a comparison table or section outlining which features/tools are available on each OS, and direct non-Windows users to supported workflows.
GitHub Create Pull Request
Logic Apps Why move from BizTalk Server to Azure Logic Apps? ...ticles/logic-apps/biztalk-server-migration-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the frequent mention and prioritization of Windows-specific tools, technologies, and patterns (such as PowerShell, Windows registry, Windows Authentication, MMC consoles, and Visual Studio). Windows-centric terminology and tooling are referenced before or instead of Linux equivalents, and developer/administration workflows are described using Windows tools. There is little to no mention of Linux-native tools, shell scripting, or cross-platform alternatives in examples or tool recommendations.
Recommendations
  • Include Linux-specific or cross-platform examples and tooling (e.g., Bash, CLI, VS Code on Linux, Linux authentication methods) alongside or before Windows-specific ones.
  • When describing developer experiences, mention Linux-compatible IDEs and workflows, such as JetBrains Rider, VS Code on Linux, or command-line deployment using Bash.
  • For administration and monitoring, reference Azure CLI, REST API, and other platform-agnostic tools, not just MMC or PowerShell.
  • Replace or supplement references to Windows registry, Windows Authentication, and Windows-specific deployment/configuration patterns with Linux equivalents (e.g., environment variables, PAM, systemd, config files in /etc).
  • Highlight Azure Logic Apps and related services' support for Linux-based hosting and deployment, including containerization and Kubernetes on Linux.
  • Where custom code or scripting is discussed, provide examples in Bash, Python, or other Linux-native languages, not just PowerShell or C#.
  • Explicitly state cross-platform compatibility and provide parity in documentation for both Windows and Linux users.
GitHub Create Pull Request
Logic Apps Create and run .NET code from Standard workflows ...rticles/logic-apps/create-run-custom-code-functions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by explicitly stating that the custom functions capability is only available in Visual Studio Code running on Windows, without mentioning Linux or macOS support or alternatives. All examples and troubleshooting steps assume a Windows environment (e.g., file paths, error messages, and tool usage), and there are no instructions or examples for Linux users. Windows-specific tools and patterns (such as referencing Windows file paths and the Windows version of Visual Studio Code) are used exclusively.
Recommendations
  • Clearly state OS limitations in the prerequisites section and provide a roadmap or timeline for Linux/macOS support if possible.
  • Add Linux/macOS parity or alternatives for all steps, including installation, project creation, building, debugging, and troubleshooting.
  • Include Linux/macOS-specific error messages and troubleshooting guidance.
  • Where Windows-only features exist, suggest workarounds or alternative approaches for Linux/macOS users.
  • Use cross-platform file path examples or clarify when instructions are OS-specific.
  • If the feature is Windows-only, consider linking to equivalent Linux workflows or tools, or provide guidance for Linux users on how to achieve similar outcomes.
GitHub Create Pull Request
Logic Apps Create Standard logic app workflows for hybrid deployment ...ic-apps/create-standard-workflows-hybrid-deployment.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several forms of Windows bias. Troubleshooting and cluster management instructions rely heavily on Windows PowerShell, with commands and scripts (e.g., troubleshoot.ps1) provided only for PowerShell. There are explicit references to running Visual Studio Code as administrator, which is a Windows-centric instruction. When discussing Kubernetes and SMB CSI driver installation, commands are shown for Windows PowerShell and Windows command prompt, with no Linux shell equivalents. The documentation does not provide Linux/bash alternatives for key steps, nor does it mention Linux tools or patterns for troubleshooting, deployment, or cluster management. Windows tools and terminology (e.g., 'run as administrator', PowerShell scripts) are mentioned before or instead of Linux equivalents.
Recommendations
  • Provide equivalent bash shell commands for all PowerShell instructions, especially for kubectl and helm usage.
  • Include Linux-specific troubleshooting steps and scripts (e.g., a troubleshoot.sh for bash users).
  • Clarify instructions for running Visual Studio Code on Linux and macOS, avoiding Windows-specific terms like 'run as administrator'.
  • Mention Linux command-line tools (e.g., bash, sh, sudo) alongside Windows tools.
  • Ensure all deployment and configuration steps are documented for both Windows and Linux environments.
  • Add explicit notes or tabs for Linux users throughout the guide, especially in troubleshooting and deployment sections.
GitHub Create Pull Request
Logic Apps Call Azure Functions from workflows ...cles/logic-apps/call-azure-functions-from-workflows.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by frequently referencing Windows-specific tools (Azure PowerShell, Visual Studio), providing PowerShell commands as the only CLI example, and listing Windows-centric tools before cross-platform or Linux-native alternatives. There are no explicit Linux or bash shell examples, and the workflow for finding tenant/object IDs relies on PowerShell or Azure Portal, both of which are more familiar to Windows users. Visual Studio is mentioned before Visual Studio Code, and Azure PowerShell is listed before Azure CLI, despite CLI being more cross-platform. The Kudu/Advanced Tools instructions are also Windows-centric, with no mention of Linux-native approaches.
Recommendations
  • Provide equivalent bash/Azure CLI commands for all PowerShell examples, especially for finding tenant/object IDs.
  • List cross-platform tools (Azure CLI, Visual Studio Code) before Windows-only tools (PowerShell, Visual Studio) when presenting options.
  • Explicitly mention Linux support and provide Linux-specific instructions or screenshots where relevant (e.g., editing function.json, using Azure CLI in bash).
  • Clarify that Kudu/Advanced Tools are accessible from any OS via browser, and suggest alternative file editing methods for Linux users (e.g., using VS Code Remote, FTP, or Azure CLI).
  • Add a section or note on developing and deploying Azure Functions from Linux environments, including links to relevant documentation.
GitHub Create Pull Request
Logic Apps Connect Workflows to IBM Informix ...s/blob/main/articles/logic-apps/connectors/informix.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page displays a Windows bias by referencing Windows-specific tools and authentication methods (e.g., Kerberos in Windows Server), mentioning Windows-based Informix deployments first, and omitting Linux equivalents or examples. There are no Linux-specific instructions, screenshots, or authentication guidance, and the only referenced platform for Kerberos is Windows Server.
Recommendations
  • Add examples and instructions for connecting to Informix databases running on Linux, including common Linux deployment scenarios.
  • Include authentication guidance for Linux environments, such as Kerberos on Linux, and reference relevant Linux documentation.
  • Provide parity in screenshots and sample connection strings for both Windows and Linux Informix servers.
  • Mention Linux as a supported platform explicitly when listing Informix deployment options.
  • Reference Linux tools and patterns (e.g., systemd services, Linux firewall configuration) where relevant.
GitHub Create Pull Request
Logic Apps Create common SAP workflows ...ps/connectors/sap-create-example-scenario-workflows.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page exhibits Windows bias primarily through its troubleshooting and configuration instructions. It references Windows-specific file paths (e.g., %windir%\System32\drivers\etc\services and hosts), and configuration files (Microsoft.PowerBI.EnterpriseGateway.exe.config), without mentioning Linux equivalents or alternatives. The guidance for network service name resolution and host mapping is exclusively Windows-centric. Additionally, the troubleshooting steps and examples for the on-premises data gateway focus on Windows environments, with no mention of Linux or cross-platform support. There is also an implicit ordering where Windows tools and patterns are described first or exclusively, suggesting a Windows-first approach.
Recommendations
  • Include Linux equivalents for file paths and configuration steps, such as /etc/hosts and /etc/services.
  • Provide troubleshooting and configuration instructions for Linux-based installations of the on-premises data gateway.
  • Explicitly state platform support and any differences in setup or troubleshooting between Windows and Linux.
  • Add examples or notes for Linux users where PowerShell or Windows-specific tools are referenced.
  • Ensure parity in documentation by presenting cross-platform instructions side-by-side or in dedicated tabs/sections.
GitHub Create Pull Request
Logic Apps Create built-in connectors for Standard logic apps ...ogic-apps/create-custom-built-in-connector-standard.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a Windows bias by primarily referencing Windows tools, PowerShell scripts, and Windows-style file paths. PowerShell is presented as the main method for installing extensions, with Bash only mentioned as a wrapper for running PowerShell scripts. Output examples use Windows paths and conventions. There is no mention of Linux-native workflows, nor are Linux-specific tools or shell scripts provided. Visual Studio Code is referenced as the only supported authoring environment, but there is no discussion of Linux support or alternatives.
Recommendations
  • Provide native Bash or shell script examples for installing extensions, rather than only wrapping PowerShell scripts.
  • Include Linux file path examples and clarify cross-platform compatibility for all steps.
  • Explicitly state Visual Studio Code support on Linux and macOS, or provide alternatives if available.
  • Offer instructions for using .NET CLI and NuGet on Linux/macOS, including package installation and project setup.
  • Ensure all output examples include both Windows and Linux path formats.
  • Mention any platform-specific limitations or requirements for Linux users.
GitHub Create Pull Request
Logic Apps Create Standard Workflows with Visual Studio Code ...c-apps/create-standard-workflows-visual-studio-code.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a Windows bias in several areas: Windows-specific tools and patterns (e.g., Windows Defender Firewall prompts, registry edits via regedit, App Service plan selection limited to Windows-based plans), Windows paths and screenshots, and troubleshooting steps that reference Windows-only features. Linux/macOS equivalents are often missing or mentioned after Windows, and some examples (such as registry edits and firewall prompts) are exclusively for Windows. The use of Windows-centric terminology and instructions may hinder parity and clarity for Linux users.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific steps, such as firewall configuration, registry edits, and file paths.
  • Include screenshots and examples from Linux/macOS environments alongside Windows ones.
  • When referencing tools (e.g., ngrok, command prompts), clarify usage on Linux/macOS (e.g., terminal commands, installation instructions).
  • Ensure App Service plan instructions cover Linux-based hosting options if supported, or clearly state Windows-only limitations.
  • Avoid presenting Windows instructions first or exclusively; interleave or parallelize instructions for all platforms.
  • Audit troubleshooting and error resolution steps to ensure Linux/macOS users are not excluded.
  • Use platform-agnostic language and paths where possible, or provide both formats.
GitHub Create Pull Request
Logic Apps Create and manage integration accounts ...s/enterprise-integration/create-integration-account.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure Portal (web UI) instructions first, referencing Azure PowerShell as a management option, and using Windows-centric tools (Azure Resource Explorer, Visual Studio Code with local.settings.json) for configuration and management. There is no explicit mention of Linux-specific CLI environments, nor are Linux shell examples (bash, zsh) provided. The Azure CLI examples are platform-neutral, but the overall workflow and tool recommendations lean toward Windows or web-based interfaces.
Recommendations
  • Add explicit instructions and examples for managing integration accounts using Azure CLI in Linux environments, including bash/zsh shell usage.
  • Mention that Azure CLI is cross-platform and provide sample commands for Linux/macOS terminals.
  • Include references to Linux-native editors (e.g., nano, vim) for editing configuration files, in addition to Visual Studio Code.
  • Clarify that Azure Portal and Azure Resource Explorer are web-based and accessible from any OS, not just Windows.
  • If PowerShell is mentioned, also reference bash or other Linux shells where applicable.
  • Ensure parity in screenshots and step-by-step guides for Linux users, especially for tasks like linking/unlinking integration accounts and managing environment variables.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/includes/logic-apps-single-tenant-project-structure-visual-studio-code.md ...pps-single-tenant-project-structure-visual-studio-code.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. It references .NET Framework (net472) and NuGet package-based projects, both of which are traditionally associated with Windows environments. The use of Visual Studio Code is cross-platform, but there are no explicit Linux-specific examples or mentions of Linux equivalents for .NET or NuGet workflows. The documentation lists Windows-centric technologies (NuGet, .NET Framework) before mentioning cross-platform or Linux-friendly options (Node.js/extension bundles), and does not provide parity in examples or guidance for Linux users.
Recommendations
  • Include explicit examples or notes for Linux users, such as how to work with NuGet and .NET projects on Linux (e.g., using .NET Core/.NET 6+ instead of .NET Framework).
  • Mention cross-platform alternatives to Windows-centric tools, such as using Mono or .NET Core for custom assemblies on Linux.
  • Provide folder/file structure examples for Linux environments, highlighting any differences (such as case sensitivity or file system conventions).
  • Clarify that Visual Studio Code and extension bundle-based projects are fully supported on Linux and macOS, and provide troubleshooting tips for those platforms.
  • Add references to Linux package managers or tools where relevant (e.g., how to install Azure Functions Core Tools on Linux).
GitHub Create Pull Request
Logic Apps Install on-premises data gateway for logic app workflows ...gic-apps/install-on-premises-data-gateway-workflows.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All installation instructions, screenshots, and operational details are centered around Windows environments. The gateway installer is described as running on 'local computer', but all references, examples, and service accounts are Windows-specific (e.g., Windows service, NT SERVICE\PBIEgwService). There are no Linux installation instructions, examples, or mentions of Linux service management. Automation is referenced only via PowerShell cmdlets, with no mention of Bash, shell scripts, or Linux-native tools. Troubleshooting and administration sections also assume a Windows environment.
Recommendations
  • Add explicit instructions and examples for installing and running the gateway on supported Linux distributions, if available.
  • Include Linux-specific service management details (e.g., systemd unit, service name, commands to start/stop/restart the gateway on Linux).
  • Provide automation examples using Bash scripts or Linux CLI tools in addition to PowerShell.
  • Clarify OS requirements and supported platforms early in the documentation, and link to platform-specific guides.
  • If the gateway is not supported on Linux, state this clearly and provide alternative solutions or workarounds for Linux environments.
GitHub Create Pull Request
Logic Apps Azure Resource Manager templates for Azure Logic Apps ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-azure-resource-manager-templates-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its explicit recommendation to use Azure PowerShell (with the LogicAppTemplate module) for creating Logic App templates, without mentioning cross-platform or Linux-native alternatives such as Azure CLI. The only tooling example provided is PowerShell, which is traditionally associated with Windows, and there are no Linux or macOS-specific instructions or examples. This may unintentionally signal to users that Windows is the preferred or only supported environment for these tasks.
Recommendations
  • Add equivalent Azure CLI examples for creating and deploying Logic App templates, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly state that all template authoring and deployment steps can be performed on Linux, macOS, and Windows, and provide links or instructions for installing required tools on each OS.
  • Where PowerShell is mentioned, clarify that PowerShell Core is available on Linux and macOS, or provide alternative commands using Azure CLI.
  • Review all tooling recommendations to ensure Linux parity and avoid implying that Windows is required for Azure Logic Apps template development.
GitHub Create Pull Request
← Previous Page 1 of 14 Next →