init

demisto · Mar 4, 2025 · 4bc3e11 · 4bc3e11
1 parent c5cf857
commit 4bc3e11
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 0 deletions.
diff --git a/...urity/Integrations/MicrosoftGraphSecurity/MicrosoftGraphSecurity_description.md b/...urity/Integrations/MicrosoftGraphSecurity/MicrosoftGraphSecurity_description.md
@@ -19,6 +19,7 @@ If you previously had an API V1 configured based on the credentials obtained fro
 ### Important
 1. The ***eDiscovery*** and ***Threat Assessment*** commands are only supported when using the `Authorization Code flow` with `Delegated (work or school account)` permission type.
 2. When using `Authorization Code flow`, the connection should be tested using the ***!msg-auth-test*** command.
+3. When using the `Authorization Code flow` for this integration, the user needs to log in as an administrator or a user with administrative privileges (`Security Reader` or `Security Administrator`) after running the **msg-generate-login-url** command and the login window appears. For more information, see [here](https://learn.microsoft.com/en-us/graph/security-authorization).
 
 ### Authentication Based on Azure Managed Identities
 ##### Note: This option is relevant only if the integration is running on Azure VM.

diff --git a/Packs/MicrosoftGraphSecurity/Integrations/MicrosoftGraphSecurity/README.md b/Packs/MicrosoftGraphSecurity/Integrations/MicrosoftGraphSecurity/README.md
@@ -6,6 +6,8 @@ This integration was integrated and tested with version 1.0 of Microsoft Graph.
 For more details about the authentication used in this integration, see [Microsoft Integrations - Authentication](https://xsoar.pan.dev/docs/reference/articles/microsoft-integrations---authentication)  
 *Note*: [The eDiscovery](#ediscovery-commands) and [Threat Assessment](#threat-assessment-commands) commands are only supported when using the `Authorization Code flow` with `Delegated (work or school account)` permission type.
 
+When using the `Authorization Code flow` for this integration, the user needs to log in as an administrator or a user with administrative privileges (`Security Reader` or `Security Administrator`) after running the **msg-generate-login-url** command and the login window appears. For more information, see [here](https://learn.microsoft.com/en-us/graph/security-authorization).
+
 ## Important Notes:
 - Due to API limitations, the ***message-search-alerts*** command does not filter Office 365 provider alerts.\
 For more information, see: https://github.com/microsoftgraph/security-api-solutions/issues/56.