VNET
3 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 MichaelSolved269Views0likes1CommentWhich route to add in following peering scenario for traffic forwarding ?
Hi, I am trying a scenario as per the diagram where ABC Azure network are peered in a chain & VM-A is trying to communicate with VM-C. "Allow forwarded traffic" is enabled for all peering's. A is not directly peered with C. Will a traffic transit work over B with custom route here or is A-C direct peering the way to go.1.5KViews0likes1CommentVM: to add/change vnet i need to redeploy VM ?
Hello Team, I could not add another vnet to my vm, nor change assigned vnet to another. Found in a documentation: If you create a VM and later want to migrate it into a virtual network, it is not a simple configuration change. You have to redeploy the VM into the virtual network. The easiest way to do this is to delete the VM, but not any disks attached to it, and then re-create the VM using the original disks in the virtual network That's strange. Why i can not attach my VM to a different network ? I could do it on any hypervisor. Interface flap for OS causes DHCP process to jump in to get the right ip. Could you clarify ? Thanks, Michal1.2KViews0likes1Comment