Intermittent connectivity issue between Azure Data Factory and Blob Storage — 'remote name could not be resolved'

Hi everyone, For about a week now, I’ve been experiencing an intermittent issue when running a pipeline in Azure Data Factory that writes data to an Azure Blob Storage container. The pipeline sometimes fails with the following error:

Operation on target SOURCE failed: Operation on target INGEST failed: Operation on target ForEach Table failed: Activity failed because an inner activity failed; Inner activity name: Export table, Error: ErrorCode=AzureBlobFailedToCreateContainer,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Unable to create Azure Blob container. Endpoint: 'https://xxxxxxxxx.blob.core.windows.net/', Container Name: 'container01'.,Source=Microsoft.DataTransfer.ClientLibrary,''Type=Microsoft.WindowsAzure.Storage.StorageException,Message=The remote name could not be resolved: 'xxxxxxxxx.blob.core.windows.net',Source=Microsoft.WindowsAzure.Storage,''Type=System.Net.WebException,Message=The remote name could not be resolved: 'xxxxxxxxx.blob.core.windows.net',Source=System,'.

The issue is intermittent, sometimes the pipeline runs successfully, and other times it fails, with no configuration changes in between.

We’ve noticed that this problem only happens in pipelines that use data sources located on-premises, which require a Self-hosted Integration Runtime (SHIR) to access the data. Pipelines that do not use a SHIR (i.e., those pulling from cloud-based sources) are able to complete the copy activity without errors.

In addition, we are also experiencing similar errors when running Python code (Azure function) that attempts to write to the same Blob Storage account, where it also fails intermittently with a “remote name could not be resolved” message.

Prior to this issue, everything was working fine — both the ADF pipelines and the Python-based processes were functioning normally.

No changes have been made to our infrastructure:

• The Storage Account has not been recreated
• The managed private endpoint between Data Factory and the Storage Account remains unchanged

Has anyone else encountered this issue recently? If you’ve experienced something similar and found a solution or workaround, your help would be greatly appreciated. Thanks in advance!