Microsoft MVP | User Adoption, Dynamics 365 + Power Platform Expert at Reenhanced
Dynamics 365 roadmap items discussed for November include a refreshed Quick Campaign email experience, AI data enrichment and reusable maintenance plans in Field Service. These updates may matter to Sales users and administrators, as well as organizations that manage service assets or use Field Service with Project Operations. Heidi Neuhauser [MVP] reviews the roadmap items and describes what she could verify, along with questions that remain open.
The Sales Quick Campaign item is described as an enhanced experience for one-time bulk email outreach. The proposed interface brings campaign setup into a more consolidated flow, with a campaign title, audience, activity type and template selection. The audience options remain contacts, leads and accounts, while the new experience discussed is focused on email.
AI data enrichment is another Sales roadmap item. According to the details read in the discussion, it applies to opportunities, leads, contacts and accounts, and can use CRM notes as a data source. The item also describes filtering records, analyzing proposed changes and having a person review and approve updates. The exact relationship between notes and other CRM activities is not explained.
For Field Service, reusable maintenance plans are intended to let teams define a template and apply it to eligible assets. The described process is to build a plan, assign it to one or more assets, and then schedule activities, forecast maintenance and generate work. The discussion also flags integration updates between Field Service and Project Operations, including task-level work order associations, project-driven scheduling, project dependencies, integrated time entry and financial integration.
The Quick Campaign experience is identified as a preview and is limited, in the roadmap description discussed, to Sales Hub and Sales Professional apps. The speaker says it would not work in a custom model-driven app. The discussion also says the setting needs to be enabled, but the presenter could not determine how to get it working in her demo environment.
The AI enrichment item distinguishes notes by the license of the user who created them: only notes added by users with Sales Premium licenses are described as being used. That could matter where users have different licenses and contribute notes to the same records. The material does not clarify the licensing requirements for using enrichment or how any related credits are charged.
The maintenance-plan item is relevant to Field Service teams managing assets that can share a preventive maintenance template. The transcript gives no detailed prerequisites, licensing information or supported-region details for these items. It reports preview availability for the maintenance plan in October and a rollout start in February, but does not specify a year for those milestones.
The transcript does not provide a verified, step-by-step configuration guide. It does outline the intended user flow for the two most concrete changes. Treat these as descriptions of the roadmap items, not confirmation that the steps are currently available in every environment.
For AI enrichment, the discussion describes a review-and-approval step for proposed record updates. It does not provide the exact menu path or configuration steps, so administrators should consult the relevant product documentation before planning a deployment.
The Quick Campaign preview was not demonstrated live: Neuhauser says she could not make it work in either a new demo environment or her own environment. She also notes that Exchange would be required to show the email functionality. As a result, the proposed interface and its behavior should be treated as roadmap details rather than a hands-on verification.
Other details remain unsettled in the discussion. For Quick Campaigns, the speakers question what scheduling options will be available and how other activity types will work. For AI enrichment, they raise questions about how notes are treated alongside activities, which users' notes qualify and how credits factor into licensing. The transcript does not resolve those points.
The Field Service and Project Operations integration list is limited to named areas of improvement; it does not explain configuration or deployment. The discussion also does not establish whether each roadmap item has rolled out or is available to a particular tenant. Check the current roadmap and product documentation before making operational or licensing decisions.
The discussion identifies it as a preview for Sales Hub and Sales Professional apps, not custom model-driven apps. It does not establish availability across tenants.
The audiences described are contacts, leads and accounts. The new experience discussed is focused on email.
The roadmap details discussed say only notes added by users with Sales Premium licenses are used. The discussion does not clarify how notes relate to other activities or explain the full licensing and credits requirements.
The described flow is to create a reusable template, apply it to eligible assets, then schedule activities, forecast maintenance and generate work. Detailed setup requirements are not provided.