-
Notifications
You must be signed in to change notification settings - Fork 980
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
Bug Report -Existing Management Group #1080
Comments
Hey @aj-msft, Good find. What would you want the error message to say and where would you like it to appear? We can then get this implemented. We can make this a dynamic warning though it would just be a generic warning displayed all the time. As in the portal experience we cannot do any pre-validation I'm afraid. The error would look similar to this on the MG blade: |
Hey @jtracey93 Thanks for getting back to me. A warning along the lines stating that any existing management groups with the same name as what is specified in the Accelerator deployment would be moved to the new Landing zone would suffice if it were displayed in the validation screen. Thanks |
Hey @aj-msft we cannot make this appear on the validation screen, as this is a screen that is provided by the underlying service used for custom portal experiences. However, we can make it appear on the "Azure core" tab/page, would that be sufficient? Let us know Thanks Jack |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. |
Hey @aj-msft, Any thoughts on my last suggestion (#1080 (comment))? Let us know Thanks Jack |
Hi @jtracey93, Would it be possible to add it to the tabs where Management Groups are created (Platform, Azure Core, Landing Zone etc) ? Regards |
Existing Management Group with the same name under the Root Tenant gets moved while running the Accelerator
Steps to reproduce
This is an issue as customers who have existing Management Group with the same name as what is specified within the Accelerator could face issues when the MG and subscriptions are moved under the new Landing zone and policies are applied. It would be good to see a warning if there are any MG groups with the same name already present in the customer environment.
The text was updated successfully, but these errors were encountered: