When we say: Data, bratwurst and beer, we are of course talking about DataGrillen. After more than 2 years of absence, it was time again in recent days, with speakers from all over the world with almost 50 sessions, good weather and a large group of participants, quite a bit of knowledge has been shared again. And as is traditional with this event, the first day will be finalized with a barbecue for all participants. The organization is in the hands of Ben and WIlliam and you can leave that up to them. Everything was well organized again. My session on Microsoft Purview was well attended, the slides can be found in the link below.
Before you can start Authoring your workflows make sure you the correct user to the role assignment Workflow administrators, if you haven't done that correctly the option will be greyed out.
Azure Purview is localized in 18 languages. To change the language used, go to the Settings from the top bar and select the desired language from the dropdown.
Migrate Azure Storage to Storage Account with Azure Data Lake Gen2 capabilities
Does it sometimes happen that you come across a Storage Account where the Hierarchical namespace is not enabled or that you still have a Storage Account V1? In the tutorial below I describe the different steps that have recently become possible to perform this migration.
Azure Storage V1
The first step is to check what Account kind is currently deployed. If this is Storage (general purpose v1), we first need to Migrate the Storage account to V2, if this is already V2 then go to the next step.
You can click on change and a new window will pop-up.
Note: Choosing a storage access tier during account upgrade is free. Changing the storage access tier after the upgrade operation may result in changes to your bill.
Select the Tier you want to Migrate to, once you have done that start the Upgrade.
When the upgrade is successful, you will see that the Account kind is now StorageV2. We can now continue to the next step.
Azure Storage V2
To start the Migration click in the Taskbar on Data Lake Gen2 upgrade or click in the blob service properties on 'Disabled' for the Hierarchical namespace property.
The Migration window will open and we can start with step 1.
Take notice of the unsupported features/functionalities.
Agree with implications of Upgrading your Azure Data Lake Storage. Once this step is done we can continue with step 2, the validation.
If everything runs fine, you can start the upgrade step 3. If it fails check the errors. You need to download the error.json file to check which blobs are failing, mostly this are the unsupported functionalities or incompatible features.
