Build a task-tracking app
Build a web app that displays tasks stored in Azure SQL. Start with sample data and make it your own.
Bring the idea. Build with Azure SQL.
Start with a prompt. Give your AI coding agent SQL skills, and make your next app yours.
Works with Claude Code, GitHub Copilot, Codex, and Cursor.
Could not play the demo. Please try again.
Choose your starting point: the cloud, local development, or your coding agent.
Create it in the Azure portal with the free offer, then verify from any SQL editor. Prerequisites and offer limits are in the setup guide.
SELECT 1 AS connected;Same engine as the cloud, in a container, offline. Preview today. Sign up and we send registry access.
One command teaches Claude Code, Copilot, Codex, or Cursor how Azure SQL works. You stay in the loop on every step.
npx skills add microsoft/microsoft-sqlStart with a task app, an API, or search over your content. Choose a scenario and use its prompt with your coding agent to build on Azure SQL.
Each prompt works against a database you already have. No database yet? Get a database running takes three steps.
Build a web app that displays tasks stored in Azure SQL. Start with sample data and make it your own.
Give your app a way to create, complete, and retrieve tasks. Build a Python API that connects to Azure SQL with Microsoft Entra, no passwords.
Find relevant text with vector search in Azure SQL. Build the retrieval layer for a RAG app using sample text and an embedding model you provide.
Read and save tasks through an Azure Functions API backed by Azure SQL. Build and test the functions locally.
Extend the serverless API with a function that reacts when tasks change in Azure SQL. Log inserts, updates, and deletes as a starting point for automation.
Extend a task app for multiple customers. Add row-level security and test that one tenant cannot read another tenant's tasks.
The pieces an AI app needs, inside the engine.
A native VECTOR type and VECTOR_DISTANCE. Store embeddings next to the rows they describe.
Vector docsGenerate and chunk from inside the database with external model calls. No separate pipeline.
AI_GENERATE_EMBEDDINGSChunk, embed, store, retrieve, ground. One skill walks your agent through all five.
Copy the RAG promptRow-level security, Entra identity, and injection-safe patterns the skills enforce by default.
Row-level security docsPick your agent. One install. The skills load themselves when the work matches.
claude plugin marketplace add microsoft/microsoft-sql
claude plugin install microsoft-sql@microsoft-sqlTwo commands: register the marketplace, then install the plugin with every skill. Or the portable form: gh skill install microsoft/microsoft-sql --all --agent claude-code.
Then just ask:
Click to copy. Paste into your agent.
Full catalog, every skill's source, and the feedback form at aka.ms/azuresql-skills. Skills teach your agent the engine; they do not grant access to the Preview container.
Longer walkthroughs from the Microsoft SQL team. Scroll for more.
Point the prompts above at an existing development database. Review permissions and schema changes before you let an agent run them.
The Azure SQL Database container runs the same engine offline. Sign up for the Preview.
An Azure account and a development database. The free offer covers everything on this page, within its limits. If you want to work offline, sign up for the container Preview.
Use a development database with least-privilege access. The skills default to parameterised queries, Entra identity over passwords, and row-level security for multi-tenant work. Review schema changes before they run against anything real.
No. Every prompt here targets Azure SQL Database in the cloud. The container is the local option, in Preview today.
The free offer covers the database for every example here, within its limits; see the offer details for what those are. The RAG example needs an embedding service, priced by whoever provides it; the prompt asks which one you have before using it.
Same engine family, managed for you, with features that ship to Azure SQL Database first. The container runs the Azure SQL Database engine, not the SQL Server image.