Here are 3 effective ways to build that relational bridge, depending on your technical comfort level. 1. This is the "gold standard" for 2026. Microsoft has replaced the old "Export to Data Lake" service with the Azure Synapse Link or the Microsoft Fabric integration.
You "link" your Dataverse environment to a Fabric workspace or an Azure Data Lake Storage account.
It automatically synchronizes your tables (Accounts, Contacts, Leads) into Parquet or Delta format, which can be queried using SQL just like a relational database.
CIJ interactions (the "big data") are naturally stored in the lake, so linking them here keeps everything in one place.
2. If you already have an existing SQL Server or PostgreSQL database and want to "pull" the data into it, you'll use the OData v4 Web API.
You can use Azure Data Factory (ADF) or SSIS with a Dynamics 365 connector.
1. Point ADF to your Dynamics 365 Organization URL. 2. Select the entities (tables) you need. 3. Map the fields to your destination SQL tables.
This is great for Profile data (who people are), but it is very inefficient for Interaction data (what they did) due to API throttling.
3. When you are looking for Journey data specifically (which journey did they join? which email was sent?), you need to look at specific tables.
Tables starting with msdynmkt_ (e.g., msdynmkt_journey, msdynmkt_email) contain the "definition" of your marketing assets.
These are the "events." In CIJ, these aren't always visible as standard SQL tables in Dataverse. You must enable the Analytics export in the CIJ Settings to push these into your own Azure storage for your relational database to ingest.
if this helps pls mark as verified so that it may be helpful for someone else. Thanks!
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.