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 276-300 of 339 flagged pages
Logic Apps Reference for functions in workflow expressions .../articles/logic-apps/expression-functions-reference.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation demonstrates a Windows bias primarily in its handling of time zone names and date/time formatting. For functions like convertFromUtc, convertTimeZone, and convertToUtc, the documentation references 'Microsoft Windows Default Time Zones' and instructs users to use Windows-style time zone names. Date/time format strings and locale codes are referenced using .NET and Windows conventions, with no mention of Linux/ICU equivalents. There are no Linux-specific examples or guidance for users on non-Windows platforms.
Recommendations
  • Include guidance on using IANA/Olson time zone names (e.g., 'America/Los_Angeles') for Linux and cross-platform compatibility, or clarify platform limitations.
  • Mention that the time zone names and format strings are based on .NET/Windows conventions, and provide a mapping or reference for users on Linux or other platforms.
  • Add examples or notes for users on Linux/macOS, explaining how to handle time zones and date formats if their environment differs from Windows.
  • Clarify whether the functions work identically on Linux-hosted Logic Apps, and if not, provide platform-specific instructions or warnings.
  • Where possible, reference cross-platform standards (e.g., ICU format strings, IANA time zones) alongside Windows/.NET references.
GitHub Create Pull Request
Logic Apps Move logic apps across subscriptions, resource groups, or regions ...b/main/articles/logic-apps/move-logic-app-resources.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently lists Azure PowerShell before Azure CLI when mentioning automation options, and provides no concrete examples for either tool. There are no platform-specific command examples, but the order and emphasis suggest a subtle Windows bias. Visual Studio is mentioned as a tool for exporting and managing logic apps, with no mention of cross-platform alternatives like VS Code. There are no Linux-specific instructions or examples, and the documentation does not acknowledge platform differences for CLI usage.
Recommendations
  • Provide explicit Azure CLI examples alongside or before Azure PowerShell examples, especially since Azure CLI is cross-platform.
  • Include instructions or references for using VS Code (cross-platform) in addition to Visual Studio for template management.
  • Add notes clarifying that Azure CLI and REST API are available on Linux and macOS, and provide sample commands for those platforms.
  • Ensure that any automation or scripting guidance is not Windows-centric and highlights cross-platform capabilities.
GitHub Create Pull Request
Logic Apps Quickstart - Create Consumption logic app workflow with Bicep .../articles/logic-apps/quickstart-create-deploy-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is featured equally alongside CLI, and there is no explicit mention of Linux-specific tools or shell environments (e.g., Bash, zsh). The use of PowerShell, which is traditionally associated with Windows, may suggest a Windows bias, especially since there are no examples using native Linux shell commands or guidance for Linux users. Additionally, Visual Studio Code is mentioned as the next step, but no alternative editors or Linux-specific instructions are provided.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and clarify that PowerShell Core is cross-platform if referenced.
  • Provide example commands using Bash or zsh where appropriate, especially for file operations (e.g., saving the Bicep file).
  • Include notes or tabs for Linux/macOS users, such as instructions for installing Azure CLI and Bicep on those platforms.
  • Mention alternative editors for Bicep files, such as Vim or nano, in addition to Visual Studio Code.
  • Add troubleshooting tips for common Linux-specific issues (e.g., file permissions, path formats).
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by exclusively referencing the Azure portal and providing examples using Microsoft 365, Office 365 Outlook, and other Microsoft services. There are no examples or guidance for Linux environments, CLI tools, or cross-platform alternatives. The documentation assumes usage of the Azure portal (typically accessed via a browser on Windows) and does not mention Linux-specific workflows, tools, or authentication patterns.
Recommendations
  • Include examples for using Azure Logic Apps and OBO flow via Azure CLI, PowerShell, and REST API, with explicit instructions for Linux and macOS environments.
  • Provide guidance for setting up agent workflows and connections using cross-platform tools, such as Azure CLI or Terraform, and clarify any platform-specific requirements.
  • Mention and demonstrate how to test agent workflows from Linux-based external chat clients or browsers.
  • Clarify that the Azure portal and agent workflows are accessible from any OS, and provide troubleshooting steps for common Linux-specific issues (e.g., browser compatibility, authentication flows).
  • Add references to documentation for Linux users, such as installing Azure CLI on Linux, and provide parity in screenshots or command-line examples.
GitHub Create Pull Request
Logic Apps Set Up DevOps for Standard Workflows ...et-up-devops-deployment-single-tenant-azure-logic-apps.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing command-line instructions and environment setup steps primarily for Windows and Mac users, with no explicit mention of Linux equivalents. For example, pip installation and CLI commands are described as being run from 'Windows or Mac operating system', and there are no Linux-specific instructions or examples for common developer tasks such as checking pip installation, setting up the Azure CLI, or deploying Logic Apps. Additionally, references to authentication types (e.g., 'windows' in ARM templates) may reinforce a Windows-centric perspective.
Recommendations
  • Add explicit Linux instructions and examples for all command-line steps, including pip installation, Azure CLI setup, and deployment commands.
  • When referring to operating systems, use inclusive language such as 'Windows, Mac, or Linux' and provide platform-specific notes where necessary.
  • Include Linux shell commands (e.g., bash/zsh) alongside Windows command prompt examples, especially for tasks like checking pip installation and running Azure CLI commands.
  • Clarify whether ARM template authentication types such as 'windows' are required or if alternatives exist for Linux environments.
  • Ensure parity in troubleshooting and installation guidance for Linux users, including links to relevant documentation.
GitHub Create Pull Request
Logic Apps Reference for functions in workflow expressions .../articles/logic-apps/expression-functions-reference.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation exhibits Windows bias primarily in its handling of time zone names and date/time formatting. Time zone parameters for functions such as convertFromUtc, convertTimeZone, and convertToUtc reference 'Microsoft Windows Default Time Zones' and link to Windows-specific documentation, with no mention of IANA/Olson time zones commonly used on Linux. Date/time format strings and locale codes are described in terms of .NET and Windows conventions, with examples and links focused on Windows/.NET standards. There are no references to Linux tools, standards, or cross-platform alternatives for time zones or formatting.
Recommendations
  • Add support and documentation for IANA/Olson time zone names, which are standard on Linux and many cross-platform environments.
  • Include examples using IANA time zone identifiers (e.g., 'America/New_York', 'Europe/London') alongside Windows time zone names.
  • Clarify whether the functions accept only Windows time zone names or also IANA names, and document any conversion or mapping required.
  • Reference cross-platform standards (such as Unicode CLDR for locales and IANA for time zones) in addition to Windows/.NET documentation.
  • If only Windows time zones are supported, explicitly state this limitation and provide guidance for Linux users on how to map IANA time zones to Windows equivalents.
  • Consider adding a table or link to resources that help users convert between Windows and IANA time zone names.
GitHub Create Pull Request
Logic Apps Move logic apps across subscriptions, resource groups, or regions ...b/main/articles/logic-apps/move-logic-app-resources.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page lists Azure PowerShell before Azure CLI when mentioning migration options, and provides no command-line examples for either tool. Visual Studio is referenced as the primary IDE for template export and management, with no mention of Linux-friendly alternatives (such as VS Code or CLI-only workflows). There are no explicit Linux or cross-platform examples, and the documentation assumes use of tools most commonly available on Windows.
Recommendations
  • Provide explicit Azure CLI examples alongside or before Azure PowerShell examples, as CLI is cross-platform.
  • Include instructions for exporting and managing templates using VS Code, which is available on Linux and macOS.
  • Add command-line examples for moving resources using Azure CLI and REST API, not just portal and Visual Studio workflows.
  • Mention cross-platform alternatives for template editing and deployment, such as using text editors and CLI tools.
  • Clarify that all steps can be performed on Linux, macOS, or Windows, and note any platform-specific limitations.
GitHub Create Pull Request
Logic Apps Quickstart - Create Consumption logic app workflow with Bicep .../articles/logic-apps/quickstart-create-deploy-bicep.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is featured equally alongside CLI, and there is no explicit mention of Linux-specific tools or shell environments (e.g., Bash). The use of PowerShell may implicitly favor Windows users, as PowerShell is native to Windows, while Bash is native to Linux. There are no Linux-specific instructions or examples, and the documentation does not acknowledge platform differences or provide guidance for Linux users.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and clarify that PowerShell is primarily for Windows (or for cross-platform PowerShell Core users).
  • Add Bash shell examples or note that CLI commands can be run in Bash on Linux/macOS.
  • Include a brief section or note about platform compatibility for the tools used (CLI, PowerShell).
  • Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples to reduce perceived Windows-first bias.
  • If relevant, mention any Linux-specific considerations (e.g., file paths, shell syntax) when saving or referencing files.
GitHub Create Pull Request
Logic Apps Set Up DevOps for Standard Workflows ...et-up-devops-deployment-single-tenant-azure-logic-apps.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows-centric instructions and examples first, particularly in sections about checking pip installation and running commands. There is a lack of explicit Linux-specific examples or guidance, especially for command-line operations and environment setup. The documentation assumes familiarity with Windows tools and workflows, and does not provide parity for Linux users in terms of step-by-step instructions or troubleshooting.
Recommendations
  • Add explicit Linux and macOS command-line examples alongside Windows instructions, especially for pip installation, Azure CLI usage, and environment setup.
  • Include troubleshooting steps and environment checks for Linux (e.g., using 'which python3', 'pip3', and package managers like apt, yum, or Homebrew).
  • Provide guidance for setting environment variables and paths on Linux and macOS, not just Windows.
  • Ensure that all steps referencing the Azure portal or Visual Studio Code are accompanied by notes about cross-platform compatibility.
  • Where commands or tools differ between platforms, present both options equally and avoid assuming Windows as the default.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/expression-functions-reference.md .../articles/logic-apps/expression-functions-reference.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation exhibits Windows bias primarily in its references to time zone names and date/time formatting. Time zone parameters for functions such as convertFromUtc, convertTimeZone, and convertToUtc explicitly direct users to 'Microsoft Windows Default Time Zones' and require Windows-style time zone names. Date/time format strings are referenced using .NET documentation, which is more familiar to Windows users. No mention is made of Linux/Unix time zone naming conventions (e.g., IANA/Olson database), nor are Linux equivalents or cross-platform considerations discussed. There are no PowerShell-heavy examples, but the documentation assumes Windows-centric patterns and tools for key functionality.
Recommendations
  • Add information about IANA/Olson time zone names and clarify whether they are supported or not. If only Windows time zones are supported, explicitly state this limitation and provide guidance for Linux users.
  • Include cross-platform notes for date/time formatting, explaining how .NET format strings map to other environments and what Linux users should expect.
  • Where external references are made (e.g., time zone lists), provide links or explanations for both Windows and Linux/Unix conventions, or clarify the scope of support.
  • Add a note about the lack of support for Linux-style time zones if applicable, and suggest workarounds for users on non-Windows platforms.
  • Consider including examples or documentation for Linux/Unix users, especially where platform differences may affect workflow behavior.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/move-logic-app-resources.md ...b/main/articles/logic-apps/move-logic-app-resources.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation lists multiple migration methods (Azure portal, PowerShell, CLI, REST API) but only provides detailed step-by-step instructions for the Azure portal, which is platform-agnostic but most commonly used on Windows. PowerShell is mentioned as an option before Azure CLI, which is more popular among Linux users, and no explicit Linux-specific examples or CLI command walkthroughs are given. Visual Studio is referenced for template management, but there is no mention of Linux-friendly alternatives (e.g., VS Code). There are no examples or instructions tailored for Linux users or tools.
Recommendations
  • Add explicit Azure CLI command examples for each migration scenario, with step-by-step instructions.
  • Include Linux shell (bash) usage patterns and highlight cross-platform compatibility.
  • Mention and provide examples using VS Code for template management, not just Visual Studio.
  • Ensure PowerShell and CLI instructions are presented with equal prominence, or group them together as cross-platform options.
  • Clarify that the Azure portal is accessible from any OS and provide screenshots or notes for Linux users if UI differs.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/quickstart-create-deploy-bicep.md .../articles/logic-apps/quickstart-create-deploy-bicep.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is presented as an equal alternative to CLI, despite being primarily a Windows tool, and is listed immediately after CLI in every example. There is no explicit mention of Linux-specific considerations, nor are there examples for Bash scripting or other Linux-native tools. The use of PowerShell throughout may implicitly favor Windows users, as Linux users are less likely to use PowerShell.
Recommendations
  • Clearly indicate that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is primarily for Windows (though available on Linux, but less common).
  • Consider listing CLI examples first and making them the default, as CLI is cross-platform.
  • Add explicit Bash shell script examples for common tasks, or clarify that CLI commands can be run in Bash.
  • Remove or de-emphasize PowerShell examples unless there is a specific Windows-only scenario.
  • Add notes or sections on Linux/macOS environment setup if any steps differ from Windows.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/set-up-on-behalf-of-user-flow.md ...n/articles/logic-apps/set-up-on-behalf-of-user-flow.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by exclusively referencing the Azure portal and Microsoft 365 services, with examples focused on Office 365 Outlook and Microsoft Entra ID. There are no examples or guidance for Linux environments, CLI-based workflows, or cross-platform tools. All screenshots and step-by-step instructions assume use of the Azure portal, which is most commonly accessed from Windows environments, and there is no mention of Linux-specific authentication flows, tools, or troubleshooting.
Recommendations
  • Add examples using Azure CLI and PowerShell, and ensure parity with Bash or shell scripts for Linux users.
  • Include instructions for setting up OBO flows using cross-platform tools (e.g., Azure CLI, REST API calls) rather than only through the Azure portal UI.
  • Provide troubleshooting steps and authentication guidance for Linux environments, including common issues with Linux-based agents or connectors.
  • Reference Linux-compatible connectors and agent tools, and clarify any platform-specific limitations.
  • Ensure screenshots and examples are not exclusively Windows-centric, and consider including terminal-based workflows.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-securing-a-logic-app.md ...articles/logic-apps/logic-apps-securing-a-logic-app.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias, primarily through its use of Windows-specific tooling and patterns. For example, instructions for converting PFX certificates to base64 explicitly use PowerShell and reference Windows file paths (e.g., 'c:\certificate.pfx') before mentioning OpenSSL as an alternative. The troubleshooting steps for certificate conversion also assume Windows environments and PowerShell usage, with Linux tools (OpenSSL) mentioned only as a workaround. There are no Linux-specific examples or explicit parity for Linux command-line usage, and Windows-centric terminology (such as 'Default.htm', 'iisstart.htm', 'default.aspx') appears in configuration samples, further reinforcing the Windows-first approach.
Recommendations
  • Provide Linux and macOS equivalents for all command-line instructions, especially for certificate conversion (e.g., show OpenSSL usage first or alongside PowerShell).
  • Use platform-neutral file paths in examples (e.g., '/home/user/certificate.pfx' or './certificate.pfx') and clarify that instructions apply to all major OSes.
  • When listing default documents or configuration options, avoid Windows/IIS-specific files unless necessary, or add notes about Linux/Apache/Nginx equivalents.
  • Explicitly mention cross-platform tools and workflows, and provide links or examples for Linux and macOS users.
  • Review all troubleshooting steps and ensure Linux-first or platform-agnostic guidance is included, not just Windows/PowerShell solutions.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/quickstart-create-deploy-bicep.md .../articles/logic-apps/quickstart-create-deploy-bicep.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is featured equally and sometimes before Linux-native alternatives, and there is no explicit mention of Linux-specific considerations or shell environments (e.g., Bash). The use of PowerShell as a primary example may indicate a slight Windows bias, especially since PowerShell is traditionally associated with Windows, even though it is now cross-platform.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux/macOS and Windows, and clarify shell requirements (e.g., Bash, zsh).
  • Add Bash-specific notes or examples where appropriate, especially for users on Linux/macOS.
  • If PowerShell is shown, note that PowerShell Core is available cross-platform, but CLI is generally preferred on Linux/macOS.
  • Consider listing Azure CLI examples before PowerShell, as CLI is more commonly used on Linux.
  • Add troubleshooting tips or environment setup instructions for Linux users, if relevant.
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by explicitly stating that the custom functions capability is only available in Visual Studio Code running on Windows. There are no instructions, examples, or troubleshooting steps for Linux or macOS users. All examples and screenshots are based on Windows environments, and the prerequisites do not mention Linux or macOS support.
Recommendations
  • Clearly state OS limitations at the top of the page and provide a roadmap or timeline for Linux/macOS support.
  • Add equivalent instructions or troubleshooting steps for Linux and macOS if/when support is available.
  • Include notes or alternative approaches for non-Windows users, such as using containers or remote development environments.
  • Provide parity in examples and screenshots for Linux/macOS environments once supported.
  • Regularly update the documentation to reflect changes in cross-platform support.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/expression-functions-reference.md .../articles/logic-apps/expression-functions-reference.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation demonstrates a Windows bias primarily through its exclusive use of Microsoft Windows time zone names and .NET format strings for date/time and number formatting. References to time zones consistently point to the Microsoft Windows Default Time Zones documentation, with no mention of IANA/Olson time zones commonly used on Linux. Format strings and locale handling are described in terms of .NET conventions, which are native to Windows environments. There are no Linux-specific examples, nor is there guidance for Linux users on how to map or use equivalent time zone or formatting standards.
Recommendations
  • Add references and examples for IANA/Olson time zone names, which are standard on Linux and many cross-platform environments.
  • Clarify whether functions accept IANA time zone names or only Windows names, and provide conversion guidance or tooling for Linux users.
  • Include notes or tables mapping Windows time zone names to their IANA equivalents.
  • Where .NET format strings are referenced, explain their relation to other cross-platform standards (e.g., strftime on Linux) and provide conversion tips.
  • Explicitly state platform limitations or differences in time zone and formatting support between Windows and Linux.
  • Consider adding Linux-centric examples or usage notes for developers working outside Windows environments.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/move-logic-app-resources.md ...b/main/articles/logic-apps/move-logic-app-resources.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently lists Azure PowerShell before Azure CLI when mentioning command-line options, and does not provide any explicit examples or instructions for Linux users. There are no platform-specific command-line examples at all, and Visual Studio (a Windows-centric tool) is referenced for template management, with no mention of Linux alternatives (such as VS Code or CLI-based workflows).
Recommendations
  • Provide explicit Azure CLI examples for each migration scenario, as CLI is cross-platform and preferred by many Linux users.
  • When listing command-line options, mention Azure CLI before or alongside Azure PowerShell to avoid implicit Windows-first bias.
  • Include instructions or references for managing logic apps using VS Code or other cross-platform editors, not just Visual Studio.
  • Add notes clarifying that all Azure CLI steps work on Linux, macOS, and Windows.
  • Where Visual Studio is referenced, suggest VS Code or CLI-based template editing as alternatives for non-Windows users.
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently presenting Windows-centric instructions and examples first (e.g., command prompts, Azure portal, Visual Studio Code on Windows/Mac), and by omitting explicit Linux shell or tooling examples for key steps such as checking pip installation, running CLI commands, and managing files. There are no Linux-specific instructions or screenshots, and references to command-line usage default to Windows/Mac environments, leaving out Linux terminal conventions and package management.
Recommendations
  • Add explicit Linux shell examples (e.g., bash/zsh) for pip installation and verification, including package manager commands (apt, yum, etc.) for installing Python and pip.
  • Include Linux-specific instructions for opening terminals, running Azure CLI commands, and managing files (e.g., using unzip, mv, cp commands).
  • Provide parity in screenshots and step-by-step instructions for Linux environments, not just Windows/Mac.
  • Mention cross-platform compatibility for Visual Studio Code and Azure CLI, and clarify any platform-specific caveats.
  • Where commands or tooling differ between Windows and Linux (e.g., path separators, environment variables), highlight both approaches.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/set-up-on-behalf-of-user-flow.md ...n/articles/logic-apps/set-up-on-behalf-of-user-flow.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and Microsoft-centric environments. All examples, screenshots, and tool references are based on Microsoft services (Azure portal, Office 365 Outlook, Microsoft Entra ID, etc.), with no mention of Linux, cross-platform CLI tools, or non-Microsoft alternatives. There are no examples or guidance for users working from Linux environments, nor are there references to Linux-specific authentication flows, tools, or connectors.
Recommendations
  • Provide examples using cross-platform tools such as Azure CLI, which runs on Linux, macOS, and Windows.
  • Include instructions or screenshots for accessing Azure Logic Apps and setting up OBO flow from Linux environments (e.g., using browser-based portal, CLI, or REST API).
  • Mention and link to documentation for Linux-compatible authentication methods and agent workflows.
  • Clarify that the OBO flow and per-user connections can be configured and tested from non-Windows environments, if supported.
  • If any steps require Windows-only tools or interfaces, explicitly state this and offer Linux alternatives where possible.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-maps-data-transformation-visual-studio-code.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-maps-data-transformation-visual-studio-code.md
Medium Priority View Details →
Scanned: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation explicitly states that the Data Mapper tool is only available in Visual Studio Code running on Windows operating systems. There are no instructions, examples, or troubleshooting steps for Linux or macOS users. The prerequisites and all workflow steps assume a Windows environment, and there is no mention of Linux compatibility or workarounds.
Recommendations
  • Clearly indicate in the introduction and prerequisites that the Data Mapper tool is currently Windows-only, and provide a roadmap or status update for Linux/macOS support if available.
  • Add a dedicated section for Linux/macOS users, outlining any possible workarounds, alternative tools, or expected timelines for cross-platform support.
  • If partial functionality is available on Linux/macOS (e.g., editing maps manually, using CLI tools, or deploying maps), document those workflows explicitly.
  • Ensure all screenshots, file paths, and instructions are either cross-platform or provide platform-specific variants.
  • Monitor and update the documentation as soon as Linux/macOS support is released, ensuring parity in examples and troubleshooting guidance.
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
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing Windows-based tools (Fiddler 4) for testing templates and not providing equivalent Linux alternatives or examples. There are no command-line or scripting examples (e.g., PowerShell, Bash), but the only explicit tool guidance is for a Windows application. No Linux or cross-platform alternatives are mentioned for the debugging/testing step.
Recommendations
  • Include Linux-friendly or cross-platform alternatives to Fiddler, such as mitmproxy or Charles Proxy, in the 'Test your template' section.
  • Provide example instructions for using these alternative tools on Linux/macOS.
  • When referencing third-party tools, clarify their platform compatibility and suggest options for all major operating systems.
  • If possible, add a note or table listing recommended web debugging tools for Windows, Linux, and macOS.
  • Review other sections for opportunities to add Linux/macOS parity, such as mentioning Azure CLI usage or showing screenshots from non-Windows environments where relevant.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/export-from-ise-to-standard-logic-app.md ...es/logic-apps/export-from-ise-to-standard-logic-app.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page focuses exclusively on Visual Studio Code as the export tool, but all instructions, screenshots, and workflow descriptions implicitly assume a Windows environment. There are no explicit Linux or macOS instructions, no mention of cross-platform differences, and no terminal/CLI alternatives. Keyboard shortcuts (Shift + Alt + A) and UI references are Windows-centric. There is no guidance for Linux users regarding possible differences in UI, file paths, or required dependencies.
Recommendations
  • Explicitly state that Visual Studio Code and the Azure Logic Apps (Standard) extension are cross-platform and supported on Windows, Linux, and macOS.
  • Include Linux/macOS-specific instructions or notes where UI, keyboard shortcuts, or file paths may differ.
  • Provide at least one example or screenshot from a Linux (and/or macOS) environment to demonstrate parity.
  • Mention any required dependencies or troubleshooting steps that may be unique to Linux (e.g., installing .NET runtime, handling permissions).
  • If possible, offer CLI-based alternatives (e.g., using Azure CLI or PowerShell Core, which is cross-platform) for users who prefer or require non-GUI workflows.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/add-rules-operators.md ...rticles/logic-apps/rules-engine/add-rules-operators.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively references the Microsoft Rules Composer, a Windows-only GUI tool, and provides instructions specific to its interface. There are no examples or guidance for Linux users, command-line alternatives, or cross-platform workflows. No mention is made of using the Rules Engine or composing rules outside of the Windows environment.
Recommendations
  • Provide information on whether the Microsoft Rules Composer is available or supported on Linux (e.g., via Wine, or if a cross-platform version exists).
  • If the Rules Composer is Windows-only, suggest alternative methods for Linux users, such as editing ruleset XML files directly with cross-platform editors.
  • Include command-line or API-based workflows for rule creation and editing that work on Linux.
  • Explicitly state platform limitations and offer guidance for Linux users to achieve parity in rule authoring and management.
  • Where possible, provide screenshots or step-by-step instructions for both Windows and Linux environments, or clarify when features are Windows-specific.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/create-manage-vocabularies.md .../logic-apps/rules-engine/create-manage-vocabularies.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively references the Microsoft Rules Composer, a GUI tool that is only available for Windows. There are no instructions, examples, or alternatives provided for Linux users, nor is there any mention of command-line or cross-platform approaches. All steps assume the use of a Windows environment and Windows-style UI interactions.
Recommendations
  • Clearly state platform requirements and limitations at the beginning of the documentation, specifying that Microsoft Rules Composer is Windows-only.
  • If possible, provide or reference any available Linux-compatible tools or command-line alternatives for managing vocabularies and rulesets.
  • Include guidance for Linux users, such as using Azure Portal, REST APIs, or other cross-platform interfaces if available.
  • If no Linux alternatives exist, suggest workarounds (e.g., using a Windows VM or container) and encourage feedback to help prioritize cross-platform support.
  • Ensure future documentation includes parity in examples and tool references for both Windows and Linux environments.
GitHub Create Pull Request
← Previous Page 12 of 14 Next →