You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close

02: If I have both Azure joined and Hybrid Azure AD joined machines, how do I count the exact number of licenses I need?

First of all, we here at PolicyPak don’t want to charge you twice. If a machine is joined to On-Prem AD and also joined to Azure AD (called Hybrid Azure AD joined)… then you should only have to pay for the machine one time. Here’s Microsoft’s diagram below (borrowed from https://docs.microsoft.com/en-us/azure/active-directory/devices/concept-azure-ad-join-hybrid ).

In this case, if you had exactly ONE machine like this you would need to:

  • PAY for one license (remember, you only need to pay once.) But…
  • ENGAGE both PolicyPak licensing mechanisms for this computer: PolicyPak Group Policy and PolicyPak MDM.

We recommend you don’t deliver the same PolicyPak settings from BOTH Group Policy or MDM. But you might want to enable the ability to get those licenses from both sources, then transition away from Group Policy to MDM over time.

Knowing you’ll have some machines:

  • Joined to on-prem AD & GPO (but not in Azure)
  • Joined to Azure AD (but not on-prem AD) and
  • Hybrid Azure AD Joined (dual enrolled to both)

How do you dial in exactly how many computers to license? We’ll go over this same math again at the end, but here’s the gist. Let’s pretend you had the following numbers (which we will explain more in this document below):

  • Part 1 (On-Prem AD & GPO machines): 1000.
  • Part 2 (Azure AD joined only): 250
  • Part 3 (Hybrid AD joined): 150

To correctly pay for each computer ONE time you would pay for:

  • Azure AD joined only: 250.
  • Hybrid AD joined: 150
  • AD & GPO machines : 1000
  • SUBTRACT the number of Hybrid AD joined: MINUS 150

Final number for purchase.. where each machine is licensed ONCE:

  • 250 +
  • 150 +
  • 1000 MINUS
  • 150

Grand total: 1,250 computers

There is no “easy button” for this, but it is a straightforward procedure.

Step 1: Counting your on-prem AD & GPO machines

Typically, you do this with the PolicyPak on-prem licensing tool (preferred), or if you need to, you can use PowerShell. Some example Powershell commands to count on-prem machines can be found at this KB: https://kb.policypak.com/kb/article/246-my-organization-doesnt-permit-me-to-run-the-lt-policypak-licensing-tool-or-provide-the-xml-information-it-produces-what-are-my-other-options/

Preparing for Steps 2 and 3: Before we count the Azure only machines and before we count the Hybrid Azure AD joined machines

In Azure you can use Devices | All Devices then look at the Join Type. You should see four possible fields:

  • Azure AD registered: This is not required for a PolicyPak license, as this is NOT Azure or MDM enrolled.
  • Azure AD joined: This means the machine is joined directly to Azure AD and is not Hybrid (that is, it is NOT also joined to on-prem AD.)
  • Hybrid Azure AD Joined: This means the machine is joined BOTH to Azure AD and to on-prem AD.
  • Blank: Unknown.

The problem is that you cannot count each type with this interface unless you have a mere handful of machines. Instead you need to use Powershell and have it do the counting for you.

Next: Using PowerShell to connect to Azure AD

Start out by installing the Azure AD module. Details are here: https://docs.microsoft.com/en-us/powershell/azure/install-az-ps?view=azps-4.4.0

Here’s a copy of the command:
if ($PSVersionTable.PSEdition -eq 'Desktop' -and (Get-Module -Name AzureRM -ListAvailable)) {
   Write-Warning -Message ('Az module not installed. Having both the AzureRM and ' + 'Az modules installed at the same time is not supported.')
} else {
   Install-Module -Name Az -AllowClobber -Scope CurrentUser
}

Here’s the result.

Start out with the Connect-AZAccount cmdlet (not shown). You will get prompted for credientals the first time.

The command should finish and return you with a result like this.

Then use the connect-azuread command and provide credentials again, for a second time.

Results of connection are then seen here.

You can then list all Windows 10 devices with the following command.
Get-AzureADDevice -all $true | select displayname, DeviceOSType, DeviceTrustType

Step 2: Count your Joined to Azure AD only (but not on-prem domain joined machines)

To count Azure AD joined machines, run the first command.

Get-AzureADDevice -All $true | Where-Object {$_.DeviceTrustType -eq "AzureAd"} | measure

Step 3: Count Hybrid Azure AD joined machines (those joined to on-prem AD and also Azure AD) 

To count your Hybrid Azure AD joined machines, run this command.

Get-AzureADDevice -All $true | Where-Object {$_.DeviceTrustType -eq "ServerAd"} | measure

Results of your counting:

Results examples are seen here.

A final example with Math

Let’s pretend you got the following numbers:

  • Part 1 (On-Prem AD & GPO machines): 1000.
  • Part 2 (Azure AD joined only): 250
  • Part 3 (Hybrid AD joined): 150

To correctly pay for each computer ONE time you would pay for:

  • Azure AD joined only: 250.
  • Hybrid AD joined: 150
  • AD & GPO machines : 1000
  • SUBTRACT the number of Hybrid AD joined: MINUS 150

Final number for purchase.. where each machine is licensed ONCE:

  • 250 +
  • 150 +
  • 1000 MINUS
  • 150

Grand total: 1,250 computers

  • 941
  • 07-Mar-2021
  • 3161 Views