-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation: Missing guidance when deploying with an existing Firewall. #279
Comments
Hi @MiguelElGallo, It seems like you are asking us to provide the option to deploy DNS & Firewall, only DNS or none of the two. This would most likely solve your problems? |
I have the same concern. Currently the Data Management Landing Zone Documentation is describing on how to deploy the resources in Data Management Landing Zone Subscription only with a service principal account created under this subscription. How about a case (mine as well):
How can we deploy the Data Management Landing Zone, while utilizing a existing Firewall, DNS resolver endpoints and other resources that are in another subscription, but under the same AD tenant. |
Sorry for the late response @imcloud-unni, data-management-zone/infra/params.dev.json Lines 29 to 31 in ffdae90
If you want to deploy into an existing Azure Virtual Network provided by the platform team, you have to make some modifications to the network.bicep. Should not be too difficult to make these changes. If you need help with them, then deel free to ping me. |
Documentation Issue
Hello,
Some guidance, specially parameters (for example DNS),are missing for the following case, which is common:
Data team, needs to deploy a smaller version of the Data Management Zone ( Purview and DNS?, etc.).
No guidance and exists, we have been trying for 3 days, and no success yet, mainly DNS issues we guess.
We think this is common scenario if you are following: https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/
Can you please explain a bit about this case?
Thanks!
Code of Conduct
The text was updated successfully, but these errors were encountered: