Skip to content

Commit 7734461

Browse files
authored
Merge pull request #2129 from MicrosoftDocs/main
Published main to live, Monday 5:00 PM IST, 12/09
2 parents 3a163ab + 3667c1e commit 7734461

File tree

5 files changed

+13
-12
lines changed

5 files changed

+13
-12
lines changed

CloudAppSecurityDocs/protect-workplace.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,14 @@
22
title: Protect your Workplace environment | Microsoft Defender for Cloud Apps
33
description: Learn how about connecting your Workplace app to Defender for Cloud Apps using the API connector.
44
ms.topic: how-to
5-
ms.date: 12/06/2023
5+
ms.date: 12/08/2024
66
---
77

88
# How Defender for Cloud Apps helps protect your Workplace environment (Preview)
99

1010

1111

12-
Workplace by Meta is an online collaboration software tool developed by Meta that facilitates online groupwork, instant messaging, video conferencing, and news sharing in one place. Along with the benefits of effective collaboration in the cloud, your organization's most critical assets may be exposed to threats. Exposed assets include messages, posts, and files with potentially sensitive information, collaboration, partnership details, and more. Preventing exposure of this data requires continuous monitoring to prevent any malicious actors or security-unaware insiders from exfiltrating sensitive information.
12+
Workplace by Meta is an online collaboration software tool developed by Meta that facilitates online group work, instant messaging, video conferencing, and news sharing in one place. Along with the benefits of effective collaboration in the cloud, your organization's most critical assets may be exposed to threats. Exposed assets include messages, posts, and files with potentially sensitive information, collaboration, partnership details, and more. Preventing exposure of this data requires continuous monitoring to prevent any malicious actors or security-unaware insiders from exfiltrating sensitive information.
1313

1414
Connecting Workplace by Meta to Defender for Cloud Apps gives you improved insights into your users' activities and provides threat detection for anomalous behavior.
1515

@@ -96,6 +96,7 @@ This section provides instructions for connecting Microsoft Defender for Cloud A
9696
> - The first connection can take up to 4 hours to get all users and their activities.
9797
> - The activities that will show are the activities that were generated from the moment the connector is connected.
9898
> - After the connector's **Status** is marked as **Connected**, the connector is live and works.
99+
> - Before deleting the app in Workplace, make sure to disconnect the connector in the Defender for Cloud Apps portal.
99100
100101
## Next steps
101102

defender-office-365/anti-spam-protection-about.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.custom:
1919
- seo-marvel-apr2020
2020
description: Admins can learn about the anti-spam settings and filters that help prevent spam in Exchange Online Protection (EOP).
2121
ms.service: defender-office-365
22-
ms.date: 10/18/2023
22+
ms.date: 12/08/2024
2323
appliesto:
2424
- ✅ <a href="https://learn.microsoft.com/defender-office-365/eop-about" target="_blank">Exchange Online Protection</a>
2525
- ✅ <a href="https://learn.microsoft.com/defender-office-365/mdo-about#defender-for-office-365-plan-1-vs-plan-2-cheat-sheet" target="_blank">Microsoft Defender for Office 365 Plan 1 and Plan 2</a>
@@ -133,15 +133,15 @@ These settings aren't configured in the default anti-spam policy by default, or
133133

134134
|Action|Spam|High<br>confidence<br>spam|Phishing|High<br>confidence<br>phishing|Bulk|
135135
|---|:---:|:---:|:---:|:---:|:---:|
136-
|**Move message to Junk Email folder**: The message is delivered to the mailbox and moved to the Junk Email folder|✔<sup>\*</sup>|✔<sup>\*</sup>||²|✔<sup>\*</sup>|
136+
|**Move message to Junk Email folder**: The message is delivered to the Junk Email folder in the mailbox|✔<sup>\*</sup>|✔<sup>\*</sup>||²|✔<sup>\*</sup>|
137137
|**Add X-header**: Adds an X-header to the message header and delivers the message to the mailbox. <br/><br/> You enter the X-header field name (not the value) in the available **Add this X-header text** box. <br/><br/> For **Spam** and **High confidence spam** verdicts, the message is moved to the Junk Email folder.¹ ³||||||
138138
|**Prepend subject line with text**: Adds text to the beginning of the message's subject line. The message is delivered to the mailbox and moved to the Junk email folder.¹ ³ <br/><br/> You enter the text in the available **Prefix subject line with this text** box.||||||
139139
|**Redirect message to email address**: Sends the message to other recipients instead of the intended recipients. <br/><br/> You specify the recipients in the **Redirect to this email address** box.||||||
140140
|**Delete message**: Silently deletes the entire message, including all attachments.||||||
141141
|**Quarantine message**: Sends the message to quarantine instead of the intended recipients. <br/><br/> You select or use the default _quarantine policy_ for the spam filtering verdict in the **Select quarantine policy** box that appears.⁴ Quarantine policies define what users are able to do to quarantined messages, and whether users receive quarantine notifications. For more information, see [Anatomy of a quarantine policy](quarantine-policies.md#anatomy-of-a-quarantine-policy). <br/><br/> You specify how long the messages are held in quarantine in the available **Retain spam in quarantine for this many days** box.|||✔<sup>\*</sup>|✔<sup>\*</sup> ⁵||
142142
|**No action**||||||
143143

144-
¹ EOP uses its own mail flow delivery agent to route messages to the Junk Email folder instead of using the junk email rule in the mailbox. The _Enabled_ parameter on the **Set-MailboxJunkEmailConfiguration** cmdlet in Exchange Online PowerShell has effect on mail flow in cloud mailboxes. For more information, see [Configure junk email settings on Exchange Online mailboxes](configure-junk-email-settings-on-exo-mailboxes.md).
144+
¹ EOP uses its own mail flow delivery agent to route messages to the Junk Email folder instead of using the junk email rule in the mailbox. The _Enabled_ parameter on the **Set-MailboxJunkEmailConfiguration** cmdlet in Exchange Online PowerShell has no effect on mail flow in cloud mailboxes. For more information, see [Configure junk email settings on Exchange Online mailboxes](configure-junk-email-settings-on-exo-mailboxes.md).
145145

146146
² For **High confidence phishing**, the **Move message to Junk Email folder** action is effectively deprecated. Although you might be able to select the **Move message to Junk Email folder** action, high confidence phishing messages are always quarantined (equivalent to selecting **Quarantine message**).
147147

defender-office-365/configure-junk-email-settings-on-exo-mailboxes.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.collection:
1616
- tier2
1717
description: Admins can learn how to configure the junk email settings in Exchange Online mailboxes. Many of these settings are available to users in Outlook or Outlook on the web.
1818
ms.service: defender-office-365
19-
ms.date: 09/16/2024
19+
ms.date: 12/08/2024
2020
appliesto:
2121
- ✅ <a href="https://learn.microsoft.com/defender-office-365/eop-about" target="_blank">Exchange Online Protection</a>
2222
- ✅ <a href="https://learn.microsoft.com/defender-office-365/mdo-about#defender-for-office-365-plan-1-vs-plan-2-cheat-sheet" target="_blank">Microsoft Defender for Office 365 Plan 1 and Plan 2</a>
@@ -31,11 +31,11 @@ In Microsoft 365 organizations with mailboxes in Exchange Online, organizational
3131

3232
But, there are also specific anti-spam settings that admins can configure on individual mailboxes in Exchange Online:
3333

34-
- **Move messages to the Junk Email folder based on anti-spam policies**: When an anti-spam policy is configured with the action **Move message to Junk Email folder** for a spam filtering verdict, the message is moved to the Junk Email folder _after_ the message is delivered to the mailbox. For more information about spam filtering verdicts in anti-spam policies, see [Configure anti-spam policies in EOP](anti-spam-policies-configure.md). Similarly, if zero-hour auto purge (ZAP) determines that a delivered message is spam or phish, the message is moved to the Junk Email folder for **Move message to Junk Email folder** spam filtering verdict actions. For more information about ZAP, see [Zero-hour auto purge (ZAP) in Exchange Online](zero-hour-auto-purge.md).
34+
- **Deliver messages to the Junk Email folder based on anti-spam policies**: When an anti-spam policy is configured with the action **Move message to Junk Email folder** for a spam filtering verdict, the message is delivered to the Junk Email folder of the mailbox. For more information about spam filtering verdicts in anti-spam policies, see [Configure anti-spam policies in EOP](anti-spam-policies-configure.md). Similarly, if zero-hour auto purge (ZAP) determines that a delivered message is spam or phishing, the message is moved to the Junk Email folder for **Move message to Junk Email folder** spam filtering verdict actions. For more information about ZAP, see [Zero-hour auto purge (ZAP) in Exchange Online](zero-hour-auto-purge.md).
3535

3636
- **Junk email settings that users configure for themselves in Outlook or Outlook on the web**: The _safelist collection_ is the Safe Senders list, the Safe Recipients list, and the Blocked Senders list on each mailbox. The entries in these lists determine whether the message is moved to the Inbox or the Junk Email folder. Users can configure the safelist collection for their own mailboxes in Outlook or Outlook on the web (formerly known as Outlook Web App). Admins can configure the safelist collection on any user's mailbox.
3737

38-
EOP is able to move messages to the Junk Email folder based on the spam filtering verdict action **Move message to Junk Email folder** or the Blocked Senders list on the mailbox, and prevent messages from being delivered to the Junk Email folder (based on the Safe Senders list on the mailbox).
38+
EOP is able to deliver messages to the Junk Email folder based on the spam filtering verdict action **Move message to Junk Email folder** and the Blocked Senders list in the mailbox, and prevent messages from being delivered to the Junk Email folder based on the Safe Senders list on the mailbox.
3939

4040
Admins can use Exchange Online PowerShell to configure entries in the safelist collection on mailboxes (the Safe Senders list, the Safe Recipients list, and the Blocked Senders list).
4141

defender-office-365/secure-by-default.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,8 +38,8 @@ However, security needs to be balanced with productivity. This can include balan
3838

3939
Microsoft 365 organizations with mailboxes in Exchange Online are protected by Exchange Online Protection (EOP). This protection includes:
4040

41-
- Email with suspected malware will automatically be quarantined. Whether recipients are notified about quarantined malware messages is controlled by the quarantine policy and the settings in the anti-malware policy. For more information, see [Configure anti-malware policies in EOP](anti-malware-policies-configure.md).
42-
- Email identified as high confidence phishing will be handled according to the anti-spam policy action. See [Configure anti-spam policies in EOP](anti-spam-policies-configure.md).
41+
- Email with suspected malware is automatically quarantined. Whether recipients are notified about quarantined malware messages is controlled by the quarantine policy and the settings in the anti-malware policy. For more information, see [Configure anti-malware policies in EOP](anti-malware-policies-configure.md).
42+
- Email identified as high confidence phishing is handled according to the anti-spam policy action. See [Configure anti-spam policies in EOP](anti-spam-policies-configure.md).
4343

4444
For more information about EOP, see [Exchange Online Protection overview](eop-about.md).
4545

@@ -55,7 +55,7 @@ If you want to temporarily allow certain messages that are still being blocked b
5555
More information on these overrides can be found in [Create safe sender lists](create-safe-sender-lists-in-office-365.md).
5656

5757
> [!NOTE]
58-
> We have deprecated the **Move message to Junk Email folder** action for a **High confidence phishing email** verdict in EOP anti-spam policies. Anti-spam policies that use this action for high confidence phishing messages will be converted to **Quarantine message**. The **Redirect message to email address** action for high confidence phishing messages is unaffected.
58+
> The **Move message to Junk Email folder** action for a **High confidence phishing email** verdict in EOP anti-spam policies has been deprecated. Anti-spam policies that use this action for high confidence phishing messages are converted to **Quarantine message**. The **Redirect message to email address** action for high confidence phishing messages is unaffected.
5959
6060
Secure by default isn't a setting that can be turned on or off, but is the way our filtering works out of the box to keep potentially dangerous or unwanted messages out of your mailboxes. Malware and high confidence phishing messages should be quarantined. By default, only admins can manage messages that are quarantined as malware or high confidence phishing, and they can also report false positives to Microsoft from there. For more information, see [Manage quarantined messages and files as an admin in EOP](quarantine-admin-manage-messages-files.md).
6161

defender-xdr/advanced-hunting-devicebaselinecomplianceassessment-table.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ For information on other tables in the advanced hunting schema, see [the advance
4545
| `OSVersion` | `string` | Version of the operating system running on the device |
4646
| `ConfigurationId` | `string` | Unique identifier for a specific configuration |
4747
| `ProfileId` | `string` | Unique identifier for the profile |
48-
| `IsCompliant` | `boolean` | Indicates whether the device that initiated the event is compliant or not |
48+
| `IsCompliant` | `nullable` | Indicates whether the device that initiated the event is compliant or not |
4949
| `IsApplicable` | `boolean` | Indicates whether the configuration or policy is applicable |
5050
| `Source` | `dynamic` | The registry path or other location used to determine the current device setting |
5151
| `RecommendedValue` | `dynamic` | Set of expected values for the current device setting to be compliant |

0 commit comments

Comments
 (0)