You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|**Comments**|Available in Defender for Endpoint version 101.23062.0010 or higher.||
695
+
|**Comments**|Available in Defender for Endpoint version `101.23062.0010` or later.||
696
696
697
697
## Recommended configuration profile
698
698
699
699
To get started, we recommend the following configuration profile for your enterprise to take advantage of all protection features that Defender for Endpoint provides.
700
700
701
-
The following configuration profile will:
701
+
The following configuration profile:
702
702
703
-
-Enable real-time protection (RTP)
704
-
-Specify how the following threat types are handled:
703
+
-Enables real-time protection (RTP)
704
+
-Specifies how the following threat types are handled:
705
705
-**Potentially unwanted applications (PUA)** are blocked
706
706
-**Archive bombs** (file with a high compression rate) are audited to the product logs
707
-
-Enable automatic security intelligence updates
708
-
-Enable cloud-delivered protection
709
-
-Enable automatic sample submission at `safe` level
707
+
-Enables automatic security intelligence updates
708
+
-Enables cloud-delivered protection
709
+
-Enables automatic sample submission at `safe` level
710
710
711
711
### Sample profile
712
712
@@ -815,32 +815,34 @@ The following configuration profile contains entries for all settings described
815
815
When you run the `mdatp health` command for the first time, the value for the tag and group ID will be blank. To add tag or group ID to the `mdatp_managed.json` file, follow the below steps:
816
816
817
817
1. Open the configuration profile from the path `/etc/opt/microsoft/mdatp/managed/mdatp_managed.json`.
818
-
2. Go down to the bottom of the file, where the `cloudService` block is located.
819
-
3. Add the required tag or group ID as following example at the end of the closing curly bracket for the `cloudService`.
820
818
821
-
```JSON
822
-
},
823
-
"cloudService": {
819
+
2. Go down to the bottom of the file, where the `cloudService` block is located.
820
+
821
+
3. Add the required tag or group ID as following example at the end of the closing curly bracket for the `cloudService`.
822
+
823
+
```JSON
824
+
},
825
+
"cloudService": {
824
826
"enabled": true,
825
827
"diagnosticLevel": "optional",
826
828
"automaticSampleSubmissionConsent": "safe",
827
829
"automaticDefinitionUpdateEnabled": true,
828
830
"proxy": "http://proxy.server:port/"
829
-
},
830
-
"edr": {
831
-
"groupIds":"GroupIdExample",
832
-
"tags": [
831
+
},
832
+
"edr": {
833
+
"groupIds":"GroupIdExample",
834
+
"tags": [
833
835
{
834
836
"key": "GROUP",
835
837
"value": "Tag"
836
838
}
837
839
]
838
840
}
839
-
}
840
-
```
841
+
}
842
+
```
841
843
842
-
>[!NOTE]
843
-
>Add the comma after the closing curly bracket at the end of the `cloudService` block. Also, make sure that there are two closing curly brackets after adding Tag or Group ID block (please see the above example). At the moment, the only supported key name for tags is `GROUP`.
844
+
> [!NOTE]
845
+
> Add the comma after the closing curly bracket at the end of the `cloudService` block. Also, make sure that there are two closing curly brackets after adding Tag or Group ID block (please see the above example). At the moment, the only supported key name for tags is `GROUP`.
0 commit comments