Azure Cosmos DB
by Microsoft
Applications on Azure often keep user profiles, carts and catalog items as JSON documents in Cosmos DB containers. Reading documents and the change feed through the SDK copies them into the Lake on a schedule, where nested JSON becomes queryable alongside orders, payments and support data instead of staying behind application code.
- Category
- Cloud & Data Platforms
- Type
- Database
- Interface
- SDK
- Built with
- Connect Anything
- Credentials
- Signed requests, OAuth 2.0
02Data
What you can sync.
- Documents
- Containers
- Databases
- Change feed
Load Azure Cosmos DB documents into your Lake and model it in the Warehouse with the rest of your stack.
Need more? Name any other Azure Cosmos DB data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- Signed requests (key and secret)
- OAuth 2.0 (client ID, client secret, refresh token)
Azure Cosmos DB uses signed requests (key and secret) or OAuth 2.0 (client ID, client secret, refresh token). You add the credentials once, when the AI asks for them, and it tells you where to create them in Microsoft if you need help.
04Questions
Questions you can answer.
Once Azure Cosmos DB data is in your Lake, ask an AI Mind in plain words or build the answer in DataPrism BI.
- How many carts created in Cosmos DB last week never turned into an order?
- Which document properties are missing or null across product catalog items?
- How do user profiles in Cosmos DB match customer records in the CRM?
- How many documents changed per day in each container, according to the change feed?
05How it works
How it works in DataMind.
-
Pick Azure Cosmos DB.
Open Lake, pick Azure Cosmos DB in the source picker and name the connection. Connect Anything opens with a ready prompt that points the AI at the Azure Cosmos DB API docs.
-
Answer a few questions.
The AI reads the Azure Cosmos DB documentation, then asks which credentials you will use, which data to sync (for example documents and containers), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
The connector agent writes a Python connector for Azure Cosmos DB, tests it against the live API and shows you sample rows. Then the data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
06Pairs
Works well with Azure Cosmos DB.
Sources teams join with Azure Cosmos DB in the Warehouse, each one connected the same way.
