Update database-export.md

fix bug in location of the import/export history in the Azure portal

Author: WilliamDAssafMSFT

articles/azure-sql/database/database-export.md

@@ -9,7 +9,7 @@ author: cawrites
 ms.custom: sqldbrb=2
 ms.author: chadam
 ms.reviewer: 
-ms.date: 01/11/2021
+ms.date: 11/01/2021
 ms.topic: how-to
 ---
 # Export to a BACPAC file - Azure SQL Database and Azure SQL Managed Instance
@@ -41,19 +41,17 @@ Exporting a BACPAC of a database from [Azure SQL Managed Instance](../managed-in
 > [!NOTE]
 > Machines processing import/export requests submitted through the Azure portal or PowerShell need to store the BACPAC file as well as temporary files generated by the Data-Tier Application Framework (DacFX). The disk space required varies significantly among databases with the same size and can require disk space up to 3 times the size of the database. Machines running the import/export request only have 450GB local disk space. As a result, some requests may fail with the error `There is not enough space on the disk`. In this case, the workaround is to run sqlpackage.exe on a machine with enough local disk space. We encourage using [SqlPackage](#sqlpackage-utility) to import/export databases larger than 150GB to avoid this issue.
 
-1. To export a database using the [Azure portal](https://portal.azure.com), open the page for your database and click **Export** on the toolbar.
+1. To export a database using the [Azure portal](https://portal.azure.com), open the page for your database and select **Export** on the toolbar.
 
    ![Screenshot that highlights the Export button.](./media/database-export/database-export1.png)
 
 2. Specify the BACPAC filename, select an existing Azure storage account and container for the export, and then provide the appropriate credentials for access to the source database. A SQL **Server admin login** is needed here even if you are the Azure admin, as being an Azure admin does not equate to having admin permissions in Azure SQL Database or Azure SQL Managed Instance.
 
     ![Database export](./media/database-export/database-export2.png)
 
-3. Click **OK**.
+3. Select **OK**.
 
-4. To monitor the progress of the export operation, open the page for the server containing the database being exported. Under to **Settings** and then click **Import/Export history**.
-
-   ![export history](./media/database-export/export-history.png)
+4. To monitor the progress of the export operation, open the page for the server containing the database being exported. Under **Data management**, select **Import/Export history**.
 
 ## SQLPackage utility