Get started with the Microsoft Intune App SDK

This guide will help you quickly enable your mobile app for app protection policies with Microsoft Intune. You may find it useful to first understand the benefits of the Intune App SDK, as explained in the Intune App SDK overview.

The Intune App SDK supports similar scenarios across iOS and Android, and is intended to create a consistent experience across the platforms for IT admins. But there are small differences in the support of certain features, because of platform limitations.

Register your store app with Microsoft

If your app is internal to your organization and will not be publicly available:

You do not need to register your app. For internal line-of-business apps, the IT administrator will deploy the app internally. Intune will detect that the app has been built with the SDK, and will let the IT administrator apply app protection policy to it. You can skip to the section Enable your iOS or Android app for app protection policy.

If your app will be released to a public app store, like the Apple App Store or Google Play:

You must first register your app with Microsoft Intune and agree to the registration terms. IT administrators can then apply app protection policy to the enlightened app, which will be listed as an Intune app partner.

Until registration has been finished and confirmed by the Microsoft Intune team, Intune administrators will not have the option to apply app protection policy to your app's deep link. Microsoft will also add your app to its Microsoft Intune Partners page. There, the app's icon will be displayed to show that it supports Intune app protection policies.

To begin the registration process, fill out the Microsoft Intune App Partner Questionnaire.

We will use the email addresses listed in your questionnaire response to reach out and continue the registration process. Additionally, we use your registration email address to contact you if we have any concerns.


All information collected in the questionnaire and through email correspondence with the Microsoft Intune team will honor the Microsoft Privacy Statement.

What to expect in the registration process:

  1. After you have submitted the questionnaire, we will contact you via your registration email address, to either confirm successful receipt or request additional information to finish the registration.

  2. After we receive all necessary information from you, we will send you the Microsoft Intune App Partner Agreement to sign. This agreement describes the terms that your company must accept before it becomes a Microsoft Intune app partner.

  3. You will be notified when your app is successfully registered with the Microsoft Intune service and when your app is featured on the Microsoft Intune partners site.

  4. Finally, your app's deep link will be added to the next monthly Intune Service update. For example, if the registration information is finished in July, the deep link will be supported in mid-August.

If your app's deep link changes in the future, you will need to re-register your app.


Please inform us if you update your app with a new version of the Intune App SDK.

Download the SDK files

The Intune App SDKs for native iOS and Android are hosted on a Microsoft GitHub account. These public repositories have the SDK files for native iOS and Android, respectively:

If your app is a Xamarin or Cordova app, please use these SDK variants:

It's a good idea to sign up for a GitHub account that you can use to fork and pull from our repositories. GitHub lets developers communicate with our product team, open issues and receive quick responses, view release notes, and provide feedback to Microsoft. For questions on the Intune App SDK GitHub, contact

Enable your iOS or Android app for app protection policy

You will need one of the following developer guides to help you integrate the Intune App SDK into your app:

Enable your iOS or Android app for app based conditional access

In addition to enabling your app for app protection policy, the following is required for your app to properly function with Azure ActiveDirectory (AAD) app based conditional access:

Configure Telemetry for your app

Microsoft Intune collects data on usage statistics for your app.

  • Intune App SDK for iOS: The SDK logs SDK telemetry data on usage events by default. This data is sent to Microsoft Intune.

    • If you choose not to send SDK telemetry data to Microsoft Intune from your app, you must disable telemetry transmission by setting the property MAMTelemetryDisabled to "YES" in the IntuneMAMSettings dictionary.
  • Intune App SDK for Android: Telemetry data is not logged through the SDK.

    iOS and Android line-of-business app version number is visible

Line-of-business app version numbers

Line-of-business apps in Intune now display the version number for iOS and Android apps. The number displays in the Azure portal in the app list and in the app overview blade. End users can see the app number in the Company Portal app and in the web portal.

Full version number

The full version number identifies a specific release of the app. The number appears as Version(Build). For example, 2.2(2.2.17560800)

The full version number has two components:

  • Version
    The version number is the human-readable release number of the app. This is used by end users to identify different releases of the app.

  • Build Number
    The build number is an internal number that can be used in app detection and to programmatically manage the app. The build number refers to an iteration of the app that references changes in the code.

Version and build number in Android and iOS

Android and iOS both use version and build numbers in reference to apps. However, both operating systems have meanings that are OS-specific. The following table explains how these terms are related.

When you are developing a line-of-business application for use in Intune, remember to use both the version and the build number. Intune App management features rely on a meaningful CFBundleVersion (for iOS) and PackageVersionCode (for Android). These numbers are included in the app manifest.

Intune iOS Android Description
Version number CFBundleShortVersionString PackageVersionName This number indicates a specific release of the app for end users.
Build number CFBundleVersion PackageVersionCode This number is used to indicate an iteration in the app code.


  • CFBundleShortVersionString
    Specifies the release version number of the bundle. This number identifies a released version of the app. The number is used by end users to reference the app.‚Äč
    • CFBundleVersion
      The build version of the bundle, which identifies an iteration of the bundle. The number may be identify a release or unreleased bundle. The number is used for app detection.


  • PackageVersionName
    The version number shown to users. This attribute can be set as a raw string or as a reference to a string resource. The string has no other purpose than to be displayed to users.
  • PackageVersionCode
    An internal version number. This number is used only to determine whether one version is more recent than another, with higher numbers indicating more recent versions. This is not the version

Next steps after integration

Test your app

After you finish the necessary steps to integrate your iOS or Android app with the Intune App SDK, you will need to ensure that all the app protection policies are enabled and functioning for the user and the IT admin. To test your integrated app, you will need the following:

  • Microsoft Intune test account: To test your Intune-enlightened app against Intune app protection features, you will need a Microsoft Intune account.

    • If you are an ISV enabling your iOS or Android store apps for Intune app protection policy, you will receive a promo code after you finish the registration with Microsoft Intune, as outlined in the registration step. The promo code will let you sign up for a Microsoft Intune trial for one year of extended use.

    • If you are developing a line-of-business app that will not be shipped to the store, you are expected to have access to Microsoft Intune through your organization. You can also sign up for a one-month free trial in Microsoft Intune.

  • Intune app protection policies: To test your app against all the Intune app protection policies, you should know what the expected behavior is for each policy setting. See the descriptions for iOS app protection policies and Android app protection policies.

  • Troubleshoot: If you run into any issues while manually testing your app's user experience, check out the Troubleshooting MAM. This article offers help for common issues, dialogs, and error messages that may be experienced in Intune-enlightened apps.

Badge your app (optional)

After validating that Intune app protection policies work in your app, you can badge your app icon with the Intune app protection logo.

This badge indicates to IT administrators, end-users, and potential Intune customers that your app works with Intune app protection policies. It encourages the usage and adoption of your app by Intune customers.

The badge is a briefcase icon and can be seen in the samples below:

Badge example 1 Badge example 2

What you'll need to badge your app:

  • An image manipulation application that can read .eps files, or an Adobe application that can read .ai files.

  • You can find the Intune app badge assets and guidelines on the Microsoft Intune GitHub.