Azure Storage Account - Container cambia access level in automatico

Maybe, i found the "problem"...
Some months ago, i enabled the backup on this container within the storage account, and i set the georeplica.

It seems there is a policy that restore the access level when the replica syns run.
I found it with:

az storage account or-policy list --account-name <account_name> --resource-group <resource_group> -o json

ChatGTP says this is the "guilty".
I have also another storage account with a separate coninter and the same backup enabled but without georeplicas and i don't notice this behavior.
Do you think this is could be right?
Thanks

Hello Ducarpit

you can check this over Activity log in the azure portal.

1. Open Azure Portal
2. Go to your Storage Account
3. In the left pane → Monitoring → Activity log
4. 

• In the above screenshot go for Operation name
• Click on Update Storage account Create.
• 
• Next, go to change history where you can view the resource updates.
• Click on Resource Update to see the change logs and who made the updates.
• Then check the properties to see who made the changes or see if there is any policy in place.
• 

NOTE: Confirm that your storage account configuration aligns with your intended access policies, especially considering anonymous access settings.

To figure out what's causing the changes to the access level, you should review the storage analytic blob logs for any calls made to the Set Container ACL API. This API tracks who made the changes, along with details like user agent and client IP address.

References:

• Configuring Anonymous Read Access for Containers and Blobs
• Azure RBAC Documentation
• Access Control in Azure Data Lake Storage Gen2

Hope the above answer helps! Please let us know do you have any further queries.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".