What causes Fabric Pipeline Error 2112?

The EndpointSuffix in the storage connection string points to a sovereign or non-public cloud (e.g., Azure China, Azure Government) that is not supported in the current Fabric context. A custom or malformed EndpointSuffix was entered that does not match any known Azure cloud environment. The storage account was migrated or the endpoint was manually edited, resulting in an unrecognized suffix. The connection was copied from a different cloud environment without updating the endpoint configuration

How do I fix Fabric Pipeline Error 2112?

Step 1: Review the EndpointSuffix value in the storage connection string or linked service configuration and compare it against supported Azure endpoint suffixes (e.g., core.windows.net for Azure Public Cloud).. Step 2: Confirm that the storage account you are targeting is hosted in a cloud environment supported by Microsoft Fabric Data Factory.. Step 3: If the storage is in an unsupported sovereign cloud, migrate the data to a storage account in a supported Azure public cloud region or evaluate alternative connectivity options.. Step 4: If the EndpointSuffix is incorrect due to a typo or manual edit, retrieve the correct connection string from the Azure Portal and update the linked service.. Step 5: Re-test the connection and re-run the pipeline to confirm the error is resolved.

High severityconfigurationMicrosoft Fabric →

Power BI Refresh Error:
Fabric Pipeline Error 2112

What does this error mean?

The cloud environment type could not be determined or is not supported based on the EndpointSuffix provided in the storage connection. The pipeline cannot route the storage request to a valid cloud region.

Common causes

1The EndpointSuffix in the storage connection string points to a sovereign or non-public cloud (e.g., Azure China, Azure Government) that is not supported in the current Fabric context
2A custom or malformed EndpointSuffix was entered that does not match any known Azure cloud environment
3The storage account was migrated or the endpoint was manually edited, resulting in an unrecognized suffix
4The connection was copied from a different cloud environment without updating the endpoint configuration

How to fix it

1Step 1: Review the EndpointSuffix value in the storage connection string or linked service configuration and compare it against supported Azure endpoint suffixes (e.g., core.windows.net for Azure Public Cloud).
2Step 2: Confirm that the storage account you are targeting is hosted in a cloud environment supported by Microsoft Fabric Data Factory.
3Step 3: If the storage is in an unsupported sovereign cloud, migrate the data to a storage account in a supported Azure public cloud region or evaluate alternative connectivity options.
4Step 4: If the EndpointSuffix is incorrect due to a typo or manual edit, retrieve the correct connection string from the Azure Portal and update the linked service.
5Step 5: Re-test the connection and re-run the pipeline to confirm the error is resolved.

Frequently asked questions

Does Microsoft Fabric support connections to Azure Government or Azure China storage?

Support for sovereign clouds in Microsoft Fabric Data Factory may be limited. Check the latest Microsoft Fabric regional availability and compliance documentation to confirm whether your specific sovereign cloud endpoint is supported.

Can I use a custom domain endpoint for Azure Storage with Fabric pipelines?

Custom domain endpoints for Azure Storage may not be recognized by Fabric's cloud type resolution logic. It is recommended to use the standard Azure Storage endpoint suffix (core.windows.net) to ensure compatibility.