I would say that, if they are in the market for a new/different CRM, this is probably a good place to start. If they are looking to use MS Dynamics in addition to their already existing CRM, they might want to opt for a trial period first, to see if it has what they are looking for.
The largest issue that we have found with MS Dynamics is the integration between platforms. Microsoft offers an API which has some level of usage, but as we don't use exclusively MS products across our whole CRM system, we really like it when the software vendor offers a robust API, allowing us to pull any and all data that we need into custom reporting systems and custom mobile field portals for our employees who operate offsite. The API offered in Dynamics is just not giving us enough of the information that we need, and we are finding it difficult generating the reports that we so desperately need in this industry to gain an upper hand.
We moved into using MS Dynamics mostly because a C-level employee that was hired recently raved about its performance and payoff. We don't use it as a catch-all CRM because we have custom-made platforms that we use, and draw information from other applications to help our team meet their goals with exactly the tools they need. We have seen some integration improvements since rolling them into our platform, mostly due to the fact that a large decision-making employee base was recently hired who have a background in utilizing MS Dynamics.
Seeing as it is made by the powerhouse Microsoft, it offers a lot of support, which is key for us. Downtime is not an option for us, and Microsoft has been great by offering very customized support for us.
Again, coming back to the API support, we have found it lacking. We have received notice that MS is planning on increasing support and capability of the API, so that is a welcome change for us.