An Azure service for ingesting, preparing, and transforming data at scale.
Hi Geoffrey SOUQUIÈRE,
At this time, the native Shopify connector cannot be used with OAuth client-credentials authentication, which is why it cannot be made efficient for your scenario. The connector only supports a static, permanent access token configured directly in the linked service. It does not support dynamically generated OAuth tokens, token refresh, or injecting tokens from pipeline variables or Key Vault.
OAuth tokens obtained from /admin/oauth/access_token work correctly when calling Shopify APIs through Web or REST activities, but the native connector cannot consume these tokens. Since Shopify no longer allows creating new permanent tokens for custom apps as of January 1, 2026, this creates a compatibility gap between the connector and Shopify’s current authentication model.
Given this limitation, the recommended and supported approach is to continue using Web or REST activities with OAuth client credentials and switch to Shopify GraphQL bulk operations. Bulk operations allow you to retrieve orders and line items in a single export job, then download the generated result file once processing completes. This approach is significantly more performant and avoids the overhead of thousands of individual API calls.
the native Shopify connector does not currently support OAuth-based authentication, permanent tokens are no longer an option for new apps, and WebActivity combined with Shopify GraphQL bulk APIs is the most scalable and future-proof solution until native OAuth support is added to the connector.