Although we’re sorry to see you go, here is what happens if you decide to end your relationship with us, and what you can do on your own to remove CoreView resources (service accounts, Enterprise Apps, App Registrations) from your tenant.
Timeframes for data removal
When you decide to stop using CoreView and your account is canceled or your trial period ends, all data related to the service will be automatically and permanently deleted within 90 days after cancellation, or 180 days after the end of the trial.
Data is deleted from CoreView systems, which use Microsoft Azure as the hosting platform, in accordance with Microsoft’s standards for secure data deletion. Once this process starts, the deleted data cannot be recovered.
Deprovisioning process
In the event to stop using CoreView and your account is cancelled or your trial period ends, here are the steps you can take independently to ensure that CoreView no longer imports data from your tenant.
Contact the support
If needed, please open a ticket in our support system. Our team will assist you with the deprovisioning of the tenant.
Remove the Application Registrations
Remove the Applications Registrations from your tenant.
You can do this by following the article “Remove an application registered with the Microsoft identity platform” in the Microsoft documentation.
Below is the list of all Applications Registrations that should be removed, exactly as they are named within the App Registrations section in Microsoft Azure:
For CoreView:
- CoreView Graph Management Dev onboarding
For Configuration Manager SaaS:
- CoreView Configuration Manager
For Configuration Manager on-premise:
- Simeon Cloud Sync
Note: this may not exist, as you can choose to reuse one of your own applications that already exists in your tenant.
Remove the Enterprise Applications
Remove the Enterprise applications from your tenant.
You can do this in the way you prefer—just follow the article “Delete an enterprise application” in the Microsoft documentation.
Below is the list of all Enterprise Applications that should be removed, exactly as they are named within the Enterprise Applications section in Microsoft Azure. For additional details regarding their scope and permissions, please refer to our internal documentation on Enterprise Applications.
For CoreView:
- CoreView API Integration
- CoreView BitLocker API Integration
- CoreView Exchange Integration (potentially more than one)
- CoreView Graph Management Dev onboarding
- CoreView Management Integration
- CoreView Partner Portal API
- CoreView Partner Portal Web
- CoreView Portal
- CoreView Registration (if you onboarded CoreView before August 2024)
- CoreView SharePoint Integration (potentially more than one)
- CoreView SSO
- CoreView Teams API Integration
For Configuration Manager SaaS:
- CoreView Configuration Manager
For Configuration Manager on-premise:
- Simeon Cloud Sync
Note: this may not exist, as you can choose to reuse one of your own applications that already exists in your tenant.
Remove the Service Accounts
During onboarding, our service accounts may have been created.
These accounts are used to connect to your tenant and collect reporting data.
Below is the list of all service accounts that should be removed, exactly as they are named (display name) in the Users section of Microsoft Azure.
For CoreView and Configuration Manager SaaS:
- Admin Read Only 01
- Admin Read Only 02
- Company Administrator Account for CoreView Management (if management sessions has been enabled)
For Configuration Manager on-premise:
- Microsoft 365 Management Service Account
Note: this may not exist, as during tenant onboarding you may choose to work in delegated authentication mode. In that case, a service account is not created; instead, the identity of the user logged into the front-end application is used directly.
You can safely remove them from the user list in Microsoft Entra or Microsoft Azure. Follow the guide “How to create, invite, and delete users” in the Microsoft documentation for instructions on how to do this.