What causes ADLSGen2OperationFailed?

The error wraps a more specific Azure Data Lake Storage Gen2 error — check the inner message for details. The service principal or managed identity lacks sufficient permission to access ADLS Gen2 (Forbidden in inner message). The integration runtime's IP address is not allowed by the ADLS Gen2 storage account firewall (connection forcibly closed). Transient Azure ADLS Gen2 service issue (InternalServerError in inner message). Using an ADLS Gen2 linked service to connect to an Azure Blob Storage account that has BlobStorageEvents or SoftDelete enabled

How do I fix ADLSGen2OperationFailed?

Check the inner error message in ADLSGen2OperationFailed — it contains the specific storage error code and cause.. If the inner message contains 'Forbidden': grant the service principal or managed identity the 'Storage Blob Data Contributor' (write) or 'Storage Blob Data Reader' (read) RBAC role on the container.. If the inner message says 'connection was forcibly closed': add the ADF integration runtime IP addresses to the storage account firewall allowlist.. If the inner message says 'This endpoint does not support BlobStorageEvents or SoftDelete': either upgrade the Azure Blob Storage account to ADLS Gen2, switch the linked service to use the Azure Blob Storage connector, or disable Blob storage events and soft delete on the storage account.. For transient errors (InternalServerError): retry the operation; if it persists, contact Azure Storage support with the request ID from the error message.

High severitydata source

Power BI Refresh Error:
ADLSGen2OperationFailed

What does this error mean?

An ADLS Gen2 operation failed in ADF or Fabric. This error wraps a storage-level inner error — check the inner message for the specific cause and fix.

Common causes

1The error wraps a more specific Azure Data Lake Storage Gen2 error — check the inner message for details
2The service principal or managed identity lacks sufficient permission to access ADLS Gen2 (Forbidden in inner message)
3The integration runtime's IP address is not allowed by the ADLS Gen2 storage account firewall (connection forcibly closed)
4Transient Azure ADLS Gen2 service issue (InternalServerError in inner message)
5Using an ADLS Gen2 linked service to connect to an Azure Blob Storage account that has BlobStorageEvents or SoftDelete enabled

How to fix it

1Check the inner error message in ADLSGen2OperationFailed — it contains the specific storage error code and cause.
2If the inner message contains 'Forbidden': grant the service principal or managed identity the 'Storage Blob Data Contributor' (write) or 'Storage Blob Data Reader' (read) RBAC role on the container.
3If the inner message says 'connection was forcibly closed': add the ADF integration runtime IP addresses to the storage account firewall allowlist.
4If the inner message says 'This endpoint does not support BlobStorageEvents or SoftDelete': either upgrade the Azure Blob Storage account to ADLS Gen2, switch the linked service to use the Azure Blob Storage connector, or disable Blob storage events and soft delete on the storage account.
5For transient errors (InternalServerError): retry the operation; if it persists, contact Azure Storage support with the request ID from the error message.

Frequently asked questions

Does this error affect multiple datasets at once?

If multiple datasets connect to the same data source, yes — all of them will fail until the source connectivity is restored.

Can this error be caused by a server migration or rename?

Yes — if the server name, database name, or connection string changed (e.g., during a cloud migration), Power BI still holds the old connection details. Update the connection in Power BI Desktop and republish.

Does this error appear in Power BI Desktop?

Sometimes — if you open the .pbix file and attempt a refresh, Desktop will surface the same connection error. This is useful for debugging without affecting the Service dataset.

Will the error resolve automatically once the source is back online?

Only if it was a temporary outage. The next scheduled refresh will succeed automatically. If the connection string changed or credentials expired, manual intervention is needed.

Source · learn.microsoft.com/en-us/fabric/data-factory/connector-troubleshoot-azure-data-lake-storage