If you're saying your org has 400 employees, then it might breakdown like this:Ģ90 don't need Dynamics at all (think shop floor production workers) It's best to plan for this to be higher in years 1-2, then you can start scaling it back in some areas, like eliminating extra test environments and using locally hosted DEV environments. This is a category you can actively manage. Much of the secondary category can be considered "Azure usage". Secondary options - increased performance in Production, Azure usage, cloud hosted DEV environments, additional test environments, data warehousing, advanced analytics Types of users - Finance, SCM, Team Members, those who don't need Dynamics at all It really depends on two factors: which type of users you have and what secondary pricing options you need.
0 kommentar(er)
