Bolt.new AI and Microsoft Dynamics 365 integration: Step-by-Step Guide 2025

To integrate bolt.new with Microsoft Dynamics 365, you don’t connect “bolt” itself to Dynamics. Instead, you write code inside a bolt.new workspace that talks to Dynamics 365 through its real, documented REST API (the Microsoft Dataverse Web API). You authenticate using Azure AD OAuth (client credentials or delegated user auth), store the credentials inside bolt.new environment variables, and then call the Dynamics endpoints the same way you would from any backend. Bolt.new is simply the place where you scaffold and test the integration.

 

What You Actually Do to Integrate Bolt.new With Microsoft Dynamics 365

 

You create an Azure AD app registration, give it Dynamics 365 permissions, collect the OAuth credentials, store them in bolt.new environment variables, and then call the Dynamics 365 Web API from code running inside your bolt.new project. The Web API is a standard REST interface, so you send HTTPS requests (GET, POST, PATCH, DELETE) to URLs like https://YOUR-ORG.api.crm.dynamics.com/api/data/v9.2/contacts. This is the only correct way — there is no special “bolt integration” layer.

• Create an Azure AD application registration (this gives you a client_id and tenant_id).
• Generate a client secret or certificate (most bolt prototypes use client secret).
• Assign the app Dynamics CRM API permissions (Application or Delegated).
• Find your Dynamics 365 environment URL (example: https://org12345.crm.dynamics.com).
• Inside bolt.new, create environment variables for the credentials.
• In bolt.new, write backend code (Node.js/Express) that fetches an OAuth token from Microsoft, then calls the Dynamics REST endpoints.

 

Step-by-step Breakdown (Simple and Real)

 

You can follow this in bolt.new exactly. This is a real integration path used in production systems.

• Create Azure App Registration: Go to Azure Portal → Microsoft Entra ID → App registrations → New App. Note the client_id and tenant_id.
• Create Client Secret: Under Certificates & secrets → New client secret. Save the value.
• Assign API Permissions: Go to API permissions → Add → Dynamics CRM → choose user\_impersonation (or use Application permissions if using service accounts).
• Get Your Dynamics URL: From Power Platform admin center find “Environment URL” such as https://yourorg.crm.dynamics.com.
• Set Environment Variables in bolt.new: In the bolt sidebar → “Env Variables”.
  • DYNAMICS_CLIENT_ID
  • DYNAMICS_CLIENT_SECRET
  • DYNAMICS_TENANT_ID
  • DYNAMICS_ORG_URL

 

Working Code Example (Node.js inside bolt.new backend)

 

This is a real, correct, minimal OAuth + API call flow.

import fetch from "node-fetch";

// Fetch Microsoft OAuth token using client credentials
async function getToken() {
  const tokenUrl = `https://login.microsoftonline.com/${process.env.DYNAMICS_TENANT_ID}/oauth2/v2.0/token`;

  const params = new URLSearchParams();
  params.append("client_id", process.env.DYNAMICS_CLIENT_ID);
  params.append("client_secret", process.env.DYNAMICS_CLIENT_SECRET);
  params.append("grant_type", "client_credentials");
  params.append("scope", process.env.DYNAMICS_ORG_URL + "/.default"); // Required for Dynamics

  const res = await fetch(tokenUrl, {
    method: "POST",
    body: params
  });

  const data = await res.json();
  return data.access_token;
}

// Example: Fetch contacts from Dynamics 365
export async function getContacts(req, res) {
  try {
    const token = await getToken();

    const apiUrl = `${process.env.DYNAMICS_ORG_URL}/api/data/v9.2/contacts?$select=fullname,emailaddress1`;

    const crmRes = await fetch(apiUrl, {
      method: "GET",
      headers: {
        Authorization: `Bearer ${token}`,
        Accept: "application/json"
      }
    });

    const json = await crmRes.json();
    res.json(json);
  } catch (err) {
    res.status(500).json({ error: String(err) });
  }
}

 

What This Gives You Inside bolt.new

 

• You can directly read CRM objects like contacts, accounts, leads.
• You can create CRM records by using POST to the same API:

await fetch(`${process.env.DYNAMICS_ORG_URL}/api/data/v9.2/contacts`, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${token}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    firstname: "John",
    lastname: "Cole",
    emailaddress1: "[email protected]"
  })
});

• You can update or delete using PATCH and DELETE.
• You can wire the backend route to a frontend form inside bolt.new.

 

Important Notes So Everything Works

 

• Dynamics always requires Azure AD auth. There is no API key shortcut.
• Scopes must include /.default for client credentials.
• Every Dynamics org URL is unique. Never guess it.
• bolt.new environment variables are secure for prototyping, but production apps need a proper secrets store.

 

Summary

 

Integrating bolt.new with Microsoft Dynamics 365 is done by treating bolt as a coding workspace and talking to Dynamics through its Web API. You authenticate using Azure AD OAuth, store credentials in environment variables, and call the REST endpoints with normal HTTPS. This is stable, production-grade, and the same approach used for any full‑stack app — bolt just makes it faster to build and test the wiring.