This is part 3 of the Azure AD series. This time it’s about licensing Azure AD. I have described the different license types in the second part of the series. Today it’s about buying the licenses.
As most people know, I like to make my life easy at work. That doesn’t mean I’m afraid of work, I just like to automate or simplify it where I can. I like to use PowerShell for this.
Another reason besides the convenience or lack of time why you should solve tasks through scripts is a consistent level of quality. Let’s face it, who doesn’t know this, even if there are checklists, you might forget one step when you get distracted.
Welcome to part 2 of the Azure-AD series. This part covers license types and features. We will also deal with the topic of license procurement and licensing possibilities. Due to the scope of functions, I cannot describe all functions contained in the individual licenses in this article. But I try to cover as much as possible and to provide links to further information.
Behind the feature “Automatic Virtual Machine Activation” is a function in Microsoft Windows Server 2012R2 Datacenter, Microsoft Windows Server 2016 Datacenter and Microsoft Windows Server 2019 Datacenter for Hyper-V, but it works only with the Datacenter Edition activated. With this feature, all supported Windows Server operating systems since Microsoft Windows Server 2012R2 can be automatically activated by the Hyper-V host. But only up to the own version, which means that a Windows Server 2012 R2 Datacenter Hyper-V cannot activate Windows Server 2016. The limitation of this feature to the Datacenter Edition is due to the unlimited Virtual Windows Server Guests covered by the Datacenter License. The advantage is that it is now easier to assign the license to the corresponding datacenter license during a software audit on the AVMA license key.