Last modified by Sabrina V. on 2025/09/23 11:50

From version 9.1
edited by Sabrina V.
on 2025/09/23 11:50
Change comment: There is no comment for this version
To version 1.1
edited by Sabrina V.
on 2025/05/20 08:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Register a company application in Microsoft Entra ID
1 +Unternehmensanwendung registrieren in der Microsoft Entra ID
Content
... ... @@ -13,20 +13,12 @@
13 13  
14 14  == Register an Enterprise Application ==
15 15  
16 -First, log in to your [[Microsoft Entra ID>>url:https://aad.portal.azure.com/]]. Click the //Identity //> //Manage //tab > //Enterprise Applications// and create a new application registration.
16 +First, log in to your [[Microsoft Entra ID>>url:https://aad.portal.azure.com/]]. Click the Identity > Manage tab > //Enterprise Applications// and create a new application registration.
17 17  
18 18  [[App registrations in Microsoft Entra ID>>image:68_Unternehmensanwendung registrieren_App Registrierung Oberfläche_1919.png]]
19 19  
20 -Enter all the necessary information there: Assign an app name and select the accounts to be supported.
20 +Enter all the necessary information there: Assign an app name and select the accounts to be supported. Complete the process by clicking //Register//.
21 21  
22 -{{box}}
23 -**Note for [[setting up OAuth2 on the ACMP Server>>doc:ACMP.68.ACMP-Solutions.System.Einstellungen.ACMP Server.OAuth2 am ACMP Server einrichten.WebHome]]:**
24 -If only one account from the organisation directory is allowed to access it, you must select the first option. Under the redirect URI, you must enter the following: https://login.microsoftonline.com/common/oauth2/nativeclient
25 -Register the application as //Public client/native (mobile & desktop)//.
26 -{{/box}}
27 -
28 -Complete the process by clicking //Register//.
29 -
30 30  [[Register an application>>image:68_Unternehmensanwendung registrieren_App Registrierung neue anlegen_1919.png]]
31 31  
32 32  When you open the application you have created, you will see a summary of the information you have added. This includes the display name, details of the supported account types and the various IDs (application, object and directory ID). You will need the latter details (the IDs) if, for example, you want to create a new portal for Microsoft 365.
... ... @@ -37,38 +37,14 @@
37 37  
38 38  Next, grant the company application the necessary permissions so that it can access the interface. To do this, switch to the Permissions area within the registered app (//Manage// > //API permissions//).
39 39  
40 -[[Add permission>>image:68_Unternehmensanwendung registrieren_Berechtigungen hinzufügen_1919.png]]
32 +[[Add permissions>>image:68_Unternehmensanwendung registrieren_Berechtigungen hinzufügen_1919.png]]
41 41  
42 -Add permissions Click on //Add permission. //A page will open where you can request API permissions. In this step, you must select //Microsoft Graph/Intune//.
34 +Add permissions Click on //Add permission. //A page will open where you can request API permissions. In this step, you must select //Microsoft Graph//.
43 43  
44 44  [[API permissions: Request Microsoft Graph>>image:68_Unternehmensanwendung registrieren_API-Berechtigungen Microsoft Graph anfordern_850.png||data-xwiki-image-style-alignment="center" height="722" width="701"]]
45 45  
46 46  Depending on the area for which you want to grant authorisations, a distinction is made between ‘Delegated authorisations’ and ‘Application authorisations’. The tables below show the authorisations that you must insert here for the respective area.
47 47  
48 -=== Intune Management ===
49 -
50 -The following permissions are required to use Intune Management:
51 -
52 -**Intune**
53 -
54 -|**Type: Application**
55 -|get_data_warehouse
56 -|get_device_compliance
57 -
58 -(% class="wikigeneratedid" %)
59 -**Microsoft Graph**
60 -
61 -|**Typ: Application**
62 -|DeviceManagementApps.ReadWrite.All
63 -|DeviceManagementConfiguration.Read.All
64 -|DeviceManagementManagedDevices.PrivilegedOperations.All
65 -|DeviceManagementManagedDevices.ReadWrite.All
66 -|DeviceManagementServiceConfig.Read.All
67 -|Group.ReadWrite.All
68 -|GroupMember.ReadWrite.All
69 -|User.ReadWrite.All
70 -|Directory.ReadWrite.All
71 -
72 72  === Microsoft 365 ===
73 73  
74 74  **Only the application permissions are required to use Microsoft 365. Insert the following values individually and repeat the procedure until both list entries have been added:**
... ... @@ -121,7 +121,7 @@
121 121  Due to the higher security level, Microsoft recommends using a certificate as login information.
122 122  {{/aagon.infobox}}
123 123  
124 -Certificates can be used as an authentication method to log in to Microsoft Entra ID. A certificate always consists of a public and a private part, with the public key being loaded directly into Microsoft Entra ID. Both parts are required at a later stage when you add the certificate to the connection information for creating a new portal. This certificate pair must be generated in advance. Read here how to create a certificate via [[Microsoft>>url:https://learn.microsoft.com/en-us/azure/app-service/configure-ssl-certificate?tabs=apex%2Cportal]] or Open SSL. Due to the higher security level, Microsoft recommends using a certificate as login information
92 +Certificates can be used as an authentication method to log in to Microsoft Entra ID. A certificate always consists of a public and a private part, with the public key being loaded directly into Microsoft Entra ID. Both parts are required at a later stage when you add the certificate to the connection information for creating a new portal. This certificate pair must be generated in advance. Read here how to create 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]]. Due to the higher security level, Microsoft recommends using a certificate as login information
125 125  
126 126  {{aagon.infobox}}
127 127  The PKCS#12 or PFX/P12 format is often used for certificates. This is not supported by ACMP, as the certificate and key files are combined in a single file. However, you can use the OpenSSL commands openssl pkcs12 -in path.p12 -out newfile.crt -clcerts –nokeys for the certificate and openssl pkcs12 -in path.p12 -out newfile.pem -nocerts –nodes for the private key to generate two files from the file.
... ... @@ -128,43 +128,44 @@
128 128  You can find continuing info on this topic in the section [[Managing certificates>>doc:ACMP.68.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HEnde-zu-Ende-VerschlFCsselung"]].
129 129  {{/aagon.infobox}}
130 130  
131 -Navigate to the //Certificates & Secrets// item within the previously registered application. Click on the //Certificates //tab in the details and upload the certificate you created earlier.
99 +Navigieren Sie innerhalb der zuvor registrierten Anwendung zu dem Punkt //Zertifikate & Geheimnisse//. Klicken Sie dort in den Details auf den Reiter //Zertifikate //und laden Sie das zuvor erstellte Zertifikat hoch.
132 132  
133 -[[Upload a certificate>>image:68_Unternehmensanwendung registrieren_Zertifikat_1915.png]]
101 +[[Zertifikat hochladen>>image:68_Unternehmensanwendung registrieren_Zertifikat_1915.png]]
134 134  
135 -A field will open on the right-hand side where you can upload the certificate. Browse to the appropriate folder, upload the file and enter an optional description for the certificate. Then click //Add// and the certificate will be stored for the application.
103 +Auf der rechten Seite öffnet sich ein Feld, in dem Sie das Zertifikat hochladen können. Durchsuchen Sie den entsprechenden Ordner und laden Sie die Datei hoch und geben Sie eine optionale Beschreibung für das Zertifikat ein. Klicken Sie dann auf //Hinzufügen// und das Zertifikat wird für die Anwendung hinterlegt.
136 136  
137 137  {{aagon.infobox}}
138 -Please note that only .cer, .pem and .crt file types are supported when uploading a certificate.
106 +Beachten Sie, dass beim Hochladen eines Zertifikats nur die Dateitypen .cer, .pem und .crt unterstützt werden.
139 139  {{/aagon.infobox}}
140 140  
141 141  
142 -[[Certificate uploaded to Microsoft Entra>>image:68_Unternehmensanwendung registrieren_Hochgeladenes Zertifikat in Microsoft Entra_1919.png]]
110 +[[Hochgeladenes Zertifikat in Microsoft Entra>>image:68_Unternehmensanwendung registrieren_Hochgeladenes Zertifikat in Microsoft Entra_1919.png]]
143 143  
144 -== Add secret client key ==
112 +== Geheimen Clientschlüssel hinzufügen ==
145 145  
146 -The secret client key is a character string that is used in the company application as an authentication key or proof of identity when requesting the token. To do this, switch to the //Certificates & Secrets// area within the registered application. Click on the //Secret Client Keys //tab in the details and create a new key.
114 +Der geheime Clientschlüssel ist eine Zeichenfolge, die bei der Unternehmensanwendung beim Anfordern des Tokens als Authentifizierungsschlüssel bzw. Identitätsnachweis verwendet wird. Wechseln Sie dafür innerhalb der registrierten Anwendung in den Bereich //Zertifikate & Geheimnisse//. Klicken Sie in den Details auf den Reiter //Geheime Clientschlüssel //und legen Sie einen neuen Schlüssel an.
147 147  
148 -[[Secret client key>>image:68_Unternehmensanwendung registrieren_Geheimen Clientschlüssel_1919.png]]
116 +[[Geheimer Clientschlüssel>>image:68_Unternehmensanwendung registrieren_Geheimen Clientschlüssel_1919.png]]
149 149  
150 -When creating a new secret client key, you have the option of configuring its validity period. Please note that once the validity period has expired, a new key must be created and stored.
118 +Beim Erstellen eines neuen geheimen Clientschlüssels haben Sie die Möglichkeit, die Gültigkeitsdauer zu konfigurieren. Beachten Sie hierbei, dass nach Ablauf der Gültigkeit ein Schssel neu erstellt und dieser neu hinterlegt werden muss.
151 151  
152 -[[Add secret client key>>image:68_Unternehmensanwendung registrieren_Geheimen Clientschlüssel hinzufügen_1919.png||alt="68_Unternehmensanwendung registrieren_Geheimen Clientschlüssel_1919.png"]]
120 +[[Geheimen Clientschlüssel hinzufügen>>image:68_Unternehmensanwendung registrieren_Geheimen Clientschlüssel_1919.png]]
153 153  
154 154  {{aagon.infobox}}
155 -If you want to use the secret client key for the ACMP Intune Connector, you must create a new key after the validity period has expired and store it in the AESB.
123 +Sollten Sie den geheimen Clientschlüssel für den ACMP Intune Connector nutzen wollen, müssen Sie den Schlüssel nach Ablauf der Gültigkeit neu erstellen und diesen im AESB hinterlegen.
156 156  {{/aagon.infobox}}
157 157  
158 158  {{aagon.infobox}}
159 -You will need the secret client key you created at a later point (e.g. when setting up AESB or in Microsoft 365 to create new portals in the ACMP Console). Therefore, save the secret client key so that you can access it later.
127 +Sie benötigen zu einem späteren Zeitpunkt den erstellten geheimen Clientschlüssel noch einmal (z.B. bei der Einrichtung des AESB oder bei Microsoft 365 r das neue Anlegen der Portale in der ACMP Console). Speichern Sie sich deswegen den geheimen Clientschlüssel zwischen, damit Sie später auf ihn zugreifen können.
160 160  {{/aagon.infobox}}
161 161  
162 -= Next steps =
130 += Weiteres Vorgehen =
163 163  
164 -Now that you have registered the company application and granted the necessary permissions, you can switch to the respective application area and continue with your work:
132 +Nachdem Sie nun die Unternehmensanwendung registriert und die notwendigen Berechtigungen erteilt haben, nnen Sie in den jeweiligen Anwendungsbereich wechseln und mit Ihren Arbeiten fortfahren:
165 165  
166 166  * [[Intune Management>>doc:ACMP.68.ACMP-Solutions.Intune Management.WebHome]]
167 167  * [[Microsoft 365>>doc:ACMP.68.ACMP-Solutions.Lizenzmanagement.Microsoft 365.WebHome]]
168 -* [[Setting up OAuth2 on the ACMP Server>>doc:ACMP.68.ACMP-Solutions.System.Einstellungen.ACMP Server.OAuth2 am ACMP Server einrichten.WebHome]]
169 169  * [[ACMP Intune Connector>>doc:ACMP.68.ACMP-Solutions.Client-Management.ACMP Intune Connector.WebHome]]
137 +* [[Einrichtung von OAuth2 am ACMP Server>>doc:ACMP.68.ACMP-Solutions.System.Einstellungen.ACMP Server.OAuth2 am ACMP Server einrichten.WebHome]]
138 +
170 170  
© Aagon GmbH 2025
Besuchen Sie unsere Aagon-Community