Forum Discussion

chandrab3009's avatar
chandrab3009
Copper Contributor
Dec 15, 2021

Issue in access eventgrid using private end point

Hi experts, I need help in the below situation
1. Created a event grid topic( dynamic up for the url (https://sample-interviewupdates.westeurope-1.eventgrid.azure.net/api/events) that is generated)
2. Vnet created with a subnet ( ex10.1.0.10) https://l.facebook.com/l.php?u=https%3A%2F%2F10.1.0.10%2F16%3Ffbclid%3DIwAR0qTBHUzpEM6v8sqUSC08QKQy1UoE7KamgQUuPQ4b2FEkrbbKYISz69cKs&h=AT1mHNPFBvTAk31Bo3LXJWE8psz96GioQsS39LRUOXANUOo4irW7HrHiwO_1jfBzftyjdPR1BRXp0pQzsaKj6T4t3YKDSFkIl2FY6CaPLAwDL5SRUe-6DmJ0IuX_4D45pxQ&__tn__=-UK-R&c[0]=AT0WnODKMPlOmcVtvGahWZAws61W5GIAet-hYmP3DE9eWKFqJ-OQlJL2RUZtVMJrMvC9I6IEgpuPPIUzc4L3ng4-Mf_43i3eRDLmoap28zb-E3lWxF_nK4UsghUNCxGTLH57Yd4a5d5xpGiOcLbf8RjfXy-CGFjv0CriktGRUez2M3Lbd7_IY3_29KZspuTYBbk3BVR2SfM_
3. Virtual network gateway for vnet
4. I have on premise vpn with firewall
5. Local network gateway with above vpn network details(ex 198.1.1.1)
6. Created private endpoint for event grid by mapping above vnet.
 (https://sample-interviewupdates.westeurope-1.privatelink.eventgrid.azure.net/api/events) and ip mapping https://l.facebook.com/l.php?u=https%3A%2F%2F10.1.0.10%2F16%3Ffbclid%3DIwAR0qTBHUzpEM6v8sqUSC08QKQy1UoE7KamgQUuPQ4b2FEkrbbKYISz69cKs&h=AT1mHNPFBvTAk31Bo3LXJWE8psz96GioQsS39LRUOXANUOo4irW7HrHiwO_1jfBzftyjdPR1BRXp0pQzsaKj6T4t3YKDSFkIl2FY6CaPLAwDL5SRUe-6DmJ0IuX_4D45pxQ&__tn__=-UK-R&c[0]=AT0WnODKMPlOmcVtvGahWZAws61W5GIAet-hYmP3DE9eWKFqJ-OQlJL2RUZtVMJrMvC9I6IEgpuPPIUzc4L3ng4-Mf_43i3eRDLmoap28zb-E3lWxF_nK4UsghUNCxGTLH57Yd4a5d5xpGiOcLbf8RjfXy-CGFjv0CriktGRUez2M3Lbd7_IY3_29KZspuTYBbk3BVR2SfM_
7. Client applications which is in vpn network trying to access the event grid with its url not working. Tried to ping url it’s showing dynamic of event grid not the private end point.
Do you have any clue what could be the reason?? It seems local @firewall has an issue or routing issue??
Thankyou in advance
 

1 Reply

  • The Event Grid private endpoint has been provisioned successfully; however, client DNS resolution continues to point to the public Event Grid IP address. To ensure proper connectivity, DNS must be configured to leverage a private zone with forwarding so that the Event Grid FQDN resolves to the private endpoint IP. Once DNS resolution and network routing are correctly aligned, client applications will be able to establish secure connectivity to the private endpoint through the VPN.

Resources