Microsoft Intune integration

Microsoft Intune requirements

• A working Microsoft Intune instance

• The Clients must be Microsoft Intune-enabled for them to receive Microsoft Intune applications

• The user accounts must have unique email addresses, that is, Shopping end user accounts cannot share email addresses

• The relevant Shopping requirements must be met. Refer to Supported platforms and requirements

When the above requirements are met, you can do the following:

• Define the two required Azure Active Directory (AAD) authentication applications

• Configure administrator and service accounts. The UPN suffix for these two accounts should match in on-premises AD and AAD

• Make appropriate settings for Microsoft Intune in Shopping

• Enable the Configuration Manager co-management feature

Azure Active Directory Connect requirements

Azure AD Connect must be in hybrid mode and have either of these two options enabled:

• Pass-through authentication with seamless single sign-on (SSO)

• Federation

Both options are illustrated in the screenshots:

If these options are not available to you, then you must use the Client App Client Secret method of authentication.

You need the following Azure Active Directory accounts:

Purpose	Member of	Usage and notes
Configuration	Global administrator and Intune administrator AAD roles	During setup and for troubleshooting. This account performs the steps described in this article.
Service	Intune administrator AAD role	Ongoing for the Shopping Central service to access AAD user and device details and app deployment status. This is the AAD hybrid account that corresponds to the service account used to run the Shopping Central service.
Intune administrators	Intune administrator AAD role	Ongoing for Microsoft Intune app management. You might prefer to apply the Microsoft Intune administrator role to a group and add relevant administrator accounts to the group.
Shopping administrators	User and groups setting for the Shopping Console Authentication Client App, refer to Microsoft Intune integration	To access Microsoft Intune apps from the Shopping console and to trigger on-demand AAD device and user synchronizations. You might prefer to add a group to the User and groups list and add relevant Shopping administrator accounts to the group. The Microsoft Intune administrators and Shopping administrators might all be the same accounts but they do not have to be. Microsoft Intune administrators could manage the Microsoft Intune apps but not have Shopping privileges. Shopping administrators could use the Microsoft Intune apps but not be able to manage them.

In Microsoft Intune, you'll need to set up two authentication applications for Shopping. These are also known as Authentication Client Apps.

• Console authentication application: In this example named ShoppingConsoleAuthenticationClientApp

• Central Service authentication application: In this example named ShoppingServiceAuthenticationClientApp

Create your own application

In your AAD console, go to the Enterprise applications node and click New application.

In the Create your own application blade:

1. Provide a name for the application.

   • Console authentication application, in this example named ShoppingConsoleAuthenticationClientApp

   • Central Service authentication application, in this example named ShoppingServiceAuthenticationClientApp

2. Select Integrate any other application you don't find in the gallery

3. Click on the Create button.
   
   

   The application names are not important except for ease of identification. The essential distinction is that one relates to the Shopping console (as used by administrators) and the other relates to the Shopping Central service (as used by Shopping itself).

   At this point and similar points where objects are created or adjusted, you should see a success message in the upper right corner of the AAD console.

Note the Application (client) ID

You will then see an Overview tab.

Ensure you note which application the ID corresponds to:

• Console authentication application: In this example named ShoppingConsoleAuthenticationClientApp

• Central Service authentication application: In this example named ShoppingServiceAuthenticationClientApp
  

Add users and groups to the application

1. On the Overview page, click on the 1. Assign users and groups tile.

2. On the Users and groups page, click on Add user (which can also be used to add groups).
   

3. Click on the Users and groups None Selected row.

   If you are using an evaluation version of AAD, a message will be displayed on this page indicating that groups are not available for assignment. AAD groups are not required for Shopping's Microsoft Intune integration (though it's recommended to use them).
   

   Select from the Users and groups as appropriate.

   • For the Console authentication application, this should be group(s) or users that you expect to use the Shopping console. In our example, for the console app we choose the group ShoppingConsole_Admins used for our Active Directory implementation.

   • For the Central Service authentication application, this should be the Shopping Central service account.

     All the accounts or groups have to be from your Active Directory implementation (as opposed to being AAD-only accounts or groups). If you are not sure which are AD users or groups, use another AAD console and review the users and groups under the corresponding nodes. AD users and groups have a source of Windows Server AD.

     The users and groups you click on will be listed under Selected Items.

4. Click on Select to make the selections effective.
   

5. The number of users and/or groups will be displayed. If this is correct, click Assign.

   The users and/or groups will be displayed under the Users and groups node for the application.

   

Configure the App registrations

1. Click the App registrations node of your AAD directory. Click All applications. You will see your application (or applications) listed.

2. Click on the application name.
   

Configure API permissions for the App registration

1. In the Overview node of the selected application, click on the API permissions node, then click Add a permission.
   

2. In the Request API permissions dialog, click on the Microsoft Graph tile.
   

3. Click on Delegated permissions.

   If you are using Client Secrets and not Seamless SSO, you will need to choose Application permissions. You will also need to create a new client secret.

   To add a client secret:

   1. Click on the Certificates & secrets node and then click on the New client secret button.
   2. The Add a client secret form will open, add a Description and select an expiry from the Expires radio buttons and then click Add.
   3. Copy the new client secret value and save it, as you won't be able to retrieve it after you perform another operation or leave this blade.

   If you do not copy the Value at this point, when you navigate away from the Certificates & secrets screen, you will be unable to copy it again. This means that you will have to delete the Secret and recreate it.

   

   You will see a long list of API permissions, the list will be slightly different depending on whether you are using Application or Delegated permissions. Scroll through them and check them as appropriate, then, click Add permissions.

   

   For the Console authentication application, check off the following:

   Permission	Purpose
   DeviceManagementApps.Read.All	To get application status, application type, and target type.
   DeviceManagementManagedDevices.Read.All	To discover devices when the Trigger User and Device Intune Sync button is clicked.
   User.Read.All	To get user email address.

   For the Central Service authentication application, check off the following:

   Permission	Purpose
   DeviceManagementApps.Read.All	To get application status, application type, and target type. Also, to verify application assignments.
   DeviceManagementManagedDevices.PrivilegedOperations.All	To initiate client synchronization (to expedite deployments).
   DeviceManagementManagedDevices.Read.All	To discover devices when the Shopping Central service is started and then routinely after that.
   Group.ReadWrite.All	To create or remove groups to assign Microsoft Intune applications to that have been added to Shopping. This is required while creating or removing assignments to a Microsoft Intune application on groups by the Shopping Central Service during the assignment creation process.
   GroupMember.ReadWrite.All	To add or remove users or devices from a group, and to verify they've been added or removed as intended. This is required when adding or removing users or devices to and from a group by the Shopping Central Service during order processing of a Microsoft Intune application.
   User.Read.All	To get status when app is user targeted.

4. Click Grant admin consent for <tenant> In our example, the tenant is ACME.

   This means that as a tenant administrator for your organization, you're consenting that the users of the application would want to use these permissions. The users in this case would be people that would use the Shopping console and/or set up the Shopping service.

   

Configure Authentication for the App registration

1. Click on the Authentication node.

2. Scroll to the bottom of the page and under Advanced settings select Yes to enable the public client flows.

3. Click Save.

   

   For Shopping's purposes, this allows the use of Integrated Windows Authentication.

In the AAD console, click Users and select the name of a user that will be a Shopping console user and who might need to manage Microsoft Intune applications or initiate AAD user and device synchronization.

1. Click on the Assigned roles node.

2. Click Add assignments.

3. Check the Directory role called Intune administrator and click Add.
   
   

   You must repeat this process for the service account used to run the Shopping Central service. Both the Shopping console user and Shopping Central service accounts must be licensed for Microsoft Intune.

   The user account must be a hybrid account and so in the list of users the source of the account must be Windows Server AD.

Update license assignments

In the AAD console, go to the list of users and select the name of a user that will be a Shopping console user and who might need to manage Microsoft Intune applications or initiate AAD user and device synchronization. The steps below are also required for the Shopping Central service account to synchronize users and devices from Microsoft Intune.

1. Click on the Licenses node.

2. Click on Assignments.

3. Select an appropriate license, such as Enterprise Mobility + Security E5.

4. Click Save.
   

You can do this either during an installation or upgrade or from the Shopping Admin Console after an installation or upgrade.

During installation or upgrade

Early in the Shopping Central installation wizard, when you specify the installation type you can indicate whether the Microsoft Intune integration should be enabled by checking Enable integration with Intune.

If you enabled the integration with Microsoft Intune, later in the installation wizard you can specify the integration details:

ID	Note
Azure tenant ID	This is the same as your Azure tenant ID, available in the Overview node of your AAD console.
Service authentication client app ID	Available in the Overview node for the app in the App Registrations or Enterprise applications nodes of your AAD console.
Console authentication client app ID	Available in the Overview node for the app in the App Registrations or Enterprise applications nodes of your AAD console.

After installation or upgrade

You could have enabled Microsoft Intune integration while installing Shopping or upgrading to it. If you did not do so, start the Shopping Admin Console and go to the Intune Integration group of settings in the Settings node.

Click Save.

Restart the Shopping Central service and then the Shopping Admin Console.

This section describes where the co-management settings would be configured by a Configuration Manager administrator. The Microsoft Intune clients will not try to do software distribution if this feature is not enabled. Refer to your Configuration Manager documentation for full instructions on how to configure co-management. No additional configuration is needed in Shopping to support this feature.

1. Using a ConfigMgr console, in the Administration node, under Cloud Services, Azure Services, in the ribbon click on Configure Azure Services and add Cloud Management.

2. Under Cloud Services, Co-management, configure the co-management.

3. Set Client apps to use Intune.

4. The ConfigMgr clients must be restarted to reflect these changes (as reflected in the client-side CoManagementHandler log).
   

You are now ready to use Shopping with Microsoft Intune. If you have appropriate applications set up in Microsoft Intune, you can define the applications in Shopping (refer to Microsoft Intune applications for details) so that they can be made available to users.

Users can then request the applications from the Shopping web interface. The applications will be delivered by Microsoft Intune and their status will be returned to Shopping. The features of Shopping, such as approvals and rentals, can be used with these applications.

Here is a list of frequently asked questions regarding the integration: