Skip to content

Commit 92ba061

Browse files
authored
Merge pull request #102968 from xyh1/patch-100
Update storage-lifecycle-management-concepts.md
2 parents f4aca37 + 22cfdd7 commit 92ba061

File tree

3 files changed

+7
-6
lines changed

3 files changed

+7
-6
lines changed
11 KB
Loading

articles/storage/blobs/storage-lifecycle-management-concepts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -344,9 +344,9 @@ This example shows how to transition block blobs prefixed with `container1/foo`
344344
}
345345
```
346346

347-
### Archive data at ingest
347+
### Archive data after ingest
348348

349-
Some data stays idle in the cloud and is rarely, if ever, accessed once stored. The following lifecycle policy is configured to archive data once it's ingested. This example transitions block blobs in the storage account within container `archivecontainer` into an archive tier. The transition is accomplished by acting on blobs 0 days after last modified time:
349+
Some data stays idle in the cloud and is rarely, if ever, accessed once stored. The following lifecycle policy is configured to archive data shortly after it is ingested. This example transitions block blobs in the storage account within container `archivecontainer` into an archive tier. The transition is accomplished by acting on blobs 0 days after last modified time:
350350

351351
> [!NOTE]
352352
> It is recommended to upload your blobs directly the archive tier to be more efficient. You can use the x-ms-acess-tier header for [PutBlob](https://docs.microsoft.com/rest/api/storageservices/put-blob) or [PutBlockList](https://docs.microsoft.com/rest/api/storageservices/put-block-list) with REST version 2018-11-09 and newer or our latest blob storage client libraries.

articles/storage/blobs/storage-quickstart-blobs-portal.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -41,13 +41,14 @@ To upload a block blob to your new container in the Azure portal, follow these s
4141

4242
1. In the Azure portal, navigate to the container you created in the previous section.
4343
2. Select the container to show a list of blobs it contains. Since this container is new, it won't yet contain any blobs.
44-
3. Select the **Upload** button to upload a blob to the container.
45-
4. Browse your local file system to find a file to upload as a block blob, and select **Upload**.
44+
3. Select the **Upload** button to open the upload blade
45+
4. Browse your local file system to find a file to upload as a block blob
4646

4747
![Screenshot showing how to upload a blob from your local drive](media/storage-quickstart-blobs-portal/upload-blob.png)
4848

49-
5. Select the **Authentication type**. The default is **SAS**.
50-
6. Upload as many blobs as you like in this way. You'll see that the new blobs are now listed within the container.
49+
5. Optionally, expand the advanced section to define other setting such as authentication type, access tier, or virtual folder path.
50+
6. Select the **Upload** button to commit the upload
51+
7. Upload as many blobs as you like in this way. You'll see that the new blobs are now listed within the container.
5152

5253
## Download a block blob
5354

0 commit comments

Comments
 (0)