Skip to content

Commit 07db56b

Browse files
committed
45 days after last used date
Adding details about 45 days after last used date
1 parent 8738d5c commit 07db56b

4 files changed

+7
-4
lines changed

defender-office-365/tenant-allow-block-list-about.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ The following list describes what happens in the Tenant Allow/Block List when yo
9696
- If the message was blocked for any other reason, an allow entry for the sender email address or domain is created, and the entry appears on the **Domains & addresses** tab in the Tenant Allow/Block List.
9797
- If the message wasn't blocked due to filtering, no allow entries are created anywhere.
9898

99-
By default, allow entries for domains and email addresses, files, and URLs exist for 30 days. During those 30 days, Microsoft learns from the allow entries and [removes them or automatically extends them](https://techcommunity.microsoft.com/t5/microsoft-defender-for-office/automatic-tenant-allow-block-list-expiration-management-is-now/ba-p/3723447). After Microsoft learns from the removed allow entries, messages that contain those entities are delivered, unless something else in the message is detected as malicious. By default, allow entries for spoofed senders never expire.
99+
By default, allow entries for domains and email addresses, files, and URLs exist for 45 days after last used date. Whenever the entity is encountered during mailflow or time of click and the entity has not been learned to be clean by the filtering, the allow entry will kick in and in the real time the last used date will be updated. So the 45 day after last used date will keep the allow entry for 45 days after the filtering system has learned the entity to be clean and you will have full visibility into it. By default, allow entries for spoofed senders never expire.
100100

101101
> [!IMPORTANT]
102102
> Microsoft doesn't allow you to create allow entries directly. Unnecessary allow entries expose your organization to malicious email that could have been filtered by the system.

defender-office-365/tenant-allow-block-list-email-spoof-configure.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Instead, you use the **Emails** tab on the **Submissions** page at <https://secu
8282
>
8383
> When the entity in the allow entry is encountered again (during mail flow or at time of click), all filters associated with that entity are overridden.
8484
>
85-
> By default, allow entries for domains and email addresses exist for 30 days. During those 30 days, Microsoft learns from the allow entries and [removes them or automatically extends them](https://techcommunity.microsoft.com/t5/microsoft-defender-for-office/automatic-tenant-allow-block-list-expiration-management-is-now/ba-p/3723447). After Microsoft learns from the removed allow entries, messages that contain those entities are delivered, unless something else in the message is detected as malicious.
85+
> By default, allow entries for domains and email addresses, files, and URLs exist for 45 days after last used date. Whenever the entity is encountered during mailflow or time of click and the entity has not been learned to be clean by the filtering, the allow entry will kick in and in the real time the last used date will be updated. So the 45 day after last used date will keep the allow entry for 45 days after the filtering system has learned the entity to be clean and you will have full visibility into it.
8686
>
8787
> During mail flow, if messages containing the allowed entity pass other checks in the filtering stack, the messages will be delivered. For example, if a message passes [email authentication checks](email-authentication-about.md), URL filtering, and file filtering, the message is delivered if it's also from an allowed sender.
8888
@@ -220,6 +220,7 @@ In existing domain and email address entries, you can change the expiration date
220220
- **1 day**
221221
- **7 days**
222222
- **30 days**
223+
- **45 days after last used date**
223224
- **Specific date**: The maximum value is 30 days from today.
224225
- **Optional note**
225226

defender-office-365/tenant-allow-block-list-files-configure.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Instead, you use the **Email attachments** tab on the **Submissions** page at <h
8282
>
8383
> When the entity in the allow entry is encountered again (during mail flow or at time of click), all filters associated with that entity are overridden.
8484
>
85-
> By default, allow entries for files exist for 30 days. During those 30 days, Microsoft learns from the allow entries and [removes them or automatically extends them](https://techcommunity.microsoft.com/t5/microsoft-defender-for-office/automatic-tenant-allow-block-list-expiration-management-is-now/ba-p/3723447). After Microsoft learns from the removed allow entries, messages that contain those entities are delivered, unless something else in the message is detected as malicious.
85+
> By default, allow entries for domains and email addresses, files, and URLs exist for 45 days after last used date. Whenever the entity is encountered during mailflow or time of click and the entity has not been learned to be clean by the filtering, the allow entry will kick in and in the real time the last used date will be updated. So the 45 day after last used date will keep the allow entry for 45 days after the filtering system has learned the entity to be clean and you will have full visibility into it.
8686
>
8787
> During mail flow, if messages containing the allowed entity pass other checks in the filtering stack, the messages are delivered. For example, if a message passes [email authentication checks](email-authentication-about.md), the message is delivered if it also contains an allowed file.
8888
>
@@ -221,6 +221,7 @@ In existing file entries, you can change the expiration date and note.
221221
- **1 day**
222222
- **7 days**
223223
- **30 days**
224+
- **45 days after last used date**
224225
- **Specific date**: The maximum value is 30 days from today.
225226
- **Optional note**
226227

defender-office-365/tenant-allow-block-list-urls-configure.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ Instead, you use the **URLs** tab on the **Submissions** page at <https://securi
8484
>
8585
> When the entity in the allow entry is encountered again (during mail flow or at time of click), all filters associated with that entity are overridden.
8686
>
87-
> By default, allow entries for URLs exist for 30 days. During those 30 days, Microsoft learns from the allow entries and [removes them or automatically extends them](https://techcommunity.microsoft.com/t5/microsoft-defender-for-office/automatic-tenant-allow-block-list-expiration-management-is-now/ba-p/3723447). After Microsoft learns from the removed allow entries, messages that contain those URLs are delivered, unless something else in the message is detected as malicious.
87+
> By default, allow entries for domains and email addresses, files, and URLs exist for 45 days after last used date. Whenever the entity is encountered during mailflow or time of click and the entity has not been learned to be clean by the filtering, the allow entry will kick in and in the real time the last used date will be updated. So the 45 day after last used date will keep the allow entry for 45 days after the filtering system has learned the entity to be clean and you will have full visibility into it.
8888
>
8989
> During mail flow, if messages containing the allowed URL pass other checks in the filtering stack, the messages are delivered. For example, if a message passes [email authentication checks](email-authentication-about.md) and file filtering, the message is delivered if it also contains an allowed URL.
9090
>
@@ -221,6 +221,7 @@ In existing URL entries, you can change the expiration date and note.
221221
- **1 day**
222222
- **7 days**
223223
- **30 days**
224+
- **45 days after last used date**
224225
- **Specific date**: The maximum value is 30 days from today.
225226
- **Optional note**
226227

0 commit comments

Comments
 (0)