Skip to main content
XenonStack

Enterprise AI

XenonStack Blog Copilot for Databases: Azure SQL, SSMS and Fabric

and | Published | Updated

Copilot for Databases: Azure SQL, SSMS and Fabric
7:59

Key takeaway

  • Compare Microsoft Copilot for databases in Azure SQL, SSMS, VS Code and Fabric: what each does, permissions, licensing, limits and an adoption sequence.

Copilot for databases now means several different Microsoft experiences, not one tool: Microsoft Copilot in Azure for Azure SQL Database, GitHub Copilot in SQL Server Management Studio (SSMS), GitHub Copilot for the MSSQL extension in Visual Studio Code, and Copilot in the SQL database workload of Microsoft Fabric. Each has its own prerequisites, licensing and permission model, so the first decision is which surface fits your estate.

For enterprise teams the useful question is control, not novelty: what the assistant can see, what it can run, and who approves changes. This guide sets out what each surface does according to Microsoft Learn, a decision table, governance points and an adoption sequence. For the wider delivery picture, see our guide to Azure Copilot and GitHub Copilot for DevOps teams, and for the Dynamics side of the Microsoft estate, see Microsoft Dynamics Copilot.

What does Copilot for databases mean in 2026?

The old idea of a single code-completion tool does not match Microsoft's current documentation. Microsoft Learn describes four separate experiences, summarised below. Names, previews and availability change often, so confirm each on the linked Microsoft page before you commit.

SurfaceWhat it is, according to its siteWhere you use itPrerequisite to confirm
Microsoft Copilot in Azure with Azure SQL DatabaseA capability of the Azure Copilot experience that gives a conversational interface for managing and troubleshooting Azure SQL Database; overviewAzure portalCopilot enabled in your Azure tenant
GitHub Copilot in SSMSChat, inline chat, completions, next edit suggestions, database instructions and, from SSMS 22.7, Agent mode; overviewSQL Server Management StudioGitHub account with Copilot access; AI Assistance workload
GitHub Copilot for the MSSQL extensionSchema-aware chat with @mssql, agent mode, plan mode, slash commands and inline completions; overviewVisual Studio CodeGitHub Copilot subscription and the MSSQL extension
Copilot in Fabric SQL databaseChat pane, code completion and Fix and Explain quick actions; overviewFabric portal query editor, SSMS, Visual Studio CodeTenant switch enabled; paid F2 or P1 or higher capacity

What can Copilot do for database administrators and developers?

Microsoft Learn documents these tasks, grouped by role. None of them replaces review by someone who understands the database.

Administrators: diagnose and explain

In Azure SQL Database, Copilot answers questions using database context, dynamic management views and catalog views. Sample skills in Microsoft's prompt list include active user connections, blocking session analysis, anti-pattern query analysis, automatic tuning analysis and connection string generation. Microsoft's own example prompts include which service tier to use and why a database was unavailable.

Developers: write, explain and fix T-SQL

SSMS Copilot answers questions about SQL Server, Azure SQL Database, Azure SQL Managed Instance and SQL database in Fabric, and helps write, document, explain and fix T-SQL from natural language. The MSSQL extension adds schema suggestions, mock data and seed scripts, ORM migration scripts, plain-language explanations of stored procedures and checks for issues such as SQL injection risks or excessive permissions. Fabric adds Fix and Explain quick actions in the query editor.

Multi-step work: agent modes

SSMS Agent mode lets you state a goal and have Copilot execute queries, read execution plans and propose schema changes, with approval before each query or command. Microsoft's scenarios include creating and testing a stored procedure, analysing a slow query, reviewing the SQL error log and finding permission gaps. Microsoft advises making such changes in a test or development environment first.

How does Copilot treat permissions and data?

This is the section security and data leaders should read first. The documented behaviour differs by surface, which is why a single policy statement is not enough.

QuestionAzure SQL Database (Azure portal)SSMS (Visual Studio Code agent mode uses the extension's connection and credentials)Fabric SQL database
What access does it have?Only resources you can access, and only actions you have permission to performQueries run under your login; a query on a table you cannot read cannot runSchema, your prior messages, queries you ran and their errors; not table data
Can it change data?Microsoft describes it as answers and self-help; review output before production useAgent mode asks approval for each query or command; the security boundary is SQL Server permissionsRead-only mode suggests code; read and write mode needs your approval
Training and retentionPrompts and responses are not used to train the foundation models, per Microsoft's FAQMicrosoft Learn states GitHub Copilot in SSMS does not retain prompts or responses or use your data to train modelsPrompts and responses are not used to train foundation models, per Microsoft

Sources: Azure SQL Copilot FAQ, SSMS Agent mode and Fabric SQL database Copilot. The practical rule is to give the human or service identity the least privilege it needs, because Copilot inherits that identity's reach. For wider controls on autonomous actions, see agentic AI risk management.

Which Copilot should you choose?

Your situationBest fitWhyCheck before you commit
Estate on Azure SQL Database, portal-first operations teamCopilot in Azure with Azure SQL DatabaseAnswers in the portal using database diagnosticsTenant enablement; confirm preview or general availability status
DBAs who live in SSMS on SQL Server or Azure SQLGitHub Copilot in SSMSChat, completions and Agent mode in the tool they useGitHub account and plan; SSMS version
Application developers writing T-SQL and migrationsGitHub Copilot for the MSSQL extensionSchema-aware chat and agent mode beside application codeSubscription; note that inline completions do not see your connected schema
Operational data in Fabric SQL databaseCopilot in Fabric SQL databaseBuilt into the query editor with Fix and ExplainPaid capacity, region and tenant settings; trial SKUs are not supported

Teams on Azure Data Studio should note that Microsoft Learn states it retired on 28 February 2026, with Visual Studio Code and the MSSQL extension as the recommended replacement (Microsoft notice). Teams planning governed data and AI platforms can also see how ElixirData Context OS keeps governed context, versioned policy and decision traces in one decision layer above AI agents.

Two columns pairing Azure SQL operations, SSMS DBAs, application developers and Fabric users with Copilot in Azure, GitHub Copilot in SSMS, the MSSQL extension and Copilot in Fabric.

What do Copilot for databases cost and what limits apply?

Licensing differs by surface, and Microsoft revises it, so treat the following as the position when we read the pages and confirm it with your Microsoft account team. The Azure SQL Database Copilot FAQ states that its skills are offered at no additional cost. SSMS and Visual Studio Code use a GitHub account with Copilot access, and Microsoft documents a free plan for SSMS. Fabric requires a paid capacity of F2 or P1 or higher and a tenant administrator switch, and outside the US or France it is disabled by default unless the administrator allows data to be processed outside the capacity's region.

Known limits from the documentation: Copilot in Fabric SQL database cannot edit an existing query in the editor through the chat pane, may be inaccurate when asked to evaluate data because it sees only schema, and its chat pane is not available when Private Link is enabled and public access is disabled in the tenant setting. Microsoft states that AI output can contain mistakes and must be reviewed.

How should an enterprise adopt Copilot for databases?

A staged sequence keeps risk visible. Each step should have an owner and an exit criterion.

  1. Inventory. List engines, tools and the Microsoft surface each team already uses.
  2. Scope identities. Create read-only logins for exploration and keep write rights separate, because Copilot acts as the signed-in user.
  3. Pilot in non-production. Use development and test databases, with a short list of approved prompts and review steps.
  4. Add review gates. Treat generated T-SQL like any pull request: peer review, tests and a recorded approval.
  5. Record decisions. Keep an audit trail of which statements were suggested, approved and run, using AgentGRC, which keeps autonomous agent actions inside policy, with the audit trail risk teams need.
  6. Widen deliberately. Move to production-adjacent use only when access reviews and tests show the controls hold.

Related delivery practices are covered in Database DevOps, Data DevOps and why data quality matters. For building and governing agents across such workflows, see ElixirClaw, an agentic OS platform to build, orchestrate and govern AI agents and automation workflows while keeping humans in control.

When is Copilot not the right tool?

SituationWhy caution is neededSafer approach
Unreviewed changes to production schemaMicrosoft states the security boundary is SQL Server permissions and that output can be wrongGenerate in test, review, deploy through your pipeline
Questions that need the actual data valuesFabric Copilot sees schema only and may be inaccurate when evaluating dataRun reviewed queries and validate the results yourself
Highly regulated data movementFabric processing outside region needs an administrator decisionKeep the tenant setting off until legal review is done
Teams without a data ownerNobody can judge whether suggestions are correctAssign an accountable owner first

To map one database decision your agents should make, and the context and policy it depends on, book a Context Workshop. See what happens in the workshop.

Frequently asked questions

Does Copilot in Azure SQL Database see my table data?

According to Microsoft Learn, Copilot in Azure SQL Database answers from sources such as public documentation, dynamic management views, catalog views and Azure supportability diagnostics, and it only has access to resources you have access to. Copilot for SQL database in Microsoft Fabric uses object names and key metadata, not the data in tables.

Can Copilot change my database on its own?

Not without approval, according to Microsoft Learn. In SSMS Agent mode, Copilot asks for approval before each query or command, and Microsoft states that the security boundary is SQL Server permission enforcement, not Copilot's approval prompt. In Fabric, read-only mode suggests code for you to run, and read and write mode needs your approval.

What do I need to use Copilot in SQL Server Management Studio?

According to Microsoft Learn, SSMS 22.2 or later with the AI Assistance workload is needed for completions, SSMS 22.7 or later for Agent mode, and a GitHub account with Copilot access (a free plan is documented). Confirm current requirements on the Microsoft page before rollout.

Is Azure Data Studio still an option for Copilot?

No. Microsoft Learn states that Azure Data Studio retired on 28 February 2026 and recommends Visual Studio Code with the MSSQL extension, which includes GitHub Copilot integration.

Should production databases be Copilot-enabled for everyone?

Start in development and test, grant least-privilege logins, review every generated statement, and widen access only after the controls are proven. Microsoft advises testing changes in a non-production environment first.

Follow XenonStack on LinkedIn: XenonStack on LinkedIn for new guides on agentic AI, data and platform engineering.

Table of Contents

navdeep-singh-gill

Navdeep Singh Gill

Global CEO and Founder of XenonStack

LinkedIn profile

Navdeep Singh Gill is serving as Chief Executive Officer and Product Architect at XenonStack. He holds expertise in building SaaS Platform for Decentralised Big Data management and Governance, AI Marketplace for Operationalising and Scaling. His incredible experience in AI Technologies and Big Data Engineering thrills him to write about different use cases and its approach to solutions.

Get the latest articles in your inbox

Subscribe Now

Interested in solving your challenges with the XenonStack team?
Get Started

Tell us about you and your priorities so we can prepare the right conversation. It takes about 2 minutes.

Please Select your Industry
Banking
Fintech
Payment Providers
Wealth Management
Discrete Manufacturing
Semiconductor
Machinery Manufacturing / Automation
Appliances / Electrical / Electronics
Elevator Manufacturing
Defense & Space Manufacturing
Computers & Electronics / Industrial Machinery
Motor Vehicle Manufacturing
Food and Beverages
Distillery & Wines
Beverages
Shipping
Logistics
Mobility (EV / Public Transport)
Energy & Utilities
Hospitality
Digital Gaming Platforms
SportsTech with AI
Public Safety - Explosives
Public Safety - Firefighting
Public Safety - Surveillance
Public Safety - Others
Media Platforms
City Operations
Airlines & Aviation
Defense Warfare & Drones
Robotics Engineering
Drones Manufacturing
AI Labs for Colleges
AI MSP / Quantum / AGI Institutes
Retail Apparel and Fashion

Continue