Merge branch 'main' into New-article-remove-unsafe-permissions-sensitive-entra-connect-

DeCohen · web-flow · commit 049b3a5a47e8 · 2025-03-24T12:27:49.000+02:00
diff --git a/CloudAppSecurityDocs/accounts.md b/CloudAppSecurityDocs/accounts.md
@@ -8,63 +8,62 @@ ms.topic: how-to
 
 
 
-Microsoft Defender for Cloud Apps gives you visibility into the accounts from your connected apps. After you connect Defender for Cloud Apps to an app using the App connector, Defender for Cloud Apps reads account information associated with connected apps. The Accounts page enables you to investigate those accounts, permissions, the groups they're members of, their aliases, and the apps they're using. Additionally, when Defender for Cloud Apps detects a new account that wasn't previously seen in one of the connected apps - for example, in activities or file sharing - the account is added to the accounts list of that app. This enables you to have visibility into the activity of external users interacting with your cloud apps.
+Microsoft Defender for Cloud Apps gives you visibility into the accounts from your connected applications. After you connect Defender for Cloud Apps to an app using the [App connector](/defender-cloud-apps/enable-instant-visibility-protection-and-governance-actions-for-your-apps), Defender for Cloud Apps reads account information associated with connected applications. The Cloud application accounts tab within the Identity inventory enables you to investigate those accounts, permissions, the groups they're members of, their aliases, and the apps they're using. Additionally, when Defender for Cloud Apps detects a new account that wasn't previously seen in one of the connected apps - for example, in activities or file sharing - the account is added to the accounts list of that app. This enables you to have visibility into the activity of external users interacting with your cloud apps.
 
-## Identity Inventory (Preview)
+## Identity Inventory
 
-> [!NOTE]
-> The Identities page is in the process of merging into the unified **Identity Inventory (Preview)**. 
-> 
-> The **Identity inventory** provides a centralized view of all identities in your organization, enabling you to monitor and manage them efficiently. At a glance, you can see key details such as Domain, Tags, Type, and other attributes, helping you quickly identify and manage identities that require attention. 
-> 
-> The functionality of the Identities page, as presented below, will be provided in the new Identity Inventory under the "**Cloud application accounts**" tab, offering the same features as it does today. For more details, visit the [Identity Inventory documentation](/defender-for-identity/identity-inventory).
-> 
-## Identities
+The visibility into cloud application accounts, as described above, is provided in the Identity Inventory under the "**Cloud application accounts**" tab.
 
-Admins can search for a specific user's metadata or user's activity. The **Identities** page provides you with comprehensive details about the entities that are pulled from connected cloud applications. It also provides the user's activity history and security alerts related to the user.
+The **Identity inventory** provides a centralized view of all identities in your organization, enabling you to monitor and manage them efficiently. At a glance, you can see key details such as Domain, Tags, Type, and other attributes, helping you quickly identify and manage identities that require attention. 
 
-The **Identities** page can be [filtered](#identities-filters) to enable you to find specific accounts and to deep dive into different types of accounts, for example, you can filter for all External accounts that haven't been accessed since last year.
+For more details, visit the [Identity Inventory documentation](/defender-for-identity/identity-inventory).
 
-The **Identities** page enables you to easily investigate your accounts, including the following issues:
+## Cloud Application Accounts
 
-* Check if any accounts have been inactive in a particular service for a long time (Maybe you should revoke the license for that user to that service)
+Admins can search for specific account metadata or account activity. The **Cloud application accounts** tab provides comprehensive details about entities pulled from connected cloud applications, including activity history and security alerts related to the account.
 
-* You can filter for the list of users with admin permissions
-* You can search for users who are no longer part of your organization but may still have active accounts
-* You can take [governance actions](#governance-actions) on the accounts, such as suspending an app or going to the account settings page.
-* You can see which accounts are included in each user group  
-* You can see which apps are accessed by each account and which apps are deleted for specific accounts
+The **Cloud application accounts** tab can be filtered to find specific accounts and deep dive into different types of accounts. For example, you can filter for all External accounts that haven't been accessed since last year.
 
-    ![accounts screen.](media/accounts-page.png)
-  
-### Identities filters
+The **Cloud application accounts** tab enables easy investigation of accounts, including:
+
+- Checking if any accounts have been inactive in a particular service for a long time (consider revoking the license for that user to that service).
+
+- Filtering for accounts with admin permissions.
+
+- Searching for accounts that are no longer part of your organization but may still have active accounts.
+
+- Taking governance actions on accounts, such as suspending an app or accessing the account settings page.
+
+- Viewing which accounts are included in each user group.
+
+- Seeing which apps are accessed by each account and which apps are deleted for specific accounts.
 
-Following is a list of the account filters that can be applied. Most filters support multiple values as well as NOT, in order to provide you with a powerful tool for policy creation.  
+[![Screenshot that shows the Cloud application accounts](media/accounts/cloud-application-accounts.png)](media/accounts/cloud-application-accounts.png#lightbox)
 
-* **Affiliation**: The affiliation is either **Internal** or **External**. To set which users and accounts are internal, under **Settings** make sure to set the **IP address range** of your internal organization. If the account has admin permissions the icon in the Accounts table appears with the addition of the red tie:
+### Accounts filters
+
+The Cloud application accounts tab offers comprehensive filtering capabilities, with pre-defined filters for a quick and easy experience.
+
+Admins can also enable the "Advanced filters" toggle to filter by additional attributes or create complex filters that include conditions such as "does not equal."  
+![Screenshot that shows the Advanced filters toggle.](media/accounts/image.png)
+
+Predefined filters include:
+
+- **Account name:** Filter specific accounts.
+
+- **Affiliation:** Internal or External. Set internal accounts under **Settings** by defining the **IP address range of your organization**. Admin accounts are marked with a red tie icon.
 
     ![accounts admin icon.](media/accounts-admin-icon.png)
   
-* **App**: You can filter for any API connected app being used by accounts in your organization.
-* **Domain**: This enables you to filter for users in specific domains.
-* **Groups**: Enables you to filter for members of user groups in Defender for Cloud Apps - both built-in user groups and imported user groups.
-* **Instance**: This enables you to filter for members of a specific app instance.
-* **Last seen**: The **last seen** filter enables you to find accounts that are dormant and whose users haven't performed any activities in a while.
-* **Organization**: This enables you to filter for members of specific organizational groups defined in your connected apps.
-* **Show Admins only**: Filters for accounts and users that are admins.
-* **Status**: Filter based on user account status of N/A, staged, active, suspended, or deleted. A status of not available (N/A) is normal and may appear, for example, for anonymous accounts.
-* **Type**: This enables you to filter to either the user or the account type.
-* **User name**: Enables you to filter specific users.
-
-### Governance actions
+- **App:** Filter for any connected app used by accounts in your organization.
 
-From the **Users and account** page, you can take governance actions such as suspending an app or going to the account settings page. For a full list of governance actions, see the [governance log](governance-actions.md).
+- **Groups:** Filter for members of user groups in Defender for Cloud Apps—both built-in and imported user groups.
 
-For example, if you identify a user that is compromised, you can apply the **Confirm user compromised** action to set the user risk level to high, causing the relevant policy actions defined in Microsoft Entra ID to be enforced. The action can be applied manually or using relevant [policies that support governance actions](governance-actions.md).
+- **Show Admins only:** Filter for admin accounts.
 
-#### To manually apply a user or account governance action
+### Additional actions
 
-From the **Users and account** page, on the row where the relevant user or account appears, choose the three dots at the end of the row, then select **Confirm user compromised**.
+Additional actions for further investigation, such as viewing related activities and incidents, are available through the Cloud application accounts tab. Click the three dots at the end of the relevant account's row to view available actions, or click on the account row to see additional accounts related to a single user. Additional actions are also available via the three dots at the end of the table in this view.
 
 ## Next steps
 
diff --git a/CloudAppSecurityDocs/additional-integrations.md b/CloudAppSecurityDocs/additional-integrations.md
@@ -27,6 +27,6 @@ The Defender for Cloud Apps robust platform allows you to integrate with a wide
 
     Defender for Cloud Apps allows security teams to automatically or manually confirm a user as compromised to ensure fast remediation of compromised users.
 
-    For more information, see [How does Microsoft Entra ID use my risk feedback](/azure/active-directory/identity-protection/howto-identity-protection-risk-feedback#how-does-azure-ad-use-my-risk-feedback) and [Governance actions](accounts.md#governance-actions).
+    For more information, see [How does Microsoft Entra ID use my risk feedback](/azure/active-directory/identity-protection/howto-identity-protection-risk-feedback#how-does-azure-ad-use-my-risk-feedback).
 
 [!INCLUDE [Open support ticket](includes/support.md)]
diff --git a/CloudAppSecurityDocs/media/accounts/cloud-application-accounts.png b/CloudAppSecurityDocs/media/accounts/cloud-application-accounts.png
diff --git a/CloudAppSecurityDocs/media/accounts/image.png b/CloudAppSecurityDocs/media/accounts/image.png
diff --git a/CloudAppSecurityDocs/protect-google-workspace.md b/CloudAppSecurityDocs/protect-google-workspace.md
@@ -159,6 +159,14 @@ This section provides instructions for connecting Microsoft Defender for Cloud A
 
     ![Google Workspace authorize new client ID.](media/connect-google-workspace/google-workspace-authorize-new-client-id.png)
 
+   >[!IMPORTANT]
+   > In order for the Google connector to function correctly, enable **Google Drive** for the Super Admin user that will be used for the connector.
+   > - Navigate to admin.google.com
+   > - Select apps -> Google Workspace -> Drive and Docs
+   > - Turn on Service status for the Super Admin user used to onboard the connector. We recommended enabling Service status for all users.
+
+   
+
 ### Configure Defender for Cloud Apps
 
 1. In the Microsoft Defender Portal, select **Settings**. Then choose **Cloud Apps**. Under **Connected apps**, select **App Connectors**.
diff --git a/CloudAppSecurityDocs/toc.yml b/CloudAppSecurityDocs/toc.yml
@@ -57,45 +57,8 @@ items:
       href: activity-privacy.md
     - name: Work with IP ranges and tags
       href: ip-tags.md
-- name: Cloud app discovery
-  items:
-  - name: Overview
-    displayName: cloud discovery, best practices
-    href: set-up-cloud-discovery.md
-  - name: Govern discovered apps
-    href: governance-discovery.md
-  - name: Enrich cloud discovery
-    href: cloud-discovery-aad-enrichment.md
-  - name: Anonymize cloud discovery data
-    href: cloud-discovery-anonymizer.md
-  - name: Configure cloud discovery
+  - name: Connect apps for visibility and protection
     items:
-    - name: Find your cloud app and calculate risk scores
-      href: risk-score.md
-    - name: Add custom apps to cloud discovery
-      href: cloud-discovery-custom-apps.md
-    - name: Attest your app
-      href: attest-your-app.md
-    - name: Collect logs
-      items:
-      - name: Configure automatic log upload for continuous reports
-        href: discovery-docker.md
-      - name: Podman on Linux on-premises
-        href: discovery-linux-podman.md
-      - name: Docker on Linux on-premises
-        href: discovery-docker-ubuntu.md
-      - name: Docker on Linux in Azure
-        href: discovery-docker-ubuntu-azure.md
-      - name: Docker on Azure Kubernetes Service
-        href: discovery-kubernetes.md
-      - name: Docker on Windows on-premises
-        href: discovery-docker-windows.md
-      - name: Advanced log collector management
-        href: log-collector-advanced-management.md
-      - name: Use the custom log parser
-        href: custom-log-parser.md
-    - name: Connect apps for visibility and protection
-      items:
       - name: Overview
         displayName: connect apps
         href: enable-instant-visibility-protection-and-governance-actions-for-your-apps.md
@@ -157,6 +120,43 @@ items:
         href: protect-zoom.md
       - name: Troubleshooting API connectors using error messages
         href: troubleshooting-api-connectors-using-error-messages.md
+- name: Cloud app discovery
+  items:
+  - name: Overview
+    displayName: cloud discovery, best practices
+    href: set-up-cloud-discovery.md
+  - name: Govern discovered apps
+    href: governance-discovery.md
+  - name: Enrich cloud discovery
+    href: cloud-discovery-aad-enrichment.md
+  - name: Anonymize cloud discovery data
+    href: cloud-discovery-anonymizer.md
+  - name: Configure cloud discovery
+    items:
+    - name: Find your cloud app and calculate risk scores
+      href: risk-score.md
+    - name: Add custom apps to cloud discovery
+      href: cloud-discovery-custom-apps.md
+    - name: Attest your app
+      href: attest-your-app.md
+    - name: Collect logs
+      items:
+      - name: Configure automatic log upload for continuous reports
+        href: discovery-docker.md
+      - name: Podman on Linux on-premises
+        href: discovery-linux-podman.md
+      - name: Docker on Linux on-premises
+        href: discovery-docker-ubuntu.md
+      - name: Docker on Linux in Azure
+        href: discovery-docker-ubuntu-azure.md
+      - name: Docker on Azure Kubernetes Service
+        href: discovery-kubernetes.md
+      - name: Docker on Windows on-premises
+        href: discovery-docker-windows.md
+      - name: Advanced log collector management
+        href: log-collector-advanced-management.md
+      - name: Use the custom log parser
+        href: custom-log-parser.md
     - name: Integrate with Microsoft Defender for Endpoint
       items:
       - name: Overview
diff --git a/CloudAppSecurityDocs/troubleshooting-api-connectors-using-error-messages.md b/CloudAppSecurityDocs/troubleshooting-api-connectors-using-error-messages.md
@@ -1,5 +1,5 @@
 ---
-title: Troubleshoot App Connector errors 
+title: Troubleshoot App connector errors 
 description: This article provides a list of API App connector error messages as well as resolution recommendations for each.
 ms.date: 01/29/2023
 ms.topic: conceptual
@@ -33,7 +33,8 @@ App connector errors can be seen in the app connector dialog after attempting to
 > |HttpRequestFailure: Server returned: 401 Unauthorized|Exchange Online|User or password are incorrect|Make sure the username and password are correct and Follow the process to connect Exchange Online to Defender for Cloud Apps again.|
 > |HttpRequestFailure: Server returned: 404 Not Found|Exchange Online|The user you are using to log into Exchange Online does not have a primary mailbox in Exchange Online (for example, a user who does not exist in Microsoft Entra ID or a user exists in Microsoft Entra ID, but does not have an Exchange Online license).|Follow the process to connect Exchange Online to Defender for Cloud Apps again using a new admin account.|
 > |GoogleJsonResponseException: 401 Unauthorized|Google Workspace|Access denied. You are not authorized to read activity records. The user you log into Google Workspace with must be an admin user.|Follow the process to connect Google Workspace to Defender for Cloud Apps again using an admin account.|
-> |GoogleJsonResponseException: 403 Forbidden|Google Workspace|Problem running the Google Workspace API.|If you just deployed the Defender for Cloud Apps App Connector for Google Workspace, check the following: If you clicked Unlimited, make sure that your Google Workspace account is really unlimited. If it is not, run the App Connector again and un-select the option for an unlimited account. Check that the scopes you defined during setup are correct. If this is not a new deployment and you see this error, it may be that you reached the API limit for today and Google Workspace events will be renewed tomorrow.|
+> |GoogleJsonResponseException: 403 Forbidden|Google Workspace|
+Problem running the Google Workspace API.|If you just deployed the Defender for Cloud Apps App Connector for Google Workspace, check the following: If you clicked Unlimited, make sure that your Google Workspace account is really unlimited. If it is not, run the App Connector again and un-select the option for an unlimited account. Check that the scopes you defined during setup are correct. If this is not a new deployment and you see this error, it may be that you reached the API limit for today and Google Workspace events will be renewed tomorrow.|
 > |TokenResponseException: 400 Bad Request|Google Workspace|Either the connection to Google Workspace did not complete or is expired.|Follow the process to connect Google Workspace to Defender for Cloud Apps again.|
 > |HttpRequestFailure: Server returned: 401 Unauthorized|Okta|The Okta token is not valid.|Follow the process to connect Okta to Defender for Cloud Apps again.|
 > |IOException:|Okta|Internal error|Contact support|
