Voted Best Answer
Jun 15, 2017 - 10:24 PM
Azure is one consideration. With an MPSA, since the removal of Pay As You Go pricing, you will also require a separate agreement such as CSP (Cloud Solution Provider) or SCE (Server & Cloud Enrollment). On an EA, Azure is paid for via Monetary Commitment - and it has the full range of products & plans available.
The ability to " True Up " on an EA - this can make it easier to manage & budget licensing for new staff.
The EA offers more scope for negotiations on terms/exceptions etc. than any other agreement.
Generally, an EA works very well for centralised and standardised purchasing, while the MPSA lends itself to de-centralised organisations/situations through the ability to have separate Purchasing Accounts for different entities/departments and also multiple partners on the one agreement.
As David says, having both an EA and an MPSA is very common. Often, organsations will purchase Windows/Office/CAL Suits/Online Services via the EA and then Server OS and applications (SQL, Biztalk) etc. via the MPSA.
It is possible to drop SA at the renewal of an EA and you retain the perpetual rights (as long as it is not an Enterprise Agreement Subscription).
The MPSA has a requirement for a certain number of " points " to be purchased each year. If this isn't met, it can lead to an increase in pricing or the inability to purchase further licenses until certain conditions are met.
Ultimately, the answer depends on the organisation. What your plans are around desktop standardisation, viewpoint towards Software Assurance on the desktop and in the datacentre, plans and timescales for Cloud migration, Azure usage, license purchase quantities and more.
Let me know if you have further questions.