Merge branch 'main' into patch-43

Author: MithunRathinam

defender-for-identity/configure-scoped-access.md

@@ -56,7 +56,7 @@ The following table lists the current limitations and supported scenarios for sc
 
 > [!NOTE]
 > - Custom roles apply only to new alerts and activities. Alerts and activities triggered before a custom role was created aren't retroactively tagged or filtered.
->
+> - The Exposure Management section in the Defender Portal is not visible to users with an MDI scope assignment.
 > - Microsoft Entra ID IP alerts aren't included within scoped MDI detections.
 
 |Defender for Identity experience |Scoping by OU's|Scoping by AD domain|

exposure-management/palo-alto-prisma-data-connector.md

@@ -37,7 +37,7 @@ First, you need to create a service account with the required permissions to get
 To establish a connection with Palo Alto Prisma in Exposure Management, follow these steps:
 
 1. Open the [Exposure Management Connectors](https://security.microsoft.com/exposure-data-connectors) page and click **Connect** in the Palo Alto tile.
-2. Enter your Palo Alto API URL and authentication credentials, then click **Connect**.
+2. Enter your Palo Alto **Endpoint** and authentication credentials, then click **Connect**.
 
 ## Retrieved data