Microsoft Dynamics 365 Formerly Microsoft Dynamics CRM vs ServiceNow IT Service Management

• Some useful out-of-the-box features, like mass uploads of Leads from trade shows or when qualifying a Lead, CRM automatically creates the Opportunity, Contact, and Account for you, etc.
• Really powerful customizations through the user interface to improve user experience. Things like Business Rules, for example, if Field A = 1, then Field B = 2 and Field C = 2, if Field A = 2, then Field B and Field C don't apply, so automatically hide them.
• Or other functionality that improves user experience, like Business Process Flows. These walk users step by step through our business process, helping them know when certain actions should take place, and at what point other data is now required. We've used this extensively with our Lead to Opportunity to Quote to Order process, helping users understand the business process each step of the way.
• Customizations built on top of the platform now called model-driven PowerApps. You can have connections to "typical" data, like Accounts, Contacts, or Opportunities, for example, but then connect that data to custom entities, records that only apply to your specific business. This is all done through the user interface and allows you to customize and automate specific line-of-business applications for your specific needs.
• Behind the scenes, D365 CE is built on SQL. So the data conforms to industry standards and makes it much easier to interact with. Your developers and IT team will thank you.

Read full review

• When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
• I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
• Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
• To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.

Read full review

• Microsoft Dynamics 365 storage & license cost can prohibit some large deployments or even cost-sensitive small projects from using the platform (although I'm certain most deployments would realize a positive ROI if implemented correctly with process automation).
• The cost and licensing document for Dynamics 365 is 61 pages and will take a rocket scientist to understand it. It's better to just have your Microsoft help estimate the cost if they are willing to help you that.
• The documentation on how to first fully understand the Out of the Box default solution and settings is lacking or even non-existing. This has the potential to derail Dynamic 365 launches and implementations from the gitgo. Want to use an out of the box entity?.. well it's probably related to 5 other entities that require configuration and full understanding of it to successful implement. And you ask where is the laymen guide or instructions?... User groups and forums. In Summary, Microsoft can up its game in deployment training and supporting documentation.
• Microsoft needs to incentivize more external platforms to build app connectors for easy integration, such as ZenDesk, Slack, Tableau, etc. Even the current connector apps such as Salesforce, MailChimp, Docusign are useless or don't work at all.
• Several limitations inhibit successful Dynamics 365 deployments such as: limited number of Rollup field calculations (summarizing fields on child/related records), limited number rows that can exported to Excel via advanced find, Dynamics 365 files, log and database storage size limit is extremely small and will always require purchasing additional storage (for Online deployments).
• New user buy-in or acceptance or system platform changes can be difficult if a solid change management plan isn't enacted.
• Don't expect much help from Microsoft on implementation or solutions unless it's a technical flaw with the platform. Microsoft relies on their MVP partner network to consult for implementations at a hefty cost. Hiring a knowledgeable and savvy Dynamics 365 System Administrator can reduce the need for consultant support; of course, this is dependant upon many many variables.

Read full review

• It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
• The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
• The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!

Read full review

• For those without a centralized, all in one solution for major HR, Finance and other departments, Microsoft Dynamics 365 has vastly improved employee time utilization and profit.
• Migrating clients from on-premise to the cloud has reaped benefits including better security, no unscheduled downtime and frequent updates to functionality.
• Those transferring from cheaper solutions have lost money in the aim to be better integrated with other Microsoft products and AI they don't really utilize.

Read full review

• ServiceNow has helped majorly in removing the in-house development effort for the ticketing tool and now we can focus on using the ticketing system and rest is managed by service now
• ServiceNow have had a great impact in Incident reporting and management through its subscription models and a powerful dashboard
• With machine learning feature available within service now, we are able to analyze the incident patterns and root cause and reduce the production outages

Read full review