Share via

Logic App Standard – Trigger type 'ApiConnectionNotification' not supported despite being created via Designer

Hofer, Lukas /BSS HAM 20 Reputation points
2026-03-23T10:43:07.3333333+00:00

Problem Description

We are running Logic App Standard (Single Tenant) on a WS1 App Service Plan in West Europe.

We have a workflow that monitors an Office 365 mailbox for new emails with attachments using the "When a new email arrives (V3)" trigger (Office 365 Outlook connector).

What works

  • Creating the workflow manually via the Azure Portal Designer succeeds
  • The Designer generates a trigger of type ApiConnectionNotification with a subscribe/fetch pattern and @listCallbackUrl()
  • The workflow saves successfully in the Designer
  • The API Connection (office365) is authenticated and connected (status: Connected)

What fails

When the workflow is published/enabled, it immediately fails with:

        • What we tried

Switching to ApiConnection (Polling) with recurrence: → Fails with: The 'ListCallbackUrl' API is not supported by triggers of type 'ApiConnection'.

Redeploying the API Connection (deleted and recreated, re-authorized) → Same error

Deploying via Terraform (uploading workflow.json to the Storage Share) → Same error

Creating the workflow manually in the Designer and running it from there → The Designer creates the same ApiConnectionNotification trigger, which then also fails on publish

Environment Details

Component Value
Logic App Type Standard (Single Tenant)
-------- --------
Logic App Type Standard (Single Tenant)
App Service Plan SKU WS1
Region West Europe
Runtime Version ~4
Extension Bundle Enabled
Connector Office 365 Outlook (office365)
Trigger When a new email arrives (V3)
Auth Type Managed Service Identity

Workflow Definition (trigger excerpt)

"triggers": {

        "When_a_new_email_arrives_(V3)": {

            "type": "ApiConnectionNotification",

            "inputs": {

                "host": {

                    "connection": {

                        "referenceName": "office365-1"

                    }

                },

                "fetch": {

                    "pathTemplate": {

                        "template": "/v3/Mail/OnNewEmail"

                    },

                    "method": "get",

                    "queries": {

                        "importance": "Any",

                        "fetchOnlyWithAttachment": false,

                        "includeAttachments": false,

                        "folderPath": xxx

                    }

                },

                "subscribe": {

                    "body": {

                        "NotificationUrl": "@listCallbackUrl()"

                    },

                    "pathTemplate": {

                        "template": "/GraphMailSubscriptionPoke/$subscriptions"

                    },

                    "method": "post",

                    "queries": {

                        "importance": "Any",

                        "fetchOnlyWithAttachment": false,

                        "folderPath": xxxx

                    }

                }

            },

            "splitOn": "@triggerBody()?['value']",

            "metadata": { xxxx

               

            }

        }

    },

Questions

  1. Is ApiConnectionNotification officially supported in Logic App Standard? The Designer allows creating it, but the runtime rejects it.
  2. If not, what is the correct trigger type/pattern for the "When a new email arrives (V3)" trigger in Logic App Standard?
  3. When using ApiConnection (polling) as an alternative, why does it still reference ListCallbackUrl and fail?

Expected Behavior

The "When a new email arrives (V3)" trigger should work in Logic App Standard, as the Designer allows its creation without any warnings.

Azure Logic Apps
Azure Logic Apps

An Azure service that automates the access and use of data across clouds without writing code.

Answer accepted by question author
  1. Siddhesh Desai 4,895 Reputation points Microsoft External Staff Moderator
    2026-03-23T11:12:20.1666667+00:00

    Hi @Hofer, Lukas /BSS HAM

    Thank you for reaching out to Microsoft Q&A.

    The issue occurs because the “When a new email arrives (V3)” trigger from the Office 365 Outlook connector is implemented as a push-based trigger that uses the ApiConnectionNotification trigger type with a webhook subscription pattern (subscribe / fetch) and relies on @listCallbackUrl(). While the Logic Apps Standard (Single Tenant) designer allows creating and saving this trigger, the Logic Apps Standard runtime does not support ApiConnectionNotification triggers. As a result, when the workflow is published or enabled, the runtime validation fails and rejects the trigger. This creates a mismatch where the designer experience suggests the trigger is supported, but the runtime cannot execute it. Switching the trigger type to ApiConnection (polling) does not resolve the issue because the Outlook connector itself still internally references listCallbackUrl, which is not supported for polling triggers in Logic Apps Standard.

    Refer below points to resolve this issue or this is the workaround:

    Use Logic Apps Consumption instead of Standard The “When a new email arrives (V3)” trigger is fully supported in Logic Apps Consumption, including the ApiConnectionNotification webhook pattern. Migrating this workflow to a Consumption Logic App is the simplest and officially supported solution.

    Implement Microsoft Graph manually in Logic Apps Standard If you must stay on Logic Apps Standard, use a custom approach:

    • Create a Microsoft Graph subscription for mailbox change notifications.
    • Expose an HTTP-triggered workflow or Azure Function to receive notifications.
    • Handle subscription renewal and validation manually. This avoids the unsupported ApiConnectionNotification trigger.

    Use scheduled polling with Microsoft Graph As an alternative to push notifications:

    • Use a Recurrence trigger.
    • Call Microsoft Graph GET /messages with appropriate filters (for example, receivedDateTime).
    • Track the last processed message to avoid duplicates. This approach is fully supported in Logic Apps Standard but is not real-time.

    Avoid switching the trigger type to ApiConnection (polling) for this connector Changing the trigger type does not work because the Outlook connector still depends on listCallbackUrl internally, which causes the runtime failure in Logic Apps Standard.Thank you for reaching out to Microsoft Q&A.

    The issue occurs because the “When a new email arrives (V3)” trigger from the Office 365 Outlook connector is implemented as a push-based trigger that uses the ApiConnectionNotification trigger type with a webhook subscription pattern (subscribe / fetch) and relies on @listCallbackUrl(). While the Logic Apps Standard (Single Tenant) designer allows creating and saving this trigger, the Logic Apps Standard runtime does not support ApiConnectionNotification triggers. As a result, when the workflow is published or enabled, the runtime validation fails and rejects the trigger. This creates a mismatch where the designer experience suggests the trigger is supported, but the runtime cannot execute it. Switching the trigger type to ApiConnection (polling) does not resolve the issue because the Outlook connector itself still internally references listCallbackUrl, which is not supported for polling triggers in Logic Apps Standard.

    Refer below points to resolve this issue or this is the workaround:

    Use Logic Apps Consumption instead of Standard
    The “When a new email arrives (V3)” trigger is fully supported in Logic Apps Consumption, including the ApiConnectionNotification webhook pattern. Migrating this workflow to a Consumption Logic App is the simplest and officially supported solution.

    Implement Microsoft Graph manually in Logic Apps Standard
    If you must stay on Logic Apps Standard, use a custom approach:

    • Create a Microsoft Graph subscription for mailbox change notifications.
    • Expose an HTTP-triggered workflow or Azure Function to receive notifications.
    • Handle subscription renewal and validation manually. This avoids the unsupported ApiConnectionNotification trigger.

    Use scheduled polling with Microsoft Graph
    As an alternative to push notifications:

    • Use a Recurrence trigger.
    • Call Microsoft Graph GET /messages with appropriate filters (for example, receivedDateTime).
    • Track the last processed message to avoid duplicates. This approach is fully supported in Logic Apps Standard but is not real-time.

    Avoid switching the trigger type to ApiConnection (polling) for this connector
    Changing the trigger type does not work because the Outlook connector still depends on listCallbackUrl internally, which causes the runtime failure in Logic Apps Standard.

    1 person found this answer helpful.
    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.