Removing data sources from Cloud Compliance
Contributors
Download PDF of this page
If you need to, you can stop Cloud Compliance from scanning one or more working environments, databases, file share groups, or OneDrive accounts. You can also delete the Cloud Compliance instance if you no longer want to use Cloud Compliance with your working environments.
Deactivating compliance scans for a working environment
When you deactivate scans, Cloud Compliance no longer scans the data on the working environment and it removes the indexed compliance insights from the Cloud Compliance instance (the data from the working environment itself isn’t deleted).
-
From the Scan Configuration page, click the
button in the row for the working environment, and then click Deactivate Compliance.

| You can also disable compliance scans for a working environment from the Services panel when you select the working environment. |
Removing a database from Cloud Compliance
If you no longer want to scan a certain database, you can delete it from the Cloud Compliance interface and stop all scans.
-
From the Scan Configuration page, click the
button in the row for the database, and then click Remove DB Server.

Removing a OneDrive account from Cloud Compliance
If you no longer want to scan user files from a certain OneDrive account, you can delete the account from the Cloud Compliance interface and stop all scans.
-
From the Scan Configuration page, click the
button in the row for the OneDrive account, and then click Remove OneDrive Account.
-
Click Delete Account from the confirmation dialog.
Removing a group of file shares from Cloud Compliance
If you no longer want to scan user files from a file shares group, you can delete the File Shares Group from the Cloud Compliance interface and stop all scans.
-
From the Scan Configuration page, click the
button in the row for the File Shares Group, and then click Remove File Shares Group.
-
Click Delete Group of Shares from the confirmation dialog.
Deleting the Cloud Compliance instance
You can delete the Cloud Compliance instance if you no longer want to use Cloud Compliance. Deleting the instance also deletes the associated disks where the indexed data resides.
-
Go to your cloud provider’s console and delete the Cloud Compliance instance.
The instance is named CloudCompliance with a generated hash (UUID) concatenated to it. For example: CloudCompliance-16bb6564-38ad-4080-9a92-36f5fd2f71c7
Edit on GitHub