This scenario is aligned with the Az-104 and Az-700 path and provides a demo solution for managing overlapping IP address spaces with Azure Private Link.
It guides how to make applications running in one Azure virtual network accessible to users in another virtual network with an overlapping IP address space.
This scenario can be deployed to Azure using the Azure Developer CLI - AZD.
💪 This template scenario is part of the larger Microsoft Trainer Demo Deploy Catalog.
- Azure Developer CLI - AZD
- When installing AZD, the above the following tools will be installed on your machine as well, if not already installed:
- You need Owner or Contributor access permissions to an Azure Subscription to deploy the scenario.
- From within a new folder on your machine, run
azd initto initialize the deployment.
azd init -t daverendon/azd-private-link
- Next, run
azd upto trigger an actual deployment.
azd up
You will get prompted during the AZD deployment step for the location/region.
- If you want to delete the scenario from your Azure subscription, use
azd down
azd down --purge --force
⏩ Note: running azd down deletes the RG and Resources, but will keep the artifacts on your local machine.
- Use the demo guide
Your organization segments core IT apps and services (such as DNS and security services) from other parts of the business, including your manufacturing department. However, in some scenarios, apps and services in the core area need to communicate with apps and services in the manufacturing area. In this scenario, you configure connectivity between the segmented areas. This is a common scenario for separating production from development or separating one subsidiary from another.
Feel free to create issues for bugs, suggestions or Fork and create a PR with new demo scenarios or optimizations to the templates. If you like the scenario, consider giving a GitHub ⭐