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 151-175 of 339 flagged pages
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: 2025-07-13 21:37
Reviewed by: Unknown
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 (such as Microsoft Azure Storage Explorer), prioritizing Windows in instructions and examples, and providing PowerShell commands without equivalent Linux/bash examples. In several places, the documentation mentions PowerShell before Azure CLI, and in the function app creation section, Windows is selected as the example OS, with in-portal editing only supported on Windows. There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-native tools or workflows.
Recommendations
  • Provide equivalent bash/Azure CLI examples alongside PowerShell commands wherever PowerShell is mentioned.
  • Include explicit instructions or screenshots for Linux/macOS users, especially for tools like Azure Storage Explorer and Azure CLI.
  • When referencing operating systems, avoid defaulting to Windows in examples; instead, show both Windows and Linux options or use neutral language.
  • Mention cross-platform alternatives to Windows-only features (e.g., in-portal editing limitations) and provide guidance for Linux/macOS users.
  • Ensure that all prerequisite and setup steps are platform-agnostic or have clear, parallel instructions for Linux/macOS.
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
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by explicitly stating that the Data Mapper tool only works on Visual Studio Code running on Windows operating systems. There are no instructions, examples, or troubleshooting steps for Linux or macOS users. The prerequisites and workflow steps assume a Windows environment, and there is no mention of alternative approaches or workarounds for non-Windows platforms.
Recommendations
  • Clearly state platform limitations at the top of the documentation, and provide a roadmap or timeline for Linux/macOS support if available.
  • Offer alternative instructions or workarounds for Linux/macOS users, such as using a Windows VM, container, or remote development environment.
  • Include a section addressing the lack of Linux/macOS support, with links to feature requests or community discussions.
  • If possible, provide parity in tooling or recommend equivalent open-source or cross-platform tools for Linux/macOS users.
  • Regularly update the documentation as platform support evolves, and solicit feedback from non-Windows users to prioritize cross-platform parity.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by assuming the on-premises data gateway is installed on a 'local computer' without clarifying cross-platform support, referencing Windows-specific service management (e.g., 'gateway Windows service account'), and repeatedly linking to PowerShell-based automation for gateway management. There are no examples or instructions for Linux environments, nor are Linux tools or command-line alternatives mentioned.
Recommendations
  • Explicitly state whether the on-premises data gateway supports installation on Linux or macOS, and provide platform-specific prerequisites if available.
  • If Linux is supported, add installation and management instructions for Linux (e.g., systemd service management, Linux CLI commands).
  • Provide automation examples using cross-platform tools such as Azure CLI or REST API, not just PowerShell.
  • Clarify terminology such as 'local computer' to specify supported operating systems.
  • If PowerShell is required, note its availability on Linux and provide Linux-compatible command examples.
  • Ensure that all references to service management (e.g., restarting the gateway) include Linux equivalents if supported.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/edit-app-settings-host-settings.md ...articles/logic-apps/edit-app-settings-host-settings.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns (such as Kudu and CMD), mentioning Windows in configuration settings, and omitting Linux-specific instructions or examples for managing app and host settings. The guidance for editing files and using the Azure portal assumes a Windows environment, with no mention of Linux shells, editors, or file paths. Additionally, some settings (e.g., WEBSITE_NODE_DEFAULT_VERSION) are described as applying 'when running your logic app workflows on Windows' without clarifying Linux/macOS equivalents or differences.
Recommendations
  • Provide explicit instructions for Linux and macOS users, including equivalent shell commands (e.g., Bash) and file path conventions.
  • When referencing the Kudu environment, clarify its availability and usage on Linux-based App Service plans and provide alternative instructions if necessary.
  • For settings that are described as Windows-specific (e.g., WEBSITE_NODE_DEFAULT_VERSION), document the behavior and configuration for Linux environments.
  • Include examples of editing configuration files (local.settings.json, host.json) using cross-platform editors (e.g., VS Code, nano, vim) and clarify that these files and settings are platform-agnostic unless otherwise noted.
  • Where the Azure CLI is referenced, ensure that examples and instructions are clearly cross-platform and do not assume a Windows shell.
  • Add a section or notes highlighting any differences, limitations, or considerations when running Logic Apps Standard on Linux versus Windows hosts.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools (such as Visual Studio and PowerShell), referencing Windows-specific patterns (like Kudu's CMD console), and providing PowerShell commands without equivalent Bash/Azure CLI examples. Linux-native workflows and tools are not given equal prominence or examples, and there is a lack of explicit Linux or cross-platform guidance for key steps.
Recommendations
  • Provide Azure CLI and Bash command examples alongside PowerShell commands (e.g., for retrieving tenant IDs or managing resources).
  • Mention and demonstrate Linux/macOS-compatible tools (such as VS Code, Azure CLI, and Bash) before or alongside Windows-specific tools like Visual Studio and PowerShell.
  • Include screenshots or instructions for accessing Kudu/Advanced Tools using Bash or cross-platform shells, not just CMD.
  • Add explicit notes or sections for Linux/macOS users, clarifying any differences in workflow or tool usage.
  • Ensure all code snippets and setup instructions are platform-agnostic or provide alternatives for both Windows and Linux environments.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses PowerShell commands and Windows-centric tooling (e.g., PowerShell modules, ARMClient, C:\ paths) for creating and deploying Azure Logic App templates. There are no equivalent examples or instructions for Linux/macOS users, such as Bash/CLI commands or cross-platform file path conventions. This creates a strong Windows and PowerShell bias, potentially excluding or confusing users on other platforms.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for Linux/macOS users, including how to install and use the LogicAppTemplate module (if possible) or alternative tools.
  • Use cross-platform file path examples (e.g., ~/template.json or ./template.json) instead of Windows-specific paths like C:\template.json.
  • Mention and demonstrate how to perform the same tasks using Azure CLI and/or REST API, which are available on all platforms.
  • Clearly state platform requirements or limitations for the LogicAppTemplate module and ARMClient, and suggest alternatives for non-Windows environments.
  • Reorganize sections so that cross-platform or platform-neutral approaches (e.g., Azure CLI, REST API) are presented before or alongside PowerShell/Windows-specific instructions.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell before Azure CLI when discussing automation tools, referencing Visual Studio (a primarily Windows IDE) and its workflows in detail, and mentioning Visual Studio Code only briefly. There are no explicit Linux or cross-platform command-line examples, and the documentation does not provide parity in guidance for Linux users or alternative editors/tools commonly used on Linux. The focus on PowerShell and Visual Studio, both Windows-centric tools, further reinforces this bias.
Recommendations
  • List Azure CLI before Azure PowerShell when discussing automation tools, or present both equally with cross-platform context.
  • Expand the Visual Studio Code section with step-by-step instructions, as VS Code is cross-platform and widely used on Linux.
  • Include explicit Linux command-line examples for deploying and managing Logic Apps, such as using Azure CLI from a Bash shell.
  • Mention and provide examples for alternative editors (e.g., Vim, nano, Sublime Text) for editing JSON workflow definitions.
  • Clarify that all JSON editing and deployment steps can be performed on Linux, macOS, and Windows, and highlight any platform-specific differences.
  • Avoid assuming Visual Studio as the default IDE; instead, provide equivalent guidance for cross-platform tools.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is given a dedicated section and is listed before Azure CLI, with explicit PowerShell command examples. The use of PowerShell scripts is suggested for OAuth authorization, and Windows-centric tools and patterns (such as PowerShell and Azure DevOps) are referenced without equivalent Linux or cross-platform alternatives. There is no mention of Linux shell scripting or other Linux-native tools for deployment or automation.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell, especially for tasks like OAuth authorization.
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
  • When referencing PowerShell, note that PowerShell Core is available cross-platform, or provide equivalent Bash commands.
  • Include references to Linux-native automation tools (e.g., shell scripts, cron jobs) where PowerShell scripts are suggested.
  • Ensure that the order of examples does not always prioritize Windows tools (e.g., alternate the order of PowerShell and CLI sections, or present them together).
  • Explicitly mention that all deployment methods (except PowerShell) are available and supported on Linux.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools and workflows, such as the Azure portal, KuduPlus console, and CMD shell, without mentioning or providing Linux equivalents. All instructions for file access and script management are given in the context of Windows tools, and there are no examples or guidance for users on Linux systems. There is also an absence of PowerShell-specific bias, but the overall workflow assumes a Windows environment.
Recommendations
  • Provide equivalent instructions for accessing and editing files using Linux tools (e.g., Bash shell in Kudu, SSH, or SCP).
  • Mention that KuduPlus can be accessed via Bash as well as CMD, and show navigation steps for both.
  • Include notes or examples for users developing or deploying from Linux or macOS environments.
  • Clarify that the Azure portal and Logic Apps are cross-platform, and highlight any differences or considerations for Linux users.
  • Where file paths are referenced (e.g., site/wwwroot), note that these are accessible from both Windows and Linux environments.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-enterprise-integration-schemas.md ...ogic-apps/logic-apps-enterprise-integration-schemas.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by recommending Visual Studio 2019 and the Microsoft Azure Logic Apps Enterprise Integration Tools Extension (both Windows-only) for schema creation, without mentioning Linux alternatives. Troubleshooting steps reference Windows-specific issues (DPI awareness, registry edits). No Linux or cross-platform schema creation tools or workflows are suggested, and the only code editor example shown is Visual Studio Code, but without explicit Linux guidance. The documentation assumes the use of Windows tools and patterns, with no parity for Linux users.
Recommendations
  • Include guidance for creating schemas using cross-platform or Linux-native tools (e.g., XML editors, command-line tools like xmllint, or open-source alternatives).
  • Mention and provide examples for using Visual Studio Code extensions or other editors available on Linux for schema creation and management.
  • Remove or supplement Windows-specific troubleshooting (e.g., DPI awareness, registry edits) with Linux/macOS equivalents or note that these steps are Windows-only.
  • Explicitly state which steps or tools are Windows-only, and provide Linux/macOS alternatives wherever possible.
  • Add a section or callout for Linux users, outlining recommended tools and steps for schema creation and upload.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page lists PowerShell and .NET scripting as first-class options for running code from Logic Apps, but does not mention or provide parity for Linux-native scripting languages (such as Bash or Python). There are no explicit Linux or cross-platform CLI examples, and the only scripting language with a clear Windows association (PowerShell) is highlighted. Additionally, there is a lack of Linux-specific deployment or management tooling references, and no examples or guidance for Linux users are provided.
Recommendations
  • Add examples and documentation for running Bash and Python scripts from Logic Apps, alongside PowerShell and .NET.
  • Include cross-platform CLI (e.g., Azure CLI) usage examples for deployment, management, and monitoring tasks, not just Azure Portal or Visual Studio Code.
  • Explicitly mention Linux support and provide Linux-specific guidance or troubleshooting where relevant.
  • Ensure that scripting and automation sections do not default to Windows tools, but present cross-platform or Linux-native options equally.
  • Where PowerShell is referenced, clarify that PowerShell Core is cross-platform and provide Linux installation/use instructions.
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: 2025-07-13 21:37
Reviewed by: Unknown
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-based tools (Visual Studio, Azure Storage Explorer) and workflows, with no mention of Linux equivalents or cross-platform alternatives for key steps. Visual Studio and its extensions are highlighted for map creation and editing, and Azure Storage Explorer (a GUI tool most commonly used on Windows) is the only method described for managing blob storage. There are no CLI or Linux-native instructions, and no mention of PowerShell, but the overall workflow assumes a Windows environment.
Recommendations
  • Include instructions for creating and managing maps using cross-platform tools such as the Azure CLI or Azure PowerShell (with explicit Linux/macOS compatibility).
  • Provide examples for uploading assemblies and maps using the Azure CLI, azcopy, or REST API, which are available on Linux and macOS as well as Windows.
  • Mention and document the use of Visual Studio Code (which is cross-platform) more prominently, and clarify that the Data Mapper extension works on Linux/macOS.
  • For storage management, add steps for using az storage blob commands or azcopy for uploading files to blob storage, instead of only Azure Storage Explorer.
  • Explicitly state that all steps can be performed on Linux/macOS, or provide alternative instructions where certain tools are Windows-only.
  • Add a table or section comparing tool availability and usage across Windows, Linux, and macOS.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/mainframe-modernization-overview.md ...rticles/logic-apps/mainframe-modernization-overview.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing Microsoft-centric tools (Host Integration Server, Visual Studio, HIS Designer, 3270 Design Tool) and patterns familiar to Windows/Visual Studio users. There are no examples, tools, or workflows described for Linux or cross-platform development environments. The documentation assumes the use of Windows-based development environments and omits mention of Linux alternatives or parity in tooling.
Recommendations
  • Provide equivalent guidance and examples for Linux-based development environments, including how to use Azure Logic Apps connectors from Linux or cross-platform tools.
  • Mention and, where possible, support open-source or cross-platform alternatives to Visual Studio and Host Integration Server for mainframe integration.
  • Clarify whether the HIS Designer and 3270 Design Tool are available or supported on Linux, and if not, suggest alternative approaches for Linux users.
  • Include CLI-based or code-first examples (e.g., using Azure CLI, REST APIs, or other cross-platform tools) for creating and managing Logic Apps connectors, rather than only GUI/Windows-based workflows.
  • Explicitly state any platform limitations and provide links to Linux-compatible resources or community-supported solutions.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively mentioning PowerShell as a scripting language for code snippets, without referencing Bash or other Linux-native scripting options. Additionally, there are no examples or guidance for Linux users, and the development tools highlighted (Visual Studio Code, Azure portal) are cross-platform but the scripting focus remains Windows-centric. No Linux-specific tools, patterns, or examples are provided.
Recommendations
  • Include examples for running Bash scripts or other Linux-native scripting languages alongside PowerShell and C#.
  • Explicitly mention that Visual Studio Code and the Azure portal are cross-platform, and provide setup or usage notes for Linux users where relevant.
  • Add guidance or links for Linux-based development and deployment workflows, such as using Azure CLI or scripting with Bash.
  • Where PowerShell is referenced, provide equivalent Bash examples to ensure parity for Linux users.
  • Highlight any differences or considerations for Linux environments in migration, deployment, or testing steps.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio on Windows. All instructions, screenshots, and tool references assume the use of Windows and Visual Studio, with no mention of Linux or macOS alternatives. Required tools such as Visual Studio, Azure SDK for .NET, and Azure PowerShell are Windows-centric, and there are no examples or guidance for users on Linux. The use of PowerShell for deployment prompts further reinforces the Windows bias.
Recommendations
  • Provide equivalent instructions and examples for Linux and macOS users, such as using Visual Studio Code, the Azure CLI, or other cross-platform tools.
  • Explicitly mention and link to cross-platform alternatives (e.g., Visual Studio Code, Azure CLI) at the start of the article, not just in passing.
  • Include Linux/macOS-specific setup steps and screenshots where appropriate.
  • Clarify which steps are Windows-only and offer parallel guidance for non-Windows platforms.
  • If PowerShell is required, note how to use it on Linux/macOS, or provide Bash/Azure CLI equivalents.
  • Consider restructuring the documentation to present cross-platform options first or in parallel, rather than focusing exclusively on Windows.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/testing-framework/create-unit-tests-standard-workflow-runs-visual-studio-code.md ...e-unit-tests-standard-workflow-runs-visual-studio-code.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio Code (VS Code) and C# for unit test creation, with all examples and instructions tailored to the Windows ecosystem. There are no Linux-specific instructions, examples, or mentions of alternative tools or languages commonly used in Linux environments. The workflow assumes the use of Windows conventions (e.g., folder structure, file paths, and keyboard shortcuts) and does not address cross-platform considerations or parity.
Recommendations
  • Add explicit statements confirming cross-platform support for Visual Studio Code and the Azure Logic Apps extension, including any known limitations or differences on Linux.
  • Provide Linux-specific instructions or notes where relevant, such as alternative keyboard shortcuts, file path conventions, and installation steps for dependencies.
  • Include examples or guidance for running and managing unit tests in Linux environments (e.g., using .NET CLI instead of Visual Studio tooling, or integrating with Linux-based CI/CD pipelines).
  • Mention and, if possible, provide sample code for alternative programming languages or frameworks supported on Linux, or clarify if C# is the only supported language.
  • Ensure screenshots and UI instructions are not Windows-centric (e.g., avoid showing only Windows-style file explorers or context menus).
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/testing-framework/create-unit-tests-standard-workflow-definitions-visual-studio-code.md ...tests-standard-workflow-definitions-visual-studio-code.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio Code (a cross-platform tool, but often associated with Windows development) and C# (primarily a .NET/Windows-centric language). There are no examples or instructions for Linux or macOS environments, nor is there any mention of command-line alternatives or Linux-specific workflows. The document assumes the use of Visual Studio Code and C# without addressing how Linux users might set up or run these tests, or whether .NET dependencies are cross-platform.
Recommendations
  • Explicitly mention that Visual Studio Code and the Azure Logic Apps extension are available on Linux and macOS, and provide installation/setup instructions for these platforms.
  • Clarify that .NET and C# tooling required for unit tests can be installed and used on Linux (e.g., via .NET Core SDK), and provide links or steps for Linux users.
  • Include at least one example of running or managing tests from the command line (e.g., using dotnet CLI), which is common in Linux workflows.
  • Avoid language that implies Visual Studio Code is a Windows-only tool, and ensure screenshots or instructions are not Windows-specific.
  • If there are any platform-specific limitations or differences, document them clearly for Linux/macOS users.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/perform-advanced-ruleset-tasks.md ...ic-apps/rules-engine/perform-advanced-ruleset-tasks.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily centered on the Microsoft Rules Composer, a Windows-only GUI tool, and all instructions assume use of this tool. There are no examples or guidance for Linux users, nor are any cross-platform or command-line alternatives mentioned. The workflow and examples are deeply tied to .NET and Windows development patterns, with no mention of Linux-compatible approaches or tools.
Recommendations
  • Explicitly state platform requirements and limitations at the start of the documentation, clarifying that the Microsoft Rules Composer is Windows-only.
  • If possible, provide equivalent command-line or cross-platform alternatives for managing rulesets (e.g., using .NET CLI, PowerShell Core, or REST APIs that work on Linux).
  • Include examples or workflows for Linux users, such as how to manipulate rulesets programmatically using .NET Core on Linux.
  • Mention any available or planned Linux-compatible tools, or provide guidance for Linux users on how to interact with rulesets without the GUI.
  • Reorganize sections to clarify platform dependencies before presenting Windows-specific instructions.
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-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Azure PowerShell (and its LogicAppTemplate module) as the only tool for creating Logic App templates, without mentioning cross-platform or Linux-native alternatives such as Azure CLI. The only explicit tooling guidance is for PowerShell, which is traditionally associated with Windows, and no Linux/macOS-specific instructions or examples are provided. This may lead Linux users to believe that template creation is only possible or best supported on Windows platforms.
Recommendations
  • Add equivalent instructions and examples for using Azure CLI (which is cross-platform) to create and deploy Logic App ARM templates.
  • Where PowerShell is mentioned, also mention that Azure CLI can be used, and provide links or references to relevant Azure CLI documentation.
  • If certain features are only available in PowerShell (such as the LogicAppTemplate module), clarify this and suggest alternative approaches for Linux/macOS users.
  • Include at least one example or workflow that demonstrates template deployment or management from a Linux or macOS environment.
  • Review all tooling recommendations to ensure parity for users on non-Windows platforms, and avoid implying that PowerShell is the default or only supported method.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows environments by exclusively referencing PowerShell cmdlets for critical operations (such as incrementing control numbers) and not providing equivalent CLI, Bash, or cross-platform alternatives. There are no Linux shell or Azure CLI examples, and the only automation tooling mentioned is PowerShell, which is traditionally associated with Windows. This may hinder users working in Linux or cross-platform environments.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell cmdlet examples, especially for incrementing control numbers and managing integration accounts.
  • Include Bash or shell script examples where automation is discussed, or clarify if the operation can only be performed via PowerShell.
  • Explicitly state cross-platform support for PowerShell Core if relevant, and provide installation guidance for non-Windows users.
  • Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
  • Ensure that all critical automation steps can be performed using cross-platform tools, or document any limitations.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. The PowerShell deployment method is listed before the Azure CLI, and PowerShell is highlighted as a primary automation tool (including for OAuth consent scripting). There are no explicit Linux or Bash shell examples, and the scripting guidance assumes familiarity with PowerShell, which is traditionally a Windows-centric tool. The use of Azure DevOps and Azure Pipelines, while cross-platform, is also more commonly associated with Windows environments.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell for deployment and automation tasks, especially for OAuth consent scripting.
  • List Azure CLI examples before or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
  • Explicitly mention that Azure CLI and Azure DevOps tools are available and supported on Linux/macOS, and provide links or notes for cross-platform usage.
  • If referencing PowerShell scripts, consider also linking to equivalent Bash or Python scripts (if available) or note how Linux users can adapt the process.
  • In sections discussing automation or scripting, avoid language that implies PowerShell is the only or default option.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-only tool) and its extensions for creating maps and schemas, with no mention of Linux-compatible alternatives. Troubleshooting steps and installation instructions are tailored to Visual Studio, including registry edits and DPI settings, which are not applicable to Linux environments. While Visual Studio Code is mentioned as an option for managing and deploying logic apps, there are no Linux-specific instructions or parity in tooling for artifact creation. PowerShell is also referenced as a management option, but no equivalent Bash or CLI examples are provided.
Recommendations
  • Provide explicit instructions or alternatives for Linux users, such as using Visual Studio Code extensions or cross-platform CLI tools for creating and managing B2B artifacts.
  • Include Linux-compatible workflows and examples, especially for artifact creation and deployment.
  • Mention and document the use of Azure CLI (az logicapp) for resource management alongside PowerShell.
  • Clarify which steps or tools are Windows-only and offer guidance for Linux/macOS users.
  • If no Linux alternatives exist for certain tasks (e.g., map designer), state this clearly and suggest possible workarounds or roadmap intentions.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Logic Apps provides a broad overview and many scenario links, but there is a notable bias toward Windows and Microsoft-centric tooling. PowerShell is specifically called out as a scripting example, and there is no mention of Linux shell scripting or CLI equivalents. The deployment and management sections focus on Azure DevOps and Visual Studio Code, both of which are cross-platform but are often associated with Windows environments. There are no explicit Linux or Bash examples, nor are Linux-native tools or patterns mentioned.
Recommendations
  • Include examples for running Bash or shell scripts from Logic Apps, alongside PowerShell.
  • When referencing scripting, provide parity between PowerShell and Linux shell scripting (e.g., Bash).
  • Highlight cross-platform CLI tools (such as Azure CLI) and show usage examples on both Windows and Linux.
  • Explicitly mention that Visual Studio Code and Azure DevOps are cross-platform, and provide Linux-specific setup or usage notes where relevant.
  • Add links or sections for deploying and managing Logic Apps from Linux environments, including automation with Bash scripts.
  • Ensure that any sample code or walkthroughs that use PowerShell also provide a Bash or Linux shell equivalent.
GitHub Create Pull Request
Logic Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-enterprise-integration-schemas.md ...ogic-apps/logic-apps-enterprise-integration-schemas.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by recommending Visual Studio 2019 and the Microsoft Azure Logic Apps Enterprise Integration Tools Extension (both Windows-only) for schema creation, without mentioning cross-platform or Linux alternatives. Troubleshooting steps reference Windows-specific actions (e.g., registry edits, DPI-unaware mode). There are no examples or guidance for Linux users, and the only code editor alternative mentioned is Visual Studio Code, but without Linux-specific instructions or parity for schema creation tools.
Recommendations
  • Include cross-platform or Linux-native tools for schema creation, such as XMLSpy (if available), Eclipse plugins, or open-source alternatives.
  • Provide instructions for creating and managing schemas using command-line tools available on Linux (e.g., xmllint, xsltproc, or other XML/XSD utilities).
  • Mention and provide examples for using Visual Studio Code extensions or other editors on Linux to create and edit schemas.
  • Avoid referencing Windows-specific troubleshooting steps (e.g., registry edits, DPI-unaware mode) without offering Linux/macOS equivalents or clarifying their platform-specific nature.
  • Explicitly state when a tool or step is Windows-only, and offer Linux/macOS alternatives where possible.
  • Add a section or callout for Linux/macOS users, summarizing recommended workflows and tools for schema creation and management.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily focused on Windows development environments, specifically Visual Studio and related tools (Cloud Explorer, Azure Logic Apps Tools for Visual Studio, Azure PowerShell). There are no references to Linux or cross-platform alternatives, and all instructions, screenshots, and workflows assume the use of Windows and Visual Studio. No mention is made of using Visual Studio Code, CLI tools, or Linux-compatible workflows for managing Logic Apps.
Recommendations
  • Include instructions and examples for managing Logic Apps using Visual Studio Code, which is cross-platform and widely used on Linux and macOS.
  • Provide equivalent workflows using Azure CLI and/or Azure Portal for users who do not have access to Visual Studio on Windows.
  • Mention and link to any available Logic Apps tooling or extensions for Linux/macOS environments.
  • Clarify in the prerequisites and throughout the documentation that the described workflow is Windows/Visual Studio-specific, and offer alternative guidance for non-Windows users.
  • Add PowerShell alternatives using Azure CLI where possible, as Azure CLI is cross-platform.
  • Consider including a table or section comparing Windows and Linux/macOS options for Logic Apps development and management.
GitHub Create Pull Request
← Previous Page 7 of 14 Next →