Skip to content
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.

Sign up for GitHub

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

Jump to bottom

02 - Define which Azure regions you will allow #14

Open
edm-ms opened this issue Sep 29, 2021 · 0 comments
Open

02 - Define which Azure regions you will allow #14

edm-ms opened this issue Sep 29, 2021 · 0 comments
Labels
customer to-do Work that needs to be done after deployment of ESLZ
Milestone
Landing Zone Enab...

Comments

@edm-ms
Copy link
Owner

edm-ms commented Sep 29, 2021

It is important to define which Azure regions will be allowed for deployment. It is recommended to scope this value at the landing zone management group. If you have workloads with data sovereignty requirements these policies can be scoped again to a management group aligned to managing those workloads.
@edm-ms edm-ms added the enhancement New feature or request label Sep 29, 2021
@edm-ms edm-ms added this to the Landing Zone Enablement milestone Sep 29, 2021
@edm-ms edm-ms added customer to-do Work that needs to be done after deployment of ESLZ and removed enhancement New feature or request labels Sep 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
customer to-do Work that needs to be done after deployment of ESLZ
Projects
None yet
Milestone
Landing Zone Enablement
Development

No branches or pull requests
1 participant
@edm-ms