Skip to Content

Changes for page acmp Intune Connector

Last modified by Sabrina V. on 2026/10/08 08:36
From version 3.1
edited by Sabrina V.
on 2025/05/12 09:07
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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -ACMP Intune Connector
1 +acmp Intune Connector
Content
... ... @@ -4,60 +4,64 @@
4 4  
5 5  {{aagon.floatingbox/}}
6 6  
7 -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.
7 +{{aagon.versionierungsbox}}
8 +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.
9 +{{/aagon.versionierungsbox}}
8 8  
9 -= **Requirements for using the ACMP Intune Connector** =
11 +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.
10 10  
11 -To use the ACMP Intune Connector, the following requirements must be met:
13 += **Requirements for using the acmp Intune Connector** =
12 12  
15 +To use the acmp Intune Connector, the following requirements must be met:
16 +
13 13  * You need a user account with the appropriate permissions for Microsoft Entra ID
14 14  
15 15  {{box}}
16 -Refer to the [[//Registering an enterprise application in Microsoft Entra ID//>>doc:ACMP.68.Unternehmensanwendung registrieren in der Microsoft Entra ID.WebHome]] section for information on how to register an app and distribute the necessary permissions.
20 +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.
17 17  {{/box}}
18 18  
19 -* 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
20 -* AESB must be at least version 1.8
23 +* 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
24 +* aesb must be at least version 1.8
21 21  * You need a working internet connection, as Intune is a cloud solution and requires a network connection to work.
22 22  * A running instance of Intune
23 23  
24 24  = Prepare for Microsoft Entra ID and distribute permissions =
25 25  
26 -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//>>url:https://doc.aagon.com/bin/view/ACMP/68/Unternehmensanwendung%20registrieren%20in%20der%20Microsoft%20Entra%20ID/]]).
30 +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]]).
27 27  
28 -= Configuration in AESB and ACMP =
32 += Configuration in aesb and acmp =
29 29  
30 -Before you can use Intune in ACMP, you need to do some preliminary work in the ACMP and AESB consoles.
34 +Before you can use Intune in acmp, you need to do some preliminary work in the acmp and aesb consoles.
31 31  
32 -== 1. **ACMP console: Check SICS connection in ACMP** ==
36 +== 1. **acmp console: Check SICS connection in acmp** ==
33 33  
34 -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.
38 +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.
35 35  
36 -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.
40 +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.
37 37  
38 38  {{figure}}
39 39  [[image:65_Intune_SICS-Verbindung_575.png||alt="65_ACMP_Einstellungen_SICS Verbindung.png" data-xwiki-image-style-alignment="center"]]
40 40  
41 41  {{figureCaption}}
42 -Set up SICS connection in ACMP
46 +Set up SICS connection in acmp
43 43  {{/figureCaption}}
44 44  {{/figure}}
45 45  
46 -== 2. AESB console: **Install and configure the Intune Connector** ==
50 +== 2. aesb console: **Install and configure the Intune Connector** ==
47 47  
48 -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.
52 +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.
49 49  
50 50  {{figure}}
51 51  [[image:65_AESB_Übersicht des ACMP Intune Adapters in der AESB Console.png||data-xwiki-image-style-alignment="center"]]
52 52  
53 53  {{figureCaption}}
54 -Overview of the ACMP Intune Adapter in the AESB Console
58 +Overview of the acmp Intune Adapter in the aesb Console
55 55  {{/figureCaption}}
56 56  {{/figure}}
57 57  
58 -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.
62 +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.
59 59  
60 -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//.
64 +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//.
61 61  
62 62  In the //Intune Configuration// menu item, you can now use one of the two login methods: the secret client key or a certificate.
63 63  
... ... @@ -89,10 +89,10 @@
89 89  
90 90  === Option 2: **Secret client key authentication method:** ===
91 91  
92 -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"]].
96 +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"]].
93 93  
94 94  {{aagon.infobox}}
95 -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.
99 +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.
96 96  {{/aagon.infobox}}
97 97  
98 98  {{figure}}
... ... @@ -123,7 +123,7 @@
123 123  
124 124  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//.
125 125  
126 -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:
130 +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:
127 127  
128 128  |**Navigation point**|**Description**
129 129  |Microservices|Below the Supervisors & microservice instances, you will see the entries //IntuneConnector_1 //and //IntuneWorkflowEngine_1//.
... ... @@ -130,12 +130,12 @@
130 130  |Workflows|Within the Workflow engines & instances section, the entries //IntuneWorkflowEngine_1 //and //IntuneMobileDevices_1 //must be listed.
131 131  
132 132  {{aagon.infobox}}
133 -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//.
137 +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//.
134 134  {{/aagon.infobox}}
135 135  
136 -= How to use Intune in ACMP =
140 += How to use Intune in acmp =
137 137  
138 -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.
142 +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.
139 139  
140 140  == Query Actions ==
141 141  
... ... @@ -154,7 +154,7 @@
154 154  You can choose between the following actions:
155 155  
156 156  {{aagon.infobox}}
157 -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.
161 +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.
158 158  {{/aagon.infobox}}
159 159  
160 160  |**Query Actions**|(% style="width:1141px" %)**Description**
© Aagon GmbH 2026
Besuchen Sie unsere aagon-Community