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 101-125 of 339 flagged pages
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-09 00:34
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 environments by exclusively referencing PowerShell cmdlets for critical disaster recovery operations (such as incrementing control numbers) and omitting equivalent instructions or examples for Linux or cross-platform environments. No Bash, Azure CLI, or REST API alternatives are provided, and the only automation tooling mentioned is PowerShell, which is primarily associated with Windows.
Recommendations
  • Provide equivalent examples using Azure CLI commands for all PowerShell cmdlet instructions, ensuring Linux and macOS users can follow along without needing PowerShell.
  • Include REST API references and sample requests for operations currently described only with PowerShell.
  • Explicitly mention cross-platform options (e.g., Bash scripts, Azure CLI, REST API) wherever automation or scripting is discussed.
  • Add notes or sections clarifying that all disaster recovery steps can be performed from Linux, macOS, or Windows, and link to relevant cross-platform documentation.
  • Where PowerShell is referenced, add a parallel example for Azure CLI or Bash, and indicate which platforms each method supports.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools (Visual Studio, Azure Storage Explorer), providing detailed instructions for Visual Studio and Azure portal (both Windows-focused), and omitting explicit Linux alternatives or CLI-based workflows. Visual Studio Code is mentioned, but only in the context of its Data Mapper extension, with no parity for Linux-native or cross-platform approaches for tasks like map creation, assembly upload, or artifact management. There are no examples using Linux shell, Azure CLI, or cross-platform automation tools.
Recommendations
  • Add explicit instructions and examples for Linux users, such as using Azure CLI, PowerShell Core (cross-platform), or REST API for uploading maps and assemblies.
  • Include references to Linux-compatible tools for managing Azure resources (e.g., azcopy, Azure CLI, REST API calls) alongside or before Windows GUI tools.
  • Provide parity in map creation workflows by mentioning open-source or cross-platform editors and tools (e.g., VS Code on Linux, XML editors) and how to use them for Logic Apps.
  • Clarify that Visual Studio Code and Azure portal are available on Linux and macOS, and provide any platform-specific caveats.
  • Add sample commands and screenshots from Linux environments where possible, especially for file uploads, artifact management, and project structure.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows-specific tools and workflows, particularly Visual Studio and Cloud Explorer, with no mention of Linux or cross-platform alternatives. All examples and instructions assume the use of Visual Studio on Windows, and prerequisites list only Windows tools. Azure PowerShell is mentioned, but no Linux-compatible editors or command-line alternatives are provided. There is no guidance for users on Linux or macOS platforms.
Recommendations
  • Include instructions and examples for managing logic apps using cross-platform tools such as Visual Studio Code, Azure CLI, or other editors available on Linux and macOS.
  • Provide parity for Linux users by listing prerequisites and setup steps for Linux environments (e.g., installing Azure CLI, using VS Code extensions).
  • Add examples for deploying, editing, and managing logic apps using Azure CLI or REST API, which are platform-agnostic.
  • Clearly indicate which steps or tools are Windows-only and offer alternatives for other operating systems.
  • Consider restructuring the documentation to present cross-platform options first, or at least alongside Windows-specific instructions.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific concepts, tools, and patterns (such as PowerShell, App Service Environment v3 'Windows plans only', and BizTalk Server) are mentioned explicitly and sometimes before Linux or cross-platform equivalents. Examples and instructions reference Windows-centric technologies (PowerShell, BizTalk, Office 365) without providing Linux alternatives or parity. There is a lack of explicit Linux-focused examples, tools, or guidance, and the documentation does not mention Linux-specific deployment scenarios or scripting options (e.g., Bash, shell scripts) alongside PowerShell.
Recommendations
  • Add Linux-specific examples and instructions, such as using Bash or shell scripts in workflows, and clarify support for Linux hosting environments.
  • When mentioning scripting support (e.g., PowerShell, .NET, C#), also mention Bash, Python, or other Linux-friendly options if supported.
  • Clarify whether App Service Environment v3 supports Linux plans and provide guidance for Linux users if available.
  • Provide parity in examples and tooling references, such as including Azure CLI commands alongside PowerShell, and referencing Linux-compatible connectors and deployment scenarios.
  • Explicitly mention Linux support in workflow hosting, deployment, and management sections, and link to Linux-focused documentation where relevant.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through references to Windows-centric tools and patterns. For example, on-premises data gateway installation is described as being performed on a 'local computer' without clarifying cross-platform support, implicitly suggesting Windows. The only explicit scripting example for manual failover mentions PowerShell, with no mention of Bash or Linux alternatives. There are no examples or guidance for Linux-based automation, nor are Linux-native tools or patterns discussed. Windows terminology and tools (PowerShell, local computer) are mentioned before or instead of Linux equivalents.
Recommendations
  • Provide explicit examples for Linux environments, such as Bash scripts for activating secondary logic apps.
  • Clarify that on-premises data gateway installation is supported on both Windows and Linux, and link to cross-platform installation guides.
  • When referencing scripting or automation, mention both PowerShell and Bash/CLI alternatives, and provide sample commands for each.
  • Avoid using 'local computer' in a way that implies Windows; specify platform requirements or options.
  • Add notes or sections highlighting considerations for Linux-based deployments and automation, ensuring parity in guidance.
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-09 00:34
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 oriented toward Windows development environments, specifically Visual Studio on Windows. All examples, screenshots, and instructions assume use of Visual Studio (a Windows-only IDE), and tools like Azure PowerShell are referenced without mention of cross-platform alternatives. There are no Linux or macOS equivalents or instructions, and no parity for development workflows outside Windows. The use of Windows filesystem paths and reliance on Visual Studio extensions further reinforce the Windows bias.
Recommendations
  • Provide equivalent instructions and examples for Linux and macOS users, using Visual Studio Code or other cross-platform editors.
  • Include Azure CLI examples for deployment and management, as CLI is cross-platform.
  • Reference cross-platform tools (e.g., VS Code, Azure CLI, REST API) alongside or before Windows-specific tools.
  • Add screenshots and step-by-step guides for Linux/macOS environments.
  • Explicitly state platform requirements and offer alternatives for non-Windows users.
  • Avoid assuming PowerShell is available; suggest Bash or other shells where appropriate.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a Windows bias by exclusively referencing Microsoft tools (Microsoft Rules Composer, BizTalk Server) that are only available on Windows, and by providing instructions and screenshots that implicitly assume a Windows environment (e.g., use of backslashes in paths, .NET Framework targeting net472, and Windows-style terminal commands). There are no examples or guidance for Linux or macOS users, nor are cross-platform alternatives mentioned for key steps such as rule authoring, exporting, or debugging. The prerequisites and workflow are centered around Windows-only tooling, with no mention of Linux compatibility or equivalent open-source tools.
Recommendations
  • Explicitly state platform requirements and limitations at the start of the documentation, clarifying if Windows is required for any steps.
  • Provide Linux/macOS equivalents or alternatives for all steps, especially for rule authoring and exporting (e.g., suggest cross-platform editors, .NET Core/6+ targeting, or open-source rule engines if available).
  • Include terminal commands and file path examples using both Windows and Linux/macOS conventions (e.g., use forward slashes, show bash/zsh commands).
  • Mention whether Microsoft Rules Composer and BizTalk Server steps can be skipped or replaced for non-Windows users, or provide guidance for those scenarios.
  • Add screenshots and instructions for Visual Studio Code usage on Linux/macOS, and clarify any differences in workflow or debugging.
  • If certain features are Windows-only, suggest workarounds or alternatives for Linux users, or provide links to relevant resources.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/set-up-devops-deployment-single-tenant-azure-logic-apps.md ...et-up-devops-deployment-single-tenant-azure-logic-apps.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows-specific instructions and examples before Linux equivalents, especially in sections such as 'Check pip installation' and 'Check environment and CLI version'. The guidance for checking pip and running commands is explicitly targeted at Windows and Mac, with no mention of Linux. There are no Linux-specific command-line examples, nor are there instructions tailored for Linux environments (e.g., bash shell, package managers like apt/yum). Additionally, references to tools and patterns (such as Visual Studio Code and Azure portal) are platform-agnostic, but the step-by-step instructions and troubleshooting tips are Windows-centric.
Recommendations
  • Add explicit Linux examples for command-line operations, such as pip installation, checking pip version, and Azure CLI usage.
  • Include Linux-specific instructions for installing prerequisites (e.g., using apt, yum, or snap for Azure CLI and Python/pip).
  • Provide bash shell command examples alongside Windows/Mac command prompt instructions.
  • Mention Linux as a supported platform in all relevant sections, and ensure parity in troubleshooting and setup guidance.
  • Where possible, use cross-platform language (e.g., 'open a terminal') and provide OS-specific tabs or callouts for commands.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively supporting and referencing Windows-based App Service plans, omitting Linux-based plans, and by prioritizing Windows tools and patterns such as SQL Server Management Studio (SSMS), Visual Studio Code, and MSI installers. There are no examples or instructions for Linux environments, and Linux-based hosting is explicitly unsupported.
Recommendations
  • Add explicit instructions and examples for Linux-based development and hosting, including supported SQL server editions and connection methods on Linux.
  • Clarify whether Linux-based App Service plans will be supported in the future, or provide rationale for their exclusion.
  • Include parity for Linux tools (e.g., Azure CLI, sqlcmd, VS Code on Linux) and workflows, and demonstrate how to set up SQL storage from Linux environments.
  • If Windows-only support is a technical limitation, highlight this clearly at the start of the documentation and provide alternative guidance for Linux users.
  • Reference cross-platform SQL management tools and provide connection string examples for both Windows and Linux environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Windows-specific tools (Chocolatey, PowerShell) are used for installing Kubernetes CLI and Helm, with no Linux/macOS alternatives provided. PowerShell commands and scripts are referenced and prioritized (e.g., EnvironmentSetup.ps1, Set-ExecutionPolicy), and Windows Server is mentioned before Linux or generic Kubernetes options. The SMB file share setup provides detailed Windows instructions, while Linux setup is only referenced indirectly or via test commands, not step-by-step. There are missing Linux/macOS installation examples for key tools and processes.
Recommendations
  • Provide installation instructions for kubectl and Helm using native Linux/macOS package managers (e.g., apt, yum, brew) alongside Chocolatey/PowerShell for Windows.
  • Include Linux/macOS equivalents for PowerShell commands, such as using bash scripts or shell commands for setting execution policies and environment variables.
  • Offer step-by-step instructions for setting up SMB file shares on Linux (e.g., using Samba), not just Windows and Azure Files.
  • Reference generic Kubernetes cluster creation and management options before platform-specific (Windows Server, Azure Local) ones, or present them in parallel.
  • Ensure all example scripts (such as EnvironmentSetup.ps1) have bash or shell script equivalents for Linux/macOS users.
  • Explicitly state cross-platform support and provide parity in all procedural steps, avoiding assumptions of a Windows-only environment.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently referencing Windows tools (e.g., Microsoft Azure Storage Explorer), presenting Windows-based workflows and UI screenshots, and prioritizing Windows-specific instructions (such as in-portal editing only being available on Windows). PowerShell is frequently mentioned as a method for resource creation, often before or alongside Azure CLI, but Linux alternatives (such as Linux-native tools or workflows) are not discussed or illustrated. There are no Linux-specific examples, screenshots, or troubleshooting steps, and the documentation does not address Linux user experience or parity.
Recommendations
  • Provide explicit Linux instructions and examples for all command-line steps, including resource creation and management using Azure CLI and bash scripts.
  • Include screenshots and workflow steps from Linux environments (e.g., Azure Portal accessed from Linux, Storage Explorer on Linux, or alternative Linux-compatible tools).
  • Mention and link to Linux installation guides for tools like Azure Storage Explorer, and clarify cross-platform compatibility.
  • Discuss local development and deployment workflows for Azure Functions and Logic Apps on Linux, including supported editors and runtime environments.
  • Ensure troubleshooting and testing sections address Linux-specific issues and user experience.
  • Avoid language that assumes Windows as the default OS; instead, present OS-neutral or parallel instructions for both Windows and Linux users.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-run-custom-code-functions.md ...rticles/logic-apps/create-run-custom-code-functions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by explicitly stating that the custom functions capability is only available on Visual Studio Code running on Windows. There are no instructions, examples, or troubleshooting steps for Linux or macOS users. All tooling, workflow, and troubleshooting guidance assumes a Windows environment, and Windows-specific paths and error messages are used throughout. No Linux equivalents or alternatives are mentioned.
Recommendations
  • Clearly state OS support and roadmap for Linux/macOS parity at the top of the documentation.
  • If Linux/macOS support is planned, provide expected timelines or preview instructions.
  • Where possible, offer alternative instructions or workarounds for Linux/macOS users, such as using containers or remote development.
  • Include troubleshooting steps and error messages relevant to Linux environments.
  • Use OS-agnostic language and file paths where possible, or provide both Windows and Linux/macOS examples side-by-side.
  • If features are Windows-only, provide links to feature requests or feedback channels for cross-platform support.
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-09 00:34
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 method for running code from workflows, but does not mention Bash, shell scripts, or other Linux-native scripting options. There are no explicit Linux-specific examples or tools referenced, and Windows-centric tools (PowerShell) are mentioned without Linux equivalents, suggesting a bias toward Windows environments.
Recommendations
  • Add examples for running Bash or shell scripts from Logic Apps workflows, alongside PowerShell and C#.
  • Explicitly mention Linux support and provide parity in scripting and automation examples.
  • Reference Linux-native tools and patterns (e.g., Bash, cron, shell scripting) in relevant sections, especially in 'Run code from your workflows'.
  • Where PowerShell is mentioned, clarify that Linux users can use PowerShell Core or alternative scripting languages.
  • Ensure deployment and DevOps examples include cross-platform tools (e.g., GitHub Actions, CLI commands usable on Linux) and not just Azure DevOps or Windows-centric pipelines.
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-09 00:34
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 toward Windows environments by exclusively mentioning PowerShell as a scripting option and omitting Linux-native alternatives such as Bash. There are no examples or references to Linux tools, shell scripts, or development patterns, and the scripting guidance focuses on Windows-centric technologies. This may disadvantage users working in Linux or cross-platform environments.
Recommendations
  • Include examples for Bash scripts and other Linux-native scripting options alongside PowerShell and C#.
  • Explicitly mention that workflows can run on Linux-based infrastructure and provide guidance for Linux users.
  • Add references to Linux development tools and patterns (e.g., VS Code on Linux, deployment via CLI/bash).
  • Ensure parity in documentation by presenting both Windows and Linux options for scripting, deployment, and automation.
  • Clarify cross-platform support in relevant sections, especially where only Windows tools are referenced.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily through repeated references to 'Windows plans only' for hosting environments (App Service Environment v3), and by omitting explicit Linux hosting examples or instructions. The documentation mentions deployment and development tools (Azure portal, Visual Studio Code, Azure CLI, ARM templates, REST API, PowerShell) in a generally cross-platform manner, but when discussing hosting, it consistently specifies Windows-only options and does not provide parity or guidance for Linux-based hosting or deployment. There are no examples or instructions for deploying Logic Apps Standard to Linux-based App Service plans, nor is there mention of Linux-specific development or operational considerations.
Recommendations
  • Add explicit examples and instructions for deploying Logic Apps Standard to Linux-based App Service plans, if supported.
  • Clarify whether Standard Logic Apps can be hosted on Linux App Service plans, and if not, explain the limitation.
  • Where 'Windows plans only' is mentioned, provide equivalent Linux options or state their absence clearly.
  • Include Linux-specific development and deployment guidance, such as using Linux containers, Linux-based CI/CD pipelines, or troubleshooting on Linux hosts.
  • Ensure parity in tool references (e.g., mention Bash and Linux shell usage alongside PowerShell where relevant).
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/call-azure-functions-from-workflows.md ...cles/logic-apps/call-azure-functions-from-workflows.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools such as Visual Studio and Azure PowerShell are listed before Linux-friendly alternatives, and PowerShell commands are referenced for key tasks (e.g., finding tenant ID) without equivalent Bash/Azure CLI examples. The use of Visual Studio (Windows-only) is mentioned before Visual Studio Code (cross-platform), and Kudu (CMD) is referenced, which is more familiar to Windows users. No explicit Linux examples or parity guidance are provided.
Recommendations
  • Include Azure CLI commands alongside PowerShell for tasks such as retrieving tenant IDs and managing resources.
  • List cross-platform tools (e.g., Visual Studio Code, Azure CLI) before Windows-only tools (e.g., Visual Studio, PowerShell) when presenting options.
  • Provide explicit Linux/macOS command examples and screenshots where applicable, especially for file editing and shell access.
  • Clarify that all steps can be performed on Linux/macOS, and note any platform-specific differences or requirements.
  • Reference Bash or sh commands for scripting and automation tasks, not just PowerShell.
  • Add a section or note on using the Azure portal and CLI from non-Windows platforms.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-custom-api-authentication.md ...les/logic-apps/logic-apps-custom-api-authentication.md
High Priority View Details →
Scanned: 2026-01-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 Windows bias in several ways. PowerShell is the only CLI example provided for creating Microsoft Entra application identities, with no equivalent Bash, Azure CLI, or Linux shell examples. The use of PowerShell is referenced before any mention of cross-platform tools, and there is no guidance for Linux or macOS users. Additionally, the documentation refers to Windows-specific URLs (sts.windows.net) and patterns, and omits alternative approaches for non-Windows environments.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all steps involving scripting or automation.
  • Explicitly mention cross-platform compatibility and provide instructions for Linux/macOS users where applicable.
  • Where PowerShell is referenced, also provide equivalent commands for Azure CLI and note their OS compatibility.
  • Avoid using Windows-specific terminology or URLs where not strictly necessary, or clarify their cross-platform applicability.
  • Review all screenshots and UI instructions to ensure they do not assume a Windows environment unless required.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/add-run-csharp-scripts.md ...lob/main/articles/logic-apps/add-run-csharp-scripts.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 consistently references Windows-specific tools and patterns, such as the Azure portal, KuduPlus console, and CMD shell, without mentioning Linux equivalents or alternatives. All step-by-step instructions for file management and workflow development assume a Windows environment, and there are no examples or guidance for performing these tasks on Linux systems. This creates a bias toward Windows users and may hinder Linux users from following the documentation effectively.
Recommendations
  • Include instructions for accessing and managing workflow files using Linux tools (e.g., Bash, SCP, SFTP, or Azure CLI) alongside the Windows/CMD examples.
  • Mention that the Azure portal and KuduPlus console are web-based and accessible from any OS, but clarify any OS-specific limitations or differences.
  • Provide examples of file operations (such as creating folders, uploading files) using Linux command-line tools and workflows.
  • Add notes or sections that address Linux/macOS users explicitly, ensuring parity in guidance for all supported platforms.
  • Where possible, use cross-platform terminology (e.g., 'terminal' instead of 'CMD') and avoid assuming the user is on Windows.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/authenticate-with-managed-identity.md ...icles/logic-apps/authenticate-with-managed-identity.md
High Priority View Details →
Scanned: 2026-01-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 consistently listing Windows-centric tools (Azure PowerShell) before cross-platform alternatives (Azure CLI) in tables and references. There are no explicit Linux-specific examples, nor are Linux command-line patterns or tools (such as bash scripts or Linux shell commands) mentioned. All procedural instructions involving command-line tools are generic or reference PowerShell and CLI documentation, but do not provide direct Linux usage examples. The Azure portal is used for most step-by-step instructions, which is platform-neutral, but the absence of Linux-specific guidance or examples is notable.
Recommendations
  • Provide explicit Linux shell (bash) command examples alongside PowerShell, especially for common tasks such as enabling managed identities, assigning roles, and removing identities.
  • In tables listing tools, alternate the order so that Azure CLI (cross-platform) is listed before Azure PowerShell, or clarify that CLI is recommended for Linux/macOS users.
  • Add a section or callouts for Linux users, highlighting any differences or considerations when using Azure CLI on Linux (e.g., authentication, environment variables, file paths).
  • Include sample scripts or walkthroughs using Azure CLI in a Linux terminal for key operations, such as ARM template deployment, role assignment, and identity management.
  • Where possible, mention that all Azure CLI commands are cross-platform and provide links to Linux-specific installation and usage guides.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/biztalk-server-migration-overview.md ...ticles/logic-apps/biztalk-server-migration-overview.md
High Priority View Details →
Scanned: 2026-01-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 a Windows bias in several areas: Windows-specific tools (MMC, PowerShell, Windows registry) are referenced as default or primary options for BizTalk Server management, configuration, and deployment. PowerShell is mentioned as a key automation language, and Windows authentication is described as a common method for adapters. There is little to no mention of Linux equivalents, and examples or tooling for Linux environments are absent. The hosting section for BizTalk Server only lists Windows platforms, and developer tooling is focused on Visual Studio (Windows-only) with no mention of cross-platform alternatives for BizTalk. Azure Logic Apps is described as supporting both Windows and Linux, but this parity is not reflected in the BizTalk Server sections.
Recommendations
  • Add explicit references to Linux hosting options for BizTalk Server (if supported), or clarify platform limitations.
  • Include examples of configuration and management using cross-platform tools (e.g., Bash, CLI) where possible.
  • Mention alternatives to Windows registry and MMC for configuration and administration, or note their absence for non-Windows users.
  • Provide parity in developer tooling by listing cross-platform IDEs or editors for BizTalk Server, or clarify that Visual Studio is Windows-only.
  • When discussing automation, include Bash or CLI examples alongside PowerShell.
  • Clarify which features are Windows-specific and which are available cross-platform, especially in migration scenarios.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/connect-on-premises-data-sources.md ...rticles/logic-apps/connect-on-premises-data-sources.md
High Priority View Details →
Scanned: 2026-01-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 demonstrates a Windows bias in several ways: it refers to installing the gateway on a 'local computer' without specifying platform, but subsequent references and troubleshooting steps (e.g., restarting the 'gateway Windows service account') imply Windows as the default/only supported platform. PowerShell is repeatedly mentioned as the automation tool for gateway management, with no mention of Linux shell or CLI alternatives. There are no examples or instructions for Linux installations, nor any reference to Linux-specific tools or troubleshooting steps. The documentation also refers to Windows service management patterns and omits parity for Linux environments.
Recommendations
  • Explicitly state platform support for the on-premises data gateway, including whether Linux is supported and provide installation instructions for Linux if available.
  • Provide Linux-specific examples for gateway installation, management, and troubleshooting (e.g., systemd service management, shell commands).
  • Include automation examples using Azure CLI or Bash scripts alongside PowerShell, or clarify if PowerShell Core is required/supported on Linux.
  • Avoid referring only to Windows service management; if Linux is supported, include equivalent steps for restarting gateway services on Linux.
  • Add notes or sections clarifying any platform limitations, and ensure that Linux users are not excluded from the documented workflows.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/connectors/informix.md ...s/blob/main/articles/logic-apps/connectors/informix.md
High Priority View Details →
Scanned: 2026-01-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 referencing Windows-based Informix deployments first ("IBM Informix for Windows running in Azure virtualization"), mentioning Windows authentication (Kerberos in Windows Server) as the only advanced authentication example, and linking exclusively to Windows Server documentation for Kerberos. There are no Linux-specific examples, tools, or authentication patterns provided, nor are Linux deployments or authentication mechanisms discussed.
Recommendations
  • Add explicit examples and guidance for connecting to Informix databases running on Linux, including typical connection strings and deployment scenarios.
  • Include references to Linux authentication mechanisms (such as Kerberos on Linux, PAM, or other relevant methods) and link to Linux documentation for Kerberos.
  • Present platform-neutral language when describing Informix deployments (e.g., "Informix running on Windows or Linux") and avoid mentioning Windows first.
  • Provide screenshots or walkthroughs that show Linux-based Informix server configurations and connections.
  • Clarify that the connector works with Informix on both Windows and Linux, and address any platform-specific considerations.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/connectors/sap-create-example-scenario-workflows.md ...ps/connectors/sap-create-example-scenario-workflows.md
High Priority View Details →
Scanned: 2026-01-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 Windows bias primarily in troubleshooting and configuration guidance. It references Windows-specific file paths (e.g., %windir%\System32\drivers\etc\services and hosts), and configuration files (e.g., Microsoft.PowerBI.EnterpriseGateway.exe.config), without providing equivalent instructions for Linux environments. The troubleshooting steps and examples for resolving network service name and host resolution issues are exclusively tailored for Windows, and there is no mention of how to perform these tasks on Linux-based installations of the data gateway. Additionally, Windows terminology and tools are presented first and exclusively, with no Linux parity.
Recommendations
  • Add equivalent troubleshooting instructions for Linux environments, including file paths (e.g., /etc/hosts, /etc/services) and configuration steps.
  • Clarify whether the on-premises data gateway and SAP connector are supported on Linux, and if so, provide Linux-specific setup and troubleshooting guidance.
  • Where configuration files or service management are referenced (e.g., restarting the gateway), include Linux commands (e.g., systemctl restart service-name) alongside Windows instructions.
  • Review all examples and ensure that any Windows-specific references are accompanied by Linux alternatives, or explicitly state platform limitations.
  • Consider adding a platform support matrix or section to highlight differences and guide users on both Windows and Linux.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/connectors/sap.md ...e-docs/blob/main/articles/logic-apps/connectors/sap.md
High Priority View Details →
Scanned: 2026-01-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 exhibits a Windows bias in several areas: Windows tools and patterns (such as PowerShell scripts, .exe utilities, and references to Windows file paths) are used exclusively or mentioned first, with little to no mention of Linux equivalents. Examples for tasks like converting files to base64, extracting SAR archives, and installing SAP client libraries are provided only for Windows (PowerShell, .exe utilities, C:\ paths), while Linux alternatives (bash, shell scripts, .so files, Linux paths) are missing. The documentation also references Windows-specific troubleshooting tools and configuration files, and does not provide parity for Linux users.
Recommendations
  • Provide Linux equivalents for all Windows-only instructions, such as using bash or Python scripts for base64 conversion, and referencing Linux file paths and permissions.
  • Include instructions for extracting SAR files on Linux (e.g., using SAPCAR on Linux, tar commands).
  • Mention Linux-compatible SAP NCo client libraries and clarify platform support for both Windows and Linux.
  • Add troubleshooting steps and log file locations for Linux environments.
  • Reference Linux tools (e.g., openssl, shell utilities) alongside Windows tools (PowerShell, .exe).
  • Ensure all examples (file paths, environment variables, installation steps) are shown for both Windows and Linux.
  • Clarify any limitations or differences in connector behavior on Linux vs. Windows.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-automation-tasks-azure-resources.md .../logic-apps/create-automation-tasks-azure-resources.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 bias toward Windows by exclusively referencing Windows-specific tools (Fiddler 4, Fiddler Everywhere) for web debugging, and by not providing any Linux equivalents or examples. The workflow export and testing instructions assume the use of Fiddler, which is primarily a Windows application, and do not mention or suggest alternatives available on Linux (such as mitmproxy or curl). The page also lacks any command-line or automation examples for Linux environments, and does not mention PowerShell, but the overall approach and tooling are Windows-centric.
Recommendations
  • Include Linux-friendly web debugging tools (e.g., mitmproxy, curl, or Wireshark) in the testing section, with example usage.
  • Provide explicit instructions or examples for Linux users when referencing tooling or workflows that are platform-dependent.
  • Add a note or section listing cross-platform alternatives to Fiddler, and clarify which steps are platform-agnostic.
  • Ensure screenshots and step-by-step instructions are not exclusively tailored to Windows environments.
  • Where possible, provide CLI-based instructions (using Azure CLI, Bash, etc.) in addition to portal-based steps.
GitHub Create Pull Request
← Previous Page 5 of 14 Next →