11 KiB
lab
| lab | ||||
|---|---|---|---|---|
|
Lab 07 - Manage Azure Storage
Estimated timing: 40 minutes
Lab scenario
Your organization is currently storing data in on-premises data stores. The majority of these files are not accessed frequently. You would like to minimize the cost of storage by placing infrequently accessed files in lower-priced storage tiers. You also plan to explore different protection mechanisms that Azure Storage offers, including network access, authentication, authorization, and replication. Finally, you want to determine to what extent Azure Files is suitable for hosting your on-premises file shares.
Interactive lab simulations
There are interactive lab simulations that you might find useful for this topic. The simulation lets you to click through a similar scenario at your own pace. There are differences between the interactive simulation and this lab, but many of the core concepts are the same. An Azure subscription is not required.
-
Create blob storage. Create a storage account, manage blob storage, and monitor storage activities.
-
Manage Azure storage. Create a storage account and review the configuration. Manage blob storage containers. Configure storage networking.
Architecture diagram
Tasks
- Task 1: Create and configure a storage account.
- Task 2: Implement secure blob storage.
- Task 3: Provide limited access to blob storage.
Task 1: Create and configure the private storage account.
In this task, you will create and configure a storage account.
-
Sign in to the Azure portal -
http://portal.azure.com. -
Search for and select Storage accounts, and then click + Create.
-
On the Basics tab of the Create storage account blade, specify the following settings (leave others with their default values):
Setting Value Subscription the name of your Azure subscription Resource group az104-rg7 (create new) Storage account name any globally unique name between 3 and 24 in length consisting of letters and digits Region East US Performance Standard (notice the Premium option) Redundancy Geo-redundant storage (notice the other options) Make read access to data in the event of regional availability Check the box -
On the Advanced tab, review the available options, accept the defaults.
-
On the Networking tab, review the available options, select Private (no anonymous access).
-
Review the Data protection tab. Notice 7 days is the default soft delete retention policy. Accept the defaults
-
Review the Encryption tab. Notice the additional security options. Accept the defaults.
-
Select Review, wait for the validation process to complete and then click Create.
-
Once the storage account deploys, Go to resource.
-
Review the Overview blade and the additional configurations that can be changed.
-
Notice in the Data storage section, this storage account can be used for Blob containers, File shares, Queues, and Tables.
-
In the Data management section, view the Redundancy blade. Notice the information about your primary and secondary data center locations.
-
In the Data management section, select Lifecycle management, and then select Add rule.
-
Name the rule
Movetocool. Notice your options for limiting the scope of the rule. -
On the Base blobs tab, if based blobs were last modified more than
30 daysago then move to cool storage. -
Notice you can configure other conditions. Select Add when you are ready to create the rule.
Task 2: Manage blob storage
In this task, you will create a blob container and upload a blob into it. Blob containers are directory-like structures that store blobs (unstructured data) in the storage account.
- Continue working with your storage account.
Create a blob container and a time-based retention policy
-
In the Data storage section, click Containers.
-
Click + Container and Create a container with the following settings:
Setting Value Name dataPublic access level Private (no anonymous access) -
Select your container and in the Sectings section, select Access Policy.
-
In the Immutable blob storage area, select Add policy.
Setting Value Policy type Time-based retention Set retention period for 90days -
Select Save.
Manage blob uploads
-
Select your data container and then click Upload.
-
On the Upload blob blade, expand the Advanced section.
Note
: Locate a file to upload. This can be any type of file, but a small file is best.
Setting Value browse for files add the file you have selected to upload Blob type Block blob Block size 4 MB Access tier Hot (notice the other options) Upload to folder securitytest Note
: Access tiers can be set for individual blobs.
-
Click Upload.
-
Confirm you have a new folder and your file was uploaded.
-
Select your upload file and review the options including Download, Delete, Change tier, and Acquire lease.
-
Copy the file URL and paste into a new Inprivate browsing window.
-
You should be presented with an XML-formatted message stating ResourceNotFound or PublicAccessNotPermitted.
Note
: This is expected, since the container you created has the public access level set to Private (no anonymous access).
Configure limited access to the blob storage
-
Return to your uploaded file and select the Generate SAS tab. Specify the following settings (leave others with their default values):
Setting Value Signing key Key 1 Permissions Read Start date yesterday's date Start time current time Expiry date tomorrow's date Expiry time current time Allowed IP addresses leave blank -
Click Generate SAS token and URL.
-
Click Copy to clipboard button next to the Blob SAS URL entry.
-
Open another browser window by using InPrivate mode and navigate to the URL you copied in the previous step.
Note
: You should be able to view the content of the file by downloading it and opening it with Notepad. If you receive a Windows SmartScreen error, continue to the page.
Task 5: Create and configure an Azure Files shares
In this task, you will create and configure Azure Files shares.
Create the files share and upload a file
-
In the Azure portal, navigate back to the blade of the data storage account, in the Data storage section, click File shares.
-
Click + File share and on the Basics tab give the file share a name,
share1. Review the other settings on this tab. -
Move to the Backup tab, and ensure Enable Backup is not checked.
-
Click Review and create, and then Create. Wait for the file share to deploy.
Explore Storage Browser and upload a file.
-
Return to your storage account, and select Storage Browser.
-
Select File shares, and verify your share1 directory is present. Notice you can + Add directory.
-
Select your share1 directory and Upload a file of your choosing.
-
Select Upload. Browse to a file of your choice, and then click Upload.
Note
: You are able to view file shares and manage those shares in the Storage Browser. There are currently no restrictions.
Restrict network access to the storage account
-
In the poratal, search for and select Virtual networks.
-
Select Create. Select your resource group. and give the virtual network a name.
-
Take the defaults for other parameters, select Review + create, and then Create.
-
Wait for the resource to deploy, and then select Go to resource.
-
In the Settings section, select the Subnets blade.
- Select the default subnet.
- In the Service endpoints section choose Microsoft.Storage in the Services drop-down.
- Do not make any other changes.
- Be sure to Save your changes.
Note: The storage account should now only be accessed from the virtual network you just created.
-
Return to your data storage account.
-
In the Security + networking section, select the Networking blade.
-
Change the Public network access to Enabled from selected virtual networks and IP addresses.
-
In the Virtual networks section, select Add existing virtual network.
-
Select the new virtual network and subnet, select Add.
-
Be sure to Save your changes.
-
Select the Storage browser and Refresh the page. Navigate to your file share or blob content.
Note: You should receive a message not authorized to perform this operation. You are not connecting from the virtual network. It may take a couple of minutes for this to take effect.
Review the main points of the lab
Congratulations on completing the lab. Here are the main takeaways for this lab.
- An Azure storage account contains all of your Azure Storage data objects: blobs, files, queues, and tables. The storage account provides a unique namespace for your Azure Storage data that is accessible from anywhere in the world over HTTP or HTTPS.
- Azure storage provides several redundancy models including Locally redundant storage (LRS), Zone-redundant storage (ZRS), and Geo-redundant storage (GRS).
- Azure blob storage allows you to store large amounts of unstructured data on Microsoft's data storage platform. Blob stands for Binary Large Object, which includes objects such as images and multimedia files.
- Azure file Storage provides shared storage for structured data. The data can be organized in folders.
- Immutable storage provides the capability to store data in a write once, read many (WORM) state. Immutable storage policies an be time-based or legal-hold.
Cleanup your resources
If you are working with your own subscription take a minute to delete the lab resource group. This will ensure resources are freed up and cost is minimized.



