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 176-200 of 339 flagged pages
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
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas. When discussing certificate conversion for client certificate authentication, PowerShell is presented as the primary tool, with detailed steps and syntax. Only as a troubleshooting note is OpenSSL mentioned, and even then, the guidance is less detailed and focuses on resolving errors rather than providing a Linux/Unix-first workflow. There are no Linux shell or OpenSSL command-line examples for the main certificate conversion task, and no mention of Linux-native tools or workflows for other tasks (e.g., base64 encoding, file manipulation). The documentation assumes access to Windows tools and environments, omitting equivalent Linux guidance.
Recommendations
- Provide Linux/Unix shell and OpenSSL command-line examples alongside or before PowerShell examples for tasks such as converting and encoding certificates.
- When referencing file paths, use both Windows (C:\path) and Linux (/home/user/path) formats.
- Explicitly mention Linux-native tools (e.g., base64, openssl) for encoding and certificate manipulation, and provide step-by-step instructions.
- Where troubleshooting steps involve OpenSSL, offer full command-line workflows for Linux users, not just error resolution.
- Review other sections for implicit Windows assumptions (e.g., screenshots, terminology) and ensure parity for Linux users.
Create Pull Request
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, while not providing Linux-specific examples or mentioning Linux-native tools. Visual Studio and PowerShell are referenced as primary development tools, with no mention of Linux CLI, Bash, or cross-platform alternatives. Quickstart and getting started links focus on Azure portal and Visual Studio, which are more familiar to Windows users, and there are no explicit Linux or cross-platform command-line examples.
Recommendations
- Include Linux-native and cross-platform tools (e.g., Azure CLI, Bash scripting, VS Code on Linux) alongside Visual Studio and PowerShell.
- Provide explicit Linux-based examples or quickstarts, such as deploying or managing Logic Apps and Functions from a Linux terminal.
- Mention cross-platform development environments (e.g., Visual Studio Code, JetBrains Rider) before or alongside Windows-specific tools.
- Add references to documentation or tutorials that use Linux or macOS environments for parity.
- Ensure that all tooling recommendations are clearly marked as cross-platform or specify OS compatibility.
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 Visual Studio, Host Integration Server (HIS), and related design tools, with no mention of Linux-based alternatives or cross-platform tooling. All examples and tool recommendations are centered around the Windows ecosystem, and there is no guidance for developers working from Linux environments. This focus may limit accessibility and parity for Linux users.
Recommendations
- Include information about cross-platform alternatives or clarify if the tools (e.g., HIS Designer, 3270 Design Tool) can be used from Linux environments, or provide equivalent Linux-compatible tools if available.
- Offer examples or workflows that can be executed from Linux-based development environments, such as using VS Code (which is cross-platform) or command-line tools available on Linux.
- Explicitly state any platform requirements or limitations for the tools mentioned, so Linux users are aware of what is and isn't supported.
- If no Linux alternatives exist, provide guidance for Linux users on how to interact with Azure Logic Apps for mainframe integration (e.g., via REST APIs, CLI, or other cross-platform SDKs).
- Balance the documentation by including Linux-first or cross-platform perspectives where possible, ensuring parity in developer experience.
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 focused on Windows development environments, specifically Visual Studio (Windows-only), and references Windows tools and patterns throughout. There are no Linux or cross-platform alternatives provided for the main workflow, and PowerShell is mentioned as the only scripting tool. The instructions and screenshots are all for Windows, and there is no mention of how to perform equivalent tasks on Linux or macOS.
Recommendations
- Provide equivalent instructions and examples for Linux and macOS users, such as using Visual Studio Code or the Azure CLI for Logic Apps development and deployment.
- Mention and link to cross-platform tools (e.g., Azure CLI, VS Code) earlier and more prominently, not just as alternatives.
- Include Linux/macOS-specific setup steps, such as installing the Azure CLI, .NET SDK, and relevant extensions for VS Code.
- Replace or supplement PowerShell instructions with Bash/Azure CLI equivalents.
- Add screenshots and UI walkthroughs for cross-platform tools (e.g., VS Code) to ensure parity for non-Windows users.
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 bias toward Windows environments by highlighting PowerShell scripting as the only example of custom code integration, without mentioning or providing examples for Linux-native scripting languages (such as Bash or Python). Additionally, there is no mention of Linux-specific tools or development patterns, and the documentation assumes familiarity with Windows-centric tools (PowerShell, Visual Studio Code) without offering Linux alternatives or parity.
Recommendations
- Include examples for running Bash and Python scripts in Standard workflows, alongside PowerShell and C#.
- Explicitly mention that Visual Studio Code and the Azure Logic Apps extension are cross-platform, and provide Linux installation and usage guidance.
- Add references or links to Linux-native tools and scripting environments that can be used with Logic Apps.
- Ensure that scripting and automation examples are balanced between Windows and Linux environments, or at least acknowledge Linux support where applicable.
- Where PowerShell is mentioned, clarify that PowerShell Core is cross-platform, and provide Linux-specific instructions or notes.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/build-fact-creators-retrievers.md
...ic-apps/rules-engine/build-fact-creators-retrievers.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily focused on .NET and Microsoft-specific tooling, with all code examples in C# and references to DLL assemblies, which are primarily associated with Windows development. There are no examples or guidance for Linux or cross-platform development, nor any mention of how to use these features outside of a Windows/.NET environment. The documentation assumes the use of Microsoft Rules Composer and related tools, which are Windows-centric.
Recommendations
- Provide examples or guidance for using fact creators and retrievers in cross-platform .NET environments, such as .NET Core/.NET 6+ on Linux.
- Clarify whether the Rules Composer and related tools are available or supported on Linux, and if not, suggest alternative workflows for Linux users.
- Include instructions for building and deploying assemblies on Linux, such as using the dotnet CLI instead of Visual Studio.
- Mention any platform-specific requirements or limitations explicitly, so Linux and macOS users are aware of potential issues.
- If possible, provide sample code or scripts for Linux environments (e.g., bash scripts for building and deploying assemblies).
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/create-rules.md
.../main/articles/logic-apps/rules-engine/create-rules.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references the Microsoft Rules Composer, a GUI tool that is only available for Windows. There are no instructions, examples, or alternatives provided for Linux users. All steps, screenshots, and workflows assume the use of this Windows-only application, and there is no mention of command-line, cross-platform, or Linux-compatible approaches.
Recommendations
- Explicitly state the platform requirements for Microsoft Rules Composer, including its Windows-only availability.
- Provide guidance or alternatives for Linux users, such as programmatic rule creation using cross-platform tools, SDKs, or REST APIs if available.
- If no Linux GUI is available, document how to create, edit, and manage rulesets and vocabularies using XML or other supported formats on Linux.
- Include examples or references for managing rules via command-line or scripts that work on Linux (e.g., using .NET Core CLI, PowerShell Core, or Bash).
- Consider adding a section on how to integrate or deploy rulesets created on Windows to Linux-based Azure Logic Apps environments.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/create-rules-engine-project.md
...logic-apps/rules-engine/create-rules-engine-project.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a Windows bias by exclusively referencing Microsoft-specific tools (Microsoft Rules Composer, BizTalk Server) that are only available on Windows, and does not provide Linux alternatives or guidance for Linux users. All examples and instructions assume the use of these Windows-only tools, and there is no mention of Linux-compatible workflows, installation steps, or troubleshooting. The documentation implicitly assumes a Windows environment, especially in the prerequisites and rule export sections.
Recommendations
- Clearly state in the prerequisites whether the Microsoft Rules Composer and BizTalk Server steps require Windows, and if so, provide guidance for Linux users (e.g., using a Windows VM, Docker container, or remote desktop).
- If possible, suggest or develop cross-platform alternatives for rule authoring and export, or clarify the limitations for non-Windows users.
- Add explicit notes or sections for Linux/macOS users, including any workarounds or alternative approaches for steps that require Windows-only tools.
- Where possible, provide command-line alternatives or open-source tools that can be used on Linux for relevant tasks.
- Document any known issues or limitations when developing Logic Apps Rules Engine projects on Linux, and provide troubleshooting tips.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/rules-engine-optimization.md
...s/logic-apps/rules-engine/rules-engine-optimization.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing Microsoft-specific tools (such as Microsoft Rules Composer and .NET), omitting any Linux or cross-platform tooling or examples. All code and configuration references are .NET-centric, and there are no mentions of Linux command-line tools, deployment patterns, or alternative workflows. The documentation assumes the developer is using a Windows environment and Microsoft ecosystem tools, with no guidance for Linux users.
Recommendations
- Include examples or references for Linux-based development and deployment workflows, such as using Azure CLI or cross-platform editors.
- Mention whether the Rules Composer and related tools are available or supported on Linux, and if not, suggest alternatives or workarounds.
- Provide parity in examples by showing how to interact with the Rules Engine using REST APIs, Azure CLI, or SDKs available on Linux.
- Clarify any platform-specific limitations or requirements, especially for .NET and XML handling, and suggest cross-platform approaches where possible.
- Add a section or note addressing Linux/macOS users, outlining steps or considerations unique to those platforms.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references the Microsoft Rules Composer, a Windows-only GUI tool, and provides instructions and examples that assume a Windows environment (e.g., references to .NET assemblies, BizTalk, and Visual Studio project types). There are no examples or guidance for performing these tasks on Linux or cross-platform environments, nor are alternative tools or command-line approaches mentioned. The documentation implicitly assumes the user is on Windows and using Windows-specific tooling.
Recommendations
- Explicitly state platform requirements and limitations at the beginning of the documentation (e.g., 'Microsoft Rules Composer is only available on Windows').
- If possible, provide equivalent instructions or alternative tools for Linux users, such as command-line or cross-platform .NET Core/CLI approaches for managing rulesets.
- Include examples that use cross-platform .NET (e.g., .NET 6/7/8) and clarify which features are available on non-Windows platforms.
- Reference any available REST APIs, SDKs, or automation scripts that can be used on Linux/macOS to perform similar operations.
- If no Linux alternatives exist, suggest workarounds or clearly indicate that the described features are currently Windows-only.
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 subtle Windows bias by referencing Windows-centric encodings (e.g., 'windows-1250', 'windows-1252') in examples, linking to Microsoft/Windows-specific documentation for supported encodings, and omitting Linux/Unix-specific encoding examples or guidance. There are no examples or notes about Linux tools, encodings, or platform-specific considerations, and all code samples are in C#/.NET, which is more common in Windows environments.
Recommendations
- Include examples using common Linux encodings (e.g., 'ISO-8859-1', 'UTF-16', or 'UTF-8') alongside or before Windows-specific encodings.
- Add notes or examples for Linux/Unix users, such as how to check or convert file encodings using Linux tools (e.g., 'iconv', 'file', 'enca').
- Reference cross-platform or Linux documentation for character encodings, not just Microsoft/Windows sources.
- Provide at least one example using a Linux/Unix-based tool or scripting language (e.g., Python) for encoding conversion.
- Clarify that the .NET code samples can run cross-platform (if true), and mention any platform-specific caveats.
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 →
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, without acknowledging or providing examples for Linux or cross-platform development environments. The workflow and tooling described (VS Code, C#) are more commonly associated with Windows development, and there is no mention of Linux-specific considerations, alternative editors, or command-line workflows. The documentation also omits any terminal or shell instructions, which are often relevant for Linux users.
Recommendations
- Explicitly state that Visual Studio Code and the Azure Logic Apps extension are cross-platform and supported on Linux, macOS, and Windows.
- Include instructions or notes for Linux users, such as installing .NET SDK and VS Code on Linux, and any Linux-specific prerequisites.
- Provide example commands for running unit tests from the terminal using dotnet CLI, which is platform-agnostic, rather than assuming usage of the VS Code GUI.
- Mention any known issues or differences when using the workflow on Linux or macOS, if applicable.
- Consider including at least one example or screenshot from a Linux environment to demonstrate parity.
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 areas: Windows and PowerShell tools (such as Chocolatey and Set-ExecutionPolicy) are used for installing Kubernetes CLI tools (kubectl, Helm), and the only explicit file share setup instructions are for Windows. PowerShell scripts and commands are referenced and provided, while Linux equivalents (such as apt, yum, or shell scripts) are missing or not given equal prominence. The documentation references Windows Server and PowerShell walkthroughs before or instead of Linux alternatives, and the use of Windows-centric tools like Chocolatey is not balanced with Linux-native package manager instructions.
Recommendations
- Provide Linux-native installation instructions for kubectl and Helm (e.g., using apt, yum, or curl/bash scripts) alongside or before Windows/Chocolatey examples.
- Include explicit Linux file share setup instructions (e.g., using Samba or NFS) in addition to the Windows SMB setup steps.
- Offer Linux shell script equivalents for PowerShell commands and scripts, especially for environment setup and automation.
- Reference Linux-based Kubernetes cluster setup guides (e.g., Ubuntu, CentOS) with equal prominence as Windows Server guides.
- Avoid assuming Chocolatey or PowerShell as the default tooling; present cross-platform alternatives or clarify OS-specific instructions.
- Ensure that all code snippets and setup steps are clearly marked for their target OS, and provide parity in detail and support for both Windows and Linux environments.
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 First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows/Microsoft ecosystem bias by exclusively using Microsoft services and tools (e.g., Office 365 Outlook, Outlook.com, Bing Maps) in all examples and instructions. There are no Linux-specific or cross-platform alternatives mentioned for email providers, mapping APIs, or workflow management. The documentation assumes the user is operating within the Microsoft ecosystem, and does not provide parity for Linux users or those using open-source or non-Microsoft tools.
Recommendations
- Include examples using non-Microsoft email providers (e.g., generic SMTP, IMAP, or open-source email services) and provide step-by-step instructions for their integration.
- Mention and provide examples for alternative mapping APIs (such as Google Maps, OpenStreetMap, or MapQuest) where possible, and link to relevant connectors or custom connector documentation.
- Explicitly state that Azure Logic Apps is a cross-platform service and can be used from any OS, and provide guidance for Linux/macOS users where relevant (e.g., using Azure CLI or REST APIs from Bash).
- Add troubleshooting and setup notes for users who may not have access to Microsoft accounts or tools, including how to authenticate with non-Microsoft services.
- Balance the order of examples and tool mentions so that Microsoft/Windows tools are not always presented first or exclusively.
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 displays a Windows bias by consistently referencing Windows tools (such as Microsoft Azure Storage Explorer), presenting Windows as the default or only option in several steps (e.g., in-portal editing for Azure Functions), and listing Azure PowerShell before Azure CLI. There are no Linux-specific instructions or parity notes for Linux users, and examples for command-line operations do not include Bash or Linux shell alternatives. The documentation assumes use of Windows-centric tools and workflows, with minimal acknowledgment of cross-platform needs.
Recommendations
- Provide explicit Linux/macOS instructions and screenshots where applicable, especially for command-line steps and tool installation.
- When referencing command-line tools, present Azure CLI examples before or alongside Azure PowerShell, as Azure CLI is cross-platform.
- Mention and link to alternative tools for managing Azure Storage on Linux/macOS (e.g., AzCopy, Azure CLI, or third-party tools) in addition to Storage Explorer.
- Clarify when features (like in-portal editing) are Windows-only, and provide guidance for Linux users (e.g., how to develop and deploy Azure Functions from Linux).
- Include notes or callouts for Linux/macOS users throughout the tutorial, especially in setup and troubleshooting sections.
- Balance screenshots and UI walkthroughs by including those from non-Windows environments where possible.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-single-tenant-workflows-azure-portal.md
...ic-apps/create-single-tenant-workflows-azure-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas. The instructions for creating a Standard logic app resource explicitly require a Windows-based App Service plan and state that Linux-based plans are not supported. The storage account error message references a Windows file path (C:\home\data\Functions\secrets\Sentinels). The troubleshooting section instructs users to use the Kudu Advanced Tools and CMD shell, which are Windows-centric tools and terminology, without mentioning Linux alternatives or clarifying cross-platform compatibility. There are no examples or guidance for Linux users, and no mention of Linux command-line equivalents or considerations.
Recommendations
- Clearly state early in the prerequisites and plan selection sections that Standard logic apps currently only support Windows-based App Service plans, and explain any roadmap or alternatives for Linux users.
- Where Windows-specific tools or paths are referenced (e.g., Kudu, CMD, Windows file paths), clarify whether these are accessible from Linux/macOS environments via the Azure portal, and provide equivalent instructions or notes for non-Windows users.
- If certain features or troubleshooting steps are only available on Windows, explicitly call this out and suggest alternative approaches for Linux users where possible.
- Add a section or callout summarizing platform support and limitations, so Linux users can quickly determine applicability.
- Where possible, provide cross-platform command-line examples (e.g., using Bash or Azure CLI) alongside or in place of Windows CMD instructions.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/azure-integration-services-choose-capabilities.md
...apps/azure-integration-services-choose-capabilities.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing BizTalk Server and SQL Server Integration Services (SSIS) as primary integration platforms for migration, both of which are traditionally Windows-centric technologies. There are no Linux or cross-platform integration tools mentioned as migration sources or alternatives, and no examples or guidance for users coming from Linux-based integration stacks. The focus on Windows tools and migration paths may leave Linux users underserved.
Recommendations
- Include references to common Linux-based integration platforms (such as Apache Camel, Talend, or MuleSoft) and provide migration guidance or comparison for users coming from those environments.
- Mention and provide examples for integration scenarios that originate from Linux or open-source tools, not just Windows-based ones.
- Balance the migration narrative by including Linux-native workloads or open-source ETL tools as potential sources for Azure Integration Services.
- Clarify that Azure Integration Services are cross-platform and highlight support for Linux-based environments where applicable.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/biztalk-server-migration-overview.md
...ticles/logic-apps/biztalk-server-migration-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the exclusive mention of Windows-specific tools (e.g., BizTalk Administration Console, MMC snap-ins, Windows registry, PowerShell, Windows Authentication, and references to Windows Server/SQL Server/Visual Studio). In several sections, Windows-centric patterns and tools are described in detail, often without Linux or cross-platform alternatives being mentioned or prioritized. While Azure Logic Apps and related services are cross-platform, the migration narrative and tooling references frequently assume a Windows background and ecosystem.
Recommendations
- Wherever possible, provide Linux or cross-platform equivalents for administrative tools and configuration patterns (e.g., mention Azure CLI, Bash, or cross-platform SDKs alongside PowerShell and MMC).
- When discussing deployment and automation, include examples or references for both PowerShell and Bash/CLI scripts.
- Avoid assuming Windows registry or Windows-specific configuration files as the only configuration store; highlight cross-platform options (e.g., environment variables, Azure App Configuration) equally.
- In developer tooling sections, mention cross-platform IDEs and editors (e.g., Visual Studio Code) before or alongside Visual Studio, and clarify their support on Linux/macOS.
- For authentication and security, discuss alternatives to Windows Authentication (e.g., OAuth2, managed identities) and clarify their applicability in non-Windows environments.
- In sections referencing hosting or infrastructure, explicitly note Linux support for Azure App Service, containers, and hybrid deployments.
- Review all examples and tool mentions to ensure Linux users are not excluded or left to infer their own paths.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation demonstrates a mild Windows bias, primarily in the tools and command-line examples provided. Windows-centric tools such as Visual Studio and Azure PowerShell are mentioned explicitly and often before cross-platform or Linux-native alternatives. The only explicit command-line example for retrieving the tenant ID uses PowerShell, with no mention of Bash or Azure CLI equivalents. Visual Studio (Windows-only) is listed before Visual Studio Code (cross-platform) as a function creation tool. There are no Linux-specific instructions or examples, and the documentation assumes familiarity with Windows-based workflows and tools.
Recommendations
- When listing tools for creating Azure Functions, mention cross-platform options (e.g., Visual Studio Code, Azure CLI) before or alongside Windows-only tools like Visual Studio.
- Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for common tasks like retrieving tenant IDs.
- Explicitly state when steps or tools are cross-platform, and provide guidance for Linux/macOS users where applicable.
- Include screenshots or instructions from non-Windows environments (e.g., terminal, VS Code on Linux/macOS) to demonstrate parity.
- Audit all command-line and tool references to ensure Linux users are equally supported and not required to use Windows-specific tooling.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell automation for gateway management, mentioning the 'gateway Windows service account', and lacking any Linux-specific instructions or examples for installing or managing the on-premises data gateway. There is no mention of Linux support, tools, or equivalent automation methods, and all troubleshooting and operational guidance assumes a Windows environment.
Recommendations
- Explicitly state whether the on-premises data gateway supports installation and operation on Linux systems. If not supported, clarify this limitation early in the documentation.
- If Linux is supported, provide installation and management instructions for Linux, including command-line examples (e.g., using bash, systemd for service management).
- Include Linux-specific troubleshooting steps, such as how to restart the gateway service on Linux.
- Offer automation examples for Linux environments (e.g., using shell scripts or Azure CLI) alongside PowerShell examples.
- Avoid referring exclusively to 'gateway Windows service account'; instead, use OS-neutral language or provide both Windows and Linux variants.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-custom-built-in-connector-standard.md
...ogic-apps/create-custom-built-in-connector-standard.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing PowerShell-based installation and usage instructions as the primary method, referencing Windows-style file paths and tools (e.g., func.exe), and showing output examples with Windows directory structures. While a Bash alternative is mentioned, it still relies on PowerShell scripts, which are not native to Linux/macOS environments. There are no native Linux/macOS installation instructions or examples, and the overall workflow assumes a Windows-centric development environment.
Recommendations
- Provide native Bash or shell script alternatives for installing and managing extensions, not just using PowerShell via Bash.
- Include Linux/macOS-specific instructions and examples, such as using dotnet CLI directly or alternative scripting methods.
- Show output examples from Linux/macOS terminals (e.g., with /home/user paths) alongside Windows examples.
- Clarify cross-platform compatibility for all tools and scripts mentioned, and link to any prerequisites for Linux/macOS environments.
- Avoid assuming the presence of PowerShell on non-Windows systems, or provide guidance on installing and using it if required.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-run-custom-code-functions.md
...rticles/logic-apps/create-run-custom-code-functions.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by explicitly stating that the custom functions capability is only available on Visual Studio Code running on Windows. There are no instructions, troubleshooting, or examples for Linux or macOS users. All references to file paths, tools, and environment setup implicitly assume a Windows environment, and there is no mention of Linux equivalents or cross-platform considerations.
Recommendations
- Clearly indicate platform support and, if possible, provide a roadmap or alternatives for Linux/macOS users.
- If the feature is Windows-only, suggest workarounds or alternative approaches for non-Windows users.
- Include explicit statements about the lack of Linux/macOS support in the prerequisites and throughout the documentation.
- Provide equivalent instructions, examples, and troubleshooting steps for Linux/macOS if/when support becomes available.
- Avoid using only Windows-style file paths and environment variables; include cross-platform examples where applicable.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-standard-workflows-hybrid-deployment.md
...ic-apps/create-standard-workflows-hybrid-deployment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: troubleshooting and cluster validation steps are provided only with PowerShell and Windows command prompt examples, with no equivalent Linux/bash commands. The use of 'Run Visual Studio Code as administrator' and references to Windows-specific ports and tools (e.g., SMB file share, PowerShell scripts) further reinforce a Windows-centric approach. Linux or cross-platform alternatives are not mentioned or are missing in key operational and troubleshooting sections.
Recommendations
- Provide Linux/bash equivalents for all PowerShell and Windows command prompt commands, especially for kubectl, helm, and az CLI usage.
- Include instructions for running Visual Studio Code and required commands on Linux/macOS, not just Windows (e.g., clarify 'run as administrator' for non-Windows platforms).
- Mention and provide guidance for using NFS or other Linux-friendly file share options alongside SMB, or clarify SMB support on Linux.
- Ensure troubleshooting scripts and instructions (such as troubleshoot.ps1) have cross-platform alternatives (e.g., bash scripts) or note their compatibility.
- When referencing tools (e.g., PowerShell, Windows command prompt), always provide parity with bash/zsh or other common Linux shells.
- Review all screenshots and UI instructions to ensure they are not exclusively Windows-centric, or provide Linux/macOS equivalents where applicable.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/deploy-single-tenant-logic-apps-private-storage-account.md
...eploy-single-tenant-logic-apps-private-storage-account.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in its troubleshooting section by providing only Windows command prompt examples (e.g., 'C:\>nslookup', 'C:\psping'), referencing Windows-style paths (e.g., 'C:\home\site\wwwroot'), and omitting equivalent Linux/Bash commands and file paths. There are no Linux or cross-platform command-line examples, and the tools mentioned (psping, tcpping) are Windows-centric. The main deployment instructions focus on Azure Portal and Visual Studio Code, which are cross-platform, but the troubleshooting guidance assumes a Windows environment.
Recommendations
- Provide equivalent Linux/Bash command examples for troubleshooting steps (e.g., 'nslookup', 'dig', 'ping', 'nc' or 'curl' for port checks).
- Include Linux-style file paths (e.g., '/home/site/wwwroot') alongside Windows paths in error messages and troubleshooting.
- Mention cross-platform or Linux-native tools (e.g., 'nc' or 'nmap' instead of 'psping') for network connectivity testing.
- Explicitly state that the troubleshooting steps apply to both Windows and Linux VMs, and provide command examples for both.
- Where possible, use environment-agnostic language and tools to ensure parity for Linux users.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-standard-workflows-visual-studio-code.md
...c-apps/create-standard-workflows-visual-studio-code.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation exhibits a Windows bias in several ways: Windows-specific tools and paths are mentioned first or exclusively in key sections (e.g., Windows Defender Firewall, regedit, .exe files, C:\ paths), and some setup and troubleshooting steps are only described for Windows (e.g., registry edits, firewall prompts). Linux/macOS equivalents are missing or only briefly mentioned later, and some examples (such as editing registry keys or handling firewall prompts) are not cross-platform. There is also a tendency to use Windows terminology and screenshots throughout, with limited parity for Linux/macOS users.
Recommendations
- Provide Linux and macOS equivalents alongside Windows instructions for all setup, configuration, and troubleshooting steps (e.g., firewall configuration, file paths, environment variables, and permissions).
- Include Linux/macOS-specific examples and screenshots where relevant, especially for common tasks like editing configuration files, running commands, or handling permissions.
- Avoid using Windows-specific terminology or tools (such as regedit, Windows Defender Firewall, .exe files) without offering alternatives for other platforms.
- When referencing file paths, use cross-platform notation or provide both Windows and Linux/macOS examples (e.g., C:\Users\ vs. ~/).
- For tools like ngrok, show command-line usage for Linux/macOS, not just Windows (e.g., avoid only referencing ngrok.exe).
- Explicitly state when a feature or step is Windows-only, and provide guidance or workarounds for Linux/macOS users where possible.
- Review all code snippets and configuration examples to ensure they are valid on all supported platforms, or provide platform-specific variants.