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/data-share-troubleshoot.md
+15-12Lines changed: 15 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,18 +6,18 @@ author: sidontha
6
6
ms.author: sidontha
7
7
ms.service: data-share
8
8
ms.topic: troubleshooting
9
-
ms.date: 11/30/2022
9
+
ms.date: 12/19/2023
10
10
---
11
11
12
-
# Troubleshoot common problems in Azure Data Share
12
+
# Troubleshoot common problems in Azure Data Share
13
13
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.
15
15
16
-
## Azure Data Share invitations
16
+
## Azure Data Share invitations
17
17
18
18
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:
19
19
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.
21
21
22
22
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.
23
23
@@ -31,7 +31,7 @@ In some cases, when new users select **Accept Invitation** in an email invitatio
31
31
32
32
***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.
33
33
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.
35
35
36
36
## Creating and receiving shares
37
37
@@ -43,18 +43,19 @@ The following errors might appear when you create a new share, add datasets, or
43
43
* You don't have proper permissions to x.
44
44
* We couldn't add write permissions for the Azure Data Share account to one or more of your selected resources.
45
45
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).
47
47
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.
49
49
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.
51
51
52
52
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.
53
53
54
54
SQL-based sharing requires extra permissions. For information about prerequisites, see [Share from SQL sources](how-to-share-from-sql.md).
55
55
56
56
## 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.
58
59
59
60
Snapshots commonly fail for these reasons:
60
61
@@ -87,17 +88,19 @@ For SQL sources, a snapshot can fail for these other reasons:
87
88
* 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.
88
89
89
90
## Update snapshot schedule
91
+
90
92
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.
91
93
92
94
## In-place sharing
95
+
93
96
Dataset mapping can fail for Azure Data Explorer clusters due to the following reasons:
94
97
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.
96
99
* The source or target Azure Data Explorer cluster is paused.
97
100
* 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.
98
101
99
102
## Next steps
100
103
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.
102
105
103
106
To learn how to receive data, continue to the [Accept and receive data](subscribe-to-data-share.md) tutorial.
Copy file name to clipboardExpand all lines: articles/data-share/disaster-recovery.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,21 +5,21 @@ author: sidontha
5
5
ms.author: sidontha
6
6
ms.service: data-share
7
7
ms.topic: how-to
8
-
ms.date: 10/27/2022
8
+
ms.date: 12/19/2023
9
9
---
10
10
# Disaster recovery for Azure Data Share
11
11
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.
13
13
14
14
## Achieving business continuity for Azure Data Share
15
15
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.
17
17
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).
19
19
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.
21
21
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.
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.
24
24
25
25

26
26
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).
31
34
32
35
## Next steps
36
+
33
37
Learn more about how to [add recipients to an existing data share](how-to-add-recipients.md).
Copy file name to clipboardExpand all lines: articles/data-share/how-to-add-recipients.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,23 +5,24 @@ author: sidontha
5
5
ms.author: sidontha
6
6
ms.service: data-share
7
7
ms.topic: how-to
8
-
ms.date: 10/27/2022
8
+
ms.date: 12/19/2023
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 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.
13
13
14
14
## Add recipient to an existing share
15
15
16
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. 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).
21
21
22
22

23
23
24
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
28
Learn more about how to [delete an invitation to a share](how-to-delete-invitation.md).
Copy file name to clipboardExpand all lines: articles/data-share/how-to-configure-mapping.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,37 +5,34 @@ author: sidontha
5
5
ms.author: sidontha
6
6
ms.service: data-share
7
7
ms.topic: how-to
8
-
ms.date: 10/27/2022
8
+
ms.date: 12/19/2023
9
9
---
10
10
# How to configure a dataset mapping for a received share in Azure Data Share
11
11
12
-
This article explains how to configure a dataset mapping for a Received Share using Azure Data Share. You may want to configure a dataset mapping to specify a target data store where you want to receive data, or if you need to change the target data store.
12
+
This article explains how to configure a dataset mapping for a received share using Azure Data Share. You might want to configure a dataset mapping to specify a target data store where you want to receive data, or if you need to change the target data store.
13
13
14
14
## Navigate to a received data share
15
15
16
-
In the Azure Data Share service, navigate to your received share and select the **Datasets** tab.
16
+
In the Azure Data Share service, navigate to your received share and select the **Datasets** tab.
Check the box next to the dataset you'd like to assign a destination to. Select **+ Map to target** to choose a new destination store. Select **Unmap** first if the dataset is already mapped and you want to change the target data store.
21
21
22
-

22
+

23
23
24
24
## Select a target store
25
25
26
-
Select a target data store type that you'd like the data to land in. For snapshot-based sharing, any data that already exists in any previously mapped storage accounts will not be automatically moved to the new target store. For in-place sharing, select a data store in the Location specified. The Location is the Azure data center where data provider's source data store is located at.
26
+
Select a target data store type that you'd like the data to land in. For snapshot-based sharing, any data that already exists in any previously mapped storage accounts won't be automatically moved to the new target store. For in-place sharing, select a data store in the Location specified. The Location is the Azure data center where data provider's source data store is located at.
Copy file name to clipboardExpand all lines: articles/data-share/how-to-delete-invitation.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,17 +5,19 @@ author: sidontha
5
5
ms.author: sidontha
6
6
ms.service: data-share
7
7
ms.topic: how-to
8
-
ms.date: 10/27/2022
8
+
ms.date: 12/19/2023
9
9
---
10
+
10
11
# How to delete an invitation to a recipient in Azure Data Share
11
12
12
-
This article explains how to delete an invitation to a recipient before they accept it. This will prevent them from creating a share subscription and they will never receive any shared data. If you delete the invitation to a consumer who has already created a share subscription, deleting their invitation won't have any impact.
13
+
This article explains how to delete an invitation to a recipient before they accept it. This prevents them from creating a share subscription and they'll never receive any shared data. If you delete the invitation to a consumer who has already created a share subscription, deleting their invitation won't have any impact. To revoke a share that's already been accepted, you can [revoke a share subscription.](how-to-revoke-share-subscription.md)
13
14
14
15
## Navigate to a sent data share
15
16
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. Click the boxes next to the recipients whose invitations you would like to delete and then click**Delete**.
17
+
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. Select the boxes next to the recipients whose invitations you would like to delete and then select**Delete**.
0 commit comments