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 126-150 of 339 flagged pages
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-08 00:53
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 Windows bias in several ways: PowerShell is the primary and only detailed CLI example for installing the connector, with Bash usage simply wrapping PowerShell rather than providing a native Bash or shell script. Output examples and file paths use Windows conventions (e.g., C:\Users\...), and references to tools like Visual Studio Code are made without mention of Linux-specific alternatives or considerations. There is no explicit Linux-native installation or troubleshooting guidance, and the workflow assumes a Windows-centric development environment.
Recommendations
  • Provide native Bash or shell script examples for Linux/macOS users, rather than instructing them to run PowerShell scripts via Bash.
  • Include Linux/macOS file path conventions in output and instructions, or clarify cross-platform differences.
  • Mention and document any Linux-specific prerequisites, such as .NET SDK installation steps for Linux, and how to install Visual Studio Code and required extensions on Linux.
  • Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, environment variables, path separators).
  • Explicitly state cross-platform compatibility for all tools and scripts, and provide parity in examples for both Windows and Linux/macOS environments.
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-08 00:53
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 in several areas: troubleshooting and cluster commands are shown exclusively using Windows PowerShell, with no Linux shell equivalents; instructions often reference running Visual Studio Code as administrator (a Windows concept) and opening ports in a way that assumes Windows environments; troubleshooting scripts are provided only as PowerShell (.ps1); and deployment steps and screenshots are focused on the Azure portal, which is most commonly used on Windows. There are no explicit Linux shell (bash) or cross-platform CLI examples, and Linux-specific deployment or troubleshooting patterns are missing.
Recommendations
  • Provide Linux shell (bash) equivalents for all PowerShell commands, especially for kubectl, az, and helm usage.
  • Offer troubleshooting scripts in bash (.sh) format alongside PowerShell (.ps1), or provide cross-platform guidance.
  • Clarify instructions for running Visual Studio Code with elevated privileges on Linux and macOS (e.g., using sudo).
  • Include notes or examples for opening required ports and accessing SMB shares on Linux systems.
  • Add screenshots and step-by-step instructions for using the Azure CLI and kubectl from Linux/macOS terminals.
  • 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-visual-studio-code.md ...c-apps/create-standard-workflows-visual-studio-code.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates several forms of Windows bias. Windows-specific tools and patterns (such as Windows Defender Firewall, registry edits, and .exe file references) are mentioned first or exclusively. Troubleshooting and configuration steps often reference Windows locations, registry keys, and .exe files, with Linux/macOS alternatives either missing, less detailed, or mentioned secondarily. Some examples and instructions (e.g., firewall prompts, registry edits, file paths) are Windows-centric, and PowerShell/Windows command-line tools are referenced without Linux equivalents. While some Linux/macOS notes are present, they are less thorough and often appended as afterthoughts.
Recommendations
  • Provide Linux and macOS equivalents for all Windows-specific instructions, including firewall configuration, registry edits, and file paths.
  • Ensure that troubleshooting steps (such as fixing URI length issues) include clear, actionable guidance for Linux/macOS users (e.g., web server config changes instead of registry edits).
  • When referencing tools (e.g., ngrok.exe), mention cross-platform usage and provide Linux/macOS installation and usage instructions equally.
  • Avoid presenting Windows instructions first by default; instead, group platform-specific instructions together or present them in parallel.
  • Include screenshots and examples from Linux/macOS environments where applicable.
  • Audit all references to .exe files, Windows-specific dialogs, and registry keys to ensure Linux/macOS users are not left without guidance.
  • Expand notes and examples for Linux/macOS beyond brief mentions, ensuring parity in detail and clarity.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting Azure Portal (web UI) instructions first, which is most commonly accessed from Windows environments. Azure PowerShell is mentioned as a supported method for creating and deleting integration accounts, but there is no mention of Linux-specific shell environments (e.g., Bash) or parity for PowerShell commands on Linux. The Azure CLI examples are platform-neutral, but there is an implicit prioritization of Windows-centric tools and workflows (Portal, PowerShell) throughout the document. There are no explicit Linux examples, nor is there any discussion of Linux-specific considerations or alternative tools.
Recommendations
  • Explicitly mention that Azure CLI commands work equally on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh) where appropriate.
  • Add instructions or notes for using Azure PowerShell on Linux and macOS, or clarify its cross-platform support.
  • Where PowerShell is referenced, provide equivalent Bash or shell script examples for Linux users.
  • Include screenshots or references to Azure Portal access from non-Windows platforms (e.g., Chrome on Ubuntu).
  • Review and balance the order of presentation so that platform-neutral or Linux-friendly methods (CLI, REST API) are listed before or alongside Windows-centric tools.
  • Add a section or note addressing Linux-specific considerations for integration account management, if any exist.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All installation instructions, screenshots, and operational details are focused exclusively on Windows environments. The gateway is described as a 'Windows service', and only Windows-specific tools (such as PowerShell cmdlets) are referenced for automation. There are no examples, instructions, or even mentions of Linux or cross-platform installation or management. The documentation assumes the user is operating on Windows, with no guidance for Linux or macOS users.
Recommendations
  • Add explicit information about Linux and macOS support for the on-premises data gateway, if available. If not supported, state this clearly.
  • If Linux installation is possible, provide step-by-step instructions, including command-line examples and screenshots for Linux environments.
  • Include Linux equivalents for Windows-specific tools, such as PowerShell cmdlets (e.g., Bash scripts, CLI commands).
  • Mention any limitations or differences in gateway functionality between Windows and Linux.
  • Ensure that prerequisites and troubleshooting sections address Linux-specific considerations (e.g., service management, permissions, firewall configuration).
  • If the gateway is Windows-only, add a prominent note at the start of the document to inform non-Windows users.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as the first automation tool for creating and deploying logic apps, followed by Azure CLI and REST APIs. There are no explicit Linux-specific examples, nor are Linux shell commands or editors (such as Vim, nano, or shell scripting) mentioned. The workflow for editing JSON is focused on Visual Studio and Visual Studio Code, both of which are more commonly associated with Windows environments, and there is no mention of Linux-native editors or tools. The page does not provide parity for Linux users in terms of examples or tooling guidance.
Recommendations
  • List Azure CLI before Azure PowerShell when describing automation options, as CLI is cross-platform and more commonly used on Linux.
  • Include examples or guidance for editing workflow JSON using Linux-native editors (e.g., Vim, nano, Emacs) and command-line tools.
  • Provide sample shell commands for deploying logic apps using Azure CLI on Linux.
  • Explicitly mention that Visual Studio Code is available on Linux and macOS, and provide instructions for those platforms.
  • Add a section or tips for Linux users, such as using the Azure portal in a browser or using REST APIs from curl or other Linux tools.
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-08 00:53
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 through the exclusive mention of Azure PowerShell for template creation, with no mention of cross-platform or Linux-native tools such as Azure CLI or Bash scripting. The only explicit tooling guidance is for PowerShell, and there are no examples or instructions for Linux or macOS users. This may lead Linux users to feel unsupported or unclear about their options for automating Logic App deployments.
Recommendations
  • Add equivalent Azure CLI examples for creating and deploying Logic App ARM templates, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • When mentioning PowerShell, also mention that Azure CLI and Bash scripts can be used, and provide links or examples.
  • Avoid suggesting PowerShell as the only or primary automation tool; instead, present both PowerShell and CLI options side by side.
  • Explicitly state that all JSON templates and parameter files are platform-agnostic and can be used from any OS.
  • Include a 'Platform compatibility' note clarifying that all deployment methods (PowerShell, CLI, Portal, REST API) are available on Windows, Linux, and macOS.
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-08 00:53
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 Windows-centric, and no Linux or cross-platform alternatives (such as Bash, Azure CLI, or scripting for Linux/macOS) are mentioned. The installation and usage instructions assume a Windows environment, and there are no examples or guidance for users on Linux or macOS.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash for Linux/macOS users.
  • Mention cross-platform compatibility of tools (e.g., whether LogicAppTemplate or ARMClient can run on Linux/macOS, and how).
  • Add installation instructions for required tools on Linux/macOS (e.g., using pip, npm, or native package managers).
  • Include sample commands for template generation and deployment using Bash or other non-Windows shells.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and offer alternatives where possible.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently as a deployment method, with explicit PowerShell script examples and references. The use of PowerShell for OAuth authorization is suggested, and no Linux-specific alternatives (such as Bash scripts or cross-platform automation tools) are provided. Windows-centric tools and patterns (PowerShell, virtual machines with browser sessions) are mentioned without Linux equivalents. In several sections, Windows/PowerShell approaches are described before CLI or platform-neutral options.
Recommendations
  • Provide equivalent Bash or shell script examples for deployment and OAuth authorization, highlighting cross-platform compatibility.
  • Mention that Azure CLI is available on both Windows and Linux, and consider listing CLI examples before PowerShell to avoid implicit Windows-first ordering.
  • For OAuth authorization, suggest Linux-friendly automation methods (e.g., using Azure CLI, REST API, or headless browser tools) alongside PowerShell.
  • Explicitly state platform compatibility for each tool or script, and avoid implying that deployment or authorization must be done on Windows.
  • Add notes or sections for Linux/macOS users, including troubleshooting tips and environment setup instructions.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-enterprise-integration-b2b-business-continuity.md ...ic-apps-enterprise-integration-b2b-business-continuity.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively recommending PowerShell cmdlets for incrementing control numbers during disaster recovery and failback scenarios. No Linux or cross-platform CLI alternatives (such as Azure CLI or REST API) are provided for these critical steps. The documentation assumes the use of Windows tools and does not mention or provide parity for Linux users, nor does it clarify whether the PowerShell cmdlets are available cross-platform.
Recommendations
  • Provide equivalent Azure CLI commands or REST API instructions for incrementing control numbers, ensuring Linux and macOS users can perform disaster recovery steps without PowerShell.
  • Explicitly state whether the referenced PowerShell cmdlets are available and supported on Linux and macOS (via PowerShell Core), or provide guidance for installation and usage on those platforms.
  • Add example workflows or scripts for Linux environments, or clarify that all steps can be performed from any OS using cross-platform tools.
  • Where possible, mention cross-platform tools (Azure CLI, REST API) before or alongside Windows/PowerShell tools to avoid Windows-first bias.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively recommending Visual Studio (a Windows-only tool) and its extension for creating maps and schemas, with no mention of Linux-compatible alternatives. Troubleshooting steps reference Windows-specific registry edits and DPI settings. While Visual Studio Code is mentioned as an option for managing and deploying resources, there are no examples or guidance for Linux users regarding map/schema creation or equivalent tooling. PowerShell is referenced for resource management, but no Linux shell or CLI examples are provided.
Recommendations
  • Provide guidance or examples for creating maps and schemas using cross-platform tools or command-line utilities available on Linux.
  • Include Azure CLI examples for resource management and deployment, alongside PowerShell, to ensure parity for Linux users.
  • Mention and link to any available Linux-compatible tools or workflows for B2B artifact creation and management.
  • Clarify which steps are Windows-specific and offer Linux/macOS alternatives where possible.
  • Consider adding troubleshooting steps relevant to Linux environments, not just Windows registry or DPI settings.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-enterprise-integration-maps.md ...s/logic-apps/logic-apps-enterprise-integration-maps.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools (Visual Studio, Azure Storage Explorer), providing detailed instructions for these tools, and omitting equivalent Linux alternatives or cross-platform command-line options. Visual Studio and its extensions are emphasized for map creation and management, with no mention of Linux-based IDEs or CLI workflows. Azure Storage Explorer is described as the main tool for managing blob storage, but alternatives for Linux users (such as az CLI or web portal) are not discussed. The documentation does not provide parity for Linux users in terms of tooling or workflow examples.
Recommendations
  • Include instructions for managing maps and assemblies using cross-platform tools such as the Azure CLI (az storage, az logicapp), REST API, or the Azure portal, which are accessible from Linux, macOS, and Windows.
  • Mention Linux-compatible IDEs (e.g., VS Code) and extensions for map creation, and clarify that VS Code is available on Linux and macOS.
  • Provide examples for uploading/downloading maps and assemblies using command-line tools (az CLI, curl, etc.) and REST API calls.
  • List alternatives to Azure Storage Explorer for Linux users, such as using the Azure portal or az CLI for blob management.
  • Ensure that all tool recommendations and screenshots are either cross-platform or have Linux/macOS equivalents, and avoid assuming Visual Studio or Windows-only workflows as the default.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-examples-and-scenarios.md ...ticles/logic-apps/logic-apps-examples-and-scenarios.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page references PowerShell scripting as a supported language for running code from workflows, but does not mention Bash, shell scripts, or other Linux-native scripting options. There are no examples or references to Linux-specific tools, patterns, or deployment/management workflows. The documentation implicitly assumes Windows familiarity by highlighting PowerShell and omitting Linux equivalents.
Recommendations
  • Add examples and documentation for running Bash or shell scripts from Logic Apps workflows, alongside PowerShell.
  • Explicitly mention Linux support and provide parity in scripting and automation examples (e.g., show how to trigger Bash scripts, use Linux containers, or interact with Linux-based endpoints).
  • Include references to Linux-native tools (such as SSH, cron, or systemd) in relevant sections, especially in deployment, automation, and monitoring scenarios.
  • Ensure that tutorials and walkthroughs provide both Windows and Linux command-line examples where applicable.
  • Clarify cross-platform compatibility for development tools (e.g., Visual Studio Code) and deployment pipelines.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-overview.md ...s/blob/main/articles/logic-apps/logic-apps-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page for Azure Logic Apps demonstrates a moderate Windows bias. Windows-specific technologies (PowerShell, .NET, C# scripts, App Service Environment v3 - Windows plans only) are mentioned explicitly and sometimes exclusively. PowerShell scripting is highlighted as a supported language for workflow code, but there is no mention of Bash or other Linux-native scripting languages. The documentation refers to deployment environments and features (ASE v3) as 'Windows plans only' without clarifying Linux support or alternatives. Examples and tooling references (such as Azure PowerShell) are given without Linux equivalents (e.g., Bash, shell scripts), and there are no explicit Linux command-line examples or mentions of Linux-specific patterns.
Recommendations
  • Add examples and explicit support statements for Linux environments, such as App Service Environment v3 Linux plans, if available.
  • Include Bash or shell script support and examples alongside PowerShell, especially in sections discussing custom code and scripting.
  • Mention and provide examples for Azure CLI usage in Linux environments, not just Azure PowerShell.
  • Clarify whether features (such as running custom code, deployment options) are available on Linux, and provide parity guidance.
  • Where scripting languages are listed (JavaScript, .NET, C#, PowerShell), add Bash or Python if supported, or clarify platform limitations.
  • Ensure that tooling recommendations (Visual Studio Code, Azure portal) are presented as cross-platform, and mention Linux compatibility.
  • If certain features are Windows-only, explicitly state this and provide Linux alternatives or workarounds where possible.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/manage-logic-apps-with-visual-studio.md ...les/logic-apps/manage-logic-apps-with-visual-studio.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows-specific tools and workflows, particularly Visual Studio and Cloud Explorer, with no mention of Linux-compatible alternatives or cross-platform options. All examples and instructions assume the use of Visual Studio on Windows, and prerequisites include Windows-only tools like Visual Studio and Cloud Explorer. Azure PowerShell is listed, but only in the context of Visual Studio, and there are no references to Linux editors, CLI workflows, or VS Code. This creates a strong Windows bias and excludes Linux users from following the documented procedures.
Recommendations
  • Add equivalent instructions for managing logic apps using cross-platform tools such as Visual Studio Code, Azure CLI, or Azure PowerShell outside Visual Studio.
  • Include Linux-compatible workflows and examples, such as editing Resource Manager templates with VS Code or other editors available on Linux.
  • Mention and provide guidance for using Azure Portal, Azure CLI, and VS Code for logic app management and deployment, ensuring parity for Linux and macOS users.
  • Clearly state platform limitations and suggest alternative approaches for non-Windows environments.
  • Where screenshots are provided, include examples from cross-platform tools (e.g., VS Code, Azure CLI) alongside Visual Studio.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/multi-region-disaster-recovery.md .../articles/logic-apps/multi-region-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
πŸ”§ Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its references to PowerShell scripts as the example method for activating logic apps in disaster recovery scenarios. There is no mention of Linux-native tools, such as Bash scripts, Azure CLI, or automation via Linux shell environments. The documentation also refers to installing the on-premises data gateway on a 'local computer' without clarifying cross-platform support, which may imply a Windows-centric approach. Examples and guidance for scripting and automation are Windows-first, and Linux equivalents are missing.
Recommendations
  • Include examples using Azure CLI and Bash scripts for activating logic apps and managing failover, alongside PowerShell.
  • Clarify that the on-premises data gateway can be installed on both Windows and Linux systems, if supported, and provide platform-specific instructions.
  • When mentioning scripting or manual operations, offer both PowerShell and Bash/CLI alternatives, and present them side-by-side or in a neutral order.
  • Explicitly state cross-platform compatibility for all tools and processes, and link to Linux-specific documentation where available.
  • Review and update all automation and scripting guidance to ensure Linux users are equally supported and not required to use Windows tools.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/power-automate-migration.md ...b/main/articles/logic-apps/power-automate-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively mentioning PowerShell as the scripting language for custom code in workflows, without referencing Linux-native alternatives such as Bash or Python. All code execution examples focus on .NET, C#, and PowerShell, which are traditionally Windows-centric technologies. There are no examples or guidance for Linux users, such as using Bash scripts or Linux CLI tools, nor is there mention of Linux development environments or workflows.
Recommendations
  • Add examples for running Bash scripts and Python code in Standard workflows to provide parity for Linux users.
  • Mention and illustrate development workflows using Linux-based environments (e.g., VS Code on Ubuntu, containerized development).
  • Include references to Linux-native tools and patterns where applicable, such as using SSH, cron jobs, or Linux file system operations.
  • Clarify platform compatibility for custom code execution (e.g., whether Bash/Python is supported and how to configure it).
  • Ensure that scripting and automation examples are balanced between Windows and Linux, or explicitly state platform limitations.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/quickstart-create-logic-apps-with-visual-studio.md ...pps/quickstart-create-logic-apps-with-visual-studio.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation is heavily focused on Windows and Visual Studio, with all examples and instructions assuming a Windows environment. Prerequisites and steps reference only Windows tools (Visual Studio, PowerShell), and there are no Linux or cross-platform alternatives provided. The use of PowerShell for deployment prompts and the lack of mention of Linux-compatible editors or CLI workflows further reinforce the Windows bias.
Recommendations
  • Add equivalent instructions for Linux and macOS users, such as using Visual Studio Code or Azure CLI for Logic Apps development and deployment.
  • Provide examples using cross-platform tools (e.g., Azure CLI, VS Code) alongside or before Windows-specific tools.
  • Clarify which steps are Windows-only and offer alternatives for non-Windows environments.
  • Include Linux/macOS-specific prerequisites and installation steps for required SDKs and tools.
  • Reference documentation for managing Logic Apps with Azure CLI or VS Code in the main workflow, not just as side notes.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/create-rules-engine-project.md ...logic-apps/rules-engine/create-rules-engine-project.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Microsoft tools such as Microsoft Rules Composer and BizTalk Server, which are only available on Windows. All screenshots and instructions are based on Visual Studio Code running in a Windows environment (e.g., backslash paths, .NET Framework net472, Windows-style terminal commands). There are no Linux-specific instructions, examples, or troubleshooting notes, and the prerequisites and workflow steps do not mention Linux compatibility or alternatives.
Recommendations
  • Explicitly state Linux support or limitations for Microsoft Rules Composer and BizTalk Server export steps. If unavailable on Linux, suggest alternatives or workarounds.
  • Provide Linux-specific instructions for installing prerequisites, running Visual Studio Code, and using the terminal (e.g., use forward slashes in paths, show bash commands).
  • Clarify .NET version requirements and compatibility with Linux (e.g., .NET Core/5/6+ vs. .NET Framework). If net472 is required, note that it is Windows-only and suggest cross-platform alternatives if possible.
  • Include screenshots or notes for Visual Studio Code on Linux/macOS, and highlight any differences in UI or workflow.
  • Add troubleshooting tips for common Linux issues (e.g., file permissions, case sensitivity, dependency installation).
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/set-up-sql-database-storage-standard.md ...les/logic-apps/set-up-sql-database-storage-standard.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 consistently referencing Windows-based App Service plans as the only supported hosting option, explicitly stating that Linux-based plans are not supported. Windows tools and patterns (such as SQL Server Management Studio, MSI installers, and Windows Authentication) are mentioned, while Linux equivalents are absent. There are no examples or guidance for Linux-based development, deployment, or SQL server hosting, and the prerequisites and setup instructions focus on Windows environments and tools.
Recommendations
  • Clarify whether Linux-based App Service plans will be supported in the future, and if not, explain the technical reasons.
  • Add explicit guidance for users who want to develop or host on Linux, including any supported alternatives or workarounds.
  • Include examples for connecting to SQL databases hosted on Linux, such as using SQL Server on Linux or Azure SQL Edge.
  • Reference cross-platform tools (e.g., Azure CLI, Docker, VS Code on Linux/macOS) and provide installation instructions for non-Windows environments.
  • Mention authentication methods and connection string formats relevant for Linux environments.
  • If Visual Studio Code is the recommended IDE, clarify its cross-platform support and provide steps for Linux/macOS users.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/set-up-standard-workflows-hybrid-deployment-requirements.md ...t-up-standard-workflows-hybrid-deployment-requirements.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 tools (PowerShell, Chocolatey) are used for key steps such as installing kubectl and Helm, and Windows SMB file share setup is described in detail before alternatives. PowerShell commands and references are prominent, and the main automation script is provided in PowerShell (.ps1). There are no equivalent Linux shell scripts or package manager instructions for installing kubectl/Helm, and Linux SMB setup is not covered. While Azure CLI is used for most commands, Windows-centric patterns and tools are mentioned first or exclusively in several places.
Recommendations
  • Provide Linux equivalents for all PowerShell and Chocolatey installation steps (e.g., apt, yum, or curl for kubectl and Helm).
  • Offer a Bash shell script alongside the PowerShell script for environment setup.
  • Include instructions for setting up SMB file shares on Linux (e.g., using Samba), not just Windows.
  • Ensure that examples and tooling references are presented in a cross-platform manner, or at least alternate between Windows and Linux.
  • Clarify which steps are OS-specific and provide guidance for both Windows and Linux users.
  • Add troubleshooting notes for common Linux issues (e.g., SELinux, firewall, mount permissions) when connecting to SMB shares.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/single-tenant-overview-compare.md .../articles/logic-apps/single-tenant-overview-compare.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 primarily through repeated references to Windows-specific hosting options (e.g., App Service Environment v3 'Windows plans only'), and by omitting explicit Linux hosting or deployment examples. The documentation mentions development tools (Visual Studio Code, Azure portal, Azure CLI) in a cross-platform context, but when discussing hosting and deployment, it exclusively highlights Windows plans and does not provide parity for Linux environments. There are no examples or guidance for deploying Standard Logic Apps to Linux-based App Service plans or containers, nor are Linux-specific patterns or troubleshooting steps mentioned.
Recommendations
  • Add explicit examples and documentation for deploying Standard Logic Apps to Linux-based App Service plans, containers, or other non-Windows environments.
  • Where hosting options are discussed, mention Linux plans and containerization alongside Windows plans, and clarify any feature parity or limitations.
  • Include troubleshooting steps, deployment guides, and tool usage for Linux environments (e.g., using Bash, Linux-based Azure CLI, Docker).
  • Review all references to 'Windows plans only' and provide alternative guidance or links for Linux users.
  • Ensure that any code snippets, screenshots, or step-by-step instructions are available for both Windows and Linux platforms.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/tutorial-process-email-attachments-workflow.md ...ic-apps/tutorial-process-email-attachments-workflow.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments and tooling. Windows-specific tools like Microsoft Azure Storage Explorer are required, and instructions for in-portal editing of Azure Functions are only available for Windows. PowerShell is mentioned before Azure CLI in several places, and there are no explicit Linux or cross-platform alternatives for key steps such as storage management or function development. The tutorial assumes the use of Office 365 Outlook, a Microsoft-centric email provider, and does not provide parity for Linux users or those using non-Microsoft tools.
Recommendations
  • Provide explicit Linux and macOS instructions for all steps, including storage account and container creation, and function development.
  • Mention and demonstrate Azure CLI usage before or alongside PowerShell, as CLI is cross-platform.
  • Include alternatives to Microsoft Azure Storage Explorer, such as using az CLI or third-party cross-platform tools.
  • Clarify which steps can be performed on Linux/macOS and provide screenshots or terminal examples for those platforms.
  • Highlight any limitations for non-Windows users (e.g., in-portal editing) and offer workarounds or local development instructions.
  • Expand email provider examples to include open-source or non-Microsoft options, and provide connector parity guidance.
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: 2025-07-19 13:51
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the primary tool for creating Logic App templates, without mentioning or providing examples for equivalent Linux-friendly tools such as Azure CLI or Bash scripting. The only explicit tooling guidance is for Azure PowerShell, which is most commonly used on Windows. There are no Linux or cross-platform command-line examples, nor are Linux-native tools or workflows discussed. This may lead Linux or macOS users to believe that Windows is required or preferred for these tasks.
Recommendations
  • Add Azure CLI examples alongside or in place of Azure PowerShell references, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • When mentioning tools, list Azure CLI first or equally with PowerShell to avoid the impression of Windows-first bias.
  • Provide explicit Bash or shell script examples for common deployment tasks, such as deploying ARM templates or managing parameters files.
  • Include a note clarifying that all template and deployment operations can be performed on Linux, macOS, and Windows, and link to relevant cross-platform documentation.
  • Where possible, avoid referencing Windows-specific tools (e.g., PowerShell modules) as the only option for template generation or deployment.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/azure-integration-services-choose-capabilities.md ...apps/azure-integration-services-choose-capabilities.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing BizTalk Server and SQL Server Integration Services (SSIS)β€”both Windows-centric technologiesβ€”without mentioning Linux or cross-platform alternatives. Migration scenarios and integration examples focus exclusively on moving from these Windows tools to Azure services, with no discussion of Linux-based integration platforms or data tools. No Linux-specific examples, tools, or migration paths are provided.
Recommendations
  • Include references to Linux-based integration platforms (e.g., Apache Camel, Talend, MuleSoft) and discuss migration or integration strategies for users coming from those environments.
  • Mention cross-platform data integration tools and how they can be lifted and shifted or integrated with Azure Data Factory.
  • Provide examples or case studies for users migrating from Linux or open-source middleware to Azure Integration Services.
  • Balance the discussion of Windows tools (BizTalk, SSIS) with Linux/open-source equivalents to ensure parity and inclusivity.
GitHub Create Pull Request
← Previous Page 6 of 14 Next →