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 226-250 of 339 flagged pages
Logic Apps Call Azure Functions from workflows ...cles/logic-apps/call-azure-functions-from-workflows.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation occasionally demonstrates Windows bias, primarily in the tools and examples referenced for Azure Function creation and management. PowerShell and Visual Studio are mentioned alongside cross-platform options, but Windows-centric tools are listed before Linux/macOS alternatives. The guide for finding tenant IDs explicitly references PowerShell, with no Linux/macOS CLI alternative provided. The use of Kudu's CMD console is also more familiar to Windows users, though it is accessible via the portal for all platforms.
Recommendations
  • When listing tools for creating Azure Functions, mention cross-platform options (Azure CLI, Visual Studio Code) before Windows-only tools (Visual Studio, PowerShell).
  • Provide Azure CLI equivalents for PowerShell commands, especially for tasks like finding tenant IDs, to ensure Linux/macOS users have clear instructions.
  • Clarify that Kudu's debug console is accessible from any OS via the browser, and optionally mention Bash as an alternative to CMD for users more familiar with Unix shells.
  • Review screenshots and instructions to ensure they do not assume a Windows environment where not necessary.
GitHub Create Pull Request
Logic Apps Why move from BizTalk Server to Azure Logic Apps? ...ticles/logic-apps/biztalk-server-migration-overview.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page provides a comprehensive comparison between BizTalk Server (a Windows-only product) and Azure Logic Apps. While the page is not about a Windows-only Azure feature, it does exhibit some Windows bias: Windows tools (MMC, PowerShell, Windows registry) are referenced as primary management and configuration methods for BizTalk Server, and deployment/operations examples often mention PowerShell before Bash or CLI. Windows-centric patterns (e.g., GAC, registry, MMC) are described in detail, with limited Linux/macOS alternatives or parity notes. However, Azure Logic Apps and related Azure services are presented as cross-platform and cloud-native, with developer experiences and hosting options for both Windows and Linux. The bias is moderate, mainly because BizTalk Server is inherently Windows-only, but Linux/macOS users seeking migration guidance may find some friction due to the Windows-centric framing.
Recommendations
  • When describing deployment, management, or configuration patterns for BizTalk Server, explicitly note that these are Windows-only and suggest Azure-native or cross-platform alternatives for Azure Logic Apps.
  • In sections referencing PowerShell, MMC, or Windows registry, add notes or links to Bash/CLI equivalents for Azure Logic Apps and related Azure services.
  • Where developer experiences are listed, clarify which tools are cross-platform (e.g., Visual Studio Code, Azure CLI) and which are Windows-only.
  • In migration guidance, highlight how Azure Logic Apps and related services support Linux/macOS environments, and provide links to relevant documentation for those platforms.
  • Consider reordering examples so that Azure Logic Apps (cross-platform) is described first in relevant sections, or at least in parity with BizTalk Server.
GitHub Create Pull Request
Logic Apps Examples & common scenarios ...ticles/logic-apps/logic-apps-examples-and-scenarios.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for Azure Logic Apps examples and scenarios is generally cross-platform, but there is a notable tendency to mention PowerShell and Windows-centric scripting before Linux alternatives. For example, in the 'Run code from your workflows' section, PowerShell is listed alongside JavaScript, .NET, and C#, but there is no mention of Bash, shell scripts, or Linux-native scripting options. Additionally, deployment and management examples reference Azure DevOps and Visual Studio Code, which are cross-platform, but do not provide parity examples for Linux CLI or shell scripting. The overall bias is moderate, as Linux/macOS users can still complete all tasks, but may need to adapt Windows-centric instructions.
Recommendations
  • Add examples for running Bash or shell scripts from Logic Apps workflows, alongside PowerShell.
  • Explicitly mention Linux/macOS compatibility for Visual Studio Code and Azure DevOps workflows.
  • Include references or links to using Azure CLI and scripting on Linux/macOS for deployment and management tasks.
  • Where PowerShell is referenced, provide equivalent Bash or shell script examples if supported.
GitHub Create Pull Request
Logic Apps Create workflows with multiple Azure services ...ic-apps/tutorial-process-email-attachments-workflow.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page provides examples and instructions for both Azure PowerShell and Azure CLI when creating and managing Azure resources, but PowerShell and Windows-centric tools (such as Storage Explorer) are mentioned first or exclusively in several places. The tutorial also assumes use of the Azure portal, which is cross-platform, but the in-portal function editing is only supported on Windows, and this is called out. The use of Storage Explorer (a GUI tool available on Windows, macOS, and Linux) is required, but no alternatives or command-line options are suggested for Linux users. Overall, Linux parity is present but not emphasized, and Windows/PowerShell options are often listed before Linux/CLI equivalents.
Recommendations
  • Ensure that Azure CLI examples are presented alongside or before PowerShell examples, especially in steps for creating resources and retrieving keys.
  • Explicitly mention that Storage Explorer is available for Linux and macOS, and suggest command-line alternatives (such as az storage commands) for users who prefer CLI workflows.
  • Where in-portal editing is Windows-only, provide clear instructions for local development on Linux/macOS, including links to relevant guides.
  • Add notes or tips for Linux/macOS users throughout the tutorial to highlight any differences or alternative approaches.
GitHub Create Pull Request
Logic Apps Add and Run C# Scripts in Standard Workflows ...lob/main/articles/logic-apps/add-run-csharp-scripts.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows environments by exclusively referencing Windows-specific tools (Azure portal, KuduPlus console, CMD), and omitting equivalent instructions or examples for Linux/macOS users. All file management and script deployment steps are described using Windows-centric interfaces and terminology, with no mention of Linux shell commands or cross-platform alternatives.
Recommendations
  • Provide Linux/macOS equivalents for file management tasks, such as using SSH, SCP, or Azure CLI to upload and manage .csx files.
  • Include instructions for accessing the Kudu console from Linux/macOS, and clarify that the web-based Kudu interface is cross-platform.
  • Replace references to 'CMD' with more generic terms like 'command shell', and offer examples using Bash or PowerShell Core.
  • Explicitly state that all portal-based operations are platform-agnostic, and highlight any steps that may differ for non-Windows users.
  • Add screenshots or terminal commands demonstrating how Linux/macOS users can perform the same tasks.
GitHub Create Pull Request
Logic Apps Access SAP from workflows ...e-docs/blob/main/articles/logic-apps/connectors/sap.md
Medium 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 exhibits a notable Windows bias. Most examples, instructions, and tooling references are specific to Windows environments, such as using PowerShell scripts, referencing Windows file paths, and requiring Windows executables (e.g., sapgenpse.exe, sapcar.exe). Installation and configuration steps for SAP NCo and CommonCryptoLib are described only for Windows, with no mention of Linux or macOS equivalents. All example scripts and troubleshooting tools (e.g., fuslogvw.exe) are Windows-specific, and there are no alternative instructions or examples for Linux or macOS users.
Recommendations
  • Provide equivalent instructions and examples for Linux and macOS, including file paths, environment variable setup, and required tools.
  • Include Linux/macOS-compatible scripts for tasks such as base64 encoding PSE files (e.g., using 'base64' command in bash).
  • Document how to obtain, install, and use SAP NCo and CommonCryptoLib on Linux/macOS, if supported.
  • Reference cross-platform troubleshooting tools or provide alternatives to Windows-only tools like fuslogvw.exe.
  • Clarify platform support for SAP connectors and explicitly state any limitations or requirements for non-Windows environments.
GitHub Create Pull Request
Logic Apps Create built-in connectors for Standard logic apps ...ogic-apps/create-custom-built-in-connector-standard.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, especially in the installation and usage instructions for the custom connector extension. PowerShell commands and scripts are presented first and in detail, with Bash instructions only as a wrapper for running PowerShell scripts. Output examples and file paths are Windows-centric, and there is no guidance for Linux/macOS users on using native shell tools or alternatives to PowerShell. Visual Studio Code is referenced as the only supported authoring environment, but no mention is made of platform-specific considerations for Linux/macOS users.
Recommendations
  • Provide native Bash or shell script alternatives for installation and extension management, not just wrappers for PowerShell scripts.
  • Include Linux/macOS file path examples and output samples alongside Windows ones.
  • Clarify any platform-specific requirements or limitations for Visual Studio Code and the Azure Logic Apps extension on Linux/macOS.
  • Explicitly state whether the PowerShell scripts are cross-platform and, if not, provide equivalent instructions for Linux/macOS users.
  • List prerequisites and troubleshooting steps for Linux/macOS environments, such as .NET SDK installation and environment variable configuration.
GitHub Create Pull Request
Logic Apps Create common SAP workflows ...ps/connectors/sap-create-example-scenario-workflows.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias, primarily in troubleshooting and network configuration sections. It references Windows-specific file paths (e.g., %windir%\System32\drivers\etc\services and hosts) and configuration files (Microsoft.PowerBI.EnterpriseGateway.exe.config), which are only applicable to Windows environments. These instructions are presented without Linux/macOS equivalents or guidance. Additionally, Windows tools and patterns are mentioned first or exclusively in these contexts.
Recommendations
  • Include equivalent instructions for Linux/macOS environments, such as specifying where to find and edit the 'services' and 'hosts' files (typically /etc/services and /etc/hosts) and how to restart relevant services.
  • Clarify which troubleshooting steps are platform-specific and provide alternatives for non-Windows users.
  • If the on-premises data gateway is Windows-only, explicitly state this limitation early in the prerequisites.
  • Where configuration files or service management are discussed, offer cross-platform guidance or links to platform-specific documentation.
GitHub Create Pull Request
Logic Apps Create Standard logic app workflows for hybrid deployment ...ic-apps/create-standard-workflows-hybrid-deployment.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, particularly in troubleshooting and operational guidance. PowerShell scripts and commands are referenced as the primary method for diagnostics and cluster management, with no equivalent Bash or Linux shell examples. Instructions for running scripts and commands frequently specify Windows PowerShell or Windows command prompt, and administrator privileges are assumed in Visual Studio Code steps. There is no mention of Linux/macOS alternatives for key tasks such as running troubleshoot scripts, managing Kubernetes clusters, or installing the SMB CSI driver, which may hinder Linux/macOS users.
Recommendations
  • Provide equivalent Bash or Linux shell commands for all PowerShell examples, especially for kubectl, az, and helm usage.
  • Clarify that Visual Studio Code and Azure CLI steps are cross-platform, and remove or supplement 'Run as administrator' with Linux/macOS guidance (e.g., sudo usage).
  • Offer troubleshooting scripts in Bash or cross-platform languages, or document how to run the PowerShell script on Linux/macOS (e.g., via pwsh).
  • Explicitly mention that all Azure CLI and Kubernetes commands can be run on Linux/macOS, and provide example terminal commands.
  • Add screenshots or examples from Linux/macOS environments where relevant.
  • Avoid language that assumes Windows as the default platform (e.g., 'from Windows PowerShell, run...').
GitHub Create Pull Request
Logic Apps Create and manage integration accounts ...s/enterprise-integration/create-integration-account.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation consistently references Windows-centric tools and workflows, such as the Azure portal (web), Azure PowerShell, and Visual Studio Code, with no mention of Linux/macOS-specific alternatives or parity. Windows tools (Azure PowerShell) are mentioned alongside Azure CLI, but Linux-native editors (e.g., Vim, nano) or shell scripting are not referenced. The Azure portal is presented as the primary method for most tasks, and PowerShell is listed as an option for deleting integration accounts, but no equivalent Linux/macOS shell or automation examples are provided. Visual Studio Code is referenced for local development, but alternatives for Linux users are not discussed. The ordering of examples often places Windows-centric tools and workflows before cross-platform or Linux-friendly options.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, such as using native editors (vim, nano) for editing JSON files.
  • Include bash/shell scripting examples for automation tasks, especially where PowerShell is referenced.
  • Clarify that Azure CLI is fully cross-platform and highlight its use for Linux/macOS users.
  • Mention alternative editors to Visual Studio Code for Linux/macOS environments.
  • Where PowerShell is referenced, provide equivalent bash or shell commands.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before Windows-centric ones.
  • Add notes about platform compatibility for all tools and workflows.
GitHub Create Pull Request
Logic Apps Create Standard Workflows with Visual Studio Code ...c-apps/create-standard-workflows-visual-studio-code.md
Medium Priority View Details →
Scanned: 2026-01-14 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 moderate Windows bias. Windows-specific tools and patterns (e.g., Windows Defender Firewall prompts, registry edits, use of .exe files, Windows App Service plans) are mentioned first or exclusively in several sections. Some examples and troubleshooting steps are Windows-centric, such as editing the Windows registry or referencing Windows paths and executables. Linux/macOS equivalents are sometimes mentioned, but often as secondary notes or in less detail. The use of ngrok is cross-platform, but instructions and screenshots frequently default to Windows. The deployment section focuses on Windows-based App Service plans, with Linux options not equally highlighted.
Recommendations
  • Provide Linux/macOS-specific instructions and screenshots alongside Windows examples, especially for setup, troubleshooting, and file paths.
  • Explicitly mention Linux/macOS equivalents for all tools (e.g., firewall configuration, registry edits, executable names, App Service plans).
  • Reorder examples so that cross-platform or Linux/macOS instructions are not always secondary.
  • Clarify which steps are platform-agnostic and which require OS-specific actions.
  • Add troubleshooting steps for common Linux/macOS issues (e.g., permissions, path separators, service management).
  • Highlight Linux-based App Service plans and deployment options equally with Windows.
GitHub Create Pull Request
Logic Apps Create, edit, or extend logic app JSON workflow definitions ...n/articles/logic-apps/logic-apps-author-definitions.md
Medium 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 page demonstrates a moderate Windows bias by prioritizing Windows-centric tools and workflows, such as Azure PowerShell and Visual Studio, and mentioning them before cross-platform or Linux-friendly alternatives. While Azure CLI is referenced, there are no explicit Linux/macOS-specific instructions or examples, and Visual Studio Code (which is cross-platform) is only briefly mentioned. There are no command-line examples or guidance tailored for Linux/macOS users, and the workflow for editing JSON is described mainly in the context of Windows tools.
Recommendations
  • Provide explicit Linux/macOS instructions and examples, especially for command-line operations using Azure CLI.
  • Expand the Visual Studio Code section to include step-by-step instructions, emphasizing its cross-platform nature.
  • Avoid listing Windows tools (e.g., PowerShell, Visual Studio) before cross-platform alternatives unless contextually necessary.
  • Include screenshots or terminal examples from Linux/macOS environments where relevant.
  • Clarify that all JSON editing and deployment tasks can be performed on Linux/macOS using Azure CLI and VS Code.
GitHub Create Pull Request
Logic Apps Create Consumption logic app templates for deployment ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-create-azure-resource-manager-templates.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page focuses almost exclusively on using PowerShell and Windows-centric tools (LogicAppTemplate module, ARMClient) for creating and deploying Consumption logic app templates. All code examples are in PowerShell, and installation instructions reference PowerShell Gallery and Windows file paths. There are no equivalent instructions or examples for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform alternatives.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash for Linux/macOS users.
  • Clarify whether the LogicAppTemplate module and ARMClient are supported on Linux/macOS, and provide installation instructions if so.
  • Use platform-neutral file paths in examples, or show both Windows and Linux/macOS variants.
  • Explicitly mention cross-platform compatibility and alternatives to PowerShell where possible.
  • Add a section or note for Linux/macOS users outlining any differences or additional steps required.
GitHub Create Pull Request
Logic Apps Add authentication for calls to custom APIs ...les/logic-apps/logic-apps-custom-api-authentication.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for creating Microsoft Entra application identities using the Azure portal and PowerShell, but omits equivalent Linux/macOS CLI examples (such as Azure CLI). PowerShell is featured as the only command-line option, and is referenced before any Linux-friendly alternatives. There are no bash or Azure CLI commands, and no mention of Linux-specific tools or workflows, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for all steps currently covered by PowerShell, especially for app registration and service principal creation.
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant Azure CLI documentation.
  • Where possible, show both PowerShell and Azure CLI tabs/examples side-by-side.
  • Clarify any steps that are portal-only and explain why (e.g., permissions setup), and suggest workarounds or alternatives for Linux/macOS users.
  • Include notes or tips for Linux/macOS users regarding environment setup and command usage.
GitHub Create Pull Request
Logic Apps Disaster recovery for integration accounts ...ic-apps-enterprise-integration-b2b-business-continuity.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, primarily through repeated references to PowerShell cmdlets for critical disaster recovery operations (such as incrementing control numbers in agreements). No equivalent CLI, Bash, or Linux/macOS instructions are provided, and PowerShell is presented as the sole automation tool for these tasks. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Provide equivalent Azure CLI commands or REST API instructions for all PowerShell cmdlet steps, ensuring Linux/macOS users can perform the same operations.
  • Explicitly mention that PowerShell is cross-platform, but offer installation guidance for non-Windows users or alternatives where possible.
  • Reorder examples so that cross-platform or platform-neutral solutions (e.g., Azure CLI, REST API) are presented before or alongside PowerShell.
  • Add notes clarifying platform requirements for PowerShell cmdlets and link to documentation for using PowerShell on Linux/macOS.
GitHub Create Pull Request
Logic Apps Deploy Resource Manager templates ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-deploy-azure-resource-manager-templates.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides deployment instructions for Azure Resource Manager templates using the Azure portal, PowerShell, Azure CLI, REST API, and Azure DevOps. PowerShell is given a dedicated section before Azure CLI, and scripting examples for OAuth authorization reference PowerShell specifically. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is referenced as the scripting solution for automating OAuth consent, which may not be optimal or available on Linux/macOS systems. The overall flow and examples tend to favor Windows-centric tools and patterns.
Recommendations
  • Add Bash or shell script examples alongside PowerShell for deployment and OAuth authorization tasks.
  • Explicitly mention that Azure CLI works cross-platform and provide guidance for Linux/macOS users.
  • Include notes or links for installing and using PowerShell Core on Linux/macOS if PowerShell scripting is required.
  • Reorder sections so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell).
  • Provide parity in automation examples, e.g., sample Bash scripts for OAuth consent.
GitHub Create Pull Request
Logic Apps Overview ...s/blob/main/articles/logic-apps/logic-apps-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific concepts, tools, and hosting options (such as ASE v3 'Windows plans only') are mentioned before or exclusively, and scripting examples highlight PowerShell alongside .NET and C#, with no mention of Bash or Linux-native scripting. The documentation references Azure PowerShell and CLI, but does not provide parity or examples for Linux/macOS users. Visual Studio Code is mentioned as a cross-platform tool, but the overall pattern favors Windows-first terminology and tools.
Recommendations
  • Explicitly mention Linux/macOS compatibility for hosting options and workflow deployment.
  • Provide examples of workflow scripting using Bash or other Linux-native languages where PowerShell is referenced.
  • Clarify that Azure CLI is cross-platform and provide CLI examples alongside PowerShell.
  • Avoid phrases like 'Windows plans only' without explaining Linux alternatives or limitations.
  • Add guidance for Linux/macOS users on setup, deployment, and scripting within Logic Apps.
  • Ensure that all code and deployment examples are available for both Windows and Linux environments.
GitHub Create Pull Request
Logic Apps Add maps to use with workflows ...s/logic-apps/logic-apps-enterprise-integration-maps.md
Medium Priority View Details →
Scanned: 2026-01-14 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. Visual Studio and its extensions (Windows-only tools) are mentioned prominently and described in detail for map creation and management, including screenshots and troubleshooting steps specific to Windows (e.g., DPI awareness, registry edits). Visual Studio Code is mentioned as a cross-platform alternative, but its coverage is less detailed and often secondary. Azure Storage Explorer, while cross-platform, is presented with a workflow and screenshots that assume a Windows GUI experience. There are no Linux/macOS-specific examples, CLI alternatives, or explicit parity checks for non-Windows environments.
Recommendations
  • Expand documentation for Visual Studio Code workflows, including step-by-step instructions and screenshots for map creation and management.
  • Add explicit Linux/macOS examples for uploading, editing, and deleting maps and assemblies, possibly using Azure CLI or REST API.
  • Clarify cross-platform support for Azure Storage Explorer and provide CLI alternatives (e.g., az storage commands) for blob management.
  • Avoid troubleshooting steps that are Windows-specific (e.g., registry edits) without noting their platform limitations.
  • Present cross-platform tools and workflows before Windows-only options to reduce perceived bias.
GitHub Create Pull Request
Logic Apps Examples & common scenarios ...ticles/logic-apps/logic-apps-examples-and-scenarios.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references PowerShell and C# scripting as workflow actions, but does not mention or provide parity for Linux/macOS equivalents such as Bash or Python. There are no examples or guidance for Linux-native scripting or tools, and PowerShell is referenced as a primary automation language, which is traditionally Windows-centric. No Linux-specific deployment, management, or monitoring tools are mentioned, and Windows-oriented technologies (BizTalk Server, Power Automate) are referenced in migration scenarios without Linux alternatives.
Recommendations
  • Include examples for Bash and Python scripts as workflow actions, alongside PowerShell and C#.
  • Explicitly mention cross-platform support for scripting and automation, and provide links to relevant Linux/macOS documentation.
  • Add guidance for deploying, managing, and monitoring Logic Apps using Linux-native tools (e.g., Azure CLI, Bash scripts).
  • Clarify that PowerShell Core is cross-platform, and provide instructions for Linux/macOS installation and usage.
  • Reference Linux-friendly migration paths and tools where relevant, or clarify platform neutrality.
GitHub Create Pull Request
Logic Apps Power Automate migration ...b/main/articles/logic-apps/power-automate-migration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias by explicitly mentioning PowerShell scripting as an option for custom code in workflows, without referencing Linux/macOS alternatives such as Bash or Python. There are no examples or guidance for Linux/macOS users in sections discussing script integration, and the documentation does not mention cross-platform scripting or tools. However, most of the development tooling (Visual Studio Code, Azure portal) is cross-platform, and there are no Windows-only instructions or tools required for the migration process.
Recommendations
  • Explicitly mention and provide examples for Bash and Python scripting in workflow integration, alongside PowerShell and C#.
  • Clarify that Visual Studio Code and the Azure portal are available on Linux and macOS, and provide any platform-specific setup notes if relevant.
  • Add a section or note on cross-platform scripting support in Azure Logic Apps, including any limitations or best practices for Linux/macOS users.
  • Ensure that all scripting examples are provided for both Windows (PowerShell) and Linux/macOS (Bash/Python) where applicable.
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
Medium 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 demonstrates a Windows bias by exclusively referencing the Azure portal (a web interface most commonly accessed from Windows environments) and Microsoft 365 services, with all examples centered around Office 365 Outlook and Microsoft Entra ID. There are no references to Linux/macOS-specific tools, CLI commands, or alternative authentication flows. No PowerShell or Windows tool commands are shown, but the examples and screenshots are implicitly Windows-centric, and there is no mention of Linux or cross-platform CLI usage for setup or testing.
Recommendations
  • Include examples using Azure CLI and/or REST API for OBO flow setup, which are cross-platform and commonly used on Linux/macOS.
  • Add guidance for setting up and testing OBO flows from Linux/macOS environments, such as using curl, az CLI, or other non-GUI tools.
  • Mention that the Azure portal and agent workflows can be accessed from any OS with a supported browser, and clarify any OS-specific limitations.
  • Provide troubleshooting steps or notes relevant to Linux/macOS users, such as authentication issues with non-Windows browsers or environments.
GitHub Create Pull Request
Logic Apps Create rules engine project with Visual Studio Code ...logic-apps/rules-engine/create-rules-engine-project.md
Medium Priority View Details →
Scanned: 2026-01-14 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 moderate Windows bias. It exclusively references Microsoft Rules Composer and BizTalk Server (Windows-only tools) for rule creation and export, and all screenshots and instructions are tailored to Visual Studio Code on Windows. Terminal commands use Windows path separators (e.g., .\RulesFunction.csproj) and do not provide Linux/macOS equivalents. There is no mention of Linux or macOS support for Microsoft Rules Composer, nor any alternative tooling or workflows for non-Windows platforms.
Recommendations
  • Explicitly state platform requirements for Microsoft Rules Composer and BizTalk Server, clarifying that these are Windows-only tools.
  • Provide alternative instructions or tooling for rule creation and export on Linux/macOS, or suggest workarounds (e.g., using XML editors or open-source rule engines).
  • Include Linux/macOS terminal command examples (e.g., using ./RulesFunction.csproj instead of .\RulesFunction.csproj).
  • Add notes or sections addressing any limitations or differences when developing on Linux/macOS, especially regarding rule authoring and export.
  • If possible, recommend cross-platform alternatives or clarify which steps are fully supported on Linux/macOS.
GitHub Create Pull Request
Logic Apps Set Up DevOps for Standard Workflows ...et-up-devops-deployment-single-tenant-azure-logic-apps.md
Medium 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 provides several examples and instructions that are either Windows-centric or omit explicit Linux/macOS equivalents. For instance, commands like 'Save as' in the Azure portal, and instructions to 'open a command prompt' for pip installation, mention Windows and Mac but do not reference Linux. The CLI instructions do not show Linux-specific shell usage or mention differences in installation or environment setup for Linux users. The documentation also refers to Visual Studio Code, which is cross-platform, but does not clarify platform-specific steps where they may differ.
Recommendations
  • Explicitly include Linux/macOS terminal instructions alongside Windows/Mac command prompt guidance (e.g., mention 'open a terminal' for Linux).
  • Add notes or examples for Linux-specific package installation (e.g., pip, Azure CLI) and environment setup.
  • Where file operations are described (e.g., 'Save as'), clarify how these steps work on Linux desktops.
  • Ensure all CLI commands are shown in a way that is platform-agnostic or provide platform-specific variants if necessary.
  • Review all references to tools and workflows to ensure Linux/macOS users are not left to infer steps.
GitHub Create Pull Request
Logic Apps Set up your own infrastructure for Standard logic app workflows ...t-up-standard-workflows-hybrid-deployment-requirements.md
Medium 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 demonstrates a moderate Windows bias. Windows-specific tools (Chocolatey, PowerShell) are used for installing critical components (kubectl, Helm), with explicit PowerShell commands and references to Windows Server and Windows file sharing. Linux alternatives for installing these tools are not provided, and Windows setup instructions for SMB shares appear before Azure Files and Linux-based guidance. The main automation script is provided only as a PowerShell (.ps1) file, with no Bash or shell equivalent. While some Linux usage is implied (e.g., test pods use Linux images), explicit Linux-first or cross-platform instructions are lacking in key setup steps.
Recommendations
  • Provide Linux-native installation instructions for kubectl and Helm (e.g., apt, yum, curl, or official binaries), not just Chocolatey/PowerShell.
  • Offer a Bash or shell script equivalent to EnvironmentSetup.ps1, or document manual steps for Linux/macOS users.
  • Present Azure Files and Linux SMB setup instructions before or alongside Windows SMB setup.
  • Explicitly mention how Linux/macOS users can set up and mount SMB shares, including example commands.
  • Clarify which steps are OS-agnostic and which require platform-specific handling.
  • Where PowerShell commands are given, provide Bash equivalents for Linux/macOS.
  • Add notes or sections for macOS users where relevant (e.g., mounting SMB shares, installing CLI tools).
GitHub Create Pull Request
Logic Apps Create workflows with multiple Azure services ...ic-apps/tutorial-process-email-attachments-workflow.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools (Azure Storage Explorer) are referenced exclusively, and in several places, Windows-centric options (e.g., in-portal editing only on Windows) are mentioned first or exclusively. PowerShell is given as an example for resource creation and management, sometimes before or alongside Azure CLI, but Linux/macOS alternatives are not highlighted or explained. There are no explicit Linux/macOS workflow examples or tool recommendations, and some steps (like Storage Explorer usage) assume Windows usage.
Recommendations
  • Explicitly mention and provide parity for Linux/macOS users in tool selection (e.g., alternatives to Storage Explorer, such as azcopy, Azure CLI, or web portal).
  • When listing command-line options, present Azure CLI before or alongside PowerShell, and clarify that Azure CLI is cross-platform.
  • Add notes or sections for Linux/macOS users, especially where features (like in-portal editing) are Windows-only, suggesting alternatives (e.g., VS Code, local development, CLI).
  • Include screenshots or instructions for Linux/macOS environments where UI or workflow differs.
  • Clarify that all Azure portal steps are OS-agnostic, and highlight any OS-specific limitations.
GitHub Create Pull Request
← Previous Page 10 of 14 Next →