Storage Utilities

Azure provides powerful utilities to manage:

• Azure Storage

including:

• Blob Storage
• Azure Files
• Queues
• Tables

The two primary tools are:

• 1️⃣ Azure Storage Explorer (GUI) 2️⃣ AzCopy** (CLI)**
• There is also a lightweight portal tool called Storage Browser.

1️⃣ Storage Browser (Portal-Based Tool)#

• Built into Azure Portal.

Features:

• ✔ View containers ✔ View file shares ✔ Basic upload/download ✔ Simple management

Limitations:

• ❌ Limited performance ❌ Not ideal for bulk operations ❌ Limited automation

Best for:

• Quick inspection
• Small operations
• Troubleshooting

2️⃣ Azure Storage Explorer (GUI Tool)#

Official tool:

• Azure Storage Explorer

Documentation:

Supported OS:

• Windows
• macOS
• Linux

🔹 What Storage Explorer Does#

• ✔ Connect to subscriptions ✔ Connect to individual storage accounts ✔ Upload/download blobs ✔ Manage file shares ✔ Generate SAS tokens ✔ Create snapshots ✔ Manage access policies ✔ Copy/clone containers ✔ View queues & tables

It uses:

• 👉 AzCopy** internally for data transfer**

So it is:

• GUI wrapper over AzCopy.

🔹 Connection Methods#

You can connect via:

• Azure subscription (Entra login)
• Connection string
• SAS URL
• Storage account name + key

Best practice:

• Use Microsoft Entra ID authentication when possible.

🔹 Key Capabilities Demonstrated#

In the lesson:

• Connected via account name + key
• Viewed blob containers
• Uploaded/downloaded blobs
• Managed file shares
• Created snapshots
• Generated SAS
• Managed stored access policies
• It mirrors portal functionality — but more powerful.

3️⃣ AzCopy (Command Line Tool)#

Official tool:

• AzCopy

Documentation:

AzCopy is:

• ✔ High-performance CLI tool ✔ Optimized for bulk transfers ✔ Scriptable ✔ Automation-friendly ✔ Cross-platform

🔹 Why Use AzCopy?#

Best for:

• Large data migrations
• Backup operations
• Automation scripts
• CI/CD pipelines
• DevOps workflows
• Scheduled jobs

4️⃣ AzCopy Authentication Methods#

You can authenticate using:

1️⃣ Microsoft Entra ID (Recommended)#

Command:

• azcopy login

Prompts:

• Browser authentication
• Device code login
• Best practice: use identity-based authentication.

2️⃣ SAS Token#

• Used for temporary scoped access.

Example:

• azcopy copy "source" "destination?SAS"

3️⃣ Account Key#

Provides full access.

Less secure.

5️⃣ AzCopy Common Commands#

🔹 Create Container#

azcopy make "https://account.blob.core.windows.net/container"

🔹 Upload File#

azcopy copy "localfile.txt" "https://account.blob.core.windows.net/container"

🔹 Download File#

azcopy copy "https://account.blob.core.windows.net/container/file" "localpath"

🔹 Sync (Very Powerful)#

• azcopy sync "source" "destination"

Sync supports:

• ✔ Incremental updates ✔ Efficient delta transfers

6️⃣ AzCopy Performance Features#

AzCopy includes:

• ✔ Parallel transfers ✔ Resume support ✔ Chunked uploads ✔ Large file support (TB-scale) ✔ High-throughput optimization

It is designed for:

• Enterprise-scale data movement.

7️⃣ Storage Explorer vs AzCopy#

8️⃣ Security Considerations#

When using these tools:

✔ Prefer Entra ID login ✔ Avoid hardcoding access keys ✔ Use SAS for limited sharing ✔ Rotate keys regularly ✔ Restrict network access

9️⃣ Where These Tools Fit in Architecture#

Developer Workflow#

Local machine → AzCopy → Blob container

Migration Scenario#

On-prem server → AzCopy → Azure Storage

Admin Management#

Storage Explorer → Manage blobs/files visually

CI/CD Pipeline#

Pipeline script → AzCopy → Upload artifacts

🔟 Enterprise Data Migration Pattern#

Large migration example:

• On-prem file server ↓ AzCopy recursive upload ↓ Azure Blob or Azure Files ↓ Validate integrity

AzCopy supports:

• Recursive copy
• Filtering
• Pattern matching
• Log output

11️⃣ Advanced AzCopy Capabilities#

• ✔ Cross-account copy ✔ Cross-region copy ✔ Cross-tenant copy ✔ Resume failed transfers ✔ Generate transfer logs

You can copy directly:

• Azure → Azure Without downloading locally.

12️⃣ Common Exam Pitfalls#

🚩 Storage Explorer is required → False 🚩 AzCopy supports Entra login → True 🚩 AzCopy only works on Windows → False 🚩 Storage Explorer uses AzCopy internally → True 🚩 Portal is best for bulk data migration → False

13️⃣ When to Use Each Tool#

Use Storage Explorer when:

✔ You need a visual interface ✔ You are browsing data ✔ You need quick management

Use AzCopy when:

✔ You are migrating TBs of data ✔ You need automation ✔ You need CI/CD integration ✔ You want performance

14️⃣ Best Practice Recommendations#

✔ Use Entra ID authentication ✔ Add AzCopy to system PATH ✔ Store credentials securely ✔ Use SAS for temporary access ✔ Log and monitor transfers ✔ Test transfers before production migration

15️⃣ Real-World Enterprise Example#

Scenario:

• Company migrating 50 TB to Azure.

Solution:

• Install AzCopy
• Authenticate with Entra ID
• Run recursive copy
• Monitor logs
• Validate checksums
• This is far superior to manual upload.

Final Summary#

Azure Storage Utilities include:

• 🔹 Storage Browser (basic portal tool) 🔹 Azure Storage Explorer (GUI client) 🔹 AzCopy (high-performance CLI tool)
• Storage Explorer uses AzCopy under the hood.

AzCopy is preferred for:

• Automation
• Large transfers
• Enterprise workloads
• Together, they provide both user-friendly and scriptable methods for managing Azure Storage.

If you'd like next:

• 🧠 AZ-104 exam questions on storage utilities
• 🚀 Full data migration strategy blueprint
• 🔐 Secure AzCopy authentication patterns
• 📊 Performance tuning guide for AzCopy
• 🏗 DevOps pipeline integration example
• Tell me your focus (exam prep, migration, automation, or architecture).