Article
Notes about outbound marketing removal - Dynamics 365 ...
learn.microsoft.com
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
Asset library: Common component; all items are available in real-time journeys. “Insights reports that are part of the outbound marketing user interface aren't available anymore.” Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API.
Asset library: Common component; all items are available in real-time journeys. “The SourceSystem attribute refers to the source system (outbound marketing or real-time journeys) that generated the interaction.” Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API.
Marketing lists: These are a Sales entity. You can keep using them in real-time journeys (you can include them in real-time journeys dynamic segments). “Other outbound marketing assets such as emails, content blocks, forms, marketing pages, consent data, journeys, templates, lead scoring models, social posts, and subscription lists weren't removed.” While the outbound marketing user interface isn't available in the sitemap, you can still access outbound marketing tables using the advanced search (or, in some cases, using the standard user interface, such as in the contact timeline, which has links to outbound marketing messages). These tables, while available, may not work correctly and aren't supported.
Marketing lists: These are a Sales entity. You can keep using them in real-time journeys (you can include them in real-time journeys dynamic segments). “These assets can't be used in real-time.” While the outbound marketing user interface isn't available in the sitemap, you can still access outbound marketing tables using the advanced search (or, in some cases, using the standard user interface, such as in the contact timeline, which has links to outbound marketing messages). These tables, while available, may not work correctly and aren't supported.
Accessing outbound marketing tables and data “While the tables and data remain in the system, they aren't being updated or refreshed, and some of them may not be usable or accessible from the user interface:” Asset library: Common component; all items are available in real-time journeys.
Other outbound marketing assets such as emails, content blocks, forms, marketing pages, consent data, journeys, templates, lead scoring models, social posts, and subscription lists weren't removed. These assets can't be used in real-time. Any custom user interface that updated or added records to these assets and relied on outbound marketing services may fail (for example, any custom user interface that had plugins that reacted on retrieve/retrieve multiple messages). “These tables, while available, may not work correctly and aren't supported.” Past communications about outbound marketing removal
If you previously used outbound marketing, you may still be able to access most of your tables and data created in outbound marketing. When outbound marketing was removed, the sitemap entry and outbound marketing services were removed. We didn't remove any publicly documented outbound marketing tables or data in those tables, with some exceptions (see below). You can access these tables through the Power Apps Maker portal. While the tables and data remain in the system, they aren't being updated or refreshed, and some of them may not be usable or accessible from the user interface: “Asset library: Common component; all items are available in real-time journeys.” Outbound marketing analytics data: Merged with real-time journeys data. Existing Power BI custom reports for outbound marketing don't work with the consolidated data because the data format, its location, and access methods are different in real-time journeys. Insights reports that are part of the outbound marketing user interface aren't available anymore. If you want to rebuild those reports, see Build custom reports using Microsoft Fabric integration. While the data models are the same between outbound marketing and real-time journeys, reconfigure existing custom reports and pipelines to use the new data sources in Microsoft Fabric. See the Customer Insights - Journeys interaction data schema overview. The SourceSystem attribute refers to the source system (outbound marketing or real-time journeys) that generated the interaction. You can also export your data using Microsoft Fabric capabilities and its native connectors. Alternatively, if you want to use a third-party system to store and process Customer Insights - Journeys data, see Leveraging Customer Insights - Journeys interaction data without Fabric.
“This module was removed in May 2026.” This article explains which outbound marketing tables, data, assets, and archived documentation remain available after removal.
Accessing outbound marketing tables and data “When outbound marketing was removed, the sitemap entry and outbound marketing services were removed.” Asset library: Common component; all items are available in real-time journeys.
Accessing outbound marketing tables and data “You can access these tables through the Power Apps Maker portal.” Asset library: Common component; all items are available in real-time journeys.
Other outbound marketing assets such as emails, content blocks, forms, marketing pages, consent data, journeys, templates, lead scoring models, social posts, and subscription lists weren't removed. These assets can't be used in real-time. Any custom user interface that updated or added records to these assets and relied on outbound marketing services may fail (for example, any custom user interface that had plugins that reacted on retrieve/retrieve multiple messages). “While the outbound marketing user interface isn't available in the sitemap, you can still access outbound marketing tables using the advanced search (or, in some cases, using the standard user interface, such as in the contact timeline, which has links to outbound marketing messages).” Past communications about outbound marketing removal
Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API. “However, these segments aren't updated and shouldn't be used.” Marketing lists: These are a Sales entity. You can keep using them in real-time journeys (you can include them in real-time journeys dynamic segments).
Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API. “The segment table doesn't contain the actual list of members; this information was stored in an internal table that was removed.” Marketing lists: These are a Sales entity. You can keep using them in real-time journeys (you can include them in real-time journeys dynamic segments).
Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API. “Segment queries are stored in the msdyncrm_segment table and remain available.” Marketing lists: These are a Sales entity. You can keep using them in real-time journeys (you can include them in real-time journeys dynamic segments).
Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API. “Outbound marketing segments may still be visible in real-time journeys.” Marketing lists: These are a Sales entity. You can keep using them in real-time journeys (you can include them in real-time journeys dynamic segments).
Outbound marketing segments: Aren't removed, but aren't usable. The segment table doesn't contain the actual list of members; this information was stored in an internal table that was removed. Segment queries are stored in the msdyncrm_segment table and remain available. Outbound marketing segments may still be visible in real-time journeys. However, these segments aren't updated and shouldn't be used. “Marketing lists: These are a Sales entity.” Other outbound marketing assets such as emails, content blocks, forms, marketing pages, consent data, journeys, templates, lead scoring models, social posts, and subscription lists weren't removed. These assets can't be used in real-time. Any custom user interface that updated or added records to these assets and relied on outbound marketing services may fail (for example, any custom user interface that had plugins that reacted on retrieve/retrieve multiple messages).
Outbound marketing segments: Aren't removed, but aren't usable. The segment table doesn't contain the actual list of members; this information was stored in an internal table that was removed. Segment queries are stored in the msdyncrm_segment table and remain available. Outbound marketing segments may still be visible in real-time journeys. However, these segments aren't updated and shouldn't be used. “You can keep using them in real-time journeys (you can include them in real-time journeys dynamic segments).” Other outbound marketing assets such as emails, content blocks, forms, marketing pages, consent data, journeys, templates, lead scoring models, social posts, and subscription lists weren't removed. These assets can't be used in real-time. Any custom user interface that updated or added records to these assets and relied on outbound marketing services may fail (for example, any custom user interface that had plugins that reacted on retrieve/retrieve multiple messages).
Outbound marketing analytics data: Merged with real-time journeys data. Existing Power BI custom reports for outbound marketing don't work with the consolidated data because the data format, its location, and access methods are different in real-time journeys. Insights reports that are part of the outbound marketing user interface aren't available anymore. If you want to rebuild those reports, see Build custom reports using Microsoft Fabric integration. While the data models are the same between outbound marketing and real-time journeys, reconfigure existing custom reports and pipelines to use the new data sources in Microsoft Fabric. See the Customer Insights - Journeys interaction data schema overview. The SourceSystem attribute refers to the source system (outbound marketing or real-time journeys) that generated the interaction. You can also export your data using Microsoft Fabric capabilities and its native connectors. Alternatively, if you want to use a third-party system to store and process Customer Insights - Journeys data, see Leveraging Customer Insights - Journeys interaction data without Fabric. “There are some critical differences in the event forms and pages between outbound marketing and real-time journeys.” Outbound marketing segments: Aren't removed, but aren't usable. The segment table doesn't contain the actual list of members; this information was stored in an internal table that was removed. Segment queries are stored in the msdyncrm_segment table and remain available. Outbound marketing segments may still be visible in real-time journeys. However, these segments aren't updated and shouldn't be used.
Outbound marketing analytics data: Merged with real-time journeys data. Existing Power BI custom reports for outbound marketing don't work with the consolidated data because the data format, its location, and access methods are different in real-time journeys. Insights reports that are part of the outbound marketing user interface aren't available anymore. If you want to rebuild those reports, see Build custom reports using Microsoft Fabric integration. While the data models are the same between outbound marketing and real-time journeys, reconfigure existing custom reports and pipelines to use the new data sources in Microsoft Fabric. See the Customer Insights - Journeys interaction data schema overview. The SourceSystem attribute refers to the source system (outbound marketing or real-time journeys) that generated the interaction. You can also export your data using Microsoft Fabric capabilities and its native connectors. Alternatively, if you want to use a third-party system to store and process Customer Insights - Journeys data, see Leveraging Customer Insights - Journeys interaction data without Fabric. “Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API.” Outbound marketing segments: Aren't removed, but aren't usable. The segment table doesn't contain the actual list of members; this information was stored in an internal table that was removed. Segment queries are stored in the msdyncrm_segment table and remain available. Outbound marketing segments may still be visible in real-time journeys. However, these segments aren't updated and shouldn't be used.
Asset library: Common component; all items are available in real-time journeys. “Outbound marketing analytics data: Merged with real-time journeys data.” Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API.
Asset library: Common component; all items are available in real-time journeys. “Existing Power BI custom reports for outbound marketing don't work with the consolidated data because the data format, its location, and access methods are different in real-time journeys.” Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API.
Asset library: Common component; all items are available in real-time journeys. “Insights reports that are part of the outbound marketing user interface aren't available anymore.” Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API.
Asset library: Common component; all items are available in real-time journeys. “While the data models are the same between outbound marketing and real-time journeys, reconfigure existing custom reports and pipelines to use the new data sources in Microsoft Fabric.” Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API.
Asset library: Common component; all items are available in real-time journeys. “The SourceSystem attribute refers to the source system (outbound marketing or real-time journeys) that generated the interaction.” Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API.
Asset library: Common component; all items are available in real-time journeys. “You can also export your data using Microsoft Fabric capabilities and its native connectors.” Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API.
Asset library: Common component; all items are available in real-time journeys. “Alternatively, if you want to use a third-party system to store and process Customer Insights - Journeys data, see Leveraging Customer Insights - Journeys interaction data without Fabric.” Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API.
Marketing lists: These are a Sales entity. You can keep using them in real-time journeys (you can include them in real-time journeys dynamic segments). “Any custom user interface that updated or added records to these assets and relied on outbound marketing services may fail (for example, any custom user interface that had plugins that reacted on retrieve/retrieve multiple messages).” While the outbound marketing user interface isn't available in the sitemap, you can still access outbound marketing tables using the advanced search (or, in some cases, using the standard user interface, such as in the contact timeline, which has links to outbound marketing messages). These tables, while available, may not work correctly and aren't supported.
Outbound marketing analytics data: Merged with real-time journeys data. Existing Power BI custom reports for outbound marketing don't work with the consolidated data because the data format, its location, and access methods are different in real-time journeys. Insights reports that are part of the outbound marketing user interface aren't available anymore. If you want to rebuild those reports, see Build custom reports using Microsoft Fabric integration. While the data models are the same between outbound marketing and real-time journeys, reconfigure existing custom reports and pipelines to use the new data sources in Microsoft Fabric. See the Customer Insights - Journeys interaction data schema overview. The SourceSystem attribute refers to the source system (outbound marketing or real-time journeys) that generated the interaction. You can also export your data using Microsoft Fabric capabilities and its native connectors. Alternatively, if you want to use a third-party system to store and process Customer Insights - Journeys data, see Leveraging Customer Insights - Journeys interaction data without Fabric. “Events: Shared capability between real-time journeys and outbound marketing; the same tables are used.” Outbound marketing segments: Aren't removed, but aren't usable. The segment table doesn't contain the actual list of members; this information was stored in an internal table that was removed. Segment queries are stored in the msdyncrm_segment table and remain available. Outbound marketing segments may still be visible in real-time journeys. However, these segments aren't updated and shouldn't be used.
Asset library: Common component; all items are available in real-time journeys. “While the data models are the same between outbound marketing and real-time journeys, reconfigure existing custom reports and pipelines to use the new data sources in Microsoft Fabric.” Events: Shared capability between real-time journeys and outbound marketing; the same tables are used. These tables and the data aren't removed. There are some critical differences in the event forms and pages between outbound marketing and real-time journeys. Therefore, events created in outbound marketing aren't usable in real-time and must be recreated in real-time using the user interface or API.
Quotes are verbatim and belong to their publishers. Where a quote has been translated, the original wording is kept below it.