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
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/real-time-agent-protection-during-runtime.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,22 +56,22 @@ The following steps describe the Security Administrator’s required actions to
56
56
-**If the connector isn’t connected:**
57
57
- Under **Microsoft 365 connector**, select **Connect** or **Edit**.
58
58
- Select **Microsoft Entra ID Management events** and **Microsoft 365 activities**.
59
-
- Select **Connect Microsoft 365**
59
+
- Select **Connect Microsoft 365**.
60
60
61
61
> [!IMPORTANT]
62
62
> If the Microsoft 365 connector isn’t properly connected, real-time agent protection during runtime continues to block suspicious activity on the AI agent. Alerts and incidents related to these actions won't show in the Microsoft Defender portal.
63
63
64
64
1. Make sure to collaborate with the following administrators:
65
65
66
-
- The **Microsoft Entra Administrator** needs to create [a Microsoft Entra ID application](/microsoft-copilot-studio/external-security-provider?branch=main&branchFallbackFrom=pr-en-us-1020#step-1-configure-microsoft-entra-application) and configure a Federated Identity Credential (FIC) using the URL provided in the Microsoft Defender portal. For more information, see: [Authorize the Microsoft Entra application with your provider of choice](/microsoft-copilot-studio/external-security-provider?branch=main&branchFallbackFrom=pr-en-us-1020#authorize-the-microsoft-entra-application-with-your-provider-of-choice).
66
+
- The **Microsoft Entra Administrator** needs to create [a Microsoft Entra ID application](/microsoft-copilot-studio/external-security-provider#step-1-configure-microsoft-entra-application) and configure a Federated Identity Credential (FIC) using the URL provided in the Microsoft Defender portal. For more information, see: [Authorize the Microsoft Entra application with your provider of choice](/microsoft-copilot-studio/external-security-provider#authorize-the-microsoft-entra-application-with-your-provider-of-choice).
67
67
68
-
- The **Power Platform Administrator** needs to enter the Application ID and URL in the Power Platform settings page. For more information see: [Enable external threat detection and protection for Copilot Studio custom agents](/microsoft-copilot-studio/external-security-provider?branch=main&branchFallbackFrom=pr-en-us-1020#authorize-the-microsoft-entra-application-with-your-provider-of-choice).
68
+
- The **Power Platform Administrator** needs to enter the Application ID and URL in the Power Platform settings page. For more information, see: [Enable external threat detection and protection for Copilot Studio custom agents](/microsoft-copilot-studio/external-security-provider#step-2-configure-the-threat-detection-system).
69
69
1. Enter the App ID provided by your Power Platform administrator. The Application (client) ID, uniquely identifies your application and is used in your application's code as part of validating the security tokens it receives from the Microsoft identity platform.
70
70
1. Select **Save**.
71
71
1. Copy the URL provided.
72
72
1. Share the URL with the Power Platform administrator.
73
73
74
-
:::image type="content" source="media/protect-agents-real-time/turn-on-real-time-agent-protection.png" alt-text="Screenshot that shows how to turn on Real time agent protection during runtime in the Defender portal." lightbox="media/protect-agents-real-time/turn-on-real-time-agent-protection.png":::
74
+
:::image type="content" source="media/protect-agents-real-time/turn-on-real-time-agent-protection.png" alt-text="Screenshot that shows how to turn on Real time agent protection during runtime in the Defender portal." lightbox="media/protect-agents-real-time/turn-on-real-time-agent-protection.png":::
Copy file name to clipboardExpand all lines: defender-office-365/email-authentication-dkim-configure.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,7 @@ Points to address or value: selector2-<CustomDomainWithDashes>._domainkey.<Initi
110
110
-**\<CustomDomainWithDashes\>**: The custom domain or subdomain with periods replaced by dashes. For example, `contoso.com` becomes `contoso-com`, or `marketing.contoso.com` becomes `marketing-contoso-com`.
111
111
-**\<InitialDomainPrefix\>**: The custom part of the \*.onmicrosoft.com you used to enroll in Microsoft 365. For example, if you used `contoso.onmicrosoft.com`, the value is `contoso`.
112
112
-**\<DynamicPartitionCharacter\>**: A dynamically generated character that's used for both selectors (for example, r or n). The value is automatically assigned by Microsoft when you add a new custom domain and enable DKIM. The value is determined by Microsoft's internal routing logic and isn't configurable.
113
-
- This value is part of the updated DKIM record format for new custom domains in Microsoft 365 introduced in May 2025. Existing custom domains and initial domains continue to use the old DKIM format:
113
+
-**This value is part of the updated DKIM record format for new custom domains in Microsoft 365 introduced in May 2025**. Existing custom domains and initial domains continue to use the old DKIM format:
114
114
115
115
```text
116
116
Hostname: selector1._domainkey
@@ -193,7 +193,7 @@ Proceed if the domain satisfies these requirements.
193
193
|Microsoft.Exchange.ManagementTasks.ValidationException|CNAME record does not
194
194
exist for this config. Please publish the following two CNAME records first. Domain Name
195
195
: contoso.com Host Name : selector1._domainkey Points to address or value: selector1-
196
-
contoso-com._domainkey.contoso.n-v1.dkim.mail.microsoft.com Host Name : selector2._domainkey
196
+
contoso-com._domainkey.contoso.n-v1.dkim.mail.microsoft Host Name : selector2._domainkey
197
197
Points to address or value: selector2-contoso-com._domainkey.contoso.n-v1.dkim.mail.microsoft .
198
198
If you have already published the CNAME records, sync will take a few minutes to as
199
199
many as 4 days based on your specific DNS. Return and retry this step later.
Copy file name to clipboardExpand all lines: defender-xdr/activate-defender-rbac.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,8 @@
2
2
title: Activate Microsoft Defender XDR Unified role-based access control (RBAC)
3
3
description: Activate Microsoft Defender XDR unified role-based access control(RBAC) to enforce permissions and assignments configured in your new custom or imported roles.
0 commit comments