The Azure free account is not one gift. It is three different gifts with three different clocks.

What Azure is, in one minute

Microsoft Azure is Microsoft’s cloud platform. Cloud means renting computing power, storage, and software over the internet instead of buying your own machines. With Azure you can create a virtual server in minutes, store files, run a database, host a website, or use ready-made artificial intelligence tools, and you pay only for what you use. Azure is one of the three largest cloud platforms in the world, alongside Amazon Web Services and Google Cloud.

The three parts of the free offer

When people say “Azure free account”, they usually mean a bundle of three things that start together when you sign up:

“Free account” versus “free tier”

These two phrases are used loosely. The free account is the whole sign-up experience, including the starter credit. The free tier or free services refers to the services with free monthly allowances, both the 12-month ones and the always-free ones. In this guide we use them in exactly that way.

Free offers are a smart business decision. Understanding the reason helps you understand the rules.

Cloud providers compete for developers, students, and companies. A person who learns Azure for free today is more likely to recommend it, build on it, or choose it at work tomorrow. So the free account is a form of marketing, but it is also a real learning tool. You get hands-on experience at no cost, and Microsoft gets future customers.

Who benefits most

Before you click anything, learn the five containers Azure uses to organise everything. They explain most of the confusion beginners feel.

Azure arranges things like nested boxes. Knowing which box holds which is the key to understanding billing, permissions, and cleanup.

flowchart TB
  M["Microsoft Account or Work Account: your login identity"]
  T["Microsoft Entra Tenant: your organisation's identity directory"]
  S["Subscription: the billing container, holds the free credit"]
  R["Resource Group: a folder for related resources"]
  X["Resources: VM, database, storage, website"]
  M --> T
  T --> S
  S --> R
  R --> X
    

The five containers explained

Why resource groups matter for free accounts

A resource group is the best cleanup tool you have. If you create all the resources for one experiment inside one resource group, you can delete that single group when you finish, and every resource inside it disappears together. This is the easiest way to stop forgotten resources from collecting charges.

Region: where your resources live

A region is a geographic area that contains Azure data centers, such as Central India or West Europe. When you create a resource, you choose its region. Pick one close to you for speed. Not every free service is available in every region, so if a free option seems missing, try a different region.

The credit is the most exciting part, and also the most misunderstood.

How the credit works

When your account is created, Azure puts a credit balance into your subscription, in recent years about 200 US dollars, with the amount shown in your own currency in some regions. You can spend it during the first 30 days on most Azure services, including ones that are not part of the free lists. Every hour of a virtual machine and every gigabyte stored takes a little from the balance.

Two ways the credit ends

• The 30 days pass. Whatever credit is left disappears. It does not carry over.
• The balance reaches zero before 30 days. Your paid services stop.

In both cases, Azure does not simply start charging your card. A new free subscription has a built-in spending limit. When you hit it, your resources are disabled and your data is kept for a while. You can only continue after you deliberately upgrade to a pay-as-you-go plan. This design protects beginners from silent overspending.

A short checklist saves you from failed sign-ups and wasted time.

The requirements

The whole process usually takes about ten minutes. Here is exactly what to expect at each stage.

If sign-up fails

• Card declined: try a different card, check that online payments are enabled, and make sure the address matches your bank records.
• Phone already used: a number linked to an earlier account may be refused.
• Region problems: the offer may differ by country. Check the official page for your location.
• Still stuck: use Microsoft’s support chat for sign-up and billing issues. It is free for these topics.

The first things you do matter more than the first things you build. Set up your safety nets before creating anything.

A quick tour of the portal

The Azure portal is the website where you manage everything. Think of it as the control room of your cloud. The main parts you will use are:

The safety checklist to do first

Behind the portal there is a meter for everything. Learning how the meter works is the best protection against surprises.

Meters, units, and free allowances

Every Azure service measures usage in small units called meters. A virtual machine is measured in hours it is running. Storage is measured in gigabytes kept per month, plus the number of operations performed. A function is measured in executions and in how long each one runs. Data leaving Azure to the internet is measured in gigabytes.

A free allowance is simply a number of units given away each month. For example, “750 hours of a small virtual machine per month” means the first 750 hours are priced at zero. After that, normal prices apply. There are about 730 hours in an average month, so 750 hours covers one machine running non-stop, but not two.

What happens between your click and your bill

Why the numbers lag

Cost Management is not a live speedometer. Usage can take several hours to appear, so a mistake made this morning may not show in your dashboard until this evening. That delay is a strong reason to check on your resources daily and to delete things promptly when you finish.

The spending limit

A free account begins with a spending limit turned on. It means that once the credit is consumed, Azure disables resources that would cost money instead of billing you. This is different from a normal pay-as-you-go subscription, which has no automatic ceiling. The limit disappears when you upgrade, and from that moment normal billing starts for anything beyond free allowances.

Compute means processing power, the part of the cloud that runs your programs. These are the most popular free ways to get it.

The lists below describe typical offers. Exact machine sizes, limits, and names change, so treat them as examples of the kind of thing you can expect.

Virtual machines (12-month offer)

A virtual machine is a pretend computer running inside a real one. The free offer has usually included a monthly allowance of 750 hours for small, low-cost machine sizes, in both Linux and Windows flavours. A small burstable size is enough to learn the basics: log in, install a web server, and practise commands.

App Service (free plan)

App Service is a platform where you upload your website or application code and Azure runs it for you, with no server maintenance. It has a free plan, which hosts several small apps with a limited amount of daily processing time. It is perfect for practising and for tiny hobby sites, but not for real traffic. Free-plan sites may also sleep when idle, and are slow to wake.

Azure Functions (always free allowance)

Azure Functions lets you run small pieces of code only when something triggers them, such as a web request or a file upload. This is called serverless, because you never manage a server. The consumption plan has typically included about a million executions per month free. For a learner this is almost unlimited.

Static Web Apps and containers

Static Web Apps hosts websites made of plain files, along with a small serverless back end, and it has a free plan that is ideal for portfolios and documentation sites. Container Apps runs packaged applications called containers, and has included a monthly free grant of processing and requests. For Kubernetes learners, the managed Kubernetes service has a free tier for its control part, although the machines it uses still cost money.

Almost every app remembers things. Azure gives you small free spaces to keep files and records while you learn.

Storage accounts

A storage account is a container for several kinds of storage. Blob storage keeps files such as photos and videos, called blobs. File storage offers shared folders. Queue storage holds messages waiting to be processed. Table storage keeps simple records. The 12-month offer has usually included a few gigabytes of blob storage and some file storage, with a monthly allowance of read and write operations.

Managed disks

A virtual machine needs a hard drive. Managed disks are virtual drives that Azure looks after. The free offer has typically included a couple of small disks for 12 months. Remember that a disk keeps costing money after the machine is deleted if you forget to delete the disk too.

Databases

Besides servers and storage, several supporting services are free for small use, and they teach some of the most valuable cloud skills.

Let us put the pieces together. This small design could run a real hobby project at no cost, if you stay within the limits.

The example is a simple notes website. Visitors open a web page, type a note, and the note is saved. The pieces are all chosen from free offers: static hosting for the page, a function for the logic, a database for the notes, and basic monitoring to watch it.

flowchart LR
  U["Visitor Browser"] --> SW["Static Web Apps: free plan, serves the page"]
  SW --> FN["Azure Functions: API code"]
  FN --> DB["Cosmos DB free tier: stores notes"]
  FN --> ST["Blob Storage: stores attachments"]
  FN -.-> MON["Azure Monitor: basic metrics and logs"]
  ID["Microsoft Entra ID: sign-in"] --> SW
    

How each part helps

• Static Web Apps serves the page files, and can send requests to your functions.
• Functions contain the rules, such as “check the note is not empty, then save it”.
• Cosmos DB stores each note as a small document, fast and flexible.
• Blob Storage holds optional files, such as images attached to notes.
• Entra ID lets people sign in, so each person sees only their own notes.
• Monitor tells you if errors rise or limits are being approached.

Follow one request through the notes app, then follow the life of the account itself from birth to upgrade or retirement.

One request, step by step

sequenceDiagram
  participant V as Visitor
  participant S as Static Web App
  participant F as Function
  participant D as Cosmos DB
  participant M as Monitor
  V->>S: Open the page
  S-->>V: Page files
  V->>S: Save my note
  S->>F: Forward the request
  F->>D: Write the note
  D-->>F: Saved
  F->>M: Record metrics
  F-->>V: Success message
    

The lifecycle of the account

A free account passes through predictable stages. Knowing them in advance lets you plan instead of react.

flowchart LR
  A["Sign up"] --> B["Days 1 to 30: credit active"]
  B --> C{"Decision at day 30 or when credit ends"}
  C -->|"Do nothing"| D["Paid resources disabled, data kept for a time"]
  C -->|"Upgrade to pay-as-you-go"| E["Free allowances continue, normal billing begins"]
  E --> F["Month 12: 12-month services end"]
  F --> G["Always-free services continue"]
    

What if you do nothing at day 30?

Your paid resources are disabled, not instantly deleted. You are generally given a period to upgrade and recover your data, but that period is limited, and data left too long can be removed. Treat it as a deadline. If you want to keep anything, download it or upgrade in time.

Upgrading sounds scary, but it is a normal step. It is safe when you understand what changes.

Should you upgrade?

Upgrade if you have a project you want to keep running, need services outside the free lists, or need more than the free limits. Do not upgrade just because the thirty days ended, if you are only learning. You can sit out and come back later. Many learners simply wait until they have a clear project, then upgrade with budgets already in place.

The free account is a wonderful learning tool, with honest limits. Knowing both sides helps you use it well.

Free versus pay-as-you-go versus student account

A free account is still a real account. Attackers love free cloud power, so a careless learner is an attractive target.

Why anyone would attack a free account

Cloud computing power costs money, and criminals use stolen accounts to run it for free at someone else’s expense. The most common abuse is cryptocurrency mining, where a stolen account launches huge numbers of powerful servers to calculate digital coins. With a free account and its spending limit, the damage is capped. After you upgrade, the same theft can produce a very large bill in a short time.

The shared responsibility model

Azure protects the data centers, the hardware, and the core platform. You protect your passwords, permissions, settings, and data. The simplest way to remember it: Microsoft secures the building, and you lock your own door.

Your security checklist

You cannot protect what you cannot see. A few simple screens tell you almost everything about your free usage.

Three screens worth bookmarking

Budgets and alerts

A budget is a spending target you set. An alert is a message that arrives when spending reaches a chosen percentage of that budget. Create a small budget on day one, with alerts at, for example, fifty and ninety percent. Even if your free account has a spending limit, the habit is excellent, and it becomes your life jacket after you upgrade.

Metrics, logs, and alerts for your apps

Metrics are numbers over time, such as processor use or request count. Logs are written records of events, such as errors. Alerts notify you when a number crosses a line. Azure Monitor gathers basic metrics for most resources automatically. For learning, simply open the Metrics page of a resource, watch the numbers move when you use it, and connect cause with effect.

Most accidental charges come from the same handful of mistakes. Learn them once and avoid them forever.

Other small surprises

• Outgoing data: sending large amounts of data out of Azure to the internet can cost more than you expect once you pass the free monthly amount.
• Marketplace items: third-party products may be billed separately and may not use your credit.
• Region limits: some free services exist only in certain regions, and picking another region can make a resource paid.
• Backups and snapshots: extra copies of disks and databases take extra space that is billed.
• The wrong subscription: if you have more than one subscription, check that you created things in the free one.

Thirty days go fast. A simple plan helps you learn the most while the credit is active.

Habits that pay off

A four-week plan

The same pattern of “try small, grow if it works” is how many real products and careers begin.

A two-minute habit before every click is the strongest protection you have against surprise charges.

Azure shows prices in several places, but beginners often skip all of them. Learn the routine below and use it every single time you create something new.

A worked example with hours

Suppose your free allowance is 750 hours of a small virtual machine per month. An average month has about 730 hours. If you run one machine all month, you use about 730 hours and stay free. If you run two machines all month, you use about 1,460 hours. The first 750 are free, so about 710 hours are billable. The mistake is easy to make: the allowance is shared across all machines of that kind, not given to each one.

Words to watch for

Reading about the cloud is useful. Doing small exercises is better. Each lab below is safe, short, and ends with cleanup.

Lab 1: Store and share a file

Goal: understand storage accounts, containers, and access levels.

• Create a resource group named for the lab, then create a storage account in it with the simplest, locally redundant options.
• Inside the account, create a container and keep its access level private.
• Upload a small picture, and try opening its address. You should be refused, because the container is private.
• Create a temporary access link for the file, open it, and note how it stops working after the expiry time.
• Delete the resource group.

What you learn: the difference between private and public data, and how temporary links give safe, short-term access without opening everything.

Lab 2: Launch and tame a small server

Goal: see the full life of a virtual machine, from birth to deletion.

• In a new resource group, create a virtual machine, choosing the smallest size labelled as eligible for the free offer and a popular Linux image.
• For access, restrict the login door to your own address only. Do not leave it open to the world.
• Connect, run a few basic commands, and install a simple web server.
• Look at the machine’s metrics page. Notice how processor use rises when you load the web page.
• Stop the machine with the portal’s stop button and see that its status becomes deallocated.
• Delete the whole resource group and check that the disk, address, and network card are gone.

What you learn: machines, disks, networks, and addresses are separate resources, and cleanup means removing all of them.

Lab 3: A tiny serverless website

Goal: experience the always-free style of building.

• Create a static website from a simple page of your own, using the free hosting plan.
• Add a small function that returns a greeting, and connect the page to it.
• Visit the page, press the button, and watch the function run in the monitoring view.
• Look at the execution count and compare it to the monthly free allowance. You should have used only a tiny fraction.
• Delete the resource group when finished, or keep it since it is within the free limits.

What you learn: how serverless pricing counts executions rather than hours, and why tiny apps can run at no cost.

Every major provider wants beginners. Their free offers share the same shape, but not the same numbers.

The big cloud providers all use a mix of the three ideas you met at the start: a time-limited credit or trial, a set of services free for a limited period, and a set of services free with small limits for as long as you like. The details have shifted several times over the years, so use the comparison below as a guide to the structure, and read each provider’s current page for the exact figures.

How to choose where to start

• Follow your goal: if you are preparing for a specific certification or job, learn on that provider.
• Follow your tools: teams that use Microsoft products, such as Windows servers, SQL Server, or Microsoft 365, often find Azure a natural fit.
• Learn concepts first: storage, networks, identity, and billing work in similar ways everywhere, so the skills carry over.
• Do not spread yourself thin: pick one provider for the first month and finish your labs before comparing others.

Every term from this guide in one place, each with a plain comparison.

Short, honest answers to what beginners ask most.