NAT Gateway
2 TopicsService Bus: Ip has been prevented to connect to the endpoint
Hi Since yesterday we are facing issues with our Azure Functions (ASP) connecting to the Azure Sevice Bus (Standard, not in VNET). This was working before without any issues and since yesterday it is not working anymore on all our environments so I wonder if there is any general issue. Message: Put token failed. status-code: 401, status-description: Ip has been prevented to connect to the endpoint.For more information see:Virtual Network service endpoints The Azure Functions are communication via Nat Gatway and the public Ip address is set in the IP Filter List of the SBN. As far as I deactivate the IP filter to allow any traffic, it is working again. I also can see, that the used outbound Ip is exactly the smae which is set in the ip filter list. We are susing the AMQP protocol. [Error] An unhandled exception occurred in the message batch receive loop (namespace='....servicebus.windows.net', entityPath='.../Subscriptions/...', singleDispatch='False', isSessionsEnabled='False', functionId='Host.Functions.ProcessTripsBc').System.UnauthorizedAccessException : Put token failed. status-code: 401, status-description: Ip has been prevented to connect to the endpoint.For more information see:Virtual Network service endpoints:Event Hubs: https://go.microsoft.com/fwlink/?linkid=2044192Service Bus: https://go.microsoft.com/fwlink/?linkid=2044235IP Filters:Event Hubs: https://go.microsoft.com/fwlink/?linkid=2044428Service Bus: https://go.microsoft.com/fwlink/?linkid=2044183TrackingId:0ac55176-7c9d-4577-bc35-246418724a7d_G0 Regards MichaelSolved296Views0likes1CommentOutbound IPs on App Services
I recently moved a number of my app services into a NAT gateway Vnet integration with a static outbound public IP. I have confirmed that the traffic is using the new static public IP but when I look at the app in portal.azure.com I still see all the multi-tenant outbound public IPs listed as "outbound IPs" they used to use, and my public static IP that the NAT gateway uses is not listed at all. This adds confusion for our more junior members of the team. Is there a way to remove seeing those the multi-tenant outbound IPs now that they are not used?1.1KViews0likes2Comments