| Anchor | ||||
|---|---|---|---|---|
|
...
You will need the URL of the LINK Controller and the Client ID. You may use your AD credentials or the Admin credentials to login to the LINK Controller.
Also see: Troubleshooting Guide
...
Please contact support@mobilehelix.com if you have not received the URL, Client ID, and Admin credentials.
...
Code-based activation is configured in the LINK Controller on the “Settings” tab. The first step is to change the launch link type to be “Activation Pincode” in the “Controller Settings” pane on the “Settings” tab. To do so, change the link type using the dropdown pictured here:
Activation Pincode
Please make sure that the “Attach a QR code …” and “Attach an hxl file …” are both toggled off.
...
At Files, tap the pencil icon.
...
Files
Change settings as shown below. Tap the Diskette icon to save.
...
Login to your Azure portal at https://portal.azure.com. To create a new App Registration, search for “App Registrations” and click on the service when it appears. Once you have opened the “App Registrations” panel:
...
From the app registration page for your new app, add a new redirect URI by clicking the link next to “Redirect URIs:”. Toggle on the checkbox next to https://login.microsoftonline.com/common/oauth2/nativeclient for the redirect URI.
Click “Save” at the bottom of the screen.
...
Next, add API permissions to your app registration. To do so, click “API Permissions” in the “Manage” section on the left panel of the page.
(See https://github.com/Azure-Samples/MipSdk-Dotnet-File-ServicePrincipalAuth for the original source):
...
Add LINK as an app in Intune and deploy it to your target user group
Login to https://endpoint.microsoft.com, your Intune management console. Under “All Services” or “Favorites”, select “Apps”. Click “All Apps”, “Add” … and select the following:
...