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/data-share/concepts-roles-permissions.md
+14-13Lines changed: 14 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: jifems
5
5
ms.author: jife
6
6
ms.service: data-share
7
7
ms.topic: conceptual
8
-
ms.date: 03/24/2021
8
+
ms.date: 02/07/2022
9
9
---
10
10
11
11
# Roles and requirements for Azure Data Share
@@ -20,7 +20,7 @@ To share or receive data from an Azure data store, user needs at least the follo
20
20
21
21
* Permission to write to the Azure data store. Typically, this permission exists in the **Contributor** role.
22
22
23
-
For storage and data lake snapshot-based sharing, you also need permission to create role assignment in the Azure data store. Typically, permission to create role assignments exists in the **Owner** role, User Access Administrator role, or a custom role with *Microsoft.Authorization/role assignments/write* permission assigned. This permission is not required if the data share resource's managed identity is already granted access to the Azure data store. Below is a summary of the roles assigned to Data Share resource's managed identity:
23
+
For storage and data lake snapshot-based sharing, you also need permission to create role assignment in the Azure data store. Typically, permission to create role assignments exists in the **Owner** role, User Access Administrator role, or a custom role with *Microsoft.Authorization/role assignments/write* permission assigned. This permission isn't required if the data share resource's managed identity is already granted access to the Azure data store. Below is a summary of the roles assigned to Data Share resource's managed identity:
24
24
25
25
|**Data Store Type**|**Data Provider Source Data Store**|**Data Consumer Target Data Store**|
26
26
|---|---|---|
@@ -38,7 +38,7 @@ For SQL snapshot-based sharing, a SQL user needs to be created from an external
38
38
|
39
39
40
40
### Data provider
41
-
For storage and data lake snapshot-based sharing, to add a dataset in Azure Data Share, provider data share resource's managed identity needs to be granted access to the source Azure data store. For example, in the case of storage account, the data share resource's managed identity is granted the *Storage Blob Data Reader* role. This is done automatically by the Azure Data Share service when user is adding dataset via Azure portal and the user has the proper permission. For example, user is an owner of the Azure data store, or is a member of a custom role that has the *Microsoft.Authorization/role assignments/write* permission assigned.
41
+
For storage and data lake snapshot-based sharing, to add a dataset in Azure Data Share, provider data share resource's managed identity needs to be granted access to the source Azure data store. For example, if using a storage account, the data share resource's managed identity is granted the *Storage Blob Data Reader* role. This is done automatically by the Azure Data Share service when user is adding dataset via Azure portal and the user has the proper permission. For example, user is an owner of the Azure data store, or is a member of a custom role that has the *Microsoft.Authorization/role assignments/write* permission assigned.
42
42
43
43
Alternatively, user can have owner of the Azure data store add the data share resource's managed identity to the Azure data store manually. This action only needs to be performed once per data share resource. To create a role assignment for the data share resource's managed identity manually, follow the below steps.
44
44
@@ -47,14 +47,14 @@ Alternatively, user can have owner of the Azure data store add the data share re
47
47
1. Select **Add a role assignment**.
48
48
1. Under *Role*, select the role in the role assignment table above (for example, for storage account, select *Storage Blob Data Reader*).
49
49
1. Under *Select*, type in the name of your Azure Data Share resource.
50
-
1.Click*Save*.
50
+
1.Select*Save*.
51
51
52
-
To learn more about role assignment, refer to [Assign Azure roles using the Azure portal](../role-based-access-control/role-assignments-portal.md). If you are sharing data using REST APIs, you can create role assignment using API by referencing [Assign Azure roles using the REST API](../role-based-access-control/role-assignments-rest.md).
52
+
To learn more about role assignment, refer to [Assign Azure roles using the Azure portal](../role-based-access-control/role-assignments-portal.md). If you're sharing data using REST APIs, you can create role assignment using API by referencing [Assign Azure roles using the REST API](../role-based-access-control/role-assignments-rest.md).
53
53
54
54
For SQL snapshot-based sharing, a SQL user needs to be created from an external provider in SQL Database with the same name as the Azure Data Share resource while connecting to SQL database using Azure Active Directory authentication. This user needs to be granted *db_datareader* permission. A sample script along with other prerequisites for SQL-based sharing can be found in the [Share from Azure SQL Database or Azure Synapse Analytics](how-to-share-from-sql.md) tutorial.
55
55
56
56
### Data consumer
57
-
To receive data into storage account, consumer data share resource's managed identity needs to be granted access to the target storage account. The data share resource's managed identity needs to be granted the *Storage Blob Data Contributor* role. This is done automatically by the Azure Data Share service if the user specifies a target storage account via Azure portal and the user has proper permission. For example, user is an owner of the storage account, or is a member of a custom role which has the *Microsoft.Authorization/role assignments/write* permission assigned.
57
+
To receive data into storage account, consumer data share resource's managed identity needs to be granted access to the target storage account. The data share resource's managed identity needs to be granted the *Storage Blob Data Contributor* role. This is done automatically by the Azure Data Share service if the user specifies a target storage account via Azure portal and the user has proper permission. For example, user is an owner of the storage account, or is a member of a custom role that has the *Microsoft.Authorization/role assignments/write* permission assigned.
58
58
59
59
Alternatively, user can have owner of the storage account add the data share resource's managed identity to the storage account manually. This action only needs to be performed once per data share resource. To create a role assignment for the data share resource's managed identity manually, follow the below steps.
60
60
@@ -63,9 +63,9 @@ Alternatively, user can have owner of the storage account add the data share res
63
63
1. Select **Add a role assignment**.
64
64
1. Under *Role*, select the role in the role assignment table above (for example, for storage account, select *Storage Blob Data Reader*).
65
65
1. Under *Select*, type in the name of your Azure Data Share resource.
66
-
1.Click*Save*.
66
+
1.Select*Save*.
67
67
68
-
To learn more about role assignment, refer to [Assign Azure roles using the Azure portal](../role-based-access-control/role-assignments-portal.md). If you are receiving data using REST APIs, you can create role assignment using API by referencing [Assign Azure roles using the REST API](../role-based-access-control/role-assignments-rest.md).
68
+
To learn more about role assignment, refer to [Assign Azure roles using the Azure portal](../role-based-access-control/role-assignments-portal.md). If you're receiving data using REST APIs, you can create role assignment using API by referencing [Assign Azure roles using the REST API](../role-based-access-control/role-assignments-rest.md).
69
69
70
70
For SQL-based target, a SQL user needs to be created from an external provider in SQL Database with the same name as the Azure Data Share resource while connecting to SQL database using Azure Active Directory authentication. This user needs to be granted *db_datareader, db_datawriter, db_ddladmin* permission. A sample script along with other prerequisites for SQL-based sharing can be found in the [Share from Azure SQL Database or Azure Synapse Analytics](how-to-share-from-sql.md) tutorial.
71
71
@@ -81,26 +81,27 @@ Follow these steps to register the Microsoft.DataShare resource provider into yo
81
81
82
82
1. In the Azure portal, navigate to **Subscriptions**.
83
83
1. Select the subscription that you're using for Azure Data Share.
84
-
1.Click on **Resource Providers**.
84
+
1.Select on **Resource Providers**.
85
85
1. Search for Microsoft.DataShare.
86
-
1.Click**Register**.
86
+
1.Select**Register**.
87
87
88
88
To learn more about resource provider, refer to [Azure resource providers and types](../azure-resource-manager/management/resource-providers-and-types.md).
89
89
90
90
## Custom roles for Data Share
91
91
This section describes custom roles and permissions required within the custom roles for sharing and receiving data, specific to a Storage account. There are also pre-requisites that are independent of custom role or Azure Data Share role.
92
92
93
93
### Pre-requisites for Data Share, in addition to custom role
94
-
* For storage and data lake snapshot-based sharing, to add a dataset in Azure Data Share, the provider data share resource's managed identity needs to be granted access to the source Azure data store. For example, in the case of a storage account, the data share resource's managed identity is granted the Storage Blob Data Reader role.
94
+
95
+
* For storage and data lake snapshot-based sharing, to add a dataset in Azure Data Share, the provider data share resource's managed identity needs to be granted access to the source Azure data store. For example, if using a storage account, the data share resource's managed identity is granted the Storage Blob Data Reader role.
95
96
* To receive data into a storage account, the consumer data share resource's managed identity needs to be granted access to the target storage account. The data share resource's managed identity needs to be granted the Storage Blob Data Contributor role.
96
97
* See the [Data Provider](#data-provider) and [Data Consumer](#data-consumer) sections of this article for more specific steps.
97
98
* You may also need to manually register the Microsoft.DataShare resource provider into your Azure subscription for some scenarios. See in [Resource provider registration](#resource-provider-registration) section of this article for specific details.
98
99
99
100
### Create custom roles and required permissions
100
101
Custom roles can be created in a subscription or resource group for sharing and receiving data. Users and groups can then be assigned the custom role.
101
102
102
-
* For creating a custom role, there are actions required for Storage, Data Share, Resources group, and Authorization. Please see the [Azure resource provider operations document](../role-based-access-control/resource-provider-operations.md#microsoftdatashare) for Data Share to understand the different levels of permissions and choose the ones relevant for your custom role.
103
-
* Alternately, you can use the Azure Portal to navigate to IAM, Custom role, Add permissions, Search, search for Microsoft.DataShare permissions to see the list of actions available.
103
+
* For creating a custom role, there are actions required for Storage, Data Share, Resources group, and Authorization. See the [Azure resource provider operations document](../role-based-access-control/resource-provider-operations.md#microsoftdatashare) for Data Share to understand the different levels of permissions and choose the ones relevant for your custom role.
104
+
* Alternately, you can use the Azure portal to navigate to IAM, Custom role, Add permissions, Search, search for Microsoft.DataShare permissions to see the list of actions available.
104
105
* To learn more about custom role assignment, refer to [Azure custom roles](../role-based-access-control/custom-roles.md). Once you have your custom role, test it to verify that it works as you expect.
105
106
106
107
The following shows an example of how the required actions will be listed in JSON view for a custom role to share and receive data.
Copy file name to clipboardExpand all lines: articles/data-share/how-to-add-recipients.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,23 +5,23 @@ author: jifems
5
5
ms.author: jife
6
6
ms.service: data-share
7
7
ms.topic: how-to
8
-
ms.date: 12/17/2020
8
+
ms.date: 02/07/2022
9
9
---
10
10
# How to add a recipient to your share
11
11
12
-
You can add recipient when you create a new share or to an existing share. From Azure Data Share UI, you can add recipient using the Azure login email of the user. From API, you can use a combination of user/service principal and tenant ID. When a tenant ID is specified, the invitation can only be accepted into this tenant. Also from API, you can create an invitation without sending an email to the recipient.
12
+
You can add recipient when you create a new share or to an existing share. From Azure Data Share UI, you can add recipient using the Azure sign-in email of the user. From API, you can use a combination of user/service principal and tenant ID. When a tenant ID is specified, the invitation can only be accepted into this tenant. Also from API, you can create an invitation without sending an email to the recipient.
13
13
14
14
## Add recipient to an existing share
15
15
16
-
In Azure Data Share, navigate to your sent share and select the **Invitations** tab. Listed here are all of the recipients of invitations to this data share. To add a new one, click**Add Recipient**.
16
+
In Azure Data Share, navigate to your sent share and select the **Invitations** tab. Listed here are all of the recipients of invitations to this data share. To add a new one, select**Add Recipient**.
A panel will pop out on the right side of the page. Click**Add Recipient** and then fill in the email of your new recipient on the blank line. Make sure to use recipient's Azure login email (using their email alias won't work).
20
+
A panel will pop out on the right side of the page. Select**Add Recipient** and then fill in the email of your new recipient on the blank line. Make sure to use recipient's Azure sign-in email (using their email alias won't work).
21
21
22
22

23
23
24
-
Click**Add and send invitation**. The new recipient(s) will be sent invitation emails to this share.
24
+
Select**Add and send invitation**. The new recipient(s) will be sent invitation emails to this share.
25
25
26
26
## Next steps
27
27
Learn more about how to [delete an invitation to a share](how-to-delete-invitation.md).
0 commit comments