Data flow in not showing in Event hub while Event grid has data from OAuth Partner

ChiragAggarwal-4011 0 Reputation points
2025-08-28T19:13:49.3133333+00:00

Hello All,

I wanted to inform that in one of the case, where I am facing issue that ->there is connectivity from OAuth Partner(AWS) in Event grid to the Event hub while I cannot see the data flow in Event hub from Event grid.

The Architecture is as follows: OAuth->Event Grid-> Event Hub

Additionally, both dev and prod env are setups.
Is it related to permissions on event grid? Moreover, I've the Contributor and Reader roles.

Please help to check on it.

Azure Event Hubs
0 comments No comments
{count} votes

Accepted answer
  1. John Burkholder 0 Reputation points
    2025-08-28T20:32:56.37+00:00

    Based on your architecture—OAuth Partner (AWS) → Event Grid → Event Hub—and the issue where data is visible in Event Grid but not flowing into Event Hub, here are the most likely causes and troubleshooting steps:


    1. Permissions and Role Assignments

    Even though you have Contributor and Reader roles, these might not be sufficient for event delivery to Event Hub.

    • Event Grid Data Sender role is required to send events to Event Grid topics [1].
    • For Event Hub, ensure the destination has appropriate Azure RBAC roles or Shared Access Signatures (SAS) configured [2]. Microsoft recommends using Microsoft Entra ID (formerly Azure AD) for secure access.

    🔍 2. Partner Events Configuration

    If you're using Partner Events in Event Grid (e.g., Auth0, AWS), you must:

    • Authorize the partner to create a partner topic in your Azure subscription.
    • Activate the partner topic and create an event subscription to route events to Event Hub [3].
    • Ensure the Event Grid resource provider is registered in your subscription.

    🛠️ 3. Event Subscription and Delivery Failures

    Check for delivery failures in Event Grid:

    • Use diagnostic logs and metrics to identify publish or delivery issues [4].
    • Common errors include:
      • 403 Forbidden: Often due to missing permissions.
        • Socket errors: Network communication issues between Event Grid and Event Hub[5].
          • Internal errors: May indicate transient issues or misconfigured endpoints.

    Enable distributed tracing to track events end-to-end and correlate failures[4].


    🧪 4. Connectivity and Network Configuration

    • Ensure Event Hub endpoint is reachable from Event Grid.
    • Check firewall rules, service tags, and private endpoints if used.
    • Validate that port 443 is open for HTTPS communication.

    ✅ Recommended Actions

    1. Assign the EventGrid Data Sender role to the identity publishing events.
    2. Verify Event Hub access via Microsoft Entra ID or SAS.
    3. Enable diagnostics on both Event Grid and Event Hub.
    4. Check Event Grid metrics for delivery failures and retry attempts.
    5. Confirm partner topic activation and event subscription setup.
    6. Open a support ticket if the steps above do not work.

    References

    [1] Azure Event Grid security and authentication - Azure Event Grid

    [2] Authorize access to Azure Event Hubs - Azure Event Hubs

    [3] Partner Events overview for customers - Azure Event Grid

    [4] Troubleshoot Event Grid issues - Azure Event Grid | Microsoft Learn

    [5] Azure Event Grid to Azure Event Hub events delivery failed

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

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