This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 18%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVM%3C/text%3E%3C/svg%3E)
Hi everyone,
Last Monday I did following changes to my storage account:
During this process did we lose the setting "Blob public access" which was set to Enabled.
It's now set to Disabled.
Each time I try to change it, we get following error:
Failed to update storage account 'xxx'. Error: An operation is currently performing on this storage account that requires exclusive access.
This was one week ago, and our images in our CDN is no longer available.
I have tested following:
All changes in "Configuration" gives same error -> Error: An operation is currently performing on this storage account that requires exclusive access.
After 1 week + 1 day, it worked.
I read somewhere else that upgrades etc like that sometimes need 1 week to timeout.
However
Today the configuration had change itself to Disabled and I get the same error.
And today (1 day after) I can enable it again.
What is this!?!
I will see if stays like this now, otherwise I guess I have to do a migration to a new storage account.
@Viktor Morin Can you please share the screenshot of the error message?
Can you perform other operation in the same storage account?
Note: We are adding public access control on storage account level. When you disable it, you will fail when creating a container with publicaccess. You will also fail to change container to public access, or access a blob that have been configured with public access. Azure Policy can define policy with the control to audit and enforce policy across storage accounts.”
@Sumarigo-MSFT
At the Configuratin tap, I couldnt do any changes when this error was present.
Right now it works again, I just hope it dosnt become disabled again and we lose the contact to our CDN.
What kind of process is disabling that settings without informing the user?
It seems to work now, 2 weeks after the V1 to V2 upgrade.
@ViktorMorin-7401 Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused. We need to work closer on this issue. This may require a deeper investigation, so If you have a support plan, I request you file a support ticket, else please do let us know, we will try and help you get a one-time free technical support. In this case, could you send an email to AzCommunity@Microsoft.com referencing this thread. Please mention "ATTN subm" in the subject field and subscription ID. Thank you for your cooperation on this matter and look forward to your reply.
Hope this helps!
Please do not forget to "Accept the answer" and Upvote on the post that helps you, this can be beneficial to other community members.
@ViktorMorin-7401 Just checking in to see if you have had a chance to see the previous response. Could you share the above required information to understand/investigate this issue further? If the issue is been fixed can you please share the troubleshooting steps which may benefit other community members.