First draft of changes for Issue #105347

Author: James-Green-Microsoft

articles/private-5g-core/commission-cluster.md

@@ -304,7 +304,15 @@ You should see the new **Custom Location** visible as a resource in the Azure po
 
 ## Rollback
 
-If you have made an error in the Azure Stack Edge configuration, you can use the portal to remove the AKS cluster.  You can then modify the settings via the local UI, or perform a full reset using the **Device Reset** blade in the local UI and then restart this procedure.
+If you have made an error in the Azure Stack Edge configuration, you can use the portal to remove the AKS cluster (see [Deploy Azure Kubernetes service on Azure Stack Edge](/azure/databox-online/azure-stack-edge-deploy-aks-on-azure-stack-edge)). You can then modify the settings via the local UI.  
+
+Alternatively, you can perform a full reset using the **Device Reset** blade in the local UI (see [Azure Stack Edge device reset and reactivation](/azure/databox-online/azure-stack-edge-reset-reactivate-device)) and then restart this procedure.  In this case, you should also delete any associated resources left in the Azure Portal after completing the Azure Stack Edge reset. This will include some or all of the following, depending on how far through the process you are:
+
+- **Azure Stack Edge** resource
+- Autogenerated **KeyVault** associated with the **Azure Stack Edge** resource
+- Autogenerated **StorageAccount** associated with the **Azure Stack Edge** resource
+- **Azure Kubernetes Cluster** (if successfully created)
+- **Custom location** (if successfully created)
 
 ## Next steps