Skip to content

Commit d1e9fc9

Browse files
Merge pull request #224869 from yelevin/docs-editor/bring-your-own-ml-1674582899
Fix for GitHub issue "Auto-export instruction - Code Sample - Bad Syntax #104033"
2 parents 2d38728 + 02aa17e commit d1e9fc9

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

articles/sentinel/bring-your-own-ml.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,6 @@ With the BYO-ML platform, you can get a jump start on building your own ML model
4040
- The libraries support data movements. Training and scoring notebooks demonstrate the end-to-end experience and serve as a template for you to adapt to your environment.
4141

4242
### Use cases
43-
4443
The BYO-ML platform and package significantly reduce the time and effort you'll need to build your own ML detections, and they unleash the capability to address specific security problems in Microsoft Sentinel. The platform supports the following use cases:
4544

4645
**Train an ML algorithm to get a customized model:** You can take an existing ML algorithm (shared by Microsoft or by the user community) and easily train it on your own data to get a customized ML model that better fits your data and environment.
@@ -99,6 +98,7 @@ You must be assigned the **Contributor** role in your Log Analytics workspace, y
9998

10099
Here is a sample set of commands to setup automatic exporting:
101100

101+
102102
```azurecli
103103
104104
az –version
@@ -113,10 +113,10 @@ az monitor log-analytics cluster list
113113
az account set --subscription "SUBSCRIPTION_NAME"
114114
115115
# Export to Storage - all tables
116-
az monitor log-analytics workspace data-export create --resource-group "RG_NAME" --workspace-name "WS_NAME" -n LAExportCLIStr --destination DESTINATION_NAME" --enable "true" --tables SecurityEvent
116+
az monitor log-analytics workspace data-export create --resource-group "RG_NAME" --workspace-name "WS_NAME" -n LAExportCLIStr --destination "DESTINATION_NAME" --enable "true" --tables SecurityEvent
117117
118118
# Export to EventHub - all tables
119-
az monitor log-analytics workspace data-export create --resource-group "RG_NAME" --workspace-name "WS_NAME" -n LAExportCLIEH --destination DESTINATION_NAME" --enable "true" --tables SecurityEvent Heartbeat"]
119+
az monitor log-analytics workspace data-export create --resource-group "RG_NAME" --workspace-name "WS_NAME" -n LAExportCLIEH --destination "DESTINATION_NAME" --enable "true" --tables ["SecurityEvent","Heartbeat"]
120120
121121
# List export settings
122122
az monitor log-analytics workspace data-export list --resource-group "RG_NAME" --workspace-name "WS_NAME"
@@ -165,3 +165,4 @@ Once you've set up the analytics rule based on the ML results, if there are resu
165165
In this document, you learned how to use Microsoft Sentinel's BYO-ML platform for creating or importing your own machine learning algorithms to analyze data and detect threats.
166166

167167
- See posts about machine learning and lots of other relevant topics in the [Microsoft Sentinel Blog](https://aka.ms/azuresentinelblog).
168+

0 commit comments

Comments
 (0)