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
Copy file name to clipboardExpand all lines: articles/synapse-analytics/sql/tutorial-load-data-using-entra-id.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,35 +11,35 @@ ms.author: periclesrocha
11
11
ms.reviewer: WilliamDAssafMSFT
12
12
---
13
13
14
-
# Tutorial: load data using EntraID
14
+
# Tutorial: load data using Entra ID
15
15
16
16
Applies to: Azure Synapse Analytics
17
17
18
-
This article explains how to create external tables using EntraID passthrough.
18
+
This article explains how to create external tables using Entra ID passthrough.
19
19
20
20
## Prerequisites:
21
21
22
-
This tutorial requires the following resources to be in place:
22
+
The following resources are required to complete this tutorial:
23
23
24
24
* An Azure Synapse Analytics workspace and a dedicated SQL Pool
25
25
26
-
## Give the EntraID account access to the storage account
26
+
## Give the Entra ID account access to the storage account
27
27
28
-
This examples uses an EntraID account (or group) to authenticate to the source data.
28
+
This example uses an Entra ID account (or group) to authenticate to the source data.
29
29
30
-
To enable access to data on ADLS Gen2 accounts, you need to give your EntraID account (or group) access to the source account. To grant the proper permissions, follow these steps:
30
+
To enable access to data on Azure Data Lake Storage (ADLS) Gen2 accounts, you need to give your Entra ID account (or group) access to the source account. To grant the proper permissions, follow these steps:
31
31
32
-
1. In the Azure Portal, find your storage account.
32
+
1. In the Azure portal, find your storage account.
33
33
2. Select **Data storage -> Containers**, and navigate to the folder where the source data the external table needs access to is.
34
34
3. Select **Access control (IAM)**.
35
35
4. Select **Add -> Add role assignment**.
36
36
5. In the list of job function roles, select **Storage Blob Data Reader** and select **Next**.
37
-
6. In the Add role assignment page, select **+ Select members**. The Select members pane opens in the right-hand corner.
38
-
7. Type the name of the desired EntraID account or group until it is displayed. Pick your desired EntraID account and chose **Select**.
39
-
8.Back to the Add role assignment page, make sure the list of Members include your desired EntraID account. Once verified, select **Review + assign**.
37
+
6. In the Add role assignment page, select **+ Select members**. The **Select members** pane opens in the right-hand corner.
38
+
7. Type the name of the desired Entra ID account. When displayed, pick your desired Entra ID account and chose **Select**.
39
+
8.In the the **Add role assignment** page, make sure the list of Members include your desired Entra ID account. Once verified, select **Review + assign**.
40
40
9. In the confirmation page, review the changes and select **Review + assign**.
41
41
42
-
The EntraID account or group is now a member of the Storage Blob Data Reader role and has access to the source folder.
42
+
The Entra ID account or group is now a member of the Storage Blob Data Reader role and has access to the source folder.
43
43
44
44
# Create the required database objects
45
45
@@ -49,7 +49,7 @@ External tables require the following objects to be created:
49
49
2. An external file format that defines the format of the source files.
50
50
3. An external table definition that is used for queries.
51
51
52
-
To follow these steps, you will need to use the SQL editor in the Azure Synapse Workspace, or your preferred SQL client connected to your dedicated SQL Pool. Let’s look at these steps in detail.
52
+
To follow these steps, you need to use the SQL editor in the Azure Synapse Workspace, or your preferred SQL client connected to your dedicated SQL Pool. Let’s look at these steps in detail.
53
53
54
54
### Create the external data source
55
55
@@ -97,11 +97,11 @@ Where:
97
97
98
98
* \<FileFormatName> is the name you want to use for your external file format
99
99
100
-
In the example above, adjust parameters such as FIELD\_TERMINATOR, STRING\_DELIMITER, FIRST\_ROW and others as needed in accordance with your source data. For more formatting options and to learn more about EXTERNAL FILE FORMAT, visit <https://learn.microsoft.com/en-us/sql/t-sql/statements/create-external-file-format-transact-sql?view=azure-sqldw-latest&tabs=delimited>.
100
+
In this example, adjust parameters such as FIELD_TERMINATOR, STRING_DELIMITER, FIRST_ROW and others as needed in accordance with your source data. For more formatting options and to learn more about EXTERNAL FILE FORMAT, visit <https://learn.microsoft.com/en-us/sql/t-sql/statements/create-external-file-format-transact-sql?view=azure-sqldw-latest&tabs=delimited>.
101
101
102
102
### Create the external table
103
103
104
-
Now that we’ve created all the necessary objects that hold the metadata to securely access external data, it is time to create the external table. To create the external table, use the following command:
104
+
Now that the necessary objects that hold the metadata to securely access external data are created, it's time to create the external table. To create the external table, use the following command:
105
105
106
106
```sql
107
107
-- Adjust the table name and columns to your desired name and external table schema
@@ -127,7 +127,7 @@ Where:
127
127
128
128
Make sure to adjust the table name and schema to the desired name and the schema of the data in your source files.
129
129
130
-
At this point, all the metadata required to access the external table has been created. To test your external table, use a simple query such as the one below:
130
+
At this point, all the metadata required to access the external table are created. To test your external table, use a query such as the following one to validate your work:
0 commit comments