Dynamics 365 has been officially available since 1 November 2016. But what has all changed and, above all, what does this mean for existing customers? We…
Dynamics 365 has been officially available since 1 November 2016. But what has all changed and, above all, what does this mean for existing customers? We provide answers to questions and explain what Microsoft's new product strategies look like. Interplay of CRM and ERP For the first time, the two products, CRM and ERP, can be licensed together. There is the option of using only a single „app“ or else acquiring several functionalities via licence packages. Axapta, AX, Dynamics AX, AX7, the new AX – Dynamics 365 Operations Enterprise Edition – that is the official name of the ERP functionality from Dynamics 365. Licensing options Operations (as shown in the graphic above) can be acquired either on its own or together with the CRM modules. At present, Dynamics 365 is available exclusively in the Public Cloud. This means that it is SaaS (Software as a Service). Translated: with the licence you acquire the right to use the software without having to worry about the hardware/installation. Microsoft guarantees the high availability, data backup and performance of the environments. Access is via the browser and is therefore also possible independently of location. There are now only two user tiers in the ERP: Enterprise or Team users. Until now there were four tiers (Enterprise, Functional, Task, Self Serve). This has simplified the licensing model – until now it was always only possible with great effort to allocate the users to the various models. The so-called Team Members (or light users) have the following options available: time and expense entry, maintaining personal information, entering internal purchase requisitions, creating/changing quality inspection and service orders, approval of time registrations, expenses and invoices. Data storage / synchronisation of various apps Each app has its own database and there is no automatic synchronisation with other modules. However, in order to be able to map cross-app business processes and entities, every app is based on