What causes DF-Hive-InvalidGen2StagingConfiguration?

No ADLS Gen2 linked service is configured in the Hive linked service staging settings. The ADLS Gen2 storage account does not have hierarchical namespace (HNS) enabled. The ADF managed identity or service principal lacks Storage Blob Data Contributor on the Gen2 container. The staging path (file system and folder) in the Gen2 linked service does not exist

How do I fix DF-Hive-InvalidGen2StagingConfiguration?

Open the Hive linked service in ADF Studio and find the 'Staging storage' section — confirm an ADLS Gen2 linked service is selected.. In the Azure portal, verify the storage account has 'Hierarchical namespace' enabled (Settings > Properties > Hierarchical namespace).. In the storage account, go to Containers (file systems) and confirm the staging container and folder path exist.. Under Access Control (IAM) for the container, grant the ADF managed identity the Storage Blob Data Contributor role.. Test connection the Hive linked service, then re-publish and run a debug data flow to verify.

Medium severitydata flow

Power BI Refresh Error:
DF-Hive-InvalidGen2StagingConfiguration

What does this error mean?

The ADF Mapping Data Flow Hive connector is configured to use ADLS Gen2 as its staging area, but the Gen2 linked service is missing, the container or path doesn't exist, or the ADF managed identity lacks the necessary Gen2 permissions. ADLS Gen2 staging is an alternative to standard Blob staging and requires hierarchical namespace support.

Common causes

1No ADLS Gen2 linked service is configured in the Hive linked service staging settings
2The ADLS Gen2 storage account does not have hierarchical namespace (HNS) enabled
3The ADF managed identity or service principal lacks Storage Blob Data Contributor on the Gen2 container
4The staging path (file system and folder) in the Gen2 linked service does not exist

How to fix it

1Open the Hive linked service in ADF Studio and find the 'Staging storage' section — confirm an ADLS Gen2 linked service is selected.
2In the Azure portal, verify the storage account has 'Hierarchical namespace' enabled (Settings > Properties > Hierarchical namespace).
3In the storage account, go to Containers (file systems) and confirm the staging container and folder path exist.
4Under Access Control (IAM) for the container, grant the ADF managed identity the Storage Blob Data Contributor role.
5Test connection the Hive linked service, then re-publish and run a debug data flow to verify.

Frequently asked questions

What is the difference between Blob staging (InvalidBlobStagingConfiguration) and Gen2 staging (InvalidGen2StagingConfiguration)?

Both are staging options for the Hive connector. Blob staging uses standard Azure Blob; Gen2 staging uses ADLS Gen2 with hierarchical namespace. Choose Gen2 if your primary data lake is ADLS Gen2.

How do I check if hierarchical namespace is enabled on my storage account?

In the Azure portal, go to storage account > Settings > Properties and check 'Hierarchical namespace'. HNS cannot be enabled after account creation — create a new account if needed.

Can I switch from Gen2 staging to Blob staging to work around this error?

Yes — in the Hive linked service, change the staging storage type to Azure Blob Storage and configure a standard Blob linked service. This avoids the HNS requirement. The Hive connector supports both types interchangeably.

Will changing the staging account affect existing data in the Hive tables?

No — the staging storage is only a temporary working area used during data flow execution. Changing it does not affect data already in the Hive tables or in the final destination storage.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/data-flow-troubleshoot-guide