Skip to content

Commit 951b948

Browse files
authored
Update understanding-billable-assets.md
1 parent b8b4b3e commit 951b948

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/external-attack-surface-management/understanding-billable-assets.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ When customers create their first Microsoft Defender External Attack Surface Man
1818

1919
The following kinds of assets are considered billable:
2020

21-
- Approved host : IP combinations
21+
- Approved host:IP combinations
2222
- Approved domains
2323
- Approved IP addresses
2424

@@ -33,9 +33,9 @@ This section describes the conditions that the three aforementioned asset types
3333

3434

3535

36-
### Approved host : IP combinations
36+
### Approved host:IP combinations
3737

38-
Hosts are considered billable if the Defender EASM system has observed resolutions within the last 30 days. If the host is in the Approved Inventory state, the host : IP combination is identified as a billable asset. All hosts in the Approved Inventory state are considered billable, regardless of the state of the coinciding IP address. The IP address doesn't need to be in the Approved Inventory state for the host : IP combination to be included in your billable asset count.
38+
Hosts are considered billable if the Defender EASM system has observed resolutions within the last 30 days. If the host is in the Approved Inventory state, the host:IP combination is identified as a billable asset. All hosts in the Approved Inventory state are considered billable, regardless of the state of the coinciding IP address. The IP address doesn't need to be in the Approved Inventory state for the host:IP combination to be included in your billable asset count.
3939

4040

4141
For example: if www.contoso.com resolved to 1.2.3.4 and 5.6.7.8 in the past 30 days, both combinations are added to the host count list:

0 commit comments

Comments
 (0)