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 251-275 of 339 flagged pages
Logic Apps
Differences between Standard and Consumption logic apps
.../articles/logic-apps/single-tenant-overview-compare.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. Windows-specific hosting options (App Service Environment v3, Windows plans only) are mentioned repeatedly and prominently, with no equivalent Linux hosting guidance. The documentation references Windows-centric deployment environments before alternatives, and does not clarify Linux support or provide Linux-specific examples. There is a lack of explicit Linux/macOS instructions or parity in tooling, especially regarding local development and deployment. While cross-platform tools like Visual Studio Code and Azure CLI are mentioned, the documentation does not address platform-specific differences or provide Linux/macOS setup guidance.
Recommendations
- Explicitly state whether Standard Logic Apps can be hosted on Linux-based App Service plans and provide guidance for Linux hosting if supported.
- Add Linux/macOS-specific examples and instructions for local development, deployment, and firewall/network configuration.
- Clarify any platform limitations or differences in the Azure Logic Apps runtime and connectors for Linux/macOS users.
- Ensure that cross-platform tools (VS Code, Azure CLI) are presented as first-class options, with any Windows-only steps clearly marked.
- Include troubleshooting and setup notes for Linux/macOS environments, especially for local development and artifact packaging.
Create Pull Request
Logic Apps
Call Azure Functions from workflows
...cles/logic-apps/call-azure-functions-from-workflows.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (Visual Studio, Azure PowerShell) are listed alongside cross-platform options, but Windows tools are often mentioned first or with more detail. PowerShell commands are given as an example for retrieving tenant information, with no equivalent Linux/macOS CLI example. The use of Kudu's CMD console is described, which is a Windows-style shell, without mentioning Bash or cross-platform alternatives. However, Linux/macOS users can generally follow the instructions using Azure CLI and Visual Studio Code, which are cross-platform.
Recommendations
- Provide Azure CLI command examples wherever PowerShell is referenced, especially for tasks like retrieving tenant IDs.
- List cross-platform tools (Azure CLI, Visual Studio Code) before Windows-only tools (Visual Studio, PowerShell) when describing options.
- Mention Bash or cross-platform shells in Kudu, not just CMD.
- Explicitly note that all steps can be performed on Linux/macOS, and clarify any platform-specific differences.
- Add screenshots or instructions for Linux/macOS environments where applicable.
Logic Apps
Create built-in connectors for Standard logic apps
...ogic-apps/create-custom-built-in-connector-standard.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias, especially in the installation and setup sections. PowerShell is presented as the primary method for installing the connector, with explicit PowerShell commands and scripts (add-extension.ps1) shown first and in detail. Output examples use Windows paths and conventions. Bash usage is mentioned only as a wrapper for PowerShell, not as a native alternative, and Linux/macOS-specific instructions or examples are missing. The workflow and testing steps are tightly coupled to Visual Studio Code, but do not address platform-specific differences for Linux/macOS users.
Recommendations
- Provide native Bash or shell script alternatives for installation steps, not just wrappers for PowerShell scripts.
- Include Linux/macOS-specific examples and output paths, or clarify cross-platform differences in file locations and command syntax.
- Offer instructions for using the connector and extension with common Linux/macOS tools and environments (e.g., terminal, VS Code on Linux/macOS).
- Document any prerequisites or limitations for Linux/macOS users, such as script compatibility or required dependencies.
- Present examples in a platform-neutral order, or explicitly note platform-specific steps.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page shows moderate Windows bias, primarily through references to Windows-specific tools (PowerShell, App Service Environment v3 - Windows plans only), and by listing Windows-centric scripting options (PowerShell, .NET, C#) before Linux/macOS equivalents. There is little mention of Linux/macOS-specific tools or workflows, and examples do not clarify cross-platform compatibility. While Azure CLI is mentioned, it is not highlighted equally with PowerShell. The documentation does not provide Linux/macOS-specific examples or guidance, which may create friction for non-Windows users.
Recommendations
- Explicitly mention Linux/macOS compatibility for workflow creation and management tools.
- Provide examples using Azure CLI alongside PowerShell, and clarify CLI usage on Linux/macOS.
- Include references to Linux/macOS hosting options for App Service Environment, or clarify limitations.
- Add Linux/macOS-specific scripting examples (e.g., Bash, Python) where custom code is discussed.
- Ensure parity in documentation for cross-platform development environments (e.g., Visual Studio Code on Linux/macOS).
Logic Apps
Add and Run C# Scripts in Standard Workflows
...lob/main/articles/logic-apps/add-run-csharp-scripts.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing Windows-specific tools and interfaces (Azure portal, KuduPlus console, CMD shell) for file management and workflow development. All step-by-step instructions for uploading, viewing, and editing script files rely on Windows-centric tooling, with no mention of Linux/macOS equivalents or cross-platform alternatives. There are no examples or guidance for performing these tasks from Linux/macOS environments, nor are CLI or cross-platform methods suggested.
Recommendations
- Provide equivalent instructions for Linux/macOS users, such as using Azure CLI, PowerShell Core, or REST API for file management and workflow deployment.
- Mention that the Kudu console is accessible via a browser and can be used from any OS, but clarify how to perform file operations from Linux/macOS terminals.
- Include examples using Bash, SCP, SFTP, or other cross-platform tools for uploading and managing .csx files.
- Add notes or sections explicitly addressing Linux/macOS workflows, including how to access and manipulate workflow files without relying on Windows-only interfaces.
- Consider presenting CLI and cross-platform options before or alongside Windows GUI instructions to reduce perceived prioritization of Windows.
Logic Apps
Why move from BizTalk Server to Azure Logic Apps?
...ticles/logic-apps/biztalk-server-migration-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, primarily through frequent references to Windows-specific tools, technologies, and patterns (e.g., MMC snap-ins, Windows registry, PowerShell, Windows Authentication, Visual Studio Enterprise/Professional, and Windows-only hosting environments). Windows tools and patterns are often mentioned first or exclusively, with limited or no mention of Linux/macOS alternatives, especially in developer tooling, deployment, configuration, and management sections. While Azure Logic Apps and related services are cross-platform, the migration narrative and examples are heavily oriented toward Windows-centric BizTalk Server environments, and Linux/macOS users may need to infer or research equivalent approaches.
Recommendations
- Explicitly mention and provide examples for Linux/macOS environments where possible, especially in developer tooling, deployment, and automation sections.
- Highlight cross-platform capabilities of Azure services (e.g., Azure CLI, Bash scripting, VS Code on Linux/macOS) alongside Windows tools.
- Include Linux/macOS equivalents for configuration management (e.g., environment variables, config files) and avoid exclusive references to Windows registry or MMC.
- When discussing hosting, clarify support for Linux-based Azure App Service environments and containers.
- Provide parity in automation examples (e.g., Bash scripts, Azure CLI) alongside PowerShell.
- List supported developer experiences for Linux/macOS (e.g., VS Code, CLI) in the developer tools section.
- Review and update sections that reference Windows-only authentication or deployment patterns to include cross-platform alternatives.
Logic Apps
Connect to on-premises data sources
...rticles/logic-apps/connect-on-premises-data-sources.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page exhibits a moderate Windows bias. The on-premises data gateway is described as being installed on a 'local computer' without clarifying platform support, but references to 'gateway Windows service account' and PowerShell automation suggest a Windows-centric approach. PowerShell is mentioned as the automation tool for gateway management, with no Linux/macOS alternatives provided. There are no explicit Linux/macOS installation or management instructions, and Windows terminology appears in troubleshooting tips.
Recommendations
- Explicitly state platform support for the on-premises data gateway (e.g., Windows-only or cross-platform).
- If Linux/macOS installation is supported, provide step-by-step instructions and examples for those platforms.
- Offer automation and management examples using cross-platform tools (e.g., Azure CLI, Bash scripts) in addition to PowerShell.
- Replace or supplement references to 'Windows service account' with equivalent instructions for Linux/macOS (e.g., systemd service management).
- Ensure troubleshooting and tips cover Linux/macOS scenarios if supported.
Logic Apps
Connect Workflows to IBM Informix
...s/blob/main/articles/logic-apps/connectors/informix.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits some Windows bias, primarily in the authentication section, where Windows (Kerberos) authentication is mentioned explicitly and linked to Windows Server documentation before any Linux alternatives. The examples and screenshots do not show Linux-specific tools or patterns, and the only authentication guidance with platform specificity is Windows-centric. However, the overall workflow instructions are platform-neutral, focusing on Azure portal usage.
Recommendations
- Include Linux authentication options (such as Kerberos on Linux or other secure methods) and provide links to relevant Linux documentation.
- Clarify whether the on-premises data gateway and Informix connector support Linux hosts, and if so, provide setup instructions for Linux.
- Add examples or screenshots showing Informix connections from Linux environments, or note any platform-specific differences.
- Mention cross-platform compatibility explicitly in prerequisites and connection steps.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. Most installation and configuration instructions, file paths, and tooling references are Windows-centric (e.g., C:\Program Files, .exe utilities, PowerShell scripts). Key SAP client libraries and cryptographic tools are described only for Windows, with no Linux/macOS equivalents or guidance. The only example for converting PSE files to base64 uses PowerShell, with no alternative for Linux/macOS users. Steps for extracting SAR files and setting up assemblies are written for Windows environments, and troubleshooting/logging tools are Windows-specific.
Recommendations
- Provide Linux/macOS equivalents for all installation, configuration, and file management steps (e.g., using bash, openssl, or other cross-platform tools).
- Include examples for converting PSE files to base64 using Linux/macOS commands (e.g., base64 CLI).
- Document how to install and use SAP NCo libraries and CommonCryptoLib on Linux/macOS, if supported, or clarify platform limitations.
- Mention non-Windows paths and conventions (e.g., /opt, /usr/local) alongside Windows paths.
- Offer troubleshooting and logging guidance for Linux/macOS environments, including alternative tools to PerfView and fuslogvw.
- Explicitly state platform support and limitations for SAP connectors and related Azure Logic Apps features.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates a moderate Windows bias, primarily in troubleshooting and network configuration sections. Windows-specific tools and file paths (e.g., %windir%\System32\drivers\etc\services and hosts) are referenced exclusively for resolving network service and host name issues. These instructions are given without Linux/macOS equivalents, and Windows file paths are mentioned first and solely. The rest of the documentation is platform-neutral, focusing on Azure Logic Apps and SAP connectors, but the troubleshooting steps could create friction for Linux/macOS users managing on-premises data gateways.
Recommendations
- Add equivalent instructions for Linux/macOS, such as editing /etc/services and /etc/hosts for service and host name resolution.
- Explicitly state that the troubleshooting steps apply to Windows and provide parallel steps for other operating systems.
- Where file paths or tools are mentioned, include both Windows and Linux/macOS formats.
- Consider a cross-platform troubleshooting section or table summarizing steps for each OS.
Logic Apps
Create Standard logic app workflows for hybrid deployment
...ic-apps/create-standard-workflows-hybrid-deployment.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias, especially in troubleshooting and deployment sections. PowerShell scripts and commands are referenced as the primary method for diagnosing issues, and instructions often specify running Visual Studio Code as administrator (a Windows concept). Troubleshooting steps and installation commands for Kubernetes and SMB drivers are given using Windows PowerShell and Windows command prompt, with no equivalent Linux/macOS instructions. The use of Windows terminology and tools is prevalent, and Linux alternatives are not mentioned or are omitted entirely.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell and Windows command prompt instructions, such as using bash, sh, or zsh.
- Include troubleshooting scripts or guidance for Linux environments (e.g., bash scripts alongside PowerShell).
- Clarify that Visual Studio Code can be run with elevated privileges on Linux/macOS (e.g., using 'sudo'), and provide platform-specific instructions.
- Add explicit examples for Linux/macOS users for Kubernetes and SMB CSI driver installation and verification.
- Ensure that all CLI commands (az, kubectl, helm) are shown in a cross-platform way, noting any OS-specific differences.
- Avoid language that assumes a Windows environment by default; present instructions for all major platforms in parallel or note differences clearly.
Logic Apps
Create and manage integration accounts
...s/enterprise-integration/create-integration-account.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides instructions for managing Azure Logic Apps integration accounts primarily using the Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, PowerShell and the Azure portal are traditionally Windows-centric tools. PowerShell is mentioned as an option for creating and deleting integration accounts, but no equivalent Linux/macOS shell examples (e.g., Bash scripts) are provided. The Azure portal is referenced first in most sections, and screenshots and step-by-step guides are tailored to the portal experience, which is most familiar to Windows users. There is no explicit mention of Linux/macOS-specific workflows, nor are there examples using native Linux tools or shell environments. Visual Studio Code is mentioned for Standard logic apps, which is cross-platform, but the majority of examples and tooling references lean toward Windows-first experiences.
Recommendations
- Add explicit Bash shell examples for common tasks (e.g., using Azure CLI in Bash on Linux/macOS).
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample terminal screenshots from non-Windows environments.
- Where PowerShell is referenced, offer equivalent Bash or shell script examples for Linux/macOS users.
- Balance the order of instructions so that cross-platform tools (Azure CLI, VS Code) are presented before Windows-centric tools (PowerShell, Azure portal).
- Include notes or sections for Linux/macOS users, highlighting any differences or considerations when using the Azure portal, CLI, or other tools.
Logic Apps
Reference for functions in workflow expressions
.../articles/logic-apps/expression-functions-reference.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally cross-platform and does not provide OS-specific command-line examples. However, there is a notable Windows bias in the handling of time zones and date formats: references to Microsoft Windows Default Time Zones are used for specifying time zone names, and .NET format strings are referenced throughout. There is no mention of Linux/Unix time zone naming conventions (e.g., IANA/Olson database), and Windows time zone names are required for several functions. This may create friction for Linux/macOS users who are more familiar with IANA time zone names.
Recommendations
- Add guidance or mapping for users on Linux/macOS to convert IANA/Olson time zone names to Microsoft Windows time zone names.
- Explicitly state that only Windows time zone names are supported, and provide a link or table mapping common IANA names to Windows equivalents.
- Consider supporting IANA time zone names in the product or providing a conversion utility.
- Clarify that .NET format strings are required and provide examples for users unfamiliar with .NET conventions.
Logic Apps
Create Standard Workflows with Visual Studio Code
...c-apps/create-standard-workflows-visual-studio-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (e.g., Windows Defender Firewall, regedit, .exe file references) are mentioned first or exclusively in several critical setup and troubleshooting steps. Some examples and instructions (such as registry edits and firewall prompts) are Windows-only, with Linux/macOS alternatives either missing, less detailed, or relegated to notes. The use of Windows paths and screenshots further reinforces this bias. While Linux/macOS users can generally follow along, they may encounter friction or require additional research to adapt steps for their platforms.
Recommendations
- Provide Linux/macOS equivalents for all Windows-specific instructions, especially for firewall configuration, registry edits, and command-line tool usage.
- Include Linux/macOS screenshots and file path examples alongside Windows ones.
- When referencing executables (e.g., ngrok.exe, func.exe), clarify the equivalent binaries for Linux/macOS.
- For troubleshooting steps involving Windows Registry (e.g., URI length limits), offer guidance for Linux/macOS environments (e.g., web server config changes).
- Avoid presenting Windows steps first by default; alternate or group by OS.
- Explicitly state cross-platform compatibility for all tools and dependencies.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation mentions the ability to add and run PowerShell scripts in Standard workflows, but does not mention or provide examples for Bash, shell scripts, or other Linux/macOS scripting options. The scripting section is Windows-centric, and Linux/macOS users may not see their preferred tools or patterns represented.
Recommendations
- Add examples and documentation for running Bash or shell scripts within Logic Apps workflows.
- Explicitly mention support for Linux/macOS scripting environments if available.
- Provide parity in scripting documentation by listing Bash/shell alongside PowerShell and C#.
- Clarify any platform-specific limitations or requirements for script execution.
Logic Apps
Create Consumption logic app templates for deployment
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-create-azure-resource-manager-templates.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively uses PowerShell-based examples and Windows-centric tooling (LogicAppTemplate PowerShell module, ARMClient, file paths like C:\template.json). There are no Linux/macOS shell examples, nor any mention of cross-platform alternatives or instructions for Bash, Azure CLI, or other non-Windows environments. This creates friction for Linux/macOS users, who must adapt the instructions themselves.
Recommendations
- Provide equivalent Bash/Azure CLI examples for generating and deploying templates.
- Clarify cross-platform compatibility of the LogicAppTemplate module and ARMClient, and offer installation instructions for Linux/macOS.
- Use platform-neutral file paths in examples (e.g., ./template.json instead of C:\template.json).
- Explicitly mention any limitations or required adaptations for Linux/macOS users.
- Consider listing Linux/macOS instructions alongside or before Windows/PowerShell instructions to improve parity.
Logic Apps
Deploy Resource Manager templates
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-deploy-azure-resource-manager-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for deploying Resource Manager templates, but PowerShell (a Windows-centric tool) is listed before CLI, and the OAuth authorization section specifically recommends a PowerShell script for automated consent, with no mention of Linux/macOS alternatives. There are no explicit Linux/macOS-only gaps, but the ordering and scripting recommendations show a subtle Windows bias.
Recommendations
- Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform.
- In the OAuth authorization section, provide a Bash or Python script alternative for Linux/macOS users, or clarify that the CLI can be used for similar tasks.
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
- Where PowerShell scripts are referenced, link to or provide equivalent Bash/Python samples if available.
Logic Apps
Disaster recovery for integration accounts
...ic-apps-enterprise-integration-b2b-business-continuity.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing PowerShell cmdlets for critical disaster recovery operations (such as incrementing control numbers in agreements). No equivalent CLI, Bash, or cross-platform instructions are provided, and there is no mention of Linux/macOS alternatives for these tasks. This creates friction for users on non-Windows platforms, as PowerShell is not natively available and may require additional installation or adaptation.
Recommendations
- Provide Azure CLI equivalents for all PowerShell cmdlet instructions, especially for incrementing control numbers and managing integration accounts.
- Include Bash script examples or note how to use Azure CLI on Linux/macOS for the same operations.
- Explicitly state platform requirements for PowerShell steps and offer guidance for installing PowerShell Core on Linux/macOS if no CLI alternative exists.
- Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
- Add a section clarifying platform compatibility for all automation steps.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Visual Studio (Windows-only) is repeatedly referenced as a primary tool for map creation and management, with detailed instructions and troubleshooting notes specific to Windows environments (e.g., DPI-unaware mode, registry edits). Visual Studio Code is mentioned as a cross-platform alternative, but it is often secondary in order and detail. Azure Storage Explorer is referenced, which is available on multiple platforms, but screenshots and instructions use Windows UI conventions. There are no Linux/macOS-specific examples, nor are CLI alternatives (such as Azure CLI) provided for tasks like uploading maps or assemblies.
Recommendations
- Provide explicit instructions and screenshots for Linux/macOS users, especially for Visual Studio Code workflows.
- Include Azure CLI or REST API examples for uploading maps and assemblies, as these are cross-platform and avoid reliance on GUI tools.
- When listing tools, mention cross-platform options first (e.g., Visual Studio Code before Visual Studio), and clarify platform compatibility.
- Add troubleshooting notes relevant to Linux/macOS environments, not just Windows-specific issues.
- Ensure parity in detail and guidance for Visual Studio Code workflows compared to Visual Studio.
Logic Apps
Add authentication for calls to custom APIs
...les/logic-apps/logic-apps-custom-api-authentication.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides step-by-step instructions for creating Microsoft Entra application identities using the Azure portal and PowerShell, but does not mention or provide examples for Linux/macOS CLI tools (such as Azure CLI or Bash scripting). PowerShell is presented as the only command-line option, and its section is given equal prominence to the portal method. There are no references to Linux-specific tools or workflows, and no guidance for users who may prefer Bash or Azure CLI on non-Windows platforms.
Recommendations
- Add equivalent instructions using Azure CLI (az ad app create, az ad sp create-for-rbac, etc.), which is cross-platform and commonly used on Linux/macOS.
- Explicitly mention that PowerShell commands can be run on Linux/macOS (via PowerShell Core), or provide Bash/CLI alternatives.
- Include notes or links for Linux/macOS users on how to install and use Azure CLI and/or PowerShell Core.
- Ensure that examples and screenshots do not assume a Windows environment (e.g., avoid Windows-specific UI elements or terminology).
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page references running PowerShell scripts from Standard workflows and includes migration guidance for BizTalk Server and Power Automate—both traditionally Windows-centric tools. There are no explicit Linux/macOS shell (e.g., Bash) examples or mentions of Linux-specific tools or patterns. The scripting section lists PowerShell and C# but omits Bash or other Unix-like options, and there are no examples or walkthroughs for Linux users. This creates a subtle bias toward Windows environments and workflows.
Recommendations
- Add examples and documentation for running Bash scripts from Logic Apps workflows, alongside PowerShell and C#.
- Explicitly mention support for Linux/macOS environments in relevant sections, especially in scripting and deployment.
- Include migration guidance for Linux-based integration tools (if applicable), not just BizTalk Server and Power Automate.
- Provide parity in walkthroughs and tutorials for Linux/macOS users, including CLI usage and shell scripting.
- Clarify any platform-specific limitations or requirements for workflow actions involving custom code.
Logic Apps
Set Up SQL Database Storage for Standard Workflows
...les/logic-apps/set-up-sql-database-storage-standard.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows-based App Service plans are exclusively supported for hosting Standard Logic Apps, with explicit instructions not to choose Linux-based plans. The examples and instructions for local development focus on Visual Studio Code and SQL Express (a Windows-centric tool), with no mention of Linux-compatible SQL servers (e.g., SQL Server on Linux, PostgreSQL, MySQL) or Linux development workflows. There are no examples or guidance for Linux users, such as using Azure CLI on Linux, connecting to SQL Server running on Linux, or deploying from Linux environments.
Recommendations
- Add explicit support statements and examples for Linux-based SQL servers (e.g., SQL Server on Linux, PostgreSQL, MySQL) where applicable.
- Provide instructions for setting up and connecting to SQL databases from Linux environments, including connection string examples for Linux-hosted SQL Server.
- Include guidance for using Azure CLI and other cross-platform tools for deployment and configuration, not just Visual Studio Code.
- Clarify whether Linux-based App Service plans will be supported in the future, or provide rationale for their exclusion.
- Offer troubleshooting tips and known limitations for Linux users attempting similar workflows.
Logic Apps
Create workflows with multiple Azure services
...ic-apps/tutorial-process-email-attachments-workflow.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific tools (Azure Storage Explorer) are required and referenced throughout, with no mention of Linux/macOS alternatives. When command-line options are given, Azure PowerShell is listed before Azure CLI, and PowerShell-specific links are provided. The function app creation process highlights Windows as the default/preferred OS, and in-portal editing is only supported on Windows. There are no explicit Linux/macOS instructions or screenshots, and no mention of how to perform equivalent steps on those platforms.
Recommendations
- Explicitly mention and provide instructions for using Azure Storage Explorer on Linux/macOS, or suggest cross-platform alternatives (e.g., azcopy, Azure CLI, web portal).
- When listing command-line options, present Azure CLI first or equally alongside PowerShell, as CLI is cross-platform.
- Include screenshots and workflow steps for Linux/macOS users where UI or tool behavior differs.
- Clarify limitations of in-portal editing for non-Windows users and provide guidance for local development on Linux/macOS.
- Add troubleshooting notes or links for Linux/macOS users regarding authentication, file paths, and tool installation.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing the Azure portal and Microsoft 365 services, with all examples and screenshots based on Microsoft tools and interfaces. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, REST APIs, or cross-platform automation tools. The documentation assumes users interact through graphical interfaces typical of Windows environments and does not mention alternative workflows or tools available on Linux/macOS.
Recommendations
- Add examples using Azure CLI and REST API for setting up OBO flows, which are cross-platform and usable on Linux/macOS.
- Include instructions or screenshots for accessing Azure Logic Apps via browser on Linux/macOS, clarifying that the portal is web-based and not Windows-specific.
- Mention PowerShell and CLI options side-by-side, or provide equivalent bash/Linux shell commands where relevant.
- Explicitly state that the workflow can be completed from any OS with a supported browser, and provide troubleshooting tips for Linux/macOS environments.
- Reference cross-platform authentication tools (e.g., MSAL libraries for Python, Node.js) for agent development and testing.
Logic Apps
Set up your own infrastructure for Standard logic app workflows
...t-up-standard-workflows-hybrid-deployment-requirements.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. Windows-specific tools (PowerShell, Chocolatey) are used for key installation steps, such as installing kubectl and Helm, with no Linux/macOS alternatives provided. PowerShell commands (e.g., Set-ExecutionPolicy) are referenced for script execution and environment setup, and Windows SMB file share setup is described in detail before mentioning Azure Files. The use of Windows tools and patterns is presented as the default, and Linux/macOS users must infer or research their own equivalents. Linux-specific instructions (e.g., mounting SMB shares, using apt-get) are only briefly mentioned and lack the same depth as Windows steps.
Recommendations
- Provide explicit Linux/macOS installation instructions for kubectl and Helm (e.g., using apt, yum, brew, or official binaries).
- Include Linux/macOS alternatives for PowerShell commands, such as using chmod for script execution permissions.
- Offer parity in SMB file share setup instructions for Linux (e.g., using Samba server configuration, mounting instructions, and security considerations).
- When referencing scripts, clarify how to run them on Linux/macOS, including prerequisites and execution policies.
- Present cross-platform examples side-by-side or indicate platform-specific steps clearly.
- Avoid assuming Chocolatey or PowerShell is available; mention platform-agnostic installation methods first.