Publish a small web application

What you’ll be able to do

Explain the relationship between source, build, and deployment.
Choose a suitable hosting service for a static application.
Verify a source change reaches the deployed page.

Before you beginAn Azure subscription, a GitHub account and disposable repository, and permission to create Static Web Apps. Follow the official quickstart’s current prerequisites. Use only public-safe content; a deployed lab page can be accessible to others.

Get the idea

Choose hosting for the application

A simple static frontend is a good starting point for Static Web Apps. Applications requiring other runtime behavior may need different hosting options. Service selection starts with your application’s requirements.

Source is the beginning

The repository contains your application code. A workflow builds and publishes it. A commit existing in the repository does not mean a deployment has finished successfully; inspect the workflow result.

Configuration is part of delivery

Repository, branch, build preset, application location, and output location must agree. A blank page can be a build-path problem rather than a network outage. Never put API secrets in browser code.

Try it yourself

Create a disposable repository with a simple index.html containing a heading and a short paragraph. Do not include personal information, credentials, or internal documents.
Follow the linked portal quickstart to create a Static Web App. Select the appropriate plan after reviewing its terms and any billable options.
Connect the repository and branch. For plain HTML, choose the matching custom build configuration described in the quickstart; confirm application and output locations.
Inspect the generated deployment workflow and wait for success. Open the assigned URL and confirm the heading appears.
Change the heading in the source repository, commit, and verify the new workflow and deployed page. Explain each step of this source-to-site journey.

Check your resultThe live page matches the latest successful source commit, and you can locate the workflow that published it.

Finish the lab

Delete the practice Static Web App when finished and remove its deployment workflow or repository if no longer needed. Review any resources and integrations created during setup. Do not assume every plan or add-on is free.

Quick knowledge check

Your commit is visible in GitHub, but the website is unchanged. What do you inspect next?

Reveal the explanation

Check the deployment workflow, branch, build configuration, and deployment status. The source commit alone does not prove the hosting update succeeded.

Take this with you

Verify the entire delivery chain, not just the source change.

Go deeper

Build your first Static Web App

AI-assisted lesson · Reference links checked October 3, 2026. Exercises are teaching examples; they have not been executed against your Azure subscription.