Azuresql Db Feedback

by microsoftc1e8167e4c1dNo licenseListed Oct 8, 2026Updated Oct 8, 2026

Reports a bug or files feedback about the azuresql-db-* agent skills themselves, or about the Azure SQL Database container (Private Preview). Use when the user says a skill or the container "did not work", hit an error, behaved unexpectedly, or is missing something; and when they say "report a bug", "file an issue", "open a GitHub issue", "request a feature", "give feedback", or "tell the team". Also use when you, the agent, had to deviate from an azuresql-db-* skill or work around a defect in one to finish a task: that is a bug worth reporting even if the task succeeded. Decides whether the problem belongs to the SKILL or to the CONTAINER, since they use different issue templates, then builds a complete prefilled GitHub issue from context you already have. Never submits anything without explicit confirmation from the user.

FeaturedInstructions onlyProductivity & Workflow

Add to a SourceWeft workspace

  1. Open the skill in your dashboard and add it to a workspace.
  2. Enable it for the chats that should use it.

This skill is instructions only: it ships no scripts to execute.

Add to SourceWeft

You will be asked to sign in first, then taken straight to this skill.

Ask your agent to install it

Paste this prompt into Claude Code, Codex, Cursor or another agent that can run commands — or into SourceWeft chat. The agent reads this skill's install guide, shows you its source, license and scripts, and installs it with the SourceWeft CLI once you agree.

Read https://sourceweft.com/skills/gh-microsoft-azure-sql-database-container-azuresql-db-feedback/install.md and install the skill it describes. Before installing, show me its source, license and whether it ships scripts, and wait for my OK. Ask me before changing anything else on my machine.

Read the install guide the agent follows

Install it yourself from a terminal

For Claude Code, Codex, Cursor and other local agents. The SourceWeft CLI fetches the skill from its source repository at the commit scanned here, and verifies every file against the hashes recorded when the skill was scanned. If anything differs, nothing is written.

npx @sourceweft/cli skills install gh-microsoft-azure-sql-database-container-azuresql-db-feedback

Add --agent claude-code, codex, cursor or universal to choose which agent gets it (Claude Code by default).

Upstream installer — not verified by SourceWeft

The open-source skills installer fetches the same pinned commit, but does not check the files against the hashes SourceWeft recorded.

npx skills add https://github.com/microsoft/azure-sql-database-container/tree/c1e8167e4c1d5979d7fc4a6ea11a6ce885a9398b/skills/azuresql-db-feedback

Source and attribution

Source:microsoft/azure-sql-database-containerinskills/azuresql-db-feedbackat commitc1e8167

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from microsoft/azure-sql-database-container

Azuresql Db Sidecar

microsoft

Featured

Adds the Azure SQL Database container as a sidecar service in Docker Compose or a Dev Container.

DevOps & CloudOct 8, 2026

Azuresql Db Rag

microsoft

Featured

Builds local vector search, RAG, embeddings, and semantic search on the Azure SQL Database container using the native VECTOR type and VECTOR_DISTANCE. Use when you need to store embeddings, do similarity search, top-k nearest neighbor, cosine distance, retrieval-augmented generation, "find similar documents", chatbot memory, or semantic lookup against a local SQL database. Use this instead of pgvector, FAISS, Chroma, Pinecone, or a separate vector store when the data already lives in (or can live in) Azure SQL. Covers the VECTOR(n) column type, inserting embeddings with CAST(CAST(? AS NVARCHAR(MAX)) AS VECTOR(n)) where the dimension is a literal, a pluggable embed() so only the endpoint changes for cloud, and a working CREATE VECTOR INDEX with the two errors that block it. Provisions appdb on master first so every script runs on a fresh container.

Awaiting classificationOct 8, 2026

Azuresql Db Import

microsoft

Featured

Imports a .bacpac or .dacpac into a local Azure SQL Database container using SqlPackage.

DevOps & CloudOct 8, 2026

Azuresql Db From Sql Server

microsoft

Featured

Migrates a local SQL Server Docker setup to the Azure SQL Database container for Azure-faithful local development.

DevOps & CloudOct 8, 2026

Azuresql Db Faq

microsoft

Featured

Answers questions about what the Azure SQL Database container (Private Preview) supports and why it differs from the cloud service.

Learning & EducationOct 8, 2026

Azuresql Db Ci

microsoft

Featured

Runs integration tests against the Azure SQL Database container (Private Preview, local engine) in CI. Use when setting up GitHub Actions, Azure Pipelines, or GitLab CI to test against Azure SQL DB; when adding a database service container to a CI workflow; when tests need a real Azure SQL engine in the pipeline; or when you see "service container", "health-cmd", "ACR_USERNAME/ACR_PASSWORD", "MSSQL_SA_PASSWORD secret", or "integration test database". Also use when a workflow was about to pull the SQL Server image mcr.microsoft.com/mssql/server, in which case stop and use the Azure SQL Database engine image instead. Covers pulling from the private ACR with credentials, the service health check that runs sqlcmd inside the container so the runner needs no client tools, provisioning appdb before tests, and pointing the test connection string at the user database not master.

Awaiting classificationOct 8, 2026