Dynamics 365 Customer Insights Data to Fabric OneLake: Profile Shortcuts Planned for October 2026 Preview

What Microsoft says is coming​

Here is what the roadmap record says:

• Status: In development.
• Preview: October 2026.
• General availability: November 2026.
• Cloud and platform: Worldwide (Standard Multi-Tenant), web.
• Who gets it: Enabled automatically for admins, makers and marketers.

The core promise is that you can create OneLake shortcuts to the managed data lake behind Customer Insights - Data. You would then use unified profiles and insights in your core analytics and downstream workloads without copying the data.

Microsoft's example is a fictional company, Contoso, with several departments. Once Contoso creates shortcuts to all its profiles and insights, every department can use the 360-degree customer view. Microsoft's scenario says this visibility leads more departments to feed their own customer data into the unified profiles, which improves the profiles.

These dates are estimates. Microsoft's roadmap page says all release information is subject to change. It also says entries are removed once a feature reaches general availability, or is cancelled or postponed. We could not confirm from the live roadmap page that this item has reached preview. I'm not claiming it has.

Don't confuse this with the connector that already exists​

Microsoft has been building Fabric integration into Customer Insights - Data for a while. The existing pieces move data in the opposite direction.

• The input connector. Microsoft Learn describes a Fabric OneLake connector that reads Delta tables directly from your Fabric workspace, so you don't need to copy or stage data in Azure Data Lake. A Microsoft 365 admin blog says this source will reach public preview on May 29, 2026.
• The roadmap item. Item 577816 is about output. Unified profiles and insights that Customer Insights - Data creates would become visible in OneLake.

An earlier wave-2 2025 release-plan summary, written up by a community blogger, already used the same wording. It described getting access to your CI-Data data in Fabric OneLake, so you don't have to export your insights from CI-Data. The idea has been on Microsoft's plans for some time. The date has now moved to this roadmap entry.

Why shortcuts matter​

Microsoft's Fabric documentation describes shortcuts as references that add selected data to the OneLake namespace. The data stays at its source. That is why a shortcut-based design can cut data movement and avoid maintaining separate export pipelines.

Some caveats follow from Microsoft's general guidance on shortcuts:

• Shortcuts don't do heavy lifting. Microsoft says to use pipelines, dataflows or copy jobs when you need complex multi-source transformations, scheduling, or movement to destinations outside OneLake.
• "No copying" does not mean "no work". You still have to plan permissions and ownership. You also need to monitor the source, because a shortcut shows the state of whatever it points to.
• Microsoft says shortcuts to mirrored tables are read-only and inherit the source's security model. That is documented for mirrored sources, not for this feature. Whether Customer Insights shortcuts behave the same way is unconfirmed.

What isn't known yet​

The available material leaves several practical questions unanswered. Plan around these gaps and don't assume answers:

• Which artifacts are exposed: profiles only, or also segments, measures and enrichments.
• How often the data refreshes in OneLake.
• What permissions and security model apply to the new shortcuts.
• Which Fabric workloads can consume the data.
• Whether there are licensing or capacity implications.
• Any measured time or cost savings.

Microsoft's description says the capability saves time and reduces cost. It gives no figures. I'd read that as marketing language until real numbers or documentation appear.

One thing that is not guaranteed is the feedback loop in the Contoso story. Nothing in the evidence says that shortcuts automatically bring new departmental data into unification or identity resolution. Those steps stay with Customer Insights - Data's own ingestion and unification processes.

What admins can do now​

You can't configure the new output path yet, but you can prepare. The documented input connector shows the kind of Fabric settings that Customer Insights integrations tend to depend on. The new feature may or may not use the same ones:

1. A Fabric tenant admin enables Users can access data stored in OneLake with apps external to Fabric. Microsoft says changes can take up to 15 minutes to apply.
2. The service principal Dynamics 365 AI for Customer Insights goes into the Fabric workspace with at least the Contributor role. Microsoft recommends using a security group.
3. Service principals can call Fabric public APIs is enabled in the tenant's developer settings.
4. If Fabric inbound access protection is on, Private Link has to be set up.

These are documented requirements for the existing input connector. The roadmap output feature may differ, so check the final documentation when preview lands.

If you use the input connector today, a few documented limits also apply:

• Table format: Only managed Delta tables are supported.
• Primary keys: Each table needs a unique, non-null primary key.
• Table names: Physical table names must be ASCII-safe.
• Delta log retention: Keep Delta log history longer than your longest refresh cadence.
• Vacuuming: Avoid aggressive VACUUM operations on tables Customer Insights ingests.

Related documented migration path​

Microsoft also documents converting an existing Azure Data Lake Delta-table source to a Fabric OneLake source. This is a separate input-side feature. It keeps tables, mappings and downstream dependencies in place. It also includes a verify step and a revert option. Microsoft warns that editing the converted source before the first refresh is confirmed removes the saved rollback information.

The bottom line​

Customer Insights - Data is working toward two-way OneLake integration. Fabric data can already come in. Profiles and insights are slated to go out, with preview listed for October 2026 and general availability for November 2026. For Fabric-centric organizations this could remove an export step. Before you design around it, wait for the preview documentation. It should answer the refresh, permission and artifact questions above.