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 76-100 of 339 flagged pages
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a Windows bias by exclusively referencing Microsoft tools such as Microsoft Rules Composer and BizTalk Server, which are only available on Windows. There are no Linux alternatives or cross-platform equivalents mentioned, nor are there instructions for Linux users on how to perform equivalent tasks. All tool references and examples assume a Windows environment, and there is no guidance for Linux users regarding installation, usage, or troubleshooting.
Recommendations
  • Explicitly state platform requirements and limitations at the top of the page, including that Microsoft Rules Composer and BizTalk Server are Windows-only.
  • Provide guidance for Linux users, such as alternative approaches for rule authoring, or clarify if the Rules Engine project can be developed entirely in Visual Studio Code on Linux once rulesets are available.
  • If possible, suggest or document any cross-platform or open-source alternatives for rule authoring and management.
  • Include instructions or notes for Linux users regarding .NET SDK installation, building, and running projects in Visual Studio Code on Linux.
  • Add troubleshooting or FAQ sections for common Linux issues (e.g., file paths, permissions, .NET compatibility).
  • Ensure that all screenshots and step-by-step instructions clarify whether they are Windows-specific, and provide Linux equivalents where possible.
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-10 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 focused on Windows and Visual Studio, with all examples and instructions tailored to Windows users. It exclusively references Windows tools (Visual Studio, PowerShell), uses Windows-specific paths and UI, and does not provide Linux or cross-platform alternatives. There are no instructions for using Visual Studio on Linux or macOS, nor are there CLI or VS Code examples within this page, despite mentioning their existence elsewhere.
Recommendations
  • Add explicit instructions and examples for Linux and macOS users, such as using Visual Studio Code or Azure CLI.
  • Include cross-platform alternatives for deployment and management, e.g., show how to deploy Logic Apps using Azure CLI or VS Code on Linux/macOS.
  • Reference and link to Linux/macOS setup guides directly in the prerequisites and workflow sections.
  • Avoid assuming Visual Studio is the only development environment; clarify platform limitations and suggest alternatives where appropriate.
  • Provide PowerShell alternatives (such as Bash/Azure CLI commands) for credential prompts and deployment steps.
GitHub Create Pull Request
Logic Apps Authorize Agent Access with On-Behalf-Of Flow ...n/articles/logic-apps/set-up-on-behalf-of-user-flow.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and Microsoft-centric environments. All examples, screenshots, and tool references are based on Microsoft services (Azure portal, Office 365 Outlook, Microsoft Entra ID, etc.), with no mention of Linux equivalents, cross-platform CLI tools, or non-Microsoft authentication patterns. The workflow and testing instructions assume use of the Azure portal and Microsoft authentication flows, omitting guidance for Linux users or those working outside the Microsoft ecosystem.
Recommendations
  • Include examples using cross-platform tools such as Azure CLI, which runs on Linux, macOS, and Windows, for setting up OBO flows and connections.
  • Provide instructions for configuring OBO flows using REST APIs or scripting languages (e.g., bash, curl) commonly used on Linux systems.
  • Mention and demonstrate how to access and manage Logic Apps and agent workflows from Linux environments, including authentication and testing steps.
  • Add screenshots or terminal output examples from Linux environments to illustrate parity.
  • Reference open-source or non-Microsoft connectors where possible, and clarify any platform-specific limitations or requirements.
GitHub Create Pull Request
Logic Apps Set up your own infrastructure for Standard logic app workflows ...t-up-standard-workflows-hybrid-deployment-requirements.md
High Priority View Details →
Scanned: 2026-01-10 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 moderate Windows bias. Windows-specific tools (such as Chocolatey and PowerShell) are used for installing Kubernetes CLI tools (kubectl, Helm), and PowerShell commands are provided for setting execution policy. The main script for environment setup is a PowerShell script (.ps1), and Windows SMB file share setup instructions are given before Linux or cross-platform alternatives. There is limited guidance for Linux-native approaches, and Linux package managers (e.g., apt, yum) are not mentioned for installing CLI tools. The documentation assumes familiarity with Windows environments and tools, which may hinder Linux users.
Recommendations
  • Provide Linux-native installation instructions for kubectl and Helm using package managers like apt, yum, or direct download.
  • Include Bash script equivalents for environment setup, alongside the PowerShell script.
  • Offer SMB file share setup instructions for Linux (e.g., using Samba) and clarify cross-platform options.
  • Ensure examples and tooling guidance are presented in a platform-neutral order, or explicitly call out both Windows and Linux options.
  • Reference Linux documentation and tools where appropriate, not just Windows-centric resources.
  • Where PowerShell commands are given (e.g., Set-ExecutionPolicy), provide the equivalent steps for Linux/macOS users.
GitHub Create Pull Request
Logic Apps Create workflows with multiple Azure services ...ic-apps/tutorial-process-email-attachments-workflow.md
High Priority View Details →
Scanned: 2026-01-10 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 exhibits a Windows bias through the prioritization and exclusive mention of Windows tools (e.g., Microsoft Azure Storage Explorer), frequent use of Azure PowerShell examples, and explicit instructions for Windows-specific features (such as in-portal editing for Azure Functions only being available on Windows). Linux alternatives, CLI commands, and cross-platform considerations are mentioned but generally appear after Windows options or lack detailed parity. There are no Linux-specific workflow or tool examples, and the documentation assumes the use of Windows in several steps.
Recommendations
  • Provide equal prominence and step-by-step examples for Azure CLI alongside PowerShell, especially in resource creation and management sections.
  • Include instructions and screenshots for using cross-platform tools (e.g., azcopy, Azure CLI, or third-party storage browsers) for storage management, not just Storage Explorer.
  • Clarify which steps and features are available or differ on Linux/macOS, especially for Azure Functions development and portal editing.
  • Add Linux/macOS-specific notes or alternatives wherever Windows-only features or tools are mentioned.
  • Ensure that all code samples and workflow steps are tested and documented for Linux environments, including local development and authentication flows.
  • Consider adding a section or appendix for Linux users, summarizing platform differences and recommended tools.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation displays a Windows bias by exclusively supporting and referencing Windows-based App Service plans for hosting, explicitly stating that Linux-based plans are not supported. Windows tools such as SQL Server Management Studio (SSMS) and MSI installers are mentioned, while Linux equivalents are omitted. There are no examples or instructions for Linux-based development environments, SQL servers, or deployment workflows, and the prerequisites and setup steps assume a Windows-centric approach.
Recommendations
  • Add explicit guidance and examples for Linux-based App Service plans, or clarify future support if currently unavailable.
  • Include Linux-compatible SQL server options (e.g., SQL Server on Linux, Azure SQL Edge) and instructions for setup and connectivity.
  • Provide examples and instructions for using Linux-based development environments, such as Visual Studio Code on Linux, and alternative installation methods (e.g., .deb, .rpm, or npm for Azure Functions Core Tools).
  • Mention cross-platform SQL management tools (e.g., Azure Data Studio) alongside SSMS.
  • Clarify any limitations for Linux users and offer workarounds or alternatives where possible.
GitHub Create Pull Request
Logic Apps Differences between Standard and Consumption logic apps .../articles/logic-apps/single-tenant-overview-compare.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by repeatedly referencing 'Windows plans only' for hosting environments (App Service Environment v3), mentioning Windows-specific deployment scenarios before Linux or cross-platform options, and omitting explicit Linux examples or instructions. The tooling and development environment sections focus on Visual Studio Code and Azure portal, which are cross-platform, but deployment and hosting guidance is predominantly centered on Windows environments. There are no examples or guidance for deploying to Linux-based App Service plans, containers, or other non-Windows environments, and no mention of Linux-specific patterns or troubleshooting.
Recommendations
  • Add explicit examples and instructions for deploying Standard logic apps to Linux-based App Service plans, containers, or other non-Windows environments.
  • Clarify which features and hosting options are available on Linux, and note any differences in capabilities or limitations.
  • Include Linux-specific troubleshooting steps, patterns, and best practices alongside Windows guidance.
  • When referencing 'Windows plans only', provide parity by mentioning Linux alternatives or stating if/why they are not supported.
  • Ensure that any tool or workflow described (e.g., Azure CLI, VS Code) highlights cross-platform compatibility and, where relevant, provides Linux-specific configuration or usage notes.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/authenticate-with-managed-identity.md ...icles/logic-apps/authenticate-with-managed-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently lists Windows-centric tools (Azure PowerShell, Azure portal) before Linux-friendly alternatives (Azure CLI, REST API) when presenting options for creating identities, assigning roles, and managing access. PowerShell is given equal or greater prominence than Azure CLI, and all portal instructions are based on the Azure portal (a web GUI, but often associated with Windows workflows). There are no explicit Linux shell or scripting examples, and no mention of Linux-specific patterns or tools. The documentation does not provide parity for Linux users in terms of command-line examples, nor does it acknowledge Linux environments or workflows.
Recommendations
  • When listing command-line tools, alternate the order or list Azure CLI before PowerShell to avoid implicit Windows-first bias.
  • Provide explicit Bash/Azure CLI examples alongside PowerShell for all tasks, including identity creation, role assignment, and access policy management.
  • Include notes or sections for Linux users, such as how to perform tasks in Linux shells, and clarify that all steps are cross-platform unless otherwise noted.
  • Reference Linux automation tools (e.g., shell scripts, cron jobs) where relevant, and provide sample scripts for common scenarios.
  • Add a parity checklist to ensure all PowerShell instructions have equivalent Azure CLI (and, where possible, REST API) examples.
  • Consider including screenshots or walkthroughs for Azure CLI in addition to the Azure portal.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/biztalk-server-migration-overview.md ...ticles/logic-apps/biztalk-server-migration-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. BizTalk Server is inherently a Windows-only product, and the documentation reflects this by referencing Windows tools (MMC, Windows registry, Windows Authentication, Visual Studio, PowerShell) and patterns throughout. Examples and tooling references (such as BizTalk Administration Console, BizTalk Health Monitor, and deployment via MSI/PowerShell) are exclusively Windows-centric, with no mention of Linux equivalents or cross-platform alternatives for on-premises scenarios. Even in Azure Logic Apps sections, developer tooling and automation examples prioritize PowerShell and Visual Studio, with limited mention of Bash, CLI, or Linux-based workflows. There are no Linux-specific examples or guidance for users migrating from non-Windows environments.
Recommendations
  • Explicitly acknowledge BizTalk Server's Windows-only nature and provide guidance for organizations migrating from Linux-based integration platforms.
  • In Azure Logic Apps sections, provide parity by including examples for Bash, Azure CLI, and Linux-based automation, not just PowerShell and Visual Studio.
  • Where developer tools are listed, clarify cross-platform support (e.g., Visual Studio Code is available on Linux/Mac) and offer examples for those platforms.
  • For deployment and automation, include sample scripts and CI/CD pipeline steps using Bash and Azure CLI alongside PowerShell.
  • In sections discussing configuration, avoid referencing only Windows registry and config files; mention Linux equivalents (e.g., environment variables, config files in /etc) where relevant.
  • Highlight that Azure App Service and Logic Apps can be hosted on Linux, and provide links or examples for Linux-based hosting and management.
  • Where monitoring and management tools are discussed, mention cross-platform alternatives (e.g., Azure portal, REST APIs, CLI) and how Linux administrators can access these features.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/connect-on-premises-data-sources.md ...rticles/logic-apps/connect-on-premises-data-sources.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 referencing installation of the on-premises data gateway on a 'local computer' without specifying cross-platform support, repeatedly mentioning Windows-specific tools (e.g., PowerShell for automation and service management), and providing troubleshooting steps that reference restarting the 'gateway Windows service account.' There are no Linux-specific instructions, examples, or references to Linux tools or service management patterns. All automation and administrative examples are PowerShell-centric, and there is no mention of Bash, systemd, or Linux service management.
Recommendations
  • Explicitly state whether the on-premises data gateway supports installation on Linux and provide installation instructions for supported platforms.
  • Include Linux-specific examples for service management, such as using systemctl to restart the gateway service.
  • Provide automation examples using Bash scripts or Azure CLI, not just PowerShell.
  • Reference Linux equivalents for troubleshooting steps (e.g., how to restart the gateway service on Linux).
  • Clarify cross-platform compatibility in prerequisites and throughout the documentation.
  • If the gateway is Windows-only, clearly state this limitation early in the documentation.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/call-azure-functions-from-workflows.md ...cles/logic-apps/call-azure-functions-from-workflows.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-centric tools such as Visual Studio and Azure PowerShell are listed before cross-platform or Linux-friendly alternatives. PowerShell commands are referenced for tasks like retrieving tenant IDs, with no mention of equivalent Bash or Azure CLI commands. The use of Visual Studio (Windows-only) is highlighted for function creation, while Linux-native editors or workflows (e.g., VS Code on Linux, CLI, or direct file editing) are not discussed. The Advanced Tools (Kudu) interface is described using CMD (Windows shell), with no mention of Bash or Linux shell options. There are no explicit Linux or macOS examples, nor are Linux-specific considerations addressed.
Recommendations
  • Add Azure CLI examples and commands alongside or before PowerShell commands for tasks such as retrieving tenant IDs and managing resources.
  • Explicitly mention cross-platform tools (e.g., VS Code, Azure CLI) and provide instructions for Linux/macOS users.
  • When referencing development tools, list Visual Studio Code and Azure CLI before or alongside Visual Studio and PowerShell.
  • In sections describing the use of Kudu/Advanced Tools, clarify that Bash is available and provide examples for both CMD and Bash shells.
  • Include screenshots or instructions from Linux/macOS environments where applicable.
  • Review all examples and ensure parity for Linux users, including file editing, authentication setup, and workflow creation.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/connectors/informix.md ...s/blob/main/articles/logic-apps/connectors/informix.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-based Informix deployments first ("IBM Informix for Windows running in Azure virtualization"), mentioning Windows authentication (Kerberos) and linking to Windows Server documentation, and omitting Linux-specific examples, tools, or authentication patterns. There are no examples or guidance for Linux-based Informix servers, Linux authentication mechanisms, or Linux-specific deployment scenarios.
Recommendations
  • Add explicit references and examples for connecting to Informix databases running on Linux, including typical Linux hostnames and authentication methods.
  • Include links to Linux authentication documentation (such as PAM, LDAP, or Kerberos on Linux) alongside Windows references.
  • Provide screenshots or configuration examples from Linux environments (e.g., Ubuntu, Red Hat) in addition to Windows.
  • Clarify that the connector works with both Windows and Linux Informix servers, and describe any platform-specific considerations.
  • Mention Linux-based deployment options in Azure (e.g., Informix on Linux VMs) and provide parity in instructions.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/connectors/sap-create-example-scenario-workflows.md ...ps/connectors/sap-create-example-scenario-workflows.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing Windows-specific tools and configuration patterns, such as editing files in %windir%\System32\drivers\etc\services and hosts, and referencing configuration files like Microsoft.PowerBI.EnterpriseGateway.exe.config. There are no examples or instructions for equivalent Linux environments (e.g., /etc/hosts, /etc/services, or Linux-based gateway configuration). Windows paths and tools are mentioned first and exclusively, and Linux alternatives are missing throughout troubleshooting and configuration sections.
Recommendations
  • Add Linux equivalents for all Windows-specific instructions, such as editing /etc/hosts and /etc/services for name and port mapping.
  • Provide troubleshooting steps and configuration file locations for Linux-based installations of the on-premises data gateway.
  • Include notes or examples for Linux users wherever Windows paths or tools are referenced.
  • Clarify whether the SAP connector and gateway are supported on Linux, and if so, provide parity in documentation for setup and maintenance tasks.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/connectors/sap.md ...e-docs/blob/main/articles/logic-apps/connectors/sap.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: installation and configuration steps frequently reference Windows-specific tools, directories, and patterns (e.g., C:\Program Files, .exe utilities, PowerShell scripts, %windir% paths). Examples for converting files, extracting archives, and configuring host/services files are provided only for Windows, with no Linux equivalents. The use of PowerShell for file conversion and batch files for archive extraction further emphasizes this bias. There are no instructions or examples for performing these tasks on Linux systems, nor are Linux-specific tools (such as bash, tar, or Linux directory paths) mentioned.
Recommendations
  • Provide equivalent instructions for Linux environments, including directory paths, file locations, and commands.
  • Include Linux shell script examples for tasks currently demonstrated with PowerShell or batch files (e.g., base64 encoding, archive extraction).
  • Mention Linux-compatible SAP NCo client library versions and installation steps, if available.
  • Reference Linux tools (e.g., tar, bash, cp, mv) alongside Windows tools (e.g., PowerShell, batch files).
  • Clarify any platform-specific limitations or requirements for SAP connectors and related utilities.
  • Add troubleshooting steps and log file locations for Linux hosts.
  • Ensure parity in screenshots and UI instructions for Azure portal features accessed from Linux browsers.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-custom-built-in-connector-standard.md ...ogic-apps/create-custom-built-in-connector-standard.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 prioritizing Windows-centric tools and workflows. Visual Studio Code is referenced as the only supported authoring environment, and all code/project examples use .NET Core and NuGet, which are cross-platform but traditionally Windows-centric in Azure contexts. The installation instructions and output examples are heavily focused on PowerShell, with explicit PowerShell commands and scripts (add-extension.ps1) given first and in detail, including Windows-style file paths and output. Bash instructions are only briefly mentioned and are dependent on PowerShell, requiring users to invoke PowerShell scripts from Bash, which is not native to Linux environments. There are no native Linux shell (bash-only) examples, nor are Linux-specific tools or patterns discussed.
Recommendations
  • Provide native Bash/Linux shell instructions for installing and managing extensions, not just PowerShell scripts invoked from Bash.
  • Include Linux/MacOS file path examples alongside Windows paths in code/output snippets.
  • Clarify whether Visual Studio Code authoring is supported on Linux/MacOS, and if so, provide explicit guidance for those platforms.
  • Offer parity in troubleshooting and workflow steps for Linux users, such as how to terminate running processes (func.exe) on Linux/MacOS.
  • If PowerShell scripts are required, offer alternative bash scripts or document how to install PowerShell Core on Linux and use it.
  • Explicitly state cross-platform compatibility for all tools and steps, and avoid assuming a Windows environment by default.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-standard-workflows-hybrid-deployment.md ...ic-apps/create-standard-workflows-hybrid-deployment.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Windows and PowerShell-based instructions and troubleshooting steps, such as running scripts with troubleshoot.ps1, using Windows PowerShell for Kubernetes and Helm commands, and referencing Windows command prompts. There are no explicit Linux or cross-platform alternatives provided for these steps, and Windows tools and patterns are mentioned exclusively or before any Linux equivalents.
Recommendations
  • Provide Linux and macOS equivalents for all command-line instructions, including running scripts and troubleshooting steps.
  • Include examples using Bash shell and Linux-native tools where PowerShell or Windows command prompt is referenced.
  • Clarify that commands like kubectl and helm are cross-platform, and show how to run them on Linux/macOS.
  • Offer troubleshooting scripts in Bash (.sh) format alongside PowerShell (.ps1) scripts.
  • Avoid language that assumes the user is on Windows (e.g., 'run Visual Studio Code as administrator' could be 'run with elevated privileges').
  • Explicitly mention platform requirements or differences for SMB file share access and port configuration.
  • Add notes or tabs for Linux/macOS users in all relevant sections, especially in troubleshooting and deployment instructions.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-standard-workflows-visual-studio-code.md ...c-apps/create-standard-workflows-visual-studio-code.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. Windows-specific tools (e.g., Windows Defender Firewall, regedit, .exe files) and patterns are mentioned first or exclusively, with Linux/macOS alternatives either omitted, mentioned later, or given less detail. Troubleshooting steps and configuration examples often default to Windows paths, registry edits, and .exe usage. Some examples and screenshots show Windows environments, and certain instructions (e.g., registry changes, firewall prompts) are only applicable to Windows. Linux/macOS equivalents are sometimes referenced, but not with equal prominence or detail.
Recommendations
  • Ensure all tool instructions (e.g., ngrok, command prompts) include explicit Linux/macOS equivalents, with equal detail and screenshots.
  • When referencing system prompts (e.g., firewall dialogs), clarify platform differences and provide Linux/macOS guidance (e.g., ufw, iptables, security dialogs).
  • For troubleshooting steps involving registry edits, provide Linux/macOS alternatives or clarify platform applicability.
  • Present cross-platform examples side-by-side, rather than Windows-first, especially for configuration files, paths, and environment setup.
  • Use neutral language and screenshots (or alternate between platforms) to avoid implicit Windows prioritization.
  • Explicitly state platform requirements or limitations for features that are Windows-only (e.g., App Service Environment v3), and suggest Linux/macOS alternatives where possible.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/enterprise-integration/create-integration-account.md ...s/enterprise-integration/create-integration-account.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 (a web UI most commonly accessed from Windows environments) instructions first, referencing Azure PowerShell, and relying heavily on Azure-specific tools and patterns (Portal, PowerShell, Resource Explorer) that are most familiar to Windows users. While Azure CLI examples are provided and are cross-platform, there are no explicit Linux-specific instructions, nor are Linux shell patterns (such as bash scripting or Linux-native tools) mentioned. The use of PowerShell and Resource Explorer further reinforces the Windows-centric approach.
Recommendations
  • Add explicit Linux shell (bash) examples for tasks such as creating, updating, and deleting integration accounts, including environment variable management and file editing.
  • Clarify that Azure CLI commands work equally well on Linux, macOS, and Windows, and provide installation instructions for Linux distributions.
  • Include references to Linux-native editors (e.g., nano, vim) when editing configuration files like local.settings.json.
  • Mention Linux-friendly alternatives to Azure Resource Explorer, such as using az CLI with jq for resource manipulation.
  • Where PowerShell is referenced, provide equivalent bash or shell script examples.
  • Reorder examples so that cross-platform or CLI instructions are presented before or alongside Portal/PowerShell instructions, rather than always after.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-author-definitions.md ...n/articles/logic-apps/logic-apps-author-definitions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell before Azure CLI when mentioning automation tools, and by providing detailed instructions for Visual Studio (a Windows-centric IDE) but omitting equivalent Linux editor workflows (such as VS Code on Linux or CLI-based editing). There are no explicit Linux or cross-platform examples for editing or deploying logic app JSON definitions, and no mention of Linux-native tools or workflows.
Recommendations
  • List Azure CLI before or alongside Azure PowerShell when mentioning automation tools, emphasizing CLI's cross-platform nature.
  • Provide explicit instructions and examples for editing logic app JSON definitions using VS Code on Linux, including any required extensions or setup.
  • Include examples of using text editors common on Linux (such as Vim, nano, or Emacs) for editing JSON workflow definitions.
  • Add guidance for deploying logic apps using Azure CLI on Linux, including sample commands.
  • Mention that the Azure portal and REST APIs are platform-agnostic, and clarify any platform-specific limitations.
  • Avoid assuming Visual Studio is the primary editor; highlight cross-platform alternatives where possible.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/install-on-premises-data-gateway-workflows.md ...gic-apps/install-on-premises-data-gateway-workflows.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All installation instructions, screenshots, and operational details assume a Windows environment, with references to Windows services, Windows authentication, and PowerShell cmdlets for automation. There is no mention of Linux support, examples, or equivalent tools. The installer and service management are described only in Windows terms, and Linux users are not addressed.
Recommendations
  • Explicitly state platform support: Clarify whether the on-premises data gateway supports Linux, and if not, provide rationale or roadmap.
  • Provide Linux installation instructions: If Linux is supported, add step-by-step instructions for installing and configuring the gateway on Linux systems.
  • Include Linux service management: Document how to start, stop, and manage the gateway service on Linux (e.g., using systemd).
  • Offer Linux automation examples: Add equivalent automation instructions for Linux, such as Bash scripts or CLI commands, alongside PowerShell examples.
  • Mention Linux prerequisites: List OS and hardware requirements for Linux, if applicable.
  • Add Linux troubleshooting and FAQ: Include Linux-specific troubleshooting steps and frequently asked questions.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-azure-resource-manager-templates-overview.md ...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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by referencing Azure PowerShell (and its LogicAppTemplate module) as the only explicit tool for creating Logic App templates, without mentioning or providing examples for cross-platform or Linux-native alternatives such as Azure CLI, Bicep, or REST API usage. There are no Linux shell or cross-platform command-line examples, and the only automation tooling guidance is Windows-centric. Additionally, in the 'Next steps' and throughout the page, there is no mention of Linux or macOS workflows, nor are there links to Linux-friendly tools or instructions.
Recommendations
  • Include Azure CLI examples for creating and deploying Logic App ARM templates, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Mention and provide examples for using Bicep, which is also cross-platform and increasingly recommended for ARM template authoring.
  • Reference REST API and/or GitHub Actions for template deployment, both of which are platform-agnostic.
  • When mentioning PowerShell, clarify that Azure PowerShell is available cross-platform, and provide installation and usage notes for Linux/macOS.
  • Add a 'Platform support' note early in the document, clarifying that all template operations can be performed from Windows, Linux, or macOS.
  • Ensure that any automation or scripting guidance is presented in a platform-neutral way, or provide parallel examples for both PowerShell and Bash/Azure CLI.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-create-azure-resource-manager-templates.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-create-azure-resource-manager-templates.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions and examples for creating and deploying Consumption logic app templates. All tooling references (LogicAppTemplate module, ARMClient) are presented in the context of PowerShell, with no mention of Linux-native alternatives or cross-platform shell usage. There are no Bash, Azure CLI, or Linux-specific examples, and the installation and usage patterns assume a Windows/PowerShell environment.
Recommendations
  • Add equivalent instructions and examples using Bash and Azure CLI for Linux and macOS users.
  • Document how to use LogicAppTemplate and ARMClient on Linux, including installation steps and command syntax.
  • Provide cross-platform guidance, explicitly noting which tools and commands work on Windows, Linux, and macOS.
  • Include references to Linux package managers (e.g., apt, yum, Homebrew) for installing required tools.
  • Ensure that examples do not assume Windows file paths (e.g., use generic or platform-neutral paths).
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-custom-api-authentication.md ...les/logic-apps/logic-apps-custom-api-authentication.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing PowerShell-based instructions for creating Microsoft Entra application identities, without offering equivalent CLI or Bash examples for Linux/macOS users. The only command-line automation shown is via PowerShell, and references to tools or patterns (such as 'Add-AzAccount', 'New-AzADApplication') are Windows-centric. There is no mention of Azure CLI, Bash, or cross-platform scripting alternatives. Additionally, the order of presentation places PowerShell instructions before any mention of Linux-compatible tooling, and the ARM template deployment section explicitly states that PowerShell cannot be used for certain tasks, but does not offer Linux alternatives.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line tasks, especially for creating and managing Microsoft Entra application identities.
  • Include Bash or shell script snippets where appropriate, and clarify which steps can be performed on Linux/macOS.
  • Explicitly mention cross-platform tools and workflows, such as Azure CLI, and provide links to relevant documentation.
  • Reorder sections so that cross-platform or platform-neutral instructions (e.g., Azure portal, Azure CLI) are presented before Windows/PowerShell-specific instructions.
  • Where PowerShell is required or recommended, note the equivalent steps for Linux/macOS users and provide guidance for installing PowerShell Core on those platforms if necessary.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-deploy-azure-resource-manager-templates.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-deploy-azure-resource-manager-templates.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and referencing PowerShell scripts for OAuth authorization, while not mentioning or providing equivalent Linux shell (bash) or cross-platform scripting alternatives. Windows tools and patterns (PowerShell, virtual machine with browser sessions) are referenced exclusively or before Linux equivalents. The Azure CLI example is present, but there is a heavier emphasis on PowerShell and Windows-centric workflows.
Recommendations
  • Provide bash or shell script examples for deploying Resource Manager templates, especially for OAuth authorization steps.
  • Explicitly mention that Azure CLI is cross-platform and provide guidance for Linux/macOS users where relevant.
  • Include instructions or references for running CI/CD pipelines and deployment tasks on Linux agents, not just Windows VMs.
  • If PowerShell scripts are referenced, offer equivalent bash scripts or note how Linux users can achieve the same outcome.
  • Review and update language to avoid assuming a Windows environment (e.g., 'run as a standard user account on a virtual machine' could mention Linux VMs or containers).
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-enterprise-integration-overview.md ...gic-apps/logic-apps-enterprise-integration-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates bias towards Windows by recommending Visual Studio (a Windows-only tool) and its extension for creating maps and schemas, with no mention of Linux or cross-platform alternatives. PowerShell is referenced as a management option, but Linux-native tools or CLI examples are absent. The guidance and troubleshooting steps are tailored to Windows environments, and Windows tools are mentioned before any cross-platform options.
Recommendations
  • Include instructions for creating maps and schemas using cross-platform tools, such as Visual Studio Code or other open-source editors, if available.
  • Provide Linux/macOS equivalents for resource management, such as Azure CLI commands, alongside PowerShell examples.
  • Mention and link to any available cross-platform extensions or tools for Azure Logic Apps development.
  • Clarify which steps or tools are Windows-specific and offer alternatives for non-Windows users.
  • Add troubleshooting guidance for Linux/macOS environments where relevant.
GitHub Create Pull Request
← Previous Page 4 of 14 Next →