Logic Apps

432
Total Pages
400
Linux-Friendly Pages
32
Pages with Bias
7.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

56 issues found
Showing 1-25 of 56 flagged pages
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation explicitly states 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 Linux/macOS users unable to follow or complete the documented process.
Recommendations
  • Clearly state Windows-only support at the top of the page and in prerequisites.
  • Provide a roadmap or timeline for Linux/macOS support, if planned.
  • Offer alternative instructions or workarounds for Linux/macOS users, if any exist.
  • Include parity tables or explicit notes on feature gaps between platforms.
  • Update documentation when Linux/macOS support becomes available, ensuring examples and troubleshooting steps are provided for those platforms.
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
High Priority View Details →
Scanned: 2026-01-12 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 exclusively on PowerShell-based workflows and Windows-centric tools (LogicAppTemplate PowerShell module, ARMClient, PowerShell Gallery), with all examples and installation instructions tailored for Windows/PowerShell users. No Linux/macOS shell equivalents, cross-platform CLI examples, or alternative workflows are provided, making it difficult for Linux/macOS users to follow the instructions or complete the task without significant adaptation.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI and Bash/zsh for Linux/macOS users.
  • Highlight cross-platform tools and workflows, such as using Azure CLI and REST API directly, or containerized solutions.
  • Clarify which steps are Windows-specific and offer alternatives for non-Windows environments.
  • Include installation and usage notes for ARMClient and LogicAppTemplate on Linux/macOS, or suggest alternative open-source tools.
  • Present examples for both PowerShell and Bash, and avoid assuming PowerShell as the default shell.
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-12 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 is heavily focused on Windows and Visual Studio, with all examples and instructions assuming use of Visual Studio (a Windows-only IDE) and referencing Windows-specific tools and patterns (e.g., PowerShell, %localappdata% paths). There are no Linux/macOS equivalents or alternative instructions provided, and Windows tools are mentioned exclusively and first. Linux/macOS users are directed elsewhere for alternative workflows but cannot follow this guide as written.
Recommendations
  • Add explicit notes at the beginning clarifying that Visual Studio is Windows-only and provide links to Linux/macOS compatible alternatives (e.g., Visual Studio Code, Azure CLI).
  • Where PowerShell is referenced, offer equivalent Bash/Azure CLI commands for Linux/macOS users.
  • Include a parallel quickstart or sidebar for Linux/macOS users, showing how to create and deploy Logic Apps using cross-platform tools.
  • Avoid using Windows-specific paths and environment variables without alternatives or explanations for other platforms.
  • Highlight cross-platform options in the prerequisites and throughout the workflow steps.
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-12 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 examples and instructions assuming use of Visual Studio (a Windows-only IDE for this context). Prerequisites include Windows-specific tools like Visual Studio, Cloud Explorer, and Azure PowerShell, with no mention of Linux/macOS alternatives or cross-platform tools (such as VS Code or CLI workflows). There are no examples or guidance for Linux/macOS users, and Windows tools are referenced exclusively and first throughout.
Recommendations
  • Add instructions and examples for managing logic apps using cross-platform tools such as Visual Studio Code, Azure CLI, or REST API.
  • Include guidance for Linux/macOS users, such as how to edit, deploy, and manage logic apps without Visual Studio.
  • Mention and link to platform-agnostic alternatives (e.g., VS Code extensions, Azure Portal, Azure CLI) in the prerequisites and throughout the guide.
  • Clearly state the platform limitations at the beginning and suggest alternatives for non-Windows users.
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-12 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 Windows-only tools such as Microsoft Rules Composer and BizTalk Server, and by providing command-line examples (e.g., dotnet restore/build) using Windows PowerShell/Command Prompt syntax (with backslashes). There is no mention of Linux/macOS equivalents or compatibility for key steps, such as rule authoring, exporting, or project setup. The documentation assumes the use of Windows environments and tools, leaving Linux/macOS users without guidance for critical parts of the workflow.
Recommendations
  • Clarify whether Microsoft Rules Composer and BizTalk Server are available or supported on Linux/macOS, or provide alternative cross-platform tools or approaches for rule authoring and exporting.
  • Include Linux/macOS-specific instructions for command-line operations, such as using forward slashes in paths (e.g., dotnet restore ./RulesFunction.csproj) and any required environment setup.
  • Explicitly state platform requirements and limitations early in the prerequisites section.
  • If possible, provide guidance for running Visual Studio Code and the Rules Engine project on Linux/macOS, including any required dependencies or workarounds.
  • Add troubleshooting notes for non-Windows users regarding compatibility issues or alternative workflows.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Windows Plan Required
Summary
The documentation page demonstrates a notable Windows bias. Windows-based App Service plans are required for hosting, with explicit instructions not to use Linux-based plans. All example hosting plans reference Windows. Tooling references are Microsoft-centric (Visual Studio Code, Azure Functions Core Tools MSI installer), with no mention of Linux package managers or alternatives. There are no examples or instructions for Linux or macOS users, such as connecting to SQL Server from Linux, using Linux-based SQL servers, or deploying from Linux environments. The documentation assumes a Windows-first approach throughout critical deployment steps.
Recommendations
  • Provide explicit instructions and examples for Linux/macOS users, including how to set up SQL Server on Linux and connect from Linux environments.
  • Clarify whether Linux-based App Service plans will be supported in the future, or explain the technical reasons for the Windows-only requirement.
  • Include alternative installation instructions for Azure Functions Core Tools using Linux package managers (e.g., apt, yum, Homebrew) alongside the MSI installer.
  • Add notes or sections for common Linux/macOS development workflows, such as using SQL Server on Docker, connecting from Linux terminals, or deploying from non-Windows hosts.
  • If Windows-only is a hard technical requirement, make this clear early in the documentation and provide guidance for Linux/macOS users on possible workarounds (e.g., using Azure-hosted Windows 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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a significant Windows bias. The custom functions capability is explicitly stated as available only on Visual Studio Code running on Windows. There are no instructions, troubleshooting, or examples for Linux or macOS users. All screenshots and workflow steps assume a Windows environment, and build errors reference Windows file paths. No Linux/macOS alternatives or workarounds are provided.
Recommendations
  • Clearly state Windows-only support at the top of the page and in prerequisites.
  • Provide a roadmap or timeline for Linux/macOS support, if planned.
  • Offer alternative approaches or workarounds for Linux/macOS users, such as using remote Windows VMs or containers.
  • Include troubleshooting steps and build error examples relevant to Linux/macOS environments if/when support is added.
  • Add explicit guidance for cross-platform development and deployment where possible.
GitHub Create Pull Request
Logic Apps Connect to on-premises data sources ...rticles/logic-apps/connect-on-premises-data-sources.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation repeatedly references the on-premises data gateway, which is a Windows-only tool, and links to PowerShell-based automation and management guides without mentioning Linux alternatives. There are no examples or instructions for installing or managing the gateway on Linux or macOS, nor are cross-platform command-line tools or patterns discussed. The only troubleshooting tip for connection issues refers to restarting the 'gateway Windows service account,' further reinforcing the Windows-centric approach.
Recommendations
  • Clearly state that the on-premises data gateway is Windows-only early in the documentation.
  • Provide guidance or alternatives for Linux/macOS users, such as recommending self-hosted connectors, built-in connectors, or other cross-platform integration patterns.
  • If possible, mention any roadmap or alternatives for Linux support, or link to relevant feedback channels.
  • When referencing automation (e.g., PowerShell), note that these instructions are for Windows and suggest cross-platform management options if available.
  • Add troubleshooting tips relevant to Linux/macOS environments if any connectors or workflows support those platforms.
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-11 06:20
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 oriented toward Windows environments, specifically Visual Studio and Cloud Explorer, which are Windows-only tools. Prerequisites and all examples assume use of Visual Studio, with no mention of Linux/macOS alternatives such as VS Code or CLI workflows. Azure PowerShell is listed as a required tool, but no Bash/CLI or cross-platform instructions are provided. The workflow and screenshots exclusively reference Windows UI patterns and features, making it difficult for Linux/macOS users to follow or replicate the steps.
Recommendations
  • Add instructions and examples for managing logic apps using cross-platform tools such as Visual Studio Code, Azure CLI, or REST API.
  • Include Linux/macOS-specific setup steps and alternatives to Visual Studio and Cloud Explorer.
  • Provide parity in examples by showing how to perform key actions (edit, deploy, manage, etc.) using Azure CLI or VS Code extensions.
  • Clarify which steps are Windows-only and offer guidance for non-Windows users.
  • Reference cross-platform documentation where available, and avoid listing Windows tools as the only or primary option.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Windows and Visual Studio, with all examples and instructions assuming the use of Windows-only tools (Visual Studio, PowerShell). There are no Linux/macOS equivalents or alternatives provided for key steps such as project creation, deployment, or resource management. The use of PowerShell and Visual Studio extensions further excludes non-Windows users, and Linux/macOS tooling is only mentioned as links to other articles, not integrated into the main workflow.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users using Visual Studio Code and Azure CLI, either in parallel or as alternative sections.
  • Provide cross-platform deployment steps using Azure CLI or REST API, not just Visual Studio and PowerShell.
  • Clarify which steps are Windows-specific and offer Linux/macOS alternatives where possible.
  • Include screenshots and walkthroughs for Visual Studio Code and CLI workflows.
  • Highlight parity and limitations for non-Windows environments at the top of the article.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows-based App Service plans are required, with explicit instructions not to use Linux-based plans. All examples and screenshots reference Windows tools (Azure portal, Visual Studio Code on Windows, SQL Server Management Studio), and there are no Linux/macOS-specific setup instructions or examples. The documentation omits guidance for Linux users, such as using Azure CLI, Linux-compatible SQL clients, or Linux-based development environments.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including supported development environments and SQL clients.
  • Clarify whether Linux-based App Service plans will be supported in the future, or provide workarounds for Linux users.
  • Include Azure CLI or cross-platform command-line instructions for resource creation and configuration.
  • Mention and provide examples for connecting to SQL databases from Linux/macOS, including connection string formats and authentication options.
  • List alternative tools to SQL Server Management Studio, such as Azure Data Studio, which is cross-platform.
GitHub Create Pull Request
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 provides examples and guidance for creating Azure Functions using a variety of tools, including Visual Studio, Visual Studio Code, Azure CLI, Azure PowerShell, and ARM templates. However, Windows-centric tools (Visual Studio, PowerShell) are mentioned before Linux/macOS-friendly options (VS Code, CLI). In the section for finding tenant IDs, PowerShell is suggested as the command-line method, with no mention of Azure CLI or other cross-platform alternatives. The use of Kudu (Advanced Tools) for editing files is also more familiar to Windows users, though it is technically available cross-platform. No Linux/macOS-specific examples or workflows are provided, and PowerShell is referenced without CLI parity.
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 commands alongside PowerShell commands for tasks such as finding tenant IDs, object IDs, and application IDs.
  • Include explicit guidance or examples for Linux/macOS users, such as using VS Code and Azure CLI for function creation and management.
  • Clarify that Kudu (Advanced Tools) is accessible from any OS via the browser, and suggest alternative file editing methods for Linux/macOS users (e.g., using FTP, Azure CLI, or VS Code remote extensions).
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-12 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 notable Windows bias in its instructions for file management and console access. Steps for uploading and managing .csx files, as well as viewing/editing files, are described exclusively using Windows-centric tools and terminology (e.g., KuduPlus console, CMD, drag-and-drop in Azure portal), with no mention of Linux/macOS equivalents or CLI alternatives. All screenshots and examples reference the Azure portal and Windows-style navigation. There are no examples or instructions for performing these tasks via Linux/macOS shells, SCP, SFTP, or cross-platform CLI tools.
Recommendations
  • Add instructions for accessing and managing workflow files using cross-platform tools such as Azure CLI, PowerShell Core (cross-platform), SCP/SFTP, or direct file system access from Linux/macOS.
  • Include examples and screenshots for Linux/macOS users, showing how to upload, edit, and manage .csx files without relying on Windows-specific GUI tools.
  • Mention that the Kudu console is accessible via a browser and can be used from any OS, but provide guidance for using Bash instead of CMD.
  • Clarify any OS-specific limitations or differences in workflow file management.
  • Provide parity in troubleshooting steps for compilation/runtime errors using Linux/macOS tools (e.g., tailing logs, using jq for JSON error parsing).
GitHub Create Pull Request
Logic Apps Call Azure Functions from workflows ...cles/logic-apps/call-azure-functions-from-workflows.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation demonstrates a moderate Windows bias. Windows-centric tools such as Visual Studio and Azure PowerShell are mentioned alongside cross-platform options, but Windows tools are listed before Linux-friendly alternatives (e.g., Azure CLI, VS Code). PowerShell commands are referenced for tasks like retrieving tenant IDs, without equivalent Bash or CLI examples. The workflow and screenshots are Azure Portal-based, which is cross-platform, but the emphasis on Windows tools and PowerShell may create friction for Linux/macOS users.
Recommendations
  • List cross-platform tools (Azure CLI, VS Code) before Windows-only tools (Visual Studio, PowerShell) when describing function creation options.
  • Provide Bash/Azure CLI equivalents for all PowerShell commands (e.g., for retrieving tenant IDs).
  • Explicitly mention Linux/macOS compatibility where relevant, and offer guidance for users on those platforms.
  • Add examples or references for Linux/macOS workflows, such as editing files or running commands.
  • Clarify that the Azure Portal is accessible from any OS/browser.
GitHub Create Pull Request
Logic Apps Connect to on-premises data sources ...rticles/logic-apps/connect-on-premises-data-sources.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (e.g., 'gateway Windows service account'), linking to PowerShell automation guides, and omitting any mention of Linux/macOS installation, management, or automation options for the on-premises data gateway. There are no examples or instructions for Linux or macOS users, nor is there clarification about platform support for the gateway software.
Recommendations
  • Explicitly state platform support for the on-premises data gateway (e.g., whether Linux/macOS are supported for installation).
  • If Linux/macOS installation is supported, provide equivalent instructions and examples for those platforms, including service management and automation (e.g., systemd commands, bash scripts).
  • If only Windows is supported, clarify this early in the prerequisites section to set user expectations.
  • Reference cross-platform automation tools (such as Azure CLI or REST API) alongside PowerShell, and provide examples for both.
  • Avoid phrases like 'gateway Windows service account' without noting platform limitations or alternatives.
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-12 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. It consistently references Windows-specific tools (such as PowerShell, .exe utilities, and Windows directory paths), provides examples and instructions using Windows conventions (e.g., C:\ paths, .exe files, PowerShell scripts), and omits equivalent Linux/macOS instructions or examples. Steps for installing and configuring SAP libraries, extracting archives, and setting up environment variables are all described using Windows tools and terminology, with no mention of Linux alternatives. This bias creates friction for Linux/macOS users, who must infer or research their own platform-specific steps.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific instructions, such as using bash scripts or OpenSSL for base64 encoding, and referencing appropriate directory paths.
  • Include examples for extracting .sar files using Linux tools (e.g., SAPCAR for Linux, tar), and clarify how to install SAP NCo libraries on non-Windows platforms if supported.
  • Document environment variable setup for Linux/macOS (e.g., using export in bash, and typical locations for assemblies/libraries).
  • When referencing tools like PowerShell, also provide bash or shell script alternatives.
  • Clarify platform support for SAP NCo and connectors, and explicitly state any Windows-only limitations.
  • Where screenshots or UI instructions are Windows-centric, note differences or provide guidance for Linux/macOS users.
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-12 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, particularly in the installation section. PowerShell commands and scripts are presented first and in detail, with Bash usage only described as a wrapper for PowerShell (requiring 'powershell' to be available on Linux/macOS). Output examples use Windows-style paths and environments. There is no mention of native Bash or shell alternatives for Linux/macOS users, and the workflow assumes Visual Studio Code, which is cross-platform but the instructions and screenshots are Windows-centric.
Recommendations
  • Provide native Bash or shell script examples for installing extensions, not just PowerShell invoked from Bash.
  • Include explicit instructions for Linux/macOS environments, such as path conventions and dependency installation.
  • Show output examples using Linux/macOS file paths and environments alongside Windows examples.
  • Clarify any Windows-only requirements, and offer alternatives or workarounds for Linux/macOS users.
  • Ensure screenshots and UI instructions reflect cross-platform usage, not just Windows.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for creating Microsoft Entra application identities using the Azure portal and PowerShell, but omits equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). PowerShell is highlighted as the only command-line option, and Windows-centric tools/patterns are referenced before any cross-platform alternatives. No Linux/macOS-specific guidance or parity is offered for command-line tasks.
Recommendations
  • Add Azure CLI examples for all PowerShell command sequences, especially for app registration and service principal creation.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide links to relevant CLI documentation.
  • Present cross-platform command-line options (Azure CLI) before or alongside PowerShell, not after.
  • Include notes or sections for Linux/macOS users, clarifying any differences in workflow or tool usage.
  • Ensure screenshots and instructions are not exclusively Windows/PowerShell-focused.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias, especially in troubleshooting and deployment sections. PowerShell scripts and commands are referenced for troubleshooting and Kubernetes management, with no equivalent Bash or Linux shell examples. Instructions such as 'Run Visual Studio Code as administrator' and port 445 for SMB are Windows-centric. The troubleshooting script is provided only as a PowerShell (.ps1) file, and commands for checking SMB CSI driver status are shown for Windows PowerShell and Command Prompt, with no Linux/macOS alternatives. The documentation does not mention Linux/macOS equivalents for these steps, nor does it provide parity in example commands or tooling.
Recommendations
  • Provide Bash and Linux/macOS shell equivalents for all PowerShell and Windows Command Prompt commands, especially for kubectl and helm usage.
  • Offer troubleshooting scripts in Bash (.sh) as well as PowerShell (.ps1), or document how to run the PowerShell script on non-Windows platforms.
  • Clarify whether Visual Studio Code administrator privileges are required on Linux/macOS, and provide platform-specific guidance.
  • Include explicit instructions and examples for Linux/macOS users in sections involving SMB file shares, port configuration, and deployment.
  • Review all screenshots and UI instructions to ensure they are not exclusively Windows-centric, or provide Linux/macOS alternatives where relevant.
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-12 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 its emphasis on Visual Studio (Windows-only) and related extensions as primary tools for map creation and management. Visual Studio Code is mentioned as a cross-platform alternative, but Windows tools and patterns (such as Visual Studio, registry edits, and DPI-awareness issues) are described first and in greater detail. There is no explicit mention of Linux/macOS-specific workflows, nor are there examples or troubleshooting steps tailored for those platforms. Azure Storage Explorer is cross-platform, but instructions and screenshots are Windows-centric.
Recommendations
  • Explicitly state platform compatibility for all recommended tools (e.g., Visual Studio Code is cross-platform, Visual Studio is Windows-only).
  • Provide Linux/macOS-specific instructions or troubleshooting steps where relevant (e.g., file upload, folder navigation, using Azure Storage Explorer on Linux/macOS).
  • Include screenshots and examples from Linux/macOS environments, especially for Visual Studio Code and Azure Storage Explorer.
  • List cross-platform tools (Visual Studio Code) before Windows-only tools (Visual Studio) in all sections.
  • Mention alternative CLI or scripting options for map and assembly management that work on Linux/macOS (e.g., Azure CLI, REST API usage).
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-12 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 .NET code as examples of running scripts from Logic Apps, but does not mention or provide parity for Linux/macOS scripting options such as Bash or Python. The 'Run code from your workflows' section lists PowerShell and .NET/C# specifically, which are traditionally Windows-centric technologies, without equivalent Linux/macOS examples. No explicit Linux tools or shell scripting options are referenced, and there are no examples or tutorials tailored to Linux users.
Recommendations
  • Add examples for running Bash scripts and Python scripts from Logic Apps workflows, highlighting cross-platform compatibility.
  • Explicitly mention that Logic Apps can execute scripts on Linux/macOS environments, and provide links to relevant tutorials.
  • When listing scripting options, present cross-platform tools (e.g., Bash, Python) alongside PowerShell and .NET, or in a neutral order.
  • Include notes or sections on how Linux/macOS users can set up and manage Logic Apps, especially for hybrid and self-hosted scenarios.
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-12 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, primarily through its focus on PowerShell scripting as the only example of custom code integration in workflows. There are no explicit Linux or bash shell script examples, nor is there mention of Linux/macOS-specific development tools or patterns. While Visual Studio Code is cross-platform, the scripting examples and terminology are Windows-centric, which may create friction for Linux/macOS users seeking parity.
Recommendations
  • Add examples for running bash shell scripts or Python scripts in Logic Apps workflows, alongside PowerShell and C#.
  • Explicitly mention that Visual Studio Code and the Logic Apps extension are supported on Linux and macOS, and provide any platform-specific setup notes if needed.
  • Include references to Linux/macOS command-line tools or scripting environments where relevant.
  • Clarify that workflow deployment and management can be performed from Linux/macOS environments, not just Windows.
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-12 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 exhibits a moderate Windows bias. Windows-specific instructions and tooling (e.g., PowerShell, Chocolatey, Windows Server, Windows SMB setup) are presented prominently, sometimes exclusively, or before Linux equivalents. For example, installation of kubectl and Helm is shown only via Chocolatey/PowerShell, and SMB file share setup is detailed for Windows but lacks equivalent Linux/NAS instructions. References to scripts (EnvironmentSetup.ps1) and execution policy changes are PowerShell-centric. Linux users are expected to adapt or infer steps, which may create friction.
Recommendations
  • Provide explicit Linux/macOS installation instructions for kubectl and Helm (e.g., apt, yum, Homebrew).
  • Include SMB file share setup steps for Linux (e.g., using Samba) and/or NAS devices.
  • Offer cross-platform script alternatives (e.g., Bash scripts) or clarify how to adapt PowerShell scripts for Linux/macOS.
  • When referencing tools like Chocolatey, also mention Linux/macOS package managers.
  • Ensure all examples (especially CLI commands) are validated for Linux/macOS environments.
  • Present platform-neutral instructions first, or in parallel, rather than Windows-first.
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-12 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 bias toward Windows and Microsoft-centric environments. All examples, screenshots, and workflow steps are shown using the Azure portal and Microsoft services (Office 365 Outlook, Microsoft Entra ID, etc.), with no mention of Linux/macOS tools, CLI alternatives, or cross-platform approaches. There are no examples or instructions for performing equivalent tasks outside the Azure portal or with non-Microsoft connectors. The documentation assumes users are working in a Windows/Microsoft ecosystem and does not provide parity for Linux/macOS users or those using command-line interfaces.
Recommendations
  • Include CLI-based instructions (e.g., using Azure CLI, PowerShell Core, or REST API calls) that work on Linux/macOS as well as Windows.
  • Provide examples for setting up OBO flow using non-Microsoft connectors or generic OAuth 2.0 flows, where possible.
  • Add screenshots or step-by-step instructions for performing tasks in cross-platform environments, such as using VS Code on Linux/macOS.
  • Explicitly mention platform requirements and alternatives for users who do not use the Azure portal or Windows-based tools.
  • Clarify whether all steps can be completed in browser-only environments, and note any platform-specific limitations.
GitHub Create Pull Request
Logic Apps Differences between Standard and Consumption logic apps .../articles/logic-apps/single-tenant-overview-compare.md
Medium Priority View Details →
Scanned: 2026-01-12 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, primarily by referencing Windows-specific hosting options (App Service Environment v3 - Windows plans only) and mentioning them before any Linux alternatives. There is no explicit mention of Linux hosting or deployment scenarios, nor are Linux-specific instructions or examples provided. The documentation also omits details about running or deploying Logic Apps Standard on Linux-based App Service plans, which are supported in Azure but not discussed here. While development tooling (Visual Studio Code, Azure CLI) is cross-platform, the hosting and deployment guidance is Windows-centric.
Recommendations
  • Explicitly mention and document Linux-based App Service plans as hosting options for Logic Apps Standard, where supported.
  • Provide examples or guidance for deploying Logic Apps Standard to Linux environments, including any differences or considerations.
  • Add notes or sections clarifying cross-platform compatibility for development and deployment tools (e.g., Azure CLI, Visual Studio Code).
  • Ensure parity in documentation by listing Linux options alongside Windows options, not only referencing 'Windows plans only'.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →