> For the complete documentation index, see [llms.txt](https://docs.cloudassert.com/azure-stack-hub-multi-stamp-management/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudassert.com/azure-stack-hub-multi-stamp-management/2012.3/installation/deployment/remove-vconnect-resource-provider.md).

# Remove VConnect RP

When you are no longer using VConnect RP in an environment follow the below steps to remove it and its dependencies gracefully.

## HOST VM

1. Go to the original install location (c:\CloudAssert\VConnectMSMForAzS2002)
2. Follow steps to [validate the prerequisites](/azure-stack-hub-multi-stamp-management/2012.3/installation/deployment/validating-prerequisites.md) if not done already or if the 'InputParameters.dat' file is not available.
3. Run the following command to uninstall VConnect resource provider.

```
.\InstallVConnect.ps1 -Uninstall
```

![](/files/-M7Jc7W2F_hlrQwJooAU)

Uninstall can take 15-30 minutes to complete normally.&#x20;

&#x20;    3\. Verify removing VConnect RP in Azure Stack Portals

* In **Admin Portal** -> **Resource Groups,** the resource group named **system. \[location].cloudassert.vconnect** should not exist.
* In **Tenant Portal** -> **Resource Groups,** the resource group named **system.\[location].cloudassert.vconnect.rp** should not exist.     &#x20;

&#x20;    4\. Go to **Admin portal** -> **Offers**, clean up any Offers that VConnect RP was tied to and are no longer used

&#x20;    5\. Go to **Admin portal** -> **Plans**, clean up any plans that VConnect RP was tied to and are no longer used

### SQL Server&#x20;

If the SQL Server was created only for VConnect RP exclusively and is no longer needed:

1. Follow steps in [Create SQL Server VM and necessary databases in a tenant subscription](/azure-stack-hub-multi-stamp-management/2012.3/installation/prerequisites/create-sql-server-vm-in-tenant-subscription.md) including the parameter named  -**Uninstall $true**
2. Once deployment successfully completes, Go to **Resources** -> verify SQL Server VM is not present

If the SQL Server is being used for other purposes and need to be retained:

Remove the below called out 3 databases CloudAssert.VConnect, CloudAssert.Billing, CloudAssert.DACM that was used by VConnect RP.&#x20;

![](/files/-M7Je2ls0HlR87Nn3DBi)

&#x20;          &#x20;
