Azure · Cloud service
Azure SQL Database with OrchestrAI
Catalog exported 2026-09-02
Provision Azure SQL from chat: servers, databases, managed instances, and Azure AD administrators.
OrchestrAI exposes 6 Azure SQL operations: 5 create or modify resources and run only after you confirm the plan, and 1 is destructive and requires a typed risk phrase. 1 of them also carries a step-level approval gate.
What teams use it for
Teams use OrchestrAI to create an Azure SQL logical server, set an Azure AD administrator on it so nobody depends on a SQL password, and add the application databases. A SQL Managed Instance can be created the same way when an app needs instance-level features. There is no firewall rule operation and no way to list or resize databases, so opening the server to a client IP and changing service tiers still happen in the portal.
Every Azure SQL operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Create Azure SQL Database |
Create a database on an Azure SQL Server | Creates resources | No |
Create Azure SQL Database |
Create an Azure SQL Database | Creates resources | No |
Create Azure SQL Managed Instance |
Create an Azure SQL Managed Instance | Creates resources | No |
Create Azure SQL Server |
Create an Azure SQL Database server | Creates resources | No |
Set Azure SQL Server Azure AD Administrator |
Set an Azure AD administrator for an Azure SQL Server | Creates resources | No |
Delete Azure SQL Server |
Delete an Azure SQL Database server | Destructive | Yes |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
Prompts that work
- Create an Azure SQL server called sql-acme-prod in rg-prod in eastus with admin user sqladmin
- Set the Azure AD group DBAdmins as the administrator of sql-acme-prod
- Create a database named orders on sql-acme-prod with the S1 service objective
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Is deleting an Azure SQL server protected in OrchestrAI?
- Yes, server deletion is critical risk because every database on the server goes with it, so it requires a typed risk phrase in addition to a confirmation.
- Can OrchestrAI create an Azure SQL Managed Instance?
- It can. Managed instance creation is a medium-risk operation, and OrchestrAI shows the plan and a cost estimate before it starts, which matters since managed instances take a long time to provision.
- Which Azure SQL operations need an extra approval step?
- One operation carries a step-level approval gate on top of plan confirmation: Delete Azure SQL Server. It is classed destructive and cannot run without a typed risk phrase.
Other Azure services
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.