Connect Tablyne to Azure Cosmos DB
Connect to a Cosmos DB account for NoSQL with a key, a connection string, Microsoft Entra ID or the local emulator.
Tablyne connects to the Azure Cosmos DB for NoSQL API over HTTPS. Enter the account endpoint, which looks like https://<account>.documents.azure.com:443/. The endpoint cannot carry a path, a query string or credentials. Tablyne rejects them and tells you why.
You can sign in in two ways. The first is the account key. Tablyne stores it in the system keychain, not in the connection file. If you only plan to read, paste the read-only key. The second is Microsoft Entra ID, which uses your existing az login. You can name a tenant, and the token is sent only to your account’s documents.azure.com host. With Entra ID you can edit documents, but container and settings changes need the account key.
You can also paste a Cosmos DB connection string, and Tablyne fills in the endpoint and key. A button fills in the local emulator values. Plain HTTP is accepted only for the emulator on localhost. A connection marked as production refuses HTTP.
Other options on the form are the initial database, the RU ceiling for each query, the number of documents per page (1 to 1,000) and the connect timeout.
Tablyne handles the NoSQL API only. If your account uses the API for MongoDB, Cassandra or PostgreSQL, Tablyne says so and points you to the matching connection form. The Table API and the Gremlin API are not supported in this version.
The connection test shows the account name and the round-trip time. Tablyne also has a read-only option for the connection. It is a safeguard inside the app, so for enforcement on the server use the account’s read-only key.