azure:az-104_2024:storage_access

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
azure:az-104_2024:storage_access [2024/10/03 12:47] – ↷ Page moved from azure:storage_access to azure:az-104_2024:storage_access mmuzeazure:az-104_2024:storage_access [2024/10/08 19:21] (current) – [Blob Storage Access] mmuze
Line 1: Line 1:
 ====== Storage Access ====== ====== Storage Access ======
-  * Blob Storage Access +===== Blob Storage Access =====
 There are multiple ways to access //blob// storage. [[https://learn.microsoft.com/en-us/azure/storage/blobs/authorize-data-operations-portal|Ref.]] \\ There are multiple ways to access //blob// storage. [[https://learn.microsoft.com/en-us/azure/storage/blobs/authorize-data-operations-portal|Ref.]] \\
 👉 One way is to use the **account access key**. [[https://learn.microsoft.com/en-us/azure/storage/blobs/authorize-data-operations-portal#use-the-account-access-key|Ref.]] //This method should not be generally used, because it gives an all-powerful level of access.// 👉 One way is to use the **account access key**. [[https://learn.microsoft.com/en-us/azure/storage/blobs/authorize-data-operations-portal#use-the-account-access-key|Ref.]] //This method should not be generally used, because it gives an all-powerful level of access.//
Line 12: Line 11:
   * By default a **SAS** is created based on the account access keys and can only be revoked by rotating the access keys used to generate it. But that could affect other things that were using the key, so it's not ideal.   * By default a **SAS** is created based on the account access keys and can only be revoked by rotating the access keys used to generate it. But that could affect other things that were using the key, so it's not ideal.
   * Alternatively, an **Access Policy** can be created and used to create the **SAS**. After that the **SAS** can be revoked by deleting the policy. This will only affect other things that use the policy.   * Alternatively, an **Access Policy** can be created and used to create the **SAS**. After that the **SAS** can be revoked by deleting the policy. This will only affect other things that use the policy.
 +  * SAS can be assigned at the account or service level.
  
  
  • azure/az-104_2024/storage_access.1727959644.txt.gz
  • Last modified: 2024/10/03 12:47
  • by mmuze