@@ -42,15 +42,16 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
42
42
43
43
### Example 1
44
44
``` powershell
45
- {{ Add example code here }}
45
+ New-SensitiveInformationScan "SharePoint scan" -SharePointLocation All
46
+ New-SensitiveInformationScanRule "SharePoint scan rule" -ContentExtensionMatchesWords "pdf", "docx" -Policy "SharePoint scan" -Workload SharePoint
46
47
```
47
48
48
- {{ Add example description here }}
49
+ Above example creates a scan for all sharepoint sites scoped to pdf and docx files only. This cmdlet should be used in combination with New-SensitiveInformationScan.
49
50
50
51
## PARAMETERS
51
52
52
53
### -Name
53
- {{ Fill Name Description }}
54
+ Specify rule name for the scan
54
55
55
56
``` yaml
56
57
Type : String
@@ -66,7 +67,7 @@ Accept wildcard characters: False
66
67
` ` `
67
68
68
69
### -Policy
69
- {{ Fill Policy Description }}
70
+ Scan policy name that is parent of this rule
70
71
71
72
` ` ` yaml
72
73
Type : PolicyIdParameter
@@ -159,7 +160,7 @@ Accept wildcard characters: False
159
160
` ` `
160
161
161
162
# ## -ContentCreatedOrUpdatedDateFrom
162
- {{ Fill ContentCreatedOrUpdatedDateFrom Description }}
163
+ If specified, files last modified after this date are considered in scope of scan.
163
164
164
165
` ` ` yaml
165
166
Type: System.DateTime
@@ -175,7 +176,7 @@ Accept wildcard characters: False
175
176
` ` `
176
177
177
178
# ## -ContentCreatedOrUpdatedDateTo
178
- {{ Fill ContentCreatedOrUpdatedDateTo Description }}
179
+ Files last modified before this date are considered in scope of scan.
179
180
180
181
` ` ` yaml
181
182
Type: System.DateTime
@@ -259,7 +260,8 @@ Accept wildcard characters: False
259
260
` ` `
260
261
261
262
# ## -StartImpactAssessment
262
- {{ Fill StartImpactAssessment Description }}
263
+ Set to true to start an scan estimation by default. This needs to be passed as false to prevent starting scan estimation by default.
264
+
263
265
264
266
` ` ` yaml
265
267
Type: Boolean
0 commit comments