Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.microsoft.com/en-us/mem/intune/developer/app-sdk-get-started below:

Get started with the Microsoft Intune App SDK

This guide will help you quickly enable your mobile app to support 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 differences and limitations.

The following diagram provides the process flow for the Intune App SDK for iOS and the Intune App SDK for Android:

You do not need to register your app. For internal line-of-business (LOB) apps that were written by or for your company, 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 policies to it. You can skip to the section Enable your iOS or Android app for app protection policy.

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

Until registration has been finished and confirmed by the Microsoft Intune team, Intune administrators won't 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, and if you aren't already working with a Microsoft contact, fill out the Microsoft Intune App Partner Questionnaire.

We'll 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.

Note

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'll 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'll 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'll 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.

The deep link is the link to your app's listing in the public app store. If your app's deep link changes in the future, you'll need to re-register your app.

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:

• Intune App SDK for iOS
• Intune App SDK for Android

If your app builds with .NET Multi-platform App UI (.NET MAUI), use this SDK variant:

• Intune App SDK for .NET MAUI - Android
• Intune App SDK for .NET MAUI - iOS

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 msintuneappsdk@microsoft.com.

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

• Intune App SDK for iOS Developer Guide: This document will walk you step-by-step through enabling your native iOS app with the Intune App SDK.

• Intune App SDK for Android Developer Guide: This document will walk you step-by-step through enabling your native Android app with the Intune App SDK.

Important

Intune regularly releases updates to the Intune App SDK. We recommend subscribing to the Intune App SDK repositories for updates so that you can incorporate the update into your software development release cycle and ensure your apps support the latest App Protection Policy settings.

Plan to take mandatory Intune App SDK updates prior to every major OS release to ensure your app continues to run smoothly as OS updates can cause breaking changes. If you do not update to the latest version prior to a major OS release, you may run the risk of encountering a breaking change and/or being unable to apply app protection policies to your app.

In addition to enabling your app for app protection policy, the following is required for your app to properly function with Microsoft Entra app based Conditional Access:

• App is built with the Microsoft Authentication Library and enabled for Microsoft Entra broker authentication.

• The Microsoft Entra Client ID for your app must be unique across iOS and Android platforms.

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: The Intune App SDK for Android doesn't control data collection from your app. The Company Portal application logs telemetry data by default. This data is sent to Microsoft Intune. As per Microsoft Policy, we don't collect any personally identifiable information (PII).

  • If end users choose not to send this data, they must turn off telemetry under Settings on the Company Portal app. To learn more, see Turn off Microsoft usage data collection.

Line-of-business apps in Intune now display the version number for iOS and Android apps. The number displays in the Microsoft Intune admin center 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.

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.

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're 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.

• 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 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 isn't the version

After you finish the necessary steps to integrate your iOS or Android app with the Intune App SDK, you'll 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'll need the following:

• Microsoft Intune test account: To test your Intune-managed app against Intune app protection features, you'll need a Microsoft Intune account.

  • If you're an ISV enabling your iOS or Android store apps for Intune app protection policy, you'll 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're developing a line-of-business app that won't be shipped to the store, you're expected to have access to Microsoft Intune through your organization. You can also sign up for a one-month free trial in Microsoft Intune.

  • If you're testing your app on a mobile device using an end user account, ensure that you have given that account an Intune license by in the Microsoft 365 admin center website after logging in with an admin account, see Assign Microsoft Intune license.

• 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. If your app has integrated the Intune SDK, but isn't listed in the list of targetable apps, you can specify the app's bundle ID (iOS) or package name (Android) in the text box when selecting Custom Apps.

• Troubleshoot: If you run into any issues while manually testing your app's installation user experience, see Troubleshoot app installation issues.

If your app is using its own custom Microsoft Entra settings for authentication, then the following steps should be taken for both public store apps, as well as internal LOB apps. The steps do not need to be taken if your app is using the Intune SDK default client ID.

Once you have registered your app within an Azure tenant, and it's showing up under All Applications, you must give your app access to the Intune Mobile App Management service. In the Microsoft Intune admin center:

1. Go to the Microsoft Entra ID blade.
2. Under App registrations, go to the listing set up for the application.
3. Click + Add a permission.
4. Click on the APIs my organization uses.
5. In the search box, enter Microsoft Mobile Application Management.
6. Under Delegated Permissions, select the DeviceManagementManagedApps.ReadWrite: Read and Write the User's App Management Data* checkbox.
7. Click Add permissions.

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:

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.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4