Microsoft release a special June 2017 Product Terms Addendum to take account of the name changes coming to the Dynamics 365 products on 1 July, 2017.
In summary, Operations becomes the Dynamics 365 Unified Operations Plan, Plan 1 becomes the Dynamics 365 Customer Engagement Plan, and Plan 2 becomes the Dynamics 365 Plan.
Download this addendum here: http://bit.ly/2rRqysz.
There are VDA per User Add-on SLs added to the February 2017 Product Terms document. These are designed to be added on to VDA Device SLs and follow the same rules as the Windows 10 Enterprise E3 and E5 Add-ons. See pages 38 and 42-43 of this document.
The February 2017 Online Services Terms document adds some clarity around Dynamics 365 licensing. Firstly, external users don’t need an SL if they’re using the Operations service, but if they’re using Dynamics 365 clients to access the other services then they do. And secondly, it’s confirmed that if you’re licensed for Dynamics 365 Business edition then you don’t have the right to install and use Dynamics 365 on-premises server software. See page 3.
The January 2017 Product Terms document alerts us to some product name changes:Â Office 365 Advanced eDiscovery becomes Office 365 Advanced Compliance, and Operations Management Suite changes to Operations Management and Security – it’s all on page 5.
The Software Assurance section in the August 2016 Product Terms document is updated.
The main change is that the rules governing SA benefits for the MPSA have been moved into the Product Terms from the MPSA Licensing Manual.
Previously, Training Vouchers could not be converted to Planning Services Days within the MPSA but that restriction is now lifted (page 74), although it’s still not possible to convert 24×7 Problem Resolution Support Incidents to Premier Problem Resolution Support hours in this agreement (page 78).
There’s an updated (June 2016) “Licensing Microsoft server products for use in virtual environments” Volume Licensing Brief.
It’s updated for Exchange Server 2016 (no changes to the licensing), SQL Server 2016 (Business Intelligence edition removed, requirement to assign a minimum of 4 licences per processor rather than using the Core Factor table) and it references the Product Terms document rather than the Product List and Product Use Rights documents.
Get this updated brief here in the Application Servers section: http://bit.ly/MSLicensingGuides.
There are a couple of additions to the April 2016 Product Terms document: some add-ons for Dynamics AX and some USLs for Cloud App Security. Read on for the detail!
Dynamics AX – that’s Dynamics built on and for Azure – was made available in March 2016 and now we’ve got some extra licensing options. If you’re a Dynamics AX 2012 R3 on-premises customer and you have existing licences with active Software Assurance then you can now purchase For SA USLs to add on access to the cloud service. There’s a table on page 55 which lists the qualifying licences and the eligible For SA USLs you can purchase.
Cloud App Security, based on Microsoft’s recent acquisition of Adallom, helps IT and security teams gain deeper visibility and enhanced protection for cloud applications. How’s it licensed? Page 53 confirms it’s with a User Subscription Licence, and if you want more information and an intro to how it works, then head over to the Microsoft Cyber Trust Blog: http://bit.ly/23H7Fqq.
It’s December 1st and Office 365 E5 is added to the December 2015 Product Terms as expected. Page 58 tells us that there will be a full USL, an Add-on USL, and a From SA USL, with availability through the different Volume Licensing programs matching that of its best buddy E3.
If you’re not sure what’s in this brand new suite, then head over to the December 2015 Online Services Terms document where the table on page 26 has been updated to show the various components.
Many of these components are new (Office 365 Delve Analytics for example), and these are added to the Product Terms as standalone licences too.
From November 1st there are Bridge CALs available for Open Value customers.
When do you need a Bridge CAL? Well, if you’ve got an enterprise wide commitment to Office and a CAL Suite but want to transition to either EMS or Office 365 then you need a way to continue to pay for the on-premises components that haven’t transitioned – and that’s the Bridge CAL. They’ve been available in the Enterprise Agreement for a few years and now Open Value customers are able to buy them too.
See page 14 of the November 2015 Product Terms document.
EA customers transitioning from Office and a CAL Suite to Office 365 or the Enterprise Mobility Suite need a Bridge CAL, and from 1 August 2015 the Core and Enterprise CAL Suite Bridges are only available as User Subscription Licences.
See pages 14/15 of the August 2015 Product Terms document.
If you’re new to Microsoft licensing then you may find this just-released introductory guide from Microsoft useful. It goes through some of the licensing basics (what is a licence, what is SA etc) and introduces the new Product Terms document. Then you meet Wendy, the Director of IT for Trey Research, and look at the projects she’s working on and see what licences she’s going to need. It’s a different way of introducing licensing and worth a look through: http://bit.ly/1SJDo4F.