Skip to content

Commit 3898119

Browse files
committed
Freshness check and update
1 parent dcb6431 commit 3898119

34 files changed

+194
-185
lines changed

articles/data-share/concepts-pricing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: sidontha
55
ms.author: sidontha
66
ms.service: data-share
77
ms.topic: conceptual
8-
ms.date: 11/15/2022
8+
ms.date: 12/19/2023
99
---
1010

1111
# Understand Azure Data Share pricing

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: sidontha
55
ms.author: sidontha
66
ms.service: data-share
77
ms.topic: conceptual
8-
ms.date: 12/18/2023
8+
ms.date: 12/19/2023
99
ms.custom: subject-rbac-steps
1010
---
1111

@@ -130,7 +130,7 @@ You can follow the [step by step demo video](https://youtu.be/aeGISgK1xro), or t
130130
- SQL Server Firewall access:
131131
1. In the [Azure portal](https://portal.azure.com/), navigate to the SQL server and select **Firewalls and virtual networks**.
132132
1. Select **Yes** for **Allow Azure services and resources to access this server**.
133-
1. Select **+Add client IP**. Client IP address can change, so you may need to add your client IP again next time you share data from the portal.
133+
1. Select **+Add client IP**. Client IP address can change, so you might need to add your client IP again next time you share data from the portal.
134134
1. Select **Save**.
135135
136136
For more information about sharing to and from Azure SQL, see [the article to share and receive data from Azure SQL Database.](how-to-share-from-sql.md)
@@ -156,7 +156,7 @@ For more information about sharing to and from Azure SQL, see [the article to sh
156156
- Synapse workspace Firewall access:
157157
1. In the [Azure portal](https://portal.azure.com/), navigate to Synapse workspace. Select **Firewalls** from left navigation.
158158
1. Select **ON** for **Allow Azure services and resources to access this workspace**.
159-
1. Select **+Add client IP**. Client IP address can change, so you may need to add your client IP again next time you share data from the portal.
159+
1. Select **+Add client IP**. Client IP address can change, so you might need to add your client IP again next time you share data from the portal.
160160
1. Select **Save**.
161161

162162
#### Receive
@@ -263,7 +263,7 @@ For SQL-based target, a SQL user needs to be created from an external provider i
263263

264264
## Resource provider registration
265265

266-
You may need to manually register the Microsoft.DataShare resource provider into your Azure subscription in the following scenarios:
266+
You might need to manually register the Microsoft.DataShare resource provider into your Azure subscription in the following scenarios:
267267

268268
* View Azure Data Share invitation for the first time in your Azure tenant
269269
* Share data from an Azure data store in a different Azure subscription from your Azure Data Share resource
@@ -288,7 +288,7 @@ This section describes custom roles and permissions required within the custom r
288288
* 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.
289289
* 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.
290290
* See the [Data Provider](#data-provider) and [Data Consumer](#data-consumer) sections of this article for more specific steps.
291-
* 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.
291+
* You might 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.
292292
293293
### Create custom roles and required permissions
294294

articles/data-share/data-share-troubleshoot.md

Lines changed: 15 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -6,18 +6,18 @@ author: sidontha
66
ms.author: sidontha
77
ms.service: data-share
88
ms.topic: troubleshooting
9-
ms.date: 11/30/2022
9+
ms.date: 12/19/2023
1010
---
1111

12-
# Troubleshoot common problems in Azure Data Share
12+
# Troubleshoot common problems in Azure Data Share
1313

14-
This article explains how to troubleshoot common problems in Azure Data Share.
14+
This article explains how to troubleshoot common problems in Azure Data Share.
1515

16-
## Azure Data Share invitations
16+
## Azure Data Share invitations
1717

1818
In some cases, when new users select **Accept Invitation** in an email invitation, they might see an empty list of invitations. This problem could have one of the following causes:
1919

20-
* **The Azure Data Share service isn't registered as a resource provider of any Azure subscription in the Azure tenant.** This problem happens when your Azure tenant has no Data Share resource.
20+
* **The Azure Data Share service isn't registered as a resource provider of any Azure subscription in the Azure tenant.** This problem happens when your Azure tenant has no Data Share resource.
2121

2222
When you create an Azure Data Share resource, it automatically registers the resource provider in your Azure subscription. You can manually register the Data Share service by using the following steps. To complete these steps, you need the [Contributor role](../role-based-access-control/built-in-roles.md#contributor) for the Azure subscription.
2323

@@ -31,7 +31,7 @@ In some cases, when new users select **Accept Invitation** in an email invitatio
3131

3232
* **The invitation is already accepted.** The link in the email takes you to the **Data Share Invitations** page in the Azure portal. This page lists only pending invitations. Accepted invitations don't appear on the page. To view received shares and configure your target Azure Data Explorer cluster setting, go to the Data Share resource you used to accept the invitation.
3333

34-
* **You are guest user of the tenant.** If you're a guest user of the tenant, you'll need to verify your email address for the tenant prior to viewing the invitation. Once verified, it's valid for 12 months.
34+
* **You are guest user of the tenant.** If you're a guest user of the tenant, you'll need to verify your email address for the tenant prior to viewing the invitation. Once verified, it's valid for 12 months.
3535

3636
## Creating and receiving shares
3737

@@ -43,18 +43,19 @@ The following errors might appear when you create a new share, add datasets, or
4343
* You don't have proper permissions to x.
4444
* We couldn't add write permissions for the Azure Data Share account to one or more of your selected resources.
4545

46-
You might see one of these errors if you have insufficient permissions to the Azure data store. For more information, see [Roles and requirements](concepts-roles-permissions.md).
46+
You might see one of these errors if you have insufficient permissions to the Azure data store. For more information, see [Roles and requirements](concepts-roles-permissions.md).
4747

48-
You need the write permission to share or receive data from an Azure data store. This permission is typically part of the Contributor role.
48+
You need the write permission to share or receive data from an Azure data store. This permission is typically part of the Contributor role.
4949

50-
If you're sharing data or receiving data from the Azure data store for the first time, you also need the *Microsoft.Authorization/role assignments/write* permission. This permission is typically part of the Owner role. Even if you created the Azure data store resource, you're not necessarily the owner of the resource.
50+
If you're sharing data or receiving data from the Azure data store for the first time, you also need the *Microsoft.Authorization/role assignments/write* permission. This permission is typically part of the Owner role. Even if you created the Azure data store resource, you're not necessarily the owner of the resource.
5151

5252
When you have the proper permissions, the Azure Data Share service automatically allows the data share resource's managed identity to access the data store. This process can take a few minutes. If you experience failure because of this delay, try again after a few minutes.
5353

5454
SQL-based sharing requires extra permissions. For information about prerequisites, see [Share from SQL sources](how-to-share-from-sql.md).
5555

5656
## Snapshots
57-
A snapshot can fail for various reasons. Open a detailed error message by selecting the start time of the snapshot and then the status of each dataset.
57+
58+
A snapshot can fail for various reasons. Open a detailed error message by selecting the start time of the snapshot and then the status of each dataset.
5859

5960
Snapshots commonly fail for these reasons:
6061

@@ -87,17 +88,19 @@ For SQL sources, a snapshot can fail for these other reasons:
8788
* A target CSV file is generated, but the data can't be read in Excel. You might see this problem when the source SQL table contains data that includes non-English characters. In Excel, select the **Get Data** tab and choose the CSV file. Select the file origin **65001: Unicode (UTF-8)**, and then load the data.
8889

8990
## Update snapshot schedule
91+
9092
After the data provider updates the snapshot schedule for the sent share, the data consumer needs to disable the previous snapshot schedule, then enable the updated snapshot schedule for the received share. Snapshot schedule is stored in UTC, and shown in the UI as the computer local time. It doesn't automatically adjust for daylight saving time.
9193
9294
## In-place sharing
95+
9396
Dataset mapping can fail for Azure Data Explorer clusters due to the following reasons:
9497
95-
* User doesn't have *write* permission to the Azure Data Explorer cluster. This permission is typically part of the Contributor role.
98+
* User doesn't have *write* permission to the Azure Data Explorer cluster. This permission is typically part of the Contributor role.
9699
* The source or target Azure Data Explorer cluster is paused.
97100
* Source Azure Data Explorer cluster is EngineV2 and target is EngineV3, or vice versa. Sharing between Azure Data Explorer clusters of different engine versions isn't supported.
98101
99102
## Next steps
100103
101-
To learn how to start sharing data, continue to the [Share data](share-your-data.md) tutorial.
104+
To learn how to start sharing data, continue to the [Share data](share-your-data.md) tutorial.
102105
103106
To learn how to receive data, continue to the [Accept and receive data](subscribe-to-data-share.md) tutorial.

articles/data-share/disaster-recovery.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,21 +5,21 @@ author: sidontha
55
ms.author: sidontha
66
ms.service: data-share
77
ms.topic: how-to
8-
ms.date: 10/27/2022
8+
ms.date: 12/19/2023
99
---
1010
# Disaster recovery for Azure Data Share
1111

12-
This article explains how to configure a disaster recovery environment for Azure Data Share. Azure data center outages are rare, but can last anywhere from a few minutes to hours. Data Center outages can cause disruption to environments that are relying on data being shared by the data provider. By following the steps detailed in this article, data providers can continue to share data with their data consumers in the event of a data center outage for the primary region hosting your data share.
12+
This article explains how to configure a disaster recovery environment for Azure Data Share. Azure data center outages are rare, but can last anywhere from a few minutes to hours. Data Center outages can cause disruption to environments that are relying on data being shared by the data provider. By following the steps detailed in this article, data providers can continue to share data with their data consumers if there's a data center outage for the primary region hosting your data share.
1313

1414
## Achieving business continuity for Azure Data Share
1515

16-
To be prepared for a data center outage, the data provider can have a data share environment provisioned in a secondary region. Measures can be taken to ensure a smooth failover in the event that a data center outage does occur.
16+
To be prepared for a data center outage, the data provider can have a data share environment provisioned in a secondary region. Measures can be taken to ensure a smooth failover if a data center outage does occur.
1717

18-
Data providers can provision secondary Azure Data Share resources in an additional region. These Data Share resources can be configured to include shares and datasets that exist in the primary Azure Data Share resource. They can invite data consumers to the secondary shares when configuring the DR environment or at a later time (i.e as part of manual failover steps).
18+
Data providers can create secondary Azure Data Share resources in another region. These Data Share resources can be configured to include shares and datasets that exist in the primary Azure Data Share resource. They can invite data consumers to the secondary shares when configuring the DR environment or at a later time (i.e as part of manual failover steps).
1919

20-
If the data consumers have active share subscriptions in a secondary environment provisioned for DR purposes, they can enable snapshot schedule as part of failover. If the data consumers do not want to subscribe to a secondary region for DR purposes, they can be invited into the secondary share at a later time.
20+
If the data consumers have active share subscriptions in a secondary environment provisioned for DR purposes, they can enable snapshot schedule as part of failover. If the data consumers don't want to subscribe to a secondary region for DR purposes, they can be invited into the secondary share at a later time.
2121

22-
Data consumers can either have an active share subscription that is idle for DR purposes, or data providers can invite them at a later time as part of manual failover procedures.
22+
Data consumers can either have an active share subscription that is idle for DR purposes, or data providers can invite them at a later time as part of manual failover procedures.
2323

2424
## Related information
2525

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

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: sidontha
55
ms.author: sidontha
66
ms.service: data-share
77
ms.topic: how-to
8-
ms.date: 10/27/2022
8+
ms.date: 12/19/2023
99
---
1010

1111
# How to add datasets to an existing share in Azure Data Share
@@ -16,18 +16,22 @@ For information on how to add datasets as you create a share, see the [Share dat
1616

1717
## Navigate to a sent data share
1818

19-
In Azure Data Share, navigate to your sent share and select the **Datasets** tab. Click **+ Add Datasets** button to add more datasets.
19+
In Azure Data Share, navigate to your sent share and select the **Datasets** tab. Select **+ Add Datasets** button to add more datasets.
2020

2121
![Screenshot shows Add Datasets selected.](./media/how-to/how-to-add-datasets/add-datasets.png)
2222

23-
In the panel on the right, select the dataset type you would like to add and then click **Next**. Select the subscription and resource group of the data you would like to add. Using the dropdown arrows, find and then check the box next to the data to add.
23+
In the panel on the right, select the dataset type you would like to add and then select **Next**. Select the subscription and resource group of the data you would like to add. Using the dropdown arrows, find and then check the box next to the data to add.
2424

2525
![Screenshot shows the Add Blob Storage pane where you can select data.](./media/how-to/how-to-add-datasets/add-datasets-side.png)
2626

27-
Once you click **Add Datasets**, the datasets will be added to your share.
28-
Note: A snapshot must be triggered by your consumers in order for them to see the new datasets. If there are snapshot settings configured, consumers will see the new datasets once the next scheduled snapshot completes.
29-
Without snapshot settings configured, the consumer must manually trigger a full or incremental copy of the data to receive the updates.
30-
For more information on snapshots, see [Snapshots](terminology.md).
27+
Once you select **Add Datasets**, the datasets are added to your share.
28+
29+
>[!NOTE]
30+
>A snapshot must be triggered by your consumers in order for them to see the new datasets. If there are snapshot settings configured, consumers will see the new datasets once the next scheduled snapshot completes.
31+
32+
Without snapshot settings configured, the consumer must manually trigger a full or incremental copy of the data to receive the updates.
33+
For more information on snapshots, see [Snapshots](terminology.md#snapshot).
3134

3235
## Next steps
36+
3337
Learn more about how to [add recipients to an existing data share](how-to-add-recipients.md).

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

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,23 +5,24 @@ author: sidontha
55
ms.author: sidontha
66
ms.service: data-share
77
ms.topic: how-to
8-
ms.date: 10/27/2022
8+
ms.date: 12/19/2023
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 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.
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

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

2424
Select **Add and send invitation**. The new recipient(s) will be sent invitation emails to this share.
2525

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

0 commit comments

Comments
 (0)