Azure Service Bus
by Microsoft
Azure enterprise message broker with queues and topics, reachable over AMQP SDKs and a REST API.
- Category
- Cloud & Data Platforms
- Type
- Streaming & messaging
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- OAuth 2.0, Vendor credentials
02Data
What you can sync.
- Messages
- Queues
- Topics
- Subscriptions
Put Azure Service Bus messages next to revenue and usage, so every cost has an owner and a reason.
Need more? Name any other Azure Service Bus data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- OAuth 2.0 (client ID, client secret, refresh token)
- Other credentials
Azure Service Bus uses OAuth 2.0 (client ID, client secret, refresh token) or other credentials. 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 Service Bus.
Open Lake, pick Azure Service Bus in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Azure Service Bus API docs.
-
Answer a few questions.
The AI reads the Azure Service Bus documentation, then asks which credentials you will use, which data to sync (for example messages and queues), 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 Service Bus data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
05Related
