You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
When we remove a subscription using terraform, it is simply moved to the tenant root.
Isn't the management group "Decommisioned" in the ALZ mgmt-structure supposed to be the target location for such decomissioned subscriptions?
Describe the solution you'd like
I would like that the decomissioned subscriptions would be moved to the "Decommisioned"-folder after terraform removes them.
It would also be nice with functionality to clean up/remove them altogether after the "grace period" has ended.
The text was updated successfully, but these errors were encountered:
knuterik-ballestad
changed the title
feat:Move_And_Delete_decomissioned_subscriptions
feat:Move and delete decomissioned subscriptions
Mar 19, 2024
Doesn't solve the above, but if you change the default management group to "Decommissioned" then all subscriptions removed from the config will get disabled and dropped there.
The caveat is that all newly create subscriptions also get placed there initially.
Description
When we remove a subscription using terraform, it is simply moved to the tenant root.
Isn't the management group "Decommisioned" in the ALZ mgmt-structure supposed to be the target location for such decomissioned subscriptions?
Describe the solution you'd like
I would like that the decomissioned subscriptions would be moved to the "Decommisioned"-folder after terraform removes them.
It would also be nice with functionality to clean up/remove them altogether after the "grace period" has ended.
The text was updated successfully, but these errors were encountered: