John Reynolds hey,
you're right to be cautious about those databricks managed storage accounts. the last thing you want is to break your databricks workspace by messing with its underlying storage.
the key thing to understand is who owns the account. if the storage account was created by azure databricks when you set up the workspace, and it's named something like dbstorage..., then it is a managed resource. for these, you should not initiate the migration yourself.
microsoft is very aware that these managed resources exist. the standard procedure for service managed resources is that the owning service, in this case azure databricks, will handle the migration automatically before the deadline. they have a vested interest in making sure their customers' workspaces don't break.
your best course of action is to check the official azure databricks documentation or their release notes. sometimes they publish announcements about planned maintenance or migrations for their managed infrastructure. you can also open a support ticket with azure databricks support to get a definitive answer. they can confirm the migration plan for their managed storage accounts.
if it's a databricks managed account, you probably don't need to do anything. but to be 100% sure, check the databricks docs or contact their support for confirmation.
regards,
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer