Merge pull request #231626 from whhender/patch-88

Update deployment-best-practices.md

Author: prmerger-automator[bot]

articles/purview/deployment-best-practices.md

@@ -5,7 +5,7 @@ author: shsandeep123
 ms.author: sandeepshah
 ms.service: purview
 ms.topic: conceptual
-ms.date: 08/04/2022
+ms.date: 03/21/2023
 ---
 # Microsoft Purview (formerly Azure Purview) deployment best practices
 
@@ -315,45 +315,9 @@ In the Microsoft Purview Data Map, there are several areas where the Catalog Adm
 
 ## Moving tenants
 
-If your Azure Subscription moves tenants while you have a Microsoft Purview account, there are some steps you should follow after the move.
+If your Azure Subscription moves tenants while you have a Microsoft Purview account, you will need to create a new Microsoft Purview account and re-register and scan your sources.
 
-Currently your Microsoft Purview account's system assigned and user assigned managed identities will be cleared during the move to the new tenant. This is because your Azure tenant houses all authentication information, so these need to be updated for your Microsoft Purview account in the new tenant.
-
-After the move, follow the below steps to clear the old identities, and create new ones:
-
-1. If you're running locally, sign in to Azure through the Azure CLI.
-
-    ```azurecli-interactive
-      az login
-      ```
-    Alternatively, you can use the [Azure Cloud Shell](../cloud-shell/overview.md) in the Azure portal. 
-    Direct browser link: [https://shell.azure.com](https://shell.azure.com).
-
-1. Obtain an access token by using [az account get-access-token](/cli/azure/account#az-account-get-access-token).
-    ```azurecli-interactive
-    az account get-access-token
-    ```
-
-1. Run the following bash command to disable all managed identities (user and system assigned managed identities):
-
-    > [!IMPORTANT]
-    > Be sure to replace these values in the below commands:
-    > - \<Subscription_Id>: Your Azure Subscription ID
-    > - \<Resource_Group_Name>: Name of the resource group where your Microsoft Purview account is housed.
-    > - \<Account_Name>: Your Microsoft Purview account name
-    > - \<Access_Token>: The token from the first two steps.
-
-    ```bash
-    curl 'https://management.azure.com/subscriptions/<Subscription_Id>/resourceGroups/<Resource_Group_Name>/providers/Microsoft.Purview/accounts/<Account_Name>?api-version=2021-07-01' -X PATCH -d'{"identity":{"type":"None"}}' -H "Content-Type: application/json" -H "Authorization:Bearer <Access_Token>"
-    ```
-
-1. To enable your new system managed assigned identity (SAMI), run the following bash command:
-  
-    ```bash
-    curl 'https://management.azure.com/subscriptions/<Subscription_Id>/resourceGroups/<Resource_Group_Name>/providers/Microsoft.Purview/accounts/<Account_Name>?api-version=2021-07-01' -X PATCH -d '{"identity":{"type":"SystemAssigned"}}' -H "Content-Type: application/json" -H "Authorization:Bearer <Access_Token>"
-    ```
-
-1. If you had a user assigned managed identity (UAMI), to enable one on your new tenant, register your UAMI in Microsoft Purview as you did originally by following [the steps from the manage credentials article](manage-credentials.md#create-a-user-assigned-managed-identity).
+Moving tenants is not currently supported for Microsoft Purview.
 
 ## Next steps