Connecting Revial to Microsoft Dynamics 365

The CRM integration is set up once for the whole organisation. It acts as one identity — a Dynamics user, or an Application User — and that identity's Dataverse security roles decide what Revial can see and change.

For every column Revial reads and writes, see What Revial syncs with Microsoft Dynamics 365. For the authentication model, privileges and API behaviour, see the Dynamics 365 technical integration guide.

OverviewCopy Anchor Link

• Meeting briefs — enriched with opportunity stage, contacts and account details from Dynamics.
• Meeting summaries — written back automatically as a note on the matched opportunity, account or contact.
• Contact and company matching — meeting participants are linked to Dynamics records.
• Deal context — open opportunities, stages and values appear alongside meetings.

Revial syncs accounts, contacts, leads, opportunities and sales process stages. Activities (appointments, emails, tasks, phone calls) and notes are not synced from Dynamics.

Two ways to connectCopy Anchor Link

RequirementsCopy Anchor Link

• Revial role: Admin or Owner in your organisation.
• Revial plan: one that includes the CRM integration (Medium or Sales).
• Dataverse access: the connecting identity needs a security role with read access to accounts, contacts, leads, opportunities and system users, and create access to notes. Dynamics administrator rights are not required.
• Your Dynamics 365 instance URL, for example https://yourorg.crm4.dynamics.com.

Step 1 — Find your instance URLCopy Anchor Link

Open Dynamics in your browser and copy the address up to .dynamics.com. It has the form https://yourorg.crmN.dynamics.com, where the region suffix depends on your data centre — for example crm North America, crm4 EMEA (including Finland), crm11 United Kingdom.

Revial accepts any crmN region. Paths and trailing slashes are removed automatically; the address must use HTTPS.

Step 2 — Open CRM IntegrationsCopy Anchor Link

1. In Revial, go to Organization → CRM Integrations.
2. Find the Microsoft Dynamics 365 card (Not connected).

Step 3a — Connect with Microsoft sign-inCopy Anchor Link

1. Paste the URL into Enter your Dynamics 365 URL.
2. Click Connect with Microsoft.
3. Choose the Microsoft account the integration should use and sign in.
4. Review the requested permissions and click Accept.

Revial checks the connection with Dataverse WhoAmI and reads the user's name and email before saving.

Step 3b — Connect with a service account (app-only)Copy Anchor Link

Your Entra administrator first creates:

1. A single-tenant app registration with a client secret. It needs no API permissions and no redirect URI.
2. An Application User in Dynamics for that app, in the right business unit, with a security role covering the access above.

Then in Revial:

1. Click Connect with a service account (app-only) instead.
2. Enter the Dynamics URL, Application (client) ID, Client secret and Directory (tenant) ID (a GUID).
3. Click Connect service account.

Revial obtains a token and runs WhoAmI before saving anything. The client secret is stored encrypted.

Step 4 — Verify the connectionCopy Anchor Link

The card shows Connected with the Microsoft user's email — or "Connected via service principal (Application User)" — the instance URL, Sync Now and Disconnect.

First syncCopy Anchor Link

The first sync starts automatically in the background when you connect. After that Revial syncs roughly every hour while Automatic Sync is on in Organization → CRM Settings. Sync Now starts a sync straight away.

Microsoft Entra — granting admin consent (Microsoft sign-in only)Copy Anchor Link

If your tenant does not let users consent to apps themselves, a user sees "Need admin approval" and the request goes to Admin consent requests in Entra.

1. Sign in to the Microsoft Entra admin center as a Global Administrator or Application Administrator.
2. Go to Enterprise applications → Admin consent requests.
3. Find Revial — it appears after the first connection attempt.
4. Open Permissions, click Grant admin consent and confirm.

Consent covers Revial's delegated access to Dynamics 365 as the signed-in user. Granting it applies to all users in the tenant — review it with your security team. The service-account method needs no consent.

Managing the connectionCopy Anchor Link

Syncing — Sync Now on the card starts a sync; the Automatic Sync toggle in CRM Settings turns hourly syncing on or off. Turning it off also stops meeting summaries being pushed automatically.

Disconnecting — Disconnect, then confirm. Revial stops syncing and, in the background, deletes its synced copy of your Dynamics data, the stored tokens or client secret, and the field mappings. Notes Revial already wrote stay in Dynamics.

Reconnecting — a new Dynamics connection is refused while one exists. A connection in an error state can be reconnected with Microsoft sign-in, but its connection settings (such as appointment configuration) are reset. Rotating a service-account secret currently means disconnecting and connecting again, which removes and re-syncs the data.

Other CRMs can be connected alongside Dynamics.

TroubleshootingCopy Anchor Link

Connection errors

Sync problems

Quick guide — connectingCopy Anchor Link

1. Copy your Dynamics URL from the browser address bar.
2. Revial → Organization → CRM Integrations → Microsoft Dynamics 365.
3. Paste the URL and click Connect with Microsoft — or use the service-account option.
4. Sign in and accept. If you see "Need admin approval", forward the consent section above to your IT administrator.
5. Check the card shows Connected. The first sync starts automatically.