Skip to content

Commit a6c5453

Browse files
Merge pull request #307440 from MicrosoftDocs/main
Auto Publish – main to live - 2025-10-28 11:00 UTC
2 parents dae472f + 7b47c90 commit a6c5453

File tree

8 files changed

+46
-38
lines changed

8 files changed

+46
-38
lines changed

articles/app-service/includes/tutorial-ai-openai-chatbot/create-openai-resource.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ In this section, you'll use GitHub Codespaces to create an Azure OpenAI resource
3737
```
3838

3939
> [!IMPORTANT]
40-
> The region is critical as it's tied to the regional availability of the chosen model. Model availability and [deployment type availability](/azure/ai-services/openai/how-to/deployment-types) vary from region to region. This tutorial uses `gpt-4o-mini`, which is available in `eastus2` under the Standard deployment type. If you deploy to a different region, this model might not be available or might require a different tier. Before changing regions, consult the [Model summary table and region availability](/azure/ai-services/openai/concepts/models#model-summary-table-and-region-availability) to verify model support in your preferred region.
40+
> The region is critical as it's tied to the regional availability of the chosen model. Model availability and [deployment type availability](/azure/ai-foundry/foundry-models/concepts/deployment-types) vary from region to region. This tutorial uses `gpt-4o-mini`, which is available in `eastus2` under the Standard deployment type. If you deploy to a different region, this model might not be available or might require a different tier. Before changing regions, consult the [Model summary table and region availability](/azure/ai-services/openai/concepts/models#model-summary-table-and-region-availability) to verify model support in your preferred region.
4141
>
4242
4343
6. Create a resource group and an Azure OpenAI resource with a custom domain, then add a gpt-4o-mini model:

articles/data-factory/connector-shopify.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: jianleishen
77
ms.subservice: data-movement
88
ms.topic: conceptual
99
ms.custom: synapse
10-
ms.date: 08/12/2025
10+
ms.date: 10/12/2025
1111
---
1212

1313
# Copy data from Shopify using Azure Data Factory or Synapse Analytics (Preview)
@@ -151,7 +151,10 @@ To copy data from Shopify, set the type property of the dataset to **ShopifyObje
151151
| Property | Description | Required |
152152
|:--- |:--- |:--- |
153153
| type | The type property of the dataset must be set to: **ShopifyObject** | Yes |
154-
| tableName | Name of the table. For version 2.0 (Preview), table names retain the Shopify GraphQL structure, for example `customers`. For version 1.0, table names use simplified names with prefix, for example, `"Shopify"."Customers"`.| Yes for version 2.0 (Preview).<br> No for version 1.0 (if "query" in activity source is specified) |
154+
| tableName | Name of the table. <br><br>For version 2.0 (Preview), table names retain the Shopify GraphQL structure, for example `customers`. <br><br>For version 1.0, table names use simplified names with prefixes, for example, `"Shopify"."Customers"`.| No (if "query" in activity source is specified) |
155+
156+
> [!NOTE]
157+
> *tags* column can not be read when you specify `tableName` in the dataset. To read this column, [use `query`](#shopify-as-source).
155158
156159
**Example**
157160

@@ -181,10 +184,7 @@ To copy data from Shopify, set the source type in the copy activity to **Shopify
181184
| Property | Description | Required |
182185
|:--- |:--- |:--- |
183186
| type | The type property of the copy activity source must be set to: **ShopifySource** | Yes |
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) |
185-
186-
> [!Note]
187-
> `query` is not supported in version 2.0 (Preview).
187+
| query |For version 2.0, use the GraphQL query to read data. To learn more about this query, see this [article](https://shopify.dev/docs/api/admin-graphql). Note that the pagination query is only supported for outer tables, and each record in the outer table can include up to 250 inner table records. <br><br>For version 1.0, use the custom SQL query to read data. For example: `"SELECT * FROM "Products" WHERE Product_Id = '123'"`. | No (if "tableName" in dataset is specified) |
188188

189189
**Example:**
190190

@@ -207,8 +207,7 @@ To copy data from Shopify, set the source type in the copy activity to **Shopify
207207
],
208208
"typeProperties": {
209209
"source": {
210-
"type": "ShopifySource",
211-
"query": "SELECT * FROM \"Products\" WHERE Product_Id = '123'"
210+
"type": "ShopifySource"
212211
},
213212
"sink": {
214213
"type": "<sink type>"
@@ -249,13 +248,13 @@ The following table shows the release stage and change logs for different versio
249248
| Version | Release stage | Change log |
250249
| :----------- | :------- |:------- |
251250
| Version 1.0 | End of support announced | / |
252-
| Version 2.0 | Public Preview | • Table and column names retain the Shopify GraphQL structure. <br><br> • `useEncryptedEndpoints`, `useHostVerification`, `usePeerVerification` are not supported in the linked service. <br><br> • `query` is not supported. |
251+
| Version 2.0 | Public Preview |• Table and column names retain the Shopify GraphQL structure. <br><br> • Support GraphQL query only. <br><br>• `useEncryptedEndpoints`, `useHostVerification`, `usePeerVerification` are not supported in the linked service. |
253252

254253
### <a name="upgrade-the-shopify-connector-from-version-10-to-version-20"></a> Upgrade the Shopify connector from version 1.0 to version 2.0 (Preview)
255254

256255
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).
257256
1. For version 2.0 (Preview), note that table and column names retain the Shopify GraphQL structure.
258-
1. `query` is only supported in version 1.0. You should use the `tableName` instead of `query` in version 2.0 (Preview).
257+
1. If you use SQL query in the copy activity source or the lookup activity that refers to the version 1.0 linked service, you need to convert them to the GraphQL query. To learn more about this query, see this [article](https://shopify.dev/docs/api/admin-graphql)
259258

260259
## Related content
261260
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).

articles/data-factory/connector-upgrade-advisor.md

Lines changed: 15 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: concept-article
99
ms.custom:
1010
- references_regions
1111
- build-2025
12-
ms.date: 07/11/2025
12+
ms.date: 10/28/2025
1313
---
1414

1515
# Connector upgrade advisor in Azure Data Factory and Azure Synapse Analytics
@@ -28,20 +28,28 @@ The Connector upgrade advisor is a comprehensive tool that helps upgrade pipelin
2828

2929
## Supported data sources
3030

31-
- Salesforce
32-
- Salesforce Service Cloud
33-
- ServiceNow
34-
- Snowflake
35-
- PostgreSQL
36-
- Google BigQuery
3731
- Amazon Redshift
3832
- Amazon RDS for Oracle
3933
- Cassandra
34+
- Google BigQuery
4035
- Greenplum
36+
- Hive
37+
- HubSpot
38+
- Impala
4139
- MariaDB
4240
- MySQL
41+
- Netezza
4342
- Oracle
43+
- PostgreSQL
4444
- Presto
45+
- QuickBooks Online
46+
- Salesforce
47+
- Salesforce Service Cloud
48+
- ServiceNow
49+
- Shopify
50+
- Snowflake
51+
- Spark
52+
- Square
4553
- Teradata
4654
- Vertica
4755

0 commit comments

Comments
 (0)