Data Factory - Copy Activity - Azure Blob Storage to Snowflake V2 - Extremely long queue times

Question

Noticing this morning unusual queue times on copy activities in the second part of the staged copy from Azure to Snowflake (Azure Blob Storage to Snowflake V2). The first part of the copy activity (reading from API for instance) is fine but after it copies to blob storage (staging) and then is copying from staging to Snowflake it is getting stuck in unusually long queue times. Running just one activity at a time (no parallel tasks/activities) and even though other activities already ran (so all provisioning should have been completed already) still getting long queue time. It's happening on multiple activities (in sequence). Doesn't seem like it was happening earlier this morning but then started around 8 or 9am ET. The Snowflake linked service is using a managed azure integration with private endpoint using link to Snowflake (equiv to PrivateLink)

Answer 1

Azure has acknowledged their problem

Impact Statement: Starting at 11:39 UTC on 24 April 2026, a platform issue resulted in provisioning, scaling, and connectivity issues for customers with Azure workloads that are hosted in the East US region. This issue initially affected one availability zone in East US. As traffic was automatically rerouted and shared services were involved, some customers in other availability zones may have also experienced an impact. The impacted services affected (but are not limited to):

• App Service, Application Gateway, Azure Cache for Redis, Azure Data Factory, Azure Database for PostgreSQL - Flexible Server, Azure Databricks, Azure Kubernetes Service (AKS), Azure Service Fabric, Azure Synapse Analytics, Azure Virtual Desktop, Azure VMware Solution, Virtual Machine Scale Sets, and Virtual Machines

Current Status: We detected this issue through automated monitoring after identifying an unusual drop in service success rates. The issue was caused by a recent change, and rollback actions are in progress across availability zones (AZs). Customers may begin to see recovery if using resources in AZ03, with Availability Zone 01 currently in progress. Please refer to this documentation to understand the logical to physical availability zone mapping for your subscription.

However, there is no confirmed estimated time for full resolution at this moment.

The next update will be shared within the next 60 minutes, or as events warrant.