How to build a website with Microsoft Copilot and deploy it in 2026
Generate the code in Microsoft Copilot. Make it live on livemy.app. Full workflow with screenshots, prompt templates, and the gotchas to fix before you ship — from a real bakery site build.
Dmytro Chervonyi
Co-founder & CMO, livemy.app
Last updated
TABLE OF CONTENTS
item
AI Summary
Microsoft Copilot can generate a complete website — HTML, CSS, JavaScript — from a single prompt. What it can’t do is publish the result. This guide shows the workflow that works: ask Copilot to draft the brief, generate the code, package it as a ZIP, then push it to a live URL on livemy.app in about three minutes. Built around a real bakery website example (Golden Grain Patisserie). No coding background needed, no credit card to start.
Wait, which Copilot?
Two products from Microsoft share the name and it matters which one you’re using. Microsoft Copilot (formerly Bing Chat) is the consumer chat product at copilot.microsoft.com — free to use, generates HTML/CSS/JS from prompts, packages projects, plays the same role for non-devs that ChatGPT and Gemini do. GitHub Copilot is the developer code-completion product that lives inside an IDE — different tool, different workflow, not what this guide covers.
This article is about Microsoft Copilot at copilot.microsoft.com. If you’re here for GitHub Copilot, you want a different guide.
What Microsoft Copilot actually does (and doesn’t do) for websites
Quick truth check before anyone burns an hour.
It does: generate HTML, CSS, and JavaScript code from a prompt. Style sites to look reasonably modern. Switch between Smart and Quick modes depending on how much depth you want. Pull in Bing search results when your prompt asks for facts or inspiration. Output a complete website with semantic structure, decent typography defaults, and mobile-responsive media queries when you ask for them. Package the project into a downloadable ZIP archive in the chat.
It doesn’t: host the site for you. There’s no “Publish” button anywhere in Copilot. The output is code. The code lives in your chat (or your local disk after download). Getting from code to a real address someone on the internet can visit still requires a separate host.
This is where most “make a website with Copilot” tutorials end vaguely with “then put it somewhere.” This one doesn’t.
Two ways to get website code out of Copilot
Copilot doesn’t have a Canvas mode the way ChatGPT or Gemini do — it’s a single chat flow. But it can generate complete projects packaged as ZIP downloads, which is what you want most of the time anyway. Two practical paths:
Path A: Single HTML page (about 90 seconds)
For a one-page landing site, portfolio, brochure, or coming-soon page. Ask Copilot for “a complete HTML file with CSS and JavaScript inline” for whatever you want. Copilot drops the code in chat. Copy, paste into a single index.html file. Done.
When this works: marketing landing pages, link-in-bio sites, event signups, almost any single-screen content.
Path B: Multi-file project as a ZIP (5–10 minutes)
For multi-page sites or anything with shared CSS and JS. Ask Copilot to generate a complete project with index.html, styles.css, and script.js, then package it as a ZIP for download. Copilot writes the files, structures them, and serves the archive in the chat. This is the path the rest of this article uses.
When this works: small business sites, agency portfolios, multi-page brochure sites, simple blogs.
The 4 prompts that work in Copilot
Templates I’ve leaned on enough to trust. Copy, paste, fill in the bracketed bits.
1. The brief-generator prompt
Generate a prompt for creating a website based on HTML, CSS, and JS for [your business / project type]. Make it detailed and specific to the business style. Cover overall style, sections, typography choices, output structure, and target audience.
2. The build-it prompt
Using the brief above, generate the complete website code in HTML, CSS, and JavaScript. Make it mobile-responsive with proper viewport meta tag and media queries. Include sections for hero, products, story, and contact. Use semantic HTML — real header, main, section, footer tags, not div soup.
3. The zip-it-up prompt
Provide the entire project for download in a ZIP archive. Include index.html, styles.css, script.js, and any image placeholders needed. Tell me what each file does and how to use it.
4. The iteration prompt
Show me the index.html again. Add [specific change]. Don’t rewrite the whole file — just show me the section that changed and tell me which line to update.
Like ChatGPT and Gemini, Copilot loves rewriting whole files when you ask for a small change. The “just the section that changed” framing saves a lot of time once your file gets long.
From code to a live URL on livemy.app (about 3 minutes)
You have a ZIP. Now you need a real address — yoursite.com, or just a free livemy.site subdomain — that anyone on the internet can visit.
Step 1: Get the ZIP
If you took Path A: zip the folder containing your index.html yourself. If you took Path B: download the ZIP Copilot built.
Step 2: Sign up at livemy.app
Go to livemy.app and click Start free. No credit card. The Free tier is enough to test the deploy. For real visitors, pick Maker ($20/month) before going live — Free-tier projects sleep after 60 minutes of inactivity, which isn’t a fit for a public site.
Step 3: Create a project, upload the ZIP
In the dashboard, click New project → Upload archive and drop the file in. livemy.app auto-detects the stack — plain HTML, Vite, React, Next.js — and configures the build. No Dockerfile. No settings to wrestle with.
Step 4: Wait for the deploy
Typical time: 2 to 6 minutes for a Copilot-built site. The dashboard streams the build log live as it runs. When status flips to Live, you get a URL like your-app.livemy.site and the project card shows the IP, server name, and deploy timing.
Step 5: Point your own domain at it (optional)
Click Add custom domain in project settings, paste your domain, update one DNS record at your registrar — Cloudflare, Namecheap, GoDaddy all support this. Within 1–10 minutes the DNS propagates and Let’s Encrypt SSL fires automatically.
What goes wrong with Copilot-built sites
Five issues account for most of the “why doesn’t this look right” questions.
Image placeholders point nowhere. Copilot often references stock image filenames that don’t exist. Replace them with real URLs (Unsplash for free stock, your own files, or generate with Designer and host the result).
Mobile breaks on first try. Copilot’s defaults are desktop-first. Ask: “Make this fully mobile-responsive with media queries, a proper viewport meta tag, and a hamburger menu for nav.” It’ll redo the CSS.
Font choices look off. Copilot sometimes picks fonts that don’t load reliably. Either ask for “system fonts only” or include a Google Fonts CDN link in the prompt.
SEO basics missing. No title tag, no meta description, no Open Graph. Ask: “Add SEO meta tags — title, description, og:title, og:description, og:image, favicon link — to index.html.”
Form submissions go nowhere. Static HTML can’t handle form submissions on its own. Use Formspree or Basin (one form attribute change) or move to a server-rendered stack with a real form handler.
How much does it cost?
Three line items.
Microsoft Copilot. The free tier handles single-file HTML generation and most simple website builds. Copilot Pro is $20/month and gives you priority access to GPT-class models during peak times, plus integration with Microsoft 365 apps. Most websites are buildable on the free plan.
Hosting. livemy.app Free is enough for testing. For a live production site with a custom domain, Maker is $20/month. Worth pricing against Webflow, Squarespace, Wix — all sit in the $14–25/month range. The difference with livemy.app: you own the code and can take it anywhere.
Custom domain. A .com is roughly $10–15/year at a registrar like Namecheap or Cloudflare.
Realistic monthly total for a production site: $20–40 plus the domain.
FAQ
Can Microsoft Copilot actually build a complete website?
Yes. Copilot generates HTML, CSS, and JavaScript code that runs in any browser, and can package the result as a downloadable ZIP archive. It does not host the result — you take the code Copilot generates and deploy it on a host like livemy.app.
Do I need Copilot Pro?
Not for most websites. The free Copilot tier handles simple to mid-complexity HTML/CSS/JS generation comfortably. Copilot Pro ($20/month) gives you priority access during peak hours and tighter Microsoft 365 integration — useful if you’re building several sites a month or working inside Word/Excel/PowerPoint regularly.
Is Microsoft Copilot the same as GitHub Copilot?
No. Microsoft Copilot is the consumer chat product at copilot.microsoft.com — the tool this guide covers. GitHub Copilot is a developer code-completion product that runs inside an IDE like VS Code or JetBrains. Different products, different workflows.
Where do I host a Copilot-generated website?
Any host that accepts HTML files. livemy.app handles static HTML, Vite, React, Next.js, and other modern frameworks without configuration. Drop the ZIP, get a live URL with SSL in 2 to 6 minutes.
How long does the whole thing take?
For a single-page site: roughly 10–20 minutes of Copilot iteration plus 2–6 minutes of deploy. For a multi-page project: 20–40 minutes plus deploy.
Can I update my site after it’s live?
Yes. Paste the current file into a new Copilot conversation, ask for the specific change, copy the updated code, re-deploy on livemy.app. Builds and deploys are unlimited on Maker and above.
Deploy your Copilot-built site in 3 minutes
Prompts ready, ZIP downloaded. The only thing between you and a live URL is one upload.
→ Start free on livemy.app · No credit card · Free tier forever · Deploy your Copilot-built site in about 2 minutes.
Questions on the deploy side? Drop a line to hello@livemy.app. The team replies within one business day, build log included if you’ve got one.
Read next
Dmytro Chervonyi
,
Co-founder & CMO, livemy.app
Co-founder & CMO at livemy.app. 12 years as a CMO scaling SaaS from $0 to $10M+ ARR across marketing, sales, and infra products and tools. Now building the missing step between AI-built code and a live URL — for non-developers who’d rather ship than learn DevOps.
