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
Some applications utilize non-interactive access tokens to facilitate seamless redirection between apps within the same suite or realm. When one application is onboarded to Conditional Access App Control and the other is not, session controls may not be enforced as expected. For example, if the Teams client retrieves a non-interactive token for SharePoint Online (SPO), it can initiate an active session in SPO without prompting the user for reauthentication. As a result, the session control mechanism cannot intercept or enforce policies on these sessions. To ensure consistent enforcement, it's recommended to onboard all relevant applications, such as Teams, alongside SPO.
56
56
57
+
## IPv6 limitations
58
+
Access and session policies support IPv4 only. If a request is made over IPv6, IP-based policy rules are not applied. This limitation applies when using both reverse proxy and Edge in-browser protection.
59
+
57
60
## Limitations for sessions that the reverse proxy serves
58
61
59
62
The following limitations apply only on sessions that the reverse proxy serves. Users of Microsoft Edge can benefit from in-browser protection instead of using the reverse proxy, so these limitations don't affect them.
@@ -98,6 +101,7 @@ The following table lists example results when you define the **Block upload of
98
101
99
102
The following limitations apply only on sessions that are served with Edge in-browser protection.
100
103
104
+
101
105
### Deep link is lost when user switches to Edge by clicking 'Continue in Edge'
102
106
103
107
A user who starts a session in a browser other than Edge, is prompted to switch to Edge by clicking the ‘Continue in Edge’ button.
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/cas-compliance-trust.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,9 @@ Microsoft Defender for Cloud Apps collects information from your configured clou
21
21
- System settings and policies
22
22
- User and group configurations
23
23
24
+
> [!NOTE]
25
+
> The data collected from the various applications is dependent on the customer-provided data from the various applications and may include personal information.
26
+
24
27
## Data storage location
25
28
26
29
Defender for Cloud Apps operates in the Microsoft Azure data centers in the following geographical regions:
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/mde-govern.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,7 +120,8 @@ To block an app, do the following steps:
120
120
> - Any organizational scoping that was set manually on indicators that were created by Defender for Cloud Apps before the release of this feature will be overridden by Defender for Cloud Apps. The required scoping should be set from the Defender for Cloud Apps experience using the scoped profiles experience.
121
121
> - To remove a selected scoping profile from an unsanctioned app, remove the unsanctioned tag and then tag the app again with the required scoped profile.
122
122
> - It can take up to two hours for app domains to propagate and be updated in the endpoint devices once they're marked with the relevant tag or/and scoping.
123
-
> - When an app is tagged as *Monitored*, the option to apply a scoped profile shows only if the built-in *Win10 Endpoint Users* data source has consistently recieved data during the past 30 days.
123
+
> - When an app is tagged as *Monitored*, the option to apply a scoped profile shows only if the built-in *Win10 Endpoint Users* data source has consistently received data during the past 30 days.
124
+
> - Device groups in Microsoft Defender for Business(MDB) are managed differently. Due to this- No device groups will appear in MDA device groups for customers with MDB license.
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/protect-github.md
+3-7Lines changed: 3 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Protect your GitHub Enterprise environment | Microsoft Defender for Cloud Apps
3
3
description: Learn how about connecting your GitHub Enterprise app to Defender for Cloud Apps using the API connector.
4
-
ms.date: 12/05/2023
4
+
ms.date: 04/27/2025
5
5
ms.topic: how-to
6
6
---
7
7
# How Defender for Cloud Apps helps protect your GitHub Enterprise environment
@@ -85,10 +85,6 @@ These steps can be completed independently of the [Configure GitHub Enterprise C
85
85
86
86
1.**Create an OAuth App for Defender for Cloud Apps to connect your GitHub organization.** Repeat this step for each additional connected organization.
87
87
88
-
> [!NOTE]
89
-
> If you have [preview features](/microsoft-365/security/defender/preview) and [app governance turned on](app-governance-get-started.md), use the **App governance** page instead of the **OAuth apps** page to perform this procedure.
90
-
>
91
-
92
88
1. Browse to **Settings** > **Developer settings**, select **OAuth Apps**, and then select **Register an application**. Alternatively, if you have existing OAuth apps, select **New OAuth App**.
93
89
94
90

@@ -129,8 +125,8 @@ These steps can be completed independently of the [Configure GitHub Enterprise C
129
125
130
126
1. Select the **GitHub Profile picture** -> **your enterprises**.
131
127
1. Select **your enterprise account** and choose the account you want to connect to Microsoft Defender for Cloud Apps.
132
-
1. Confirm that the URL is the enterprise slug. For instance, in this example `https://github.com/enterprises/testEnterprise`*testEnterprise* is the enterprise slug. Enter only the enterprise slug, not the entire URL.
133
-
128
+
1. Confirm that the URL contains the enterprise slug. For instance, `https://github.com/enterprises/testEnterprise`
129
+
2. Enter only the enterprise slug, not the entire URL. In this example, *testEnterprise* is the enterprise slug.
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/protect-servicenow.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Protect your ServiceNow environment | Microsoft Defender for Cloud Apps
3
3
description: Learn how about connecting your ServiceNow app to Defender for Cloud Apps using the API connector.
4
-
ms.date: 12/12/2024
4
+
ms.date: 04/28/2025
5
5
ms.topic: how-to
6
6
---
7
7
@@ -152,14 +152,15 @@ For more information, see the [ServiceNow product documentation](https://docs.se
152
152
153
153
1. Select **Update**.
154
154
155
-
1. Establish an internal procedure to ensure that the connection remains alive. A couple of days before the expected expiration of the refresh token lifespan.
156
-
Revoke to the old refresh token. We don't recommend keeping old keys for security reasons.
157
-
158
-
1. On the ServiceNow pane, search for **System OAuth**, and then select **Manage Tokens**.
159
-
155
+
1. Establish an internal procedure to ensure that the connection remains active.
156
+
1. Before the expected expiration of the refresh token, revoke the old refresh token.
157
+
1. In the ServiceNow portal, search for **System OAuth**, and then select **Manage Tokens**.
160
158
1. Select the old token from the list according to the OAuth name and expiration date.
161
-
162
159
1. Select **Revoke Access > Revoke**.
160
+
1. In the Microsoft Defender Portal edit the existing connector, using the same client ID and client secret. This will generate a new refresh token.
161
+
162
+
> [!NOTE]
163
+
> This is a recurring process every 90 days. Without this, the ServiceNow connection will stop working.
163
164
164
165
1. In the Microsoft Defender Portal, select **Settings**. Then choose **Cloud Apps**. Under **Connected apps**, select **App Connectors**.
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/troubleshooting-proxy-url.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ For example, Contoso protects its environment using conditional access app contr
20
20
So even though Fabrikam doesn't actually use Defender for Cloud Apps, they see the DNS entry or certificate because Contoso does.
21
21
22
22
> [!NOTE]
23
-
> You may also see the following domains in the transparency logs:
23
+
> You might also see the following domains in the transparency logs:
24
24
>
25
25
> -`*.admin-rs-mcas.ms`
26
26
> -`*.rs-mcas.ms`
@@ -39,11 +39,12 @@ So even though Fabrikam doesn't actually use Defender for Cloud Apps, they see t
39
39
> -`*.admin-mcas-gov-df.ms`
40
40
> -`*.mcas-gov-df.ms`
41
41
42
+
42
43
## Here's why you see `*.mcas.ms`, `*.mcas-gov.us`, or `*.mcas-gov.ms` in your URL
43
44
44
45
This kind of URL is expected and indicates that your organization applies extra security controls to protect business-critical data.
45
46
46
-
They do this by using Defender for Cloud Apps, a solution for protecting your organization's cloud environment, to replace all relevant URLs and cookies relating to cloud apps that you use.
47
+
They do this by using Defender for Cloud Apps, a solution for protecting your organization's cloud environment, to replace all relevant URLs, and cookies relating to cloud apps that you use.
47
48
48
49
So when you try accessing a cloud app such as Salesforce, SharePoint Online, or AWS, you notice that its URL is suffixed with `.mcas.ms`, `.mcas-gov.us`, or `.mcas-gov.ms`. For example, when using the XYZ app, the URL you're used to seeing changes from `XYZ.com` to `XYZ.com.mcas.ms`.
49
50
@@ -52,10 +53,11 @@ If the URL doesn't exactly match one of the replacement patterns, such as `<app_
52
53
If you don't recognize the remaining portion of the URL, such as **myurl.com**.mcas.ms, as associated with any of your business apps, we recommend that you investigate the issue further and consider blocking the URL to avoid any potential security risks.
53
54
54
55
> [!NOTE]
55
-
> Microsoft Edge users benefit from in-browser protection, and are not redirected to a reverse proxy. Your URLs retain their original syntax in Microsoft Edge, even when access and sessions are protected by Defender for Cloud Apps. For more information, see [In-browser protection with Microsoft Edge for Business (Preview)](in-browser-protection.md).
56
+
> Microsoft Edge users benefit from in-browser protection, and aren't redirected to a reverse proxy. Your URLs retain their original syntax in Microsoft Edge, even when access and sessions are protected by Defender for Cloud Apps. For more information, see [In-browser protection with Microsoft Edge for Business (Preview)](in-browser-protection.md).
56
57
57
58
## Related content
58
59
60
+
-[Known limitations in Conditional Access app control](caac-known-issues.md)
59
61
-[Protect apps with Microsoft Defender for Cloud Apps Conditional Access app control](proxy-intro-aad.md)
60
62
-[Troubleshooting access and session controls for admin users](troubleshooting-proxy.md)
61
-
-[Troubleshooting access and session controls for end-users](troubleshooting-proxy-end-users.md)
63
+
-[Troubleshooting access and session controls for end-users](troubleshooting-proxy-end-users.md)
Copy file name to clipboardExpand all lines: defender-xdr/m365d-action-center.md
+5-10Lines changed: 5 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ f1.keywords:
8
8
ms.author: diannegali
9
9
author: diannegali
10
10
ms.localizationpriority: medium
11
-
ms.date: 5/9/2024
11
+
ms.date: 4/28/2025
12
12
manager: deniseb
13
13
audience: ITPro
14
14
ms.collection:
@@ -40,11 +40,6 @@ The unified Action center ([https://security.microsoft.com/action-center](https:
40
40
41
41
:::image type="content" source="/defender/media/m3d-action-center-unified.png" alt-text="The unified Action center in the Microsoft Defender portal." lightbox="/defender/media/m3d-action-center-unified.png":::
42
42
43
-
For example:
44
-
45
-
- If you were using the Action center in the Microsoft Defender Security Center ([https://securitycenter.windows.com/action-center](https://securitycenter.windows.com/action-center)), try the unified Action center in the <ahref="https://go.microsoft.com/fwlink/p/?linkid=2077139"target="_blank">Microsoft Defender portal</a>.
46
-
- If you were already using the <ahref="https://go.microsoft.com/fwlink/p/?linkid=2077139"target="_blank">Microsoft Defender portal</a>, you'll see several improvements in the Action center ([https://security.microsoft.com/action-center](https://security.microsoft.com/action-center)).
47
-
48
43
The unified Action center brings together remediation actions across Microsoft Defender for Endpoint and Microsoft Defender for Office 365. It defines a common language for all remediation actions and provides a unified investigation experience. Your security operations team has a "single pane of glass" experience to view and manage remediation actions.
49
44
50
45
You can use the unified Action center if you have appropriate permissions and one or more of the following subscriptions:
@@ -59,20 +54,20 @@ You can use the unified Action center if you have appropriate permissions and on
59
54
You can navigate to the list of actions pending approval in two different ways:
60
55
61
56
- Go to [https://security.microsoft.com/action-center](https://security.microsoft.com/action-center); or
62
-
- In the Microsoft Defender portal ([https://security.microsoft.com](https://security.microsoft.com)), in the Automated investigation & response card, select **Approve in Action Center**.
57
+
- In the Microsoft Defender portal ([https://security.microsoft.com](https://security.microsoft.com)) homepage, in the Automated investigation & response card, select **View pending actions**.
63
58
64
59
## Using the Action center
65
60
66
61
1. Go to <ahref="https://go.microsoft.com/fwlink/p/?linkid=2077139"target="_blank">Microsoft Defender portal</a> and sign in.
67
62
68
-
2. In the navigation pane under **Actions and submissions**, choose **Action center**. Or, in the Automated investigation & response card, select **Approve in Action Center**.
63
+
2. In the navigation pane under **Actions and submissions**, choose **Action center**. Or, in the Automated investigation & response card in the homepage, select **View pending actions**.
69
64
70
65
3. Use the **Pending actions** and **History** tabs. The following table summarizes what you'll see on each tab:
71
66
72
67
|Tab|Description|
73
68
|---|---|
74
-
|**Pending**|Displays a list of actions that require attention. You can approve or reject actions one at a time, or select multiple actions if they have the same type of action (such as Quarantine file). <br/><br/> Make sure to review and approve (or reject) pending actions as soon as possible so that your automated investigations can complete in a timely manner.|
75
-
|**History**|Serves as an audit log for actions that were taken, such as: <ul><li>>Remediation actions that were taken as a result of automated investigations</li><li>Remediation actions that were taken on suspicious or malicious email messages, files, or URLs</li><li>Remediation actions that were approved by your security operations team</li><li>Commands that were run and remediation actions that were applied during Live Response sessions</li><li>Remediation actions that were taken by your antivirus protection</li></ul> <br/><br/> Provides a way to undo certain actions (see [Undo completed actions](m365d-autoir-actions.md#undo-completed-actions)).|
69
+
|**Pending**|Displays a list of actions that require attention. You can approve or reject actions one at a time, or select multiple actions if they have the same type of action (like Quarantine file). <br/><br/> Make sure to review and approve (or reject) pending actions as soon as possible so that your automated investigations can complete in a timely manner.|
70
+
|**History**|Serves as an audit log for actions that were taken, such as: <ul><li>Remediation actions that were taken as a result of automated investigations</li><li>Remediation actions that were taken on suspicious or malicious email messages, files, or URLs</li><li>Remediation actions that were approved by your security operations team</li><li>Commands that were run and remediation actions that were applied during Live Response sessions</li><li>Remediation actions that were taken by your antivirus protection</li></ul> <br/><br/> Provides a way to undo certain actions (see [Undo completed actions](m365d-autoir-actions.md#undo-completed-actions)).|
76
71
77
72
4. You can customize, sort, filter, and export data in the Action center.
0 commit comments