You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

如何在Azure门户中为Azure Blob容器创建带存储访问策略的共享访问签名

Got it, let's walk through exactly how to create a shared access signature (SAS) tied to a stored access policy for an Azure Blob container right in the Azure Portal. Since you already know the basics of SAS and stored access policies, I'll keep this focused on the portal-specific steps to make this happen:

Step 1: Navigate to your target Blob Container
  • Log into the Azure Portal, search for and select the storage account that hosts your blob container.
  • In the left-hand menu under Data storage, click Containers.
  • Pick the specific container you want to generate the SAS for.
Step 2: Confirm or create your stored access policy

Since you mentioned you already know how to build these, let's align on the portal path:

  • Inside your container, look for Shared access tokens in the left-hand menu (under the Settings section).
  • Scroll to the Stored access policies area:
    • If you already have a policy you want to use, just select it from the list.
    • If you need a new one, click Add policy, give it a clear name, set your desired start/expiry times, check the permissions you want to grant (read, write, delete, etc.), choose allowed protocols (stick to HTTPS for security if possible), then hit Save.
Step 3: Generate the SAS linked to your policy
  • Stay on the Shared access tokens page, and scroll down to the Shared access signature section.
  • Look for the Signed access policy dropdown – select the stored access policy you just created or confirmed.
  • You’ll notice most settings here are pre-filled based on your policy (permissions, expiration, etc.) – double-check these to make sure they match what you need.
  • Click Generate SAS and connection string.
  • Once generated, you’ll see the full SAS token and the container SAS URL. Just copy these directly from the portal to use wherever you need them.

A quick reminder: The big benefit here is that if you ever need to revoke this SAS, you can just modify or delete the linked stored access policy – no need to track individual tokens. Any SAS tied to that policy will stop working immediately once the policy is updated or removed.

内容的提问来源于stack exchange,提问作者Krzysztof Czelusniak

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.20 07:59:18