Allow communication between vnets in different subscription-CodePudding

would appreciate some assistance.

I have an single enrolment with two subscriptions

Subscription A (with several vents e.g. A1, A2, A3)
Subscription B (with several vents e.g. B1, B2, B3)

I am avoiding the VPNs and VNET peering due to company policies (treat each subscription like a separate entity)

In Subscription B, Azure Files and SQL will be used which Subscription A (A1, A2, A3) need to access and vice versa

We are looking into using public endpoints for Azure SQL and Azure Files (SMB), then locking down the access via firewall rules. This does cause issues with the public endpoints and I will looking at other options other then VPN and VNET peering about securing this communication.

I do appreciate that data between Subscription A and Subscription B will be via the Azure backbone as all service are in the same region.

Could Private Links be used there?

thanks

CodePudding user response：

Could Private Links be used there?

As per the Microsoft

On the SQL side, to access public networks, you can choose Public network access option and allow only selected networks to access the server. Along with that, you should also opt for Allow Azure services and resources to access this server.