Merge pull request #192668 from MikeRayMSFT/20220323-delete-directly-connected-mi

Add tabbed conceptual for deployment type.

Author: PRMerger12

articles/azure-arc/data/delete-managed-instance.md

@@ -32,10 +32,12 @@ demo-mi 1/1         10.240.0.4:32023  Ready
 
 ## Delete Azure Arc-enabled SQL Managed Instance
 
-To delete a SQL Managed Instance, run the following command:
+To delete a SQL Managed Instance, run the appropriate command for your deployment type. For example:
+
+### [Indirectly connected mode](#tab/indirectly)
 
 ```azurecli
-az sql mi-arc delete -n <NAME_OF_INSTANCE> --k8s-namespace <namespace> --use-k8s
+az sql mi-arc delete -n <instance_name> --k8s-namespace <namespace> --use-k8s
 ```
 
 Output should look something like this:
@@ -45,6 +47,21 @@ Output should look something like this:
 Deleted demo-mi from namespace arc
 ```
 
+### [Directly connected mode](#tab/directly)
+
+```azurecli
+az sql mi-arc delete -n <instance_name> -g <resource_group>
+```
+
+Output should look something like this:
+
+```azurecli
+# az sql mi-arc delete -n demo-mi -g my-rg
+Deleted demo-mi from namespace arc
+```
+
+---
+
 ## Reclaim the Kubernetes Persistent Volume Claims (PVCs)
 
 A PersistentVolumeClaim (PVC) is a request for storage by a user from Kubernetes cluster while creating and adding storage to a SQL Managed Instance. Deleting a SQL Managed Instance does not remove its associated [PVCs](https://kubernetes.io/docs/concepts/storage/persistent-volumes/). This is by design. The intention is to help the user to access the database files in case the deletion of instance was accidental. Deleting PVCs is not mandatory. However it is recommended. If you don't reclaim these PVCs, you'll eventually end up with errors as your Kubernetes cluster will run out of disk space or usage of the same SQL Managed Instance name while creating new instance might cause inconsistencies. To reclaim the PVCs, take the following steps: