How are Dynamics 365 partners handling complex legacy-to-cloud transitions today?
Hi all, I’m interested in understanding how partners are currently approaching complex ERP modernization scenarios, especially when working with long-standing legacy systems and heavily customized environments. From a partner delivery and strategy perspective: Are you seeing more clients choosing full reimplementation vs phased migration? How are you handling deeply customized legacy environments during transition to D365 Finance & SCM? What’s the biggest challenge today, technical complexity, client mindset, or cost justification? Are clients more open to cloud now, or still preferring hybrid/extended legacy setups? How are you positioning value when clients feel their current system is “good enough”? Would be great to hear real partner experiences across industries.
Customer Insights: default database capacity
Hello, I would like to know if, in the context of the initial deployment of Dynamics 365 Sales or Customer Service with Customer Insights as an Attach, we indeed have a Dataverse database capacity of 25 GB included on the tenant. The licensing guide explains that the default capacity is not cumulative; however, if the client simultaneously purchases their Sales / Service seats and Customer Insights, do they indeed have 25 GB and not 10 GB? The guide specifies that the first base license for a Dynamics 365 product includes its default capacity. The term 'first' is ambiguous; are we indeed looking at a maximum of 25 GB vs 10 GB = 25 GB? A reference from Microsoft would be appreciated if possible.
Cannot sync Country when connecting greenfields D365 BC <-> Dataverse (and onto D365 Sales)
Hey, sorry for the very newbie question, but everyone has to start somewhere! I get this cryptic incantation when trying to connect an essentially greenfields D365 BC (a small bit of progress through assisted setup) and a similarly vanilla D365 Sales instance, using the very latest updates on 2025 wave 2 (like I've applied this weeks coming update and any and all of the background app updates etc afaik is totally up-to-date at 28 Sep 2025 - maybe this is new and because we're living bleeding edge, may possibly be a heads up for someone out there, I really dont know. Cannot sync Country when connecting greenfields D365 BC <-> Dataverse (and onto D365 Sales) - Business Process Error: Choice member name to[o] long. dyn365bc_countryregionaddressformat_v2_0.City_x002B_County_x002B_Post_x0020_Code_x0020__x0028_no_x0020_commax0029 When performing the Dataverse connection and trying to enable all of the available fields, the above error message appears, and no matter what the dropdown is set to, the choice in the error doesn't seem to change, in PowerApps, in Choices, is no entries for 'dyn365bc_country' (but plenty of others), has been setting up for a day and a half half sync'ed, country not published nor trying, but seemingly leaving some of the rest in limbo. I asked CoPilot, ChatGPT et al and poked around without coming up with anything, didnt pass the google test, thought maybe an MS Call, but we try not to take the mickey and at least try first
