M365 wrong licensing impacts performance

Tenant level security & compliance features may have performance issues when licensed wrong!

Good example is the use of Office 365 ATP e.g. detonation chamber for attachements. Behind this feature there are VMs spinned up for processing the attachments. The number of licensed users control in the background the ammount of VMs used for this. Some customers belief its a good Idea to have 1 x E5 license and then they are able to use the features as they are tenant wide activated then.

But they fail in:

1. doing a license violation

2. having not enough ressources allocated to do the work. Physical result is a strongly delayed delivery of mails with attachments or with dynamic delivery option enabled also a strong delay in delivering the final attachment. This is caused by a tremendous queue of attachments waiting to be checked as there are not enough ressources allocated in the background.

For this and more impacts please refer also to this article. It also covers the topic how to limit the services correctly to the targeted users. https://docs.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance

Windows 10 Pro Licensing Logic (OEM to VL)

From time to time the Windows 10 Pro vs. Enterprise discussion comes back. Just to clarify from a security point of view and also in relation's of limitations the Enterprise edition is still the best and recommended way to go. It offers a tremendous value in terms of security and manageability.

But we still have customers were the financial pain is so huge that we need to cut very important features as well just to fulfill their serious budget limits. 

Caution!  Just one word as advice. DO NOT TRY TO MAP WINDOWS7 TO WINDOWS 10 !!!

Its the same as you want to use a Ferrari in the same way as you did with your VW Golf before. Please rethink your potential modern workplace even only with PRO instead of Enterprise. It does not make sense to do the stuff the old way as you fear the new way or you are not willing to ask what could be the new way for you to simplify things.

If you had to go with Windows 10 Pro (knowing all current and future potential limitations) then you can go with the PRO license coming on your OEM device. There is still the rule that having 1 Windows 10 Pro VL license bought through commercial licensing brings you the right to use the VLSC and download your Windows 10 Pro Image ISO you can use for further deployment.

Please checkout here:
https://download.microsoft.com/download/3/d/4/3d42bdc2-6725-4b29-b75a-a5b04179958b/reimaging.pdf

You find here the sentence:

Using Commercial Licensing media to reimage.
Commercial Licensing Windows Desktop operating system media may be used to reimage devices if all devices being reimaged are licensed for the edition and version of Windows being reimaged onto them. (Note: Each device being reimaged does not need to be licensed under Commercial Licensing if they are properly licensed for the edition and version being reimaged onto them.)

(Which is given when you have an OEM Windows 10 Pro you can reimage with Windows 10 Pro but only in the given edition and version. So Windows 10 version and Pro edition.) I asked a few years ago MS license Q and that's what they explained to me as well.

Another Reference
https://blogs.technet.microsoft.com/uktechnet/2015/07/13/windows-10-licensing-logic/

And please be aware. You can not stop the update train! Which is from security point of view the only valid way. From a management point of view rethink things. Windows 10 is not a project. Its a continuous process!

Windows 10 Licensing Logic - Long Term Service Branch

Licensing is for some a nightmare and for others fun. I am none of either parties. Anyway its part of my job to explain also these aspects. Recently I found out there is some curiosity around the LTSB licensing topic and I did my own research on it.
 
Its quite tricky to get it licensed in not so common scenarios.
 
When you are an enterprise with your own Microsoft volume licensing contract then everything is fine. You can go for all of the different so called branches.
 
Big questionmark for any ISV / OEM is how to deal with the "evergreen" politics of Microsoft. In general this "being always up to date" is a good thing for a couple reasons:

1. You never need to pay for Windows again on the same machine and you'll always have the latest version
2. No more wipe and reload upgrades
3. Software vendors and developers can almost guarantee that 90% of Windows users will have the same build

The third point there should make you smile if your PC has ever crashed or you've needed to phone support because an application isn't working. There are so many combinations of OS, patches, drivers, runtime files and versions around that reliability and consistency are devilishly hard to achieve. Applications and peripherals should work far better if the manufacturers and developers can work to a stable and single platform.

(For nice side kick checkout this blog entry as well http://www.ms-labrats.de/2015/11/windows-10-reducing-disk-footprint.html)

On the other side you may face some supporting issues with your special ISV software you want to avoid (e.g. may be you are not able to make all the updates just in time to make sure your customer can use your cashier systems. Also you want to avoid possibly interuptive things like Cortana. I personally dont believe that this may happen but other still does.)
 
It become more tricky when you are a service provider (e.g. cashier systems) and you do not want to tell the customer they can only get the LTSB with an enterprise version where you need also an volume licensing agreement and software assurance.
 
Also the question may arise the difference between:
Windows 10 IoT Enterprise vs. Windows 10 Long Term Servicing Branch.
Technically there is NO difference. When you check out features available in LTSB and in IoT Enterprise its the same. There is even no dedicated Windows 10 IoT Enterprise image available (as of today - things may change over time). Its in fact the LTSB branch. Just a different "marketing vehicle" in the different market spaces.
 
Means for corporate standard users the Windows 10 versions are:
 

• Windows 10 Pro (Limited feature set with basic security like Bitlocker)
• Windows 10 Enterprise (Full feature set especially also around security for enterprises)
• Windows 10 Enterprise LTSB (a few less features as Enterprise like no Cortana, no Edge and no 1st party MS Universal Apps, Updates only by WSUS)

 
and in the IoT-Space (Internet of Things):
 

• Windows 10 IoT Enterprise (Full feature set of Windows 10 LTSB as it is identical)
• Windows 10 IoT Mobile Enterprise (Enterprise managable version of Windows 10 for Phones with additional support for PoS devices)
• Windows 10 IoT Core (Focused for devices without screen. Like Arduino2 PCs. More focused on sensor functionality or headless functions)

When you are service provider (ISV/OEM) you are more looking for a easy solution to provide the customer the needed license.
 
There you have a couple options.
 
As ISV - NOPE there is currently no way to license an operating system in the ISV Royalty Program. So you have to look for either getting it throught the OEM channel. Ask your OEM hardware provider for it.
 
As OEM you can get the licenses through Microsofts Embedded Distribution (these are not thre regular OEM distributors. You have to look for Embedded Distributors like Arrow, Avenet or Elbacom (no preference just alphabetical order))


The table shows you as service provider one option called "Windows 10 v2015 Enterprise Upgrade" (or in 2-3 years another year version). (These license terms were valid while this blog was published. This may change over time!)

With this version you are eligable to use the current and past LTSBs (downgrade rights).
Without Software Assurance you have only the first 5 years support (only security updates)
With Software Assurance your have support for additional 5 years (only security updates as LTSB gets by purpose no new features).

This means when you buy e.g. the Windows 10 v2015 Enterprise Upgrade (without SA) you are eligable for one static version (in this case v2015 with support until Oktober 2020). To get another 5 years of support you have to buy additionally software assurance at the beginning. This also allows you to use future LTSB versions.

If you plan to go for regular distribution like EA/MPLS or Open (the customer had already a device) then you need for Enterprise always an underlying qualifying operating system (i.e. windows 10 pro, windows 8.1 pro, windows embedded 8.1 industry etc.)

If you talk to your Embedded Distributors you can get the licensing in the way you would do with OEM licenses. They provide you the OPK Kit and this form also allows you to preactivate your license and skip the OOB.

To get the full story see also here:
http://blogs.technet.com/b/uktechnet/archive/2015/07/13/windows-10-licensing-logic.aspx
(Thanks to Harry Eagles and David Cattanach)

UPDATE 2018-3-28
There was a change in licensing to mention. Unfortunately I did not found a reference on MS Websites for this. In my country Germany there are two vendors offering a way to buy Windows embedded licensing for your production machines. These are Arrow and Avnet. I just added a good performance based explanation for the new LTSB licensing model when you need a couple single licenses outside of an EA or MPSA agreement. http://www.msembedded.biz/en/embedded-software/windows-10-iot-enterprise-2016/