What causes RestdestinationUNSupportedCompressionType?

A compression type (e.g., gzip, deflate, bzip2) was specified in the Copy Activity sink settings that the REST destination connector does not support. The pipeline configuration was copied or migrated from a file-based connector where compression settings are valid but are not applicable to REST sinks. Manual editing of the pipeline JSON introduced an unsupported compressionType property in the REST sink definition. A template or reusable pipeline component included default compression settings not compatible with REST destinations

How do I fix RestdestinationUNSupportedCompressionType?

Step 1: Open the Copy Activity settings in the Fabric Data Factory pipeline editor and navigate to the Sink (destination) configuration tab.. Step 2: Locate and remove or clear the compression type setting from the REST sink configuration, as REST destination connectors do not support compression at the connector level.. Step 3: If compression is required, implement it at the REST API level on the destination server rather than in the pipeline connector settings.. Step 4: Review the pipeline JSON directly (via the code editor) to confirm no residual compressionType property exists in the sink definition block.. Step 5: Save and re-publish the pipeline, then trigger a test run to confirm the error is resolved.

Medium severityconfigurationMicrosoft Fabric →

Power BI Refresh Error:
RestdestinationUNSupportedCompressionType

What does this error mean?

The Fabric Data Factory REST connector encountered a compression type specified in the pipeline configuration that is not supported when writing data to a REST destination. The REST sink does not support the requested compression format.

Common causes

1A compression type (e.g., gzip, deflate, bzip2) was specified in the Copy Activity sink settings that the REST destination connector does not support
2The pipeline configuration was copied or migrated from a file-based connector where compression settings are valid but are not applicable to REST sinks
3Manual editing of the pipeline JSON introduced an unsupported compressionType property in the REST sink definition
4A template or reusable pipeline component included default compression settings not compatible with REST destinations

How to fix it

1Step 1: Open the Copy Activity settings in the Fabric Data Factory pipeline editor and navigate to the Sink (destination) configuration tab.
2Step 2: Locate and remove or clear the compression type setting from the REST sink configuration, as REST destination connectors do not support compression at the connector level.
3Step 3: If compression is required, implement it at the REST API level on the destination server rather than in the pipeline connector settings.
4Step 4: Review the pipeline JSON directly (via the code editor) to confirm no residual compressionType property exists in the sink definition block.
5Step 5: Save and re-publish the pipeline, then trigger a test run to confirm the error is resolved.

Frequently asked questions

Can I compress data sent to a REST destination in any way?

Yes, but compression must be handled server-side at the REST API or by pre-compressing data in a preceding transformation step rather than using the connector's built-in compression setting.

Why does this error only appear at runtime and not during pipeline validation?

Fabric Data Factory's design-time validation may not catch all connector-level incompatibilities; some configuration conflicts are only detected when the connector attempts to execute the operation at runtime.