Error code 11408: The operation has timed out. Id. de actividad

Question

Error code 11408: The operation has timed out. Id. de actividad

Juan Esteban Mahecha Trujillo 20

Hello, I am starting with Azure Synapse, and when I want to ingest data with a copy, when I configure the connection to the data source (In this case, it is HTTP with a URL), I get this error, and I don't know why. I have configured the storage account with the IPs that have permissions, and I have also configured the IPs that have access in my Synapse resource. Additionally, I have enabled the managed virtual network with Data exfiltration protection enabled. I believe this should be related to that, but I don't know what extra configuration I need to do to allow this type of connections and others. I haven't found information regarding this error code, I would greatly appreciate any help.

1 answer

Your answer

Answer 1

Venkat Reddy Navari 2,555 Microsoft External Staff Moderator

Hi @Juan Esteban Mahecha Trujillo The error you're seeing -Error code 11408: The operation has timed out -usually indicates a network connectivity issue between Synapse and the external HTTP data source. Based on your description, it's very likely related to the managed virtual network and Data Exfiltration Protection settings.

When Data Exfiltration Protection is enabled in a Synapse managed virtual network, outbound traffic to external HTTP endpoints is blocked by default for security. This means that trying to connect to a public HTTP URL will time out unless that domain is explicitly allowed.

How to Fix It

To allow access to your HTTP endpoint:

Go to your Synapse workspace in the Azure Portal.
Navigate to Networking > Managed virtual network settings.
Find the section labeled Allowed FQDNs (Fully Qualified Domain Names).
Add the domain name from your HTTP URL (for example, api.example.com).
Click Save and Publish your changes.

IP allowlisting won’t apply in this case since the traffic is originating from a managed virtual network using internal Azure infrastructure. Instead, allowlisting the domain is the recommended and supported approach.

Test your HTTP URL outside of Synapse (e.g., in a browser or with curl) to confirm it's reachable.
Make sure your HTTP service allows requests from Azure.
Review the Azure Synapse HTTP connector documentation to confirm your setup aligns with supported configurations.

If you’ve already done all this and the error persists, it may be worth checking DNS resolution or using a Managed Private Endpoint, if your HTTP source supports Azure Private Link.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

Juan Esteban Mahecha Trujillo 20 Reputation points

2025-05-14T16:01:08.6766667+00:00

Hello @Venkat Reddy Navari , thank you for responding. I am trying to follow your recommendation, but when I go to Networking, I don't see the option for Managed virtual network settings.
Venkat Reddy Navari 2,555 Reputation points Microsoft External Staff Moderator

2025-05-14T16:53:12.6766667+00:00
@Juan Esteban Mahecha Trujillo It looks like your Synapse workspace does not have a Managed Virtual Network (MVNet) enabled, which is why you're not seeing the "Managed virtual network settings" option under the Networking blade.

Here's how to confirm:

Go to Synapse Studio → Manage (gear icon on the left)

Click Integration runtimes

Check if your AutoResolveIntegrationRuntime or any Self-hosted IR shows "Managed Virtual Network: Enabled"

If it says "Disabled", your workspace was created without MVNet, and Data Exfiltration Protection isn’t applicable — so your timeout may be caused by something else (like actual network or DNS issues).

If you do want to use MVNet with data exfiltration protection, you’d need to recreate the workspace with "Enable Managed Virtual Network" selected during creation. This setting can't be changed afterward.
Juan Esteban Mahecha Trujillo 20 Reputation points

2025-05-14T17:05:21.9566667+00:00

@Venkat Reddy Navari Yes, it is enabled :C
look
Venkat Reddy Navari 2,555 Reputation points Microsoft External Staff Moderator

2025-05-15T13:08:36.82+00:00
@Juan Esteban Mahecha Trujillo Thanks again for confirming that your Integration Runtime is using a Managed Virtual Network -that helps a lot!

Just to clarify - have you had a chance to locate and update the FQDN allowlist settings in Synapse Studio?

Here’s how to do it step-by-step (in case it helps):

Open Synapse Studio (web interface for your Synapse workspace).

Go to the Manage hub (gear icon on the left).

Select Managed Virtual Network > Networking.

Look for the section where you can add "Allowed FQDNs" (Fully Qualified Domain Names).

Add the domain of your HTTP source (e.g., api.example.com), then click Save and Publish the changes.

Once that’s done, try the copy activity again.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Venkat Reddy Navari 2,555 Reputation points Microsoft External Staff Moderator

2025-05-16T11:14:18.1433333+00:00

@Juan Esteban Mahecha Trujillo Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Share via

Error code 11408: The operation has timed out. Id. de actividad

1 answer

Your answer