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 201-225 of 339 flagged pages
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing explicit mention and guidance for creating Logic App templates using Azure PowerShell (with the LogicAppTemplate module), but does not mention or provide equivalent examples for Linux or cross-platform CLI tools (such as Azure CLI). The only automation tool referenced for template creation is PowerShell, which is primarily associated with Windows environments. There are no Linux shell or Azure CLI examples, nor is there a discussion of cross-platform approaches. This may leave Linux or macOS users without clear guidance for automating Logic App deployments.
Recommendations
- Add equivalent instructions and examples for creating and deploying Logic App templates using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- When referencing automation tools, mention Azure CLI before or alongside Azure PowerShell to avoid implying a Windows-first workflow.
- Provide sample shell (bash) scripts or command-line snippets for Linux/macOS users where appropriate.
- Explicitly state that all template deployment steps can be performed on any OS using Azure CLI, and link to relevant cross-platform documentation.
- Review and update any tips or notes that currently reference only PowerShell to include Azure CLI alternatives.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: (1) Instructions for accessing the Kudu environment and file paths in the Azure portal use Windows-centric terminology (e.g., CMD, backslashes in paths), with no mention of Linux alternatives or Bash; (2) The 'WEBSITE_NODE_DEFAULT_VERSION' setting is described as applying 'when running your logic app workflows on Windows', with no equivalent guidance for Linux; (3) There are no examples or instructions for managing app or host settings using Linux-native tools or environments (e.g., Bash, Linux file paths, or Linux-based Azure App Service environments).
Recommendations
- Include Linux/Bash equivalents alongside Windows-specific instructions, especially for accessing the Kudu environment and navigating file paths (e.g., show both CMD and Bash navigation).
- Clarify which settings or behaviors differ between Windows and Linux hosting environments, and provide explicit guidance for both.
- When referencing settings like 'WEBSITE_NODE_DEFAULT_VERSION', explain how this applies (or not) to Linux environments, and provide Linux-specific configuration steps if needed.
- Add examples of managing app and host settings using Linux-native tools (e.g., Bash scripts, Linux file navigation, or Linux-based Azure CLI usage).
- Review all file path examples to ensure both Windows (backslash) and Linux (forward slash) conventions are represented where appropriate.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/handle-long-running-stored-procedures-sql-connector.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/handle-long-running-stored-procedures-sql-connector.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page focuses exclusively on SQL Server Agent (a Windows-centric tool) and Azure Elastic Job Agent for job orchestration, with all management examples and screenshots referencing SQL Server Management Studio (SSMS), which is primarily a Windows application. There are no examples or mentions of Linux-native tools or cross-platform alternatives for managing jobs or interacting with SQL Server/Azure SQL. The documentation does not provide parity for Linux users in terms of tooling or workflow.
Recommendations
- Include examples or references to cross-platform tools such as Azure Data Studio, sqlcmd, or PowerShell Core (which runs on Linux) for managing jobs and interacting with SQL Server/Azure SQL.
- Mention and provide examples for using Linux-compatible automation/orchestration tools (e.g., cron jobs, systemd timers, or Azure CLI) to trigger or monitor long-running stored procedures.
- Add screenshots and walkthroughs using cross-platform tools (e.g., Azure Data Studio) in addition to or instead of SSMS.
- Clarify which steps or tools are Windows-only and provide Linux alternatives where possible.
- Highlight any differences or requirements for users running SQL Server on Linux (e.g., SQL Server Agent is available on SQL Server for Linux, but management is different).
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/install-on-premises-data-gateway-workflows.md
...gic-apps/install-on-premises-data-gateway-workflows.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All installation instructions, screenshots, and operational details assume a Windows environment. There is no mention of Linux or macOS support, nor are there any examples or instructions for non-Windows systems. The documentation references Windows-specific tools (e.g., PowerShell cmdlets, Windows service accounts), and even basic commands (like 'whoami /upn') are Windows-only. The use of PowerShell for automation is highlighted without Linux alternatives.
Recommendations
- Explicitly state whether the on-premises data gateway is supported on Linux or macOS. If not, clarify this early in the documentation.
- If Linux/macOS support exists, provide parallel installation and configuration instructions, including relevant screenshots and command-line examples.
- Offer automation examples using cross-platform tools (e.g., Azure CLI, bash scripts) in addition to PowerShell.
- Reference Linux equivalents for commands (e.g., how to find the UPN or equivalent on Linux).
- Discuss service management (start/stop/restart) for the gateway on Linux if supported, or clarify that only Windows services are available.
- When mentioning Windows-specific tools or patterns, provide context or alternatives for non-Windows users.
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 →
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 mentioning automation tools, referencing Visual Studio (a primarily Windows IDE) with detailed steps, and omitting equivalent Linux/CLI workflows or editors. There are no explicit Linux or cross-platform editor instructions, and PowerShell is mentioned before CLI, reinforcing a Windows-first perspective.
Recommendations
- List Azure CLI before or alongside Azure PowerShell when mentioning automation tools, to reflect cross-platform parity.
- Provide explicit instructions or examples for editing workflow JSON using cross-platform editors such as VS Code on Linux/macOS, or command-line tools (e.g., nano, vim, or code command).
- Include Linux/macOS-specific deployment and editing workflows, such as using Azure CLI in Bash or other shells.
- Balance Visual Studio references with equivalent steps for Visual Studio Code or other cross-platform tools.
- Avoid assuming Visual Studio as the default editor; clarify that it is Windows-only and suggest alternatives for other platforms.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell environments. All examples and instructions are provided exclusively using PowerShell commands and Windows file paths (e.g., C:\template.json). There is no mention of Linux or macOS equivalents, nor are there CLI/bash examples or cross-platform instructions. The tools and modules referenced (such as LogicAppTemplate and ARMClient) are presented in a PowerShell-centric manner, and installation steps assume a Windows/PowerShell environment.
Recommendations
- Provide equivalent examples using Azure CLI and bash shell commands for Linux/macOS users.
- Include file path examples using both Windows (C:\...) and Linux/macOS (/home/user/...) conventions.
- Clarify whether the LogicAppTemplate and ARMClient tools are cross-platform, and if so, provide installation and usage instructions for Linux/macOS.
- Add a section or callout specifically addressing Linux/macOS users, outlining any differences or prerequisites.
- Where possible, present Azure CLI examples before or alongside PowerShell examples to promote cross-platform parity.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-custom-api-authentication.md
...les/logic-apps/logic-apps-custom-api-authentication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing PowerShell as the only command-line example for creating Microsoft Entra application identities, with no equivalent Bash, Azure CLI, or Linux-native instructions. The PowerShell section is explicitly called out, and there is no mention of cross-platform tools or commands. Additionally, the documentation refers to 'PowerShell' and 'commandlet' terminology, which are strongly associated with Windows environments. There are no examples or guidance for users on Linux or macOS platforms.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Clearly label both PowerShell and Azure CLI sections, and present them in parallel tabs or sections to ensure parity.
- Avoid using Windows-specific terminology (such as 'commandlet') without also referencing cross-platform equivalents.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant documentation.
- Consider including Bash script examples or references for Linux users where appropriate.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is given a dedicated section before Azure CLI, and scripting examples for OAuth consent reference PowerShell specifically, with no mention of Bash or Linux-native alternatives. The Azure DevOps and Azure Pipelines sections focus on Microsoft-centric tools, which are more commonly used in Windows environments. There are no explicit Linux or Bash examples, and no mention of cross-platform scripting approaches.
Recommendations
- Provide Bash or shell script examples alongside PowerShell for deployment and OAuth authorization tasks.
- Explicitly state that Azure CLI commands are cross-platform and can be run on Windows, macOS, and Linux.
- When referencing scripting for OAuth consent, include or link to Bash/Linux-compatible scripts or note how to adapt the process for non-Windows environments.
- Balance the order of sections by presenting Azure CLI before or alongside PowerShell, as CLI is often preferred in Linux/macOS environments.
- Mention cross-platform CI/CD tools (such as GitHub Actions) in addition to Azure DevOps, or clarify that Azure Pipelines can run on Linux agents.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively referencing PowerShell cmdlets for critical disaster recovery operations (such as incrementing control numbers) and does not provide equivalent instructions or examples for Linux or cross-platform environments. There are no CLI, Bash, or REST API alternatives mentioned, and the only automation tooling discussed is PowerShell, which is traditionally associated with Windows, despite now being cross-platform. This may hinder Linux users or those preferring non-Windows automation tools.
Recommendations
- Provide equivalent Azure CLI commands or Bash script examples for all PowerShell cmdlet instructions, especially for incrementing control numbers and managing integration accounts.
- Mention REST API alternatives where available, with example requests, to ensure platform-agnostic automation.
- Explicitly state if PowerShell Core (cross-platform) is supported and provide installation guidance for Linux/macOS if PowerShell is required.
- Ensure that all automation steps are demonstrated with both Windows (PowerShell) and Linux (CLI/Bash) tooling, or clarify any platform limitations.
- Add a section or callout for Linux users, summarizing supported tools and approaches for disaster recovery tasks.
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 →
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, without mentioning any Linux-compatible alternatives or workflows. Troubleshooting steps and installation instructions are also tailored to Visual Studio on Windows. While Visual Studio Code is mentioned as an option for managing and deploying logic apps, there are no Linux-specific examples or guidance, and PowerShell (primarily associated with Windows, though cross-platform) is listed before any Linux-native tools or CLI alternatives.
Recommendations
- Provide explicit guidance and examples for Linux users, such as using the Azure CLI or Visual Studio Code for all artifact creation and deployment steps.
- List cross-platform tools (e.g., Visual Studio Code, Azure CLI) before or alongside Windows-only tools like Visual Studio.
- Clarify which steps or tools are Windows-specific and offer Linux/macOS alternatives where possible.
- Include troubleshooting and installation notes relevant to Linux environments.
- If certain features (like map/schema design) are only available on Windows, state this clearly and suggest possible workarounds or roadmap plans for Linux support.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-only tool) and the Microsoft Azure Logic Apps Enterprise Integration Tools Extension for schema creation, without mentioning cross-platform or Linux alternatives. Troubleshooting steps and notes focus on Windows-specific issues (e.g., DPI awareness, registry edits). No Linux or macOS equivalents or instructions are provided for schema creation or tool installation, and Visual Studio Code is only mentioned for uploading schemas, not for schema creation.
Recommendations
- Include instructions for creating schemas using cross-platform tools (e.g., XML editors available on Linux/macOS, or command-line tools like xmllint or xsd).
- Mention and provide examples for using Visual Studio Code (which is cross-platform) with relevant extensions for schema creation and editing.
- If possible, provide guidance for using open-source or platform-agnostic tools to generate and validate schemas.
- Add troubleshooting notes relevant to Linux/macOS environments, or clarify when steps are Windows-specific.
- Ensure that all tool recommendations and examples are either cross-platform or have clear Linux/macOS alternatives documented.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page references running PowerShell scripts from Standard workflows and includes a section on running PowerShell, but does not mention Bash, shell scripts, or Linux-native scripting options. There are no explicit Linux/Unix-specific examples or references to Linux tools, and the scripting section is Windows-centric. Additionally, there are no deployment or management instructions that highlight Linux CLI or Bash usage, and the examples for code execution focus on Windows technologies.
Recommendations
- Add examples and documentation for running Bash or shell scripts from Logic Apps workflows, alongside PowerShell.
- Include references to Linux-native tools and scripting environments where applicable, such as using Azure CLI in Bash.
- Provide parity in code execution examples by showing both PowerShell (Windows) and Bash (Linux) script integration.
- Where PowerShell is mentioned, clarify that cross-platform PowerShell Core is supported, or provide Linux-specific guidance if available.
- In deployment and management sections, add examples using Linux-based automation tools and shell environments.
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
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exhibits a Windows bias in several areas. PowerShell is used as the primary or only example for certificate conversion and base64 encoding, with no equivalent Linux or cross-platform commands provided. When troubleshooting certificate issues, the guidance focuses on Windows tools (cert mmc/PowerShell) and only mentions OpenSSL as an afterthought, without providing Linux-specific instructions. This approach may hinder Linux or macOS users, as it assumes familiarity with Windows tooling and does not offer parity in examples or guidance.
Recommendations
- For all code or command-line examples (such as converting PFX to base64), provide both Windows (PowerShell) and Linux/macOS (OpenSSL, shell) equivalents side by side.
- When troubleshooting certificate issues, include Linux/macOS-specific steps and error messages, not just Windows tools.
- Avoid referencing Windows tools (e.g., cert mmc, PowerShell) as the default or only method; instead, present cross-platform alternatives first or equally.
- Where screenshots or UI steps are shown, clarify if any steps are platform-specific and provide alternatives if needed.
- Review all sections for implicit Windows assumptions and ensure Linux users can follow the documentation without needing to translate or research missing steps.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-serverless-overview.md
.../articles/logic-apps/logic-apps-serverless-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by prioritizing Windows-centric tools (Visual Studio, Azure PowerShell) and workflows, mentioning them before or instead of Linux-friendly alternatives. There are no explicit Linux or cross-platform CLI examples, and the quickstart and getting started sections focus on the Azure portal and Visual Studio, which are traditionally Windows-first tools. Linux-native development tools and workflows (such as Azure CLI, Bash, or VS Code on Linux) are not highlighted or exemplified.
Recommendations
- Include explicit examples and quickstarts using cross-platform tools such as Azure CLI and Visual Studio Code, especially on Linux.
- Mention and provide links to Linux-friendly workflows and tools (e.g., Bash scripts, deployment from Linux terminals, VS Code on Linux).
- Balance the order of tool mentions so that Visual Studio Code and Azure CLI are listed before or alongside Visual Studio and Azure PowerShell.
- Add sample commands or walkthroughs for Linux users, such as deploying Logic Apps or Functions from a Linux shell.
- Clarify that all major development workflows are supported on Linux, macOS, and Windows, and provide documentation links for each platform.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft-centric tools (such as Host Integration Server, Visual Studio, HIS Designer, and 3270 Design Tool) for mainframe and midrange integration. There are no mentions of Linux-based tools, development environments, or cross-platform alternatives. All example tooling and workflows assume a Windows environment, and there are no instructions or guidance for Linux users.
Recommendations
- Include information about cross-platform or Linux-compatible alternatives for mainframe and midrange integration, if available.
- Provide examples or workflows using non-Windows development environments (such as VS Code on Linux or Mac, or command-line tools).
- Explicitly state platform requirements and, where possible, offer guidance for Linux users (e.g., running tools in containers, using remote development, or alternative open-source tools).
- Balance tool recommendations by mentioning both Windows and Linux options, or clarify if certain features are Windows-only and suggest workarounds.
- Add a section addressing Linux developer scenarios, even if only to acknowledge limitations and provide suggested approaches.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments, specifically Visual Studio on Windows. All examples, tool references, and workflows assume the use of Visual Studio, Cloud Explorer, and Azure PowerShell—tools that are either unavailable or have limited support on Linux. There are no instructions or alternatives for Linux users, such as using Visual Studio Code, Azure CLI, or cross-platform editors. The documentation does not mention Linux or macOS compatibility, nor does it provide parity in tooling or workflow for non-Windows platforms.
Recommendations
- Add equivalent instructions for managing Logic Apps using Visual Studio Code, which is cross-platform, and the Azure Logic Apps (Standard) extension.
- Include examples using Azure CLI (az logicapp) for tasks such as deployment, downloading, and managing Logic Apps, as Azure CLI is available on Linux, macOS, and Windows.
- Document how to edit and manage Logic Apps using other cross-platform editors (e.g., VS Code, JetBrains Rider) and JSON templates.
- Explicitly state the platform limitations of Visual Studio and Cloud Explorer, and provide links or references to Linux/macOS-compatible alternatives.
- Where PowerShell is mentioned, provide equivalent Azure CLI commands.
- Add a section or callout for Linux/macOS users, outlining supported workflows and tools for Logic Apps management.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias primarily by referencing PowerShell as the only scripting language example for running scripts within workflows, without mentioning or providing examples for Linux-native scripting options such as Bash or shell scripts. There is also a lack of Linux-specific tooling or development environment references, with a focus on Visual Studio Code and PowerShell, both of which are traditionally associated with Windows environments, even though VS Code is cross-platform. No Linux-first or cross-platform command-line examples are provided.
Recommendations
- Include examples for running Bash or shell scripts in Standard workflows, alongside PowerShell and C#.
- Explicitly mention and provide examples for developing and deploying Logic Apps from Linux and macOS environments, not just Windows.
- Reference cross-platform tools and editors (such as VS Code) in a way that highlights their availability and parity on Linux and macOS.
- If PowerShell is mentioned, clarify that PowerShell Core is cross-platform, and provide Linux usage examples.
- Add a section or note about how to perform local development, debugging, and deployment from Linux systems, including any prerequisites or differences.
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 →
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, with no mention of Linux or macOS alternatives. Windows-specific tools (Visual Studio, Azure PowerShell) are required, and there are no examples or guidance for Linux users. The use of PowerShell for deployment prompts further reinforces the Windows-centric approach.
Recommendations
- Provide equivalent instructions for Linux and macOS users, such as using Visual Studio Code or the Azure CLI for Logic Apps development and deployment.
- Include references and links to cross-platform tools and workflows, e.g., how to use VS Code with the Logic Apps extension, or how to deploy Logic Apps using the Azure CLI.
- Add Linux/macOS-specific setup and deployment steps, including screenshots where appropriate.
- Clearly indicate at the beginning that the guide is Windows-specific, and direct users on other platforms to alternative guides.
- Where PowerShell is mentioned, also provide Bash/Azure CLI equivalents for cross-platform compatibility.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/set-up-sql-db-storage-single-tenant-standard-workflows.md
...set-up-sql-db-storage-single-tenant-standard-workflows.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (e.g., SQL Server Management Studio, MSI installers), mentioning Windows authentication for local development, and omitting explicit Linux or cross-platform command-line examples. The setup and development workflows are described primarily in the context of Visual Studio Code and Azure portal, but there is no mention of Linux-specific development environments, tools, or authentication methods. The documentation assumes a Windows-centric environment for local development and SQL server setup.
Recommendations
- Add explicit instructions and examples for Linux environments, such as using Azure CLI, Bash, or cross-platform SQL tools (e.g., Azure Data Studio, sqlcmd).
- Mention and provide examples for Linux-compatible authentication methods (e.g., SQL authentication, managed identities when available) and clarify any differences in setup between Windows and Linux.
- Reference cross-platform installers for required tools (e.g., Azure Functions Core Tools via npm or apt/yum, not just MSI).
- Include notes or sections on developing and running Logic Apps on Linux or macOS, including any limitations or required workarounds.
- List cross-platform SQL management tools alongside SSMS, such as Azure Data Studio or command-line utilities.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/set-up-standard-workflows-hybrid-deployment-requirements.md
...t-up-standard-workflows-hybrid-deployment-requirements.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: it references Windows Server and PowerShell-based workflows before or instead of Linux alternatives, uses Windows-specific tools (such as Chocolatey for installing kubectl and Helm), and provides detailed SMB file share setup instructions only for Windows, with no equivalent Linux example. While some Linux commands are present (e.g., apt-get in a test pod), the overall guidance and tooling favor Windows environments, and Linux-native approaches for key steps (such as SMB share setup) are missing.
Recommendations
- Provide parallel instructions for setting up SMB file shares on Linux systems, including step-by-step guides for common distributions (e.g., Ubuntu, CentOS).
- Include Linux-native installation commands for kubectl and Helm (e.g., using apt, yum, or direct downloads) alongside or before Windows/Chocolatey examples.
- Reference Linux-based Kubernetes clusters and workflows (e.g., AKS on Ubuntu, generic Linux clusters) equally or before Windows Server-based clusters.
- Offer PowerShell and Bash script examples side-by-side, or default to Bash/Azure CLI where possible, as these are cross-platform.
- Clarify when instructions or scripts are Windows-specific and provide equivalent Linux alternatives (e.g., for setting execution policy, environment variables, or running scripts).
- Expand the SMB file share testing and troubleshooting section to include Linux-native tools and commands (e.g., mount.cifs, smbclient).
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/support-non-unicode-character-encoding.md
...s/logic-apps/support-non-unicode-character-encoding.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric encodings (such as 'windows-1250', 'windows-1252') in examples, referencing .NET and Azure Functions exclusively (which are historically Windows-first technologies), and omitting any Linux/Unix command-line or open-source tool examples (such as iconv or recode). There are no Linux shell, Python, or cross-platform code samples, nor is there mention of Linux-native encoding workflows.
Recommendations
- Add Linux/Unix command-line examples for encoding conversion, such as using 'iconv' or 'recode' to convert files between encodings.
- Include Python or other cross-platform code samples for encoding conversion, demonstrating parity with the .NET/Azure Functions approach.
- Provide examples using Linux file systems and connectors (e.g., SFTP, NFS) and mention Linux-native encoding names (e.g., ISO-8859-1, UTF-16LE) alongside Windows code pages.
- Clarify that .NET and Azure Functions are cross-platform, and provide guidance for running these examples on Linux hosts.
- List encoding names as recognized on both Windows and Linux, and link to cross-platform encoding documentation (such as the Python codecs module or iconv encoding list).
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/tutorial-build-schedule-recurring-logic-app-workflow.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/tutorial-build-schedule-recurring-logic-app-workflow.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Microsoft/Windows-centric tools and services. It exclusively uses Office 365 Outlook and Outlook.com for email actions, with only a brief mention of Gmail (and with restrictions). There are no examples or guidance for Linux users or for integrating with non-Microsoft email services, and all screenshots and workflow steps are based on the Azure Portal UI, which is most familiar to Windows users. There is no mention of using CLI tools (such as Azure CLI or Bash scripts), nor are there examples for Linux-based workflows or open-source alternatives.
Recommendations
- Provide examples using non-Microsoft email providers (such as generic SMTP, SendGrid, or other open standards) and show how to integrate them into Logic Apps.
- Include guidance or examples for users who prefer to use the Azure CLI or Bash scripts to create and manage Logic Apps, in addition to the Azure Portal UI.
- Add explicit Linux-friendly instructions, such as how to authenticate or manage resources from Linux/macOS environments.
- Balance the documentation by mentioning and demonstrating non-Windows tools and connectors earlier and more prominently, not just as afterthoughts.
- Consider including screenshots or walkthroughs from cross-platform tools (e.g., Azure CLI, VS Code) to ensure parity for Linux/macOS users.
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools (such as Microsoft Azure Storage Explorer), referencing Windows as the default or example operating system, and providing PowerShell examples and links before or alongside Azure CLI, with no explicit Linux or cross-platform alternatives. There are no instructions or screenshots for Linux users, and the use of Windows-specific features (like in-portal editing only on Windows) is highlighted without offering Linux workarounds or parity.
Recommendations
- Provide explicit Linux and macOS instructions and screenshots alongside Windows steps, especially for tool installation and usage (e.g., Storage Explorer).
- When referencing command-line tools, present Azure CLI examples before or alongside PowerShell, and clarify cross-platform compatibility.
- Avoid using Windows as the default or only example for operating system selection; include Linux and macOS as equal options.
- Mention and link to Linux-compatible tools and workflows where available, and note any limitations or differences for non-Windows users.
- For features only available on Windows (e.g., in-portal editing), suggest alternative approaches for Linux users, such as local development with VS Code or other editors.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/tutorial-process-mailing-list-subscriptions-workflow.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/tutorial-process-mailing-list-subscriptions-workflow.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows/Microsoft-centric bias by exclusively using Microsoft services (Office 365 Outlook, Outlook.com) for email triggers and actions, referencing only the Azure portal (which is most commonly accessed via Edge/Windows), and not providing Linux-friendly alternatives or examples. There is no mention of Linux-native email providers, open-source tools, or cross-platform command-line instructions. The workflow assumes the user has access to Microsoft accounts and tools, and does not discuss parity with Linux-based environments or non-Microsoft email providers beyond a brief mention of Gmail (with restrictions).
Recommendations
- Provide explicit examples using non-Microsoft email providers (e.g., generic IMAP/SMTP, Gmail with Linux clients) and show how to configure them in Logic Apps.
- Include screenshots or instructions for accessing the Azure portal from Linux systems, or mention the Azure CLI as an alternative to the portal for resource creation and management.
- Add a section or callout for Linux users, highlighting any differences or additional steps required when using non-Windows environments.
- Reference open-source or cross-platform tools (e.g., Thunderbird, Evolution, mutt) for email testing, and provide sample workflows using these clients.
- Ensure that connector documentation links and workflow steps are not solely focused on Microsoft products, and provide equal visibility to alternatives.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page for Azure Logic Apps 'Examples & common scenarios' includes references to running PowerShell scripts from workflows and mentions PowerShell as a supported language for custom code. However, there is no mention of Linux shell scripting (e.g., Bash) or other Linux-native tools. Additionally, examples and tutorials do not provide parity for Linux/macOS users in terms of scripting or automation options, focusing primarily on Microsoft-centric technologies (PowerShell, .NET, C#).
Recommendations
- Add examples and documentation for running Bash scripts or other Linux shell scripts from Logic Apps workflows.
- Explicitly mention cross-platform scripting options and clarify any OS-specific limitations for script actions.
- Where PowerShell is referenced, also provide equivalent Linux/macOS alternatives if supported (e.g., Bash, Python).
- Ensure tutorials and walkthroughs include steps for Linux/macOS environments, especially for automation and deployment scenarios.