Introduction
That container that group all azure storage services together is termed azure storage account. It is one of the foundational services provided by Microsoft Azure, that offers a highly scalable and secure platform to store a wide variety of data types in the cloud. It serves as a centralized repository for many data storage needs and is composed of many storage services such as:

Blob Storage: Ideal for storing massive amounts of unstructured data like text, images, videos, and other binary data. Blob Storage supports three access tiers (Hot(data that is used regularly), Cool(used within 30days period), and Archive(used 180days) to cater to different data access patterns and cost requirements.
File Storage: Provides fully managed file shares in the cloud, enabling traditional file storage scenarios. Azure Files allows the use of Server Message Block (SMB) protocol for accessing shared files across multiple machines.
Queue Storage: Offers a message queueing system that allows communication between different components of an application or system. Azure Queue Storage facilitates asynchronous communication and decouples components for better scalability and reliability.
Table Storage: A NoSQL key-value store suitable for semi-structured data. It allows for fast querying of large datasets and is an excellent choice for applications that require flexible schema and massive scalability.
Disk Storage: Azure Disk Storage provides block storage to support the persistent storage needs of Azure Virtual Machines (VMs). It includes both managed and unmanaged disks and offers various disk types optimized for different workloads

The storage account can be accessible anywhere in the world over HTTP or HTTPS.

Guide to create Storage Account through Azure portal
There are various ways to create Azure storage account i.e. Azure portal, Azure CLI (Command-line interface), Azure PowerShell and
Management client libraries. However, we are focusing on the first.

Step 1

Sign in to Azure Portal: Access the Azure Portal using your credentials at https://portal.azure.com/. If you don't have one, create a free account.

Step 2
On Window web browser, search for storage account:

Step 3
On the Basics Tab, the first item is the Project Details and Instance details. The project details contains the Subscriptions and the Resource group.
The Subscription allows you to determine which subscription will be billed for the resources consumed by the storage account.
While Resource Group allows you to organize and manage the storage account along with other related resources under a common grouping for administrative, billing, and lifecycle management purposes.

The Instance details contains information such as Storage account name, Region, Performance and Redundancy.

Storage Account Name: This is a unique name that identifies your Azure Storage Account. It must be a globally unique name across Azure.

Region: Also known as the Azure Region or Location, this is the geographical region where your storage account's data will be stored. optimal performance or based on compliance requirements.

Performance: Azure Storage Accounts offer different performance tiers based on your workload requirements. These tiers may include Standard and Premium options, each providing different performance characteristics and pricing. e.g.
Standard: This tier offers reliable, high-performance storage designed to provide cost-effective solutions for various storage scenarios. It includes options for Blob storage, File storage, Queue storage, and Table storage. It is used when there is need to save money.

Premium: This tier offers high-performance, low-latency storage(low data traveling period) suitable for I/O-intensive workloads. It's often used for scenarios requiring high transaction rates and low latency, such as virtual machine disks.

Redundancy: Redundancy options determine how your data is replicated within Azure Storage to ensure high availability and data durability. Azure provides several redundancy options:

Locally Redundant Storage (LRS): Copies data synchronously within a single storage scale unit in a data center. It provides redundancy against hardware failures.

Zone-Redundant Storage (ZRS): Replicates data across multiple availability zones within a region, offering higher durability against data center outages.

Geo-Redundant Storage (GRS): Replicates data to a secondary region at least hundreds of miles away from the primary location, providing data residency and high durability against regional outages. This is the most reliable and expensive.

Step 4

On the Advanced Tab:
Note: If the storage account you want to create is for your enterprise/private account, do not click or activate the Allow enabling anonymous access on individual containers

Leave every other tabs and click on review and create. Note: The deployment must be allowed to complete.

The storage account is now created:

Now, let us take a critical look at the Data Storage types here:
Containers: This is used to store all Blob. For us to store any data here, we need to create the container where it will be uploaded. The container acts like a bow inside which our data will stay.
So, click on this to create one:

Then click on + Containers:

You can see that the drop down is not activated because our storage account is local not for public. If we upload any data into this container, we will be unable to share it with the public.

Step 5

How do we upload into the container?

1. Click on the name of container created and 2. Click upload:

The data name storage logo has been loaded into the container.

Now, we need to test if this can be shared with the public:
Click on the data(storage logo)

Below is the error message:

Step 6
We will create another account and make it public and see the effect

On Basics Tab:

On Advanced Tab:

Next, leave other tabs and go to review and create:

Now we can modify to select image e.g Blob and this can be shared to the public:

Next, click on the container and upload same picture to see the outcome:

Conclusion
From the foregoing, we can see that it is easy to create Azure storage for our data. It is more easier to create container to keep the data. We can equally make the data available to the public and enterprise depending on our needs.
Your comment(s) is needed for improvement.