Skip to content

Commit d4344a3

Browse files
authored
Merge pull request #294536 from whhender/data-share-freshness-2025-2
Freshness and formatting 2025 2
2 parents d4170c2 + 858bbc4 commit d4344a3

8 files changed

+28
-27
lines changed

articles/data-share/how-to-monitor.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,14 @@ author: sidontha
55
ms.author: sidontha
66
ms.service: azure-data-share
77
ms.topic: how-to
8-
ms.date: 02/29/2024
8+
ms.date: 02/12/2025
99
---
1010

1111
# Monitor Azure Data Share status and history
1212

1313
This article explains how you can monitor your Azure Data Share status and history.
1414

15-
- As a data provider, you can monitor various aspects of your data sharing relationships. Details such as whether your data consumers have accepted your invitation to the data share, and whether they have created a share subscription and started to use your data, are all available to monitor.
15+
- As a data provider, you can monitor various aspects of your data sharing relationships. Details such as whether your data consumers accepted your invitation to the data share, and whether they created a share subscription and started to use your data, are all available to monitor.
1616

1717
- As a data consumer, you can monitor the snapshots that have been triggered into your Azure subscription.
1818

@@ -27,27 +27,27 @@ View the status of your data share invitations by navigating to Sent shares -> I
2727
There are three states that your invitation can be in:
2828

2929
* Pending - Data share recipient hasn't yet accepted the invitation.
30-
* Accepted - Data share recipient has accepted the invitation.
31-
* Rejected - Data share recipient has rejected the invitation.
30+
* Accepted - Data share recipient accepted the invitation.
31+
* Rejected - Data share recipient rejected the invitation.
3232

3333
> [!IMPORTANT]
34-
> If you delete an invitation after it has already been accepted, it is not equivalent to revoking access. If you would like to stop future snapshots from being copied into your data consumers storage account, you must revoke access through the *Share subscriptions* tab.
34+
> If you delete an invitation after it was accepted, it isn't equivalent to revoking access. If you would like to stop future snapshots from being copied into your data consumers storage account, you must revoke access through the *Share subscriptions* tab.
3535
3636
## Monitor share subscriptions
3737

3838
View the status of your share subscriptions by navigating to Sent Shares -> Share Subscriptions. This will give you details about active subscriptions created by your data consumers after accepting your invitation. You can stop future updates to your data consumer by selecting the share subscription and selecting *Revoke*.
3939

4040
## Snapshot history
4141

42-
In the **History** tab of a share, you're able to view when data is copied from data provider to data consumer's data store. You're able to monitor the frequency, duration and status of each snapshot.
42+
In the **History** tab of a share, you're able to view when data is copied from data provider to data consumer's data store. You're able to monitor the frequency, duration, and status of each snapshot.
4343

4444
![Screenshot shows Sent Shares in the Azure portal.](./media/sent-shares.png "Snapshot history")
4545

4646
You can view more details about each snapshot run by selecting the run start date. Then select on the status for each dataset to view the amount of data transferred, number of files/records copied, duration of the snapshot, number of vCores used and error message if there's any.
4747

4848
Up to 30 days of snapshot history is displayed. If you need to save and see more than 30 days worth of history, you can use diagnostic setting.
4949

50-
## Next steps
50+
## Related content
5151

5252
- Learn more about [Azure Data Share terminology](terminology.md).
5353
- See [Monitor Data Share](monitor-data-share.md) for more details about monitoring Data Share.

articles/data-share/how-to-revoke-share-subscription.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,9 @@ author: sidontha
55
ms.author: sidontha
66
ms.service: azure-data-share
77
ms.topic: how-to
8-
ms.date: 12/19/2023
8+
ms.date: 02/12/2025
99
---
10+
1011
# How to revoke a consumer's share subscription in Azure Data Share
1112

1213
This article explains how to revoke a share subscription from one or more of your consumers using Azure Data Share. This prevents a consumer from triggering any more snapshots. If the consumer hasn't yet triggered a snapshot, they'll never receive the data once the share subscription is revoked. If they have previously triggered a snapshot, the latest data that they have will stay in their account.
@@ -19,6 +20,6 @@ In Azure Data Share, navigate to your sent share and select the **Share Subscrip
1920

2021
Check the boxes next to the recipients whose share subscriptions you would like to delete and then select **Revoke**. The consumer will no longer get updates to their data.
2122

22-
## Next steps
23+
## Related content
2324

2425
Learn more about how to [monitor your data shares](how-to-monitor.md).

articles/data-share/how-to-share-from-sql.md

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

1111
# Share and receive data from Azure SQL Database and Azure Synapse Analytics
@@ -40,7 +40,7 @@ Azure Data Share supports sharing full data snapshots from several SQL resources
4040
|Synapse Analytics (workspace) dedicated SQL pool|Yes |No|
4141

4242
> [!NOTE]
43-
> Currently, Azure Data Share does not support sharing from these resources:
43+
> Currently, Azure Data Share doesn't support sharing from these resources:
4444
>
4545
> - Azure Synapse Analytics (workspace) serverless SQL pool
4646
> - Azure SQL databases with Always Encrypted configured
@@ -68,7 +68,7 @@ When you share data from a SQL source, the following mappings are used from SQL
6868
>[!NOTE]
6969
>
7070
> 1. For data types that map to the Decimal interim type, currently snapshot supports precision up to 28. If you have data that requires precision larger than 28, consider converting to a string.
71-
> 1. If you are sharing data from Azure SQL database to Azure Synapse Analytics, not all data types are supported. Refer to [Table data types in dedicated SQL pool](../synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-data-types.md) for details.
71+
> 1. If you're sharing data from Azure SQL database to Azure Synapse Analytics, not all data types are supported. Refer to [Table data types in dedicated SQL pool](../synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-data-types.md) for details.
7272
7373
| SQL Server data type | Azure Data Share interim data type |
7474
|:--- |:--- |
@@ -423,6 +423,6 @@ For large tables where incremental updates are desired, you can export updates t
423423
424424
The most common cause of snapshot failure is that Data Share doesn't have permission to the source or target data store. In order to grant Data Share permission to the source or target Azure SQL Database or Azure Synapse Analytics (formerly Azure SQL DW), you must run the provided SQL script when connecting to the SQL database using Microsoft Entra authentication. To troubleshoot other SQL snapshot failures, refer to [Troubleshoot snapshot failure](data-share-troubleshoot.md#snapshots).
425425

426-
## Next steps
426+
## Related content
427427

428428
You've learned how to share and receive data from SQL sources using Azure Data Share service. To learn more about sharing from other data sources, continue to [supported data stores](supported-data-stores.md).

articles/data-share/how-to-share-from-storage.md

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

1111
# Share and receive data from Azure Blob Storage and Azure Data Lake Storage
@@ -39,7 +39,7 @@ Azure Data Share supports sharing data from Azure Data Lake Gen1, Azure Data Lak
3939
||Containers|
4040

4141
>[!NOTE]
42-
> *Block, append, and page blobs are all supported. However, when they are shared they will be received as **block blobs**.
42+
> *Block, append, and page blobs are all supported. However, when they're shared they'll be received as **block blobs**.
4343
4444
Data shared from these sources can be received by Azure Data Lake Gen2 or Azure Blob Storage.
4545

@@ -204,6 +204,6 @@ Storage snapshot performance is impacted by many factors in addition to number o
204204
- Location of source and target data stores.
205205
- For incremental snapshot, the number of files in the shared dataset can affect the time it takes to find the list of files with last modified time after the last successful snapshot.
206206

207-
## Next steps
207+
## Related content
208208

209209
You've learned how to share and receive data from a storage account by using the Azure Data Share service. To learn about sharing from other data sources, see the [supported data stores](supported-data-stores.md).

articles/data-share/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ metadata:
1010
ms.topic: landing-page
1111
author: sidontha
1212
ms.author: sidontha
13-
ms.date: 12/19/2023
13+
ms.date: 02/12/2025
1414

1515
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
1616

articles/data-share/monitor-data-share-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Monitoring data reference for Azure Data Share
33
description: This article contains important reference material you need when you monitor Azure Data Share.
4-
ms.date: 02/28/2024
4+
ms.date: 02/12/2025
55
ms.custom: horz-monitor
66
ms.topic: reference
77
author: sidontha

articles/data-share/monitor-data-share.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
title: Monitor Azure Data Share
33
description: Start here to learn how to monitor Azure Data Share.
4-
ms.date: 03/05/2024
4+
ms.date: 02/12/2025
55
ms.custom: horz-monitor
6-
ms.topic: conceptual
6+
ms.topic: concept-article
77
author: sidontha
88
ms.author: sidontha
99
ms.service: azure-data-share

articles/data-share/move-to-new-region.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Use Azure Resource Manager template to move Azure Data Share accoun
44
ms.service: azure-data-share
55
ms.custom: devx-track-arm-template
66
ms.topic: how-to
7-
ms.date: 12/19/2023
7+
ms.date: 02/12/2025
88
author: sidontha
99
ms.author: sidontha
1010
#Customer intent: As an Azure Data Share User, I want to move my Data Share account to a new region.
@@ -27,7 +27,7 @@ The following steps show how to deploy a new Data Share account using a Resource
2727

2828
### Export the template and deploy from the portal
2929

30-
1. Log in to the [Azure portal](https://portal.azure.com).
30+
1. Sign in to the [Azure portal](https://portal.azure.com).
3131
1. Select **All resources** and then select your Data Share account
3232
1. Select **Automation** > **Export template**
3333
1. Choose **Deploy** in the **Export template** window.
@@ -67,7 +67,7 @@ The following steps show how to deploy a new Data Share account using a Resource
6767
]
6868
```
6969

70-
1. To obtain region location codes, see [Azure Locations](https://azure.microsoft.com/global-infrastructure/locations/). The code for a region is the region name with no spaces, **Central US** = **centralus**.
70+
1. To obtain region location codes, see [Azure Locations](https://azure.microsoft.com/global-infrastructure/locations/). The code for a region is the region name with no spaces, **Central US** = **centralus**.
7171

7272
1. You can also change other parameters in the template if you choose. This is optional depending on your requirements:
7373

@@ -112,7 +112,7 @@ The following steps show how to deploy a new Data Share account using a Resource
112112
* If you're also moving the resources contained in the datasets to a new region, you'll have to remove the datasets from the **template.json** file and manually readd them once the Data Share account and resources referenced in the datasets are moved to the new region.
113113

114114
>[!IMPORTANT]
115-
>* Datasets will fail to deploy if the new Data Share account you are deploying will not automatically inherit required permissions to access the datasets. The required permissions depend on the dataset type. See here for required permissions for [Azure Synapse Analytics and Azure SQL Database datasets](how-to-share-from-sql.md#prerequisites-for-sharing-from-azure-sql-database-or-azure-synapse-analytics-formerly-azure-sql-dw). See here for required permissions for [Azure Storage and Azure Data Lake Gen 1 and Gen2 datasets](how-to-share-from-storage.md#prerequisites-for-the-source-storage-account).
115+
>* Datasets will fail to deploy if the new Data Share account you're deploying won't automatically inherit required permissions to access the datasets. The required permissions depend on the dataset type. See here for required permissions for [Azure Synapse Analytics and Azure SQL Database datasets](how-to-share-from-sql.md#prerequisites-for-sharing-from-azure-sql-database-or-azure-synapse-analytics-formerly-azure-sql-dw). See here for required permissions for [Azure Storage and Azure Data Lake Gen 1 and Gen2 datasets](how-to-share-from-storage.md#prerequisites-for-the-source-storage-account).
116116

117117
```json
118118
"resources": [
@@ -140,7 +140,7 @@ The following steps show how to deploy a new Data Share account using a Resource
140140

141141
1. Under the **Project details** section, select the **Subscription** dropdown to choose the subscription where the target Data Share account will be deployed.
142142

143-
1. Select the **Resource group** dropdown to choose the resource group where the target Data Share account will be deployed. You can select **Create new** to create a new resource group for the target Data Share account.
143+
1. Select the **Resource group** dropdown to choose the resource group where the target Data Share account will be deployed. You can select **Create new** to create a new resource group for the target Data Share account.
144144

145145
1. Verify that the **Location** field is set to the target location you want the Data Share account to be deployed to.
146146

@@ -173,9 +173,9 @@ The following steps show how to deploy a new Data Share account using a Resource
173173

174174
To complete the move of the Data Share account, delete the source Data Share account. To do so, select the resource group from your dashboard in the Azure portal, navigate to the Data Share account you wish to delete and select **Delete** at the top of the page.
175175

176-
## Next steps
176+
## Related content
177177

178-
In this tutorial, you moved an Azure Data Share account from one region to another and cleaned up the source resources. To learn more about moving resources between regions and disaster recovery in Azure, refer to:
178+
In this tutorial, you moved an Azure Data Share account from one region to another and cleaned up the source resources. To learn more about moving resources between regions and disaster recovery in Azure, refer to:
179179

180180
- [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md)
181181
- [Move Azure VMs to another region](../site-recovery/azure-to-azure-tutorial-migrate.md)

0 commit comments

Comments
 (0)