Skip to content

Azure Blob Storage

Azure Blob Storage keeps application files in containers and lets you choose how often you expect to read them.

Visit Azure Blob Storage

What does an app need before it can save a file to Azure?

Start with an Azure subscription and a storage account. Choose the account’s region and how Azure copies data for redundancy. Create a private container for app files and give the server only the file permissions it needs.

Keep the file’s name or key beside the app record that owns it. Use the Azure SDK to connect from app code or a transfer tool such as AzCopy to move files. The storage account holds the files.

How do you let a customer read one private file?

Have your app check the account’s right to the record first. Its server can issue a short-lived user delegation SAS, a signed permission for one file and the intended action. Microsoft recommends Microsoft Entra credentials for this instead of sharing the storage account key.

Keep the container private and check anonymous access settings. A normal signed link can be forwarded and used while its permissions and expiry allow. If that is unacceptable, have the app check the signed-in account each time it serves the file.

Which costs change if you move files to a cooler tier?

Compare the region and redundancy choices, stored GB over time, request types priced per 10,000, retrieval per GB where it applies and network transfer. Hot is for frequent reads. Cool and Cold are online and trade a lower storage rate for higher access costs.

Archive is offline until Azure moves the object to a readable tier, which can take hours. Budget for retrieval and any early-deletion charges. The general-purpose v2 minimums are 30 days for Cool and 90 days for Cold. Archive has a 180-day minimum.

How would you plan a file restore before connecting Azure?

Draw one fictional PDF and the app record it belongs to. Use paper and no subscription, credentials or real files. Write what would happen on a normal download, after an accidental deletion and during a move.

  1. Trace the owner and an outsider
    Mark which account should get a link. Write why an unrelated account should be refused and what an expired link should do.
  2. Find the copy you could restore
    Write down the file key and when you could recover a soft-deleted file, if that feature is enabled. If the file were in Archive, include the wait before reading it.
  3. List what goes to the next host
    Plan an AzCopy download and include earlier versions only if you need and can retrieve them. Save ownership mappings and access rules separately. Check a copied file and its owner before replacing a link.