Connect your app to Azure Cloud API

1. 1

   Register an app in Microsoft Entra admin center under App registrations, set it to single tenant, and copy both the Directory (tenant) ID and the Application (client) ID.

   Lovable needs these identifiers to locate and connect to your Azure account identity.

2. 2

   Create a new client secret under Certificates & secrets in your registered app, and immediately copy the secret's Value.

   This value acts as the password for the connection, and Azure will never display it again after you leave the page.

3. 3

   In the Azure Portal, open the target subscription or resource group, navigate to Access control (IAM), and assign a role such as Reader or Cost Management Reader to your registered app.

   Registering the app grants zero permissions by default; Azure requires an explicit role assignment or every request will fail with an authorization error.

4. 4

   In Lovable, navigate to Connectors, select Azure Cloud API, and click Connect.

   This opens the configuration screen to link your Azure credentials to your Lovable workspace.

5. 5

   Paste the Tenant ID, Client ID, and Client Secret Value into the configuration fields, configure sharing if needed, and click Connect.

   Lovable verifies the credentials against Microsoft Entra and saves the connection for use across your projects.

6. 6

   In your Lovable project chat, ask Lovable to link your Azure Cloud API connection and build your requested Azure dashboard or tool.

   This enables your project to query Azure Resource Manager through the secure gateway.

Use Azure Cloud API and build a dashboard of this month's Azure spend grouped by service, with a daily trend.

Service principal

A digital identity created for software instead of a human person, allowing apps to sign in and access Azure services securely.

Client secret

A secure password string generated in Azure that lets your service principal verify its identity.

Azure RBAC

Role-Based Access Control: Azure's system for granting specific permissions (like read-only or editor) to specific users or apps on specific resources.

Microsoft Entra ID

Microsoft's cloud identity and access management service (formerly known as Azure Active Directory).

• Do not paste the Secret ID instead of the secret Value; the Secret ID is just a label, not the actual password.
• Do not confuse the Object ID with the Application (client) ID; Lovable requires the Application (client) ID.
• Do not assume a successful connection test means full access; credentials can verify correctly while API calls still return 403 errors until you assign roles in Access control (IAM).
• Do not assign broad roles like Owner or Contributor if your app only needs to display data; use narrow roles like Reader or Cost Management Reader.
• Do not forget to note the client secret's expiration date; once expired, the connection stops working until you generate a new secret and update Lovable.
• Do not expect this connector to deploy or host your Lovable app on Azure; it only connects to Azure's management APIs.