DEV Community

Cover image for From Desktop to Cloud: Create Azure Account & Upload Files to Blob in 60 Seconds
Faisal
Faisal

Posted on

From Desktop to Cloud: Create Azure Account & Upload Files to Blob in 60 Seconds

Never uploaded local data to the cloud before? No WORRIES, you landed in the right spot.

Here's exactly how you can upload them in just a few seconds. No More TALKING let's get straight into it.

Here's exactly what you'll do in the next 60 seconds!
You will:

Create Azure free account and upload file to blob storage in 60 seconds guide

Whether you're a developer, student, or just someone who wants their files backed up and accessible from anywhere. This is the starting point. Let's break it down, step by step.

What you need before starting?

You don't need much. Here is the complete checklist:

Requirement Details
An email address Gmail, Outlook, Yahoo - any work Email
A phone number For SMS verification (one time)
A credit or debit card For identity verification only. Microsoft charges $1 temporarily, then refunds. You will not be billed without permission.
A file to upload Any file: CSV, Excel, image, PDF, text. Size under 200MB recommended for speed.
Internet connection Stable enough to load a website

Don't have a test file? Right-click on your desktop -> New -> Text Document -> Name it test-file.txt. That works perfectly.

Checklist Infographic

Part 1: Create Your Free Azure Account (20 Seconds)

Azure gives new users $200 credit valid for 30 days. You also get 12 months of free services. Blob storage falls under free tier for the first 5GB.

Here is exactly how to sign up.

Step 1.1: Go to Azure Portal

Open your browser. Type this address:

Azure Portal

Press Enter. You will see a "Try Azure for free" button. Click it.

Azure Landing Page

Step 1.2: Enter Your Information

ICreate Account

Fill these fields one by one:

Field What to enter
Email address Your personal or work email
Password Minimum 8 characters. Include 1 number and 1 symbol. Example: Azure2026!
Verification code Check your email inbox. Copy the 6-digit code. Paste it.
Phone number Enter with country code. You will receive an SMS code.
Credit card Card number, expiry date, CVV. Verification only.

Important: Microsoft may charge $1 temporarily for verification. It is refunded automatically in 3–5 days.

Step 1.3: Complete Signup

After phone verification, Azure processes your request. Wait 10–15 seconds.

You will see: "Your Azure free account is ready"

Click "Go to Azure Portal".

  • $200 credit for 30 days
  • 12 months free services
  • Full access to blob storage

Azure Welcome HomePage

Part 2: Create Blob Storage Account (20 Seconds)

Now that your account is ready, you need a storage account. Think of this as a digital warehouse where your files will live.

Step 2.1: Search for Storage Account

In the Azure portal, look at the top blue bar. There is a search box with a magnifying glass icon.

Type: storage account

Press Enter.

Search results appear. Click the first result that says "Storage accounts".

Then click the "+ Create" button at the top left.

Blob Storage

Step 2.2: Fill Basics Tab & Click Start Azure Free Trial

You will see a form with multiple tabs: Basics, Advanced, Networking, etc.

Focus only on Basics tab first.

Fill these fields:

Field What to enter Why
Subscription Azure subscription 1 Your free account
Resource group Create new → rg-blob-demo Groups all related resources
Storage account name blob + 3 random numbers Must be unique across Azure
Region Closest location Faster upload speeds
Performance Standard Free tier eligible
Redundancy LRS Lowest cost

Leave all other fields as default.

Create blob resource container

Step 2.3: Configure Advanced Tab (Critical for Fabric)

Click the Advanced tab at the top.

You need to change exactly three settings. Everything else stays default.

Setting From To
Minimum TLS version 1.0 1.2
Hierarchical namespace Disabled Enabled
Blob public access Enabled Disabled
  • TLS 1.2: Required security standard.
  • Hierarchical namespace: Required for Fabric Lakehouse.
  • Blob public access: Keeps files private.

Advanced Settings

Step 2.4: Review and Create

Click the Review + create tab at the top.

Azure validates your settings. You should see:

"Validation passed"

Scroll to the bottom. Click the blue Create button.

Wait 20–30 seconds.

You will see:

"Your deployment is complete"

Click the blue Go to resource button.

Go to Resources

Part 3: Create Container (15 Seconds)

A container is like a folder. It holds your files. You can create multiple containers for different projects.

Step 3.1: Open Containers Menu

You are now on your storage account overview page.

Look at the left sidebar. Find the section labeled "Data storage".

Click "Containers".

Step 3.2: Create New Container

Click the "+ Container" button at the top.

A popup window appears.

Create Container

Fill these two fields:

Field Value Rule
Name my-data Lowercase only. No spaces. Use dashes.
Public access level Private No anonymous access. Only you can read files.

Click the blue "Create" button.

The popup closes. Your new container appears in the list.

Fill the container Fields

Part 4: Upload Your File (5 Seconds)

The final step. Your file goes from desktop to cloud.

Step 4.1: Click Into Container

Click on your container name my-data from the list.

You are now inside the container. It is empty.

Step 4.2: Upload File

Click the "Upload" button at the top.

A popup appears.

Click "Browse for files" (or "Select a file").

Navigate to your desktop. Select your file.

Optional but recommended: Click "Advanced". Set "Block size (MB)" to 4.

This optimizes uploads for files under 200MB. Then click the blue "Upload" button.

Upload file to Blob

Step 4.3: Verify Upload Success

After upload completes, the popup closes.

Your file now appears in the container list.

Check these three things:

Check What to see
File name Your file name appears in the list
Size File size matches original
Status No error messages or red text

Congratulations. Your file is now in Azure Blob Storage.

Uploaded Successfully

The 60 Second Breakdown (Proof)

Here is exactly where those 60 seconds went:

60 Sec Breakdown

Step Action Actual Time
1 Create Azure free account 20 seconds
2 Create blob storage account 20 seconds
3 Create container 15 seconds
4 Upload file 5 seconds
Total Complete 60 seconds

Note: Typing speed varies. If you read slowly or double-check fields, add 30 seconds. First-time users may take 90–120 seconds, which is still fast.

Top comments (2)

Collapse
 
scsoi profile image
疏影 •

Quick Azure Blob walkthrough. From the '60 seconds later, how do I actually use this on a Windows desktop?' angle, two patterns we use:

  • Mount Azure Blob as a drive letter on Windows (S3-compatible API in front of Blob, or Azure's own Files / Blob NFS). ScsDriver handles SMB / S3 / SFTP / WebDAV so the same mount table also carries the team's regular SMB share and the cold backups. Auto-reconnect across sleep / VPN / 网卡切换 is what made the daily 'why is my drive gone' tickets stop.
  • Pair Blob (cheap cold storage) with Azure Files SMB (for the active share). Both can be mounted side-by-side via the same client — one mount table, two cost profiles. The active share is hot + daily-mount, the Blob bucket is cold + occasional-mount (audits / restores).

A few operational notes for the 60-second Azure setup:

  • RBAC for the storage account is the most common stumbling block; least-privilege on the storage account + container SAS for the desktop client is a good baseline.
  • If you're also piping this into a NAS (SMB), mind the 'multiple connections to server' default on Windows; using distinct service accounts per destination side-steps it.
  • For cost, archive tier on Blob is great for the second copy; restore SLA should be picked before cost is. Nice quickstart.
Collapse
 
scsoi profile image
疏影 •

Great intro for the 60-second path, but the production reality has more moving parts. Three things we always add to a fresh Blob container:

  1. Soft delete on by default, retention 14 days — easy to skip, painful when needed. We have a CI rule that fails if a new container ships without soft delete configured.

  2. Versioning + blob-level immutable policy — legal/compliance teams always want "cannot delete for N days" once they learn the feature exists. Policy scoped to prefix (e.g. only invoices/) is the right starting point; container-wide immutability locks the bucket in ways you usually do not want.

  3. Lifecycle rule for last access tracking — newer tiers in Blob track last-access time and automatically move cold data. Once it is on, you stop paying for old test data sitting at hot tier for years.

For ops who would rather not run Azure CLI for every quick copy, mounting the container as a drive letter on Windows is the most friction-free option — Explorer drag-and-drop works, including into Azure File Shares.

Mount layer: ScsDriver