Azure SQL API Authentication

How to authenticate Azure SQL API requests: one Bearer API key plus a connectionId. MindCloud handles Azure SQL's custom auth scheme for you.

Every Azure SQL API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Azure SQL account. This page covers both, plus exactly how to send them, so you do not need to visit any other page to get authenticated.

Steps to authenticate

Create a MindCloud account at app.mindcloud.co if you do not already have one.
Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
Create a Azure SQL connection in Connections. Azure SQL uses its own authentication scheme. You provide whatever it requires when you create the connection — MindCloud handles the provider-specific details for you.
Copy the connection’s connectionId — you will send it on every request alongside your MindCloud API Key.

How requests are authenticated

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Azure SQL account that should run the action. MindCloud stores and refreshes the Azure SQL credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions.

For example, calling with an Azure SQL connection looks like this:

The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which Azure SQL account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Set up your Azure SQL connection

You need the Azure SQL server name and database name. Depending on the authentication type you choose, you also need either a SQL username and password or Microsoft Entra service principal credentials.

Find the server and database names in Azure
In the Azure portal, open the Azure SQL server and database you want MindCloud to use. Note the server name and the database name exactly as Azure shows them.
Azure portal → SQL databases
Choose the authentication type you will use
Decide whether this connection will use SQL credentials or Microsoft Entra service principal credentials. If you use a service principal, collect the client ID, client secret, and tenant ID before you continue.
Enter the core connection fields in MindCloud
Enter the Server and Database values in MindCloud. If your environment uses the default Azure SQL port, use 1433. Leave Encrypt enabled unless your database administrator explicitly tells you to use a different setting.
Enter the credentials that match your authentication type
If you chose SQL authentication, enter the username and password. If you chose the Microsoft Entra service principal option, enter the client ID, client secret, and tenant ID instead.

Keep your key safe

Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs. Anyone with the key can call the Universal API as your MindCloud account, across every connection you have created.