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 301-325 of 339 flagged pages
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/azure-arc-enabled-logic-apps-create-deploy-workflows.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/azure-arc-enabled-logic-apps-create-deploy-workflows.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is largely cross-platform in intent, focusing on Azure CLI and Visual Studio Code, both of which are available on Windows, Linux, and macOS. However, there are subtle signs of Windows bias: (1) The documentation refers to 'command window' and 'terminal' interchangeably, but does not provide explicit Linux/macOS shell examples or mention Bash, Zsh, or other common Linux shells. (2) There are no explicit Linux/macOS-specific instructions, troubleshooting tips, or environment setup notes, and no screenshots or examples that show Linux terminals. (3) The installation instructions for Azure CLI are linked generically, but no Linux-specific package manager commands (e.g., apt, yum, brew) are shown. (4) The documentation does not mention or demonstrate using Linux-native tools or patterns (such as Bash scripting, environment variables, or file paths in Linux format), nor does it address potential differences in file permissions, case sensitivity, or CLI usage on Linux.
Recommendations
- Explicitly mention both Windows and Linux/macOS environments when referring to 'terminal' or 'command window', and provide examples for both (e.g., 'Open a terminal (Command Prompt on Windows, Terminal on Linux/macOS)').
- Include Linux/macOS-specific installation commands for Azure CLI (e.g., apt-get, yum, brew) alongside the generic installation guide link.
- Add example commands and screenshots from Linux/macOS terminals to demonstrate parity.
- When referencing file paths, show both Windows (C:\path\to\file) and Linux (/home/user/path/to/file) formats where relevant.
- Mention any known platform-specific issues, such as file permissions or case sensitivity, that may affect Linux users.
- If scripting or automation is discussed, provide Bash script examples in addition to any PowerShell or batch examples.
- Ensure that all tool references (such as Visual Studio Code) clarify that they are cross-platform and provide links or instructions for Linux/macOS installation if needed.
Create Pull Request
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/expression-functions-reference.md
.../articles/logic-apps/expression-functions-reference.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally cross-platform and does not provide OS-specific command-line examples, but it does exhibit Windows bias in its references to time zone names and date/time formatting. Specifically, it refers exclusively to 'Microsoft Windows Default Time Zones' for time zone names and uses .NET and Windows-centric date/time format strings. There is no mention of IANA/Olson time zone names or Unix/Linux equivalents, and the documentation does not clarify how Linux users should map or use time zones in Logic Apps. Additionally, all links and references for time zone handling point to Windows documentation, and the default examples and explanations assume a Windows/.NET environment.
Recommendations
- Add information about IANA/Olson time zone names and clarify whether they are supported or how to map them to Windows time zone names.
- Explicitly state that time zone names must use the Windows format and provide a mapping table or reference for Linux/Mac users.
- Where .NET or Windows-specific format strings are referenced, clarify that these are required regardless of the user's OS, and provide guidance for users coming from Linux or other environments.
- Consider including a note or section on cross-platform considerations for users who may be more familiar with Linux/Unix conventions (e.g., time zone naming, date/time formatting).
- Where possible, provide links to cross-platform resources or explain the rationale for Windows-centric requirements in Azure Logic Apps.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-enterprise-integration-edifact.md
...ogic-apps/logic-apps-enterprise-integration-edifact.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a Windows bias by referencing 'App Service Environment v3 (Windows plans only)' as the environment for Standard logic apps, without mentioning Linux support or alternatives. There are no explicit Linux examples, and the documentation assumes the use of the Azure Portal (a web interface, but some features may differ between OSes). The phrase 'Windows plans only' is used without clarifying Linux parity or providing guidance for Linux users.
Recommendations
- Clarify if and how EDIFACT connectors and workflows can be used on Linux-based App Service plans or Azure Logic Apps (Standard) running on Linux.
- If Linux is not supported, explicitly state this limitation and provide a roadmap or alternatives for Linux users.
- If Linux is supported, provide equivalent instructions and examples for Linux environments, including any differences in setup or configuration.
- Avoid using 'Windows plans only' without context—explain the implications for cross-platform users.
- Where relevant, mention CLI or automation alternatives (such as Azure CLI, which is cross-platform) alongside portal instructions.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/move-logic-app-resources.md
...b/main/articles/logic-apps/move-logic-app-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions Azure PowerShell before Azure CLI when listing automation options, and provides no command-line examples for either tool. There are no examples or guidance specific to Linux environments, and the only development tool mentioned for exporting and managing templates is Visual Studio, which is primarily a Windows application. This creates a subtle Windows-first and missing-Linux-example bias.
Recommendations
- When listing automation tools, alternate the order (e.g., mention Azure CLI before PowerShell in some places) or explicitly state that both are cross-platform.
- Provide concrete example commands for both Azure PowerShell and Azure CLI, making clear that Azure CLI is fully supported on Linux and macOS.
- Include references to cross-platform editors (e.g., VS Code) for template editing and deployment, not just Visual Studio.
- Add a section or note highlighting that all steps can be performed from Linux, macOS, or Windows, and link to relevant cross-platform tool documentation.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/monitor-health-standard-workflows.md
...ticles/logic-apps/monitor-health-standard-workflows.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing the Azure portal (a web UI), and more notably, by instructing users to use KuduPlus and the Debug console with 'CMD' for editing files—tools and terminology that are Windows-centric. There are no examples or instructions for performing equivalent actions using Linux-friendly tools, such as SSH, SCP, or Bash. No command-line or automation examples are provided for Linux users, and the documentation does not mention how to perform these steps outside of the Azure portal or KuduPlus CMD interface.
Recommendations
- Provide alternative instructions for Linux users, such as editing host.json via SSH or using the Azure CLI.
- Include examples of using Bash or other cross-platform shells to update configuration files.
- Mention that KuduPlus offers both CMD (Windows) and Bash (Linux) consoles, and show how to use the Bash console for file editing.
- Add Azure CLI or PowerShell (cross-platform) commands for enabling Health Check and updating settings, ensuring parity for users on all operating systems.
- Clarify that the Azure portal and KuduPlus are web-based and accessible from any OS, but that the CMD reference is a Windows-centric naming convention.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/add-rules-operators.md
...rticles/logic-apps/rules-engine/add-rules-operators.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references the Microsoft Rules Composer, a Windows-only GUI tool, and all instructions are based on its use. There are no examples or guidance for Linux users, nor are any cross-platform or command-line alternatives mentioned.
Recommendations
- Clarify platform support for Microsoft Rules Composer at the start of the documentation, explicitly stating if it is Windows-only.
- If available, provide instructions or alternatives for Linux users, such as command-line tools, REST APIs, or cross-platform editors.
- Include examples or workflows that can be performed without relying on Windows-specific GUI tools.
- Reference any available open-source or third-party tools that support similar functionality on Linux.
- If no Linux support exists, suggest workarounds (e.g., running the tool in a Windows VM or via Wine) and note any limitations.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/create-manage-vocabularies.md
.../logic-apps/rules-engine/create-manage-vocabularies.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references the Microsoft Rules Composer, a GUI tool that is only available for Windows. There are no instructions, examples, or even mentions of Linux or cross-platform alternatives. All workflows, screenshots, and prerequisites assume a Windows environment, with no guidance for Linux users.
Recommendations
- Explicitly state platform requirements early in the documentation, clarifying that the Microsoft Rules Composer is Windows-only.
- If possible, provide or reference any available Linux-compatible tools or command-line alternatives for managing vocabularies and rulesets.
- Offer guidance for Linux users, such as using a Windows VM, Wine, or remote desktop solutions, if no native Linux support exists.
- Advocate for or document REST APIs, CLI tools, or cross-platform SDKs that could allow Linux users to perform equivalent tasks.
- Include a section addressing Linux/macOS users, outlining current limitations and any planned support.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/test-rulesets.md
...main/articles/logic-apps/rules-engine/test-rulesets.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references the Microsoft Rules Composer, a Windows-only tool, and provides instructions and UI steps that assume a Windows environment. There are no mentions of Linux or cross-platform alternatives, nor any command-line or scripting examples that would work on Linux. All examples and workflows are centered around the Windows GUI tool, with no guidance for Linux users.
Recommendations
- Explicitly state the platform requirements and limitations of Microsoft Rules Composer at the start of the documentation.
- If available, provide information about any cross-platform or Linux-compatible alternatives for ruleset testing.
- Offer command-line or scripting-based workflows (e.g., using .NET Core CLI tools, Docker containers, or REST APIs) that can be executed on Linux.
- Include a section addressing Linux/macOS users, even if only to clarify the lack of support and suggest workarounds or future plans.
- Where possible, decouple the conceptual explanation of ruleset testing from the specific Windows tool, so that the guidance is more broadly applicable.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/add-rules-control-functions.md
...logic-apps/rules-engine/add-rules-control-functions.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on the Microsoft Rules Composer, a Windows-only GUI tool, and does not mention or provide examples for Linux or cross-platform alternatives. All instructions and workflows assume the use of this Windows application, with no command-line or platform-agnostic guidance, nor any mention of how to perform these tasks on Linux or macOS.
Recommendations
- Explicitly state the platform requirements and limitations of Microsoft Rules Composer at the start of the documentation.
- If available, provide equivalent instructions for Linux or macOS users, such as command-line tools, APIs, or alternative workflows.
- If no Linux-compatible tools exist, suggest workarounds (e.g., running the tool in a Windows VM or via Wine) or provide guidance on using the underlying APIs or SDKs directly from cross-platform environments.
- Include sample code or automation scripts (e.g., .NET CLI, REST API, or SDK usage) that can be executed on Linux, not just GUI-based instructions.
- Add a section addressing cross-platform considerations and explicitly mention any gaps or future plans for Linux support.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/set-up-devops-deployment-single-tenant-azure-logic-apps.md
...et-up-devops-deployment-single-tenant-azure-logic-apps.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias in several areas, particularly in the sections on checking pip installation and environment setup, where only Windows and Mac are mentioned explicitly, and Linux is omitted. There are no Linux-specific examples or instructions for common tasks such as checking pip installation or installing the Azure CLI, which may hinder Linux users. The documentation assumes familiarity with Windows-centric workflows and does not provide parity for Linux users.
Recommendations
- Add explicit Linux instructions and examples alongside Windows and Mac for tasks such as checking pip installation, installing/updating the Azure CLI, and managing environment variables.
- When providing command-line instructions, include Linux shell equivalents (e.g., bash commands) and note any OS-specific differences.
- Ensure that all prerequisite and setup steps are cross-platform, or clearly indicate platform-specific steps in separate sections or tabs.
- Review the documentation for any other implicit Windows assumptions (such as file paths, tool usage, or screenshots) and provide Linux alternatives where appropriate.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/set-up-zone-redundancy-availability-zones.md
...ogic-apps/set-up-zone-redundancy-availability-zones.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation references 'Windows plan' multiple times, specifically in the context of enabling zone redundancy, and does not mention Linux-based hosting options or provide parity for Linux users. The instructions and notes focus on Windows plans, implying Windows as the default or only supported environment, with no mention of Linux equivalents or guidance.
Recommendations
- Explicitly mention Linux-based hosting options (e.g., App Service plans running on Linux) and clarify whether zone redundancy is supported for them.
- Provide instructions or notes for both Windows and Linux plans, or clearly state if Linux plans are not supported.
- Avoid language that assumes Windows as the default (e.g., 'Windows plan') unless it is truly the only supported option, and if so, explain why.
- If there are differences in feature support between Windows and Linux, summarize them in a comparison table for transparency.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/testing-framework/create-unit-tests-standard-workflow-runs-visual-studio-code.md
...e-unit-tests-standard-workflow-runs-visual-studio-code.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by only referencing Visual Studio Code usage patterns and workflows that are typical for Windows environments (e.g., referencing the 'Run' menu, F5 for debugging, and C#-centric examples), without providing any Linux-specific instructions or examples. There are no mentions of Linux command-line equivalents, terminal instructions, or alternative editors/tools. The documentation assumes a Windows-like experience and omits guidance for Linux users.
Recommendations
- Add explicit instructions for Linux users, such as how to start debugging in Visual Studio Code using the command palette or terminal commands (e.g., 'code --start-debugging').
- Mention keyboard shortcuts and menu navigation differences between Windows and Linux (e.g., F5 may be the same, but menu layouts can differ).
- Include notes on installing and using the Azure Logic Apps (Standard) extension in Visual Studio Code on Linux.
- Clarify that all instructions apply equally to Linux and macOS, or provide platform-specific notes where behavior diverges.
- If any steps require Windows-only features (such as certain C#/.NET dependencies), explicitly state this and provide Linux-compatible alternatives or workarounds where possible.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows and Microsoft-centric environments by exclusively using Office 365 Outlook/Outlook.com for email triggers and actions, and by referencing Microsoft accounts and services throughout. There are no Linux-specific examples, nor are alternative email providers (such as IMAP/SMTP or Linux-friendly mail services) given equal prominence. The documentation assumes the user is operating within the Microsoft ecosystem, which may not reflect the needs of Linux or open-source users.
Recommendations
- Provide parallel examples using non-Microsoft email providers (e.g., generic IMAP/SMTP connectors) to illustrate how Linux users or those outside the Microsoft ecosystem can implement similar workflows.
- Explicitly mention and demonstrate how to use Logic Apps connectors with open-source or Linux-friendly email services (such as Gmail, with clear guidance for both G-Suite and consumer accounts, or other IMAP-compatible providers).
- Include a section or callout that addresses cross-platform considerations, highlighting any differences in experience or setup for users on Linux or macOS.
- Avoid assuming Office 365 Outlook as the default; instead, present it as one option among several, and ensure that alternative providers are given equal visibility and step-by-step instructions.
- Where screenshots or UI steps are shown, consider providing equivalent examples for users who may not have access to Microsoft accounts or services.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-maps-data-transformation-visual-studio-code.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-maps-data-transformation-visual-studio-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation explicitly states that the Data Mapper tool only works in Visual Studio Code running on Windows operating systems. There are no instructions, examples, or troubleshooting steps for Linux or macOS users. All setup and usage guidance assumes a Windows environment, and there is no mention of parity or alternatives for non-Windows platforms.
Recommendations
- Clearly indicate at the top of the page that Data Mapper is currently Windows-only, and provide a roadmap or estimated timeline for Linux/macOS support if available.
- Add a dedicated section addressing Linux/macOS users, explaining the current limitations and any possible workarounds (such as using a Windows VM, remote development, or alternative tools).
- If possible, provide links to feature requests or feedback channels where users can express interest in cross-platform support.
- Once Linux/macOS support is available, update the documentation with platform-specific installation and usage instructions, and ensure all examples are validated on all supported platforms.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-automation-tasks-azure-resources.md
.../logic-apps/create-automation-tasks-azure-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing Fiddler (a Windows-centric tool) for web debugging in the template testing section, and by not mentioning or providing examples for Linux-compatible alternatives. There are no PowerShell or Windows command-line examples, but the only explicit tooling guidance is Windows-focused. No Linux tools or cross-platform alternatives are suggested, and no Linux-specific instructions or screenshots are provided.
Recommendations
- Mention and provide examples for Linux-compatible web debugging tools, such as mitmproxy or Charles Proxy, alongside Fiddler.
- Include instructions or example scripts for using these alternative tools to test templates, ensuring parity for Linux and macOS users.
- Add a note clarifying that Fiddler is just one option, and that any web debugging tool capable of request interception and modification can be used.
- Wherever screenshots or step-by-step instructions are given for a tool, consider providing equivalent guidance for a popular Linux alternative.
- Review other sections for implicit assumptions about the user's OS (e.g., file paths, browser recommendations) and clarify cross-platform compatibility where relevant.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/set-up-devops-deployment-single-tenant-azure-logic-apps.md
...et-up-devops-deployment-single-tenant-azure-logic-apps.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by presenting environment-specific instructions (such as checking pip installation) that mention Windows and Mac, but do not reference Linux explicitly. Additionally, there are no Linux-specific examples or terminal commands, and the order of instructions and terminology often assumes a Windows or Mac environment. While the Azure CLI is cross-platform, the lack of explicit Linux guidance or examples may make Linux users feel less directly supported.
Recommendations
- Include explicit Linux instructions and examples alongside Windows and Mac, especially in sections about checking pip installation and running CLI commands.
- Add Linux-specific terminal commands and troubleshooting steps where relevant (e.g., using apt, yum, or other package managers for pip installation).
- When referencing command prompts or terminals, clarify that the instructions apply to all platforms, or provide separate tabs/sections for Windows, Mac, and Linux.
- Review all environment setup steps to ensure Linux users are not required to infer steps from Windows/Mac instructions.
- Consider adding a table or section summarizing platform-specific setup steps for Windows, Mac, and Linux.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-create-api-app.md
.../main/articles/logic-apps/logic-apps-create-api-app.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page does not provide explicit Windows-only examples or mention Windows-specific tools directly. However, there is a subtle bias in the examples and tooling recommendations: all code samples and GitHub references use C#/.NET (e.g., ASP.NET, Swashbuckle, TRex), which are traditionally more common in Windows environments. There are no Linux-specific examples, nor are there references to Linux-native frameworks, deployment patterns, or tools. The focus on Azure App Service and .NET-centric tools may implicitly favor Windows developers, even though cross-platform support exists.
Recommendations
- Include example implementations using popular Linux-first stacks (e.g., Flask for Python, Express for Node.js, Spring Boot for Java) alongside .NET examples.
- Reference Linux-native tools for OpenAPI/Swagger generation (e.g., Swagger CLI, openapi-generator) in addition to Swashbuckle and TRex.
- Add deployment guidance for Linux-based hosting environments (e.g., Azure App Service for Linux, Docker containers, or Azure Functions on Linux).
- Ensure that code samples and GitHub references include at least one non-.NET, non-Windows-centric example.
- Explicitly state that all patterns and recommendations apply equally to Linux-hosted APIs and provide links to relevant Linux documentation where appropriate.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/logic-apps-enterprise-integration-edifact.md
...ogic-apps/logic-apps-enterprise-integration-edifact.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing 'App Service Environment v3 (Windows plans only)' as the only supported environment for Standard logic apps, and by exclusively using the Azure portal (a web-based GUI) for all examples and instructions. There are no references to Linux-specific environments, tools, or command-line alternatives (such as Azure CLI, PowerShell, or Bash scripts), nor are there any examples or guidance for Linux users. The documentation assumes users are working in environments compatible with Windows plans and the Azure portal, potentially excluding Linux-native workflows or automation.
Recommendations
- Clarify support for Linux-based App Service plans for Standard logic apps, or explicitly state if only Windows plans are supported.
- Provide equivalent instructions and examples for Linux users, such as using Azure CLI or ARM templates, in addition to Azure portal steps.
- Include notes or sections on how to perform relevant tasks (such as uploading schemas, configuring agreements, or managing resources) using cross-platform tools.
- If certain features are Windows-only, clearly indicate this and suggest alternative approaches for Linux users where possible.
- Add references to automation and scripting options (e.g., Bash, Azure CLI) for users who prefer or require non-GUI workflows.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/monitor-health-standard-workflows.md
...ticles/logic-apps/monitor-health-standard-workflows.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing the Azure portal and KuduPlus (with CMD shell) for file editing and configuration, which are Windows-centric tools. There are no examples or instructions for performing equivalent tasks using Linux tools, CLI, or cross-platform approaches. The use of 'CMD' in KuduPlus and the absence of Linux shell or Azure CLI/PowerShell alternatives further reinforce this bias.
Recommendations
- Provide alternative instructions for editing files and configuring settings using cross-platform tools such as Azure CLI, Azure Cloud Shell (Bash), or direct SSH access.
- Include examples for managing the host.json file using Linux shell commands (e.g., nano, vi, or echo/cat for editing JSON files).
- Mention that KuduPlus offers both CMD and Bash shells, and show how to use the Bash shell for Linux users.
- Where possible, add Azure CLI commands for enabling Health Check and updating configuration, so users on any OS can follow along.
- Ensure screenshots and step-by-step instructions are not limited to Windows interfaces or terminology.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/move-logic-app-resources.md
...b/main/articles/logic-apps/move-logic-app-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently lists the Azure portal, Azure PowerShell, Azure CLI, and REST API as migration options, but always mentions Azure PowerShell (a Windows-centric tool) before Azure CLI (cross-platform). No explicit examples or command snippets are provided for either PowerShell or CLI, but the ordering may suggest a Windows-first approach. There are no Linux-specific instructions, examples, or references, and Visual Studio (primarily a Windows IDE) is mentioned for template management, with no mention of cross-platform alternatives like VS Code.
Recommendations
- Alternate the order of Azure PowerShell and Azure CLI when listing options, or list Azure CLI first to reflect its cross-platform nature.
- Provide explicit example commands for both Azure PowerShell and Azure CLI, ensuring parity and clarity for Linux users.
- Mention and provide instructions for using Visual Studio Code (VS Code) as a cross-platform alternative to Visual Studio for managing and deploying ARM templates.
- Add notes or sections highlighting any platform-specific considerations, especially for Linux/macOS users.
- Ensure that any references to tools or workflows (such as exporting templates) include cross-platform options and not just Windows-centric tools.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/set-up-zone-redundancy-availability-zones.md
...ogic-apps/set-up-zone-redundancy-availability-zones.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits a mild Windows bias by referencing 'Windows plan' multiple times and only mentioning Windows-based hosting options when discussing zone redundancy. There are no Linux-specific examples, nor is there mention of Linux-based plans or parity in the creation process. The screenshots and instructions focus solely on the Azure portal experience, which is platform-agnostic, but the explicit references to 'Windows plan' without mention of Linux equivalents suggest a Windows-first perspective.
Recommendations
- Explicitly mention both Windows and Linux hosting options where applicable, such as 'Windows or Linux plan' instead of just 'Windows plan'.
- Clarify whether zone redundancy is supported for both Windows and Linux plans, and provide guidance for both.
- If there are differences in enabling zone redundancy for Linux-based logic apps, include those steps or note any limitations.
- Add examples or notes for users deploying logic apps on Linux-based App Service plans.
- Review screenshots and instructions to ensure they are not implicitly favoring Windows environments.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/single-tenant-overview-compare.md
.../articles/logic-apps/single-tenant-overview-compare.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias, most notably by referencing 'Azure App Service Environment v3 (Windows plans only)' multiple times before mentioning any cross-platform or Linux options. There is also a lack of explicit mention of Linux-based hosting or development environments, and no Linux-specific tools or instructions are provided. However, the documentation does not rely heavily on PowerShell or Windows-only CLI tools, and most instructions are platform-agnostic (Azure Portal, VS Code, Azure CLI).
Recommendations
- Explicitly mention Linux-based hosting options (such as Linux App Service plans) where applicable, or clarify if they are not supported.
- If certain features are Windows-only (e.g., ASE v3), provide equivalent Linux options or clearly state the limitation.
- Include examples or notes for Linux users, such as using Bash with Azure CLI, or developing on Linux-based VS Code.
- Where documentation references 'Windows plans only', consider adding a parallel statement about Linux support or lack thereof.
- Ensure parity in tool recommendations (e.g., if Azure PowerShell is mentioned, also mention Bash/Azure CLI for Linux).
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/workflow-definition-language-functions-reference.md
...ps/workflow-definition-language-functions-reference.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page for Azure Logic Apps and Power Automate expression functions shows evidence of Windows bias. Specifically, references to time zone names and date/time formatting consistently point to Microsoft Windows resources (e.g., 'Microsoft Windows Default Time Zones', .NET date/time format strings), and no mention is made of Linux or IANA time zone standards. The documentation relies on .NET conventions and Windows-centric resources, which may not be familiar or directly applicable to Linux users. There are no PowerShell-specific examples, but Windows tools and patterns are referenced exclusively or before any cross-platform alternatives.
Recommendations
- Where time zone names are referenced, also provide IANA/Olson time zone equivalents or clarify how to map between Windows and IANA time zones.
- When referencing date/time format strings, note that these are .NET-specific and provide links or mappings to equivalent POSIX/strftime formats where possible.
- Add a note clarifying that the underlying implementation is based on .NET, which may use Windows conventions, but provide guidance for Linux users on how to adapt or interpret these values.
- Where external resources are linked (e.g., Microsoft Windows Default Time Zones), also link to cross-platform resources or explain any differences.
- Explicitly state any platform dependencies or limitations, and provide examples or explanations relevant to Linux environments if applicable.
Logic Apps
Why move from BizTalk Server to Azure Logic Apps?
...ticles/logic-apps/biztalk-server-migration-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page is focused on migrating from BizTalk Server (a Windows-only product) to Azure Logic Apps. While the overall content is appropriately Windows-centric due to BizTalk's nature, there are several instances where Windows tools (such as MMC snap-ins, PowerShell, and Windows registry) are referenced as default or primary options, sometimes without mentioning Linux/macOS alternatives or parity. Examples and tool references (e.g., BizTalk Administration Console, BizTalk Health Monitor, PowerShell for deployment) are Windows-specific and appear before any mention of cross-platform or Linux-native tools. However, Azure Logic Apps and related Azure services are described as cross-platform, and the documentation does not prevent Linux/macOS users from completing migration or using Azure services.
Recommendations
- Where possible, clarify which management and deployment tasks for Azure Logic Apps can be performed using cross-platform tools (e.g., Azure CLI, Bash scripts) in addition to PowerShell.
- When referencing developer experiences, highlight Visual Studio Code and Azure portal as cross-platform options before mentioning Windows-only tools.
- For monitoring and operations, mention Azure Monitor, Application Insights, and other web-based or cross-platform tools before or alongside Windows-only tools.
- Explicitly state when a tool or feature is Windows-only and suggest alternatives for Linux/macOS users if available.
- In deployment sections, provide examples using both PowerShell and Azure CLI/Bash where applicable.
Logic Apps
Call Azure Functions from workflows
...cles/logic-apps/call-azure-functions-from-workflows.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides examples and instructions for creating and managing Azure Functions using both cross-platform and Windows-specific tools. However, there is a slight bias towards Windows tools and patterns: PowerShell is mentioned as a way to find tenant IDs, and Visual Studio (Windows-only) is listed before Visual Studio Code and Azure CLI. The use of Kudu (Advanced Tools) for editing files is also more familiar to Windows users. Linux/macOS equivalents (such as Bash, cross-platform CLI commands, or VS Code) are present but not emphasized equally.
Recommendations
- When listing tools for creating Azure Functions, mention cross-platform options (Azure CLI, VS Code) before Windows-only tools (Visual Studio, PowerShell).
- Provide explicit Bash/Azure CLI commands for tasks like finding tenant IDs, object IDs, and editing function.json, alongside PowerShell examples.
- Clarify that Kudu is accessible via the browser and is not Windows-specific, and suggest alternatives for editing files (e.g., using Azure CLI or VS Code).
- Ensure screenshots and step-by-step instructions are not overly tailored to Windows UI conventions.