Is Azure storage Copy Blob From URL operation atomic
I have a C# application that uploads data to an Azure BLOB storage container as a temp file and then renames the temp file to some well-known name. Since the file’s data can be used elsewhere immidiately, I rely on the rename operation being atomic (either succeeding or failing completely with no intermediate state).
unable to create a container using `az` command
I am trying to create to create a blob
container using the following command
Securing Blob Access using Entra ID
I thought this would be simple to find an answer for but I’m struggling and hoping someone can point me in the right direction. I have an Azure Blob Storage account that I’m wanting to put blobs into via code, using a SAS token. However, I want to ensure that only internal employees, from a single user group, can access the blobs themselves. I presume I can secure the container and lock it to the group, but how do I retrieve/generate secure links to send to the users?
azcopy not working when authenticated without using SAS tokens
got a storage account using a private endpoint connection, i am trying to move the cotainers onto a different storage account. Using the azcopy utility as it appears to be the only way. if there are other ways, please share and show an example.
Azure Blob Storage – is there no UnDelete event availabe?
I’m working with Azure DataFactory as part of churning some backup/restore usecases – looking at event types for Azure Blob Storage for Gen2 storage accounts :
Storage account with private access disabled. 403 when accessing blobs
I have a storage account with a private endpoint and public access disabled (the strictest version possible). The vnet is peered with a hub, in which the private dns zone, and the entry exists. I am storage blob data contributor. To complicate matters further, I use a vpn and have added the ip for the private endpoint and the url into my /etc/hostsfile.
When I want to look at a blob, I get the following error:
Image uploading issue in azure blob storage using SAS token
I’m working on a critical issue regarding image uploading in Azure blob storage using sas token api.
While testing the functionality via Postman, we’ve observed that the image upload process is successful, yielding a status code of 201. However, when attempting the same operation from within our application, although we receive a status code of 201, the image fails to load.
Unable to read from the secondary storage account region
I have an app which connects to a Storage account by using a DefaultAzureCredentials. It is working fine. However if I change the Blob storage account to a secondary: