How to integrate Microsoft Azure with Bubble

Integrating Microsoft Azure with Bubble is done through Bubble’s API Connector. Azure exposes normal HTTPS APIs, so you connect by creating an Azure App Registration, getting a token from Azure’s OAuth 2.0 endpoint, then calling the Azure service you need (Graph API, Cognitive Services, Storage, etc.). Bubble does not have a native Azure plugin, but every Azure REST API works if you authenticate correctly.

How to integrate Azure with Bubble

The core idea is: you first get an access token from Azure, then you use that token in your API calls. Bubble does this inside the API Connector. Azure always requires an App Registration, which gives you a Client ID, Client Secret, and Tenant ID. Those are pasted into Bubble so Bubble can authenticate on your behalf.

• Create an App Registration in Azure Portal and enable the permissions you need.
• Copy the Client ID, Client Secret, Tenant ID.
• In Bubble, install the API Connector.
• Configure OAuth2 Client Credentials or manually request a token.
• Use the returned token to call your Azure endpoint.

Example: Getting an Azure Access Token in Bubble

This is the simplest working setup using the Client Credentials flow (server-to-server). In API Connector create a call to get a token:

{
  "url": "https://login.microsoftonline.com/YOUR_TENANT_ID/oauth2/v2.0/token",
  "method": "POST",
  "headers": {},
  "body": "client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET&scope=https%3A%2F%2Fgraph.microsoft.com%2F.default&grant_type=client_credentials"
}

Set the call as Action and send body as Form-data or x-www-form-urlencoded. The response gives you access\_token.

Calling an Azure API from Bubble

Then create another API call and include the token:

{
  "url": "https://graph.microsoft.com/v1.0/users",
  "method": "GET",
  "headers": {
    "Authorization": "Bearer <dynamic access_token>"
  }
}

• You run the token call first inside a Backend Workflow.
• Store the token in the database (expires in ~3600 seconds).
• Use the stored token in all other Azure calls.

Important Notes

• Avoid Client Credentials if you need a logged-in Microsoft user. Then use OAuth2 User-Agent flow instead.
• Cognitive Services (AI, OCR, TTS) usually do not use Azure AD; they require passing your Ocp-Apim-Subscription-Key header.
• Azure Storage REST API also works the same way but requires correct shared key signing.