What authentication does this API use?

The API uses Azure AD OAuth 2.0 with the implicit flow, scoped to user_impersonation against management.azure.com. Through Jentic, the bearer token is held in your Jentic One instance and exchanged for a scoped access token at execution time.

Can I register multiple SQL Servers under one registration?

Yes. A sqlServerRegistration is a parent resource; SQL Server entries are children at /sqlServerRegistrations/{name}/sqlServers/{sqlServerName}. PUT each child to add it; DELETE to detach without removing the parent.

What are the rate limits for this API?

Azure Resource Manager applies tenant-level throttling - typically 12,000 reads and 1,200 writes per hour per subscription. Most operations on this preview API are synchronous and return 200 with the resulting resource.

How do I create a registration through Jentic?

Run pip install jentic, then search for 'register sql server with azure data'. Jentic returns the PUT /sqlServerRegistrations/{name} operation, loads the registration property schema, and executes against the resource group you specify.

Does this API run queries against the registered SQL Servers?

No. This API manages registration metadata only. Connecting to the registered SQL Server data plane to run queries requires a SQL client and direct network access to the on-prem instance.

Can I limit what my agent is allowed to do with the Microsoft Azure Data SQL Server API?

Yes. Because you run Jentic One yourself, your own rules decide which Microsoft.AzureData operations and credentials the agent may use. You pick the exact calls it can make, so destructive operations like DELETE on a sqlServerRegistration or on a SQL Server child are excluded unless you explicitly add them. Since the registration and child names sit in the URL path, a rule can also pin the agent to a single registration while still allowing it to list or create the SQL Server entries beneath it.