You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article explains how to import or export an Azure SQL Database using [Private Link](private-endpoint-overview.md) by using the Azure portal or Azure PowerShell with *Allow Access to Azure Services* set to **Off** on the Azure SQL [logical server](logical-servers.md).
22
23
23
-
Running Import or Export requires you to set [Allow Access to Azure Services](network-access-controls-overview.md) to **On**, otherwise the Import or Export operation fails with an error.
24
+
Using Private Link allows you to perform import/export operations securely without needing to set [Allow Access to Azure Services](network-access-controls-overview.md) to **On**, which would otherwise be required for standard import/export operations.
24
25
25
26
> [!NOTE]
26
27
> Import/export using private link for Azure SQL Database is currently in preview.
27
28
29
+
## Prerequisites
30
+
31
+
Before using import/export with Private Link, ensure you have the following:
32
+
33
+
- An Azure SQL logical server with private endpoint connectivity configured to a virtual network
34
+
- An Azure Storage account with a blob container that contains your BACPAC file (for import) or will store the exported BACPAC file
35
+
- The Azure SQL logical server and Storage account must have private endpoints configured within the same or peered virtual networks
36
+
- Appropriate permissions to approve private endpoint connections on both the Azure SQL logical server and the Storage account
37
+
28
38
## What is import/export private link?
29
39
30
-
The database import/export private link is a service managed private endpoint created by Microsoft. When enabled, a private link is exclusively used for all communications by the database import/export process, the Azure SQL database, and related Azure Storage services. A service managed private endpoint is a private IP address within a specific virtual network and subnet.
40
+
The database import/export private link is a service managed private endpoint created by Microsoft. When you enable the **Use private link** option during import or export, the service automatically creates private endpoints to facilitate secure communication between the database import/export process, your Azure SQL database, and the Azure Storage service.
41
+
42
+
These service-managed private endpoints are created within the same virtual network and subnet where your existing Azure SQL logical server private endpoint is located. The endpoints receive private IP addresses from that subnet's address space and must be manually approved before the import/export operation can proceed.
43
+
44
+
> [!IMPORTANT]
45
+
> If your Azure SQL logical server or Storage account already has private endpoints configured, the import/export service will create **additional** service-managed private endpoints specifically for the import/export operation. These are separate from your existing private endpoints and require separate approval.
31
46
32
47
The private endpoint must be manually approved for both the Azure SQL logical server and the Azure Blob storage account, in separate steps, with details included in this tutorial.
33
48
@@ -37,6 +52,9 @@ The private endpoint must be manually approved for both the Azure SQL logical se
37
52
38
53
Import/Export Private Link can be configured via Azure portal, PowerShell, or using REST API.
39
54
55
+
> [!NOTE]
56
+
> The service automatically creates private endpoints in the same virtual network and subnet as your Azure SQL logical server's existing private endpoint. You don't need to manually specify the VNet or subnet during the import/export process. If your SQL server doesn't have a private endpoint configured, you must set one up before using import/export with Private Link.
57
+
40
58
### 1. Configure Import/Export private link using the Azure portal
41
59
42
60
<aid="create-import-private-link"></a>
@@ -53,7 +71,7 @@ You need to enable and approve the import private link. Creating the private lin
53
71
54
72
<aid="create-export-private-link"></a>
55
73
56
-
#### Enable Export private link
74
+
#### Enable export private link
57
75
58
76
You need to enable and approve the export private link. Creating the private link is performed automatically in Azure.
59
77
@@ -65,6 +83,9 @@ You need to enable and approve the export private link. Creating the private lin
65
83
66
84
The new private endpoint must be approved by the user in the Private Link Center or in the Azure SQL Database, or you can approve both private links individually in their respective Azure portal locations.
67
85
86
+
> [!TIP]
87
+
> If you already have private endpoints configured for your Azure SQL logical server and Storage account, you'll see the new service-managed private endpoints appear as **pending connections**. These are specifically for the import/export operation and are separate from your existing private endpoints. Look for private endpoints with names indicating they were created by the import/export service.
88
+
68
89
#### Option 1: Approve private endpoints in Private Link Center in Azure portal
69
90
70
91
1. Navigate to the Private Link Center in the Azure portal. In the Azure search box, search for "Private Link". Select **Private Link**.
@@ -111,6 +132,8 @@ The new private endpoint must be approved by the user in the Private Link Center
111
132
112
133
## Configure import/export private link using PowerShell
113
134
135
+
When using PowerShell, the service-managed private endpoints are automatically created in the same virtual network and subnet as your Azure SQL logical server's existing private endpoint. Ensure your SQL server has private endpoint connectivity configured before running these commands.
136
+
114
137
### Import a database using private link in PowerShell
115
138
116
139
Use the [New-AzSqlDatabaseImport](/PowerShell/module/az.sql/new-azsqldatabaseimport) cmdlet to submit an import database request to Azure. Depending on database size, the import might take some time to complete. The DTU-based provisioning model supports select database max size values for each tier. When importing a database, [use the supported edition and service objective values for Azure SQL Database](/sql/t-sql/statements/create-database-transact-sql?view=azuresqldb-current&preserve-view=true#create-a-database).
0 commit comments