Duration
1 day
Overview
Most organizations have diverse requirements for their cloud-hosted data. For example, storing data in a specific region, or needing separate billing for different data categories. Azure storage accounts let you formalize these types of policies and apply them to your Azure data.
Suppose you work at a chocolate manufacturer that produces baking ingredients such as cocoa powder and chocolate chips. You market your products to grocery stores who then sell them to consumers.
Your formulations and manufacturing processes are trade secrets. The spreadsheets, documents, and instructional videos that capture this information are critical to your business and require geographically redundant storage. This data is primarily accessed from your main factory, so you would like to store it in a nearby datacenter. The expense for this storage needs to be billed to the manufacturing department.
You also have a sales group that creates cookie recipes and baking videos to promote your products to consumers. Your priority for this data is low cost, rather than redundancy or location. This storage must be billed to the sales team.
By creating multiple Azure storage accounts, with each one having the appropriate settings for the data it holds, you can handle these types of business requirements.
Learning Objectives
In this module, you will:
- Decide how many storage accounts you need for your project.
- Determine the appropriate settings for each storage account.
- Create a storage account using the Azure portal.
Outline
- Decide how many storage accounts you need
- What is Azure Storage?
- What is a storage account?
- Storage account settings
- How many storage accounts do you need?
- Data diversity
- Cost sensitivity
- Tolerance for management overhead
- Choose your account settings
- Name
- Deployment model
- Account kind
- Choose an account creation tool
- Available tools
- How to choose a tool
- Exercise - Create a storage account using the Azure portal
- Create a storage account using Azure portal
Summary
Storage accounts let you create a group of data management rules and apply them all at once to the data stored in the account: blobs, files, tables, and queues.
If you tried to achieve the same thing without storage accounts, the end product would be tedious and error-prone. For example, what are the chances that you could successfully apply the same rules to thousands of blobs?
Instead, you capture the rules in the settings for a storage account, and those rules are automatically applied to every data service in the account.
Programme scope, delivery arrangements and suitability are confirmed during enquiry.