When I opened the Azure Portal for the first time, my first instinct wasn’t curiosity. It was panic.
There were hundreds of services. Compute. Storage. Networking. DevOps. Identity. Containers. Things I had never used. Things I didn’t fully understand. Things I didn’t even know existed.
It felt less like opening a tool and more like opening control panel for the internet itself. Up until now, my mental model of deployment was simple.
- I build something in React or Node.
- I push to GitHub.
- I connect it to Vercel.
- I click deploy.
- It works.
My app is live. End of story. Yay.
I never really questioned what happened after that.
Not because I didn’t care, but because I didn’t need to.
Platforms like Vercel are designed to remove friction. They hide infrastructure. They give you a clean interface where deployment feels instant and effortless.
But that abstraction also hides something important: the system underneath.
Azure doesn’t hide the system. It exposes it.
And that’s when I realized how small my world had been.
Before this, “cloud” was mostly a conceptual idea to me.
I knew the definitions. I knew cloud meant running software on remote servers instead of your own machine. I knew it helped with scaling, reliability, and availability.
But those were just words. Opening Azure made it real.
I wasn’t just deploying code anymore. I was seeing the environment that makes deployment possible. I started seeing that every running application depends on multiple layers beneath it.
- There’s compute: the actual machines that execute your code.
- There’s storage: where your files, databases, and state live.
- There’s networking: how different parts of your system communicate with each other.
- There’s identity and access control: deciding who can access what.
- There’s monitoring: tracking what happens when things fail.
- There’s scaling: handling more users without crashing.
When I deployed to Vercel before, all of this still existed. I just never saw it.
Vercel handled it for me.
Azure showed it to me.
And seeing it changed how I think about software.
One thing that confused me initially was why Azure had so many separate services. It felt unnecessarily complicated.
Why couldn’t it just be one “Deploy App” button?
The answer became clearer the more I thought about real-world systems. Not all applications have the same requirements.
A personal portfolio might only need basic hosting.
But something like a banking system needs strict network isolation, encrypted storage, identity management, access policies, backup systems, regional failover, and detailed monitoring.
These aren’t optional features. They’re requirements.
Platforms like Vercel simplify things by making decisions for you. Azure gives you the ability to make those decisions yourself.
That flexibility is what makes it powerful. It’s also what makes it overwhelming at first.
This also helped me understand where DevOps fits into the picture.
Before this, my workflow ended at deployment. Once the app was live, I moved on. But in real systems, deployment isn’t the end. It’s part of a continuous lifecycle.
Code needs to be built automatically, tested automatically, deployed automatically, monitored continuously, and recovered automatically when failures happen.
DevOps connects development and production into a single, reliable system. It ensures software doesn’t just run once, but continues running reliably under real-world conditions.
Another realization was that Azure isn’t fundamentally different from platforms I’ve already used. The architecture is actually very similar.
A typical application I build might have:
- A React frontend
- A Node backend
- A database
On Azure, those same pieces exist.
- The frontend can run on Azure Static Web Apps.
- The backend can run on Azure App Service.
- The database can run on Azure SQL or Cosmos DB.
The structure is the same. The difference is visibility and control.
Azure shows you how everything connects. It exposes the building blocks.
This also made me understand the role of a Cloud Solution Architect better.
Initially, I assumed cloud providers handled everything.
But cloud providers don’t design your system. They provide the tools.
Architects design how those tools are used.
They decide how services connect, how systems scale, how security is implemented, and how failures are handled. They design the structure that allows software to run reliably in the real world.
Azure provides the pieces. Architects decide how to assemble them.
What surprised me most wasn’t how much I didn’t know.
It was how much existed beneath the surface of things I thought I already understood. Deployment had always felt like the final step.
Now it feels like the beginning of understanding how software actually lives.
I didn’t deploy anything today. I didn’t build anything new.
I just opened the portal, explored, and realized there’s an entire layer of software engineering I’m only beginning to see.
And honestly, my brain is fried.
I’m going to be exploring Azure more deeply over the coming weeks and documenting the most interesting things I discover along the way.
But for today, I’m done.
If you’ve been further down this path, I’d genuinely love to know:
What’s one thing you wish you understood earlier when you started learning cloud?
Top comments (20)
Azure exposes the system. Vercel hides it. Both valid. But here's what really matters: understanding why those abstractions exist saves you when they fail. The "panic" is actually pattern recognition kicking in. You're seeing the gap between "it works" and "I control why it works." That's the jump from consumer to architect. Good writeup.
Thanks Guilherme! Really appreciate your supportive comment, gonna learn about compute services next! Stay tuned!
Bro, 'control panel for the internet itself' — that line hit different. 😂
I remember opening AWS for the first time and literally closing the tab after 30 seconds. Too many buttons. Too much power. Too overwhelming.
But here's the thing: that panic you felt? That's just your brain expanding. You realized your world was small, and now it's getting bigger.
What was the first Azure service you actually tried to learn? For me, it was Blob Storage (and I still mess it up sometimes 😅
That’s reassuring to hear honestly, because that initial panic felt very real in the moment. It’s strange how quickly abstraction can make you forget what actually exists underneath. I haven't tried anything on azure yet but I did some tutorials back in college on hosting a simple website on AWS but it's all blurry now, I'm trying to learn it properly at my pace this time.
I will put Blob Storage on my list to explore next.
Also, “that’s just your brain expanding” is a great way to frame it. It really did feel like my mental model stretching beyond its previous boundaries.
Exactly! That feeling when abstraction leaks or suddenly disappears — it's terrifying but also exciting. It means you're actually understanding what's happening under the hood, not just treating the cloud like a magic box.
And honestly? Taking it at your own pace this time is the right move. AWS especially is a BEAST — there's so much there that it's easy to get overwhelmed if you try to cram it. Slow and steady wins the cloud race ☁️🐢
When you do get to Blob Storage (or AWS S3), you'll probably find it clicks faster than you expect. The core ideas are simple: buckets/containers, objects/blobs, keys, metadata, and permissions. Everything else is just variations on that theme.
Also glad the "brain expanding" line helped. That moment when things feel messy and confusing? That's literally your neurons rewiring. Embrace the discomfort — it means you're leveling up 🧠💪
Let me know how the cloud journey goes! Always happy to geek out about this stuff.
"Slow and steady wins the cloud race" - gonna chant this while I conquer this mountain.
I liked the core ideas you listed, definitely looking forward to learning about them.
For now I've decided to learn more about the compute services on azure portal, my father's helping me with this stuff, since he's already an architect.
I'll definitely keep posting about it as I learn through it.
Cheers to embracing the discomfort - to leveling up! 🍻
Wow! You’ve entered the world of the cloud. It’s so fun, but also quite challenging. There are so many new things to learn. I’m looking forward to seeing what you create with it! 😄
Thank you for the support WDH!!!<(￣︶￣)>
I will definitely post more as I move forward on this journey.
I loved your post. It is humble and informative. I've personally never entered the Azure portal, so it was interesting to read what it has to offer. It is certainly a place to go if you want to build a serious application.
I've experienced this feeling in software many times. There are always new rabbit holes to explore and that is what makes this career so enjoyable. I had a blast getting deep into the story of the internet (starting from the 1970's in the US military complex) and getting deep into the different abstractions in web internals. Exploring JS and TS deeply has also been a world of surprises, JS been pretty funny though 😝
Thank you, that means a lot to hear.
I relate deeply to what you said about rabbit holes. This experience felt less like learning something new and more like realizing how much was always there without me noticing. It shifts your perspective from “I build apps” to “apps live inside systems.”
Your point about exploring the history and abstractions behind the internet resonates strongly too. I’m starting to see that understanding software isn’t just about writing code, but understanding the layers, decisions, and evolution that made modern development possible.
And yes, JavaScript is both amazing and slightly goofy at times.¯\(°_o)/¯
That happened to me a few years ago when I entered the AWS ecosystem. There are lots of tools, and the list keeps growing year after year. I recall feeling paralyzed by the amount of things to learn, links to click, and docs to read. I recall feeling I was never going to learn enough or use enough of The Cloud, but the thing is, it gets easier every time. Nowadays, I feel like a kid in a toystore. I get to play with tools that help me not only build better apps, but also more complex ones. I like to think I can do anything my mind designs.
One thing I wish I had understood earlier is how you are charged for using those precious tools. I was reckless at the beginning and ended up paying a lot of money for my mistakes. Once I understood how this thing worked and had read a lot of documentation, my wallet was happy again.
Thank you so much Ed! Your experience is really valuable for someone like me who is just starting to learn these things. When you said it gets easier every time, I got that confidence that maybe I can do it too!
And I will make sure to learn from what you shared and read a lot of documentation. (^^ゞ
" there’s an entire layer of software engineering I’m only beginning to see."
That´s exactly what IT is all about. Be so damn curious it scares you and bores everyone else ^^
That´s how it is for me.
IT lives and expands and changes. I love this article...I have been where you are now so many times...
There is so much to learn, so many things to discover...Take your time. It´s not a race is the best advice I can give you.
That’s a powerful way to put it, Ali.
I think what surprised me most wasn’t the complexity itself, but the realization that this layer was always involved in everything I’ve built, I just never saw it directly. It makes the act of deploying something feel less like a button press and more like participating in a larger system.
And your advice about taking time really resonates. There’s a temptation to rush toward “understanding everything,” but this feels more like something that unfolds gradually as you interact with it.
Curiosity feels like the only reliable compass here.
Thank you for the advice Ali!
I just started using Azure also and I can relate with all your discoveries. Haha.
Hahaha I've got a learning buddy nice!!(≧︶≦))(￣▽￣ )ゞ
Some comments may only be visible to logged-in visitors. Sign in to view all comments.