Skip to content

Commit 5d81358

Browse files
authored
Merge pull request #187698 from whhender/update-share-dates
Updating Dates
2 parents 5ecde31 + e44ce56 commit 5d81358

File tree

4 files changed

+37
-36
lines changed

4 files changed

+37
-36
lines changed

articles/data-share/concepts-roles-permissions.md

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: jifems
55
ms.author: jife
66
ms.service: data-share
77
ms.topic: conceptual
8-
ms.date: 03/24/2021
8+
ms.date: 02/07/2022
99
---
1010

1111
# 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
2020

2121
* Permission to write to the Azure data store. Typically, this permission exists in the **Contributor** role.
2222

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:
2424

2525
|**Data Store Type**|**Data Provider Source Data Store**|**Data Consumer Target Data Store**|
2626
|---|---|---|
@@ -38,7 +38,7 @@ For SQL snapshot-based sharing, a SQL user needs to be created from an external
3838
|
3939

4040
### 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.
4242

4343
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.
4444

@@ -47,14 +47,14 @@ Alternatively, user can have owner of the Azure data store add the data share re
4747
1. Select **Add a role assignment**.
4848
1. Under *Role*, select the role in the role assignment table above (for example, for storage account, select *Storage Blob Data Reader*).
4949
1. Under *Select*, type in the name of your Azure Data Share resource.
50-
1. Click *Save*.
50+
1. Select *Save*.
5151

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).
5353

5454
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.
5555

5656
### 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.
5858

5959
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.
6060

@@ -63,9 +63,9 @@ Alternatively, user can have owner of the storage account add the data share res
6363
1. Select **Add a role assignment**.
6464
1. Under *Role*, select the role in the role assignment table above (for example, for storage account, select *Storage Blob Data Reader*).
6565
1. Under *Select*, type in the name of your Azure Data Share resource.
66-
1. Click *Save*.
66+
1. Select *Save*.
6767

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).
6969

7070
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.
7171

@@ -81,26 +81,27 @@ Follow these steps to register the Microsoft.DataShare resource provider into yo
8181

8282
1. In the Azure portal, navigate to **Subscriptions**.
8383
1. Select the subscription that you're using for Azure Data Share.
84-
1. Click on **Resource Providers**.
84+
1. Select on **Resource Providers**.
8585
1. Search for Microsoft.DataShare.
86-
1. Click **Register**.
86+
1. Select **Register**.
8787

8888
To learn more about resource provider, refer to [Azure resource providers and types](../azure-resource-manager/management/resource-providers-and-types.md).
8989

9090
## Custom roles for Data Share
9191
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.
9292

9393
### 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.
9596
* 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.
9697
* See the [Data Provider](#data-provider) and [Data Consumer](#data-consumer) sections of this article for more specific steps.
9798
* 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.
9899

99100
### Create custom roles and required permissions
100101
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.
101102

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.
104105
* 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.
105106

106107
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.

articles/data-share/how-to-add-recipients.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,23 +5,23 @@ author: jifems
55
ms.author: jife
66
ms.service: data-share
77
ms.topic: how-to
8-
ms.date: 12/17/2020
8+
ms.date: 02/07/2022
99
---
1010
# How to add a recipient to your share
1111

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.
1313

1414
## Add recipient to an existing share
1515

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**.
1717

1818
![Screenshot shows Add Recipient selected.](./media/how-to/how-to-add-recipients/add-recipient.png)
1919

20-
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).
2121

2222
![Screenshot shows the Add Recipient pane where you can Add and send invitation.](./media/how-to/how-to-add-recipients/add-recipient-side.png)
2323

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.
2525

2626
## Next steps
2727
Learn more about how to [delete an invitation to a share](how-to-delete-invitation.md).

0 commit comments

Comments
 (0)