Currently setting up a storage account for a synapse analytics workspace, there is an existing synapse workspace with a linked service to an azure storage account, When I tried to setup a similar configuration I get the error message below. Here it doesnt work If I disable soft delete for containers and blobs, the test connection functionality works, but the moment I enable it, it fails. What worries me is this, within one of our other environments soft delete for containers and blobs is enabled and the connection works, setup with a managed identity, this was done over a year ago, but If I try to do that today with a new configuration it doesnt work. Not sure what i am supposed to do here.

Hello MrFlinstone , Greetings! Welcome to Microsoft Q&A Platform. The “Conflict” error indicates that there’s a conflict between the configuration you’re trying to set up and the capabilities of the storage account. Could you please double check if your storage type is General purpose V2? You can go to Storage account Settings and under Configuration section you can find these details. Please see below image for reference: Ensure that the managed identity associated with your Synapse Analytics workspace has the necessary permissions to access the storage account and verify that the managed identity is correctly configured and has the appropriate roles assigned (e.g., Storage Blob Data Contributor). If you still facing the issue I would recommend you to please give a try creating another General Purpose v2 storage account / ADLS Gen2 and share the results. Hope this answer helps! Please let us know if you have any further queries. I’m happy to assist you further. Please "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Hi MrFlinstone - Thanks for reaching out. The first account in the snippet appears to be an ADLS Gen2 account and you are using a DFS endpoint which will tend to work. The second account in the snippet appears to be a non ADLS Gen2 account and is a standard GPv2 account. You are using a DFS endpoint with that one and that particular combination along with soft delete isn't supported one and hence the failure. You can either use ADLS Gen2 account or you make use of blob endpoint i.e. AccountName. Blob .Core.Windows.net instead of DFS one. Please let us know if you have any further queries. I’m happy to assist you further. Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

ADLS Gen2 operation failed: Operation returned an invalid status code Conflict. Account: 'x' endpoint does not support BlobStorageEvents or SoftDelete

Accepted answer

Nehruji R 2,661 Reputation points Microsoft Vendor

2024-05-09T06:46:05.9333333+00:00

Hello MrFlinstone,

Greetings! Welcome to Microsoft Q&A Platform.

The “Conflict” error indicates that there’s a conflict between the configuration you’re trying to set up and the capabilities of the storage account. Could you please double check if your storage type is General purpose V2? You can go to Storage account Settings and under Configuration section you can find these details. Please see below image for reference:

Ensure that the managed identity associated with your Synapse Analytics workspace has the necessary permissions to access the storage account and verify that the managed identity is correctly configured and has the appropriate roles assigned (e.g., Storage Blob Data Contributor).

If you still facing the issue I would recommend you to please give a try creating another General Purpose v2 storage account /ADLS Gen2 and share the results.

Hope this answer helps! Please let us know if you have any further queries. I’m happy to assist you further.

Please "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Please sign in to rate this answer.
MrFlinstone 501 Reputation points

2024-05-09T07:40:17.7766667+00:00

Hi,

Thank you for the proposed answer, looking at the configuration screen below. they appear identical, the only key difference that I can see is that on the storage account where it doesnt work, it has an option to upgrade to data lake gen 2 upgrade, whereas the one that works doesnt have this option which suggests that its already a data lake gen 2 specification.

Please advise.

Nehruji R 2,661 Reputation points Microsoft Vendor

2024-05-09T08:08:30.32+00:00

Yes, Seems the one it works has already been a Data Lake Gen 2 and the one doesn't works should be upgraded to Gen2 and hence would request you to perform the upgration to Data Lake Storage Gen2,

Precheck: Your storage account might be configured to use features that aren't yet supported in Data Lake Storage Gen2 enabled accounts. If your account is using such features, the upgrade will not pass the validation step. Review the Blob Storage feature support in Azure Storage accounts article to identify unsupported features. If you're using any such features in your account, disable them before you begin the upgrade.

The following features are supported for Data Lake Storage Gen2 accounts, but are not supported by the upgrade process:

Blob snapshots

Encryption scopes

Immutable storage

Last access time tracking for lifecycle management

Soft delete for blobs

Soft delete for containers

If your storage account has such features enabled, you must disable them before performing the upgrade. If you want to resume using the features after the upgrade is complete, re-enable them.

refer - https://learn.microsoft.com/en-us/azure/storage/blobs/upgrade-to-data-lake-storage-gen2-how-to?tabs=azure-portal for detailed guidance.

Note: It is one-way, and there’s no way to revert your account once the upgrade is complete. It’s essential to validate the upgrade in a nonproduction environment before performing it in a production setting

Please let us know if you have any further queries. I’m happy to assist you further.

Please "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

MrFlinstone 501 Reputation points

2024-05-09T08:37:28.0666667+00:00

Can a storage account be created using bicep with data lake gen v2 capabilities or does it have to be created standard and then go through the upgrade process ? I am looking for a way to script this out.

Nehruji R 2,661 Reputation points Microsoft Vendor

2024-05-09T08:50:42.8266667+00:00

You can use Bicep to define your storage account resources. Here’s an example Bicep snippet for creating a standard general-purpose v2 storage account:

resource mystorage 'Microsoft.Storage/storageAccounts@2021-04-01' = { name: 'mydatalakestorage' location: 'East US' kind: 'StorageV2' sku: { name: 'Standard_LRS' } properties: { supportsHttpsTrafficOnly: true isHnsEnabled: true // Enable hierarchical namespace } }

Adjust the parameters (such as name, location, and sku) according to your requirements.

After defining your Bicep template, deploy it using the Azure CLI or Azure PowerShell. For example, using the Azure CLI:

az deployment group create --resource-group MyResourceGroup --template-file mystorage.bicep

Replace mystorage.bicep with the actual path to your Bicep file.

Data Lake Storage Gen2 capabilities are supported in the following types of storage accounts:

Standard general-purpose v2: This type of account provides access to all Azure Storage services, including blobs, files, queues, tables, and disks.

Premium block blob: If you specifically need premium performance for block blobs, you can choose this type.

Please "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Sign in to comment

Share via

ADLS Gen2 operation failed: Operation returned an invalid status code Conflict. Account: 'x' endpoint does not support BlobStorageEvents or SoftDelete

1 additional answer