Changes for page acmp Intune Connector

Last modified by Sabrina V. on 2026/10/08 08:36

Manage
- Copy
Actions
- Export
- Print Preview
Viewers
- Source
- Children
- Content

From 1.1 to 2.1

From version 2.1

edited by Sabrina V.
on 2024/10/23 06:03

Change comment: There is no comment for this version

To version 8.1

edited by Sabrina V.
on 2026/10/08 08:36

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--ACMP Intune Connector
++acmp Intune Connector

Content

@@ -4,219 +4,64 @@
  {{aagon.floatingbox/}}
--Microsoft Intune is a cloud-based solution that helps you manage your mobile devices. It allows you to remotely manage devices, secure access or even lock them down. With the ACMP Intune Connector, you can inventory the devices from Intune in ACMP and send the most important actions to the devices from ACMP.
++{{aagon.versionierungsbox}}
++Please note that the acmp Intune Connector has been replaced by [[Intune Management>>doc:ACMP.610.ACMP-Solutions.Intune Management.WebHome]] in version 6.8 of acmp.
++{{/aagon.versionierungsbox}}
--= **Requirements for using the ACMP Intune Connector** =
++Microsoft Intune is a cloud-based solution that helps you manage your mobile devices. It allows you to remotely manage devices, secure access or even lock them down. With the acmp Intune Connector, you can inventory the devices from Intune in acmp and send the most important actions to the devices from acmp.
--To use the ACMP Intune Connector, the following requirements must be met:
++= **Requirements for using the acmp Intune Connector** =
--* You need a user account with the appropriate permissions for Microsoft Azure Active Directory
--* There must be a connection between AESB and ACMP. AESB must be available for this and the necessary details of the [[SICS connection>>doc:||anchor="H1.ACMPconsole:CheckSICSconnectioninACMP"]] must be stored in ACMP
--* AESB must be at least version 1.8
--* You need a working internet connection, as Intune is a cloud solution and requires a network connection to work.
--* A running instance of Intune
++To use the acmp Intune Connector, the following requirements must be met:
--= Preparations in Azure Active Directory =
++* You need a user account with the appropriate permissions for Microsoft Entra ID
--To enable the ACMP Intune Connector to access the Intune API, you must first register an enterprise application in Azure Active Directory and grant the required permissions within those applications.
++{{box}}
++Refer to the [[//Registering an enterprise application in Microsoft Entra ID//>>doc:ACMP.610.Unternehmensanwendung registrieren in der Microsoft Entra ID.WebHome]] section for information on how to register an app and distribute the necessary permissions.
++{{/box}}
--== Register the Enterprise Application ==
++* There must be a connection between aesb and acmp. aesb must be available for this and the necessary details of the [[SICS connection>>doc:||anchor="H1.ACMPconsole:CheckSICSconnectioninacmp"]] must be stored in acmp
++* aesb must be at least version 1.8
++* You need a working internet connection, as Intune is a cloud solution and requires a network connection to work.
++* A running instance of Intune
--First, sign in to the [[Azure AD (Active Directory)>>https://aad.portal.azure.com/]] and navigate to Azure Active Directory in the Overview. Click the //Manage// > //Application// //Registrations// tab and create a new application registration.
++= Prepare for Microsoft Entra ID and distribute permissions =
--{{figure}}
--[[image:65_Intune_App-Registrierung in der Azure AD.png||data-xwiki-image-style-alignment="center"]]
++In order for the acmp Intune Connector to access the Intune API, you must first register a company application in the Microsoft Entra Admin Centre and grant the necessary permissions within these applications (see [[//Registering a company application in Microsoft Entra ID//>>doc:ACMP.610.Unternehmensanwendung registrieren in der Microsoft Entra ID.WebHome]]).
--{{figureCaption}}
--App registrations in the Azure AD
--{{/figureCaption}}
--{{/figure}}
++= Configuration in aesb and acmp =
--Enter all the necessary information: Enter a name for the application and select the accounts to support. Finish the process by clicking //Register//.
++Before you can use Intune in acmp, you need to do some preliminary work in the acmp and aesb consoles.
--{{figure}}
--[[image:65_Intune_Anwendung registrieren.png||data-xwiki-image-style-alignment="center"]]
++== 1. **acmp console: Check SICS connection in acmp** ==
--{{figureCaption}}
--Register application
--{{/figureCaption}}
--{{/figure}}
++It is necessary that you have a working SICS connection in acmp. To do this, go to //System// > //Settings// > //acmp Server// > //SICS Connection//. First tick the box to enable the connection. Then enter the host and port, as well as the user name and password for the operator. You specified the corresponding operator during the installation of the aesb, which you must also specify here. Specify whether to attempt an unencrypted connection if SSL/TLS fails. Then test the connection.
--If you now open the created application, you will see a summary of the information added. This includes the display name, the various IDs (application, object and directory ID) and details of the account types supported.
++Also tick the Public API access rights box to grant access. You can now save your settings. acmp and SICS are now connected to each other.
  {{figure}}
--[[image:65_Intune_Zusammenfassung der Anwendungsinformationen.png||alt="65_Intune_Anwendung registrieren.png" data-xwiki-image-style-alignment="center"]]
--
--{{figureCaption}}
--Summary of the application information
--{{/figureCaption}}
--{{/figure}}
--
--== Distribute permissions ==
--
--The next step is to assign the necessary permissions to the business application to access the Graph API. To do this, go to the Permissions section within the registered application (//Manage// > //API// //Permissions//).
--
--{{figure}}
--[[image:65_Intune_API Berechtigungen.png||data-xwiki-image-style-alignment="center"]]
--
--{{figureCaption}}
--API permissions
--{{/figureCaption}}
--{{/figure}}
--
--There, click //Add Permission//. This will bring up a page where you can request the API permissions. In this step you need to select the //Microsoft Graph//.
--
--{{figure}}
--[[image:65_Intune_Microsoft Graph anfordern.png||data-xwiki-image-style-alignment="center"]]
--
--{{figureCaption}}
--API permissions: Request Microsoft Graph
--{{/figureCaption}}
--{{/figure}}
--
--A distinction is made between "Delegated Permissions" and "Application Permissions". Enter the following values individually under 'Delegated permissions' and repeat the process by entering each of the following list entries:
--
--* DeviceManagementManagedDevices.Read.All
--* DeviceManagementManagedDevices.ReadWrite.All
--* User.Read
--
--{{figure}}
--[[image:65_Intune_Delegierte Berechtigungen verteilen.png||data-xwiki-image-style-alignment="center"]]
--
--{{figureCaption}}
--Distribute delegated permissions
--{{/figureCaption}}
--{{/figure}}
--
--Tick the appropriate items, scroll back to the top, click the //Application Permissions// field and add the following permissions:
--
--* DeviceManagementApps.Read.All
--* DeviceManagementConfiguration.Read.All
--* DeviceManagementManagedDevices.PrivilegedOperations.All
--* DeviceManagementManagedDevices.Read.All
--* DeviceManagementManagedDevices.ReadWrite.All
--* DeviceManagementServiceConfig.Read.All
--* User.Read.All
--
--When you have selected all the permissions, click //Add Permissions//. You will see the entries in the overview.
--
--{{figure}}
--[[image:65_Intune_Verteilte Berechtigungen (ohne Einwilligung).png||data-xwiki-image-style-alignment="center"]]
--
--{{figureCaption}}
--Deployed permissions (without consent)
--{{/figureCaption}}
--{{/figure}}
--
--If you have not already done so, you may need to give your consent to the permissions. To do this, click on the //Grant administrator// //consent for// //"%Your Company%//" field. This will change the status and the user permission will be granted.
--
--{{figure}}
--[[image:65_Intune_Bewilligte Berechtigungen.png||data-xwiki-image-style-alignment="center"]]
--
--{{figureCaption}}
--Authorised permissions
--{{/figureCaption}}
--{{/figure}}
--
--== Upload client secret key or certificates ==
--
--Later, during the initial setup of the ACMP Intune Connector, you have to specify an authentication type in the AESB console. You can choose from two methods supported by the Microsoft Client Credentials Provider: //Certificate// or //Client Secret Key//.
--
--{{aagon.infobox}}
--The procedure differs depending on the authentication type selected. Read below to find out what you need to consider for each method.
--{{/aagon.infobox}}
--
--=== Upload certificate ===
--
--{{aagon.infobox}}
--Due to the higher level of security, Microsoft recommends that you use a certificate as your credential.
--{{/aagon.infobox}}
--
--Certificates can be used as an authentication method to log in to Azure Active Directory in the AESB console. A certificate always consists of a public and private part, where the public key is loaded directly into Azure AD. The private part is used in the AESB console. This certificate pair needs to be generated beforehand. Read how to generate a certificate via [[Microsoft>>url:https://learn.microsoft.com/en-us/azure/app-service/configure-ssl-certificate?tabs=apex%2Cportal]] or[[ Open SSL>>url:https://stackoverflow.com/questions/6307886/how-to-create-pfx-file-from-certificate-and-private-key]].
--
--Navigate to //Certificates & Secrets// in the previously registered application. In the details, click on the //Certificates// tab and upload the previously created certificate.
--
--{{figure}}
--[[image:65_Intune_Zertifikat hochladen.png||data-xwiki-image-style-alignment="center"]]
--
--{{figureCaption}}
--Upload certificate
--{{/figureCaption}}
--{{/figure}}
--
--A field will open on the right hand side where you can upload the certificate. Browse to the appropriate directory, upload the file and enter an optional description for the certificate. Then click Add and the certificate will be saved for the application.
--
--{{aagon.infobox}}
--Please note that only .cer, .pem and .crt file types are supported when uploading a certificate.
--{{/aagon.infobox}}
--
--{{figure}}
--[[image:65_Intune_Hochgeladenes Zertifikat in der Azure Active Directory.png||data-xwiki-image-style-alignment="center"]]
--
--{{figureCaption}}
--Uploaded certificate in the Azure Active Directory
--{{/figureCaption}}
--{{/figure}}
--
--=== Adding a secret client key ===
--
--The secret client key is a string of characters used by the enterprise application as an authentication key or proof of identity when requesting the token. To do this, go to the Permissions area within the registered application (//Security// > //Permissions//) and click the Application Registration link. Navigate to //Certificates// & //Secrets//. In the details, click the //Secret Client Keys// tab and create a new key.
--
--{{figure}}
--[[image:65_Intune_Neuen Clientschlüssel hinterlegen.png||data-xwiki-image-style-alignment="center"]]
--
--{{figureCaption}}
--Store new client key
--{{/figureCaption}}
--{{/figure}}
--
--When creating a new secret client key, you can configure the validity period. Note that once the validity period has expired, a new key must be created and stored in the AESB.
--
--{{figure}}
--[[image:65_Intune_Geheimen Clientschlüssel hinterlegen.png||data-xwiki-image-style-alignment="center"]]
--
--{{figureCaption}}
--Adding a secret client key
--{{/figureCaption}}
--{{/figure}}
--
--{{aagon.infobox}}
--You will need the secret client key you created when you set up the AESB. Keep this in mind for future reference.
--{{/aagon.infobox}}
--
--= Configuration in AESB and ACMP =
--
--Before you can use Intune in ACMP, you need to do some preliminary work in the ACMP and AESB consoles.
--
--== 1. **ACMP console: Check SICS connection in ACMP** ==
--
--It is necessary that you have a working SICS connection in ACMP. To do this, go to //System// > //Settings// > //ACMP Server// > //SICS Connection//. First tick the box to enable the connection. Then enter the host and port, as well as the user name and password for the operator. You specified the corresponding operator during the installation of the AESB, which you must also specify here. Specify whether to attempt an unencrypted connection if SSL/TLS fails. Then test the connection.
--
--Also tick the Public API access rights box to grant access. You can now save your settings. ACMP and SICS are now connected to each other.
--
--{{figure}}
  [[image:65_Intune_SICS-Verbindung_575.png||alt="65_ACMP_Einstellungen_SICS Verbindung.png" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
--Set up SICS connection in ACMP
++Set up SICS connection in acmp
  {{/figureCaption}}
  {{/figure}}
--== 2. AESB console: **Install and configure the Intune Connector** ==
++== 2. aesb console: **Install and configure the Intune Connector** ==
--Now go to the AESB console. From the Dashboard, navigate to the //Products// menu item. In the overview you will find a list of all packages available for installation or updates. Select //ACMP Intune Adapter// and click //Install// either in the quick selection bar or directly in the fields. A new window will open and the installation will begin.
++Now go to the aesb console. From the Dashboard, navigate to the //Products// menu item. In the overview you will find a list of all packages available for installation or updates. Select //acmp Intune Adapter// and click //Install// either in the quick selection bar or directly in the fields. A new window will open and the installation will begin.
  {{figure}}
  [[image:65_AESB_Übersicht des ACMP Intune Adapters in der AESB Console.png||data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
--Overview of the ACMP Intune Adapter in the AESB Console
++Overview of the acmp Intune Adapter in the aesb Console
  {{/figureCaption}}
  {{/figure}}
--The first step tells you what you need to have already done to successfully install the Intune Adapter: You need a configured and working Microsoft Intune instance and a working ACMP SICS connection. In the second step of the installation wizard, you have the option to assign a template name at the top of the pages.
++The first step tells you what you need to have already done to successfully install the Intune Adapter: You need a configured and working Microsoft Intune instance and a working acmp SICS connection. In the second step of the installation wizard, you have the option to assign a template name at the top of the pages.
--Under //Intune Connector Configuration//, you can set basic settings for the Intune Connector. Under ACMP Server ID, you need to specify the server to which the changes will be sent. If you enter an asterisk, the changes will be sent to all ACMP servers that have a SICS connection and whose connection information is identical to the information you entered in step //[[1. ACMP console: Check SICS connection in ACMP>>doc:||anchor="H1.ACMPconsole:CheckSICSconnectioninACMP"]]//. You can also specify the name of the workflow instance under which the settings are to be sent. You can do this under //Ondemand definition name//.
++Under //Intune Connector Configuration//, you can set basic settings for the Intune Connector. Under acmp Server ID, you need to specify the server to which the changes will be sent. If you enter an asterisk, the changes will be sent to all acmp servers that have a SICS connection and whose connection information is identical to the information you entered in step //[[1. acmp console: Check SICS connection in acmp>>doc:||anchor="H1.ACMPconsole:CheckSICSconnectioninacmp"]]//. You can also specify the name of the workflow instance under which the settings are to be sent. You can do this under //Ondemand definition name//.
  In the //Intune Configuration// menu item, you can now use one of the two login methods: the secret client key or a certificate.
@@ -248,10 +248,10 @@
  === Option 2: **Secret client key authentication method:** ===
--Select //secret client key// as the authentication type. Under //secret client key//, enter the value that you generated as the secret key on the  [[Azure Active Directory pages>>doc:||anchor="HUploadclientsecretkeyorcertificates"]].
++Select //secret client key// as the authentication type. Under //secret client key//, enter the value that you generated as the secret key on the [[Azure Active Directory pages>>doc:||anchor="HUploadclientsecretkeyorcertificates"]].
  {{aagon.infobox}}
--Please note that the value is displayed in abbreviated form. This means that it will have a different character length when entered in the AESB console.
++Please note that the value is displayed in abbreviated form. This means that it will have a different character length when entered in the aesb console.
  {{/aagon.infobox}}
  {{figure}}
@@ -282,7 +282,7 @@
  Click //Verify Connection//. If the connection is successful, you will be taken to the //scanner configuration//, where you can optionally set time intervals for the scanner. If you do not want to make any changes, click //Next//.
--The Intune adapter installation will begin in the background. When the installation is complete and all items have been successfully installed, you can click //Finish//. You will be returned to the AESB Console Overview page. There are several places in the AESB Console where you can check that the installation was successful and that all the required applications are available:
++The Intune adapter installation will begin in the background. When the installation is complete and all items have been successfully installed, you can click //Finish//. You will be returned to the aesb Console Overview page. There are several places in the aesb Console where you can check that the installation was successful and that all the required applications are available:
  |**Navigation point**|**Description**
  |Microservices|Below the Supervisors & microservice instances, you will see the entries //IntuneConnector_1 //and //IntuneWorkflowEngine_1//.
@@ -289,12 +289,12 @@
  |Workflows|Within the Workflow engines & instances section, the entries //IntuneWorkflowEngine_1 //and //IntuneMobileDevices_1 //must be listed.
  {{aagon.infobox}}
--You can also install the Intune Connector more than once. This allows you to use both the secret client key and the certificate as the authentication type. A dual installation is useful, for example, if you are using multiple ACMP servers and want the data to flow to them. Multiple installations will increment the microservices and workflow entries. In this case, you would have, for example, //IntuneWorkflowEngine_1//,// IntuneWorkflowEngine_2, and IntuneMobileDevices_1 and IntuneMobileDevices_2//.
++You can also install the Intune Connector more than once. This allows you to use both the secret client key and the certificate as the authentication type. A dual installation is useful, for example, if you are using multiple acmp servers and want the data to flow to them. Multiple installations will increment the microservices and workflow entries. In this case, you would have, for example, //IntuneWorkflowEngine_1//,// IntuneWorkflowEngine_2, and IntuneMobileDevices_1 and IntuneMobileDevices_2//.
  {{/aagon.infobox}}
--= How to use Intune in ACMP =
++= How to use Intune in acmp =
--Once you have set up the ACMP Intune Connector, devices are imported from Intune into ACMP. You can use this data in queries and reports, for example. You can also send some actions to the devices through ACMP.
++Once you have set up the acmp Intune Connector, devices are imported from Intune into acmp. You can use this data in queries and reports, for example. You can also send some actions to the devices through acmp.
  == Query Actions ==
@@ -313,7 +313,7 @@
  You can choose between the following actions:
  {{aagon.infobox}}
--Note that any subsequent actions (sending notifications,retire devices, etc.) that you want to send or perform on the endpoint via Intune may be delayed. The status of the job will be shown as //Finished// in the Job Monitor as the action has been executed by ACMP and successfully passed to Intune.
++Note that any subsequent actions (sending notifications,retire devices, etc.) that you want to send or perform on the endpoint via Intune may be delayed. The status of the job will be shown as //Finished// in the Job Monitor as the action has been executed by acmp and successfully passed to Intune.
  {{/aagon.infobox}}
  |**Query Actions**|(% style="width:1141px" %)**Description**