Create indicators for IPs and URLs/domains
In brief
The documentation now uses a local link, updates the URL precedence example, clarifies network protection logging, and restates that policy changes can take up to 48 hours to apply, usually under two hours.
What Defender admins need to know
Administrators have clearer guidance for configuring and troubleshooting indicators; no configuration change is required.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Create indicators for IPs and URLs/domains
Behavior Monitoring enabled.
Cloud-based protectionCloud-based protection turned on.
Network Protection requirements
Network allow and block indicators in Microsoft browsers are controlled by the browser's SmartScreen setting.
For other browsers and applications, network allow and block indicators require that the Microsoft Defender for Endpoint component Network Protection is enabled in block mode. For more information on Network Protection and configuration instructions, see Enable network protection.
- Only single IP addresses are supported (no CIDR blocks or IP ranges) in custom indicators
- HTTP URLs (including a full URL path) can be blocked for any browser or process
- HTTPS fully qualified domain names (FQDN) can be blocked in non-Microsoft browsers (indicators specifying a full URL path can only be blocked in Microsoft Edge)
- Blocking FQDNs in non-Microsoft browsers requires that QUIC and Encrypted Client Hello be disabled in those browsers
- FQDNs loaded via HTTP2 connection coalescing can only be blocked in Microsoft Edge
- If there are conflicting URL indicator policies, the longer path is applied. For example, the URL indicator policy
https://support.microsoft.com/takes precedence over the URL indicator policyofficemicrosoft-365/https://support.microsoft.com.
Network protection implementation
The determination of whether to allow or block access to a site is made after the completion of the three-way handshake via TCP/IP and any TLS handshake. Thus, when a site is blocked by network protection, you might see an action type of ConnectionSuccess under NetworkConnectionEvents in the Microsoft Defender portal, even though the site was blocked. NetworkConnectionEvents are reported from the TCP layer, and not from network protection. After the three-way handshake has completed, access to the site is allowed or blocked by network protection.
Here's an example of how that works:network protection blocking is logged:
Suppose that a user attempts to access a website on their device. The site happens to be hosted on a dangerous domain, and it should be blocked by network protection.
The TCP/IP handshake commences. Before it completes, a
NetworkConnectionEventsaction is logged, and itsActionTypeis listed asConnectionSuccess. However, as soon as the TCP/IP handshake process completes, network protection blocks access to the site.All of thisThe handshake, logging, and blocking sequence happens quickly. A similar process occurs withMicrosoft Defender SmartScreenMicrosoft Defender SmartScreen; it's after the handshake completes that a determination is made, and access to a site is either blocked or allowed.In the Microsoft Defender portal, an alert is listed in the alerts queue. Details of that alert include both
NetworkConnectionEventsandAlertEvents. You can see that the site was blocked, even though you also have aNetworkConnectionEventsitem with the ActionType ofConnectionSuccess.
Create an indicator for IPs, URLs, or domains from the settings page
To create an indicator for IPs, URLs, or domains from the Microsoft Defender portal, perform the following steps:
In the navigation pane, selectSettings>Endpoints>Indicators(underRules).Review the details in theSummarytab, then selectSave.
To create an indicator for IPs, URLs, or domains from the Microsoft Defender portal, perform the following steps:
- In the navigation pane, select Settings > Endpoints > Indicators (under Rules).
- Review the details in the Summary tab, then select Save.
Related content
@@ -6,19 +6,19 @@ ms.service: defender-endpoint ms.author: lwainstein author: limwainstein ms.localizationpriority: medium-ms.collection: +ms.collection: - m365-security - tier2 - -asr ms.topic: how-to-ms.subservice: -ms.date: 06/16/2026+ms.subservice:+ms.date: 07/03/2026 appliesto: - Microsoft Defender for Endpoint Plan 1 - Microsoft Defender for Endpoint Plan 2 ai-usage: ai-assisted-ms.custom: msecd-doc-authoring-1014+ms.custom: msecd-doc-authoring-1016 --- # Create indicators for IPs and URLs/domains @@ -48,7 +48,7 @@ Integration into Microsoft browsers is controlled by the browser's SmartScreen s - [Behavior Monitoring](behavior-monitor.md) enabled. -- [Cloud-based protection](/windows/security/threat-protection/microsoft-defender-antivirus/deploy-manage-report-microsoft-defender-antivirus) turned on.+- [Cloud-based protection](deploy-manage-report-microsoft-defender-antivirus.md) turned on. - [Cloud Protection network connectivity](configure-network-connections-microsoft-defender-antivirus.md). @@ -73,7 +73,7 @@ IP, URL, and domain indicators are supported on the following operating systems: ### Network Protection requirements -Network allow and block indicators in Microsoft browsers are controlled by the browser's SmartScreen setting. +Network allow and block indicators in Microsoft browsers are controlled by the browser's SmartScreen setting. For other browsers and applications, network allow and block indicators require that the Microsoft Defender for Endpoint component _Network Protection_ is enabled in **block mode**. For more information on Network Protection and configuration instructions, see [Enable network protection](enable-network-protection.md). @@ -97,9 +97,9 @@ For processes other than Microsoft Edge and Internet Explorer, web protection sc - Only single IP addresses are supported (no CIDR blocks or IP ranges) in custom indicators - HTTP URLs (including a full URL path) can be blocked for any browser or process - HTTPS fully qualified domain names (FQDN) can be blocked in non-Microsoft browsers (indicators specifying a full URL path can only be blocked in Microsoft Edge)-- Blocking FQDNs in non-Microsoft browsers requires that QUIC and Encrypted Client Hello be disabled in those browsers +- Blocking FQDNs in non-Microsoft browsers requires that QUIC and Encrypted Client Hello be disabled in those browsers - FQDNs loaded via HTTP2 connection coalescing can only be blocked in Microsoft Edge-- If there are conflicting URL indicator policies, the longer path is applied. For example, the URL indicator policy `https://support.microsoft.com/office` takes precedence over the URL indicator policy `https://support.microsoft.com`.+- If there are conflicting URL indicator policies, the longer path is applied. For example, the URL indicator policy `https://support.microsoft.com/microsoft-365/` takes precedence over the URL indicator policy `https://support.microsoft.com`. ## Network protection implementation @@ -107,11 +107,11 @@ In non-Microsoft Edge processes, Network Protection determines the fully qualifi The determination of whether to allow or block access to a site is made after the completion of the [three-way handshake via TCP/IP](/troubleshoot/windows-server/networking/three-way-handshake-via-tcpip) and any TLS handshake. Thus, when a site is blocked by network protection, you might see an action type of `ConnectionSuccess` under `NetworkConnectionEvents` in the Microsoft Defender portal, even though the site was blocked. `NetworkConnectionEvents` are reported from the TCP layer, and not from network protection. After the three-way handshake has completed, access to the site is allowed or blocked by network protection. -Here's an example of how that works:+Here's an example of how network protection blocking is logged: -1. Suppose that a user attempts to access a website on their device. The site happens to be hosted on a dangerous domain, and it should be blocked by network protection. +1. Suppose that a user attempts to access a website on their device. The site happens to be hosted on a dangerous domain, and it should be blocked by network protection. -1. The TCP/IP handshake commences. Before it completes, a `NetworkConnectionEvents` action is logged, and its `ActionType` is listed as `ConnectionSuccess`. However, as soon as the TCP/IP handshake process completes, network protection blocks access to the site. All of this happens quickly. A similar process occurs with [Microsoft Defender SmartScreen](/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview); it's after the handshake completes that a determination is made, and access to a site is either blocked or allowed.+1. The TCP/IP handshake commences. Before it completes, a `NetworkConnectionEvents` action is logged, and its `ActionType` is listed as `ConnectionSuccess`. However, as soon as the TCP/IP handshake process completes, network protection blocks access to the site. The handshake, logging, and blocking sequence happens quickly. A similar process occurs with [Microsoft Defender SmartScreen](/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen/); it's after the handshake completes that a determination is made, and access to a site is either blocked or allowed. 1. In the Microsoft Defender portal, an alert is listed in the [alerts queue](alerts-queue.md). Details of that alert include both `NetworkConnectionEvents` and `AlertEvents`. You can see that the site was blocked, even though you also have a `NetworkConnectionEvents` item with the ActionType of `ConnectionSuccess`. @@ -168,6 +168,9 @@ The result is that categories 1-4 are all blocked. This scenario is illustrated ## Create an indicator for IPs, URLs, or domains from the settings page +> [!IMPORTANT]+> It can take up to 48 hours after a policy is created for a URL or IP address to be blocked on a device. In most cases, blocks take effect in under two hours.+ To create an indicator for IPs, URLs, or domains from the Microsoft Defender portal, perform the following steps: 1. In the navigation pane, select **Settings** \> **Endpoints** \> **Indicators** (under **Rules**).@@ -185,7 +188,7 @@ To create an indicator for IPs, URLs, or domains from the Microsoft Defender por 1. Review the details in the **Summary** tab, then select **Save**. > [!IMPORTANT]-> It can take up to 48 hours after a policy is created for a URL or IP address to be blocked on a device. In most cases, blocks take effect in under two hours.+> After you create a policy for a URL or IP address, it can take up to 48 hours for the policy to take effect. In most cases, policy changes take effect in under two hours. <a name="related-articles"></a> ## Related content@@ -197,4 +200,3 @@ To create an indicator for IPs, URLs, or domains from the Microsoft Defender por - [Exclusions for Microsoft Defender for Endpoint and Microsoft Defender Antivirus](defender-endpoint-exclusions-overview.md) - 