Prototyping different storage scenarios for an IT department in Azure Portal.
Tags: azure, storage
Published: 2024-05-26 15:38:51

---
title: Prototyping different storage scenarios for an IT department in Azure Portal.
published: true
description: creating and configuring a storage account.
tags: azure, storage
cover_image: https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qro8jkedn7euqk6dhm7m.jpg
# Use a ratio of 100:42 for best results.
# published_at: 2024-05-20 17:32 +0000
---



#Introduction

In this post, I'll walk you through the process of providing Storage for a fictitious IT department, in the Azure portal. For the department, the data isn’t important enough to back up and doesn’t need to be restored if the data is overwritten or removed. 

##Prerequisites 

Before we start, you'll need a Microsoft Account and an Azure free trial account. I covered opening a free trial account [here](https://dev.to/tundeiness/setting-up-a-windows-11-virtual-machine-with-azure-on-a-macos-88m)


###Step 1: Creating a resource group
Go to the Azure Portal Dashboard, and at the search bar - at the top level of the page - search and select Resource groups. This navigates to another page. While on that page select **+ create**. On the next page, you are required to name your resource group. Go ahead and name your resource group. Then select a region. At the bottom of the page select the **Review + create** button to validate the resource group.
Select the 'create' button to deploy the resource group. The image below shows the created resource group.

![resource group](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/paw1c5s7qbh5yw1f994l.png)


###Step 2: Creating and deploying a storage account

On the page of the resource group and the search bar - at the top level of the page - search and select Storage Accounts. 
![search bar step 1](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/rnibcf4jfrrby84hp8vl.png)

![storage](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3mbj5kfdw8lx25z1ksu9.png)

This navigates to another page. While on that page select **+ create** at the upper left of the page or click on the **create storage account** button on that page.

![options to creating storage account](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/b9lqgzfkr72zifc99plr.png)

This next page has 6 Tabs namely **Basics**, **Advanced**, **Networking**, **Data protection**, **Encryption**, **Tags** and **Review + create**.

![Tabs](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/bk6zhg5k54v02jbvqj15.png)

At the **Basics** tab, select the **Resource group** label under the **project details** section and select the Resource group created in Step 1. 
![resource group](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ef2tzhrx52yvbruqu7tk.png)

Next, Under the **Instance details** section, give the storage account a unique name, select the (US)East US option at the **Region** label, and for the **Performance** label, select the **standard** radio button. 
![Storage name](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/kxh8pw8qq8k5fxnkrhd4.png)

![Region](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/8cih7obzetem7a3nv7cm.png)

![Performance](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/xp0biyuk8if1bghqv0hd.png)

Accept the default **Redundancy** label option as shown. Afterward, select the **Review + create** button on the page and subsequently the "Create" button.

![validating in progress](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/z9khjnoinvjkzvzlmw19.png)

![create](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/v5fylj7174262zc77fnh.png)

Wait for the storage account to **deploy**. 
![deployment in progress](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/fa08ffzzqdzpkpfufgdf.png)
![deployment in progress II](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/wz3flavar0eibmcc77hu.png)
After successfully deploying, click the **go to resource** button.
 ![go to resources](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2fjwzrlcgv7b0w9y162x.png)

###Step 3: Configure settings in the Storage Account.

####I: Data in this storage account does not need to be highly available.

We want to configure this storage account with the most basic settings. We don't have to worry if data isn't highly available. To do this, select **Data Management** at the left-hand side of the page and the **Redundancy** blade.

![Data Management](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/t3o72tjkmzlekqojrfgs.png)

![Redundancy](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9j2unqqrqpi7mat5maxr.png)

![Redundanncy part 2](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/d4t6t8wxrh7fvpwkw8ra.png)

Select the **Locally redundant Storage** (LRS) option from the **Redundancy** label. The reason for this is that "the data isn’t important enough to back up and doesn’t need to be restored if the data is overwritten or removed". As a result, High availability isn't required. This means the redundancy can take the least available option which is **Locally redundant Storage**.
![Locally redundant Storage](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/08dvekrijfwshs8z17lp.png)
Click **save** at the top of the page.

![save](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/pri0ho9lumw6wvrt6a6k.png)

Previously, 2 locations may have shown up on the map displayed on this page. However, since we selected the **Locally redundant Storage** (LRS) option from the **Redundancy** label, only one location will be displayed on the map. Refresh the page if this isn't displaying.

![redundancy changes](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/0ib6momx98tifnddaci6.png)

####II: Storage account should only accept requests from secure connections.

The next configuration to set is to make the Storage account only accept requests from secure connections. To do this, follow these steps:

- Locate **settings** at the left-hand side of the page, and select 
![Settings](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/i7226uwc4orpafc2t6jn.png)
the  **Configuration** blade. 

![Configuration blade](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/guw4j3jqpd2wk2m1nk17.png)

- At the page displayed, confirm that **Secure Transfer required** is **Enabled**
![Secure Transfer](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/8fosxky3ejh475i76vlu.png)

####III: Storage account should use a TLS version.
For the Storage account to use a TLS version, 
- go to **settings**
![Settings](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/i7226uwc4orpafc2t6jn.png)
- select **configuration** blade,
![Configuration blade](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/guw4j3jqpd2wk2m1nk17.png)
-Then, set **Minimal TLS Version** to **version 1.2**

![Minimal TLS Version](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2xba2z2z5t9ayl6anpx9.png)

####IV: Request to the storage account is disabled until needed
For disabling requests to the storage account until required,
- Select **Settings**, then
![Settings](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/i7226uwc4orpafc2t6jn.png)
- Select the **Configuration** blade.
![Configuration blade](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/guw4j3jqpd2wk2m1nk17.png)
- In the **Allow Storage Account key access** label, select the **Disabled** radio button.
![Allow Storage Account key access](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/99ll1hgr2qlteiyncpwg.png)
- Select the **Save** icon at the top level of the page.


####V: Allow Storage Account to permit public access from all Networks.

For the last configuration in this task which is to permit public access from all Networks, follow the steps listed below:

- At the left-hand side of the storage account page, select **Security + networking** 
![Security + networking](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/1gue737bcm0bluhdjoiv.png)
- Select the **Networking** blade
![Networking](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/yftivd7mc61uh9wlbnal.png)
- set **Public network access** to **Enabled from all network**

![Public network access](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/wk5s8vwwelnb20hllyn0.png)
- Click the **Save** icon of the page to save the changes. 


#Conclusion

To avoid unnecessary charges, delete your resource group if you will not be using it. You can do this from the Azure portal by navigating to your Resource group and clicking the "delete resource group" button.
In this post, we successfully created a Resource group which is a container for our storage account. We adjusted some basic settings for the storage account and saved these settings. Remember to monitor your usage to stay within the free tier limits and delete resources when they are no longer needed. Stay tuned for more posts on cloud development with Azure!



Cover Image by <a href="https://unsplash.com/@markusspiske?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Markus Spiske</a> on <a href="https://unsplash.com/photos/black-and-gray-laptop-computer-turned-on-FXFz-sW0uwo?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Unsplash</a>