Changes for page Microsoft 365

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,100 +1,10 @@
1	1	{{aagon.floatingbox/}}
2	2
3		-= Preparing for the Microsoft Entra ID =
	3	+= Register preparations for Microsoft Entra ID and enterprise application =
4	4
5		-To use Microsoft 365, you must first navigate to the Microsoft Entra Admin Centre, register an enterprise application, and grant the necessary permissions within that application. These steps are necessary for ACMP to access and import the required Microsoft 365 data.
	5	+To use Microsoft 365, you must first navigate to the Microsoft Entra Admin Centre, register a business application, and grant the necessary permissions within that application. These steps are necessary to allow ACMP to access and import the required Microsoft 365 data. Detailed instructions on how to do this can be found [[here>>doc:ACMP.69.Unternehmensanwendung registrieren in der Microsoft Entra ID.WebHome]], along with all the permissions you will need to grant.
6	6
7		-== Register an Enterprise Application ==
8	8
9		-First, log in to your [[Microsoft Entra ID>>url:https://aad.portal.azure.com/]] . Click the //Manage// tab > //Enterprise Applications// and create a new application registration.
10		-
11		-[[Application registrations in Microsoft Entra ID>>image:67_Microsoft 365_App-Registrierung in der Entra_2910.png]]
12		-
13		-Enter all required information: Enter an application name and select the accounts to support. Click //Register// to complete the process.
14		-
15		-[[Registering an application>>image:67_Microsoft 365_Anwendung registrieren_2262.png]]
16		-
17		-When you open the created application, you will see a summary of the information added. You will need the application and directory ID from this for the next step when you create a new portal for Microsoft 365.
18		-
19		-[[Application information summary>>image:67_Microsoft 365_Zusammenfassung der Anwendungsinformationen_3344.png]]
20		-
21		-== Distribute permissions ==
22		-
23		-Next, grant the required permissions to the business application so that the interface can be accessed. To do this, go to the Permissions section within the registered application (//Security// > //Permissions//).
24		-
25		-[[Permissions>>image:67_Microsoft 365_Berechtigungen_2720.png]]
26		-
27		-Click //Add Permission//. This will open a page where you can request API permissions. In this step you need to select Microsoft Graph.
28		-
29		-[[API Permissions: Request Microsoft Graph>>image:67_Microsoft 365_Microsoft Graph_1284.png||data-xwiki-image-style-alignment="center" height="822" width="650"]]
30		-
31		-**Only the application permissions are required to use Microsoft 365. Add the following values one at a time and repeat the process until both list entries are added:**
32		-
33		-* **User.Read.All (Type: Application)**
34		-* **Organisation.Read.All (Type: Application)**
35		-
36		-{{aagon.warnungsbox}}
37		-You only need to assign the application permissions, not the delegated permissions!
38		-{{/aagon.warnungsbox}}
39		-
40		-[[Assigning application permissions>>image:67_Microsof 365_Anwendungen verteilen_Umrandung_3822.png||alt="67_Microsof 365_Anwendungen verteilen_3822.png"]]
41		-
42		-Once you have selected both permissions, click //Add Permissions//. You will see the entries in the overview.
43		-
44		-[[Assigned privileges (without consent)>>image:67_Microsoft 365_Verteilte Berechtigungen (ohne Einwilligung)_2818.png]]
45		-
46		-You may need to grant permissions if you have not already done so. To do this, click on the //'Grant administrator consent for %your company%//' field. This will change the status and provide user consent.
47		-
48		-[[Approved permissions>>image:67_Microsoft 365_Verteilte Berechtigungen (ohne Einwilligung)_2818.png]]
49		-
50		-= Upload private client keys or certificates =
51		-
52		-When you first set up Microsoft 365, you need to specify authentication types. You can choose from two methods supported by the Microsoft Client Credentials Provider: //certificates// or //secret client keys//.
53		-
54		-{{aagon.infobox}}
55		-The procedure is different depending on the authentication type you choose. Read below to find out what to do for each method.
56		-{{/aagon.infobox}}
57		-
58		-== Upload a certificate ==
59		-
60		-{{aagon.infobox}}
61		-Because of the higher level of security, Microsoft recommends that you use a certificate as your credential.
62		-{{/aagon.infobox}}
63		-
64		-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, where the public key is loaded directly into the Microsoft Entra ID. Both parts will be needed later when you can add the certificate to the connection information to create a new portal. This certificate pair must be created beforehand. Read on to find out how to create a certificate using [[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]].
65		-
66		-{{aagon.infobox}}
67		-The PKCS#12 or PFX/P12 format is often used for certificates. This is not supported by ACMP because the certificate and key file are combined in one file. However, you can use the OpenSSL commands openssl pkcs12 -in path.p12 -out newfile.crt -clcerts –nokeys to generate two files from the file for the certificate and openssl pkcs12 -in path.p12 -out newfile.pem -nocerts –nodes for the private key.
68		-For more information, see the [[Managing certificates>>doc:ACMP.67.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HEnde-zu-Ende-VerschlFCsselung"]] section.
69		-{{/aagon.infobox}}
70		-
71		-Within the previously registered application, navigate to //Certificates & Secrets//. In the details section, click the //Certificates// tab and upload the certificate you created earlier.
72		-
73		-[[Upload certificates>>image:67_Microsoft 365_Zertifikat hochladen_3356.png]]
74		-
75		-A field will open on the right-hand side for you to upload the certificate. Browse to the appropriate directory and upload the file, then enter an optional description for the certificate. Click //Add// and the certificate will be saved for the application.
76		-
77		-{{aagon.infobox}}
78		-Please note that only .cer, .pem and .crt file types are supported when uploading a certificate.
79		-{{/aagon.infobox}}
80		-
81		-
82		-[[Uploaded certificate in Microsoft Entra>>image:67_Microsoft 365_Hochgeladenes Zertifikat in Entra_3052.png]]
83		-
84		-== Adding a secret client key ==
85		-
86		-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 //Certificates & Secrets// section of the registered application. In the details, click on the //Secret Client Keys// tab and create a new key.
87		-
88		-[[Adding a news client key>>image:67_Microsoft 365_Neuen Clientschlüssel hinterlegen_3052.png]]
89		-
90		-When creating a new secret client key, you will be given the option to configure the validity period. Please note that when the validity period expires, a new key must be created and saved.
91		-
92		-[[Adding a secret client key>>image:67_Microsoft 365_Geheimen Clientschlüssel hinzufügen_3052.png]]
93		-
94		-{{aagon.infobox}}
95		-You will need the created secret client key when setting up Microsoft 365 to create new portals in the ACMP console. Therefore, save the secret client key so that you can access it later.
96		-{{/aagon.infobox}}
97		-
98	98	= Settings for Microsoft 365 =
99	99
100	100	The //Microsoft 365// section provides an overview of the portals you have saved and from which you want to import information.
...	...	@@ -103,7 +103,7 @@
103	103
104	104	To manage the portals, in the open ACMP console, navigate to //System// > //Settings// > //Licence// //Management// > //Microsoft// //365//. The view is split into two parts. On the left, you will see the action fields where you can add ([[image:1731318667592-246.png]]), edit ([[image:1731318667592-758.png]]) or delete ([[image:1731318667592-156.png]]) the Microsoft 365 portals. At the bottom is a list of all the existing portals that you have previously created. On the right, you can see the details of the portal you selected.
105	105
106		-[[Microsoft 365 portals overview>>image:67_M365_Hinzugefügtes Portal_1361.png]]
	16	+[[Microsoft 365 portals overview>>image:68_M365_Hinzugefügtes Portal_1361.png||alt="67_M365_Hinzugefügtes Portal_1361.png"]]
107	107
108	108	== Add a Microsoft 365 portal ==
109	109
...	...	@@ -147,7 +147,7 @@
147	147
148	148	Finish the wizard by clicking //Done//. You will return to the overview page within the ACMP settings, where the new portal has been added to the list.
149	149
150		-[[Added portal in the Microsoft 365 settings>>image:67_M365_Hinzugefügtes Portal_1361.png]]
	60	+[[Added portal in the Microsoft 365 settings>>image:68_M365_Hinzugefügtes Portal_1361.png||alt="67_M365_Hinzugefügtes Portal_1361.png"]]
151	151
152	152	== Editing or deleting Microsoft 365 portals ==
153	153
...	...	@@ -169,7 +169,7 @@
169	169
170	170	= Licenses, products and compliance =
171	171
172		-The execution of two [[server tasks>>doc:ACMP.67.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HGeplanteServeraufgaben"]] is required to import licenses and products and to calculate the status:
	82	+The execution of two [[server tasks>>doc:ACMP.69.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HGeplanteServeraufgaben"]] is required to import licenses and products and to calculate the status:
173	173
174	174	|**Server task**|**Description**
175	175	|1. Import Microsoft 365 licence data|The server task imports the Microsoft 365 licence and product data for License Management and creates the licences and products.
...	...	@@ -176,13 +176,13 @@
176	176	|2. Recalculation of the data for the compliance view|The compliance data is recalculated to determine the consumers and the status of the licence.
177	177
178	178	{{aagon.infobox}}
179		-The execution interval of the Scheduled Server Tasks depends on the configured start condition. You can view the status of the server jobs using the [[Server Monitor>>doc:ACMP.67.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HServermonitor"]].
	89	+The execution interval of the Scheduled Server Tasks depends on the configured start condition. You can view the status of the server jobs using the [[Server Monitor>>doc:ACMP.69.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HServermonitor"]].
180	180	{{/aagon.infobox}}
181	181
182	182	The licences, products and required contacts are created when the data is imported. The compliance recalculation is used to calculate the status.
183	183
184	184	{{aagon.infobox}}
185		-The new contacts can be accessed from the [[Master Data>>doc:ACMP.67.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Stammdaten.WebHome]] (//Master Data //> //Contacts//). The contacts are required to complete the compliance calculation at the end and to record them as licence users and link them to the appropriate licences and products.
	95	+The new contacts can be accessed from the [[Master Data>>doc:ACMP.69.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Stammdaten.WebHome]] (//Master Data //> //Contacts//). The contacts are required to complete the compliance calculation at the end and to record them as licence users and link them to the appropriate licences and products.
186	186	{{/aagon.infobox}}
187	187
188	188	For more detailed information on products and licences, navigate to Licence Management.
...	...	@@ -191,13 +191,13 @@
191	191	All licence and product data from the portal is read-only and cannot be edited. The Microsoft 365 portal is the leading system and cannot be changed by the administrator.
192	192	{{/aagon.infobox}}
193	193
194		-[[Read linked product from licence>>image:67_M365_Lizenzen Verknüpfte Produkte_1831.png]]
	104	+[[Read linked product from licence>>image:68_M365_Lizenzen Verknüpfte Produkte_1831.png||alt="67_M365_Lizenzen Verknüpfte Produkte_1831.png"]]
195	195
196	196	== Products ==
197	197
198	198	Products are created on initial creation in the following output directory //Microsoft 365// > //Portal name// (here: Microsoft 365 Portal). Products can be dragged and dropped into other directories as required. The product name is made up of the portal name (prefix) and the licence title.
199	199
200		-[[Reading Microsoft 365 portal products>>image:67_M365_Produkte markiert_1280.png]]
	110	+[[Reading Microsoft 365 portal products>>image:68_M365_Produkte markiert_1280.png||alt="67_M365_Produkte markiert_1280.png"]]
201	201
202	202	{{aagon.infobox}}
203	203	There is a new automatic consumer (type: Microsoft 365) to correctly identify consumers. This is only used for Microsoft 365 imports and is not available for selection when manually creating a product
...	...	@@ -225,68 +225,69 @@
225	225	|The portal has been deleted.|The complete portal has been deleted from the settings and no longer exists.|If you have deleted the portal in the ACMP settings, you must manually delete the already imported products and licenses from the License Management.
226	226
227	227	{{aagon.infobox}}
228		-You can find out more about the different statuses of the licenses [[here>>doc:ACMP.67.ACMP-Solutions.Lizenzmanagement.Compliance.WebHome||anchor="HStatusderLizenzen"]].
	138	+You can find out more about the different statuses of the licenses [[here>>doc:ACMP.69.ACMP-Solutions.Lizenzmanagement.Compliance.WebHome||anchor="HStatusderLizenzen"]].
229	229	{{/aagon.infobox}}
230	230
231		-= Fehlermeldungen beim Zugriff auf die Microsoft 365 GraphAPI =
	141	+= Error messages when accessing the Microsoft 365 GraphAPI =
232	232
233		-Beim Zugriff auf die Microsoft 365 GraphAPI wird ein sogenannter Access Token benötigt. Dieser Token wird von der geplanten Serveraufgabe beim Import der Microsoft 365 Daten für jedes konfigurierte Portal generiert. Sollte es beim Generieren des Tokens zu Problemen kommen, wird Ihnen dies als Fehlermeldung im Log angezeigt. Den Eintrag dazu finden Sie im [[Servermonitor>>doc:ACMP.67.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HServermonitor"]].
	143	+An access token is required to access the Microsoft 365 GraphAPI. This token is generated by the scheduled server task when importing Microsoft 365 data for each configured portal. If there are problems generating the token, this will be displayed as an error message in the log. You can find the corresponding entry in the [[Server Monitor>>doc:ACMP.69.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.Monitore.WebHome||anchor="HServermonitor"]].
234	234
235		-Generell gibt es zwei grundsätzliche Fehler, die auftreten können:
	145	+Generally, there are two basic errors that can occur:
236	236
237		-1. Ein von der GraphAPI gemeldeter Fehler wurde vom entsprechenden Webserver generiert.
238		-1. Es ist zu einem Fehler gekommen, der bei der Verbindung vom ACMP Server zur GraphAPI oder bei der Auswertung der Antwort der GraphAPI aufgetreten ist.
	147	+1. An error reported by the GraphAPI was generated by the corresponding web server.
	148	+1. An error occurred during the connection from the ACMP Server to the GraphAPI or during the evaluation of the GraphAPI response.
239	239
240		-Nachfolgend einige detaillierte Fehlermeldungen, die bei Ihnen erscheinen können:
	150	+The following are some detailed error messages that may appear on your system:
241	241
	152	+
242	242	|(((
243		-**Fehlermeldung **
	154	+**Error message**
244	244	)))|(((
245		-**Fehlerbeschreibung **
	156	+**Error log**
246	246	)))
247	247	|(((
248	248	Die GraphAPI meldet einen Fehler und eine Fehlerbeschreibung.
249	249	)))|(((
250		-Der ACMP Server konnte die Microsoft GraphAPI erreichen und bekam einen Fehler gemeldet.
	161	+The ACMP Server could reach the Microsoft GraphAPI and received an error.
251	251
252		-Die Fehlerbeschreibungen stammen von Microsoft und geben die Art des Fehlers wieder, die von der Microsoft GraphAPI gemeldet wurde.
	163	+The error descriptions come from Microsoft and indicate the type of error reported by the Microsoft GraphAPI.
253	253	)))
254	254	|(((
255	255	„Could not connect to GraphAPI server.“
256	256	)))|(((
257		-Der ACMP Server konnte keine Verbindung zur Microsoft GraphAPI aufbauen.
	168	+The ACMP Server could not establish a connection to the Microsoft GraphAPI.
258	258
259		-**Lösung**: Überprüfen Sie, ob Sie die [[notwendigen URLs>>doc:ACMP.67.ACMP installieren.Checkliste zur Installation.WebHome||anchor="HErforderlicheURLs"]] für Ihre Umgebung freigegeben haben.
	170	+**Solution**: Check if you have released the [[necessary URLs>>doc:ACMP.69.ACMP installieren.Checkliste zur Installation.WebHome||anchor="HErforderlicheURLs"]] for your environment.
260	260	)))
261	261	|(((
262	262	„GraphAPI webcall returned success but information could not be deserialized.“
263	263	)))|(((
264		-Der ACMP Server konnte eine Verbindung aufbauen und die Gegenstelle meldete einen Erfolg (HTTP Status 200), allerdings konnte die gelieferte Antwort nicht erfolgreich ausgewertet werden. Hier kann es sein, dass das Format ein anderes ist, als erwartet.
	175	+The ACMP Server was able to establish a connection and the remote station reported a success (HTTP status 200), but the delivered response could not be successfully evaluated. It is possible that the format is different than expected.
265	265
266		-Mögliche Fehlerquelle ist, wenn ein System Informationen im Cache behält und diese als Antwort zurückliefert. Überprüfen Sie beispielsweise Ihre Proxyeinstellungen, ob der ACMP Server die richtigen Konfigurationen hinterlegt hat, um die URL auflösen zu können. Sollte das von Ihnen ausgeschlossen worden sein, wenden Sie sich bitte an unseren Support.
	177	+A possible source of error is when a system retains information in the cache and returns it as a response. For example, check your proxy settings to see if the ACMP Server has stored the correct configurations to resolve the URL. If you have excluded this, please contact our Support.
267	267	)))
268	268	|(((
269	269	„GraphAPI webcall returned failure but error information could not be deserialized.“
270	270	)))|(((
271		-Der ACMP Server konnte erfolgreich eine Verbindung aufbauen, jedoch meldet die Gegenstelle einen Fehler. Die gelieferte Antwort konnte nicht ausgewertet werden.
	182	+The ACMP Server was able to establish a connection successfully, but the remote station reports an error. The response could not be evaluated
272	272
273		-**Lösung**: Überprüfen Sie, ob die[[ Firewall/Proxy Einstellungen>>doc:ACMP.67.ACMP installieren.Checkliste zur Installation.WebHome||anchor="HErforderlicheURLs"]] richtig konfiguriert sind.  Sollte das von Ihnen ausgeschlossen worden sein, wenden Sie sich bitte an unseren Support.
	184	+**Solution**: Check if the [[firewall/proxy settings>>doc:ACMP.69.ACMP installieren.Checkliste zur Installation.WebHome||anchor="HErforderlicheURLs"]] are configured correctly or whether you have something else in the network that is intercepting or blocking the communication.. If this has been excluded by you, please contact our Support.
274	274	)))
275	275	|(((
276	276	„Thumbprint from public key could not be read.“
277	277	)))|(((
278		-Dieser Fehler tritt ausschließlich auf, wenn Sie als Authentifizierungsmethode das Zertifikat verwendet haben.
	189	+This error only occurs if you have used the certificate as the authentication method.
279	279
280		-In diesem Fall versucht der ACMP Server einen JSON Web Token für die GraphAPI zu generieren. Hierbei muss der Fingerabdruck des öffentlichen Schlüssels des Zertifikats vermerkt werden. Beim Auslesen dieses Wertes trat ein Fehler auf.
	191	+In this case, the ACMP Server tries to generate a JSON Web Token for the GraphAPI. The fingerprint of the certificate's public key must be noted. An error occurred when reading this value.
281	281
282		-**Lösung**: Spielen Sie beim Auftreten des Fehlers das Zertifikat neu ein.
	193	+**Solution**: When the error occurs, reinstall the certificate.
283	283	)))
284	284	|(((
285	285	„JSON Web Token generation for authentication with GraphAPI failed.“
286	286	)))|(((
287		-Dieser Fehler tritt ausschließlich auf, wenn Sie als Authentifizierungsmethode das Zertifikat verwendet haben.
	198	+This error only occurs if you have used the certificate as the authentication method.
288	288
289		-Der ACMP Server versucht einen JSON Web Token für die GraphAPI mit dem privaten Schlüssel des Zertifikats zu signieren. Hierbei tritt ein Fehler auf.
	200	+The ACMP Server tries to sign a JSON Web Token for the GraphAPI with the certificate's private key. An error occurs.
290	290
291		-**Lösung**: Möglicherweise kann es sich um ein abgelaufenes Zertifikat handeln. Legen Sie entweder ein neues Zertifikat an oder spielen Sie beim Auftreten des Fehlers das Zertifikat erneut ein.
	202	+**Solution**: This may be an expired certificate. Either create a new certificate or re-import the certificate when the error occurs.
292	292	)))