orchardcore-omnichannel-event-grid

Orchard Core Omnichannel Azure Event Grid

Configure Event Grid Ingestion

You are an Orchard Core expert. Configure a secure Azure Event Grid webhook for the CrestApps Omnichannel pipeline, most commonly to receive Azure Communication Services (ACS) inbound texts.

Guidelines

• Install CrestApps.OrchardCore.Omnichannel.EventGrid in the web/startup project and enable CrestApps.OrchardCore.Omnichannel.EventGrid (it depends only on CrestApps.OrchardCore.Omnichannel).
• The endpoint POST ~/api/azure/webhook/eventgrid is anonymous and disables antiforgery; every request, including the validation handshake, must pass the SAS key or bearer-token check or it gets 401 Unauthorized.
• Only the Event Grid event schema is accepted. A CloudEvents subscription is answered with 400 Bad Request.
• Keep the SAS key and Entra settings in secrets or environment configuration, never in recipes or source.
• For ACS, also enable CrestApps.OrchardCore.Omnichannel.AzureCommunicationServices for the outbound providers (see orchardcore-omnichannel).

Enable via Recipe

{
  "steps": [
    {
      "name": "Feature",
      "enable": [
        "CrestApps.OrchardCore.Omnichannel.EventGrid"
      ],
      "disable": []
    }
  ]
}

Configure Authentication

EventGridOptions is bound from the tenant shell configuration section CrestApps:Omnichannel:EventGrid. In the application's root appsettings.json the section sits under the OrchardCore key:

{
  "OrchardCore": {
    "CrestApps": {
      "Omnichannel": {
        "EventGrid": {
          "EventGridSasKey": "set-from-secrets",
          "AADIssuer": "https://sts.windows.net/<tenant-id>/",
          "AADAudience": "api://<application-id>",
          "AADMetadataAddress": "https://login.microsoftonline.com/<tenant-id>/.well-known/openid-configuration"
        }
      }
    }
  }
}

A tenant's own App_Data/Sites/{tenant}/appsettings.json uses the same keys without the OrchardCore wrapper.