Intune Apple VPP Tokens Test

Location tokens are also known as Volume Purchase Program (VPP) tokens. These tokens are used to assign and manage licenses purchased using Apple Business Manager. Content Managers can purchase and associate licenses with location tokens they have permissions to in Apple Business Manager. These location tokens are then downloaded from Apple Business Manager and uploaded in Microsoft Intune. Microsoft Intune supports uploading multiple location tokens per tenant. Each token is valid for one year.

Microsoft Intune helps you manage apps purchased through Volume Purchase Program by:

• Synchronizing location tokens that are download from Apple Business Manager

• Tracking how well the licenses are used for purchased apps

• Helping you to install apps up to the number of available licenses

• Tracking resource utilization by purchased apps

• Updating the purchased apps

In organizations where multiple iOS/iPad and macOS apps are being used, multiple location tokens may be uploaded to Intune. Using these tokens, Intune can streamline the processes of purchasing, deploying, managing licenses, tracking resource usage, synchronizing and updating the purchased apps. When a token becomes invalid, expires or encounters errors, Intune will not be able to manage licenses and resource utilization of the purchased application that uses the particular token. This may lead to over/under utilization of licenses/resources in the environment. If the tokens are not renewed or replaced before they expire, it will create disruptions in app deployment and management. This in turn will adversely impact the availability of business-critical applications and lead to poor user experience. To avoid such inconveniences, administrators should continuously monitor the token uploaded to Intune. This Intune Apple VPP Tokens test can help administrators .

This test auto-discovers the location tokens imported to Intune, and for each token, reports the current and expiration status. These information helps the administrators to instantly identify the tokens that are in error/critical/invalid/expired state and quickly decide on whether to renew or replace the token. In addition, this test also reveals whether the synchronization triggered for a token was successful or failed. This measure alerts administrators to sync failures (if any) so that they can initiate corrective actions to synchronize the app names, metadata and license information of the purchased apps in Intune for a token. Additionally, this test keeps close watch on how many days are still left for each token to be expired and proactively alerts administrators to renew the token before it expires.

Target of the Test: Microsoft Azure Intune

Agent deploying the test: A remote agent

Output of the test: One set of results for each VPP token uploaded to the Azure Intune

Configurable parameters for the test

Parameters	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Tenant ID	Specify the Directory ID of the Azure AD tenant to which the target subscription belongs. To know how to determine the Directory ID, refer to Configuring the eG Agent to Monitor Microsoft Azure Intune Using Intune REST API.
Client ID, Client Password, and Confirm Password	To connect to the target subscription, the eG agent requires an Access token in the form of an Application ID and the client secret value. For this purpose, you should register a new application with the Azure AD tenant. To know how to create such an application and determine its Application ID and client secret, refer to Configuring the eG Agent to Monitor Microsoft Azure Intune Using Intune REST API. Specify the Application ID of the created Application in the Client ID text box and the client secret value in the Client Password text box. Confirm the Client Password by retyping it in the Confirm Password text box.
ProxyHost and ProxyPort	In some environments, all communication with the Azure cloud be routed through a proxy server. In such environments, you should make sure that the eG agent connects to the cloud via the proxy server and collects metrics. To enable metrics collection via a proxy, specify the IP address of the proxy server and the port at which the server listens against the ProxyHost and ProxyPort parameters. By default, these parameters are set to none, indicating that the eG agent is not configured to communicate via a proxy, by default.
ProxyUsername, ProxyPassword, Confirm Password	If the proxy server requires authentication, then, specify a valid proxy user name and password in the Proxy Username and Proxy Password parameters, respectively. Then, confirm the password by retyping it in the Confirm Password text box. If no proxy server is used, or if the proxy server used does not require authentication, then the default setting - none - of these parameters, need not be changed.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements reported by the test

Measurement	Description	Measurement Unit	Interpretation
Token expiration status	Indicates the current expiration status of this token.		The values reported by this measure and its numeric equivalents are mentioned in the table below: Measure Value Numeric Value Good 0 Warning 1 Error 2 Critical 3 Note: By default, this measure reports the Measure Values listed in the table above to indicate the expiration state of this token. The graph of this measure however, is represented using the numeric equivalents only - 0 to 3. The detailed diagnosis of this measure if enabled, lists the name of organization to which the token belongs to, Apple Identifier of the token, the timestamp at which the last sync was triggered and the timestamp at which the token was modified.
Token state	Indicates the current status of this token.		The values reported by this measure and its numeric equivalents are mentioned in the table below: Measure Value Numeric Value Default state 0 Token is valid 1 Token is managed by another MDM Service 2 Token is invalid 3 Token is expired 4 Note: By default, this measure reports the Measure Values listed in the table above to indicate the current state of this token. The graph of this measure however, is represented using the numeric equivalents only - 0 to 4. The detailed diagnosis of this measure if enabled, lists the URL that is used to hit the web app, the service plan, the web space of the web app and the tier of the web app.
Days until expiration	Indicates the number of days by which the license of this token will expire	Number	A high value is desired for this measure. A very low value for this measure indicates that the license is nearing expiry. You may have to request for a license extension if you want to continue using the token.
Last sync status	Indicates the status of sync operation triggered for this token during the last measurement period.		The values reported by this measure and its numeric equivalents are mentioned in the table below: Measure Value Numeric Value Default status 0 Last Sync in progress 1 Last Sync completed successfully 2 Last Sync failed 3 Note: By default, this measure reports the Measure Values listed in the table above to indicate sync status of each token. The graph of this measure however, is represented using the numeric equivalents only - 0 or 3.
Account type	Indicates the account type to which this token is associated with.		The values reported by this measure and its numeric equivalents are mentioned in the table below: Measure Value Numeric Value Business 0 Education 1 Note: By default, this measure reports the Measure Values listed in the table above to indicate the account type to which each token is associated with. The graph of this measure however, is represented using the numeric equivalents only - 0 or 1.