Azure Table Storage
by Microsoft
NoSQL key-attribute store in Azure Storage; the Table service OData REST API queries tables and entities.
- Category
- Cloud & Data Platforms
- Type
- Database
- Interface
- OData API
- Built with
- Connect Any API
- Credentials
- Signed requests, OAuth 2.0
02Data
What you can sync.
- Tables
- Entities
Put Azure Table Storage tables next to revenue and usage, so every cost has an owner and a reason.
Need more? Name any other Azure Table Storage 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 Table Storage 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.
04How it works
How it works in DataMind.
-
Pick Azure Table Storage.
Open Lake, pick Azure Table Storage in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Azure Table Storage API docs.
-
Answer a few questions.
The AI reads the Azure Table Storage documentation, then asks which credentials you will use, which data to sync (for example tables and entities), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Azure Table Storage data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.