s2s | A tool to write code | Code Inspection library

I have situation where I want to open my Vnet(lets say Vnet1) for other Vnets (which has private IP range defined ) , I am thinking to use NSG rules and allow private IP ranges of other Vnets (lets say Vnet2 , Vnet3) to this entry point Subnet(in Vnet1) which host my API gateway . I have two questions :

1. I assume it should be feasible using private IP addresses and allowing them using NSG (of Vnet 1/Subnet 1) ? I am not looking for peering/s2s vpn of Vnet as both belongs to separate teams and Vnet2/Vnet3 just wanted to access APis of Vnet1 using Api gateway.

2. Is there any security issues which we foresee , I assume it safe to expose since these are private IPs and can not be accesses from internet .

Please let me know opinion on feasibility and security .

Thanks Xslguy

Would a VM on-premises connected to Azure through an S2S VPN tunnel be able to query Azure DNS (168.63.129.16) for Azure private zones, or would a custom DNS be required to forward the query?

Thanks!

I know Virtual network peering is a thing but just like that is VPN Gateway peering is a thing? if so then if a VPN Gateway(A) with AD AuthN(OpenVPN SSL tunnel type) and a VPN Gateway(B) with Azure certificate-based authN with SSTP(SSL) tunnel type, Can A and B be peered.

Questions based on above:

1. Do we have to do S2S peering setup between A and B with manual routing for each to access any resource from A to B and vice versa?
2. What is the limitation of this setup and advantages(if any)?
3. Will it be called a Hybrid solution?

Is it possible to send s2s events to branch from 3d party tracker? I see documentation for inapp events.

I am trying to deploy Hybrid Application on Azure. My Application will be hosted on Azure Cloud App Service and Database will be on company's private DC. I have some question on optimal architecture or optimum architecture solution on Azure in this scenario. I have an option to use VPN S2S connection or Azure Application Service Hybrid Connection Manager (HCM).

Since they both establish connection over public Internet they both will suffer from multiple hops connections and probably no SLA guarantees.

So what are the design consideration while choosing one over other and when would I choose Hybrid Connection manager (HCM) over VPN Site-to-site (S2S) when establishing hybrid connectivity from Azure hosed Application (PaaS) with the on-premise DB? Which one is faster?

Configuring a VNet-to-VNet connection is the preferred option to easily connect VNets if you need a secure tunnel using IPsec/IKE. In this case the documentation says that traffic between VNets is routed through the Microsoft backbone infrastructure.

According to the documentation, a Site-to-Site connection is also possible:

If you are working with a complicated network configuration, you may prefer to connect your VNets using the Site-to-Site steps, instead the VNet-to-VNet steps. When you use the Site-to-Site steps, you create and configure the local network gateways manually.

In this case we have control over the configuration of the virtual local network address space, but we need expose public IPs. Documentation don´t says nothing about where the traffic goes (azure internal or public internet)

My question is, in this scenario, S2S between VNets, the traffic is routed through azure infrastructure as in the case of VNet-to-VNet or the comunication is done through public internet?

I am trying to configure a VPN in Azure Powershell following the procedure here. When running the following command

Is there an API point or whatever other queryable source where I can get the total queued data?:

setting up a little dataflow in NiFi to monitor NiFi itself sounds sketchy, but if it's a common practice, let's be it. Anyway, I cannot find the API endpoint to get that total

Note: I have a single NiFi instance: I don't have nor will implement S2S reporting since I am on a single instance, single node NiFi setup

We're having a strange issue today brought on by an unexpected power failure back in our office while we're all working remotely. After dispatching someone to restart the equipment, our office internet connection came back up and we're able to reach some services, but our Site-to-Site (S2S) VPN between our office network and the cloud is no longer functioning. The odd part is that Azure indicates that the VPN is "Connected", and -- after some creative tunneling -- I was able to confirm that Windows Server 2019 in the office also indicates the connection as "Connected", so this looks like a routing issue. This VPN has worked faithfully for 10 months, through reboots and Windows Updates, and yet today it's inexplicably down.

Now, some history: Back in June 2019, we set-up an S2S VPN between our office in LA and resources in Azure. The goal was to start using Windows Virtual Desktop on Azure for remote employee virtual desktops, while enabling them to access the same resources as on-site employees. Back then, we ran the following PowerShell script on the domain controller in LA to configure Windows Server 2019 with the S2S VPN to Azure: