Skip to content

Commit 204f866

Browse files
committed
Update microsoft-defender-core-service-configurations-and-experimentation.md
1 parent fafa41f commit 204f866

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

defender-endpoint/microsoft-defender-core-service-configurations-and-experimentation.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: YongRhee-MSFT
77
ms.author: yongrhee
88
manager: deniseb
99
ms.localizationpriority: medium
10-
ms.date: 03/26/2024
10+
ms.date: 07/19/2024
1111
audience: ITPro
1212
ms.topic: troubleshooting
1313
ms.subservice: ngp
@@ -23,6 +23,7 @@ This article describes the interaction between Microsoft Defender Core Service a
2323

2424
> [!CAUTION]
2525
> If you disable communications with the service, this will affect Microsoft's ability to respond to a severe bug in a timely manner.
26+
2627
> [!IMPORTANT]
2728
> Make sure clients can access the following URLs so payloads can be received:
2829
>
@@ -33,18 +34,19 @@ This article describes the interaction between Microsoft Defender Core Service a
3334
>
3435
>Enterprise U.S. Government customers should allow the following URLs:
3536
> - `*.events.data.microsoft.com`
36-
> - `*.endpoint.security.microsoft.us (GCC-H & DoD)`
37-
> - `*.gccmod.ecs.office.com (GCC-M) *.config.ecs.gov.teams.microsoft.us (GCC-H)`
38-
> - `*.config.ecs.dod.teams.microsoft.us (DoD)`
37+
> - `*.endpoint.security.microsoft.us (GCC-H & DoD)`
38+
> - `*.gccmod.ecs.office.com (GCC-M)`
39+
>- `*.config.ecs.gov.teams.microsoft.us (GCC-H)`
40+
> - `*.config.ecs.dod.teams.microsoft.us (DoD)`
3941
4042
> [!NOTE]
41-
> This applies to Microsoft Defender Antivirus platform update version [4.18.24030](microsoft-defender-antivirus-updates.md) or later.
43+
> The information in this article applies to Microsoft Defender Antivirus platform update version [4.18.24030](microsoft-defender-antivirus-updates.md) or later.
4244
4345
## Configurations
4446

4547
Configurations are the payload meant to ensure product health, security, and privacy compliance, and are intended to have the same value for all the users (based on platforms and channels.) This could be to enable a feature flag for a domain action, and can also be used to disable a feature flag in the event of a bug.
4648

47-
## Controlled Feature Rollout
49+
## Controlled feature rollout
4850

4951
Controlled Feature Rollout (CFR) is a procedure for slowly increasing the size of the user group that receives a feature. By distributing a new feature to a randomly selected subset of the user population, it's possible to compare user feedback to an equally sized control group without the feature to measure the impact of the feature.
5052

0 commit comments

Comments
 (0)