Last night, the Intune update enabling support for Apple’s Apple Volume Purchase Program for Business (VPP) went live (on my tenant :)). The VPP program itself is meant to reduce the overhead of having to track multiple purchased copies of apps in the Enterprise.

Intune works with VPP by importing information from the app store, tracking how many of the licenses you have used, and preventing you from installing more copies of the app than you own. Before continuing with this article, we assuming you have already setup an Apple VPP account and have confirmed your organization information and DUNS number.

Per the article here, you should review the following before you start:

  • Each organization can have only one VPP account and token.
  • Once you associate an Apple VPP account to Intune, you cannot subsequently associate a different account. For this reason, it’s very important that more than one person has the details of the account you use.
  • If you have previously used a VPP token with a different product, you must generate a new one to use with Intune.
  • Each token is valid for one year.
  • By default, Intune syncs with the Apple VPP service twice a day. You can, however, initiate a manual sync at any time.
  • After you have imported the VPP token in Intune do not import the same token into any other device management solution. Doing so might result in the loss of license assignment and user records.
  • Before you start to use iOS VPP with Intune, remove any existing VPP user accounts created with other MDM vendors. Intune will not synchronize those user accounts into Intune as a security measure. Intune will only synchromize data from the Apple VPP service that was created by Intune.

First, let’s navigate to the Intune Administration console and choose Admin > iOS and Mac OS X > Volume Purchase Program.

Click the link to sign into the VPP Program

Let’s go ahead and search for the app we want, in this case we’ll use everyone’s favorite game Angry Birds HD 🙂

Then we’ll choose how many copies to purchase and choose Managed Distribution for deployment with MDM.

Shortly, you should get an e-mail that looks like this

If you go back to the Apple VPP page, you should now see your order

Under your account name dropdown, choose Account Summary

Select Download Token

Save the token

Back in Intune, let’s choose to Upload the token

Enter your token and the Apple ID it’s associated with

We can now see our VPP information is loaded in and healthy

Next, let’s navigate to the Apps pane, and you’ll see a new tab for VPP apps, with our Angry Birds HD app pre-populated.

You can right-click to deploy the app like any other Intune application.

Per the guidelines above, when deploying a VPP app:

  • When you deploy a volume purchased app, one license you purchased is used by each user that installs the app. To reclaim the license, change the deployment action to Uninstall.
  • When you deploy the app, new users with eligible devices are sent an invitation to join the Apple Volume Purchase Program. To continue, they must accept the terms of use.

NOTE:

Look at the VPP Terms Status column to see the acceptance status for each user to whom the app was deployed.

If there are no further licenses available, the deployment will fail.

Now, let’s go to our iPad and check it out!

First, we manually refreshed compliance to force the policy down.

You can see that immediately we get a prompt for App and Book Assignment

You’ll see that we get prompted to accept the terms.

Then shortly after, we’ll see a prompt for the app

Installing!

Let’s play some Angry Birds HD!

Now if we go back to the Intune console, you should see a license marked as in use.

It appears that it takes a bit of time for this to populate, even after a policy refresh, so we’ll check back later.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>