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-factory/connector-shopify.md
+83-3Lines changed: 83 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: jianleishen
7
7
ms.subservice: data-movement
8
8
ms.topic: conceptual
9
9
ms.custom: synapse
10
-
ms.date: 11/05/2024
10
+
ms.date: 08/12/2025
11
11
---
12
12
13
13
# Copy data from Shopify using Azure Data Factory or Synapse Analytics (Preview)
@@ -18,6 +18,9 @@ This article outlines how to use the Copy Activity in an Azure Data Factory or S
18
18
> [!IMPORTANT]
19
19
> This connector is currently in preview. You can try it out and give us feedback. If you want to take a dependency on preview connectors in your solution, please contact [Azure support](https://azure.microsoft.com/support/).
20
20
21
+
> [!IMPORTANT]
22
+
> The Shopify connector version 2.0 (Preview) provides improved native Shopify support. If you are using Shopify connector version 1.0 in your solution, please [upgrade the Shopify connector](#upgrade-the-shopify-connector-from-version-10-to-version-20) before **October 22, 2025**. Refer to this [section](#shopify-connector-lifecycle-and-upgrade) for details on the difference between version 2.0 (Preview) and version 1.0.
23
+
21
24
## Supported capabilities
22
25
23
26
This Shopify connector is supported for the following capabilities:
@@ -37,6 +40,9 @@ The connector supports the Windows versions in this [article](create-self-hosted
37
40
38
41
The billing_on column property was removed from the Recurring_Application_Charges and UsageCharge tables due to Shopify's official deprecation of billing_on field.
39
42
43
+
> [!Note]
44
+
> For version 2.0 (Preview), column names retain the Shopify GraphQL structure, such as `data.customers.edges.node.xx`. For version 1.0, column names use simplified names.
@@ -70,7 +76,44 @@ The following sections provide details about properties that are used to define
70
76
71
77
## Linked service properties
72
78
73
-
The following properties are supported for Shopify linked service:
79
+
The Shopify connector now supports version 2.0 (Preview). Refer to this [section](#upgrade-the-shopify-connector-from-version-10-to-version-20) to upgrade your Shopify connector version from version 1.0. For the property details, see the corresponding sections.
80
+
81
+
-[Version 2.0 (Preview)](#version-20)
82
+
-[Version 1.0](#version-10)
83
+
84
+
### <aname="version-20"></a>Version 2.0 (Preview)
85
+
86
+
The Shopify linked service supports the following properties when apply version 2.0 (Preview):
87
+
88
+
| Property | Description | Required |
89
+
|:--- |:--- |:--- |
90
+
| type | The type property must be set to: **Shopify**| Yes |
91
+
| version | The version that you specify. The value is `2.0`. | Yes |
92
+
| host | The endpoint of the Shopify server. (that is, mystore.myshopify.com) | Yes |
93
+
| accessToken | The API access token that can be used to access Shopify’s data. The token does not expire if it is offline mode. Mark this field as a SecureString to store it securely, or [reference a secret stored in Azure Key Vault](store-credentials-in-key-vault.md). | Yes |
94
+
95
+
**Example:**
96
+
97
+
```json
98
+
{
99
+
"name": "ShopifyLinkedService",
100
+
"properties": {
101
+
"type": "Shopify",
102
+
"version": "2.0",
103
+
"typeProperties": {
104
+
"host" : "mystore.myshopify.com",
105
+
"accessToken": {
106
+
"type": "SecureString",
107
+
"value": "<accessToken>"
108
+
}
109
+
}
110
+
}
111
+
}
112
+
```
113
+
114
+
### Version 1.0
115
+
116
+
The Shopify linked service supports the following properties when apply version 1.0:
74
117
75
118
| Property | Description | Required |
76
119
|:--- |:--- |:--- |
@@ -108,7 +151,7 @@ To copy data from Shopify, set the type property of the dataset to **ShopifyObje
108
151
| Property | Description | Required |
109
152
|:--- |:--- |:--- |
110
153
| type | The type property of the dataset must be set to: **ShopifyObject**| Yes |
111
-
| tableName | Name of the table. |No (if "query" in activity source is specified) |
154
+
| tableName | Name of the table. |Yes for version 2.0 (Preview).<br> No for version 1.0 (if "query" in activity source is specified) |
112
155
113
156
**Example**
114
157
@@ -140,6 +183,9 @@ To copy data from Shopify, set the source type in the copy activity to **Shopify
140
183
| type | The type property of the copy activity source must be set to: **ShopifySource**| Yes |
141
184
| query | Use the custom SQL query to read data. For example: `"SELECT * FROM "Products" WHERE Product_Id = '123'"`. | No (if "tableName" in dataset is specified) |
142
185
186
+
> [!Note]
187
+
> `query` is not supported in version 2.0 (Preview).
188
+
143
189
**Example:**
144
190
145
191
```json
@@ -172,10 +218,44 @@ To copy data from Shopify, set the source type in the copy activity to **Shopify
172
218
]
173
219
```
174
220
221
+
## Data type mapping for Shopify
222
+
223
+
When you copy data from Shopify, the following mappings apply from Shopify's data types to the internal data types used by the service. To learn about how the copy activity maps the source schema and data type to the sink, see [Schema and data type mappings](copy-activity-schema-and-type-mapping.md).
224
+
225
+
| Shopify data type | Interim service data type (for version 2.0 (Preview)) | Interim service data type (for version 1.0) |
To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
178
244
245
+
## Shopify connector lifecycle and upgrade
246
+
247
+
The following table shows the release stage and change logs for different versions of the Shopify connector:
248
+
249
+
| Version | Release stage | Change log |
250
+
| :----------- | :------- |:------- |
251
+
| Version 1.0 | End of support announced | / |
252
+
| Version 2.0 | Public Preview | • Column names retain the Shopify GraphQL structure, such as `data.customers.edges.node.xx`. <br><br> • `useEncryptedEndpoints`, `useHostVerification`, `usePeerVerification` are not supported in the linked service. <br><br> • `query` is not supported. |
253
+
254
+
### <aname="upgrade-the-shopify-connector-from-version-10-to-version-20"></a> Upgrade the Shopify connector from version 1.0 to version 2.0 (Preview)
255
+
256
+
1. In **Edit linked service** page, select 2.0 (Preview) for version. For more information, see [linked service version 2.0 (Preview) properties](#version-20).
257
+
1. For version 2.0 (Preview), note that column names retain the Shopify GraphQL structure, such as `data.customers.edges.node.xx`. For version 1.0, column names use simplified names.
258
+
1.`query` is only supported in version 1.0. You should use the `tableName` instead of `query` in version 2.0 (Preview).
179
259
180
260
## Related content
181
261
For a list of data stores supported as sources and sinks by the copy activity, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).
Copy file name to clipboardExpand all lines: articles/reliability/includes/storage/reliability-storage-architecture-include.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@
9
9
ms.custom: include file
10
10
---
11
11
12
-
[Locally redundant storage (LRS)](/azure/storage/common/storage-redundancy?#locally-redundant-storage) replicates the data within your storage accounts to one or more Azure availability zones located in the primary region of your choice. Although there's no option to choose your preferred availability zone, Azure may move or expand LRS accounts across zones to improve load balancing. There's no guarantee that your data will be spread across zones. LRS provides at least 99.999999999 (11 nines) durability of objects over a given year. For more information about availability zones, see [What are Availability Zones?](../../availability-zones-overview.md).
12
+
[Locally redundant storage (LRS)](/azure/storage/common/storage-redundancy?#locally-redundant-storage) replicates the data within your storage accounts to one or more Azure availability zones located in the primary region of your choice. Although there's no option to choose your preferred availability zone, Azure may move or expand LRS accounts across zones to improve load balancing. There's no guarantee that your data will be spread across zones. For more information about availability zones, see [What are Availability Zones?](../../availability-zones-overview.md).
13
13
14
14
:::image type="complex" source="../../media/reliability-storage/locally-redundant-storage.png" alt-text="Diagram that shows how data is replicated in availability zones by using LRS." lightbox="../../media/reliability-storage/locally-redundant-storage.png" border="false":::
15
15
A blue box represents the primary region. It contains a gray box that represents the datacenter. A dark purple box inside the datacenter box represents LRS. It contains a light purple box that includes the storage account and three icons labeled copy 1, copy 2, and copy 3.
Copy file name to clipboardExpand all lines: articles/reliability/regions-multi-region-nonpaired.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,6 +130,12 @@ To achieve geo-replication in nonpaired regions:
130
130
131
131
- To learn about how to create multi-region solutions by using Queue Storage, see [Reliability in Queue Storage](./reliability-storage-queue.md).
132
132
133
+
-**For Azure Table Storage:** To learn about how to create multi-region solutions using Azure Table Storage, see [Reliability in Azure Table Storage](./reliability-storage-table.md).
134
+
135
+
## Azure Table Storage
136
+
137
+
To learn about how to create multi-region solutions using Azure Table Storage, see [Reliability in Azure Table Storage](./reliability-storage-table.md).
138
+
133
139
## Azure Virtual Desktop
134
140
135
141
For geo-replication in nonpaired regions for Azure Virtual Desktop, you need to consider session host VMs and storage for user profiles, applications, and data. Microsoft manages the Azure Virtual Desktop control plane, which is globally distributed and highly available.
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments