Setting up Azure takes about ten minutes, and almost all of the confusion people run into isn't about the setup itself — it's about two specific surprises that catch people who didn't know to look for them. This walks through both the account creation and those two traps, so neither one catches you. It picks up from the "20–40 min" section of Your first hour with a template, where this step first comes up.
Step 1: Create the account
Go to Azure's free account signup page and sign up with a Microsoft account (a personal Outlook/Hotmail address works fine, or you can create one on the spot). You'll be asked for:
- Basic identity details (name, phone number, a verification code).
- A credit card.
That second one is the first surprise worth knowing about ahead of time.
Trap 1: The credit card is identity verification, not a bill
Azure asks for a card the same way a hotel asks for one at check-in — to confirm you're a real, verifiable person, not to start charging you. The free tier these templates run on (the F1 App Service plan) is free indefinitely. It isn't a trial that quietly converts to paid after 30 days; there's no clock running out on you.
That said, it's worth spending twenty seconds doing one thing while you're already in the account: go to Cost Management + Billing → Budgets and set a small spending limit or alert (even $1) so that if you ever add a paid resource by mistake later, you get an email instead of a surprise. It costs nothing to set up and it means the account genuinely can't surprise you.
Step 2: Create your Web App resource
Once your account exists, go to Create a resource → Web App. A few choices matter here:
- Resource Group — a folder that groups related resources together. Create a new one named after your app; you'll want this name later.
- Runtime stack — your README will tell you exactly which one your template needs (Node, Python, .NET, etc.) — match it exactly.
- Region — pick one physically close to your users; it affects load speed slightly and doesn't affect cost on the free tier.
- Pricing plan — this is the one to check carefully. Select Free F1, not one of the "Basic" or "Standard" tiers that look similar in the list but bill by the hour.
Create the resource, and Azure gives you a live (if empty) URL immediately.
Trap 2: The free tier sleeps, and that's normal
The F1 plan puts your app to sleep after a period with no visitors, to keep it free for everyone. The first request after a quiet stretch — say, first thing the next morning — takes a few extra seconds while it wakes back up. Every request after that is normal speed until it goes quiet again.
For a business app your own team uses a few times a day, this is genuinely a non-issue — a few seconds, once, and then it's fine. It's worth knowing only so the first time you see it, you recognize it as expected behavior and not a bug.
Step 3: Connect it to your GitHub repository
The last piece — turning "an empty Azure resource" into "your actual running app" — happens through Deployment Center, inside your new Web App: connect it to the GitHub repository holding your code, and Azure sets up the automated pipeline that redeploys on every push from there. Your template's README covers the exact one-time details for your specific stack; the deployment mechanics themselves — why this pipeline exists and what it's actually doing — are covered in From localhost to live.
Key Takeaways
- The credit card is identity verification, not a charge. The F1 free tier is free indefinitely, not a trial.
- Set a spending limit anyway — twenty seconds of setup means the account can never bill you by surprise.
- Match your runtime stack exactly to what your README specifies when creating the Web App.
- Select the Free F1 plan specifically — similarly named "Basic" or "Standard" tiers bill by the hour.
- The free tier sleeps when idle, and the first request after a quiet stretch takes a few extra seconds. That's expected, not broken.
- Deployment Center connects your GitHub repo to Azure, and from there every push deploys automatically.