During the business survey in the early stage of your cloud adoption strategy, you can disable the landing zone management feature. After you disable the feature, you can build a landing zone at any time. However, if the landing zone that you build has been used in formal enterprise management, carefully consider whether to disable the feature after you read this topic.
Impacts of disabling the feature
Deleted resources
After you disable the landing zone management feature, the following resources are automatically deleted:
You can delete blueprint settings and job history.
You can delete all enabled protection rules in the Cloud Governance Center.
Retained resources
For the sake of security and risk management, the following cloud services or resources are retained after you disable the landing zone management feature:
Retains enabled resource directories, folders, and members.
Your existing CloudSSO and access configurations are retained.
Resources that are created and related resource configurations, such as the Object Storage Service (OSS) bucket or Simple Log Service Logstore to which you deliver logs and the Cloud Enterprise Network (CEN) instance and virtual private cloud (VPC) that you create
If you want to delete all landing zone deployment configurations, you must manually delete the retained resources.
Procedure
Log on to the Cloud Governance Center console.
In the navigation pane on the left, click Settings.
In the Disable Landing Zone Management section of the Settings page, click Deactivate.
In the Shutdown Landing Zone Management Service dialog box, read the shutdown risks and confirm the shutdown by clicking Confirm Shutdown.