You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add driver and docs
* Add M365DGraph data environment to compatible driver list
* Remove warnings import
* Fix numpy 2.0 NaN now being nan test failure
* Default to delegated auth when username is present in config or cs
---------
Co-authored-by: Ryan Cobb <[email protected]>
Co-authored-by: Ian Hellen <[email protected]>
Microsoft 365 Defender APIs can be accessed in both `application <https://learn.microsoft.com/en-us/defender-endpoint/api/exposed-apis-create-app-webapp>`
20
+
and `delegated user contexts <https://learn.microsoft.com/en-us/defender-endpoint/api/exposed-apis-create-app-nativeapp>`.
21
+
Accessing Microsoft 365 Defender APIs as an application requires
22
+
either a client secret or certificate, while delegated user auth requires
23
+
an interactive signin through a browser or via device code.
24
+
25
+
As such, the details on registering an Azure AD application for MS 365 Defender
26
+
are different for application and delegated user auth scenarios. Please
27
+
see the above links for more information. Notably, delegated user auth
28
+
scenarios do not require a application credential and thus is preferrable.
29
+
30
+
For delegated user auth scenarios, ensure that the application has a
31
+
"Mobile or Desktop Application" redirect URI configured as `http://localhost`.
32
+
A redirect URI is not required for applications with their own credentials.
33
+
34
+
API permissions for the client application will require tenant admin consent.
35
+
Ensure that the consented permissions are correct for the chosen data environment
36
+
and auth scenario (application or delegated user):
0 commit comments